On 2016-05-12 14:56:38 +0200, Andreas Henriksson wrote: > Also, it's still unknown /why/ bootlogd doesn't work with systemd! > Apparently bootlogd relies on some facitily not provided by systemd.
Well, the bootlogd description says: bootlogd logs all messages printed to the system console during system boot, and records those messages to a logfile. However, with systemd, nothing seems to be written to the system console (well, nothing appears, but I don't know whether something is printed but hidden or nothing is printed). This may be the cause. If a conflict is not possible (at least, bootlogd doesn't seem to hurt), I think that having a clear description would be sufficient. Something like: Description: daemon to log boot messages printed to the system console bootlogd logs all messages printed to the system console during system boot, and records those messages to a logfile. Note that not all init systems print messages to the system console, so that the logfile may remain empty; this is the case with systemd. Someone might also want to add a systemd unit file that writes a message saying that bootlogd does nothing with systemd, which has its own logging system (systemd journal). -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)