From owner-freebsd-ipfw@FreeBSD.ORG  Wed Dec 26 12:19:52 2007
Return-Path: <owner-freebsd-ipfw@FreeBSD.ORG>
Delivered-To: freebsd-ipfw@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 7676316A417
	for <freebsd-ipfw@freebsd.org>; Wed, 26 Dec 2007 12:19:52 +0000 (UTC)
	(envelope-from rihad@mail.ru)
Received: from mx4.mail.ru (fallback.mail.ru [194.67.57.14])
	by mx1.freebsd.org (Postfix) with ESMTP id 41B0A13C442
	for <freebsd-ipfw@freebsd.org>; Wed, 26 Dec 2007 12:19:52 +0000 (UTC)
	(envelope-from rihad@mail.ru)
Received: from mx27.mail.ru (mx27.mail.ru [194.67.23.23])
	by mx4.mail.ru (mPOP.Fallback_MX) with ESMTP id A8A1B75A4F
	for <freebsd-ipfw@freebsd.org>; Wed, 26 Dec 2007 12:17:11 +0300 (MSK)
Received: from [217.25.27.27] (port=48813 helo=[217.25.27.27])
	by mx27.mail.ru with esmtp id 1J7SNx-000E0G-00
	for freebsd-ipfw@freebsd.org; Wed, 26 Dec 2007 12:17:09 +0300
Message-ID: <47721BFF.9010309@mail.ru>
Date: Wed, 26 Dec 2007 13:16:47 +0400
From: rihad <rihad@mail.ru>
User-Agent: Icedove 1.5.0.14pre (X11/20071018)
MIME-Version: 1.0
To: freebsd-ipfw@freebsd.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: disabling syslog messages?
X-BeenThere: freebsd-ipfw@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IPFW Technical Discussions <freebsd-ipfw.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw>,
	<mailto:freebsd-ipfw-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ipfw>
List-Post: <mailto:freebsd-ipfw@freebsd.org>
List-Help: <mailto:freebsd-ipfw-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ipfw>,
	<mailto:freebsd-ipfw-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Dec 2007 12:19:52 -0000

Hi, I'm using "ipfw zero NNN" to periodically zero many counters, each 
of which results in a syslog message generated despite the -q flag:

Dec 26 13:00:01 foo kernel: ipfw: Entry 1001 cleared.
Dec 26 13:00:01 foo kernel: ipfw: Entry 1002 cleared.
...
and so on. After looking in ipfw's sources in /usr/src/sbin/ipfw/ipfw2.c 
I now think that quite probably the messages are generated by some 
setsockopt call or by the kernel itself. I _could_ work around the issue 
by piping the "ipfw:" messages to /dev/null in syslogd, but there might 
be a cleaner solution?

Thank you.