> > What other information can I provide that might assist in diagnosing this?
> 
> Please send me your elogd.cfg configuration file.

Stefan - I am having the exact same problem as outlined here. I sent you an
email with a somewhat complicated config file. Attached to this message is a
much simpler one. 

With this file, if you remove the B5 server (remove it from top group a2, and
remove the [b5] entry) the crash does not happen. If the B5 server (or any
additional server) is in the file, then the problem occurs.

For me, there are 3 places where the crash happens:
- on logout
- when an invalid username/password is used to login
- when you login to A1, then try to go to A2

This is happening on elog v2.5.9-1 (built May 2, 2005, 12:17:18 revision 1.642)

I have tried on windows 2000 and 2003 servers, and it seems to happen on both of
them.

Matt

> LOL ..this way I can't see the list of other threads .. so il my goal is to inspect the thread
> looking for something I have to:
> - open the 3d
> - return to 3d list
> - open another 3d ..
> [loop]
> 
> my wish would be to reduce it to
> - open the 3d
> - open another 3d ..
> [loop]

Well, I have the browser's back button on one of my mouse buttons, so "- return to 3d list" is one
mouse click. My policy is: If I can save someone two or more mouse clicks for am operation, I will
implement it. If it's less, it's not worth investing some hours of programming just to save 0.5s
each tim (;-).

Ok ok, I'll put it on the wish list. Just in case I'm running out of work. :-)

> Ok, fixed. I do however not evaluate the conditional attribute, but just remove any
> empty attribute, I guess that makes more sense.

ok, it work perfectly, tnx .. I agree with you choice of course :-)

> > ok, i've downgraded my request then ...
> > 
> > it will be still useful to have the possibility of expland selectively a single thread :-)
> 
> That you can do by clicking on the thread and look at the thread at the top of the page (;-))
> 
> That's exactly the same number of clicks as you would need to expand a thread (:-)))

LOL ..this way I can't see the list of other threads .. so il my goal is to inspect the thread
looking for something I have to:
- open the 3d
- return to 3d list
- open another 3d ..
[loop]

my wish would be to reduce it to
- open the 3d
- open another 3d ..
[loop]

of course I'm thinking to a big number of entries in a short number of 3ds .. making ugly to
simply expand everything .. :-)

Ok, fixed. I do however not evaluate the conditional attribute, but just remove any
empty attribute, I guess that makes more sense.

> ok, i've downgraded my request then ...
> 
> it will be still useful to have the possibility of expland selectively a single thread :-)

That you can do by clicking on the thread and look at the thread at the top of the page (;-))

That's exactly the same number of clicks as you would need to expand a thread (:-)))

> > A way may be using cookies, otherwise one can implement a kind o session mechanism
> > (using cookies or QS to pass sessid and storing user data on the server for a limited
> > time...)
> > the session method may be useful, but more difficult to implemnet, of course
> 
> The concept of a session ID is not present in elog, so implementing it would be harder
> than writing elog from scratch. Keeping the thousand 'expansion' flags in cookies is bad
> as well, because your browser will send them all each time you request a page, which can
> then slow down things considerably over slow lines.

ok, i've downgraded my request then ...

it will be still useful to have the possibility of expland selectively a single thread :-)

> A way may be using cookies, otherwise one can implement a kind o session mechanism
> (using cookies or QS to pass sessid and storing user data on the server for a limited
> time...)
> the session method may be useful, but more difficult to implemnet, of course

The concept of a session ID is not present in elog, so implementing it would be harder
than writing elog from scratch. Keeping the thousand 'expansion' flags in cookies is bad
as well, because your browser will send them all each time you request a page, which can
then slow down things considerably over slow lines.