That's good advice though, honestly. I'll go ahead and do that. I just hadn't bothered before. I figured my pc could keep decent enough track of it's own time, and it mostly did. I was fiddling around with something else that apparently changed it without my noticing (since the hourly time was still accurate. I suppose that's what rdate or ntpd is for. What's different about ntpd that makes it so much better? How does it better prevent it from straying from a value it reads in every day or so?
NTP keeps in touch with time servers like time.nist.gov on more or less a constant basis, it uses the data it gets back to not only set your clock, but fine-tune it so it runs at the right speed. Rather than running every day or so it stays connected as much as possible. It runs as a service, not a cron-job.
-- Andrew Jorgensen
smime.p7s
Description: S/MIME Cryptographic Signature
____________________ BYU Unix Users Group http://uug.byu.edu/ ___________________________________________________________________ List Info: http://uug.byu.edu/cgi-bin/mailman/listinfo/uug-list
