Hello,

I'm new to elog. I've installed it under Slackware 11. Everything worked smoothly until I wanted to establish access control. I followed the steps described under Access control heading in Syntax of elog.cfg chapter. I specified a new password file name and the following steps with no problem. After having created a new user I stopped elogd  and added  Admin user to config file. And here is my problem - each time I want to login to elog, I get "Invalid user name or password!" message. The meaning of it is obvious. So I have repeated all the steps several times. Of course I paid attention to enter user name and password correctly but I can't get rid of this message. For sure I making something wrong, but what it is ? 

Can you try the current SVN version?

http://savannah.psi.ch/websvn/filedetails.php?repname=elog&path=/trunk/src/elogd.c&rev=0&sc=0

There has been some issues with the password encoding, maybe this is fixed now. 

Is it possible to include an option in the next release to have the Options list reference a text file of attributes rather than explicity listing the attributes in the Config file directly?

This would make it much easier to maintain a particular list that is referenced in several log books.

I can put it on the wish list.

Just my two cent - I would have many very good applications for that feature:

• Keep option lists identical over different logbooks.
• Keep option lists identical over different applications.
• Create option lists from a database - that allows to use the options in many applications and in the database; e.g. a list of systems with a failure database, but failure reports in the regular ELOG.
• Export extendable option lists to other applications:
  • Inform administrator about options that have been newly added to a logbook for a review.
  • Provide option lists as menu buttons in these applications.
  • Prevent other applications to submit elog entries with illegal option choices.
• Import extendable option lists from other applications (at least after next elogd restart, if no "update option list" URL/command is provided for elogd).

We recently went through the process of renaming a "system list" in several logbooks, to make it consistent over several facilities. If the "on-call service" is called "radio frequency", but the "system" is called "RF", then searching the logbook can become difficult. It was painful: half a dozen applications had to be adapted at the same time the lists were updated, because they had features to create a failure report to ELOG - assuming specific "system" names.

So I'm in favour of putting that high up in the wishlist :-)

Dear All,

I could not submit a new enetry to my logbook whenever restarting my laptop.  I am a new user to elog.

Attached is the screenshot of the error message and also there is "nobody" while I grep elog.

----------------------

>>

Tapasis-MacBook-Pro-2:elog-3.1.0 tapasi$  ps aux | grep elog

tapasi            560   0.4  0.0  2432772    644 s002  S+    9:50AM   0:00.01 grep elog

nobody             76   0.0  0.4  2481308  18440   ??  Ss    9:48AM   0:00.08 /usr/local/sbin/elogd -c /usr/local/elog/elogd.cfg

--------------------------

Any suggesstion will be very much appreciated.

Thanks in advance,

Tapasi

You should check if the directory /usr/local/elog/logbooks/demo belongs to the right user and has the right write permissions.

Since the elogd process belongs to the user "nobody", the directory should best belong to "nobody" as well (or - not recommended - allows write access for "others")

Cheers, Andreas

Thanks for your reply.

I am the user and  it also has the write access 

cd /usr/local/elog/

ls -ltr

drwxrwxrwx  6 tapasi  admin  204 Jan  7 18:26 demo