[ntp:questions] Re: Deprecating ntpdate

Richard B. Gilbert rgilbert88 at comcast.net
Fri Jul 8 22:55:25 UTC 2005


Danny Mayer wrote:

> Steve Kostecke wrote:
>
>> Johan Swenker said:
>>
>>
>>> On Fri, 08 Jul 2005 11:20:59 +0200, Maarten Wiltink wrote:
>>>
>>>
>>>> "Martin Burnicki" <martin.burnicki at meinberg.de> wrote in message
>>>> news:n8q1q2-uio.ln1 at gateway.py.meinberg.de...
>>>>
>>>>
>>>>> What I really appreciate with ntpdate is that I can run "ntpdate -q
>>>>> <host>" just to check quickly if a specific NTP server or client is
>>>>> up and running, and which time offset it observes.
>>>>>
>>>>> This can be done although ntpd is already running on my system,
>>>>> keeping my system time synchronized. I'm not sure whether this can
>>>>> be achieved with ntpd.
>>>>
>>>>
>>>> I'm not sure I'd want to use ntpd for that. ntpq -p is what I do.
>>>
>>>
>>> Unfortunately ntpq -p gives historical data on servers which are
>>> configured to be used by ntpd.
>>
>>
>>
>> ntpq -p [hostname] provides the current observed offset between an ntpd
>> and it's time sources.
>>
>> ntpq -crv [hostname] provides the current ntpd variables, including the
>> current offset from the syspeer.
>>
>> Both invocations may be used to test if an arbitrary ntpd is up and
>> running as long as queries have not been blocked.
>>
>
> Steve, he's using ntpdate to track down a time-loss issue on his 
> system. He needs an accurate current time so that he can see where in 
> his script he's losing time. It's the first intelligent use I've seen 
> of ntpdate.
>
> Danny
> _______________________________________________
> questions mailing list
> questions at lists.ntp.isc.org
> https://lists.ntp.isc.org/mailman/listinfo/questions
>
Wouldn't ntpq -p do the same thing?  If the offsets from all the servers 
have gone -40ms between two invocations, what happened between the two 
did the dirty deed!




More information about the questions mailing list