[ntp:questions] ntpdate works, but ntpd doesn't (reach = 0)

Richard B. Gilbert rgilbert88 at comcast.net
Tue Feb 10 14:48:01 UTC 2009


Harlan Stenn wrote:
>>>> In article <uck566-23p.ln1 at gateway.py.meinberg.de>, Martin Burnicki <martin.burnicki at meinberg.de> writes:
> 
> Harlan> Because ntpd also gets restarted, and there is a strong belief that
> Harlan> -g is bad for a restart and restarts will happen more often than
> Harlan> boots.
> 
> Martin> Huh? I'm afraid I don't understand what you mean here.
> 
> The general case is that -g should only be used at startup, when time can be
> stepped.
> 
> If ntpd is restarted, it is Bad for the time to be stepped backwards for
> many people.  Since this could happen with -g, when restarting ntpd for this
> common case, one should not use -g.

Why should it be necessary to restart ntpd????  Unless I have a power 
failure that lasts longer than my UPS, I almost never restart my NTP 
server!  Same for the NTP clients.

Systems that go down and up like a yo-yo are never going to know what 
time it is anyway!




More information about the questions mailing list