From owner-freebsd-hackers Thu Apr 1 1:38: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 2DF1C14C11 for ; Thu, 1 Apr 1999 01:37:59 -0800 (PST) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id DAA14972; Thu, 1 Apr 1999 03:37:24 -0600 (CST) Date: Thu, 1 Apr 1999 03:37:24 -0600 From: "Matthew D. Fuller" To: Adrian Pavlykevych Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: [Q]: Piping from syslogd to program Message-ID: <19990401033724.B11572@futuresouth.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Adrian Pavlykevych on Thu, Apr 01, 1999 at 12:33:08PM +0300 X-OS: FreeBSD Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Apr 01, 1999 at 12:33:08PM +0300, a little birdie told me that Adrian Pavlykevych remarked > Hello everybody! > > Are there any special tricks to be done to have program which is run by > syslogd and piping logs through it? I don't think I have anything to touch on this precise problem, but... > program is perl script in the form of: > > open(LOG, "/dev/stdin") > while() { Why? What's wrong with just while() { --- *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | Matthew Fuller http://www.over-yonder.net/ | * fullermd@futuresouth.com fullermd@over-yonder.net * | UNIX Systems Administrator Specializing in FreeBSD | * FutureSouth Communications ISPHelp ISP Consulting * | "The only reason I'm burning my candle at both ends, | * is because I haven't figured out how to light the * | middle yet" | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message