From owner-freebsd-stable@FreeBSD.ORG Sun Nov 27 00:40:54 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4E9EE16A41F for ; Sun, 27 Nov 2005 00:40:54 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: from regurgitate.ugcs.caltech.edu (regurgitate.ugcs.caltech.edu [131.215.176.97]) by mx1.FreeBSD.org (Postfix) with ESMTP id D11B543D82 for ; Sun, 27 Nov 2005 00:40:43 +0000 (GMT) (envelope-from jd@ugcs.caltech.edu) Received: by regurgitate.ugcs.caltech.edu (Postfix, from userid 3640) id B4228E816; Sat, 26 Nov 2005 16:40:42 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by regurgitate.ugcs.caltech.edu (Postfix) with ESMTP id 9D19FE815; Sat, 26 Nov 2005 16:40:42 -0800 (PST) Date: Sat, 26 Nov 2005 16:40:42 -0800 (PST) From: Jon Dama To: Brett Glass In-Reply-To: <6.2.5.6.2.20051126150622.0843d3e0@lariat.org> Message-ID: References: <200511260118.SAA20596@lariat.net> <6.2.5.6.2.20051126150622.0843d3e0@lariat.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Cc: Brett Glass , stable@freebsd.org Subject: Re: FreeBSD 6.0 cron is running on GMT X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Nov 2005 00:40:54 -0000 What is the output of date vs date -u on your system? What's the value of machdep.adjkerntz ? Is /etc/localtime intact? Does anything change if you rerun tzsetup? On Sat, 26 Nov 2005, Brett Glass wrote: > At 07:20 PM 11/25/2005, Jon Dama wrote: > > >Uh, the problem would be that kernel does not know that the CMOS clock is > >set to the local time. Standard practice is that the CMOS clock should be > >set to UTC. > > We've never set the CMOS clock to UTC/GMT on any previous version of > FreeBSD, and yet have never seen this behavior. > > By the way, the "date" command does report the correct time. It's cron > that seems to be getting the time wrong. > > --Brett Glass >