Long-time readers of this group may recall a problem that was reported
at the beginning of 1996, in which Digital UNIX (or OSF/1) systems that
were shut down over the New Year's holiday had an incorrect system date
when booted for the first time in the new year.
This notice is to advise all system administrators that the problem is
potentially still out there for systems earlier than version 3.2G. Patches
exist for versions 3.0 through 3.2f. These patches are available for
anonymous FTP at the location listed below.
The following text is taken from a letter that was sent to Digital customers
in early December:
=========================================================================
Problem Description
--------------------
Every system running a version of Digital UNIX earlier than V3.2G is vulnerable
to a problem that may produce an incorrect system date/time under special
circumstances occurring around the end of a calendar year. This problem does not
affect systems running V3.2G or later of Digital UNIX. Version V4.0 and
its variants are not affected by this problem.
If any system fitting this description is shutdown prior to January 1 and is
not rebooted until January 2, the system date/time can be incorrect at boot
time.
Workaround
-----------
There are two workarounds to this problem:
1. DO NOT shut the system down from before January 1 until January 2. If the
system is not shut down when a new year begins, the system will maintain
the correct system date/time.
2. If the system date/time becomes incorrect due to the reasons explained
above, reset the system date/time manually using the UNIX 'date' command.
Solution
---------
As released, versions V3.2G and later of Digital UNIX incorporate changes to
prevent this problem from occurring. No patches are needed for these versions.
Digital UNIX Engineering has developed fixes for this problem for all supported
versions of Digital UNIX prior to V3.2G, specifically:
V3.0, V3.0B, V3.2, V3.2B, V3.2C, V3.2D-1, V3.2E-1, V3.2D-2,
V3.2E-2, and V3.2F
Digital has packaged the fixes to this problem into patch kits, which are
available from your normal Digital support channels.
Digital UNIX Engineering strongly recommends that the appropriate patch be
applied to every pre-V3.2G Digital UNIX system which may be shutdown when the
the new year begins.
Please note that the appropriate patch kit must be reapplied after installation
to or upgrade to any version of Digital UNIX up to and including V3.2F.
Also, as usual, please refer to the README file which is packaged with the
patch kit prior to applying any of the patches on your system.
=========================================================================
[End of customer letter excerpt]
The patches are available via anonymous FTP from atlanta.service.digital.com
under the following directory hierarchy:
/pub/mandatory_upgrades/AXP/OSF1
Specific patch kits for each version are under this directory as follows:
3.0 ./v3.0/toy_clock_v30.tar.Z
3.0b ./v3.0b/toy_clock_v30b.tar.Z
3.2 / 3.2a ./v3.2/toy_clock_v32.tar.Z
3.2b ./v3.2b/toy_clock_v32b.tar.Z
3.2c ./v3.2c/toy_clock_v32c.tar.Z
3.2d-1 / 3.2e-1 ./v3.2d-1/toy_clock_v32de1.tar.Z
3.2d-2 / 3.2e-2 ./v3.2d-2/toy_clock_v32de2.tar.Z
3.2f ./v3.2f/toy_clock_v32f.tar.Z
Prior to 3.0 - No patches available (versions no longer supported).
3.2g and higher - No patches necessary (problem is fixed).
Please direct any questions regarding retrieving or installing these patches
to gw-admin_at_alf.dec.com. Do *NOT* send any other questions or problem
reports to that address (or to me, either); please use your regular support
channels for any such.
Thank you.
--
Martin J. Moore 5555 Windward Parkway West
Digital UNIX Support Alpharetta GA 30201-7407
Digital Equipment Corporation 1-800-354-9000 x31679
martin_at_alf.dec.com DECATL::MARTIN
Received on Mon Dec 30 1996 - 17:20:18 NZDT