From: "Jan Beulich" <JBeulich@suse.com>
To: "Kay Sievers" <kay@vrfy.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: printk behavioral regression
Date: Tue, 19 Jun 2012 15:04:28 +0100 [thread overview]
Message-ID: <4FE0A30C020000780008AA0B@nat28.tlf.novell.com> (raw)
In-Reply-To: <CAPXgP13y_xOUzHdStsDWescPtJYn0nvMhsQ7c2XS3HBuE=jwow@mail.gmail.com>
>>> On 19.06.12 at 15:53, Kay Sievers <kay@vrfy.org> wrote:
> On Tue, Jun 19, 2012 at 3:30 PM, Jan Beulich <JBeulich@suse.com> wrote:
>> running 3.5-rc3 on a SLE11 SP1 system, early boot messages (apart
>> from the very first one) end up in /var/log/messages rather than
>> /var/log/boot.msg. I didn't dig deep enough yet to figure out what
>> is causing this, and would hope that you (having contributed most
>> of the changes between 3.4 and 3.5-rc3) might have an idea.
>
> Hmm, no idea really, and why this should change.
Okay, then I'll indeed need to do some debugging.
> /var/log/boot.msg is a SUSE speciality, that, as far as I know, just
> dumps 'dmesg' after bootup, it has not much to do with the normal
> syslog/klog logging in /var/log/messages, where all your messages should
> always end up, and what seems to work for you.
No, boot messages (at least by default) end up _only_ in
/var/log/boot.msg, and thus significantly help keeping the size
of /var/log/messages down. SUSE specialty or not, there
clearly is some user space visible change here.
Jan
next prev parent reply other threads:[~2012-06-19 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 13:30 Jan Beulich
2012-06-19 13:53 ` Kay Sievers
2012-06-19 14:04 ` Jan Beulich [this message]
2012-06-19 14:34 ` Kay Sievers
2012-06-22 15:24 ` Jan Beulich
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=4FE0A30C020000780008AA0B@nat28.tlf.novell.com \
--to=jbeulich@suse.com \
--cc=kay@vrfy.org \
--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
all inboxes | Powered by JetHome®