Comment 3 for bug 1349566

On Mon, Jul 28, 2014 at 3:46 PM, Steve Langasek
<email address hidden> wrote:
> Dann, what upstart services fail to be shut down? The last messages
> shown in your log are from /etc/init.d/sendsigs and /etc/init.d/reboot,
> which on an upstart system are only ever called via /etc/init/rc.conf,
> systemd notwithstanding.

When shutting down by running 'poweroff', I see:

ubuntu@ubuntu:~$ sudo poweroff

Broadcast message from ubuntu@ubuntu
    (/dev/ttyS0) at 18:02 ...

The system is going down for power off NOW!
ubuntu@ubuntu:~$wait-for-state stop/waiting
 * Stopping rsync daemon rsync [ OK ]
 * Asking all remaining processes to terminate... [ OK ]
 * All processes ended within 1 seconds... [ OK ]
 * Deactivating swap... [ OK ]
 * Unmounting local filesystems... [ OK ]
 * Will now halt
[ 46.799956] reboot: Power down

When shutting down via the power button, I see:

ubuntu login: wait-for-state stop/waiting
 * Stopping rsync daemon rsync [ OK ]
 * Asking all remaining processes to terminate... [ OK ]
[ 54.199961] reboot: Power down

So on this system with a minimal install, I'm failing to see evidence
of it deactivating swap or umounting local filesystems.

I should be clear that my bug title is speculation - I saw rsync being
shutdown which I know ships a sysvinit script, but that it missed
doing some other "normal" things that upstart does on shutdown. I
guessed that systemd was triggering shutdown in a manner that only
tickled the sysvinit compat code - but perhaps this is another pid
matching bug in sendsigs or something.

 -dann