[lkml]   [2001]   [May]   [1]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Question about /proc/kmsg semantics..
Followup to:  <>
By author: Michael Bacarella <>
In newsgroup:
> I've seen a couple of patches in the archives to make open()/close()
> on /proc/kmsg do more than NOP. As of 2.4.4, klogd still needs to
> run as root since access is checked on read() rather than once at
> open(). I can't find the rationale as to why they're rejected.
> Also, why is reading /proc/kmsg a privileged operation, yet dmesg
> can happily print out the entire ring via (do_)syslog() ?

Probably because reading /proc/kmsg may cause syslogd to miss

<> at work, <> in private!
"Unix gives you enough rope to shoot yourself in the foot."
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:52    [W:0.027 / U:0.112 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site