Would it be possible to instead of appearing a "clip" and/or "multiple-clips" (as the number of attachments grow) to appear a number which will be = to the count of attachments to avoid the column become too wide?

Hope it works because this is tool better every day.

Keep up the GOOD Work!

> ------
> 
> I plan on letting elogd create a core dump, but so far I haven't managed to change its cwd to a directory 
elog can write to.
> 
> Please let me know if there is any other information I can provide.  Any suggestions would be greatly 
appreciated.
> 
> Many thanks,
> Devin 

There are other debugers ...

  Whay don't you give them a try?

  example: Install "strace" (if you don't have it) and do something like ...

           strace   gdb /usr/local/sbin/elogd 6162  -debug 2>debug.out


   Also there is "ltrace", etc.

Hi, I've been using the ELOG software for about a year now. I love it! But as my ELOG becomes more valuable, I become more paranoid about potential data loss. (We've had numerous close-calls with disk failures, recently.) Is there a way to download a backup of my ELOG, all at once? Maybe a command that could create a tar.gz of all the entries and attachments? Further, is there also a command to restore from such a backup? Apologies if this question is answered elsewhere. I couldn't readily find it in the documentation. Regards, --Ed

After we upgarde to eLog 3.1.4 ... The HTML editor tools are grayed out and you can't paste any images in the body of the log like I did below.. Any help will be much appreciated..

Thank yoy for responding back to me ... I run the excutable that I downloaded from the website .. How can I do the full directory tree with the ELOG JavaScript files??

We just tested eLog and it works in Chrome but not in IE .. Is it a setting issue that we need to chnage on IE ?!

I found a way to get this to work.  Define a "Messages" logbook for the messages to be broadcast.  None of the user installations need access to it. Use "Execute new = " to execute a script calling the elog command line client passing the message on to each target logbook.  Example:

--- elogd.cfg snippet begin ---

[Messages]

...

Execute new = mass_post.sh $text &

--- elogd.cfg snippet end ---

--- mass_post.sh begin ---

#!/bin/sh

elog -a Sender="System Administrator" -l "Logbook 1" $@

elog -a Sender="System Administrator" -l "Logbook 2" $@

elog -a Sender="System Administrator" -l "Logbook 3" $@

--- mass_post.sh end ---

The $@ expands to all the command line arguments, so the $text field, with all its spaces, gets passed correctly.  Sorry I showed you the example in bash/linux rather than in Windows, but I don't know Windows real well - you're better off translating into it yourself than my untested attempts.  The one thing I can tell you is that the "Execute new" command must include the "background fork".  In Linux this is provided by the & at the end of the line. In windows you'll need to use

Execute new = start "dummy" /min mass_post.bat

to background the process.  This is ESSENTIAL.  Without backgrounding the batch file, the elogd server will go into an infinite loop.  The parent process will wait for the child process to exit before continuing.  elogd is single-threaded, so the child process cannot start until the parent process has completed its current task (which is waiting for the child process to exit). 

You may need to tweak the above a little if you want to pass variable attributes to the script instead of defining them all in the script itself.