- tz - lists.iana.org

18 sec
by Garrett Wollman March 29, 1994

March 29, 1994

<<On Tue, 29 Mar 1994 10:12:19 +0200 (MESZ), Hinrich Eilts <eilts(a)late.e-technik.uni-erlangen.de> said: > I synchronized FreeBSD-1.1-BETA to a stratum-1 timeserver by ntpdate > and xntpd and compared localtime by "date" with it and two other > machines, which are synchronized by xntpd too. FreeBSD has a > difference of -18 secounds to all other machines (a NeXT-Station > with NeXTStep, a Sun with SunOS 4.x and a HP9000-750 with > HPUX). What you are seeing is the interaction of several different `features' of NTP and FreeBSD. I'll try to explain, and again hope that somebody out there can provide a complete solution. Here are the problems... 1) The timezone database does not reflect the fact that the first time step, in going from GMT (pre-1972) to UTC (1972 to present) was actually 10 seconds, and not just one like all subsequent leap seconds. 2) The timezone database DOES include all subsequent time steps. 3) The NTP code ``handles'' leap seconds by turning the clock back when they happen. By contrast, the timezone code assumes that time_t's are increasing (which they ought to be; I hold that xntpd's behavior is simply wrong). To wit: NTP code wants: Real Time UNIX Time --------------- --------- --------- 30 June 1994, 23:59:59 t s 30 June 1994, 23:59:59 t+1 s 01 July 1994, 00:00:00 t+2 s+1 Timezone code wants: Real Time UNIX Time -------------------- --------- --------- 30 June 1994, 23:59:59 t s 30 June 1994, 23:59:60 t+1 s+1 01 July 1994, 00:00:00 t+2 s+2 A temporary (ugly hack) solution is to use `posix/your/time/zone' rather than `right/your/time/zone' (which is the same as `your/time/zone') for /etc/localtime. -GAWollman -- Garrett A. Wollman | Shashish is simple, it's discreet, it's brief. ... wollman(a)lcs.mit.edu | Shashish is the bonding of hearts in spite of distance. formerly known as | It is a bond more powerful than absence. We like people wollman(a)emba.uvm.edu | who like Shashish. - Claude McKenzie + Florent Vollant

2 2

Re: 18 sec
by Bradley White March 29, 1994

March 29, 1994

Garrett Wollman <wollman(a)adrastea.lcs.mit.edu> writes: > What you are seeing is the interaction of several different `features' > of NTP and FreeBSD. I'll try to explain, and again hope that somebody > out there can provide a complete solution. Here is an encore of my reply of February 7th. --- Begin forwarded message Date: Mon, 07 Feb 1994 18:05:34 -0500 (EST) From: Bradley White <bww+(a)transarc.com> Subject: Re: leap seconds To: Garrett Wollman <wollman(a)emba.uvm.edu> Cc: Paul Eggert <eggert(a)twinsun.com>, Zone Watchers <tz(a)elsie.nci.nih.gov>, freebsd-tz(a)freefall.cdrom.com Message-Id: <09490.760662334(a)capitol.transarc.com> In-Reply-To: Your message of Mon, 7 Feb 94 17:23:21 -0500 <9402072223.AA23255(a)bajoran.emba.uvm.edu> Any system that runs with ``REDO=right_*'', and which therefore wants to continue to tick normally over leap seconds, needs to do a little bit of work to generate NTP-style timestamps. That is, NTP-style timestamps are discontinuous over leaps, while ``REDO=right_*'' time_t's are continuous. Recent incantations of the `tz' package provide the time2posix() function to help in mapping between these two formats. For example, in the (old, version-1) NTP code, you need to change ... stampp->int_part = htonl(tvp->tv_sec + JAN_1970); to stampp->int_part = htonl(time2posix(tvp->tv_sec) + JAN_1970); I haven't looked at the (new, version-3) XNTP code, but I imagine the change needed there is just as trivial. After that, you will chime NTP harmoniously with the rest of the world, *and*, you will sail smoothly through leap events without the jitter or confusion suffered by your NTP peers. Bradley

1 0

AU Summer time channges (proposed).
by Robert Elz March 29, 1994

March 29, 1994

I'm not in AU right now, and haven't seen the announcementss, though there was talk of changes before I left, but I'm told there is agreement for Vic SA and Tas to switch to summer time on Oct 1, and revert to standard time Mar 31 to give exactly 6 months daylight saving (summer time really) a yearA. One would presume they'd keep the "change on a Sunday" rule, but who knows. Apparently NSW weren't impressed, but may end up changing their minds. I'm sure others in AU can give more details on this. kre

1 0

Re: EU Summer Time update [forwarded with permission]
by ado March 29, 1994

March 29, 1994

> From @doc.memex.co.uk:peter@memex.co.uk Tue Mar 29 08:03:37 1994 > Return-Path: <@doc.memex.co.uk:peter@memex.co.uk> > Received: from relay2.UU.NET by elsie.nci.nih.gov (4.1/SMI-4.1) > id AA09181; Tue, 29 Mar 94 08:03:34 EST > Received: from young.cs.strath.ac.uk by relay2.UU.NET with SMTP > (5.61/UUNET-internet-primary) id AAwjia29244; Tue, 29 Mar 94 08:03:28 -0500 > Received: from doc.memex.co.uk by young.cs.strath.ac.uk id aa02542; > 29 Mar 94 14:02 +0100 > Received: by doc.memex.co.uk (4.1/memex_18) > id AA15065; Tue, 29 Mar 94 13:51:13 BST > Date: Tue, 29 Mar 94 13:51:13 BST > From: Peter Ilieve <peter(a)memex.co.uk> > Message-Id: <9403291251.AA15065(a)doc.memex.co.uk> > To: ado(a)elsie.nci.nih.gov > Subject: Re: EU Summer Time update > Status: RO > > > Thanks for the scoop on EU Summer Time. Is it premature to forward it to > > the time zone list? > > ... > > It is the best info available at present. My personal guess is that > nothing will be changed. I have no idea why it has taken since last > September to fail to confirm this directive, nor why it may take until > May. The first change from existing practice is not until October 95, > when the UK/Eire date is Sun>=22 rather than Sun>=23 so it is probably > safe to pass it on, even if you have to correct it later. > > > Peter

1 0

EU Summer Time update [forwarded with permission]
by ado March 29, 1994

March 29, 1994

> From @doc.memex.co.uk:peter@memex.co.uk Mon Mar 28 04:36:25 1994 > Return-Path: <@doc.memex.co.uk:peter@memex.co.uk> > Received: from relay2.UU.NET by elsie.nci.nih.gov (4.1/SMI-4.1) > id AA12705; Mon, 28 Mar 94 04:36:22 EST > Received: from young.cs.strath.ac.uk by relay2.UU.NET with SMTP > (5.61/UUNET-internet-primary) id AAwjdu24981; Mon, 28 Mar 94 04:36:08 -0500 > Received: from doc.memex.co.uk by young.cs.strath.ac.uk id aa20721; > 28 Mar 94 10:34 +0100 > Received: by doc.memex.co.uk (4.1/memex_18) > id AA05804; Mon, 28 Mar 94 10:32:19 BST > Date: Mon, 28 Mar 94 10:32:19 BST > From: Peter Ilieve <peter(a)memex.co.uk> > Message-Id: <9403280932.AA05804(a)doc.memex.co.uk> > To: ado(a)elsie.nci.nih.gov > Subject: EU Summer Time update > Status: RO > > I now have a copy of the proposal for the 7th EC directive on summer time > arrangements (COM (93) 439 final, 27 September 1993). This is not yet > a formal directive, treat this as advance warning, some dates may still > change. > > I what looks like a triumph of British obduracy over the poor benighted > foreigners it is proposed to move to a common end date of the 4th Sunday > in October from 1997 so the foreigners will have their winter benightment > postponed by a month. The EC Commission actually asked its tame polling > organisation to conduct one of its Eurobarometer surveys which showed > `that European public opinion is very much in favour of having summer > time extended until the end of October'. > > The dates proposed are: > > 1995: last Sunday in March (26 March) to last Sunday in September (24 Sep) > (UK & Eire ending on 4th Sunday in October (22 Oct)) > 1996: last Sunday in March (31 March) to last Sunday in September (29 Sep) > (UK & Eire ending on 4th Sunday in October (27 Oct)) > 1997: last Sunday in March (30 March) to 4th Sunday in October (26 Oct) > 1998: last Sunday in March (29 March) to 4th Sunday in October (25 Oct) > > The UK/Eire end date of 22 October conflicts with your current rule of > Oct Sun>=23, and the historical UK formula of Sun after 4th Sat. The > last time 4th Sun and Sun after 4th Sat differed was in 1989, when 29 > October was used. That year was covered by a UK Summer Time Order for > only a single year and it looks as though there was a matching 4th EC > directive for just this year. I don't have the text of the 5th EC > directive (for 1990--92) but my guess would be it said 4th Sun. To > maintain strict historical accuracy you could start a new UK ending > rule of Oct Sun>=22 in 1990. A similar rule will be needed for all the > -Eur rules from 1997. > > Negotiations about joinging the EU have been concluded with Austria, > Finland, Norway and Sweden and if the current argument among the existing > members about consequential changes in voting rules can be resolved > they should join on 1 Jan 1995, and will presumably use the same > summer time rules as the existing members. I don't know what they do now. > > As I said, this is only a proposal at present. The EC information office > in Edinburgh could give a guesstimate of when the final version might > emerge. The Home Office guessed at the end of May. > I will keep you posted. > > > Peter Ilieve peter(a)memex.co.uk

1 0

Re: mktime() failures under PCTS testing
by Grant Sullivan March 23, 1994

March 23, 1994

In PCTS, "ambiguous" is referring to the time periods at, and 59:59 minutes after the start of daylight savings, where the time given is as if there were no transition to daylight savings 59:59 minutes before, and at the end of daylight savings, where the time given is as if there were no transition from daylight savings and tm_isdst = -1, assuming the difference between standard vs. daylight is 60:00 minutes. I've run tests on SVR4v3 and HP-UX C.09.01 systems and found their mktime() maps 02:MM:SS/DST-UNKNOWN to 01:MM:SS/DST-OFF I think I prefer 02:MM:SS/DST-UNKNOWN to 03:MM:SS/DST-ON but either mapping is acceptable to PCTS. ------- Forwarded Message Return-Path: bww+(a)transarc.com Received: from sparc51.transarc.com (sparc51.transarc.com, [192.55.207.51]) by transarc.com (5.54/3.15) id <AA06638> for grant(a)osf.org; Wed, 23 Mar 94 14:51:15 EST Received: by sparc51.transarc.com with BradMail(MH 6.8); Wed, 23 Mar 1994 14:51:06 -0500 (EST) To: Grant Sullivan <grant(a)osf.org> Cc: Arthur David Olson <ado(a)elsie.nci.nih.gov> Subject: Re: mktime() failures under PCTS testing In-Reply-To: Your message of Wed, 23 Mar 1994 13:37:01 -0500 Date: Wed, 23 Mar 1994 14:51:05 -0500 (EST) Message-Id: <16001.764452265(a)sparc51.transarc.com> From: Bradley White <bww+(a)transarc.com> > mktime() is failing only those PCTS tests which test "ambiguous" transitions > from standard to daylight time. mktime() passes all the tests for "ambiguous" > transitions from daylight to standard time, however. The first and second senses of the word "ambiguous" should be distinguished. The daylight->standard transition period does indeed include wall-clock times that each correspond to two distinct time_t's. However, the standard->daylight transition period renders wall-clock times that simply do not exist. And now my opinion: I am all for mktime() failing for *all* non-existent times-of-day, but, given that we do `isdst' correction, and map the non-existent times of ... 02:MM:SS/DST-OFF to 03:MM:SS/DST-ON and 02:MM:SS/DST-ON to 01:MM:SS/DST-OFF ..., it seems that we should also map 02:MM:SS/DST-UNKNOWN to one of those. Bradley PS: I won't mention that the test suite assumes too much about time_t's :-). ------- End of Forwarded Message

1 0

Re: mktime() failures under PCTS testing
by ado March 23, 1994

March 23, 1994

The ftpable-from-elsie version of the time zone code suffers the same fate as related by grant@osf; on our SunOS 4.1.1 system, after making this change to the sample code: > SCCS/s.try.c: 1.1 vs. 1.2 > *** 1.1/try.c Tue Mar 22 18:45:08 1994 > --- 1.2/try.c Tue Mar 22 18:45:08 1994 > *************** > *** 34,43 **** > --- 34,53 ---- > printf("mktime test: for this test, set TZ=dst0std,J057,J059\n"); > printf("current value of TZ = %s\n", getenv("TZ")); > > + #if 0 > if (setenv("TZ", TZ_value, 1) != 0) { > printf("resetting TZ failed\n"); > exit(1); > } > + #else > + { > + char buf[512]; > + > + (void) strcpy(buf, "TZ="); > + (void) strcat(buf, TZ_value); > + putenv(buf); > + } > + #endif > printf("new value of TZ = %s\n", getenv("TZ")); > > time_str.tm_year = TM_year - 1900; ...I get these results: > mktime test: PCTS/STD/LS/mktime 8.1.58_9 Assert 5.1.3 > mktime test: for this test, set TZ=dst0std,J057,J059 > current value of TZ = (null) > new value of TZ = std0dst,J057,J059 > time_str tm struct set to: > year = 91, mon = 1, mday = 26, hour = 2, min = 0, sec = 0, wday = -1, yday = -1, isdst = -1 > expected value from mktime = 667530000 >>>>> mktime returned -1 (-unknown-) > mktime() final time_str tm struct reset to: > year = 91, mon = 1, mday = 26, hour = 2, min = 0, sec = 0, wday = -1, yday = -1, isdst = -1 Vintage time zone hands will recognize this as behavior that certain SunOS versions of the "cron" program clashed with. The time zone package is assuming that the "mktime" call is asking a question such as... If US DST rules are in effect and I'm in the Eastern US, when, on April 3, 1994, will a wall clock show 2:30 a.m. (irrespective of whether it is or isn't daylight saving time)? ...and the "-1" answer is the package's way of saying... There is no such time! If someone has the relevant wording from the current version of the relevant standard(s) on what to do here, I'd love to hear from you. --ado

3 2

mktime() failures under PCTS testing [forwarded with permission]
by ado March 23, 1994

March 23, 1994

> From grant(a)osf.org Tue Mar 22 17:47:33 1994 > Return-Path: <grant(a)osf.org> > Received: from postman.osf.org by elsie.nci.nih.gov (4.1/SMI-4.1) > id AA07444; Tue, 22 Mar 94 17:47:32 EST > Received: from vishnu.osf.org by postman.osf.org (5.64+/OSF 1.0) > id AA27681; Tue, 22 Mar 94 17:47:26 -0500 > Message-Id: <9403222247.AA27681(a)postman.osf.org> > To: ado(a)elsie.nci.nih.gov (Arthur David Olson) > Cc: grant(a)osf.org > Subject: mktime() failures under PCTS testing > Date: Tue, 22 Mar 1994 17:47:21 -0500 > From: Grant Sullivan <grant(a)osf.org> > Status: RO > > > Hi Arthur, > > I am a contractor at the Open Software Foundation, Cambridge, MA, responsible > for helping to make sure that OSF/1 R1.3 utlities and libraries are > conforming to POSIX.1, POSIX.2, XPG4, and other standards. > > My department's QA group recently completed a PCTS test of our current OSF/1 > libc, and reported to me that there were a number of mktime() failures in > PCTS STD/LS/mktime, such as the following: > > 5.<p1>.5.1.1. Preparation [4009] > Setup environment for testing. > > 5.<p1>.5.1.2. Testing [4009] > TZ is of the form: TZ=dst0std,J057,J059 > Non-leap year, one second prior to Jstart_day time. > > MESSAGE (5.<p1>.5.1.2.): > Testing local time of: Tue Feb 26 01:59:59 1991 > PCTS action taken: CONTINUE > > 5.<p1>.5.1.3. Testing [4009] > Non-leap year, at ambiguous Jstart_day time. > > MESSAGE (5.<p1>.5.1.3.): > Testing local time of: Tue Feb 26 02:00:00 1991 > PCTS action taken: CONTINUE > > ERROR (5.<p1>.5.1.3.): > Call to mktime() failed (returned -1). > PCTS action taken: CONTINUE > > ERROR (5.<p1>.5.1.3.): > Incorrect time returned by call to mktime(). > Expected: 667530000 Or: 667533600 > Actual: -1 > PCTS action taken: CONTINUE > > This particular test calls mktime() with tm_isdst set to -1, so it is expecting > mktime() to return either the standard time value (667530000), or the > daylight time value (667533600), under the apparent assumption that if > tm_isdst == -1, then mktime() would attempt to determine if tm_isdst should be > 0 or 1 and return the proper seconds, and adjust the struct tm accordingly. > > Our current OSF/1 libc ctime.c is based on BSD 4.4-alpha snapshot > "@(#)ctime.c 5.26 (Berkeley) 2/23/91" > with additional fixes from your June'93 kit: > elsieid[] = "@(#)localtime.c 7.9" > plus some other adjustments. > > There are quite a few PCTS failures, but I think they all boil down to a common > cause: mktime() returns -1 when tm_isdst = -1 and the tm structure specifies > the daylight savings time day, and a time at or within the first hour of > daylight savings time. > > I have created a simple test program, based on the XPG4 mktime() example, > which exercises the first PCTS failure case above. I've tried this on > several systems which have older versions of the Zoneinfo package, and on > several systems which don't have the package. I got the same failure on the > older Zoneinfo systems I tested, and mktime() returned 667530000, and set > tm_isdst to 0 on the several systems I tested which don't use the package. > > My own interpretation of the XPG4 and POSIX.2 standards suggest that mktime() > should return 667533600, and reset the passed tm_isdst to 1, under the belief > that for the above case, daylight savings starts exactly at > Tue Feb 26 02:00:00 1991 > for TZ=dst0std,J057,J059, instead of after this time, i.e. instead of at > Tue Feb 26 02:00:01 1991 > > A friend of mine at another company told me he had run into similar mktime() > problems with the FIPS151-2 test suite. He made alterations which resulted > in mktime() returning 667533600, and tm_isdst reset to 1, so we both have the > same interpretations of the XPG4 and POSIX.1 standards. His version of > mktime() was based on something older than your June'93 kit. > > I am wondering what mktime() in your current kit does in this case? Do you > think it should return: > > -1 , tm_isdst = -1 > or 667530000, tm_isdst = 0 > or 667533600, tm_isdst = 1 > > ? > > I am attaching a test program. > > Thanks very much for your help, > > Grant W. Sullivan, grant(a)osf.org > Open Software Foundation > 11 Cambridge Center, > Cambridge, MA 02142 > > > mktime_XPG4_example.c > ========================================================================== > /* XPG4, pg. 276 mktime() example > * > * with input data from PCTS STD/LS/mktime 8.1.58_09 5.1.3 test > * > */ > > #include <stdio.h> > #include <time.h> > > #include <stdlib.h> > > struct tm time_str; > > char daybuf[20]; > > /* values for struct tm; from PCTS STD/LS/mktime 8.1.58_09.c */ > #define TZ_value "std0dst,J057,J059" > #define TM_year 1991 /* non-leap year */ > #define TM_mon 2 /* dst start month -- February */ > #define TM_mday 26 /* dst start day J057 non-leap year */ > #define TM_hour 2 /* for J057 dst start hour */ > #define TM_min 0 /* for J057 dst start hour/min */ > #define TM_sec 0 /* for J057 dst start hour/min/sec */ > #define TM_wday -1 /* don't know */ > #define TM_yday -1 /* don't know */ > #define TM_isdst -1 /* don't know if std or dst */ > #define MKTIME_expected 667530000L > > > main() > { > time_t mktime_returned; > > printf("mktime test: PCTS/STD/LS/mktime 8.1.58_9 Assert 5.1.3\n"); > printf("mktime test: for this test, set TZ=dst0std,J057,J059\n"); > printf("current value of TZ = %s\n", getenv("TZ")); > > if (setenv("TZ", TZ_value, 1) != 0) { > printf("resetting TZ failed\n"); > exit(1); > } > printf("new value of TZ = %s\n", getenv("TZ")); > > time_str.tm_year = TM_year - 1900; > time_str.tm_mon = TM_mon - 1; > time_str.tm_mday = TM_mday; > time_str.tm_hour = TM_hour; > time_str.tm_min = TM_min; > time_str.tm_sec = TM_sec; > time_str.tm_wday = TM_wday; > time_str.tm_yday = TM_yday; > time_str.tm_isdst = TM_isdst; > > printf("time_str tm struct set to:\n year = %d, mon = %d, mday = %d, hour = %d, min = %d, sec = %d, wday = %d, yday = %d, isdst = %d\n", > time_str.tm_year, time_str.tm_mon, time_str.tm_mday, time_str.tm_hour, time_str.tm_min, time_str.tm_sec, time_str.tm_wday, time_str.tm_yday, time_str.tm_isdst); > printf("expected value from mktime = %d\n", MKTIME_expected); > > if ((mktime_returned = mktime(&time_str)) == (time_t)-1) { > (void)puts("mktime returned -1 (-unknown-)"); > printf("mktime() final time_str tm struct reset to:\n year = %d, mon = %d, mday = %d, hour = %d, min = %d, sec = %d, wday = %d, yday = %d, isdst = %d\n", > time_str.tm_year, time_str.tm_mon, time_str.tm_mday, time_str.tm_hour, time_str.tm_min, time_str.tm_sec, time_str.tm_wday, time_str.tm_yday, time_str.tm_isdst); > exit(1); > } > else { > printf("mktime returned value = %d\n", (int) mktime_returned); > printf("mktime() final time_str tm struct reset to:\n year = %d, mon = %d, mday = %d, hour = %d, min = %d, sec = %d, wday = %d, yday = %d, isdst = %d\n", > time_str.tm_year, time_str.tm_mon, time_str.tm_mday, time_str.tm_hour, time_str.tm_min, time_str.tm_sec, time_str.tm_wday, time_str.tm_yday, time_str.tm_isdst); > > (void)strftime(daybuf, sizeof(daybuf), "%A", &time_str); > (void)puts(daybuf); > } > > exit(0); > } > ==========================================================================

2 1

Re: Does anyone have the source for this function?
by myersn＠roguewave.com March 23, 1994

March 23, 1994

> Does anyone have a UNIX function for converting a time from timezoneX > to timezoneY? I know how to write this by mucking with char** environ > and by calling tzset(), but I'm interested in a more elegant solution > (perhaps using fields in the tm structure). > > convert(timezoneX, timezoneY, inputTime, outputTime) > > The char** environ solution seems to me to be inelegant because > > 1) I have to reread a file whenever I call tzset() (I think), > and > > 2) while I'm doing the conversion the call to tzset() has a > global effect on my process. If I'm interrupted by a > signal handler that displays the time it will be in a > foreign timezone. My current best solution is to use the Rogue Wave Tools.h++ library class RWZone. Nathan Myers myersn(a)roguewave.com

1 0

Does anyone have the source for this function?
by aaron＠lehman.com March 22, 1994

March 22, 1994

Does anyone have a UNIX function for converting a time from timezoneX to timezoneY? I know how to write this by mucking with char** environ and by calling tzset(), but I'm interested in a more elegant solution (perhaps using fields in the tm structure). convert(timezoneX, timezoneY, inputTime, outputTime) The char** environ solution seems to me to be inelegant because 1) I have to reread a file whenever I call tzset() (I think), and 2) while I'm doing the conversion the call to tzset() has a global effect on my process. If I'm interrupted by a signal handler that displays the time it will be in a foreign timezone. aaron(a)lehman.com

1 0