[systemd-bugs] [Bug 90427] systemctl reload PATTERN reloads disabled units

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=90427

Lennart Poettering <lennart at poettering.net> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #1 from Lennart Poettering <lennart at poettering.net> ---
"reload" issues a reload command for the daemon itself, i.e. executes a
service's ExecReload= line.

Moreover "enabling" and "disabling" is about configuring whether services shall
be started on next boot, not about whether they are started/stopped right-away.
use "systemctl start" and "systemctl stop" for that.

"systemctl list-units" shows all units that are currently not stopped cleanly,
which means all units that are running, are being started, are being stopped,
or have failed. It is hence unaffected by "systemctl enable" and "systemctl
disable".

Note that this is a bug tracker, not a support forum. Please refer to the
systemd ML or downstream forums for support, but let's strictly focus on bugs
in this bug tracker. Thanks.

Also see:

http://0pointer.de/blog/projects/three-levels-of-off

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20150513/808ba54a/attachment-0001.html>