bmcdowell
12-10-2002, 04:35 PM
FYI: This isn't a request for help, rather a post that I wish would have been here three or four hours ago.
If you are getting log messages in your active consoles (like I was) you might try checking your /etc/sysconfig/syslog or /etc/rc.d/init.d/syslog files. The basic concept here is that when 'klogd' starts it is given a parameter that states what level of messages get spammed to the screen. Both of these files contain the parameters that klogd is getting when it starts (at least on my system). If not the latter, then the former. To fix the issue, I simply had to add '-c 4' to the startup parameters in the /etc/rc.d/init.d/syslog file. I tried it in the other location about a hundred different ways before I open my eyes and read what the script was doing. Anyway, I hope this helps.
On the downside, I have no idea how it got FUBAR'ed so I'm kinda bummed.
If you are getting log messages in your active consoles (like I was) you might try checking your /etc/sysconfig/syslog or /etc/rc.d/init.d/syslog files. The basic concept here is that when 'klogd' starts it is given a parameter that states what level of messages get spammed to the screen. Both of these files contain the parameters that klogd is getting when it starts (at least on my system). If not the latter, then the former. To fix the issue, I simply had to add '-c 4' to the startup parameters in the /etc/rc.d/init.d/syslog file. I tried it in the other location about a hundred different ways before I open my eyes and read what the script was doing. Anyway, I hope this helps.
On the downside, I have no idea how it got FUBAR'ed so I'm kinda bummed.