click_chatter

arvind venkaa at cs.rpi.edu
Sun Feb 24 21:28:28 EST 2002


> click_chatter() output uses printk() to generate its output. The system
> logger daemon (syslogd) logs this output in /var/log/messages, and
dmesg(1)
> can get it. Unfortunately, as it seems like you've discovered, syslogd can
> lose some messages, if they are generated too fast. There is no easy way
> around this. If you want better control, you will need to "roll your own".
> But I would recommend generating fewer messages, to make sure that syslogd
> gets all the ones you need.

Yes, they are being generated so fast that most of them are getting lost.
Thanks for getting back to me
promptly and clarifying the whole issue.

Thanks again!

-arvind





More information about the click mailing list