From: Andrew Morton <akpm@osdl.org>
To: Seth Arnold <sarnold@immunix.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: setterm -msg off broken in 2.6.9
Date: Fri, 22 Oct 2004 04:06:21 -0700 [thread overview]
Message-ID: <20041022040621.30f8c1bf.akpm@osdl.org> (raw)
In-Reply-To: <20041019063344.GC4415@immunix.com>
Seth Arnold <sarnold@immunix.com> wrote:
>
> Hello, I'm using 2.6.9 on my ibook g3 700mhz, debian unstable.
>
> I use setterm -msg off to turn off kernel log buffer to console from
> time to time. It now reports an error:
> $ setterm -msg off
> klogctl error: Unknown error 4294967295
>
> kernel log messages are still printed to the console.
>
I assume that's because:
2643 syslog(0x6, 0, 0) = -1 EPERM (Operation not permitted)
but cap_syslog() has disallowed command 6 for a long time.
It seems reasonable to be able to kill console messages if the user is
using the console, but from my reading current 2.4 kernels will fail this
if you're not root as well.
With what kernel were you able to run `setterm -msg' without being root?
prev parent reply other threads:[~2004-10-22 11:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-19 6:33 setterm -msg off broken in 2.6.9 Seth Arnold
2004-10-22 11:06 ` Andrew Morton [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=20041022040621.30f8c1bf.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sarnold@immunix.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox