Messages in this thread | | | From | "H. Peter Anvin" <> | Subject | Re: Question about /proc/kmsg semantics.. | Date | 30 Apr 2001 22:33:09 -0700 |
| |
Followup to: <20010501005237.A2776@sync.nyct.net> By author: Michael Bacarella <mbac@nyct.net> 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 -- <hpa@transmeta.com> at work, <hpa@zytor.com> 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 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/
| |