From: Gerrit Pape <pape@smarden.org>
Subject: Re: limit svlogd log dir size
Date: Tue, 14 Feb 2006 10:25:04 +0000 [thread overview]
Message-ID: <20060214102504.3076.qmail@5b4f164cab24ab.315fe32.mid.smarden.org> (raw)
In-Reply-To: <20060214091543.GJ6585@home.power>
On Tue, Feb 14, 2006 at 11:15:43AM +0200, Alex Efros wrote:
> On Tue, Feb 14, 2006 at 08:49:08AM +0000, Gerrit Pape wrote:
> > > Is there exists way to limit size of svlogd's log directory, to guarantee
> > > it will not become too big and result in 'disk full' error?
> > Take a look at the 'N' config in the svlogd man page.
>
> I know about 'N'. This isn't a solution. Yeah, maybe when disk will become
> full svlogd will remove some log files. But what about all other software -
> like MySQL? I don't think it's good idea to allow svlogd to fill all hdd
> first and then fall into interesting endless loop: got 'disk full', remove
> a couple of log files, work for a couple of minutes/seconds, got next
> 'disk full' error...
Well, this normally really doesn't happen. You constructed a case where
you made svlogd crash by sending it SIGKILL. What should an application
do if it crashes? It cannot know why, and at what point ist crashed,
best is to do nothing, not removing any data from before the crash at
least.
What's sending SIGKILL to the svlogd process on your system so that you
run into this problem? You should fix that, svlogd behaves well on
SIGTERM, and shouldn't crash by itself.
Regards, Gerrit.
prev parent reply other threads:[~2006-02-14 10:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-13 18:16 Alex Efros
2006-02-14 8:49 ` Gerrit Pape
2006-02-14 9:15 ` Alex Efros
2006-02-14 10:25 ` Gerrit Pape [this message]
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=20060214102504.3076.qmail@5b4f164cab24ab.315fe32.mid.smarden.org \
--to=pape@smarden.org \
/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).