Hi All,

I tried to block the logging of 'printk' messages with priority 'KERN_INFO' by setting the log level to 3 using klogd.

---
klogd -c 3.
---

Even after that, I am getting those printk messages in '/var/log/messages'.
I have also verified the current log level by using the following.

----
cat /proc/sys/kernel/printk

Output is:
3 4 1 7
----

Can anyone guide me to achieve what I am looking for.

BTW:
I am using 'Fedora core 6 linux (2.6.18)'


Thanks,

"-c" sets the log level of messages on the console. Edit the /var/log/messages line in /etc/syslog.conf then restart the Syslog service.


You really, really should not. That release of Fedora is so deprecated it isn't even funny.

Hi unspawn,

Thank you very much for your reply.

I think by specifying 'debug.none' we can stop the debug messages logging from /var/log/messages.


I am looking for a way to prevent only the printk messages with a particular priority from logging in.

Is it possible?

I have very little knowledge in this. Please let me know if you want more information from my side.

Thanks,

You probably mean facility LOG_KERN and priority LOG_INFO, so setting it to "kern.notice" should show only messages with priority "notice" and higher. However note that messages of the informational level do just that: informing you of something so you can basically ignore them. Syslog itself will trigger a duplicate message warning if the amount of successive logged messages exceeds the threshold. Also note that using "kern.notice" will block out all informational level messages the kernel sends. This may be too drastic. One way to overcome the problem could be to redirect the application to use one of the LOG_LOCAL slots for logging instead if possible, or else look at syslog-ng which has qualitatively better filtering compared to syslog.

Hi unspawn,

I mean 'KERN_INFO', which we use in drivers to output debug message.

Thanks,

OK, thanks, but that doesn't change my reply. besides, isn't a "debug" setting something that should be governed by per-module arguments (/etc/modprobe.conf, /etc/modprobe.d/)?

Hi there,

I am not able to understand your explanation. Such is my knowledge in syslog and logging mechanism :-( . Can you please explain further or else give me some pointers to refer.

Still I am not able to do what I intend?

Thanks,