Received: by 10.180.97.162 with SMTP id eb2mr915790wib.0.1351624906853;
        Tue, 30 Oct 2012 12:21:46 -0700 (PDT)
Path: q13ni108550wii.0!nntp.google.com!proxad.net!feeder1-2.proxad.net!news.mixmin.net!eternal-september.org!feeder.eternal-september.org!mx04.eternal-september.org!.POSTED!not-for-mail
From: David Taylor <david-tay...@blueyonder.co.uk.invalid>
Newsgroups: comp.protocols.time.ntp
Subject: Re: What is the NTP recovery time from 16s step in GPS server?
Date: Tue, 30 Oct 2012 19:21:46 +0000
Organization: A noiseless patient Spider
Lines: 25
Message-ID: <k6p9ca$qh6$1@dont-email.me>
References: <k6p3v2$h2p$1@dont-email.me> <k6p4fd$k40$1@dont-email.me>
Reply-To: david-tay...@blueyonder.co.uk
Mime-Version: 1.0
Injection-Date: Tue, 30 Oct 2012 19:21:46 +0000 (UTC)
Injection-Info: mx04.eternal-september.org; posting-host="ec31590fbbc62faa9d891a3130cd48b3";
	logging-data="27174"; mail-complaints-to="ab...@eternal-september.org";	posting-account="U2FsdGVkX1+XA51B+RUj7oqFzqOipqJLzHpu0NZ3P0w="
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
In-Reply-To: <k6p4fd$k40$1@dont-email.me>
Cancel-Lock: sha1:CfiDZTs8CUZieL9qfsMaYfL/5YA=
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 30/10/2012 17:57, David Woolley wrote:
> David Taylor wrote:
>
>>
>> However, suppose I had /only/ the GPS receiver?  NTP has the GPS time
>> and the PPS signal for the exact second, syncs, and then a few minutes
>> in the time suddenly changes by 16 seconds.  I would hope that then
>> causes NTP to step the clock onto UTC rather than GPS time.  I realise
>> that the time for the GPS receiver to be sending UTC rather than GPS
>> time varies, but how long might it then take NTP to react to the 16
>> second change, and alter the system clock?  Both the PPS and the gpsd
>> are being polled at fixed 16 second intervals.
>>
>
> It's not a specified characteristic, as it is a GIGO case.  However, I
> believe it it is the order of 20 minutes, with standard parameters. Most
> of this is for ntpd to convince itself that the local clock time it has
> really is wrong.

Thanks, David.  Do you think that it would still be 20 minutes when the 
clock in question is being polled every 16 seconds?
-- 
Cheers,
David
Web: http://www.satsignal.eu