> > an entry like
> > file:///E:/Dossier\!!shorcut
> > will open IE with these current adresse
> 
> Yes it does, and what is your question?
> 
> > Stef could you add a logbook  
> > 'wishlist'
> > 'subgroup' contribution/icons
> 
> If you have any icons, just put it under the contributions logbook. There 
> are only few entries, so no deed to make a subgroup.
> 
> As for wishlist, start with the "Forum" Logbook. If a wish gets "accepted", 
> I put it on the official web page.

sorry for my 'stupid' question please delete this entry :)

Hi,

The default email subject line for a new entry is: "New ELOG entry", and the default email subject line for an edited entry is: "Updated ELOG entry". However when we set "Use Email Subject", both new entries and the updated entries use the same email subject. Is there an equivalent of "Use Email Heading Edit" for the subject line? I tried "Use Email Subject Edit", to no avail.

Thanks in advance,

e.

Since there were no responses, I decided to make good use of the fact that the software is thankfully open-sourced. I modified elogd.c and added just a couple of lines to get what I wanted.

22245,22250d22244
<    if (old_mail && getcfg(lbs->name, "Use Email Subject Edit", subject, sizeof(subject))) {
<       i = build_subst_list(lbs, slist, svalue, attrib, TRUE);
<       sprintf(str, "%d", message_id);
<       add_subst_list(slist, svalue, "message id", str, &i);
<       strsubst_list(subject, sizeof(subject), slist, svalue, i);
<    } else

These lines just follow the comment line: /* compose subject from attributes */

Hi,

I am having trouble with uploading large (>0.5MB) files to elog. We click on upload and in a couple of seconds, the webbrowser complains that the server has dropped the connection.

Following the suggestions I found on these forums (https://midas.psi.ch/elogs/Forum/66753), I increased the timeout.tv_sec to 30 in three locations in elogd.c, but this did not help.

The problem is present in my old elog installation (from ~2 years ago), as well as the latest git snapshot from bitbucket that I cloned on June 10, 2017.

PS: Upload seems to work for non-secure configuration. It still takes a while to load, but it completes. However we prefer to use secure connections ( SSL = 1 ).
PS: Using nmap I looked at the latency to the relevant port, it can be as high as 0.5sec, but most often it is shorter.

Cheers,
e.

Hi,

Could someone at least suggest how I could debug this problem myself? If I know where to start, perhaps I can fix it myself and contribute to the software.

Best,

e.

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.