Steven Malin <[email protected]> writes: > I use slapd as backend for kerberos and, although it is not recommended, > run both services on the same machine.
> However, with this setup the following problem arises: > When the machine boots, krb5-kdc gets started before slapd is ready and > therefore fails. > This can be solved by adding a dependency towards slapd in the init > script of krb5-kdc (see attached patch). > Since the usage of slapd is optional, a should dependency is sufficient. > Please contact me if there are any questions left. The problem with this patch is that an equally common configuration is to run a KDC and slapd on the same system but *not* use slapd as the database backend, and instead be using Kerberos for slapd replication. In that use case, adding this dependency will cause slapd startup to fail because the KDC is not ready yet. Either direction we go with this will break a different use case. The real long-term solution is to convert both services to use systemd socket activation. -- Russ Allbery ([email protected]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
