> 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.

> I'm not sure if this is a configuration problem or a bug, but running
> v2.5.4subver1.413, elogd runs as user ROOT (UID0) even though the following
> is in the elogd.cfd file:
> 
> Usr = nobody
> Grp = essadm
> 
> All other directives added to the cfg file work, so I know eLog is reading
> the cfg file.  
> 
> The elogd binary *is not* setuid 0.

I could not reproduce your problem with the current version (Revision 1.460)
under Linux. I guess you made sure that user "nobody" and group "essadm" exist.
Try to run elogd interactively, if you see any error message (without "-D"
flag). In the most recent version (1.460), I added some more debugging code
which tells you if elogd successfully fell back to another user, if you use the
"-v" (verbose) flag.

If all that does not help, I guess it's some peculiarity of Solaris. Maybe
someone else using Solaris has some idea. All elogd does is a call to 

setuser("<user>");

I see no reason why this should not work on Solaris.

> > I'm not sure if this is a configuration problem or a bug, but running
> > v2.5.4subver1.413, elogd runs as user ROOT (UID0) even though the following
> > is in the elogd.cfd file:
> > 
> > Usr = nobody
> > Grp = essadm
> > 
> > All other directives added to the cfg file work, so I know eLog is reading
> > the cfg file.  
> > 
> > The elogd binary *is not* setuid 0.
> 
> I could not reproduce your problem with the current version (Revision 1.460)
> under Linux. I guess you made sure that user "nobody" and group "essadm" exist.
> Try to run elogd interactively, if you see any error message (without "-D"
> flag). In the most recent version (1.460), I added some more debugging code
> which tells you if elogd successfully fell back to another user, if you use the
> "-v" (verbose) flag.
> 
> If all that does not help, I guess it's some peculiarity of Solaris. Maybe
> someone else using Solaris has some idea. All elogd does is a call to 
> 
> setuser("<user>");
> 
> I see no reason why this should not work on Solaris.

Ok, just checking.  I will fiddle around with running it interactively and see what
I get, plus I'll have a look at the setuser function under Solaris.

Just for grins, what version of compiler are you using under Linux?

Thanks again!

> Just for grins, what version of compiler are you using under Linux?

gcc 3.2.2 (from RedHat Linux 9.0)

> > Just for grins, what version of compiler are you using under Linux?
> 
> gcc 3.2.2 (from RedHat Linux 9.0)

Well, I am running 2.95.3 - hmmm.  We have 3.3.2 - perhaps I'll try that and
see if there is a difference.

> I'm trying to run elog 2.6.0-beta4 under Apache 2.0.  I follow the directions, and everything works fine, so my
> elog runs as
> 
> http://grattalab3.stanford.edu/elog/
> 
> running under port 8082, with the following lines in my httpd.conf file
> 
>  Redirect permanent /elog http://grattalab3.stanford.edu/elog
>  ProxyPass /elog/ http://grattalab3.stanford.edu:8082/
> 
> This machine has an alias, which is http://exo-elog.stanford.edu.  My question is, how can I run elog so that
> when someone types in this name, it brings up my elog? I know that I can make a VirtualHost entry and put a
> redirect at the document root of that virtual host, but that seems clumsy.  Can I just modify ProxyPass or add a
> Redirect statement somehow?

To my knowledge you need a VirtualHost entry, plus a "URL = http://exo-elog.stanford.edu" entry in elogd.cfg

 I have a similar problem when I restart the elogd daemon. To fix that, I usually also restart Apache.