From owner-freebsd-ipfw@FreeBSD.ORG  Wed Sep 19 10:20:34 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 33D0A16A417;
	Wed, 19 Sep 2007 10:20:34 +0000 (UTC) (envelope-from sem@FreeBSD.org)
Received: from mail.ciam.ru (ns.ciam.ru [213.247.195.75])
	by mx1.freebsd.org (Postfix) with ESMTP id D6C7213C500;
	Wed, 19 Sep 2007 10:20:33 +0000 (UTC) (envelope-from sem@FreeBSD.org)
Received: from dhcp250-210.yandex.ru ([87.250.250.210])
	by mail.ciam.ru with esmtpa (Exim 4.x)
	id 1IXw6B-0003U0-9F; Wed, 19 Sep 2007 13:43:59 +0400
Message-ID: <46F0EF1E.5070709@FreeBSD.org>
Date: Wed, 19 Sep 2007 13:42:54 +0400
From: Sergey Matveychuk <sem@FreeBSD.org>
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Remko Lodder <remko@FreeBSD.org>
References: <200709190920.l8J9KFVs025856@freefall.freebsd.org>
In-Reply-To: <200709190920.l8J9KFVs025856@freefall.freebsd.org>
Content-Type: text/plain; charset=windows-1251; format=flowed
Content-Transfer-Encoding: 7bit
Cc: freebsd-ipfw@FreeBSD.org
Subject: Re: misc/116458: Logging problems with syslog and ipfw an 6.2.REL-p5
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, 19 Sep 2007 10:20:34 -0000

Remko Lodder wrote:
>  Hello,
>  
>  First of all thank you for using FreeBSD and taking the time to write
>  this report. However I do not think that this is a problem perse, did
>  you go and ask around on the ipfw@ mailinglist? They have very good
>  clue on the ipfw framework and might tell you what the problem is and
>  whether this should be fixed by using the PR system or whether it was
>  only you making a typo or something, this is important to not overload
>  the ticketing system with potentially things that are not problems but
>  user typo's (which ofcourse can occur, we all have that :-))
>  

I'll repeat here a history.

We have a high load routers with ipfw. And a lot of log messages as a 
result. We've patched em(4) driver and it use kernel threads (it's not a 
main reason as I got reports other people saw a junk like us but 
rarely). And we got a lot of junk in syslog from ipfw.

There is no junk at all after my patch was applied on one of our core 
routers for a month.

-- 
Dixi.
Sem.