The 03.08.03 at 13:04, Johannes Liedtke wrote:
BTW: Are those messages from console 10 logged to a file somewhere? Or is it at all possible to log those messages to a file?
Yes... to a point. It is done by the syslog daemon, whose configuration file is "/etc/syslog.conf". See syslogd(8) and syslog.conf(5) Kernel error messages are defined thus: kern.warn;*.err;authpriv.none /dev/tty10 kern.warn;*.err;authpriv.none |/dev/xconsole *.emerg * So, kernel error message of level "warn" and above - that is: warn (same as warning), err, error (same as err), crit, alert, emerg, panic (same as emerg) - logged by the "facility kern" go to tty10, and to the xconsole in x (you may or may not see it on your X session, depends). A few more things go there: every message of level "error" and above, and authorization errors. Notice that any messages of level "emerg" go to any active console. Now, if you want to log kernel messages to a file, you could add this line: kern.* -/var/log/kernel The "-" sign implies that output is buffered, not immediately written to disk. Mind you, this file can some times grow pretty fast, like hundred of megabytes per hour, in case of some repeated error, but not normally. Of course, if you enable it you have to configure logrotate to periodically erase and/or compress those logs. I normally have it enabled. But, in the case at hand, it shows nothing! Reasons? All filesystems are umounted before the system is halted (they would be trashed otherwise). Only console number 10 shows the error (see my other message on this thread). -- Cheers, Carlos Robinson