On Thu, November 22, 2012 at 13:29 (+0100), Kay Sievers wrote: > On Thu, Nov 22, 2012 at 11:44 AM, Jan Schmidt <list.l...@jan-o-sch.net> wrote: >> I'm currently debugging something in btrfs in good old printk style, >> generating >> around 10MB/min. I'm seeing /proc/kmsg returning eof on a blocking read (and, >> side note, syslog-ng won't reopen it, effectively stopping logging kernel >> messages silently). > > Are you sure there is not something else that opens the same file?
Those errors didn't happen on that machine ever before, and there should have been no user land changes to it for quite a long time. I'm tempted to say there is no other kmsg reader, but just to make it entirely sure, how would I trace this? From a quick look at ftrace I don't see it would output file names when tracing sys_open, unfortunately. Thanks! -Jan -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
