Blah, second time I've done this. Dropped the keyboard, which by some stroke of chance managed to put scroll lock on on the vconsole with syslog spewing things. Buffer fills, syslog hangs, anything trying to use syslog hangs. Chaos ensues. If you're like me and have a "*.* /dev/tty12" in your syslog.conf, and suddenly find youself unable to log in, check the scroll lock on that vconsole... (If you don't have physical access to the console at the time you're screwed. ;) Check scroll lock after you've knocked the keyboard off the desk for the Nth time. Or use some kind of tail on a log file rather than directly dumping to a console. Though this strikes me as a rather serious bug. Something as vital as syslog shouldn't hang if it can't write somewhere, should it? ;P --------------------------------------------------------------------- To unsubscribe, e-mail: tclug-list-unsubscribe at mn-linux.org For additional commands, e-mail: tclug-list-help at mn-linux.org