Petter Reinholdtsen <[email protected]> writes: > [Russ Allbery] >> Although I suppose they might be able to make use of the overrides >> directory instead. I'm not sure how that works or if packages are >> allowed to install overrides for themselves.
> One way to do this would be to add a file like this to put krb5-kdc > behind slapd during boot: > r...@tjener:~# cat /etc/insserv/overrides/krb5-kdc > ### BEGIN INIT INFO > # Provides: krb5-kdc > # Required-Start: $local_fs $remote_fs $network $syslog > # Required-Stop: $local_fs $remote_fs $network $syslog > # Should-Start: slapd > # Should-Stop: slapd > # Default-Start: 2 3 4 5 > # Default-Stop: 0 1 6 > ### END INIT INFO > r...@tjener:~# Right, but the problem is that if you don't have the KDC database in LDAP, one wants the opposite ordering. In that case, the KDC should start before slapd, since slapd may be using Kerberos for authentication (to slaves, for instance). The ordering has to change based on what the LDAP server is used for, or the KDC needs to be more robust against not being able to connect during startup. > The /usr/share/insserv/overrides/ directory can not be used, as its > override files only take effect if the /etc/init.d/krb5-kdc script is > missing headers, which it is not. > Perhaps the /etc/insserv/overrides/krb5-kdc file should be part of the > krb5-kdc-ldap package? Yeah, that would work. > I do not see a reason why a package should not be allowed to create an > override file if it want to. :) So /etc/insserv/overrides *can* be used, just not /usr/share/insserv/overrides? -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
