When kadmind tells kpropd that it needs a full resync kpropd then
asks for the resync then sets up the listener.  This can be racy,
particularly if we should make kadmind share a single global iprop
dumps for full resyncs.  The whole thing looks very brittle, so a
redesign of how kpropd handles full resyncs seems to be in order

E.g., https://github.com/nicowilliams/krb5/commit/7e2cfd5c10918e286cfa4dc85dcffd0f75f9cb67