Timeout in NTPTRACE

[yurika]

I was wondering if there is any way I can use NTPDATE to get our systems all synchronized without impacting the jobs that are regulary scheduled to run. I have a few systems that are about 20 minutes off from where the ntp server is set. I am scared to run the command ntpdate to bring it up to date because of the big difference in time. Also even after I run the command, I still cannot get a successful trace. I get back this:
loopback: stratum 16, offset 0.000038, synch distance 1.00029
0.0.0.0: *Timeout*

I also I get no association ID's returned when I run the ntpq -p command.

Please help!
thank you in advance.

[RAC_1]

Never do ntpdate "server". That adjusts the time immediatly and this can cause problems for apps/programs that are time sensititive.

You should be doing ntpdate -B "server", this would slowly adjust the time.

Anil

[Rick Garland]

Here are a couple of sites that contain useful info for NTP

http://www.eecis.udel.edu/~mills/ntp/html/index.html#prog
http://www.ntp.org/


The no association IDs indicates that the /etc/ntp.conf file has not been configured.

There are options to the NTPDATE to do steps instead of all at once.

[yurika]

Thank you both for the fast repsonses!

How long should I expect for a 20 minute delay to come upto date using ntpdate -B ?

thanks again.