Am 22.09.19 um 16:46 schrieb Michael Biebl: > Am 22.09.19 um 16:29 schrieb Marc Haber: >> On Sun, Sep 22, 2019 at 04:12:43PM +0200, Michael Biebl wrote: >>> Since systemd-time-wait-sync.service doesn't seem to really work with >>> alternative implementations, I wonder if it wouldn't be better to err on >>> the safe safe and do the following: >>> - Rename it systemd-timesyncd-wait-time-sync.service >>> - Add Requires=systemd-timesyncd.service to >>> systemd-timesyncd-wait-time-sync.service >>> - Update the documentation and remove the section which says that it >>> sort-of supports alternative implementations as fallback. >> >> Maybe the same heuristics that prevent systemd-timesyncd from starting >> on such systems can be used. > > In case you are referring to the > /lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf > hack, which is Debian specific: > > That would be unnecessary to duplicate if we add the Requires=
Requires=systemd-timesyncd.service + After=systemd-timesyncd.service to be precise. I now also tested a buster VM and can't seem to get systemd-timesyncd-wait-time-sync work with neither chrony nor ntp. It did work with systemd-timesyncd (took about 20secs until time-sync.target was reached). It was a default default buster VM with a 4.19 kernel My previous test was under unstable with kernel 5.2 and systemd v243 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
