Hi

Im currently experimenting with Elog to see if we can use it to track maintenance work. But Ive come up against a problem, When I export the data to a csv file,

the date has a comma inserted between the day of the week and the rest of the date. This means that all the fields are then shifted to the right after the date.

This looks like a bug to me, the test records included in the demo does not exhibit this problem, until a new record is added.

cheers Richard

  What about exporting record separated by a semicolong ";" ?

I fixed that in SVN revision #2040, the comma is simply replaced by a space in the date string.

Hi Stefan

Thanks for the quick reply.

We seem to be running 2012 - Which may explain the problem - I will see with our system administrator why we are not running 2040. By the way I also had this problem when running the windows version.

Cheers.. Richard

Hi Stefan

Our IT administrator has just downloaded and installed the latest source code from the site and installed it. We still now have version 2012?

Where do we get version 2041 ?

Cheers,  Richard

The bleeding edge version you get always from our SVN server, but you have to recompile it yourself. For your convenience, I just made you a version 2.7.2-3 containing the latest source code.

Thanks Stefan

Everything works now.

I installed elog 2.7.2 rev 2041 into /data/elog on Redhat ES 4 Update 4. This is my initial elogd.cfg file:

[global]
port = 80
Resource dir = /data/elog/elog
Logbook dir = /data/elog/elog/logbooks
Logfile = /data/elog/elog/logs/access_log
Logging level = 2
Resolve host names = 0
Usr = nobody
Grp = nobody

[demo]
Theme = default
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type

and start elogd - all is right with the world, everything is working properly. I shut down elog and try to add more logbooks using this template:
[A-B]
Subdir = cr_a-b
Comment = Change requests for Customers A-B
Menu commands = New, Reply, Download, Find, Last day
List Menu commands = New, Find
Display mode = summary

I create 14 of them, one for every 2 letters of the English alphabet and 0-9. The logbook name and Subdir change appropriately. When I start elog, it stays up for about 30 seconds, then crashes. No messages are recorded in syslog nor in the logfile. The only thing that looks suspicious are a couple lines in syslog:
Feb 15 17:11:05 iadopsutil04p elogd[23761]: elogd 2.7.2 built Feb 14 2008, 20:55:38 
Feb 15 17:11:05 iadopsutil04p elogd[23761]: revision 2041
Feb 15 17:11:05 iadopsutil04p elogd[23761]: FCKedit detected
Feb 15 17:11:05 iadopsutil04p elogd[23763]: Cannot restore original GID/UID.
Feb 15 17:11:05 iadopsutil04p elogd[23763]: Cannot remove pidfile "/var/run/elogd.pid" ; Permission denied
Feb 15 17:11:05 iadopsutil04p elogd[23761]: Server listening on port 80 ...

This is obviously the child process responsible for the highlighted lines and it's coming from the cleanup function. Why it's getting called is beyond me.
Ideas?