[ntp:questions] ntp client: keep all servers at startup

Ralf Fassel ralfixx at gmx.de
Tue May 3 14:16:27 UTC 2005

I have two isolated computers (no internet connection on both),
needing synchronized time to each other.  One is the
NTP-master-server, the other acts as client only.

Now when the client boots, the master might not be reachable (network
down, master down).  In such a situation when I later ask ntpq to show
the peers, only LOCAL is listed, most probably because the server did
not survive the 'initial sanity check' mentioned in the NTP Docs.

How can I convince ntpd on the client to keep the 192.168.1.x machine
in the ntp-server list, even if it is not reachable on startup?

A workaround could be to use ntpdc to add the server when the network
connection is up and running, but I'd rather use this as a last


More information about the questions mailing list