From owner-freebsd-security Fri Sep 17 16:45: 6 1999 Delivered-To: freebsd-security@freebsd.org Received: from news.lucky.net (news.lucky.net [193.193.193.102]) by hub.freebsd.org (Postfix) with ESMTP id 5AA4515113 for ; Fri, 17 Sep 1999 16:44:28 -0700 (PDT) (envelope-from mail@news.lucky.net) Received: (from mail@localhost) by news.lucky.net (8.Who.Cares/8.Who.Cares) id CAA02506 for freebsd-security@freebsd.org; Sat, 18 Sep 1999 02:44:17 +0300 (envelope-from mail) To: freebsd-security@freebsd.org From: ay@sita.kiev.ua.europe Subject: Re: ipfw and syslogd User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.1-RELEASE (i386)) Organization: Home Sweet Home Message-ID: References: Date: Fri, 17 Sep 1999 21:20:51 GMT Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Brian F. Feldman wrote: > On Thu, 16 Sep 1999, Crist J. Clark wrote: >> Dag-Erling Smorgrav wrote, >> > Root 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. >> >> Bug or feature? >> > Neither. I just haven't merged back the changes which make ipfw use log(9). > (I should say "yet," as I hope to do so soon.) Is it a nice way to speed up kernel ? One may use ipfw show from cron to store most of valuable information from ipfw. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message