On Fri, 2009-01-09 at 08:39 +0100, Frank Kardel wrote: > I see that dhcpd apparently does the restart dance with ntp. As of ntp > 4.2.4 (already included in NetBSD 4.0) restarting > ntp for coping with changed IP-addresses is no longer necessary. ntpd > perfectly understands changed ip addresses on > interfaces and re-binds itself (unless running as non-root). Usually it > is better to keep ntpd running as a restart > destroys all statistics. > may we should consider to avoid restarting ntpd unless it runs as non-root. We restart it because the NTP server(s) to use may have changed. I'm pretty sure that NTP does not detect this on the fly. Also we only restart NTP if the generated config file has actually changed and if NTP was already running. Thanks Roy
Attachment:
signature.asc
Description: This is a digitally signed message part