I should have added this:
remote refid st t when poll reach delay offset
jitter
==============================================================================
LOCAL(0) LOCAL(0) 10 l 43 64 377 0.000 0.000
0.015
*core-sw1.wa.iin tictoc.tip.CSIR 2 u 341 1024 377 139.913 -13.741
15.700
+sol.ccs.deakin. murgon.cs.mu.OZ 2 u 363 1024 377 209.749 -18.357
3.488
+cougar.esec.com murgon.cs.mu.OZ 2 u 385 1024 377 209.995 -13.794
36.014
-augean.eleceng. murgon.cs.mu.OZ 2 u 454 1024 377 228.644 -3.868
7.554
-huon.itd.adelai sol.ccs.deakin. 3 u 398 1024 377 230.059 -2.207
7.050
-ns.saard.net tictoc.tip.CSIR 2 u 388 1024 377 289.122 -26.200
48.720
In practise, when sync is lost (dialup drops usually), after a few
minutes LOCAL becomes the source and the slaves lock back up when its
declared stable (as 10). When the dialup comes online, the sync source
just seamlessly shifts to the higher accuracy source. Same occurs if
the current remote sync source declares itself unstable. The large
offsets are because Perth is a few thousand miles from these sources in
the Eastern states (Oz) - I should look for one of the University
sources here and add that as well.
Another thought - you are not starting ntpd with extra args (especiallly
the -x one)?
BillK
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
