systemd does not shut down rsyslog

[msp3k]

This bug is 100% reproducible.

Example output:

Script started on Wed 09 Mar 2016 10:04:42 AM EST
root@flea:/etc/init.d# ps -ef | grep rsyslog
syslog 5219 1 0 10:04 ? 00:00:00 /usr/sbin/rsyslogd -n
root 5240 5227 0 10:04 pts/0 00:00:00 grep --color=auto
root@flea:/etc/init.d# systemctl stop rsyslog
Warning: Stopping rsyslog.service, but it can still be activated by:
  syslog.socket
root@flea:/etc/init.d# systemctl stop syslog
Warning: Stopping syslog.service, but it can still be activated by:
  syslog.socket
root@flea:/etc/init.d# systemctl stop rsyslogd
Failed to stop rsyslogd.service: Unit rsyslogd.service not loaded.
root@flea:/etc/init.d# ps -ef | grep rsyslog
syslog 5254 1 0 10:05 ? 00:00:00 /usr/sbin/rsyslogd -n
root 5263 5227 0 10:05 pts/0 00:00:00 grep --color=auto
root@flea:/etc/init.d# exit

Script done on Wed 09 Mar 2016 10:05:12 AM EST

[msp3k (peek-nimbios)]

This is on Ubuntu Server 16.04 beta

[msp3k (peek-nimbios)]

Nevermind. Apparently "systemctl stop <service>" doesn't do what I thought it should do. Rsyslogd can be stopped with:

systemctl disable rsyslog
systemctl stop rsyslog

After issuing the disable command, the stop command worked as I expected.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Mrten (bugzilla-ii)]

expected behaviour:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=815862#10