My orginial question/statement of irritation follows:
----------------------------------------------------
I have 8 DEC 3000/4000 running DU 3.0 and
one that is running DU 1.3. All of those systems
agree that today's date is Feb 29, 1996.
And no, I didn't install any patch to make this happen.
So what is the deal with DEC? I spent time on the phone
with a DEC support rep who told me that my systems
would report today's date as March 1. He told me that
I should definitely install these patches. He also said
that any time I needed to reboot these systems from Feb 29
thru March 31, I would have to boot to single user mode, set
the date, and continue on to multiuser mode, or my systems
would have messed up dates.
Apparently at least some of this isn't true. This whole issue
caused undue strain and I'm very unhappy with DEC.
Is anyone experiencing any problem with today's date?
-------------------------------------------------------------
The answer I got came from Martin Moore of the CSC both by
email and by phone.
>From: Martin Moore <martin_at_jerry.alf.dec.com>
>
>If a system just stays up and runs normally, the date will change from
>Feb 28 to Feb 29 to March 1 ... as it should. The problem comes in two
>areas:
>
>1. You can't set the date to 2/29 with the 'date' command.
>
>2. If you reboot your system in March, you'll lose a day on the clock.
As for the other CSC specialist who yesterday told me that my systems
would report March 1st as today's date, Martin said that specialist
was misinformed.
And so it goes.
Kathy
Received on Thu Feb 29 1996 - 16:19:55 NZDT