On Sun, 26.02.12 19:13, Reindl Harald (h.rei...@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 configured. Lennart -- Lennart Poettering - Red Hat, Inc. _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
