On Tue, 5 Feb 2013, ray vantassle wrote:
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
> 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
On Mon, Feb 04, 2013 at 10:49:45PM -0600, ray vantassle wrote:
> > This reading from chrony.drift is absurd. Where did it come from?
>
> Um, no RTC. Also, ntpdate and chronyd are stepping on one another at
> startup. I think that the timing is such that chronyd is in the midst
> of conditioning
