Hi Nicholas

thanks for the info. that seems to have fixed the problem, but wouldn't
that cause the time on the server to keep changing based on the offset
difference received from various time servers ?

Look at the offset that the time servers with whom my server peers shows
for my server:

ntpq -c peers
     remote           refid      st t when poll reach   delay   offset
jitter
==============================================================================
 LOCAL(0)        LOCAL(0)        13 l    4   64    1    0.000    0.000
 0.004
 time-A.timefreq .ACTS.           1 u    6   64    1   28.419    0.516
 0.004
 ntp1.tpgi.com.a ntp.sydney.nmi.  2 u   14   64    1  177.003    4.285
 0.004
 caesar.cs.wisc. ben.cs.wisc.edu  2 u    7   64    1   70.884    1.858
 0.004
 ourconcord.net  rubidium.broad.  2 u    7   64    1  113.295   -3.323
 0.004
 gabe.kjsl.com   usno.pa-x.dec.c  2 u    6   64    1   20.820    1.019
 0.004
 clock.via.net   .GPS.            1 u   10   64    1   22.607    0.273
 0.004
 c-24-130-58-99. .GPS.            1 u    2   64    1   42.421    0.728
 0.004
 clock.fmt.he.ne .GPS.            1 u    7   64    1   26.162   -0.013
 0.004
 c-66-229-200-20 .GPS.            1 u   12   64    1   39.343   -1.878
 0.004
 zorro.sf-bay.or clock.sjc.he.ne  2 u   13   64    1   21.971   -1.150
 0.004
 zoroaster.sf-ba navobs1.wustl.e  2 u    5   64    1  147.072   -0.461
 0.004

thanks
parag

Nicholas Suan said the following on 9/2/2006 4:36 PM:
> On 9/2/06, Parag Mehta <[EMAIL PROTECTED]> wrote:
>> Hi Laurence
>>
>> thanks for the info but here is the output:
>> ntpq -c peers
>>      remote           refid      st t when poll reach   delay   offset
>> jitter
>> ==============================================================================
>>
>> *LOCAL(0)        LOCAL(0)         3 l   41   64  377    0.000    0.000
>>  0.004
>>
>> It appears that no peers get listed here. here is some more config info
>> from my server:
>>
>> /etc/ntp.conf
>> restrict default kod nomodify notrap
>> restrict xx.xxx.xx.xx
>>  restrict default kod nomodify notrap
> 
> 
> Unless 'restrict xx.xxx.xx.xx' is 'restrict  127.0.0.1', the reason no
> peers get listed is because ntp is unable to configure them at startup
> due to the 'nomodify' restrictions
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers

Reply via email to