supervision - discussion about system services, daemon supervision, init, runlevel management, and tools such as s6 and runit
 help / color / mirror / Atom feed
From: "Csillag Tamás" <cstamas@digitus.itk.ppke.hu>
Subject: Re: svlogd: blocking on ENOSPC
Date: Mon, 1 Nov 2004 23:00:29 +0100	[thread overview]
Message-ID: <20041101220029.GQ32116@digitus> (raw)
In-Reply-To: <20041018173902.24555.qmail@9227b11f156c29.315fe32.mid.smarden.org>

On 10/18, Gerrit Pape wrote:
> Hi, svlogd, just as multilog, sleeps and retries in case it's unable to
> write to the current logfile in a log directory and the system is ``out
> of disk space''.  This usually makes the service block because svlogd
> stops reading from the pipe.  Even though the space for logs can be
> calculated properly, if a log partition fills up by accident, it can
> bring the system in a troublesome state.
> 
> Here's a patch that makes svlogd remove the oldest of rotated log files
> in the log directory in case the disk is full.  In the worst case only
> the current logfile will be left.  I would be interested in your
> opinions.
Interesting, It would be nice as a command line switch like '-d'
(or maybe even better another line in config?)
So the admin can decide what is more important to keep the service
always up or to be sure the logs are preserved.

If you turn on debugging on one service (e.g. openldap) it is better to remove only
it's logs and not the others (e.g. auth logs).

What do you think?

-- 
cstamas


  reply	other threads:[~2004-11-01 22:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-18 17:39 Gerrit Pape
2004-11-01 22:00 ` Csillag Tamás [this message]
2004-11-02 15:04   ` Gerrit Pape
2004-11-02 21:15     ` Csillag Tamas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20041101220029.GQ32116@digitus \
    --to=cstamas@digitus.itk.ppke.hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).