Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon4.gif   Defunct daemons, posted by David Pilgram on Sat Mar 29 12:14:11 2014 
    icon2.gif   Re: Defunct daemons, posted by David Pilgram on Sat Mar 29 13:14:44 2014 
       icon2.gif   Re: Defunct daemons, posted by Konstantin Olchanski on Wed Nov 12 03:19:17 2014 
          icon2.gif   Re: Defunct daemons, posted by Konstantin Olchanski on Wed Nov 12 03:48:29 2014 
             icon2.gif   Re: Defunct daemons, posted by Stefan Ritt on Mon Nov 24 13:24:27 2014 
Message ID: 67713     Entry time: Wed Nov 12 03:19:17 2014     In reply to: 67684     Reply to this: 67714
Icon: Reply  Author: Konstantin Olchanski  Author Email: olchansk@triumf.ca 
Category: Bug report  OS: Linux  ELOG Version: 2.9.2-a738 
Subject: Re: Defunct daemons 
Also see this in ALPHA at CERN. Eventually there are so many defunct elogd processes that the user runs out of "maxproc" quota and automatic submission 
of elog messages starts to fail. (and the users complain, reboot all computers, etc).

The elogd we use is this:
https://bitbucket.org/ritt/elog/commits/44800a769b99599db7620779e2142b1161c694fc?at=master

The best I can tell, the main elogd is spawning something but does not reap finished subprocesses (wait() syscall). My guess it is spawning ImageMagik stuff 
to create preview images.

K.O.
ELOG V3.1.5-fe60aaf