Thanxs Chuck ;^) But why would I want this script to point to someone else's ntp server? You have missed the point. I want accurate time synchronization. I don't care about accurate time. Pointing to someone else's server would only introduce jitter between my machines because of random lag times. Which is at least as senseless as running ntpdate 3 times in a row ;^)
Speaking of which, as for running ntpdate 3 times in a row being a waste of time, perhaps, and perhaps not. The script was recommended by the manufacturer. I think you may be right, it might be better to run ntpdate every second, instead of 3 times in a row ever 5 seconds ;^) Do you think that the ntpd would keep the machines in better synch than the ntpdate script? I would have to see this for myself... --- On Thu, 9/16/10, Chuck Swiger <[email protected]> wrote: > From: Chuck Swiger <[email protected]> > Subject: Re: [ntp:questions] Why does ntp keep changing my conf file? > To: [email protected] > Cc: [email protected] > Date: Thursday, September 16, 2010, 5:35 PM > On Sep 16, 2010, at 2:59 PM, Daniel > Havey wrote: > > I want ntpdate, and don't really care about > ntpd. I need an ntp server running on one node, and > the other nodes connect to the first node with ntpdate like > this: > > > > #!/bin/bash > > SERVER=ntpserver1 > > RATE=5 > > while [ 1 ]; > > do > > ntpdate -b $SERVER > > ntpdate -b $SERVER > > ntpdate -b $SERVER > > sleep $RATE > > done > > > > So I think what I would like to do is install an NTP > server on one node, verify that it works ;^) and have the > others keep in synch with the script. > > > At some point, perhaps, you will figure out that invoking > "ntpdate -b" three times in a row in a script running every > five seconds is not sensible. In the meantime, please > make sure you don't configure such a script to point to > anyone else's NTP servers.... > > Regards, > -- > -Chuck > > _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
