Time in @TM

[Jean-Pierre A. Radley]

Jay R. Ashworth propounded (on Fri, Mar 23, 2007 at 08:10:47PM -0500):
| On Fri, Mar 23, 2007 at 04:06:57PM -0700, Rodgers Hemer wrote:
| > Please note that the standard /etc/TIMEZONE never explicitly states  
| > the beginning and end of DST, only that it is used and the time zone  
| > of the server.  SCO has to look elsewhere for the start and stop dates.
| 
| To be clear, the standard setting of TZ does not *override* the
| timezone rules built into the libraries, which are occasionally updated
| to conform to various civil rulemakings.
| 
| If and when SCO issues official changes, and you install you should
| *remove* the override from your /etc/TIMEZONE to avoid future problems.

Users outside of North America or Oz have always had to use the longer
explict start|stop format of the TZ variable.  But for North America and
Oz, libc had carnal knowledge of the start|stop dates of DST, including
each change made by the civil authorities over the last 30 years, so that
the shorter TZ format sufficed for those privileged geographies.

The patches that SCO has issued (for UW 7.12.4, OSR 5.0.7, and OSR 6.0.0
are in libc|libc.so.  If a program was compiled using static libraries
(which was the case for filePro modules up to 5.0.14), **it will not
(can not) see** the changes just now made to libc|libc.so.

-- 
JP
	==> http://www.frappr.com/cusm <==