From owner-freebsd-questions@FreeBSD.ORG Thu Mar 3 20:57:52 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 381A316A4CE for ; Thu, 3 Mar 2005 20:57:52 +0000 (GMT) Received: from hosea.tallye.com (joel.tallye.com [216.99.199.78]) by mx1.FreeBSD.org (Postfix) with ESMTP id CA7AD43D49 for ; Thu, 3 Mar 2005 20:57:51 +0000 (GMT) (envelope-from lorenl@alzatex.com) Received: from hosea.tallye.com (hosea.tallye.com [127.0.0.1]) by hosea.tallye.com (8.12.8/8.12.10) with ESMTP id j23KvoqS006402 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 3 Mar 2005 12:57:51 -0800 Received: (from sttng359@localhost) by hosea.tallye.com (8.12.8/8.12.10/Submit) id j23KvoZM006400; Thu, 3 Mar 2005 12:57:50 -0800 X-Authentication-Warning: hosea.tallye.com: sttng359 set sender to lorenl@alzatex.com using -f Date: Thu, 3 Mar 2005 12:57:50 -0800 From: "Loren M. Lang" To: Luke Message-ID: <20050303205750.GK30896@alzatex.com> References: <20050302102908.GF30896@alzatex.com> <1529139444.20050302193225@wanadoo.fr> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="GID0FwUMdk1T2AWN" Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-GPG-Key: ftp://ftp.tallye.com/pub/lorenl_pubkey.asc X-GPG-Fingerprint: B3B9 D669 69C9 09EC 1BCD 835A FAF3 7A46 E4A3 280C cc: freebsd-questions@freebsd.org Subject: Re: Received mail timestamp is off by 7 hours X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Mar 2005 20:57:52 -0000 --GID0FwUMdk1T2AWN Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Mar 02, 2005 at 01:00:15PM -0800, Luke wrote: >=20 > >>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. >=20 > 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= =20 > easy either. For me it involved a scavenger hunt through out-of-date=20 > websites and a lot of failed attempts. http://www.nist.gov/ > 3) If your clock tends to run noticably fast or slow, constant NTP=20 > corrections tend to do more harm than good, at least in my experience. I= t=20 > got to where I couldn't even run a buildworld because NTP kept tinkering= =20 > 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 "freebsd-questions-unsubscribe@freebsd.o= rg" --=20 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 =20 --GID0FwUMdk1T2AWN Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFCJ3pObTXoRwEYo9IRAv54AJ0dRP2Eba0uJP0OeG5LfMLoqHrKFACfcQ3w YqqKNwNzdmW2FLt41iOnLqA= =8u5s -----END PGP SIGNATURE----- --GID0FwUMdk1T2AWN--