From owner-freebsd-questions Tue May 15 22:14:45 2001 Delivered-To: freebsd-questions@freebsd.org Received: from fedde.littleton.co.us (cfedde.dsl.frii.net [216.17.139.141]) by hub.freebsd.org (Postfix) with ESMTP id 0D00537B422 for ; Tue, 15 May 2001 22:14:43 -0700 (PDT) (envelope-from cfedde@fedde.littleton.co.us) Received: from fedde.littleton.co.us (localhost [127.0.0.1]) by fedde.littleton.co.us (8.11.2/8.11.2) with ESMTP id f4G5Ef836010; Tue, 15 May 2001 23:14:41 -0600 (MDT) Message-Id: <200105160514.f4G5Ef836010@fedde.littleton.co.us> To: "Crist Clark" Cc: freebsd-questions@FreeBSD.ORG Subject: Re: mktime(3) Bug? In-Reply-To: <3B01CD18.6E725786@globalstar.com> From: Chris Fedde Date: Tue, 15 May 2001 23:14:41 -0600 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 15 May 2001 17:43:04 -0700 "Crist Clark" wrote: +------------------ | Before I send in a PR, I wanted to make sure this was really a bug and | not some bizarre "feature" everyone already knew about but me. | | I noticed odd behavior when doing some conversions with date(1) (FreeBSD's | date(1) rewls for letting you do these kinds of conversions, BTW). Note what | happens when I cross a daylight savings time boundary (which was the 1st | of April for my timezone this year), | | $ date -j -f %Y%m%d%H%M 200104010000 | Sat Mar 31 23:00:46 PST 2001 +------------------ I suspect that you are correct. I'd expect date to print Sun Apr 1 00:00 PST 2001 for your input. -- Chris Fedde To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message