Hi Piero: That's do it!. I checked the ntp doc's about this file and found nothing. In further check I find that this file is parsed to get servers names to pass to "ntpdate" (to sync dates) on the "/etc/init.d/ntpd" script (at service start) and by default the file is empty. One interesting thing is that if this file is missing (not empty), the "etc/init.d/ntpd start" script will add the option -g to ntpd parameters. This is supposed to force ntpd to set the system clock at startup (once) in case of any differences and should be the preferred way because ntpdate is to be retired (the ntpd docs says so...). The problem is that it seems the "-g" options is not working properly. I stopped the ntdp service, removed the step-tickers file, set an invalid date/time and started the ntpd service again. The date was not affected!. Anyway, I will stick with the step-tickers file and ntpdate as they are. Thanks for your help! El Jue 27 Feb 2003 03:14, Piero Calucci escribió: > On Wed, 2003-02-26 at 15:26, Carlos A. Siso wrote: > > Hi John: > > > > Thank you for your answer. Tried the restrict directive but still ntpd > > does not affect the machine time. To test it, I stop the ntpd service, > > set an invalid time in the machine and start the ntpd service again. The > > machine keeps the invalid time. > > > > I am able to sync the machine time using the "Time Server" option of the > > "time&date" module in "Webmin". So the problem is not the network, > > firewall or remote server. > > > > It seems I will have to spend the rest of the week reading the > > (extensive) ntp documentation :-(. > > do you have a /etc/ntp/step-tickers file? > > It should contain a list of time servers to query at ntp startup to sync > the clock even if the difference is above the "regular" ntp threshold > > Piero -- Carlos A. Siso -- Psyche-list mailing list Psyche-list@redhat.com https://listman.redhat.com/mailman/listinfo/psyche-list
