Sujet : Re: systemd controversy
De : ldo (at) *nospam* nz.invalid (Lawrence D'Oliveiro)
Groupes : comp.lang.adaDate : 21. Mar 2024, 01:01:43
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <utfpsn$1ol4n$9@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10
User-Agent : Pan/0.155 (Kherson; fc5a80b8)
On Wed, 20 Mar 2024 09:56:18 -0000 (UTC), Kevin Chadwick wrote:
I'm skeptical of the flexibility being lost.
systemd service definitions let you state dependencies between services.
Furthermore, it separates them into ordering dependencies versus
requirement dependencies.
E.g. an application that uses a MariaDB database requires MariaDB to be
running before it can be started (ordering + requirement dependency).
An application that can (but doesn’t have to) make use of network services
should be started after the network stack is up (ordering dependency).
I’m not aware of any other service-management system that provides this
level of control.
SysV init scripts are quite horrid but OpenBSDs rc system is far more
transparent, flexible and nicer to work with than systemd.
Does it have the equivalent of cgroups? These are a Linux feature (also
used by OpenRC) to ensure that, no matter how service processes may fork/
exec/terminate, the service manager can always track them down.