From owner-freebsd-ipfw@FreeBSD.ORG Thu Dec 27 05:32:45 2007 Return-Path: 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 0087716A41A for ; Thu, 27 Dec 2007 05:32:45 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from smtp1.yandex.ru (smtp1.yandex.ru [213.180.200.14]) by mx1.freebsd.org (Postfix) with ESMTP id 4965B13C455 for ; Thu, 27 Dec 2007 05:32:43 +0000 (UTC) (envelope-from bu7cher@yandex.ru) Received: from ns.kirov.so-cdu.ru ([77.72.136.145]:24783 "EHLO [127.0.0.1]" smtp-auth: "bu7cher" TLS-CIPHER: "DHE-RSA-AES256-SHA keybits 256/256 version TLSv1/SSLv3" TLS-PEER-CN1: ) by mail.yandex.ru with ESMTP id S8372675AbXL0Fcc (ORCPT ); Thu, 27 Dec 2007 08:32:32 +0300 X-Yandex-Spam: 1 X-Yandex-Front: smtp1 X-Yandex-TimeMark: 1198733552 X-MsgDayCount: 2 X-Comment: RFC 2476 MSA function at smtp1.yandex.ru logged sender identity as: bu7cher Message-ID: <477338E6.2070906@yandex.ru> Date: Thu, 27 Dec 2007 08:32:22 +0300 From: "Andrey V. Elsukov" User-Agent: Mozilla Thunderbird 1.5 (FreeBSD/20051231) MIME-Version: 1.0 To: rihad References: <47721BFF.9010309@mail.ru> In-Reply-To: <47721BFF.9010309@mail.ru> Content-Type: text/plain; charset=KOI8-R; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-ipfw@freebsd.org Subject: Re: disabling syslog messages? X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 27 Dec 2007 05:32:45 -0000 rihad wrote: > 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? If you don't use `ipfw log ...` rules you can reset sysctl variable net.inet.ip.fw.verbose to 0 and these messages will not be logged. -- WBR, Andrey V. Elsukov