Am Mittwoch, 4. Februar 2009 14:57:28 schrieb Alan McKinnon: > ntpd is really designed for Unix servers with 3 digit uptimes and clocks > not assembled by Mickey Mouse's younger brother (which seems to include all > pcs ever made.....)
Errh, no. It is designed for exactly those machines, so that they are
independant of their hardware (Mickey Mouse) clock and of course to keep them
all in sync with each other (and the Unix servers they connect to).
> Most folk are better off with ntpdate run from a cron. When run, it checks
> the upstream time and immediately corrects the local clock to that time.
> Schedule it for once an hour or so, depending on your bandwidth and local
> ntp site's policies.
That does exactly what NTP tries to avoid: Time jumps.
So when you're not connected to the net permanently, one has two choices:
1) Choose one of your machines as the ntp time server which delivers the time
of its internal clock and synchronize each others time with this one. In the
end it only matters that the time is correct in _your_ own network, isn't it.
2) If even the most accurate internal clock on your network is not accurate
enough, plug an accurate time source into one machine you choose as time
server, then goto 1).
Bye...
Dirk
signature.asc
Description: This is a digitally signed message part.
