Well as Steve suggested. Either change syslogd to not log critical's to
the console (probably a bad idea) or change the --log-level iptables
uses on every line where you tell it to log. See man iptables.

On Sat, 2003-01-11 at 14:09, Steve Kowalik wrote:
> At  5:44 pm, Friday, January 10 2003, Adam Hewitt mumbled:
> > What is the best way to go about preventing iptables logging to the consol, 
> > but still having it log to syslog. It's getting to the point where I am 
> > unable to use the consol because of log flodding...
> > 
> Set $KLOGD in /etc/init.d/sysklogd.
> 
> KLOGD="-c 4"
> 
> I may have changed something in iptables, but I can't remember.
> 
> -- 
>                                            Steve
> WINDOWS = Will Install Needless Data On Whole System
>                                       -- CompuMan
> -- 
> SLUG - Sydney Linux User's Group - http://slug.org.au/
> More Info: http://lists.slug.org.au/listinfo/slug
-- 
---<GRiP>--- 
Web: www.arcadia.au.com/gripz 
Mobile: 0408 686 201
-- 
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug

Reply via email to