All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Question about /proc/kmsg semantics..
Date: 30 Apr 2001 22:33:09 -0700	[thread overview]
Message-ID: <9clhql$lep$1@cesium.transmeta.com> (raw)
In-Reply-To: <20010501005237.A2776@sync.nyct.net>

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

      reply	other threads:[~2001-05-01  5:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-01  4:52 Question about /proc/kmsg semantics Michael Bacarella
2001-05-01  5:33 ` H. Peter Anvin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='9clhql$lep$1@cesium.transmeta.com' \
    --to=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.