From owner-freebsd-questions@FreeBSD.ORG Thu Nov 29 19:30:33 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 9754AF5C for ; Thu, 29 Nov 2012 19:30:33 +0000 (UTC) (envelope-from prvs=673b923ba=pauls@utdallas.edu) Received: from ip-002.utdallas.edu (ip-002.utdallas.edu [129.110.20.108]) by mx1.freebsd.org (Postfix) with ESMTP id 655258FC08 for ; Thu, 29 Nov 2012 19:30:33 +0000 (UTC) X-Group: None X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvEHAGi2t1CBbgogOmdsb2JhbABEhWQBujYDAQEBARkIS4JdAoFjGhOIEAydWpgwiQiQIGEDiF6OP5I5 X-IronPort-AV: E=Sophos;i="4.84,186,1355119200"; d="scan'208";a="104298243" Received: from zxtm01.utdallas.edu (HELO utd71538.utdallas.edu) ([129.110.10.32]) by ip-002.utdallas.edu with ESMTP/TLS/DHE-RSA-AES256-SHA; 29 Nov 2012 13:30:26 -0600 Date: Thu, 29 Nov 2012 13:30:25 -0600 From: Paul Schmehl To: FreeBSD Questions List Subject: Unexepected results when piping syslog to a fifo Message-ID: <80AACED86FEA012CB5D1F5F9@utd71538.campus.ad.utdallas.edu> X-Mailer: Mulberry/4.1.0a1 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline; size=780 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Nov 2012 19:30:33 -0000 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? -- Paul Schmehl (pauls@utdallas.edu) Senior Information Security Analyst The University of Texas at Dallas http://www.utdallas.edu/infosecurity/