[ntp:questions] Re: New to NTPD

Brian Inglis Brian.Inglis at SystematicSW.Invalid
Wed May 10 05:32:42 UTC 2006


On Tue, 09 May 2006 22:49:25 GMT in comp.protocols.time.ntp, Ted
Gervais <ve1drg at av.eastlink.ca> wrote:

>On Tue, 9 May 2006, Brian Inglis wrote:
>
>> On Tue, 09 May 2006 15:41:45 GMT in comp.protocols.time.ntp, Ted
>> Gervais <ve1drg at av.eastlink.ca> wrote:
>>
>>> On Tue, 9 May 2006, Heiko Gerstung wrote:
>>>
>>>> Hi, Ted:
>>>>
>>>> Ted Gervais wrote:
>>>>> Well I finally am moving away from netdate and have ntpd installed and
>>>>> running.
>>>>> I brought it up using ntpd -g,  and hope that is ok.
>>>>>
>>>>> Also I have no idea that it is doing anthing?   How do I know that it is
>>>>> running.
>>>>> The drift file has only one entry in it, and that is all zeros..
>>>>>
>>>>> Is there some way that I can watch what is happening like the way I watch
>>>>> log files using 'tail -f messages'  ??
>>>>>
>>>>> I have all the logfile stuff turned on so I can read any and all stuff that
>>>>> is happening and  yet while that says a few things I at this point don't
>>>>> know that it is doing anything with the system time.
>>>>>
>>>>> I am running linux (slackware 10.2)..
>>>>
>>>> Maybe you can try it with "ntpq -p" which shows you all configured time
>>>> references (the "server" or "peer" lines in /etc/ntp.conf). If you want,
>>>> you can run it periodically : "watch -n 1 ntpq -p"
>>>
>>> OK on the 'watch' line. Here is what that gives me"
>>>
>>> Every 1.0s: ntpq -p                                     Tue May  9
>>> 12:39:45 2006
>>>      remote           refid      st t when poll reach   delay   offset
>>> jitter
>>> ==============================================================================
>>> *LOCAL(0)        73.78.73.84      5 l   58   64  377    0.000    0.000
>>> 0.001
>>>  time-b.nist.gov .RSTR.          16 u    -   64    0    0.000    0.000
>>> 4000.00
>>>  time-b.nist.gov .RSTR.          16 u    -   64    0    0.000    0.000
>>> 4000.00
>>>  time-A.timefreq .RSTR.          16 u    -   64    0    0.000    0.000
>>> 4000.00
>>>  time.nist.gov   .RSTR.          16 u    -  128    0    0.000    0.000
>>> 4000.00
>>
>> Use the Canadian pool servers as in http://www.pool.ntp.org/zone/ca
>>
>> "Canada - ca.pool.ntp.org
>>
>> There are 24 active servers in this zone.
>>
>> We can use more servers in this country. If you have a server with a
>> static IP, please consider joining the pool!
>>
>> To use this pool zone, add the following to your ntp.conf file:
>>
>>   server 0.ca.pool.ntp.org
>>   server 1.ca.pool.ntp.org
>>   server 2.ca.pool.ntp.org"
>>
>> OR these public servers:
>>
>> 	ntp1.cmc.ec.gc.ca
>> 	ntp2.cmc.ec.gc.ca
>> 	time.nrc.ca
>> 	time.chu.nrc.ca
>> 	timelord.uregina.ca
>>
>Now - what I have in place right now shows some improvement but I wonder 
>if it is right yet.  Here is what ntpq -p gives me:
>--------------
>Every 1.0s: ntpq -p                                     Tue May  9 
>19:42:06 2006
>      remote           refid      st t when poll reach   delay   offset 
>jitter
>==============================================================================
>+clock.via.net   .GPS.            1 u  223  256  377  101.718   21.183 
>5.465
>  gnomon.cc.colum .USNO.           1 u  483 1024  301   55.229   26.100 
>2.439
>-NAVOBS1.MIT.EDU .PSC.            1 u   11  256  377   60.820   28.740 
>2.602
>+ntp3.usv.ro     .PPS.            1 u   15  256  377  173.654   26.977 
>1.469
>*clock.xmission. .GPS.            1 u  216  256  377   88.717   23.674 
>4.681
>+c-24-130-58-99. .GPS.            1 u   83  256  377  118.072   23.165 
>1.358
>
>-------------------------
>
>How does this look?  I think it actually is working now?? Anyone, please
>let me know.

Looks good: synced to clock.xmission..., but reachability problems to
?gnomon.cc.colombia.edu and longish delays to clock.via.net (and high
jitter), ntp3.usv.ro, and c-24... so you might want to drop those, add
in some Canadian servers, and see what things look like the next day. 
Your goal should be to sync to four reliable local stratum 2 servers. 
Ask your ISP about reliable local NTP servers, and try to get in touch
with someone at Dalhousie about access to noc.dal.ca. 

-- 
Thanks. Take care, Brian Inglis 	Calgary, Alberta, Canada

Brian.Inglis at CSi.com 	(Brian[dot]Inglis{at}SystematicSW[dot]ab[dot]ca)
    fake address		use address above to reply




More information about the questions mailing list