Adding an "logamount" option to each logging rules would be to "long way work around". Adding net.inet.ip.fw.verbose_limit=100 to /etc/sysctl.conf would be the short way. -----Original Message----- From: owner-freebsd-questions_at_freebsd.org [mailto:owner-freebsd-questions_at_freebsd.org]On Behalf Of Rob Sent: Sunday, July 04, 2004 8:15 AM To: freebsd-stable_at_freebsd.org; freebsd-questions_at_freebsd.org; freebsd-current_at_freebsd.org Subject: Re: IPFIREWALL_VERBOSE_LIMIT ignored by recent kernel/world? Dan Pelleg wrote: > I have a patch for that in kern/46080. Note I haven't tested it in a while > > http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/46080 > So what I observed (security logfile get floaded with ipfw2 logs) is actually a kind of bug. If so, I'd rather wait till the fix makes it into the official sources. If not, then I won't change my own sources. Work around for now could be to add a "logamount" statement to each of the logging rules of ipfw2. Right? Thanks! Regards, Rob. PS: does this problem also occur in CURRENT, which uses by default IPFW2 ? _______________________________________________ freebsd-questions_at_freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe_at_freebsd.org"Received on Sun Jul 04 2004 - 10:35:35 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:00 UTC