Having the URL link to a different logbook is right now not possible. But 
what about setting up a single logbook with a write password. Everybody can 
access it for reading, but only these people who know the write password 
can enter messages.

> The exit status of elog is always 1.  It should be zero for
> a successful submission.

Has been fixed in 2.0.4

> If a message is submitted via the elog command then the reply string '> ' 
is only inserted in the first line if a reply is made.
> This message was submitted with the following commandline:
> elog -v -h midas.psi.ch -p 80 -s elogdemo -l Forum -a "Icon=icon4.gif" -
a "Author=Heiko Scheit"  -a "Author Email=h.scheit@mpi-hd.mpg.de" -
a "Subject=elog submit problem" "...Message-text..."
> Please press the reply button to see the problem.

Has been fixed in 2.0.4 (as you can see from this entry). Please make sure 
not to submit too long lines via "elog". For browser submissions, the line 
length is limited to 78 characters, but not for "elog" submissions.

> When the option 'Reverse sort = 1' is used then the first entry
> is not displayed (ID=1) when threaded mode is requested.
> 
> Probably you can see the problem using this link and switching 
> on reverse sort.  
> 
> http://midas.psi.ch/elogdemo/Linux/last20?mode=threaded

Has been fixed in 2.0.4, have a look at

http://midas.psi.ch/elogdemo/Linux/last20?mode=threaded&reverse=1

> Where can I get more information about the config and themes file. I
> downloaded the latest version (2.0.4) and the config file docs seem out of
> date. I would like to get the icons working as well as getting the email 
to
> work. The demo page at the elog home site shows both but I cannot find ant
> references to the icons.

Oops, I forgot the "IOptions" statement to documentation. Please see the 
updated version at

http://midas.psi.ch/elog/config.html

look for "IOptions". For the Email notification see the whole 
section "Email 
notification" near the bottom of the page.

> In version 2.0.4 of eLog I was having some problems with saving my 
> configuration file once I edited it on the web using the config. command.
> I keep getting the message "Cannot open file %s: elogd.cfg".  I made sure 
> the file was in the right directory.  I dont know if I am doing something 
> wrong or if its a bug?

The error display is certainly wrong. I fixed that and you can download the 
updated version at 

http://midas.psi.ch/cgi-bin/cvsweb/elog/elogd.c

As for the error, you should check the file permissions. If you run the 
daemon under a user which has no write access to the directory or file, you 
would get the described error.

> Comiling elogd 2.0.4 under Solaris obviously fails with
> 
> gcc  -o elog elog.c -lsocket -lnsl
> gcc  -o elogd elogd.c -lsocket -lnsl
> elogd.c: In function `ss_file_find':
> elogd.c:1372: `alphasort' undeclared (first use in this function)
> elogd.c:1372: (Each undeclared identifier is reported only once
> elogd.c:1372: for each function it appears in.)
> make: *** [elogd] Error 1
> 
> because alphasort is an ucb'ism which does not exist under SYSV
> 
> ... not very portable :-(

I was not aware of this. Actually, I don't need 'alphasort' so I removed it 
from the source. The update is at

http://midas.psi.ch/cgi-bin/cvsweb/elog/elogd.c

Please give it a try.

> With elog it is possible to submit messages to a password protected
> logbook without specifying the -u option.  I.e. NO PASSWORD is
> necessary to submit a message.  I assume it is related to the problem
> of expiring password-cookies while entering the message using a web
> browser.

Indeed this problem is related to the expiring password cookies. As a 
reminder: For the submission of a new entry, the password is checked when one 
presses the "New" button, but NOT for the "submit". This is because a 
password can expire between the "New" and the "Submit", so a entered message 
could not be sent. The question is now what to do with the standalone "elog".

Right now, elog does a normal submission where the password is not checked, 
which is maybe not what one wants. But what to do? If elog sends a special 
flag "please do check password on submit", someone could analyze the source 
code, remove the flag from elog and then still submit messages without a 
password. If I put an additional flag to the web browser submission "please 
do not check the password since the cookie might have been expired", someone 
can add this flag into elog and still bypass the password checking.

Anothe thing which bothers me is if you specify the password explicitly on 
the command line of elog, it's visible in some scripts etc, which yould be a 
security issue as well.

Any ideas?