I have a question about ELOG. Let's say after the user finishes his shift 
and passess on to the next user on duty. A staff member would want to look 
through the entries and vet them. The staff could lock the entries to 
maintain integrity of the information. How can that be done with ELOG? Can 
you enlighten me. Thank u.

> Hello friends, 
> 
> Exist some form to increase limits of items (100) in the Options List
> 
> 
> 
> Thanks for any help

I believe only through an edit of the C code and a recompile, as the values
are set as constants.  I think this might be the line:

#define MAX_N_LIST      100

So, yes, there exists a way and the ease of this way is dependent upon your
comfort level with changing stefan's code.

At some point, in the last week or so, I upgraded the debian-unstable
version (r1459-1) of elog.  Now, PostScript files (as attachments) are
displayed (shown in ascii text, instead of just showing the link).  

Is there an option in the elog.cfg to only display certain files (like .gif
or .jpg).

> > Hello friends, 
> > 
> > Exist some form to increase limits of items (100) in the Options List
> > 
> > 
> > 
> > Thanks for any help
> 
> I believe only through an edit of the C code and a recompile, as the values
> are set as constants.  I think this might be the line:
> 
> #define MAX_N_LIST      100
> 
> So, yes, there exists a way and the ease of this way is dependent upon your
> comfort level with changing stefan's code.

Agree. The only potential problem is that if this value becomes too big, you
will get a stack overflow from time to time. So best is experiment yourself a
bit. A avlue of 150 or so should be no problem.

- Stefan

> Hmmm.  I like the little buttons with the pull-downs for selections. 
> Unfortunately, I don't get that.  With a config of:
> 
> Find Menu commands = New, Find, Select, Config, Change password, Logout, Help, Admin
> Menu commands = Back, New, Edit, Delete, Reply, Find, Move To, Copy To, Config, Help

Unfortunately menu commands are case sensitive, so you need a "Move to" instead a "Move
To". I changed this in the code so future versions will not be case sensitive any more.

> BTW, on a log entry screen, is the appropriate behavior for the "Move To" option
> to show multiple "Move To" links (one for each logbook) or should there also be
> pulldowns?  

On the log entry screen, only menu links are possible for internal reasons, that's why I
have chosen that display mode. I agree that it can look clumsy if you have many
logbooks, but there is the "move to = <logbook list>" option to restrict the number of
target logbooks.

> Newly installed elog gives this response when I try to submit a new record:
> 
> New entry cannot be written to directory "./logbooks/Linux/" 
> Please check that it exists and elogd has write access
> 
> I started the daemon.  I've not yet assigned passwords -- just checking
> things out.  How can I create this access to my own directory?

First, find out under which account the daemon is running. It you account if
you start it interactively, if you installed from the RPM, an account "elog" is
created. Then make sure that the account under which elogd is running has write
access to the ./logbooks/Linux/ directory. One common problem is that people
start the daemon the first time under their account, which causes elogd to
create the logbook directory under the user name. If elogd is later started
under the account "elog" this one of course does not have access to the
directory. A

chown -R elog.elog /usr/local/elog/

issued as root could help in that case. Please replace /usr/local/elog with the
directory where elog is installed.

That bug has been fixed recently, please update to the newest version.

One possibility is to use the option "Restrict edit time = <hours>". This way
an entry can only be edited let's say 8 hours after it has been created.

Another way is to maintain two logbooks, a "scratch" logbook and an "archive"
logbook. Users would put their entries into the scratch logbook, the staff
would examine it and move them to the archive logbook, where all users only
have read access to. To move entries between logbooks, you have to put the
"Move to" command in the configuration file like:

Menu commands = Back, New, Edit, Delete, Reply, Find, Move to, Config, Help