Ahoj, Dňa Sun, 31 Aug 2014 17:09:04 +0100 Brian <ad44@cityscape.co.uk> napísal: > On Sun 31 Aug 2014 at 17:24:50 +0200, Erwan David wrote: > > > Le 31/08/2014 16:12, Brian a écrit : > > > > > > I get the same thing too. It goes away when systemd-shim is > > > purged. :) > > > > This is related to the error messages. Not th fact that the logs of > > systemd are not saved in any file, but only in dmesg buffer, so > > will get lost. > > #757696 (merged with #748648, a report you opened) has > > That's a problem of running logind standalone. > > The systemd log infrastructure uses the kernel ring buffer only > during early boot. As soon as the journal is available, the log > messages are logged to the journal. > The problem here is, that systemd-shim doesn't provide the journal > functionality, so the systemd components (like logind) continue to > use the kernel ring buffer (kmsg). > > I'm inclined to re-assign this bug to systemd-shim, as this bug is > caused by running logind under systemd-shim and the shim failing to > provide that logging infrastructure. > Yes, i am sure, that this is great example of the systemd modularity. -- Slavko http://slavino.sk
Attachment:
signature.asc
Description: PGP signature