On Thu, 2018-05-10 at 10:41 -0700, Russ Allbery wrote: > It means that the configured timeout for which it's reasonable to wait for > randomness is centralized in one service that can set that based on > understanding of what's necessary in practice, and timeouts to catch other > startup problems can remain in place for other services. Right now, to > have krb5-kdc wait for randomness requires extending the startup timeout > of the service as a whole, thus potentially not diagnosing various other > problems that might be preventing the KDC from starting unrelated to > randomness.
Would it also mean that the user would see messages like "Waiting for rng to be ready" instead of "Waiting for $someservice to be ready" in the boot logs? I think it would and, if so, that seems useful in its own right as well. Ian.
