Conference smurf::buildhelp

2126.0. "Important - ODE Pools and Build Environment - Downtime Wednesday 2/28" by AOSG::FILTER (Automatic Posting Software - mail to flume::puck) Tue Feb 27 1996 15:17

Date Of Receipt: 	27-FEB-1996 14:55:04.74
From: 	SMURF::FLUME::"[email protected]" "Lucinda Mazza OSG/UES"
To: 	osf_developers@DEC:.zko.flume
CC: 	releng@DEC:.zko.flume, osf_ode_admins@DEC:.zko.flume,
	odehelp@DEC:.zko.flume, tresvik@DEC:.zko.flume, 33adms@DEC:.zko.flume
Subj: 	Important - ODE Pools and Build Environment - Downtime Wednesday 2/28

ODE Pools and Build Environment - Will be down Wednesday 2/28 from 7-8AM
				  to incorporate time/date patch
========================================================================
In order to implement an important patch to fix a Digital UNIX Date/Time 
problem, we will need to reboot several of the machines in the build 
environment.  This needs to be done before February 29th.

Tomorrow, Wednesday February 28th, we will take the following machines 
down and reboot them between the hours or 7am and 8am. 

	Buffer - RCS Server
	Secret - Submit Server
	KGB - ODE File Server
	NSA - ODE File Server
	CIA - ODE File Server
	FBI - ODE File Server
	INR - ODE File Server
	Burnit - Release Engineering Ris Server
	Baggy - PT Ris Server

What does this mean to you as a developer: 

        For developers at ALL sites, this means all ODE access to
        the OSF project pools will be locked. (ie: bco, blog, etc.)
        People will need to exit and re-start any workon sessions once
        the environment is back up.

        For developers at ZKO, it means all backing trees will be taken
        off line and will not be available for backing sandbox builds.

Please note that the nightly builds will not be impacted by the 
downtime.

We are recommending that any developers running Digital UNIX or OSF/1 
consider putting this patch on their system before 2/29 if possible.  In 
case you have not seen the patch, I have attached it for your 
convenience.

If you have any questions about the build environment downtime, please 
send mail to flume::mazza.  Any questions about the patch should be 
directed to Ron Uberti (guru::uberti).

Thank you for your support,

Regards, Lucinda Mazza
	 Digital UNIX Release Engineering

* * * * * * * * * * * * * * * * * *

Subject: 
        FYI - Digital UNIX Leap Year Problem 
  Date: 
        Tue, 27 Feb 96 13:45:16 -0500 
  From: 
        uberti
    To: 
        usg
    CC: 
        uberti



Attached are 3 messages regarding problems
pertaining to Leap  Year.  We have workarounds
and patches available for resolving these
problems.  We have notified all Customer
Service Centers world-wide regarding this issue.
We are also working on notifying our customer
base.

We are distributing this notification
to alert you of the problems and their resolution.

The 1st message describees the problems, in brief,
and also discusses workarounds.
 
The 2nd messsge is the first blitz which we
issued on February 12, 1996.

The 3rd message is the corrected blitz which also
adds support for V2.*


   Ron Uberti
   Digital UNIX Problem Management

=================================================================================
From: [email protected] (Michael W. Zaharee  
22-Feb-1996 1446)
To: [email protected]
Cc: ZAHAREE
Subject: Replaces previous reply.

If a machine without any patches is up and running and is not rebooted 
during
the month of March, the problem will not be seen.  Reboots will cause 
the loss
of a day.

A workaround for this would be to boot the system to single user mode, 
set the
date & time to whatever is appropriate, then continue the boot process 
to
multi-user mode.  This could be done on each powerup/reboot if it is not
possible to install the available patches.

A workaround for the 'date' command not taking the 29th would be to set 
the
date to the 1st of March and reboot, provided of course, the clock.o 
patch has
not been installed.

- - - - M

================================================================================

Return-Path: uberti
Message-Id: <[email protected]>
To: [email protected], [email protected]
Cc: [email protected], malcolm, [email protected], uberti,
        [email protected], [email protected],
        [email protected], [email protected],
        [email protected], [email protected]
Subject: BLITZ: Digital UNIX Systems Date/Time Problems - Leap Year
Date: Mon, 12 Feb 96 17:02:54 -0500
From: uberti
X-Mts: smtp


+---------------------------+TM
|   |   |   |   |   |   |   |
| d | i | g | i | t | a | l |      TIME   DEPENDENT   BLITZ
|   |   |   |   |   |   |   |
+---------------------------+



      BLITZ TITLE:  Digital UNIX Systems Date/Time Problems - Leap Year

                                                      DATE: 12-Feb-1996
      AUTHOR: Mike Zaharee                            TD #:
      DTN:    381-2479                                ENET: 
