On Sat, 2003-12-20 at 22:26, Daniel Bush wrote:
am wondering if the LOG facility of iptables and syslogd are the problem. Have also disabled any '(x)console/tty' items from /etc/syslog.conf )
It's always possible you missed something...
In any case, I always found on my Debian systems that to be sane and happy I would do the following:
rm /dev/console ln -s /dev/tty2 /dev/console
[where 2 was a vt I removed the getty from and had it just for logging]
That, in turn, is a trick I learned from years and years ago on Xenix systems when the default resulting in the same effect you're describing - caused because /dev/console was pointing at /dev/tty0 - which results in any and all console [virtual] ttys being sprayed.
Just my 0.02:
My /etc/syslog.conf file has a customised entry: *.* /dev/tty12 # Log EVERYTHING to tty12
/dev/tty12 is reached by ALT+F12.
I also symlinked /dev/console -> /dev/tty11 (ALT+F11). This way I see *everything* on tty12 and only the critical stuff on tty11.
tty's 1-6 are usually getty's, tty7=Xserver, this leaves tty8-12 for playing around with this console logging stuff. I started at 12 and worked backwards as sometimes I run more than one X session and they increment from 7 upwards. So if I had console logging to tty8, it might cause problems.
Just a thought :) YMMV
--James
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
