On Thu, Jun 23, 2005 at 06:37:03PM -0500, ephemeroot@bluebottle.com wrote: > Quoting Alban Browaeys <browaeys.alban@wanadoo.fr>: > > > Le Wed, 15 Jun 2005 15:39:07 -0400, Jeff Elkins a écrit > > : > > > > > I'm trying to rid myself of annoying iptables messages > > that are clogging up > > > the console and dmesg. To my firewall script I've > > added: > > > > > > echo 0 > > > /proc/sys/net/ipv4/netfilter/ip_conntrack_log_invalid > > > > > > And to sysklogd: > > > > > > KLOGD="-c 4" > > > > > > The console messages seem to be gone, but dmesg is > > still clogged with iptables > > > junk. > > > > > > This is dmesg . From dmesg manual : dmesg -n1 , it fixed > > it for me. > > Is there a similarly concise way to restrict the console > messages to one ttyX (but not eliminate them altogether)? > One poster suggested (in another thread) that I install the > package console-log. But surely there's a one line command > that will do the trick? What files in /etc or /proc do I > need to modify? > Hi! The standard "kernel-to-console-logging-feature" logs to the active console, whichever that may be. If you want to have your kernel debugging output directed to a specific one, you have to disable this feature (dmesg -n1, klogd -c1, or calling the C routine klogctl() yourself), and add something like this to your /etc/syslog.conf: kern.* /dev/tty8 Note that now the debug messages will have the usual syslog stuff prepended (timestamp, hostname, and "kernel:"), but I can't think of a different solution atm. HTH, Jan -- Jan C. Nordholz <jckn At gmx net>
Attachment:
signature.asc
Description: Digital signature