Quote Originally Posted by birdman View Post
whereas yours showed that ntpdate-sync had reset the time to 0 (or at least <= 10000).

I can't see why it would do that on one system but not on another.
The ntpdate source code contains this at the start of clock_adjust() (which is the only entry to the code which changes the clock):

Code:
        if (server == 0) {
                msyslog(LOG_ERR,
                        "no server suitable for synchronization found");
                return(1);
        }
Leaving aside the fact that the check is against 0* this means that if no NTP server has been reachable then the code just returns without ever changing the clock. So I'm at a loss to see how your system gets past this if it has no network connexion.



*(it should be against NULL or , better, !server - on Unix systems these tests are all the same, but I've used systems where they are not...)