[systemd-devel] shutdown: how to tell systemd to stop a service before killing other processes
Reindl Harald
h.reindl at thelounge.net
Sun Aug 25 22:48:32 UTC 2019
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Am 26.08.19 um 00:19 schrieb Hans-Dieter Doll:
> There are also interactive applications started as user sessions.
> Some of these must not be killed but terminated by the supervisor,
> otherwise we (i.e. our customers) run into trouble.
>
> With pre systemd linux this was not an issue, because the init
> scripts where called before anything else got killed. We thought
> systemd is backward compatible, but in this respect it is not.
> Thank you for clarifying. I only wanted to verify my understanding
> is right...
typically that issue is a sign of bad design and just worked by luck
with a simple init system lacking of concepts for service states
you should split your stuff into multiple systemd units and pack them
into a target instead wrap a dozen of more or less independent things
in a single unit
-----BEGIN PGP SIGNATURE-----
iQGzBAEBCAAdFiEEnStGzbwUCjZ1OuTXMxdNWliSt7gFAl1jEEAACgkQMxdNWliS
t7hRcAwAifga0wdt0YYgyeo0Zb30LoCGXHhdam18PPbC65LpvCeu/KkqncOvFTVM
gI4+u+uUkCZ4lvnuN/W4RG4/Jp4LlEchF8eKT2aI9kwMIZOHti30AaOBuG8QidKw
y7MtKeOZHZ9XIy39IxlUe9VrfszMnRU67sn/6GrNSN3q9eKxJl8mrnWjWdKQ2+qt
KKRsP240hnb3vscyI11yxxupGWmA5DWiVoJFqgyfpyEW8yExCPfndGk/GBeMZXHO
L5noJlpnmUS88VzZt8GH9pGAkMOSzltcfsexl/B1/nUkD/c42kwj7qqJV+fs7yh4
Fk45nxmbc1Qhe8DFknY3Tnt4Etj11ffNcbc9zkflfCAtCMhaTpo1l46cA8mVygQY
9rvYAgkz/ly9rsQ5ktwsr1O7ttbg2nX9+JpFCGrwRmH5zDq0XnV8G9jp0OfPi0jC
AdxlEZ2ekrjHMhZrg648vqIbnNItYTYqBaAkaCIQeuxBLI78WSrPAF8MCWfCXXUr
C70YA+QS
=Xtby
-----END PGP SIGNATURE-----
More information about the systemd-devel
mailing list