Description of problem: Kerberos systemd start (e.g. /usr/lib/systemd/system/krb5kdc.service && co.) should WAIT until the KDC is really running. Currently in scenarios like a very slow system (e.g. boot via dracut over an overloaded network connection) there are cases where the KDC comes up so late that clients can't get their tickets. Suggested fix: KDC systemd script should explicitly wait for the KDC to enter the |poll()|/|epoll()| state.
Created attachment 951803 [details] Sample script which waits for the KDC to become ready Sample script which shows (in function kdc_t.run_kdc) how to wait for the KDC to become ready (waiting for the PID file doesn't work so we have to do it the hard way... ☹).
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
I'm not seeing the use case. If someone wants to make a case for this, please reopen and we can consider it.