[Bug 942043] [NEW] Ubuntu does not shutdown properly due to wrong symlinks in runlevel 0 and 6

[Metabaronen]

Public bug reported:

Description:	Ubuntu 10.04.3 LTS
Release:	10.04

initscripts: 2.87dsf-4ubuntu17.5

I expect my system to kill all processes, umount all volumes gracefully
or forcefully.

By default the symlinks for umountfs, umountroot, sendsigs, reboot and
umountnfs.sh are created as S-links (start) but the scripts only handles
the stop option. The scripts should be installed as K-scripts or
disabled in case upstart should handle these.

Note: upstart doesn't handle stale processes before running it's umount
-a in mountall-shell.conf so any left process will cause a blocked
umount and an unclean file system and a fsck on boot.

A workaround is to manually change the boot order.

** Affects: sysvinit (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to sysvinit in Ubuntu.
https://bugs.launchpad.net/bugs/942043

Title:
  Ubuntu does not shutdown properly due to wrong symlinks in runlevel 0
  and 6

Status in “sysvinit” package in Ubuntu:
  New

Bug description:
  Description:	Ubuntu 10.04.3 LTS
  Release:	10.04

  initscripts: 2.87dsf-4ubuntu17.5

  I expect my system to kill all processes, umount all volumes
  gracefully or forcefully.

  By default the symlinks for umountfs, umountroot, sendsigs, reboot and
  umountnfs.sh are created as S-links (start) but the scripts only
  handles the stop option. The scripts should be installed as K-scripts
  or disabled in case upstart should handle these.

  Note: upstart doesn't handle stale processes before running it's
  umount -a in mountall-shell.conf so any left process will cause a
  blocked umount and an unclean file system and a fsck on boot.

  A workaround is to manually change the boot order.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sysvinit/+bug/942043/+subscriptions