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

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

> 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

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

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

Hi,
where can I find this correction for ELOG?
thanks a lot :o)

> > > > 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
> 
> Hi,
> where can I find this correction for ELOG?
> thanks a lot :o)

It's under CVS. You have to recompile the executable yourself, or you wait for the next
release (;-)

Hi Stephen,

I see that you don't allow branching in your threads.  Why do you need to propagate the Status throughtout the thread?  Why not just mark the latest entry and (incase it is necessary) 'collapse to last = 1'

I'm not saying that the bug (if bug it is, rather than a preset limitation) you've found should not be fixed, but I'm puzzled as to why you happen to use the feature.  I can see the point if an initial entry provides a whole tree of branches (and a limit of 10 is rather limiting).  OK, I know if it is historic, it cannot easily be changed because of other users.  Or if some users will primarily be responding to emails rather viewing the logbook via a browser.  I'm a single (ab)user elog system myself, so I'm very tolerant of changing how elog works if it offers an improvement.

 Thank you for the reply, the not allowing branching was added during the troubleshooting phase of the crashing.  Initially I thought the branches caused the issue because crashing only occured on log notes that branched as I only saw the crash on notes that branched, this proved not to be the case.  Even with branches the system will crash once there are 10 replies in the note with propagate on.

As for use case, with  a few users I needed a way to represent a note as open so that the next person knew work still needed to be done.  Once work was completed all notes close, the reason for not using edit is so I have a clear record of what happened (although I may need to change to edit if 10 is the max).  I will experiment with the collapse to last to see how it looks.  Any other suggestions would be helpful.