Re: New Debian package (2.5.8+r1592) -- needs testing, posted by Recai Oktas on Wed Mar 23 16:44:32 2005
|
> It seems to work nice to me.
> Just another suggestion: I think it would be better to insert a commented out
> example for all allowed parameters in the distributed /etc/default/elog
Thanks for the test. Please note that, /etc/default/elog is partially auto
created during the installation. All options except PIDFILE and CONFFILE are
currently listed (as configured or commented out). If you didn't see these
options (after the update), there must be a problem. Did you mean the lack of
PIDFILE and CONFFILE in the default file? |
Crash with Protect Selection page = 1, posted by Stephen A. Wood on Thu Mar 24 10:31:01 2005
|
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
|
Re: Crash with Protect Selection page = 1, posted by Stefan Ritt on Thu Mar 24 10:39:00 2005
|
> Using 2.5.8, if I set "Protect Selection page" to 1, then elogd seg faults
> as soon as it is accessed.
Thanks for reporting this bug. I fixed it and committed the change to CVS.
- Stefan |
|
Re: Crash with Protect Selection page = 1, posted by Emiliano Gabrielli on Thu Mar 24 11:00:59 2005
|
> > Using 2.5.8, if I set "Protect Selection page" to 1, then elogd seg faults
> > as soon as it is accessed.
>
> Thanks for reporting this bug. I fixed it and committed the change to CVS.
>
> - Stefan
wow, who's Speedy Gonzales ?!? :-P |
|
Re: Crash with Protect Selection page = 1, posted by Emiliano Gabrielli on Thu Mar 24 11:01:06 2005
|
> > Using 2.5.8, if I set "Protect Selection page" to 1, then elogd seg faults
> > as soon as it is accessed.
>
> Thanks for reporting this bug. I fixed it and committed the change to CVS.
>
> - Stefan
wow, who's Speedy Gonzales ?!? :-P |
|
Re: Crash with Protect Selection page = 1, posted by Stephen A. Wood on Thu Mar 24 11:28:13 2005
|
> > Using 2.5.8, if I set "Protect Selection page" to 1, then elogd seg faults
> > as soon as it is accessed.
>
> Thanks for reporting this bug. I fixed it and committed the change to CVS.
>
> - Stefan
That was fast! I put the elogd.c from the cvs on top of 2.5.8 and now I can run
the server with Protect Selection page=1 again.
Logins work OK if the username/password is valid. However, if I try to login
with invalid authentication, the server crashes. If I turn off the protect
selection page, then invalid authentication does not crash elogd.
Thanks, Steve |
|
Re: Crash with Protect Selection page = 1, posted by Stefan Ritt on Thu Mar 24 11:47:58 2005
|
> Logins work OK if the username/password is valid. However, if I try to login
> with invalid authentication, the server crashes. If I turn off the protect
> selection page, then invalid authentication does not crash elogd.
Ok, it's me, Speedy Gonzales again (as Emiliano says... (;-))
I fixed that as well and committed the changes.
Greetings to JLab (I once worked at UVa in Charlottesville...). Is David Abbott
still there?
- Stefan |
|
Re: Crash with Protect Selection page = 1, posted by Stephen A. Wood on Thu Mar 24 12:09:55 2005
|
> > Logins work OK if the username/password is valid. However, if I try to login
> > with invalid authentication, the server crashes. If I turn off the protect
> > selection page, then invalid authentication does not crash elogd.
>
> Ok, it's me, Speedy Gonzales again (as Emiliano says... (;-))
>
> I fixed that as well and committed the changes.
That seems to do the trick! Thanks, Steve |