On Wed, Mar 02, 2005 at 01:00:15PM -0800, Luke wrote: > > >>There's no excuse for a mailserver to not be synced to a NTP source. > > > >I'd extend that to apply to any server. Practically all the things a > >server does are dependent in some way on the correct time. > > I have three excuses: > 1) NTP is difficult to configure. I've done it, but it wasn't trivial.
ntpdate once at boot. > 2) Finding an NTP server willing to accept traffic from the public isn't > easy either. For me it involved a scavenger hunt through out-of-date > websites and a lot of failed attempts. http://www.nist.gov/ > 3) If your clock tends to run noticably fast or slow, constant NTP > corrections tend to do more harm than good, at least in my experience. It > got to where I couldn't even run a buildworld because NTP kept tinkering > with the clock in the middle of the process. Same as 1) > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- I sense much NT in you. NT leads to Bluescreen. Bluescreen leads to downtime. Downtime leads to suffering. NT is the path to the darkside. Powerful Unix is. Public Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc Fingerprint: CEE1 AAE2 F66C 59B5 34CA C415 6D35 E847 0118 A3D2
pgp3yOu0GrZHj.pgp
Description: PGP signature
