From owner-freebsd-ipfw  Tue Jul 27 13:11:57 1999
Delivered-To: freebsd-ipfw@freebsd.org
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
	by hub.freebsd.org (Postfix) with ESMTP
	id A9FF114E2C; Tue, 27 Jul 1999 13:11:47 -0700 (PDT)
	(envelope-from julian@whistle.com)
Received: from current1.whistle.com (current1.whistle.com [207.76.205.22])
	by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id NAA01865;
	Tue, 27 Jul 1999 13:08:25 -0700 (PDT)
Date: Tue, 27 Jul 1999 13:08:24 -0700 (PDT)
From: Julian Elischer <julian@whistle.com>
To: Joe Greco <jgreco@ns.sol.net>
Cc: Nate Williams <nate@mt.sri.com>, hackers@FreeBSD.ORG,
	freebsd-ipfw@FreeBSD.ORG
Subject: Re: securelevel and ipfw zero
In-Reply-To: <199907271949.OAA13262@aurora.sol.net>
Message-ID: <Pine.BSF.3.95.990727130556.29565H-100000@current1.whistle.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-ipfw@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG



a system wide limit and each rule's logging counter individually resetable
back to 0.



On Tue, 27 Jul 1999, Joe Greco wrote:

> 
> 1) Set a global VERBOSE_LIMIT mechanism and:
> 	a) allow your logging counter to be reset, or
> 	b) allow your limit to be raised to re-enable logging
> 2) Set a rule-oriented VERBOSE_LIMIT mechanism and allow each rule's
>    logging counter to be reset.
> 
> So, what's your vote?
> 
> (I'm wondering if maybe we can do a combined 1a and 2 of some sort)
> 
> ... Joe



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ipfw" in the body of the message