ntpdate requires that the socket be open locally, so you have to shutdown ntpd before running it. ntpdate -d will bring back results either way, but will not reset the local clock.
Once you get the time synced with ntpdate, just restart the ntpd. You can put the ntp sever in the step-tickers file and it will sync time at each reboot then start ntpd. See the init.d script. Hope this helps. ------------------ Marvin Blackburn Systems Administrator Glen Raven "He's no failure. He's not dead yet" --William Lloyd George > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of James D. Parra > Sent: Thursday, September 18, 2003 8:32 PM > To: Redhat-List (E-mail) > Subject: setting up NTPd > > > Hello, > > I have ntpd running on three machines; one (primary) internal server > pointing to a stratum 2 server on the net, and the other two > pointing to the > internal primary server. When I issue ntpdate on all three > machines I get > the following error; "18 Sep 17:13:44 ntpdate[14942]: the NTP > socket is in > use, exiting". If I use 'rdate -p' on the two internal > servers pointing to > our primary internal NTP server I get a 'connection refused' > error. The > 'rdate -p" command works when pointing to the stratum 2 > server. The daemons > are running on all three machines. > > How can make our primary internal ntp server accept > connections? And, how > can I ensure that all the clocks on the internal machines are > in sync with > one another? > > Thank you in advance, > > James > > > -- > redhat-list mailing list > unsubscribe mailto:[EMAIL PROTECTED] > https://www.redhat.com/mailman/listinfo/redhat-list -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/redhat-list
