Re: Question about /proc/kmsg semantics..

2001-04-30 Thread H. Peter Anvin 

Followup to:  <[EMAIL PROTECTED]>
By author:Michael Bacarella <[EMAIL PROTECTED]>
In newsgroup: linux.dev.kernel
> 
> 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
messages.

-hpa
-- 
<[EMAIL PROTECTED]> at work, <[EMAIL PROTECTED]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Question about /proc/kmsg semantics..

2001-04-30 Thread Michael Bacarella 

Two pronged:

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() ?

Thanks

-- 
Michael Bacarella <[EMAIL PROTECTED]>
Technical Staff / System Development,
New York Connect.Net, Ltd.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/