guru::zaharee
                                                      CROSS REFERENCE 
#'s:
      DEPARTMENT: Digital UNIX Support  Engineering   
(PRISM/TIME/CLD#'s)

      INTENDED AUDIENCE:  All                   PRIORITY LEVEL:  1
      (U.S./EUROPE/GIA)                         (1=TIME CRITICAL,
                                                 2=NON-TIME CRITICAL)
      
=====================================================================

On January 10th of this year USEG issued a BLITZ concerning a 
timekeeping
problem which can occur on Digital Unix when a system is in a powered 
off
state prior to midnight on New Year's Eve and booted after the 
transition to
the new year.

In the process of porting a fix for this problem to a number of versions 
of
Digital Unix we discovered several other serious timekeeping problems 
which
need to be addressed before the complete fix can be made available.

On Digital Unix systems the following behavior will be observed:

1) The 'date' command rejects February 29, 1996 (or any other leap
   year) as a valid date.
2) When the system time is changed with the 'date' to any date in March
   of a leap year and then rebooted, the system clock will lose
   one day.

The first problem is the result of the libc routine strptime not 
recognising
February 29th of a leap year as a valid date.  The 'date' command makes 
use of
strptime in the processing of the time.  The problem is fixed in Digital 
Unix
V3.2c and later and corrected by patch OSF300-234 for V3.0, OSF305-234 
for
V3.0b, OSF-320-214 for V3.2, and OSF3250-32191 for V3.2b.  These are 
already
available from the CSC, unfortunately, the README documentation does not 
point
out the implication of this defect.

The second problem is the result of an improper check for February of a 
leap
year in the kernel routine resettodr which is found in the kernel module
clock.c.  The uncorrected routine will fail to add a days worth of 
seconds to
the TOY clock during the month of March of a leap year when adjustment 
to the
system time is made.  USEG has prepared an interim fix for this problem.
Corrections for V3.0, V3.0b, V3.2, V3.2b, V3.2c and V3.2d can be found 
in the
compressed tar archive found at 
guru:/usr/guest/misc/osf/clock_patches.tar.Z.

================================================================================


Forwarded: Fri, 23 Feb 96 10:29:25 -0500
Forwarded: mse1::safford uberti
Forwarded: Tue, 20 Feb 96 13:30:23 -0500
Forwarded: [email protected] uberti  
[email protected] zaharee
Return-Path: uberti
Message-Id: <[email protected]>
To: [email protected], [email protected]
Cc: [email protected], malcolm, [email protected], uberti,
        [email protected], [email protected],
        [email protected], [email protected],
        [email protected], [email protected]
Subject: BLITZ: ** Correction ** Digital UNIX Date/Time Problems - Leap 
Year
Date: Tue, 20 Feb 96 11:21:43 -0500
From: uberti
X-Mts: smtp


+---------------------------+TM
|   |   |   |   |   |   |   |
| d | i | g | i | t | a | l |      TIME   DEPENDENT   BLITZ
|   |   |   |   |   |   |   |
+---------------------------+



   BLITZ TITLE: ** Correction **  Digital UNIX Date/Time Problems - Leap 
Year

                                                      DATE: 20-Feb-1996
      AUTHOR: Mike Zaharee/Ron Uberti                 TD #:
      DTN:    381-2479                                ENET: 
guru::zaharee.
              381-1851                                      guru::uberti
                                                      CROSS REFERENCE 
#'s:
      DEPARTMENT: Digital UNIX Support  Engineering   
(PRISM/TIME/CLD#'s)

      INTENDED AUDIENCE:  All                   PRIORITY LEVEL:  1
      (U.S./EUROPE/GIA)                         (1=TIME CRITICAL,
                                                 2=NON-TIME CRITICAL)
      
=====================================================================

On Febrary 12th of this year USEG issued a Blitz concerning several
timekeeping problems in Digital Unix.

For reference, the problem definition was:

"On Digital Unix systems the following behavior will be observed:

 1) The 'date' command rejects February 29, 1996 (or any other leap
   year) as a valid date.
 2) When the system time is changed with the 'date' to any date in March
   of a leap year and then rebooted, the system clock will lose
   one day. "

The Blitz referenced several patches available from the CSC
(OSF300-234, OSF305-234, OSF320-214 and OSF325-320191).
A problem has been discovered with the copy of the 'date' command 
included in
these patches.  A copy of the 'date' command which corrects these 
problems
has been packaged with the corrections to clock.o and placed in the
tar archive found at 
guru:/usr/guest/misc/osf/clock_patches_update.tar.Z.

Additionally, corrections which support V2.0, V2.0b, & V2.1 have been 
added
to the archive.  See the README included for instructions.
===========================================================================