Re: Elog ID entry bug at >99999 entries, posted by Andreas Luedeke on Sat May 5 20:55:23 2018
|
Well, in my example the ID link worked just fine.
There could be a string length limitation, but it could be as well the way you are creating the ID that is the source of the problem: I would
need the part of your elogd.cfg that defines how you format your ID in order to try to reproduce your problem. |
|
Re: Elog ID entry bug at >99999 entries, posted by Stefan Ritt on Mon May 7 14:24:18 2018
|
As Andreas said we have to reproduce the problem. What is special in your case is the elog:SequencerEvents/XXXXX.
This is non-standard and must be created through your configuration of elog or by an external script. I just guess that you have something like
Preset ID = elog:SequencerEvents/##### |
|
Re: Elog ID entry bug at >99999 entries, posted by Chris Rasmussen on Mon May 7 18:10:20 2018
|
ah yes, that was a helpful clue. Our elogd.cfg file led me to a .js file which redefines the ID to the elog:SequencerEvents/XXXXX
format and it indeed had a silly hard coded length of that string.
Since I am pretty sure this is our code, I think it is safe to say that this is not a bug in the elog |
Re: Elog ID entry bug at >99999 entries, posted by Joseph McKenna on Tue May 8 16:17:28 2018
|
Thank you all for your kind responses. Please consider this thread resolved: no bug in elog
Chris
Rasmussen wrote:
ah yes, that was a helpful clue. Our elogd.cfg file led me to a |
elogd service crashes after windows update, posted by Tom Roberts on Fri May 18 00:57:33 2018
|
We have been using elog on Windows 10 for a long time. Today, after a Windows update, the elogd service started crashing (error 1067, unexpected termination).
It ran fine just before the Windows update (which took > 1 hour, so it was a major one). Uninstalling and re-installing did not help, including replacing
my elogd.cfg with the default. Installing on another PC (that also has this update) fails in the same way. I have a good backup of my logbook. |
|
Compile issues on Fedora withe current elog source, posted by Allen Tuttle on Tue Sep 11 19:46:40 2018
|
Tried compiling on FC27 and 28, both result in binaries but with serious issues; writing data larger than then allowed.
Example output:
make
gcc -O3 -funroll-loops -fomit-frame-pointer -W -Wall -Wno-deprecated-declarations |
|
Re: Compile issues on Fedora withe current elog source, posted by Stefan Ritt on Wed Sep 12 11:10:18 2018
|
This warning is triggered by the use of the sprintf() funciton, which can write beyond the boundary of the destination string. I replaced it by snprintf(),
which should make the compiler happy. Code is committed. Unfortuantely I have no FC27 here, so if there is still some waring with the current code, please
post the full warning list here. |
|
Re: Compile issues on Fedora withe current elog source, posted by Allen Tuttle on Wed Sep 12 15:20:11 2018
|
I don't see the update on elog/download/tar/.
Do you keep builds elsewhere, perhaps on get or sourceforge?
Stefan |