From owner-freebsd-stable Tue Sep 7 14:30:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 3A90D14D67 for ; Tue, 7 Sep 1999 14:30:35 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id OAA24190; Tue, 7 Sep 1999 14:29:15 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199909072129.OAA24190@freeway.dcfinc.com> Subject: Re: The importance of a correctly set time In-Reply-To: <44586.936695180@axl.noc.iafrica.com> from Sheldon Hearn at "Sep 7, 99 11:06:20 am" To: sheldonh@uunet.co.za (Sheldon Hearn) Date: Tue, 7 Sep 1999 14:29:15 -0700 (MST) Cc: stable@freebsd.org Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> *If your kernel/CMOS time is not set correctly, your 'make world' and >> 'make install' of various ports may fail in unexpected ways* Can someone please explain the linkage (if any) between the kernel's idea of the time, and the CMOS clock on the motherboard? I know Solaris x86 attempts to keep them in sync. There's a /etc/system switch to turn that off if, for example, you're running xntp (so you don't have several processes fiddling with kernel time). I know Interactive UNIX (yes, I'm that old, and yes, we still have some running) will set the CMOS clock anytime settimeofday(3) is called. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message