From: Jeff Dike <jdike@ka...> - 2001-06-08 20:27:18
> I experienced a strange
> behavior with the printk() function. Observing the output with
> cat /proc/kmsg
> I can only see every 2nd message.
I tried this and my cat hung (and no snide remarks from dwmw2 puleeze :-)
I *think* the situation is that /proc/kmsg is for klogd only, and when I read
it, klogd has already recorded everything, so there's nothing new and cat
blocks. And I think what's happening in your case is that you're competing
with klogd for the new stuff, and you're getting half of it and klogd is
getting the other half.
You can check this by seeing if the half that you don't get from cat is ending
up in the error log.
From: David Woodhouse <dwmw2@in...> - 2001-05-05 17:27:20
> tnfink@... said:
> > cat /proc/kmsg
> > I can only see every 2nd message.
> Hmm, I'm not even getting that. I'm just getting a hung cat.
> One more thing to add to the todo list.
/me looks at the feathers on the living room floor. Hmmm. "hung cat". Now
there's an idea.
Get latest updates about Open Source Projects, Conferences and News.