Hi, > In practice, my experience is that if I install bootchart, then install > bootchart2 without purging bootchart, and boot with systemd, systemd gets > very confused and leaves the bootchart daemon running indefinitely. In > contrast, if I boot with sysvinit, the init script in /etc/rc2.d/ does a > perfectly adequate job of stopping bootchartd at the right point. So the > lack of sysvinit integration looks to actually hurt integration with systemd > too.
systemd doesn't get "very confused". The bug here is, that bootchart2 ships systemd unit files, but doesn't actually enable them. The systemd unit responsible for stopping the bootchart daemon is called bootchart-done.service. Until we ship the necessary helper tool, systemd units need to be enabled manually via systemctl enable <foo.service> David, as for this particular case, when you ship a sysv init script, please consider naming it after the native systemd service file (i.e bootchart-done). Cheers, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
