It took me some time to figure out there even was a vt12. Syslog messages with a priority of <1> should not be that hard to find. Reproducible: Always Steps to Reproduce: 1. printk("<1>Something\n"); 2. search high and low for the output without typing dmesg Actual Results: Tried every available syslogd. Ranted in #gentoo for a while, then eventually located /etc/syslog-ng/syslog-ng.conf on my own and filed this bug report Expected Results: destination console_all { file("/dev/console"); }; The syslog daemon should output high priority messages to the console and syslog. Not doing this is very frusterating, especially when switching back to console from X seems to not work for some other strange reason, leaving my monitor displaying a frequency out of range message. Thus vt12 being impossible to find.
Some nvidia drivers were buggy when switching from X back to console. Happen to have an nVidia card?
Curtis - can you talk more about why you think this should be a global change and not just something you change on your own system? Thanks.
Created attachment 11057 [details, diff] proposed patch to configuration I agree. X-users can set up xconsole to view their console messages. Here is the proposed patch to the syslog-ng.conf. chuck
My reasons being the ability to intecept the console messages in X if so desired, as well as that being the expected behaviour of syslog. See here for one example: http://www.xml.com/ldd/chapter/book/ch02.html from O'Reillys Linux Device Driver book. Further, every *nix I've worked with behaves this way.
On second thought, its probably not a good idea to dump *everything* to /dev/console. Probably just LOG_EMERG, LOG_ALERT, LOG_CRIT, and possibly LOG_ERR. Otherwise tty1 becomes a very messy place if the console alerts aren't intercepted.
I've modified the default syslog-ng.conf with an uncommentable line to address this. The default behavior for syslog-ng on Gentoo Linux is to log to /dev/tty12. If this isn't what you want, feel free to modify the config files locally.
