Messages in this thread |  | | Date | Tue, 1 May 2001 00:52:37 -0400 | From | Michael Bacarella <> | Subject | Question about /proc/kmsg semantics.. |
| |
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 <mbac@nyct.net> 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 majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |