[Goswin von Brederlow] > Shouldn't cryptdisks-early have a unique boot sequence number on > shutdown too?
Not because of its interactive fag, as far as I know. The interactive flag only affect the boot, not the shutdown, and as far as I know that is by design. The shutdown should not be interactive. > Also I wonder why sendsigs is not listed there too. If that ever > runs in parallel with any other script then it will kill the other > script. That late in the shutdown sequence, I believe all scripts are already well-ordered, but if you find an example where that could happen, we should have a look and fix it. When every script in the archive is ordered, sendsigs get its own sequence number for both runlevel 0 and 6, so I do not believe it is likely to happen. This is the ordering for rc0.d at the moment: K07sendsigs K08rsyslog K09umountnfs.sh K10nfs-common K10portmap K11hwclock.sh K11networking K12atm K12ifupdown K13open-vm-tools K13shorewall-init K14umountfs K15cryptdisks K16lvm2 K17cryptdisks-early K18mdadm-raid K18umountroot K19live-boot K20halt See <URL: http://lintian.debian.org/~pere/ > for the daily updated logs. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
