Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG  Not logged in ELOG logo
icon5.gif   deadc0de, posted by Niklas on Fri Aug 1 13:47:58 2008 
    icon2.gif   Re: deadc0de, posted by Stefan Ritt on Mon Aug 4 09:00:43 2008 
       icon2.gif   Re: deadc0de, posted by Niklas on Thu Nov 13 19:27:02 2008 
          icon2.gif   Re: deadc0de, posted by Niklas on Fri Nov 14 08:48:05 2008 
             icon2.gif   Re: deadc0de, posted by Eoin Butler on Thu Dec 18 10:32:09 2008 
                icon2.gif   Re: deadc0de, posted by Stefan Ritt on Thu Dec 18 10:39:57 2008 
                   icon2.gif   Re: deadc0de, posted by Eoin Butler on Thu Dec 18 11:16:37 2008 
                      icon2.gif   Re: deadc0de, posted by Stefan Ritt on Thu Dec 18 11:51:07 2008 
Message ID: 65941     Entry time: Fri Aug 1 13:47:58 2008     Reply to this: 65942
Icon: Question  Author: Niklas  Author Email: elog@niklas.hoglund.pp.se 
Category: Question  OS: Linux  ELOG Version: 2.7.3 
Subject: deadc0de 

Hi,

 

my ELOG sometimes dies with "deadc0de", do I have too large ELOG config or logbook? Or is it simply a bug?

What can I do to solve this problem? "ulimit"? Or some trace output from elog?

 

BR, Niklas

ELOG V3.1.5-3fb85fa6