[systemd-devel] Journald stops logging when lots of output

[Colin Guthrie]

'Twas brillig, and Lennart Poettering at 26/09/13 19:35 did gyre and gimble:
> On Thu, 26.09.13 15:46, Olav Vitters (olav at vitters.nl) wrote:
> 
>>
>> On Wed, Sep 11, 2013 at 08:35:49PM +0200, Lennart Poettering wrote:
>>> (Of course, journald should not exit under any such circumstances, but
>>> to find that we first need to track down why it does that currently).
>>
>> Though it might hide problems, shouldn't journald be configured to
>> automatically be restarted by systemd?
> 
> We do that, but not indefinitely. See
> StartLimitInterval=/StartLimitBurst= in systemd.service(5).

Quick question, I presume logging is still lost for services stderr/out
etc. when journald is restarted? Or has this been worked-around these days?

Col

-- 

Colin Guthrie
gmane(at)colin.guthr.ie
http://colin.guthr.ie/

Day Job:
  Tribalogic Limited http://www.tribalogic.net/
Open Source:
  Mageia Contributor http://www.mageia.org/
  PulseAudio Hacker http://www.pulseaudio.org/
  Trac Hacker http://trac.edgewall.org/