Bug #595
Updated by Marc Dequènes 4 months ago
Quite often a service is considered OK because the init script did not return an error, but the SYSV compatibility layer in systemd has no way to know if this is a one-shot run or if a daemon is to be run, and maybe forked.
We should evaluate all the compat services listed with this command:
<pre>
ansible all -m shell -a "systemctl | grep -E 'active +(exited|running) +(LSB|SYSV):' +exited +LSB:' | awk '{ print \$1 }'"
</pre>
We should list the one-shot services somewhere, to be able to filter-out in a later (regular?) check.
We should borrow missing systemd config from Debian unstable if existing and applicable or create our own and contribute it.
We should evaluate all the compat services listed with this command:
<pre>
ansible all -m shell -a "systemctl | grep -E 'active +(exited|running) +(LSB|SYSV):' +exited +LSB:' | awk '{ print \$1 }'"
</pre>
We should list the one-shot services somewhere, to be able to filter-out in a later (regular?) check.
We should borrow missing systemd config from Debian unstable if existing and applicable or create our own and contribute it.