From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/1032 Path: news.gmane.org!not-for-mail From: Gerrit Pape Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: limit svlogd log dir size Date: Tue, 14 Feb 2006 10:25:04 +0000 Message-ID: <20060214102504.3076.qmail@5b4f164cab24ab.315fe32.mid.smarden.org> References: <20060213181612.GD6585@home.power> <20060214084908.25375.qmail@a70d3f60c6741a.315fe32.mid.smarden.org> <20060214091543.GJ6585@home.power> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1139912688 20242 80.91.229.2 (14 Feb 2006 10:24:48 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 14 Feb 2006 10:24:48 +0000 (UTC) Original-X-From: supervision-return-1268-gcsg-supervision=m.gmane.org@list.skarnet.org Tue Feb 14 11:24:46 2006 Return-path: Envelope-to: gcsg-supervision@gmane.org Original-Received: from antah.skarnet.org ([212.85.147.14]) by ciao.gmane.org with smtp (Exim 4.43) id 1F8xMS-0005rc-Jd for gcsg-supervision@gmane.org; Tue, 14 Feb 2006 11:24:44 +0100 Original-Received: (qmail 14425 invoked by uid 76); 14 Feb 2006 10:25:06 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Archive: Original-Received: (qmail 14420 invoked from network); 14 Feb 2006 10:25:06 -0000 Original-To: supervision@list.skarnet.org Mail-Followup-To: supervision@list.skarnet.org Content-Disposition: inline In-Reply-To: <20060214091543.GJ6585@home.power> Xref: news.gmane.org gmane.comp.sysutils.supervision.general:1032 Archived-At: 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.