From owner-freebsd-ipfw Sat Dec 7 15:15:40 2002 Delivered-To: freebsd-ipfw@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 15A7937B401 for ; Sat, 7 Dec 2002 15:15:40 -0800 (PST) Received: from gs166.sp.cs.cmu.edu (GS166.SP.CS.CMU.EDU [128.2.205.169]) by mx1.FreeBSD.org (Postfix) with SMTP id 9564643EC5 for ; Sat, 7 Dec 2002 15:15:39 -0800 (PST) (envelope-from dpelleg@gs166.sp.cs.cmu.edu) To: Dan Pelleg Cc: freebsd-ipfw@freebsd.org Subject: Re: logamount in ipfw2 References: From: Dan Pelleg Date: 07 Dec 2002 18:15:32 -0500 In-Reply-To: Message-ID: Lines: 15 User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-ipfw@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Dan Pelleg writes: > It seems that the "log" option in ipfw2 works differently than it does on > ipfw. When given no "logamount" argument, then ipfw does as the man page > says and sets the limit to the value of net.inet.ip.fw.verbose_limit. > On the other hand, ipfw2 sets it to zero (meaning unlimited logging). > I've opened a PR for this (kern/46080). It includes a patch to mimic the ipfw functionality (admittedly, the code is taken from the corresponding section in ipfw.c). -- Dan Pelleg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ipfw" in the body of the message