Friday, March 7, 2008

Printk() problem solved !!!

Prink()'s on my systems seem to come as <4> = KERN_WARNING from all my dccp kernel codes.

In order to catch them (by neck :@), the trick was to kill "klogd" and restart it with the following options ::

klogd -x -f - -n -c 8

This will log everything conveniently on the console which can easily be redirected to any file if needed, finally leaving me in peace with exactly what I wanted ;) God bless "klogd" !!!