From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.comp.sysutils.supervision.general/1163 Path: news.gmane.org!not-for-mail From: Alex Efros Newsgroups: gmane.comp.sysutils.supervision.general Subject: Re: monitoring svlogd-produced logfiles Date: Thu, 15 Jun 2006 02:59:09 +0300 Organization: asdfGroup Inc., http://powerman.asdfGroup.com/ Message-ID: <20060614235909.GA20474@home.power> References: <20060614233508.GP898@annvix.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1150329555 1554 80.91.229.2 (14 Jun 2006 23:59:15 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 14 Jun 2006 23:59:15 +0000 (UTC) Original-X-From: supervision-return-1399-gcsg-supervision=m.gmane.org@list.skarnet.org Thu Jun 15 01:59:14 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 1FqfGP-0001dl-Vp for gcsg-supervision@gmane.org; Thu, 15 Jun 2006 01:59:10 +0200 Original-Received: (qmail 30430 invoked by uid 76); 14 Jun 2006 23:59:31 -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 30424 invoked from network); 14 Jun 2006 23:59:31 -0000 Original-To: supervision@list.skarnet.org Mail-Followup-To: supervision@list.skarnet.org Content-Disposition: inline In-Reply-To: <20060614233508.GP898@annvix.org> User-Agent: Mutt/1.5.11 Xref: news.gmane.org gmane.comp.sysutils.supervision.general:1163 Archived-At: Hi! There a lot of ways to do what you need and I think you overcomplicate. If you don't need svlogd writing to disc and wish to redirect it output to some 'summarize' program, then why not use that program instead of svlogd in ./log/run? Main svlogd task is reliable _writing_to_disc_! But you can configure svlogd to duplicate your logs (optionally filtered) to STDERR (in addition to writing to disc). In degenerate case you even can configure svlogd to write nothing to disc and send all log lines to STDERR, but I don't understand why you need svlogd in this case. :) Then, in ./log/run you redirect svlogd's STDERR to some FIFO file: svlogd /var/log/something 2>/var/log/MYFIFO (you can configure a lot of different svlogd to output into single FIFO) and setup special service which will fetch data from /var/log/MYFIFO, summarize it, print colored to /dev/tty12 or everything - ./run example: exec my_cool_summarizer <>/var/log/MYFIFO Only one important note about FIFOs - if your 'my_cool_summarizer' service will be down and will not read from /var/log/MYFIFO all other svlogd which write into FIFO will also stop soon (after they fill kernel buffers) and in turn will stop services which they logging. -- WBR, Alex.