[UPDATE] Re: Crafted URL causes elog to coredump, posted by Steve Jones on Mon Mar 6 18:54:32 2006
|
[quote="Steve Jones"][quote="Stefan Ritt"][quote="Steve Jones"]Try a non-existent logbook - example http://midas.psi.ch/elogs/elog/NewForum. This is occurring
under rev 1660. [/QUOTE]
|
|
[UPDATE2] Re: Crafted URL causes elog to coredump, posted by Steve Jones on Wed Mar 8 18:05:54 2006
|
[quote="Steve Jones"][quote="Steve Jones"][quote="Stefan Ritt"][quote="Steve Jones"]Try a non-existent logbook - example http://midas.psi.ch/elogs/elog/NewForum.
This is occurring under rev 1660. [/QUOTE]
|
|
[Segmentation Fault source identified] Verbose Output: Re: Crafted URL causes elog to coredump, posted by Steve Jones on Wed Mar 8 20:19:14 2006
|
[quote="Steve Jones"][quote="Steve Jones"][quote="Steve Jones"][quote="Stefan Ritt"][quote="Steve Jones"]Try a non-existent logbook - example http://midas.psi.ch/elogs/elog/NewForum.
This is occurring under rev 1660. [/QUOTE]
|
OPTION <attribute> not working right in [ global <name>] Top Group, posted by Steve Jones on Wed Mar 8 22:33:56 2006
|
I've verified that when the following is part of the definition of a [logbook] OR is part of a regular [global] config:
[code]
|
|
Removing 'New' from "List Menu commands" prevents saving elogd.cfg, posted by Steve Jones on Thu Mar 9 04:46:42 2006
|
Strange as it mmay seem, when I attempt to remove the "New" menu item from "List Menu commands" in a logbook section, I am no longer able to Save the config
file -- I am presented with a message saying "Error: Command "Save" not allowed". I have to manually edit the file, add that menu item back in, and then
all is ok. This is on the system where I am using 'Top Groups', so the logbook is a part of one of the top groups. |
Strange "bug?" report - disappearing data when attribute is "Locked", posted by Steve Jones on Thu Mar 9 06:04:46 2006
|
[quote="Steve Jones"]I have come across an issue where an attribute value is "blanked" upon either editing or replying. The interesting thing is this is
a logbook entry that was "Moved" from one logbook to another, all under the same Top Group. All configs are done under the [global <topgroup>] so the
attribute is not being reset on purpose. Most interesting of all is this only happens:
|
|
Re: Problem submitting entries in ELOG after migrating from Windows to Linux, posted by Steve Jones on Fri Mar 10 06:12:55 2006
|
[quote="Edmundo T Rodriguez"]I was able to install ELOG v2.61. in a Compaq ProLiant DL360 running with SUSE Linux v10
The migration/implementation went quiet well ...
|
elogd 2.6.1 program Crash is repeatable under Windows, posted by Steve Jones on Tue Mar 14 17:51:52 2006 
|
Stefan, I have previously reported that elog crashes with a specific URL -- I have now re-created the crash running under WindowsXP Pro using the pre-packaged
Windows installation that I just downloaded. I am attaching screenshots, etc. for your information but I think the source of the problem stems from using
"Top Group". I hope that you are able to look into this as I have logged other issues that i believe are specifically related to the use of the Top Group |