reassign 541349 autofs retitle 541349 autofs: Incorrect init.d dependency info make script start to early found 541349 4.1.4+debian-2.1 user initscripts-ng-de...@lists.alioth.debian.org usertag 541349 + incorrect-dependency thanks
[Andrew Chittenden] > autofs should start after nis but autofs is being started with level > 01 whereas nis is being started with level 17: The dependency information provided by the autofs init.d script currently look like this in version 4.1.4+debian-2.1: ### BEGIN INIT INFO # Provides: autofs # Required-Start: $local_fs # Required-Stop: $local_fs # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: automount daemon # Description: daemon to mount (possibly remote) filesystems # automatically upon entering the mountpoint ### END INIT INFO If autofs need to start after nis, it should list nis in its Required-Start header. Thank you for bringing this to our attention. The bug need to be fixed in autofs. Debian unstable switched to dependency based boot sequencing recently, and the packages failing to specify correct dependency information in their init.d scripts need to be fixed. As far as I know, most scripts in the 850 packages with init.d scripts have correct dependency information already. Reassigning this bug to autofs. If you are aware of other scripts with incorrect dependency information (I see you mention several, but it is not obvious to me that these have wrong dependency information), please report them as bugs too. I am aware of openvpn (#539764) already being reported. I'll have a look at binfmt-support, edac, fancontrol, mercury-base, nvidia-glx, nvidia-kernel, snmpd, sysklogd, syslog-ng, uml-utilities and winbind to see if these are buggy too. I suspect most of these are just fine starting without a running syslog collector. Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
