From owner-freebsd-stable Sat Apr 28 15:21:30 2001 Delivered-To: freebsd-stable@freebsd.org Received: from kristen.shadowdale.net (omah6400gw2poolB75.omah.uswest.net [63.227.157.75]) by hub.freebsd.org (Postfix) with ESMTP id A0DD137B42C; Sat, 28 Apr 2001 15:21:24 -0700 (PDT) (envelope-from hey9811@yahoo.com) Received: from localhost (hey9811@localhost) by kristen.shadowdale.net (8.9.3/8.9.3) with ESMTP id RAA11684; Sat, 28 Apr 2001 17:21:20 -0500 (CDT) (envelope-from hey9811@yahoo.com) X-Authentication-Warning: kristen.shadowdale.net: hey9811 owned process doing -bs Date: Sat, 28 Apr 2001 17:21:20 -0500 (CDT) From: Virtual Bob To: Tim Zingelman Cc: FreeBSD STABLE discussion , FreeBSD Install & Config discussion Subject: Re: adjkerntz ain't running' In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Alright, what's wrong? I sure like to know under what conditions will > > adjkerntz fail to run? Should I even be concerned with adjkerntz? > > adjkerntz only runs if your CMOS (hardware) clock is set to local time, it > is not needed if the CMOS clock is set to UTC. 'man adjkerntz' for > details. If /etc/wall_cmos_clock exists, adjkerntz will run, otherwise it > will not. Whew! That's certainly good to know. My previous impression by reading the man page was that adjkerntz was some interface between CMOS clock and the internal clock. I thought that's bit weird, but didn't thought about it too much. And the server is indeed in UTC in CMOS. Now I have to go change that secondary server to UTC so I don't get confused... ------------- clip here with virtual scissors -------------- ************************************************************ Keyboard stuck error. Press F1 to continue. Any unsolicited e-mails will be charged US$500 per e-mail, plus court cost. Your contribution to Bill Gates' personal wealth: US$359.17 ************************************************************ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message