[systemd-devel] not running ExecStop= when stopping "activating" services?
Nekrasov, Alexander
alexander.nekrasov at emc.com
Thu Mar 19 12:08:39 PDT 2015
Hi All,
With these settings
[Service]
ExecStart=/cli run
ExecStop=/cli stop
Type=forking
PIDFile=/tmp/cli.pid
The service is active once "cli run" exits. A call to systemctl stop then produces a call to "cli stop". This is as expected.
However if I call "systemctl stop" on this service before "cli run" exited, i.e., when the service is still activating, the service is stopped, all threads are killed off, but "cli stop" is never run.
Is that as intended? Why? Is there a way to change this behavior?
systemd-210-34.9.x86_64
systemd-bash-completion-210-34.9.noarch
systemd-rpm-macros-2-7.2.noarch
util-linux-systemd-2.25-2.2.x86_64
systemd-32bit-210-34.9.x86_64
systemd-sysvinit-210-34.9.x86_64
systemd-presets-branding-SLE-12.0-12.1.noarch
Thanks,
Alex
More information about the systemd-devel
mailing list