Bug #595
closedCreate missing systemd configuration for SYSV compatibility services
100%
Description
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:
ansible all -m shell -a "systemctl | grep -E 'active +(exited|running) +(LSB|SYSV):' | awk '{ print \$1 }'"
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.
Updated by Marc Dequènes about 7 years ago
- Related to Bug #605: No mail since 2017-10-15 07:00:02 added
Updated by Pierre-Louis Bonicoli about 7 years ago
- Related to Bug #606: Bip service unavailable since Oct 15 (Thorfinn) added
Updated by Marc Dequènes over 6 years ago
Added `playbooks/restart_lsb_services.yml` as a workaround to restart these services.
Updated by Marc Dequènes over 6 years ago
- Status changed from New to In Progress
- Assignee set to DC Admins
I recently created one for spoolinger. It will be in the package when this is ready.
Updated by Marc Dequènes over 6 years ago
policyd-weight is no more so no need to continue working on this.
Updated by Marc Dequènes over 5 years ago
firewalling.servicemultihoming.servicett-rss.servicecyborghood_postman.service
As for the rest, Buster is coming soon, so I think we can reevaluate after migration.
Updated by Marc Dequènes over 5 years ago
- Status changed from In Progress to Resolved
- Assignee changed from DC Admins to Marc Dequènes
- % Done changed from 40 to 100
Updated by Marc Dequènes over 5 years ago
- Blocks Enhancement #648: Debian Buster Migration added