Date: Thu, 29 Nov 2012 13:46:41 -0600 From: Noel <noeldude@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: Unexepected results when piping syslog to a fifo Message-ID: <50B7BBA1.7090308@gmail.com> In-Reply-To: <80AACED86FEA012CB5D1F5F9@utd71538.campus.ad.utdallas.edu> References: <80AACED86FEA012CB5D1F5F9@utd71538.campus.ad.utdallas.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/29/2012 1:30 PM, Paul Schmehl wrote: > I'm working on a project which requires that I pipe a remote > syslog to a fifo so a daemon can parse the results. After some > googling I *thought* that I had figured out how to configure > syslog to do this. Here's the syslog.conf entry: > > + hostname.utdallas.edu > *.* | cat > /var/run/program/program.fifo > > This seems to work for one syslog message. The rest go to > /var/log/messages. > > So I tried this: > + hostname.utdallas.edu > *.* | tail -f > /var/run/program/program.fifo > > But that seems to do the same thing. > > I want these messages to be piped to the fifo *only* and not show > up in local logs. What's the secret sauce for this? > I've used this in the past ... !* +host.example.com *.* | /path/to/fifo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50B7BBA1.7090308>