** Reply to note from Kevin Saenz <[EMAIL PROTECTED]> Tue, 04 Nov 2003 12:24:07 +1100
>
> why are you tuesday 10pm?
Kevin, that's a good Q.
the answer is long and involved, and, I do not understand some parts of it...
<snip>
so, today, when I noticed I'm out by DST, and, adelaide no longer is there, I though, I'd try an NTPD instead of daytime, I've set up NTPD sometime in 1999, but, never used it since then, NTPD had these in: poll interval = 16384 augean.eleceng.adelaide.edu.au ntp.cs.mu.OZ.AU ntp.ml.csiro.au ntp.tip.CSIRO.AU tick.usno.navy.mil tock.usno.navy.mil time.nist.gov 206.54.0.21
Bad ... these are stratum 1 servers. Ordinary folks like us should *really* be synchronising to stratum 2 servers. Real differences between the strata amount to milliseconds usually. www.ntp.org has *all* the info.
I guess, NTPD takes an average between local machine time as well as remote clocks, and, I guess, NTPD shouldn't be invoked on on obviously incorrect time, and, I guess, if I left NTPD running, it would eventually correct the time. Perhaps an interval of '16384' prevented re-calc from being somewhat quicker...
Not really. ntpd will adjust (slew) your clock according to the dfirtfile (/var/ntp/drift) ntpdate steps the change in one hit (see below).
which reminds me, I should really configure ntpd on my Linux server.
ntpd probably isn't the best solution for an intermittent dialup, unless you can stay dailled up for about 24 hours while ntpd sets up a drift file. If the Linux box is dialling, put ntpdate into your ppp.up script
If you do decide to go ahead with ntpd, be sure to check out the pool.ntp.org website.
Cheers, Rob
-- A good quantum physicist is hard to find.
This is random quote 140 of 1254.
Distance from the centre of the brewing universe [15200.8 km (8207.8 mi), 262.8 deg](Apparent) Rennerian
Public Key fingerprint = 6219 33BD A37B 368D 29F5 19FB 945D C4D7 1F66 D9C5
-- SLUG - Sydney Linux User's Group - http://slug.org.au/ More Info: http://lists.slug.org.au/listinfo/slug
