Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 380 of 808  Not logged in ELOG logo
ID Date Icondown Author Author Email Category OS ELOG Version Subject Text Attachments
  67713   Wed Nov 12 03:19:17 2014 Reply Konstantin Olchanskiolchansk@triumf.caBug reportLinux2.9.2-a738Re: Defunct daemonsAlso see this in ALPHA at CERN. Eventually
there are so many defunct elogd processes
that the user runs out of "maxproc" quota
  
  67714   Wed Nov 12 03:48:29 2014 Reply Konstantin Olchanskiolchansk@triumf.caBug reportLinux2.9.2-a738Re: Defunct daemons> Also see this in ALPHA at CERN.
> The elogd we use is this: https://bitbucket.org/ritt/elog/commits/44800a769b99599db7620779e2142b1161c694fc?at=master
  
  67717   Fri Nov 21 16:09:37 2014 Reply Stefan Rittstefan.ritt@psi.chInfoWindows2.8Re: 5.5.4 cannot decode AUTH parameter

    

       
            
  
  67718   Fri Nov 21 17:00:09 2014 Reply harish aminharish.amin@holiday.co.omInfoWindows2.8Re: 5.5.4 cannot decode AUTH parameter

    

       
            
  
  67719   Sat Nov 22 14:50:35 2014 Reply harish aminharish.amin@holiday.co.omInfoWindows2.8Re: 5.5.4 cannot decode AUTH parameter

    

       
            
  
  67720   Sat Nov 22 16:05:34 2014 Reply Yoshio Imai$user_emailInfoWindows2.8Re: 5.5.4 cannot decode AUTH parameter[quote=harish amin]Dear Stefen,
Please help me & reply on my request. Is
my global config correct?[/quote]
  
  67721   Mon Nov 24 13:10:13 2014 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.7.6Re: Elogbook on windows 8

    

       
            
  
  67722   Mon Nov 24 13:24:27 2014 Reply Stefan Rittstefan.ritt@psi.chBug reportLinux2.9.2-a738Re: Defunct daemons> Okey, found it. waitpid() in my_shell()
is not protected against the periodic alarm
signal. (UNIX signals are evil).
  
ELOG V3.1.5-3fb85fa6