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 [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
- Re: securelevel and ipfw zero Joe Greco
- Re: securelevel and ipfw zero Nate Williams
- Re: securelevel and ipfw zero Joe Greco
- Re: securelevel and ipfw zero Nate Williams
- Re: securelevel and ipfw zero Joe Greco
- Re: securelevel and ipfw zero Nate Williams
- Re: securelevel and ipfw zero Joe Greco
- Re: securelevel and ipfw zero Nate Williams
- Re: securelevel and ipfw zero Joe Greco
- Re: securelevel and ipfw zero Achim Patzner
- Re: securelevel and ipfw zero Julian Elischer
- Re: securelevel and ipfw zero Henk van Oers
- Re: securelevel and ipfw zero Brian F. Feldman
- Re: securelevel and ipfw zero Nate Williams
- Re: securelevel and ipfw zero Brian F. Feldman
- Re: securelevel and ipfw zero Henk van Oers
- Re: securelevel and ipfw zero Nate Williams
- Re: securelevel and ipfw zero Nate Williams
- Re: securelevel and ipfw zero Brian F. Feldman
- Re: securelevel and ipfw zero Nate Williams
- Re: securelevel and ipfw zero Brian F. Feldman