[ntp:questions] Standalone Windows XP/7 Machine Needs to Serve NTP

Martin Burnicki martin.burnicki at meinberg.de
Mon Sep 30 15:05:45 UTC 2013

E-Mail Sent to this address will be added to the BlackLists wrote:
> David Woolley wrote:
>> BlackLists wrote:
>>> Although that is abnormal, I don't see the problem.
>>> Unlike normal ntpd use;
>>>    Use server Undisciplined Local Clock (LOCAL) ONLY,
>>>     Fudge it to True,
>>>    Restart ntpd when you jump the time around with your simulator?
>> The clients will shut down as the time step
>>   is more than 1,000 seconds.
>>    For steps less than 1,000 second they'll still take
>>     upwards of 20 minutes to react.
>> You can tweak these numbers, although I don't know if
>>   panic can be set as large as several days.
> Yes, I meant restart the ntpd service on _all_ systems
>   with ntpd -g so it won't panic stop.
> IIRC meinberg has a script for that?
>   restartntp.bat ?
> You probably want to restart the one being used as the
>   "Server" (with the Undisciplined Local Clock) first,
>   then restart the "Clients" that are following the "Server".
> You may also have to set the "Server" as true in the clients
>   .conf server line.

This would simply be "net stop ntp" and "net start ntp" on Windows.

If this is a test environment ist should be possible to restart NTP on 
the Linux clients by an ssh command once the "reference time" has been 

Martin Burnicki

Meinberg Funkuhren
Bad Pyrmont

More information about the questions mailing list