Comment # 45 on bug 1145193 from Thorsten Kukuk

(In reply to Reinhard Max from comment #44)
> Thorsten, could you please provide a list of services that use certs and
> might get into trouble when chrony-wait.service is not enabled, so that we
> can investigate if they really need the sub-second clock precision of
> time-sync.target or if time-set.target would be good enough for them?

I don't have such a list, only look at the services which depend on it. Most of
them are systemd units for timers, and if you look at the mailing lists and the
complains about timer running to early (especially on notebooks, who wonders
why?), it should be pretty clear who needs them why.

According to the systemd documentation, time-set.target depends on a correct
working hardware clock. But we know from the other bug reports and this report,
that we cannot trust the hardware clock. So time-set.target is in my opinion no
solution at all.
Some of the services I'm aware of need a one our precision, and a wrong
hardware clock does not provide this.