Path: utzoo!mnetor!uunet!cbmvax!vu-vlsi!devon!paul
From: paul@devon.UUCP (Paul Sutcliffe Jr.)
Newsgroups: comp.sys.tandy
Subject: Re: Time on Tandy 3.2
Message-ID: <751@devon.UUCP>
Date: 13 Apr 88 17:22:04 GMT
References: <1618@scicom.alphacdc.com>
Reply-To: paul@devon.UUCP (Paul Sutcliffe Jr.)
Organization: Devon Computer Services, Lancaster, PA
Lines: 55
Summary: you need the 3.2 dev sys

In article <1618@scicom.alphacdc.com> cyrill Sun Apr 10 06:49:16 1988 writes:
+---------
| Reply direct to 'reo!root by mail as he doesn't get news.
+---------

Okay, I did.  But I decided to post this too, since others may benefit.

+---------
| The advent of Daylight Savings Time this past week has brought out
| an appearent bug in either XENIX 3.2 or MBASIC for the Tandy 16/6000.
| Both products are from Microsoft.  The "bug" is as follows:
| 
| 1.  uucp still executes its scheduled calls according to crontab
| entries, using Daylight time.  However, when it logs these, and all
| incoming calls, it logs them in STANDARD time (without an xST suffix).
| 
| 2.  When BASIC reads the time, such as in "PRINT TIME$", the time
| returned is, again, STANDARD time, not daylight.  I do not remember
| this problem occurring in previous years, under different versions
| of XENIX.
+---------

The 3.2 runtime system (the kernel and all utilities supplied with
it) were created with a new (improved!) ctime(S) call that knows about
the recent changes in DST rules.  In fact, the ruleset is in a text
file called /etc/usa.dst and can be modified and recompiled into
the kernel when necessary (smart move Tandy!).

However the 3.0 development system stuff (uucp, etc) are using the
old ctime() that won't acknowledge the DST change until the end
of this month.  The case you state in (1) is caused by the fact
that cron knows the new rules (it comes with 3.2 runtime), so it
invokes commands at the right time, but uucp doesn't, so its log
entries are off by 1 hour.

My temporary fix to this (until 3.2 development system is released)
was to run /etc/tz.  Answer the questions this way:

    Does daylight savings time apply at your location?	no
    Are you in north america?				no
    What is the name of your timezone?			EDT
    How many hours west of GMT are you?			4

This has the effect of changing TZ to say "TZ=EDT4" instead of
"TZ=EST5EDT" and then updating the appropriate files (/etc/rc,
/etc/default/login and others).  This technique was discussed last
year in various newsgroups.

- paul

-- 
Paul Sutcliffe, Jr.				       +----------------------+
						       |  THINK ...           |
UUCP (smart):  paul@devon.UUCP			       |            or THWIM  |
UUCP (dumb):   ...rutgers!bpa!vu-vlsi!devon!paul       +----------------------+