> We have been using Elog successfully as a shiftlog book for over a month
> now, but I recently ran into an annoying bug, I think.
> We had a thread that was created and was being replied to over several
> days. We first replied to the original thread and then each subsequent
> reply was a reply of the previous reply. When the thread reached above 13
> of these, the elogd.exe would crash everytime a user attempted to select
> the logbook that contained the enormous thread.
> I found the only workaround was to manually delete the offending entry
> from the log file and to instruct my users to not reply to replies unless
> absolutely necessary. I have been able to replicate this error across the
> rest of my logbooks as well. If there is any more information you may
> need, please feel free to contact me.
Sorry my late reply, I was pretty busy these days...
I tried to reporduce your problem, but without success. Have a look at
http://midas.psi.ch/elogdemo/Linux/32
where I replied 20 times producing a very long thread without any problem. So
can you reproduce your problem? I suspect that there was some other problem,
since the number of replies is internally not limited in any way. If you
again get into a situation where elodg.exe crashes on the *DISPLAY* of some
message, you can send me the offending file xxxxxxa.log directly by email and
I can analyze it. Only if I can reproduce a problem, I can fix it.
- Stefan |