From owner-freebsd-bugs Mon Mar 30 05:20:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA01451 for freebsd-bugs-outgoing; Mon, 30 Mar 1998 05:20:33 -0800 (PST) (envelope-from owner-freebsd-bugs@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA01431; Mon, 30 Mar 1998 05:20:18 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id XAA29255; Mon, 30 Mar 1998 23:16:08 +1000 Date: Mon, 30 Mar 1998 23:16:08 +1000 From: Bruce Evans Message-Id: <199803301316.XAA29255@godzilla.zeta.org.au> To: ache@FreeBSD.ORG, helbig@Informatik.BA-Stuttgart.DE Subject: Re: bin/6164 Cc: freebsd-bugs@FreeBSD.ORG Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Hmm. The reason for this warning message (``non existent UCT time'') >is an erraneous use of mktime(3): mktime(3) *always* assumes >that the passed tm structure (utc) holds *local* time, even if the >parameter is filled by gmtime(3). >At March 29th 4:01 CEST gmtime() put 2:01 into utc, which is correct. >Then mktime(3) assumes March 29th 2:01 *local* time which does not exist. Isn't that the point of using local time? The purpose of `adjkerntz -a' is to adjust the RTC to local time when DST changes. The adjustment can't be done if it would give a nonexistent time or an ambiguous time. mktime() happens to handle nonexistent times in a convenient way (by failing; it's not clear what else it could do). I think there are more problems with ambiguous times when DST starts, since mktime() doesn't fail then. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message