> Weird. Maybe you should have chrony come up before then, which would block
> the port for ntpdate.
I just tested that. Ntpdate works just fine while chrony is running.
There is no "port to block". Ntpdate doesn't listen on any port, it
only establishes an outbound connection to a remote
> So why are you using ntpdate?
Installed automatically by the distro (debian).
This machine is a Pogoplug, which does not have a RTC. Neither does
my router, which runs Linux TomatoUSB. Neither does a Raspberry Pi.
On these low power computers, ntpd has a heavy footprint, so chrony is
a much
Debian system, without a RTC. So at bootup the time is zero.
At startup, 32 seconds into startup, /etc/network/if-up.d/ntpdate
invokes ntpdate-debian, which starts a ntpdate which takes about 14
seconds to finish.
Chronyd starts at about 37 seconds into startup, before the ntpdate is
done.
