In article <[email protected]>, Chuck Swiger <[email protected]> wrote: > > In most cases, it is easier to solve the problem of sync'ing all computers to > a correct timesource (and thus all be mutually in sync), then it is to setup > a bunch of truly & completely isolated machines which happen to stay in sync. > If I really had to solve the latter problem, I would likely connect the > machines to a valid NTP timesource long enough to calibrate each machines' > intrinsic drift from realtime, and then run time in standalone mode against > their local clock.
How good does the timekeeping need to be? Was the max error ever stated? Anyway, what I have done in such situations is to anoint a freewheeling ordinary workstation as the "NTP Timeserver" (trumpet flare please), and have everybody else synch to it. Synch to external time is by eyeball and wistwatch. This approach does keep them all together, but their sense of time is a good indicator of the local temperature wherever that anointed workstation is installed. That said, it is admittedly an approach taken only in desperation, and GPS-based NTP timeservers are cheap - just buy the box, install it on the network, and point everybody to it. Joe Gwinn _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
