[systemd-devel] customized shutdown service needed

Lennart Poettering lennart at poettering.net
Wed Feb 29 08:16:04 PST 2012

On Sun, 26.02.12 19:13, Reindl Harald (h.reindl at thelounge.net) wrote:

> the ExecStop is called but systemd DOES NOT wait
> until it is finished leading to all virtual machines
> are killed hard while "systemctl stop vmware-default.service"
> does supsend them perfectlly as long it is not combined with
> any sort of shutdown

systemd waits for ExecStop= to finish before executing later jobs (well,
subject to a timeout, of a couple of minutes).

What really matters is that you order your service before/after the
right things, and be aware that:

a) the stop order is implicitly the reverse of the start order

b) if a job is started and another one stopped and they are ordered
against each other, then the stop is executed first, and the start
executed second, regardless which kind of ordering is actually


Lennart Poettering - Red Hat, Inc.

More information about the systemd-devel mailing list