On Tue, Nov 18, 2008 at 6:08 PM, Kurt Buff <[EMAIL PROTECTED]> wrote: > It's not necessarily for the precision, though that's nice.
If highly accurate time is not needed, I just set the time on a designated master computer using my wrist watch. :) Then everything else sync's to that. Sure, the master computer's clock might drift by a few minutes every few months, but everything is internally consistent, which is often what matters. In other words, we don't care if 4:32:27 PM is actually 4:33:11 PM at the US Naval Observatory, so long as it's the same between two computers internally. > It's for the independence from possibly erroneous NTP sources ... For our network which does have Internet access, I sync to multiple disseparate sources, including Microsoft, Apple, the us.ntp.org pool, a local ISP, and a local university. I figure that's reasonable defense against a wonky time server. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
