Re: printk behavioral regression

[Jan Beulich]

>>> On 19.06.12 at 15:53, Kay Sievers <kay@xxxxxxxx> wrote:
> On Tue, Jun 19, 2012 at 3:30 PM, Jan Beulich <JBeulich@xxxxxxxx> 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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/