On Wednesday 04 October 2006 20:02, Carlos E. R. wrote:
In other words, ntpd is designed for machines with permanent network connections.
At the risk of turning this thread circular, ... Even though that's true, what is the reason _not_ to start ntpd (rcntp start) just after a network connection is started, and stop it again just before the network connection is shut down? (Forgive my ignorance, but) does 'rcntp start' effectively perform an 'ntpdate' command, then start ntpd? If so, then simply issuing the 'rcntp stop/start' commands from the NetworkManager applet when the link(s) go up and down would seem ideal for machines with intermittent network connectivity. If not, then first calling 'ntpdate', followed by 'rcntp start' when a link comes up, and 'rcntp stop' before closing a link, would work? KNetworkManager allows commands to be run at "Link Up" and "Link Down", so why not do it there? What are the security implications of making the rcntp script suid root? Hmm, .....