Return to BSD News archive
Xref: sserve comp.sys.sun.admin:36491 comp.unix.bsd:14892 Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!MathWorks.Com!panix!berke From: berke@panix.com (Wayne Berke) Newsgroups: comp.sys.sun.admin,comp.unix.bsd Subject: Re: want syslog to pipe entry to command Date: 13 Sep 1994 20:52:29 GMT Organization: Nalgame Dios, Ltd. Lines: 35 Message-ID: <3553ed$1au@news.panix.com> References: <34nie0$c69@spruce.cic.net> <34nqrd$e6v@pulitzer.eng.sematech.org> <1994Sep10.112038.463@flapjack.ieunet.ie> NNTP-Posting-Host: berke.dialup.access.net X-Newsreader: NN version 6.5.0 #1 nick@flapjack.ieunet.ie (Nick Hilliard) writes: >Quentin Fennessy (fennessq@thecount.eng.sematech.org) wrote: >: In article <34nie0$c69@spruce.cic.net>, >: Paul Southworth <pauls@locust.cic.net> wrote: >: > >: >I want to have a script that will act on certain syslog messages as they >: >arrive (using the syslog entry as either stdin or an argument). >: > >: >What I wish for is a functional syslog.conf entry like this: >: > >: >foo.debug /var/log/syslog, |/usr/local/bin/snork >: > >: Paul - >: If you make the output file for syslogd to be a named pipe, >: you can have a program listening on the other end, ready to >: process your data. For example: >Alternatively, you can use 'tail -f /var/log/syslog | /usr/local/bin/snork'. >This avoids using a named pipe at the expense of using another process slot. This would have the side effect of piping _all_ syslog facilities that write to /var/log/syslog (eg. the user.alert messages). That may not be what the original user wants. >Nick >-- >Thought for the day: >One Page Principle: > A specification that will not fit on one page of 8.5x11 inch >paper cannot be understood. -- Wayne Berke berke@panix.com