-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [EMAIL PROTECTED] wrote: > > I beleive that ntpd will choose the server that has the closest time from > your kernel time when you start ntpd up. Just run ntpdate with the server > you want ntpd to pick up before starting ntpd. That should do it. >
I've found just using the 'prefer' option to be really helpful. I set that on the local ntpd I have going at home and at our work locations so that it prefers my server and then I just added 4 random pool servers. The example lines in my config: server rikku.vrillusions.com prefer server 1.us.pool.ntp.org server 2.us.pool.ntp.org server 3.us.pool.ntp.org server us.pool.ntp.org I still have the local clock defined below those, fudged to st10, as my home connection isn't usually the most reliable. A very detailed explanation of the prefer keyword: http://www.lnf.infn.it/computing/Unix/ntp/prefer.html The way I interpret prefer: As long as rikku is providing an accurate time, use it over any of the pool members. It's overridden st1 servers that are in the pool (again, wtf?) that may be ever so slightly more accurate. My intent though is to have my server be the primary timekeeper for the various locations. But if the connection to rikku goes down or something, it will fall back on one of the other servers. - -- Todd http://www.vrillusions.com/ My PGP Key ID: 0xBC90230C -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFG9Zh7iSebwryQIwwRAgxvAKCoYqg1Dpi54zuxRFmrURQpj/mblwCfedpD woKCsbgdTHvE1KhPR5xxh/Y= =7Z4t -----END PGP SIGNATURE----- _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
