Using 2.5.8, if I set "Protect Selection page" to 1, then elogd seg faults
as soon as it is accessed.
Under 2.5.7, a login page will come up, and the logbook will work, but only
if a valid username/password is given. If an invalid login is given, then
elogd crashes. We have a cron job that periodically restarts elogd if it is
has crashed.
Steve
[global]
logbook tabs = 0
port = 8080
Protect Selection page = 1
Password file = user.info
Admin user = saw
|