First, I really appreciate this software. Thank you.

Next, I have question - am wanting to have a 'dashboard' of sorts that shows all entries that are 'open'. That part is easy enough. But, then I want to color the time (or some other field) if the ELOG has not been updated/created for more than X hours. This will help us keep track of events that need status updates.

Doable?

Thanks!

Unfortunately not. What I would do is to define a quick filter, so with one click all 'open' entries are shown. Then you can look at the date column and see how long they have been open (actually when they have been submitted, so the difference you must calculate in your head!). 

In the elogd.c file nearly at the very top is the following line:

char svn_revision[] = "$Id: elogd.c 2411 2011-04-01 14:39:35Z ritt $";

How does this information get into the source file?  Is it a script used when the svn changes are committed, or perhaps when they are checked out?  Any details or pointers to info on the web would be greatly appreciated.

Thanks.

This gets handled automatically by SVN. All you have to do is to put an "$Id$" in your text somewhere and enable the keyword ID. See for example

http://svnbook.red-bean.com/en/1.4/svn.advanced.props.special.keywords.html

Hello,

Is there still a limit of 50 attachments per topic?  If so, is there or could there be a parameter to change this setting?

Thanks,

Devin

The limit is defined in elogd.h:

#define MAX_ATTACHMENTS   50

I never thought that someone wants to have more than 50 attachments, since it will take forever to upload them. You can change the value on your own risk and recompile elogd. At some point you will run out of stack space, in which case elogd will crash, but you could increase the heap memory with a linker option. Just google for it.

Best,

Stefan

 Dear Stefan,

I am having a log book with the 5 logbooks. All other books are working fine except only one, every time while submitting the entry I am getting a error message.

I have attached the screen shot along with the error log file.

Please help me in solving this bug.

Regards

Harish Amin 

It's hard to guess from the information you sent what is wrong. The program just crashes, after the email notification has been sent successfully. Can you check if the one logbook which is not working is using some path for the logbook directory which it cannot write to due to access limitations? Just a guess.

-Stefan