I think I will try the mentioned work-a-round. In fact, many services do the same:
# grep "stop on runlevel \[!2345\]" /etc/init/* acpid.conf:stop on runlevel [!2345] anacron.conf:stop on runlevel [!2345] apport.conf:stop on runlevel [!2345] atd.conf:stop on runlevel [!2345] console.conf:stop on runlevel [!2345] cron.conf:stop on runlevel [!2345] irqbalance.conf:stop on runlevel [!2345] nmbd.conf:stop on runlevel [!2345] smbd.conf:stop on runlevel [!2345] ssh.conf:stop on runlevel [!2345] tty1.conf:stop on runlevel [!2345] upstart-socket-bridge.conf:stop on runlevel [!2345] whoopsie.conf:stop on runlevel [!2345] -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to powernap in Ubuntu. https://bugs.launchpad.net/bugs/872109 Title: powernap 2.15-0ubuntu2 causes unclean rootfs unmount To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powernap/+bug/872109/+subscriptions -- Ubuntu-server-bugs mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
