> Thank you.  I had added the "Move To" and this works at the log entry
level (i.e., "Move
> To <name>) but in the threaded view one does not get the enumerated list
of logbooks.

You get the "Move To" button only after pressing "Select", otherwise it does
not make sense. See attached screendump and config example.

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

> > The help text on the website says the following:
> > 
> > "The command Select can be used to select multiple messages for deletion of
> > moving to other logbooks."
> > 
> > This is not clear but was the intent to indicate that SELECT can be used to
> > either select multiple log entries for deletion OR for moving to another
> > logbook?  If the latter, then this does not work if one adds the MOVE TO
> > menu item to the list.  If the former then the helptext is a little misleading.
> 
> SELECT can be used for deletion OR moving OR copying. To enable the copy and move
> commands, they have to be present in the "Menu commands" list, like
> 
> Menu commands = Back, New, Edit, Delete, Reply, Find, Config, Logout, Move to, Copy
> to, Help
> 
> I added an appropriate note to the documentation, sorry for the misleading descriptoin.

Thank you.  I had added the "Move To" and this works at the log entry level (i.e., "Move
To <name>) but in the threaded view one does not get the enumerated list of logbooks.

I'll play around with it a little more before re-posting.  When it didn't work as I
expected I read the docs and ran across the confusing text - so I stopped and asked!

Thanks again.

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

> The help text on the website says the following:
> 
> "The command Select can be used to select multiple messages for deletion of
> moving to other logbooks."
> 
> This is not clear but was the intent to indicate that SELECT can be used to
> either select multiple log entries for deletion OR for moving to another
> logbook?  If the latter, then this does not work if one adds the MOVE TO
> menu item to the list.  If the former then the helptext is a little misleading.

SELECT can be used for deletion OR moving OR copying. To enable the copy and move
commands, they have to be present in the "Menu commands" list, like

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

I added an appropriate note to the documentation, sorry for the misleading descriptoin.

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.

Thanks

The help text on the website says the following:

"The command Select can be used to select multiple messages for deletion of
moving to other logbooks."

This is not clear but was the intent to indicate that SELECT can be used to
either select multiple log entries for deletion OR for moving to another
logbook?  If the latter, then this does not work if one adds the MOVE TO
menu item to the list.  If the former then the helptext is a little misleading.

Thanks!

> First - Some of the logbook entries should not be viewed by certain users.  
> What would be the easiest way to restrict viewing some entries?  

The easiest way is to define two logbooks, with two different password files.
The more restricted logbook contains only those users who are allowed to see the
restricted entries. Use the commands "Move to" to move entries between the two
logbooks (see documentation).

> Second - I have a welcome page for the ELOG that lists some info about the 
> ELOG.  When I start the ELOG, the user sees the login page.  After the user 
> logs in, the welcome page appears listing the restrictions.  Right now, I 
> have a hyperlink that takes the user to new, find, etc.  But I would like 
> to take the user right to the logbook and not have to come back to the 
> welcome page everytime.  How can I do this?

Right now you need an exteral page on a public webserver. This page contains
then links to your elog server. I the next version I will implement the
possibility to server *.html files directly through elog. You can then put your
welcome page under themes/default/Welcome.html, and access it through the
starting link:

http://your.elog.server/logbook/Welcome.html

You will only see the Welcome page once, since all links in elog will point back
to .../logbook/ and not to .../logbook/Welcome.html. The config option "Welcome
page = Welcome.html" you have to remove then of course.