Project

General

Profile

Actions

Bug #595

closed

Create missing systemd configuration for SYSV compatibility services

Added by Marc Dequènes about 7 years ago. Updated over 5 years ago.

Status:
Resolved
Priority:
High
Category:
System :: Base
Start date:
2017-09-23
Due date:
% Done:

100%

Estimated time:
Patch Available:
Confirmed:
No
Branch:
Entity:
DuckCorp
Security:
Help Needed:

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.


Related issues 3 (0 open3 closed)

Related to DuckCorp Infrastructure - Bug #605: No mail since 2017-10-15 07:00:02RejectedPierre-Louis Bonicoli2017-10-16

Actions
Related to DuckCorp Infrastructure - Bug #606: Bip service unavailable since Oct 15 (Thorfinn)ResolvedPierre-Louis Bonicoli2017-10-23

Actions
Blocks DuckCorp Infrastructure - Enhancement #648: Debian Buster MigrationResolvedMarc Dequènes2019-04-21

Actions
Actions

Also available in: Atom PDF