Bug#762700: systemd: journald fails to forward most boot messages to syslog
Michael Biebl
biebl at debian.org
Wed Feb 25 20:27:41 GMT 2015
Control: tags -1 moreinfo
Am 25.02.2015 um 18:59 schrieb Christian Seiler:
> Control: severity -1 serious
>
> Thoughts?
Those missing syslog messages (only) happen when systemd flushes the
initial boot kernel/messages to the syslog socket, right?
Once the syslog daemon is running, do you still get messages about
syslog messages being dropped?
If the former, I don't think it's a serious bug. After all, with classic
syslog, you didn't even capture that data from early boot in the first
place.
It would certainly be good to fix this issue, but I don't think it
qualifies as RC.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 834 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150225/e2204a0f/attachment-0002.sig>
More information about the Pkg-systemd-maintainers
mailing list