Re: Defunct daemons, posted by Konstantin Olchanski on Wed Nov 12 03:48:29 2014
|
> Also see this in ALPHA at CERN.
> The elogd we use is this: https://bitbucket.org/ritt/elog/commits/44800a769b99599db7620779e2142b1161c694fc?at=master
|
|
Re: Defunct daemons, posted by Stefan Ritt on Mon Nov 24 13:24:27 2014
|
> Okey, found it. waitpid() in my_shell() is not protected against the periodic alarm signal. (UNIX signals are evil).
Acknowledged. Thanks for the fix. I added it to the development branch.
|
v3.1.3 does not work with logbooks from v2.9.2?, posted by Yves on Thu Feb 1 03:12:03 2018 
|
I have just upgraded elog from 2.9.2 -> 3.1.3.
3.1.3 runs fine with new logbooks. However, when trying to run 3.1.3 with my logbooks created with 2.9.2 things stop working.
Here is the command I run for testing [attachment 1]: first of all it takes a very long time (~ 10 minutes) for it to index the logbooks. When |
|
Re: v3.1.3 does not work with logbooks from v2.9.2?, posted by Andreas Luedeke on Thu Feb 1 10:14:55 2018
|
Hi Yves,
just my two pence, maybe they help you to figure out what's going on:
versions 2.* had all entries of one
logbook in one directory. Version 3.* create a subdirectory for each year. This had been added for me: if you use AFS for logbook storage, then you have
a limit on how many files you can put into a single directory.
So the first time you start elogd 3.* with data from an elogd 2.* it should |
|
Re: v3.1.3 does not work with logbooks from v2.9.2? - solved, posted by Yves on Fri Feb 2 00:02:54 2018
|
Hi Andreas,
Thanks - you pointed me in the right direction. It appears that my logbooks were a combination of the two versions. I had all the year-directories
(version 3) but also all the entry files in the main logbook directory. Seems version 2 does not care but version 3 does not like it. After carefully checking |
|
Compilation failure on Mac OSX 10.9, posted by A.G. Schubert on Tue Nov 5 23:21:52 2013
|
When compiling elog on OSX 10.9 (Mavericks), I get the error below.
Elog will compile without error if I add -D_FORTIFY_SOURCE=0 to CFLAGS in Makefile, but I'm not sure whether this is a good idea.
|
|
Re: Compilation failure on Mac OSX 10.9, posted by Stefan Ritt on Wed Nov 6 09:04:32 2013
|
A.G. Schubert wrote:
When compiling elog on OSX 10.9 (Mavericks), I get the error below. |
|
Re: Compilation failure on Mac OSX 10.9, posted by A.G. Schubert on Thu Nov 7 02:18:17 2013
|
Stefan Ritt wrote:
|