From: Kalin KOZHUHAROV <kalin@thinrope.net>
To: linux-kernel@vger.kernel.org
Subject: Re: SysReq & serial console
Date: Wed, 11 Jan 2006 14:51:12 +0900 [thread overview]
Message-ID: <dq26cg$3el$1@sea.gmane.org> (raw)
In-Reply-To: <20060102091808.GA11673@flint.arm.linux.org.uk>
Russell King wrote:
> On Mon, Jan 02, 2006 at 04:29:38PM +0900, Kalin KOZHUHAROV wrote:
>
>>Another wild guess: the syslog is still running and writes the output to
>>the log.
>
>
> I don't think syslog can influence whether you see sysrq output via the
> console. Nevertheless, try sysrq-8 before other sysrq functions.
>
While playing with a borked 2.6.15 box and syslog-ng, I ran across this again.
The issue is that syslog-ng can use /proc/kmesg as a source for logging and
if this is the case, then (intentionally or not), it sucks all the MSGs and
if not setup correctly MSGs from kernel will go to nowhere. The relevant
syslog-ng setup is:
source foo { pipe("/proc/kmsg"); };
This might be a problem/feature/bug with syslog-ng, but I still find it more
natural to see the output of SysRq and oopses on the console as well.
Kalin.
--
|[ ~~~~~~~~~~~~~~~~~~~~~~ ]|
+-> http://ThinRope.net/ <-+
|[ ______________________ ]|
prev parent reply other threads:[~2006-01-11 5:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-01 23:44 SysReq & serial console Reinhard Nissl
2006-01-02 0:37 ` Russell King
2006-01-02 7:29 ` Kalin KOZHUHAROV
2006-01-02 9:18 ` Russell King
2006-01-02 20:16 ` Reinhard Nissl
2006-01-11 5:51 ` Kalin KOZHUHAROV [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='dq26cg$3el$1@sea.gmane.org' \
--to=kalin@thinrope.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox