Return to BSD News archive
Xref: sserve comp.sys.sun.admin:36369 comp.unix.bsd:14885 Newsgroups: comp.sys.sun.admin,comp.unix.bsd Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msuinfo!agate!howland.reston.ans.net!EU.net!ieunet!flapjack!nick From: nick@flapjack.ieunet.ie (Nick Hilliard) Subject: Re: want syslog to pipe entry to command Followup-To: comp.sys.sun.admin,comp.unix.bsd X-Newsreader: TIN [version 1.2 PL2] Organization: Integrated Flapjacks Message-ID: <1994Sep10.112038.463@flapjack.ieunet.ie> References: <34nie0$c69@spruce.cic.net> <34nqrd$e6v@pulitzer.eng.sematech.org> Date: Sat, 10 Sep 1994 11:20:38 GMT Lines: 26 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. 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.