<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Reload of systemd makes it restart service that was stopping\"
href="https://bugs.freedesktop.org/show_bug.cgi?id=69800#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - Reload of systemd makes it restart service that was stopping\"
href="https://bugs.freedesktop.org/show_bug.cgi?id=69800">bug 69800</a>
from <span class="vcard"><a class="email" href="mailto:sylviabz1@cryogenic.net" title="Sylvia Else <sylviabz1@cryogenic.net>"> <span class="fn">Sylvia Else</span></a>
</span></b>
<pre>If a systemctl stop foo command has been given, but the foo service has not yet
stopped, and then the systemctl --system daemon-reload is given, then when the
foo service eventually stops, systemd will restart it, when clearly it should
not.
I speculate that the particular bit of state consisting of the fact that the
service is being stopped gets lost in the process of serialization and
deserialization.
Since it appears that a reload also occurs for systemctl disable foo, this
makes it a particular gotcha for a service that is seeking to stop and disable
itself.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>