[ntp:questions] Re: Deprecating ntpdate

Steve Kostecke kostecke at ntp.isc.org
Fri Jul 8 21:26:34 UTC 2005


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 Kostecke <kostecke at ntp.isc.org>
NTP Public Services Project http://ntp.isc.org/
Public Key at http://ntp.isc.org/Users/SteveKostecke



More information about the questions mailing list