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
To check, I put KDC IP address in krb5.conf. Yet, the issue persisted,
suggesting this does not have to do with name resolution not being
available early on in the boot process.
Youssef Eldakar
Bibliotheca Alexandrina
I am experiencing the same issue.
I thought that implementing the init as systemd units could be the
solution. I attempted the following, but nslcd-kstart.service so far fails
to start during the boot process, starts successfully when invoked manually
after the system is up:
#
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
4 matches
Mail list logo