Package: insserv Version: 1.12.0-10 Severity: critical Justification: breaks unrelated software
autofs should start after nis but autofs is being started with level 01 whereas nis is being started with level 17: # ls /etc/rc*d/*nis /etc/rc1.d/K01nis@ /etc/rc3.d/S17nis@ /etc/rc5.d/S17nis@ /etc/rc2.d/S17nis@ /etc/rc4.d/S17nis@ # ls /etc/rc*d/*autofs /etc/rc0.d/K01autofs@ /etc/rc3.d/S01autofs@ /etc/rc6.d/K01autofs@ /etc/rc1.d/K01autofs@ /etc/rc4.d/S01autofs@ /etc/rc2.d/S01autofs@ /etc/rc5.d/S01autofs@ This makes autofs unusable. It looks like a lot of startup scripts are also being run at level 01: /etc/rc1.d/S01killprocs@ /etc/rc4.d/S01binfmt-support@ /etc/rc2.d/S01autofs@ /etc/rc4.d/S01edac@ /etc/rc2.d/S01binfmt-support@ /etc/rc4.d/S01fancontrol@ /etc/rc2.d/S01edac@ /etc/rc4.d/S01mercury-base@ /etc/rc2.d/S01fancontrol@ /etc/rc4.d/S01nvidia-glx@ /etc/rc2.d/S01mercury-base@ /etc/rc4.d/S01nvidia-kernel@ /etc/rc2.d/S01nvidia-glx@ /etc/rc4.d/S01openvpn@ /etc/rc2.d/S01nvidia-kernel@ /etc/rc4.d/S01snmpd@ /etc/rc2.d/S01openvpn@ /etc/rc4.d/S01sysklogd@ /etc/rc2.d/S01snmpd@ /etc/rc4.d/S01syslog-ng@ /etc/rc2.d/S01sysklogd@ /etc/rc4.d/S01uml-utilities@ /etc/rc2.d/S01syslog-ng@ /etc/rc4.d/S01winbind@ /etc/rc2.d/S01uml-utilities@ /etc/rc5.d/S01autofs@ /etc/rc2.d/S01winbind@ /etc/rc5.d/S01binfmt-support@ /etc/rc3.d/S01autofs@ /etc/rc5.d/S01edac@ /etc/rc3.d/S01binfmt-support@ /etc/rc5.d/S01fancontrol@ /etc/rc3.d/S01edac@ /etc/rc5.d/S01mercury-base@ /etc/rc3.d/S01fancontrol@ /etc/rc5.d/S01nvidia-glx@ /etc/rc3.d/S01mercury-base@ /etc/rc5.d/S01nvidia-kernel@ /etc/rc3.d/S01nvidia-glx@ /etc/rc5.d/S01openvpn@ /etc/rc3.d/S01nvidia-kernel@ /etc/rc5.d/S01snmpd@ /etc/rc3.d/S01openvpn@ /etc/rc5.d/S01sysklogd@ /etc/rc3.d/S01snmpd@ /etc/rc5.d/S01syslog-ng@ /etc/rc3.d/S01sysklogd@ /etc/rc5.d/S01uml-utilities@ /etc/rc3.d/S01syslog-ng@ /etc/rc5.d/S01winbind@ /etc/rc3.d/S01uml-utilities@ /etc/rcS.d/S01hostname.sh@ /etc/rc3.d/S01winbind@ /etc/rcS.d/S01mountkernfs.sh@ /etc/rc4.d/S01autofs@ so I expect some of them to be broken too (on other systems without insserv installed, there's very few level 01 scripts). On a different system, I managed to dpkg-reconfigure insserv and disabled it. That resets the autofs level to 19. However, it left the system needing its filesystems checking manually on next boot. Having done that, the system is now unable to boot: I'm guessing that the scripts' order hasn't been restored properly. -- System Information: Debian Release: squeeze/sid APT prefers transitional APT policy: (500, 'transitional'), (500, 'oldstable'), (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.30-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages insserv depends on: ii debconf [debconf-2.0] 1.5.27 Debian configuration management sy ii initscripts 2.87dsf-2 scripts for initializing and shutt ii libc6 2.9-23 GNU C Library: Shared libraries ii sysv-rc 2.87dsf-2 System-V-like runlevel change mech ii sysvinit-utils 2.87dsf-2 System-V-like utilities insserv recommends no packages. Versions of packages insserv suggests: pn bootchart <none> (no description available) -- debconf information: insserv/enable: true -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
