Clock Synchronization

Mike Snitzer msnitzer at plogic.com
Tue Jun 25 20:00:57 EDT 2002


Wow!.. upon further investigation broadcast seems to be working:

[root at LC1 ~]# ntpdc -l
client    LOCAL(0)
client    otc2.psu.edu
broadcast 192.168.0.255
[root at LC2 ~]# ntpdc -l
bclient   LC1
[root at LC2 ~]# ntpq -p
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
*LC1             128.118.25.3     3 -   41   64  377    0.134   -0.091   0.031

All this after doing absolutely nothing.  rgb was right when he said "ntp
is pretty simple and automagic, really."

Mike
 

Angel R. Rivera (angel at wolf.com) said:

> I am coming into this late too, but how about using
>          ntpdc -l
> 
> on my own server it shows...
> 
> >[root at sinapu /root]# ntpdc -l
> >broadcast NTP.MCAST.NET
> >client    <time server 1>
> >client    <time server 2>
> 
> with an ntp.conf:
> >broadcast 224.0.1.1 autokey ttl 6  # brpadcast on LAN shared key
> 
> 
> The Client:
> >[root at gatekeeper root]# ntpdc -l
> >client    NTP.MCAST.NET
> 
> with an ntp.conf:
> 
> >manycastclient 224.0.1.1 autokey
> 
> I am not an expert but did spend a lot of time on getting this up here-then
> moved it over to the cluster and i have not had any problems.  HTH
> 
> 
> Angel R. Rivera, Angel.R.Rivera at wolf.com
> -----
> Veritas et Libertas
> 
> 
_______________________________________________
Beowulf mailing list, Beowulf at beowulf.org
To change your subscription (digest mode or unsubscribe) visit http://www.beowulf.org/mailman/listinfo/beowulf



More information about the Beowulf mailing list