Thanks Dimitri for all the pre-work and the suggested systemd unit matching the
old upstart job.
We really like that, especially as it avoids the concern of "just another
ongoing log" due to being an initial one-shot task that does not continue to
log the ongoing messages.
And yes - having especially the initial boot messages can be quite handy way
later.
There also is not only the journal but also at /etc/rsyslog.d/50-default.conf:
kern.* -/var/log/kern.log
But it is on logrotation (4) so it would as well over time loose the early boot
messages.
In our discussion we even consider to SRU this as it is essentially a
loss of functionality post-Trusty.
The journal style invocation is clearly better to not exceed ring buffers so
fast on huge systems.
And especially on such it might be interesting later on what was going on.
Being lost post-trusty we might consider the more reliable way to get all
messages (journalctl) more important than keeping the format absolutely the
same.
There is nothing there people can rely upon yet, so the new format won't break
them.
This isn't releas breaking, so as usual we'd have to wait until DD
opens, then implement there and potentially SRU it back then.
** Tags added: server-next
** Changed in: rsyslog (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1450588
Title:
/var/log/dmesg No Longer Being Updated
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1450588/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
