Package: libnss-ldapd Version: 0.6.1 Severity: important Tags: patch User: [EMAIL PROTECTED] Usertags: incorrect-dependency
When using libnss-ldapd and slapd on a machine with dependency based boot sequencing enabled, the boot script order is wrong. This is the default setting in Debian Edu. The nslcd init.d script should start after slapd, but it does not. The solution is to add a soft dependency in nslcd. This patch solve the problem: Index: debian/libnss-ldapd.nslcd.init =================================================================== --- debian/libnss-ldapd.nslcd.init (revision 715) +++ debian/libnss-ldapd.nslcd.init (working copy) @@ -23,8 +23,8 @@ # Provides: nslcd # Required-Start: $local_fs $syslog # Required-Stop: $local_fs $syslog -# Should-Start: $remote_fs $network -# Should-Stop: $remote_fs +# Should-Start: $remote_fs $network slapd +# Should-Stop: $remote_fs slapd # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: nss-ldapd connection daemon You can probably drop the redundant dependency on $network (already a dependency of $remote_fs) and replace $local_fs with $remote_fs as a hard dependency. These would be equivalent and make the dependency list shorter. To be exact, you could make it like this: # Required-Start: $remote_fs $syslog # Required-Stop: $remote_fs $syslog # Should-Start: slapd # Should-Stop: slapd Happy hacking, -- Petter Reinholdtsen -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]