On 11/15/2017 12:33 AM, Guillaume Courtois wrote:
https://www.freedesktop.org/software/systemd/man/systemd.service.html
from example 1
"Since no ExecStop= was specified, systemd will send SIGTERM
to all processes started from this service, and after
a timeout also SIGKILL. This behavior can be modified, see
systemd.kill(5) for details."
I couldn't find anyuthing on ExecReload
That seems normal, if no stop action is given, systemd will kill
remaining processes.
All init scripts do the same.
I got this back from Ask Fedora:
$ sudo systemctl reload bluetooth
Failed to reload bluetooth.service: Job type reload is not applicable
for unit bluetooth.service.
See system logs and 'systemctl status bluetooth.service' for details.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Computers are like air conditioners.
They malfunction when you open windows
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
--
sane-devel mailing list: sane-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/sane-devel
Unsubscribe: Send mail with subject "unsubscribe your_password"
to sane-devel-requ...@lists.alioth.debian.org
