From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/573 Path: main.gmane.org!not-for-mail From: Enrico Scholz Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: [runit/svlogd] RFE: periodic log-rotation; filter-malfunction Date: Thu, 02 Sep 2004 23:58:21 +0200 Message-ID: <87llfse3k2.fsf@kosh.ultra.csn.tu-chemnitz.de> References: <87sma1dmfu.fsf@kosh.ultra.csn.tu-chemnitz.de> <20040902194813.8878.qmail@892d5ec05c70b4.315fe32.mid.smarden.org> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1094162313 24334 80.91.224.253 (2 Sep 2004 21:58:33 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 2 Sep 2004 21:58:33 +0000 (UTC) Original-X-From: supervision-return-811-gcsg-supervision=m.gmane.org@list.skarnet.org Thu Sep 02 23:58:26 2004 Return-path: Original-Received: from antah.skarnet.org ([212.85.147.14]) by deer.gmane.org with smtp (Exim 3.35 #1 (Debian)) id 1C2zb8-0000j5-00 for ; Thu, 02 Sep 2004 23:58:26 +0200 Original-Received: (qmail 21256 invoked by uid 76); 2 Sep 2004 21:58:46 -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 21250 invoked from network); 2 Sep 2004 21:58:46 -0000 Original-To: supervision@list.skarnet.org In-Reply-To: <20040902194813.8878.qmail@892d5ec05c70b4.315fe32.mid.smarden.org> (Gerrit Pape's message of "Thu, 2 Sep 2004 19:48:11 +0000") User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through Obscurity, linux) X-Scanned-By: MIMEDefang 2.43 X-Scan-Signature: e12d97d61532ad8cf10729288984e4c0 Xref: main.gmane.org gmane.comp.sysutils.supervision.general:573 X-Report-Spam: http://spam.gmane.org/gmane.comp.sysutils.supervision.general:573 pape@smarden.org (Gerrit Pape) writes: >> Would it be possible to add another option (e.g. 'a') which >> sends SIGALRM at seconds after the last logrotation? > > I'll have to think about it, in the meantime you could setup a separate > service doing this work, e.g.: > > /var/service/socklogrotate/run: > #!/bin/sh > runsvctrl alarm /var/service/socklog > exec sleep I do not like this, because: * it adds extra bloat to the system (it is bad enough that I have to spawn a stunnel-instance per logrotation; an additional sleep+bash-process would increase system-load significantly). Without looking at the code, I guess that an implementation in svlogd would be much smaller because the SIGALRM handler is already there. (Things are getting worse because I run 20-30 svlogd instances per machine in linux-vservers[1] (chroots, BSD-jail like)) * it requires additional software (svlogd is used without the other runit tools here) and setup. * it would logrotate every buffer inclusive those which should not be touched (e.g. I have a local debug-buffer which I want to keep). 'a...' could send a new signal (USR2??) which logrotates only the outdated buffers (I know that it conflicts with my initial idea...). >> Another issue: the '-/+...' filters seem to fail sometimes. > ... > This shouldn't happen. Can you please give an exact example of a line > that ends up in the wrong log, copied and pasted, and also re-check that > you post the exact contents of the config files? Do you use the -r or > -R command line options to svlogd in socklog-ucspi-tcp/log/run? Please see http://www.tu-chemnitz.de/~ensc/runit/badfilter.txt When you need de-anonymoused values, please contact me privatly. Enrico Footnotes: [1] http://linux-vserver.org