We use our instance of ELOG as a operations log so that newest events are sorted at the top.

Sometimes we are also up front informed about planned maintenance, and i would be nice to could "pin" them at the top - before the sorting, so that operatores could have them in mind when starting a new shift. Have anyone found a way to solve this?

Kind Regards Finn

The way to do this is to ensure that the date of the entry is in the future.  As a hard -core linux (ab)user of elog, I create an entry, then dive into the yymmdda.log files, and edit it so that the date at the top of the entry is, for example, Sat, 31 Dec 2022 23:59:59.  Then, that entry will remain at the top of the listings until the New Year.  I do this very thing for the very same reason, i.e. to keep one entry at the top of the listings until after a certain date.

It may be that if you have "date of entry" field and sort by that, you could set the date of entry in the future.  I've not tried that.

The same effect could be done by adjusting the computer/server's date to the future, make the entry and then reset back to the present, but that may well be unpopular and impractical.  On a single computer, I have done this, although I then changed to editing the yymmdda.log file directly.

We have always had issues with eLOG crashing intermittently...  I upgraded from Server 2003 to Server 2008 about a year ago to try to reduce the issues...  which really didn't help.

The service now seems to crash every week...  (getting worse)...  Is anyone seeing these issues in Windows servers?  Any suggestions??

We do run ELOG on a Linux server and see about weekly crashes, too. It seems to be connected to the authentication process (Kerberos, File), but we could not nail it down yet.

But we have set up a supervision process that checks every minute if the "elogd" process is still running. If not, it simply restarts it.

If ELOG is down for two minutes a week, this is fine for our users.

 How can I block access to some tools (like edit, erase, config...) for each user? I want only admin users can edit, erase , etc. 

I want know too, how can I erase configuration of SMTP?  I make a test with the "elogd -t" command and now every time I create a new entry in my log book I receve the mensage of error to send email, cause I don't configure a SMTP host. 

 Hello, you can use the "Deny" flag in the config file for each logbook.

Deny <function> = <user>

Example: Deny Edit = Gian

simply add as many deny functions as you would like. Its a bit of work if you have a lot of logbooks but its the easiest solution.

Hope that helps.

Elog Syntax guide is helpful for this stuff too.

 Thanks for help. It work's. 

 But I want to know if I can block a logbook from a user. For example I have a logbook named "Store". I want only users of the vendors have access to this log. How can I do it? 

I didn't find this in manual.

 The only way I find for this trouble is using the "Login user". But we have something best?