在 2013年11月19日星期二UTC+8上午9时35分40秒，[email protected]写道： > 在 2013年11月19日星期二UTC+8上午9时24分18秒，unruh写道： > On 2013-11-18, David Woolley > <[email protected]> wrote: > On 18/11/13 08:30, > [email protected] wrote: >> hello : >> I had recently start a work > about ntp service ,my friends and me use windows and linux to sync time in > ntp.we could use w32time service to sync linux in ntp.In windows we could I > found that in the registry??? >> > HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config\ > MaxAllowedPhaseOffset may be could set the offset time between the local time > and the server that they will be synchronize. If out of range of > MaxAllowedPhaseOffset in seconds ,they synchronize,otherwise not. >> But I > have a question that Is there a paremeter in ntp service that control the > offset like in registry above in windows. >> > > That sounds like tinker > panic, which is documented in the miscopt.html > file, and defaults to 1000s. > If the offset exceeds that value, ntpd > will shut down. He said that he is > using W32time on the windows machine, not ntpd. Ie, this has nothing to do > with ntpd as far as I can see. > > All tinker options may are used at your > own risk. They set things that > should not normally need setting. > > Note > that there is a command line option to ignore this setting for for > the > first step after startup. > I said that w32time service can set aparemeter > not to sync. in a offset time. Is NTP had this paremeter?
not the clock offset value ,but just a error offset value ,in the range of this paremeter it sync. out of it ,it did not sync. _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
