I'm (ab)using elog as a database and would like to use conditional attributes, like:

Attributes = PC Name, Operating System, Version, Distribution
Options Operating System = Linux{1}, Windows{2}
{1} Show Attributes Edit = Operating System, Distribution, PC Name
{2} Show Attributes Edit = Operating System, PC Name, Version

Problem is that there are several conditions and the list of attributes is rather long. Also, since it's a
rather dynamic environment I have to make new attributes all the time, and adding them to all "show attributes"
 lists is not only tedious, but bound to cause errors as well.
 

So... 

I was thinking, would it be an idea to make the list of attributes to be shown or hidden on a per attribute base.

 

Like:

Attributes = PC Name, Operating System, Version, Distribution

# hide specific attributes
Hide attributes = Distribution, PC Name

# or configure which fields should be shown allways
Show Attributes = Operating System, Version

# add attributes based on OS
Options Operating System = Linux{1}, Windows{2}
{1} Show Attribute Edit = Distribution
{2} Show Attribute Edit = PC Name

(just thinking out loud here).

> I'm (ab)using elog as a database and would like to use conditional attributes, like:
> 
> Attributes = PC Name, Operating System, Version, Distribution
> Options Operating System = Linux{1}, Windows{2}
> {1} Show Attributes Edit = Operating System, Distribution, PC Name
> {2} Show Attributes Edit = Operating System, PC Name, Version
> 
> Problem is that there are several conditions and the list of attributes is rather long. Also, since it's a
> rather dynamic environment I have to make new attributes all the time, and adding them to all "show attributes"
>  lists is not only tedious, but bound to cause errors as well.
>  
> 
> So... 
> 
> I was thinking, would it be an idea to make the list of attributes to be shown or hidden on a per attribute base.
> 
>  
> 
> Like:
> 
> Attributes = PC Name, Operating System, Version, Distribution
> 
> # hide specific attributes
> Hide attributes = Distribution, PC Name
> 
> # or configure which fields should be shown allways
> Show Attributes = Operating System, Version
> 
> # add attributes based on OS
> Options Operating System = Linux{1}, Windows{2}
> {1} Show Attribute Edit = Distribution
> {2} Show Attribute Edit = PC Name
> 
> (just thinking out loud here).

Sure such a think can be implemented, but I have no time right now to do so. I will put it on the wish list.

Hi, I've been using the ELOG software for about a year now. I love it! But as my ELOG becomes more valuable, I become more paranoid about potential data loss. (We've had numerous close-calls with disk failures, recently.) Is there a way to download a backup of my ELOG, all at once? Maybe a command that could create a tar.gz of all the entries and attachments? Further, is there also a command to restore from such a backup? Apologies if this question is answered elsewhere. I couldn't readily find it in the documentation. Regards, --Ed

There is a simple way. In your logbook directory you will find files of the format xxyyzza.log where xxyyzz is the year/month/day of the entries being submitted during that day. The attachments have a similar form, they have just the attachment name appended to the date. To back it up, just copy or tar all files of that directory. If you want to back up a certain year, you can select 2009 for example with 09*.*  To restore these files, simply untar them into the directory and restart the elogd daemon. The restart is necessary, since during start the daemon indexes all entries. 

Hello,

Please could you help me.

We have 2 elog servers synchronized every minute via Elog mirroring function.

2 or 3 times a week, the slave crashes and we have to restart Elogd. I have found in /var/log/messages the same message every time elogd crash :

xmalloc: not enough memory

Thanks.

Dominique Bolla.

Is there any way I can limit the ammount of characters in the Subject line?

Thank you,