elogd -m Error sending local entry: Error transmitting message, posted by Dave on Thu Mar 10 00:26:03 2016
|
I'm running ELOG on a seperate Windows Servers.
When I try to synchronize the logbooks using "elogd -m", I get an "Error sending local entry: Error transmitting message"
If I click on the "Synchronize" link in the logbook, it can correctly send entry to remote ELOG. |
elogd -m , posted by Dave on Thu Mar 10 00:16:33 2016
|
I'm running ELOG on a seperate Windows Servers.
When I try to synchronize the logbooks using "elogd -m", I get an "Error sending local entry: Error transmitting message"
If I click on the "Synchronize" link in the logbook, it can correctly send entry to remote ELOG. |
Execute new|edit doesn't seem to work, posted by Juergen Diefenbach on Fri Feb 26 17:35:54 2016
|
I am trying to use the "Execute new|edit|delete" feature to track changes to an elog using git.
When a new entry is created a shell script should be executed (certain attributes of the logbook entry should be passed as arguments to it). The script |
Re: Execute new|edit doesn't seem to work, posted by Andreas Luedeke on Sun Feb 28 18:24:58 2016
|
[quote="Juergen Diefenbach"]I am trying to use the "Execute new|edit|delete" feature to track changes to an elog using git.
[...]
However, I experienced unreproducible behavior when creating "new" entries. Sometimes the command specified by "Execute new=" is called, sometimes the |
|
Re: Execute new|edit doesn't seem to work, posted by Juergen Diefenbach on Mon Mar 7 13:03:13 2016
|
[quote="Andreas Luedeke"]I'm just guessing, but you could try to disable the "save drafts" feature and see if the behaviour changes:
Save drafts = 0
|
|
Re: Execute new|edit doesn't seem to work, posted by Andreas Luedeke on Tue Mar 8 14:12:26 2016
|
[quote="Juergen Diefenbach"][quote="Andreas Luedeke"]I'm just guessing, but you could try to disable the "save drafts" feature and see if the behaviour
changes:
Save drafts = 0
|
|
Attribute Field Size Limited to 255 Characters, posted by Mike Bodine on Thu Mar 3 00:12:45 2016
|
I currently have an Attribute defined in my .cfg file as "Format <Attribute> = 0, attribname, attribvalue, 120, 500".
I've found if I exceed 255 characters elogd.exe fails. Is there a method that will allow me to exceed 255 characters? |
|
Re: Attribute Field Size Limited to 255 Characters, posted by Andreas Luedeke on Thu Mar 3 14:51:55 2016
|
No. At least there is no simple method.
You would need to edit the source code and recompile elogd. But the number 256 is used for about 300 times in the source code, you'll have
a hard time finding the right one to increase. |
|
Attribute Field Size Limited to 255 Characters, posted by Mike Bodine on Thu Mar 3 00:02:26 2016
|
I currently have an Attribute defined in my .cfg file as "Format <Attribute> = 0, attribname, attribvalue, 120, 500".
I've found if I exceed 255 characters elogd.exe fails. Is there a method that will allow me to exceed 255 characters? |
Links to images in notification message, posted by Devin Bougie on Fri Feb 26 17:20:52 2016 
|
We see two problems with the notificaiton email when attaching an image inline using drag-and-drop.
The thumbnail does not appear in its proper location inline. There is a ? placeholder where the thumbnail should be, and the
thumbnail then appears at the end of the message.
Neither the ? placeholder nor the thumbnail that do appear are clickable.
Our |
|
Re: Links to images in notification message, posted by Devin Bougie on Fri Feb 26 18:11:14 2016
|
From the notification I received, it looks like "2" is a problem with this server. In the email notification, we would like images to
be a link to a URL displaying the full-size image (as they are in v2.9.2).
Thanks, |
Possible bug in elogd execute_shell, posted by Nigel Warr on Fri Feb 26 08:47:22 2016
|
I was just playing around with gcc6's new feature for warning about misleading indentation (which can often hide real bugs) and I think it found
one in elog-3.1.1-1 at src/elogd.c:22538. Here there is an if statement, which looks as though it should be inside a loop, but it isn't.
The code is: |
|
Re: Possible bug in elogd execute_shell, posted by Stefan Ritt on Fri Feb 26 09:09:03 2016
|
Absolutely correct! Nice to see compilers getting better and better. I changed the code and committed it.
Nigel
Warr wrote:
I was just playing around with gcc6's new feature for warning about |
|
Possible bug in elogd execute_shell, posted by Nigel Warr on Fri Feb 26 08:38:06 2016
|
I was just playing around with gcc6's new feature for warning about misleading indentation (which can often hide real bugs) and I think it found
one in elog-3.1.1-1 at src/elogd.c:22538. Here there is an if statement, which looks as though it should be inside a loop, but it isn't.
The code is: |