From owner-freebsd-questions Mon May 17 8:40:33 1999 Delivered-To: freebsd-questions@freebsd.org Received: from dt051nc7.san.rr.com (dt051nc7.san.rr.com [204.210.32.199]) by hub.freebsd.org (Postfix) with ESMTP id B5D3E1564D for ; Mon, 17 May 1999 08:40:22 -0700 (PDT) (envelope-from Studded@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt051nc7.san.rr.com (8.8.8/8.8.8) with ESMTP id IAA00505; Mon, 17 May 1999 08:40:07 -0700 (PDT) (envelope-from Studded@gorean.org) Message-ID: <37403856.E9638EA2@gorean.org> Date: Mon, 17 May 1999 08:40:06 -0700 From: Studded Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-STABLE-0516 i386) X-Accept-Language: en MIME-Version: 1.0 To: Chris England Cc: questions@freebsd.org Subject: Re: ipfw - question / suggestion References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris England wrote: > > Why is it that using IPFIREWALL_VERBOSE in conjunction with ipfw logging > rules, the logging is dumped in bold to the console, as well as logged to > syslogd? > > Is there any way I can prevent it from logging directly to the console? I > think it would be much more clean if it was only picked up syslogd, that > way if I really wanted it to see it on my console, I could point the > !ipfw output to /dev/console from syslog.conf. Unfortunately, ipfw logs to the kernel syslog facility. Why doesn't it log to its own facility? I dunno. In any case, it logs at the critical level, so all you need to do is change your syslog.conf file so that it doesn't log things of critical level or below to the console. The info on how to do that is in the man page for syslog.conf. Good luck, Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message