Date: Mon, 20 Sep 1999 20:11:08 -0400 (EDT) From: "Crist J. Clark" <cjc@cc942873-a.ewndsr1.nj.home.com> To: des@flood.ping.uio.no (Dag-Erling Smorgrav) Cc: green@FreeBSD.ORG (Brian F. Feldman), cjclark@home.com, root@net72-105.student.yale.edu (Root), skalir@hotmail.com (skalir scalar), freebsd-security@FreeBSD.ORG Subject: Re: ipfw and syslogd Message-ID: <199909210011.UAA05849@cc942873-a.ewndsr1.nj.home.com> In-Reply-To: <xzp7lllqse9.fsf@flood.ping.uio.no> from Dag-Erling Smorgrav at "Sep 20, 1999 09:45:02 pm"
index | next in thread | previous in thread | raw e-mail
Dag-Erling Smorgrav wrote, > "Brian F. Feldman" <green@FreeBSD.ORG> writes: > > On Thu, 16 Sep 1999, Crist J. Clark wrote: > > > Dag-Erling Smorgrav wrote, > > > > Root <root@net72-105.student.yale.edu> writes: > > > > > !ipfw > > > > > *.* /var/log/firewall.log > > > > Won't work in -STABLE, because ip_fw.c uses printf() instead of log(). > > It should work just fine, since printf()s go to syslog too. > > It's never worked for me in -STABLE, though it's possible that I'm > mistaken and that it's a syslogd issue rather than a printf() vs. > log() issue. I'm also curious about this for another reason to. I just configured a machine as a bridge, and there is a steady, but not alarming, flow of "collision" messages. I looked up the source in /usr/src/sys/net/bridge.c and see that the messages are printf()'s. These messages are annoying in my /var/log/messages file. I'd rather run them through a script to boil them down to stats or even direct to /dev/null, but how do I direct kernel messages produced by printf()'s? Now that I wrote this, it looks like the _exact_ same problem as with ipfw. -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the messagehelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199909210011.UAA05849>