On Tue, Feb 05, 2013 at 11:50:20AM -0600, ray vantassle wrote:
> It's easy to duplicate.
> ntpdate starts up this way:
> NTPSERVERS="0.debian.pool.ntp.org 1.debian.pool.ntp.org
> 2.debian.pool.ntp.org 3.debian.pool.ntp.org"
> /usr/sbin/ntpdate $NTPSERVERS
>
> It makes 4 queries to each of 16
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
You could just start chrony earlier and as you say, tell it to do a makestep
if the time is way off. I can certainly see why chrony gets totally confused
if it thinks that the clock rate is out by over 90 PPM. Perhaps it should
just exit at that point. It is not clear what a reasonable
> 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
On Sun, 3 Feb 2013, ray vantassle wrote:
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.
So why are you using ntpdate?
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.
