<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body><span class="vcard"><a class="email" href="mailto:lennart@poettering.net" title="Lennart Poettering <lennart@poettering.net>"> <span class="fn">Lennart Poettering</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - systemctl start should run "systemd daemon-reload" automatically"
href="https://bugs.freedesktop.org/show_bug.cgi?id=69096">bug 69096</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr>
<tr>
<td style="text-align:right;">Resolution</td>
<td>---
</td>
<td>WONTFIX
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - systemctl start should run "systemd daemon-reload" automatically"
href="https://bugs.freedesktop.org/show_bug.cgi?id=69096#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WONTFIX - systemctl start should run "systemd daemon-reload" automatically"
href="https://bugs.freedesktop.org/show_bug.cgi?id=69096">bug 69096</a>
from <span class="vcard"><a class="email" href="mailto:lennart@poettering.net" title="Lennart Poettering <lennart@poettering.net>"> <span class="fn">Lennart Poettering</span></a>
</span></b>
<pre>This has been requested before, but I still don't think this is a good idea.
(Similar requests using inotify to make all file changes instantaneous have
been made as well).
The problem is one of atomicity: installing something into systemd usually
consists of creating/editing not only one but multiple unit files, and creating
subdirectories as well as symlinks. Since doing these changes all in one atomic
step is not possible it is problematic doing reloads at arbitrary points in
time since systemd then might see some changes applied and others not. This can
result in various problems: for example services showing up multiple times or
not at all.
By making reloads explicit and controlled by the user we avoid the problem as
far as we can: as it is the admin who executed the operation at a point of time
of his choice we can be reasonably sure that the configuration is in a sane
state at that time.
"systemctl daemon-reload" is done implicitly by "systemctl enable" and
"systemctl disable" since the latter commands each execute one change
transaction anyway. However start/stop is something that is frequently done
implicitly in the background where the admin does not expect this, so we cannot
do this there.
Sorry.</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>