RJrLm> I'm not sure what klogd is, my system currently runs only
RJrLm> syslogd. Is there an advantage to getting and running
RJrLm> klogd? (I don't have it) Note that when the disk is dead,
RJrLm> processes that are not very active and suddenly need to do
RJrLm> something stand a high chance of failure. (because they
RJrLm> have been swapped out)
klogd is supposed to handle kernel messages more cleanly than
syslogd... whatever this means.
RJrLm> I know it is against the "do it in user mode" religion, but
RJrLm> I really think that critical error message printing should
RJrLm> be done in the kernel, not in a user process that probably
RJrLm> dies with the system.
If the process dies, the syslog interface to the kernel is closed.
When this interface is closed (because of a crash or because syslogd
has not been started), error messages are just sent by the kernel to
the console. Syslogd is only an utility program that allows you to
filter and redirect those messages. The real work of creating and
sending the message is done in the kernel.
ldd