Well, funny thing -- I discovered that even though klogd was started
it wasn't running by the time I got to the command prompt. When I
restarted it manually I got the following response which was recorded
in the correct files and after the response klogd continued
"normally".
Apr 16 03:36:38 ccs kernel: klogd 1.3-3, log source = /proc/kmsg started.
Apr 16 03:36:39 ccs kernel: Loaded 5885 symbols from /boot/System.map.
Apr 16 03:36:39 ccs kernel: Symbols match kernel version 2.1.89.
Apr 16 03:36:39 ccs kernel: Error seeking in /dev/kmem
Apr 16 03:36:39 ccs kernel: Error adding kernel module table entry.
What does this mean? How can I get klogd to remain?
-- John Covici covici@ccs.covici.com- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu