This page on the systemd wiki sheds light on the issue: https://www.freedesktop.org/wiki/Software/systemd/NetworkTarget/
According to the page, ideally, the ticket refresh (k5start) should be implemented such that it is able to react in a friendly way to network changes. I take this as implying that nslcd should start without depending on Kerberos ticket initialization and instead attempt to obtain credentials on demand. As temporary workaround, I installed the following in cron.d: */3 * * * * root if [ \( ! -e /var/run/nslcd/k5start_nslcd.pid -o ! -e /var/run/nslcd/nslcd.pid \) -a -f /etc/libnss-ldap.keytab -a -r /etc/libnss-ldap.keytab ]; then systemctl restart nslcd; fi On Mon, Feb 1, 2016 at 5:25 PM, Youssef Eldakar <[email protected]> wrote: > It is silly, but if I add > > RestartSec=2s > > to both unit files, nslcd is successful during the boot process. > > This does not feel like a real fix, however. > > Youssef Eldakar > Bibliotheca Alexandrina
