Comment 6 for bug 603363

I was able to reproduce this by installing with the minimal ISO in a VM with a separate /usr partition, then installing openssh-server, then halting the machine.

This caused errors to be printed out because /usr had files open. The system simply remounted /usr readonly and rebooted, which in effect caused the fs to be clean so the fsck was normal. Still, this seems to be improper behavior and ssh-server should be stopped when the system is rebooting/halting.

I don't quite understand why /etc/init/ssh.conf has 'stop on runlevel S'. Does this runlevel ever occur after normal system bootup?