Bug 90427

Summary:	systemctl reload PATTERN reloads disabled units
Product:	systemd	Reporter:	Chris Severance <lo.severach>
Component:	general	Assignee:	systemd-bugs
Status:	RESOLVED INVALID	QA Contact:	systemd-bugs
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Chris Severance 2015-05-12 19:16:51 UTC

systemctl enable faxgetty@ttyUSB0.service
systemctl enable faxgetty@ttyUSB1.service

systemctl -l list-units "faxgetty@*.service"
#We see both services. ttyUSB1 was a mistake so we disable it.

systemctl disable faxgetty@ttyUSB1.service

systemctl -l list-units "faxgetty@*.service"
#We still see both services. I can't see any difference from being disabled.

cd /etc/systemd/system/multi-user.target.wants;ls faxgetty*
#faxgetty@ttyUSB0.service
# Clearly only one service is enabled

systemctl reload "faxgetty@*.service"
#Both services are loaded. Why does reload load a disabled service? If disable isn't good enough, how do I get ttyUSB1 out of the list that reload faxgetty*.service wants to reload?

Comment 1 Lennart Poettering 2015-05-13 13:07:03 UTC

"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

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.