-BEGIN PGP SIGNED MESSAGE-
>> FWIW they announced this a month or so ago on (IIRC) BugTraq. I
>> understand that it's a once-only problem, the "Y2K+1" bug. Har har har
>> har har har har.
I seem to remember reading about it long ago. Yes, it's retarded, but
it's also true that server
Is it just coincidence that this is for April's 1st? Aprils fools.
- Original Message -
From: "Mike Watson" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, April 04, 2001 7:59 PM
Subject: Re: Micro$oft strikes again!
> We discovered
ROTECTED]>
Sent: Wednesday, April 04, 2001 4:41 AM
Subject: Re: Micro$oft strikes again!
> I had to set the time on all my Linux machines which were not running at
> the switch over time.
>
>
> david
>
> On Tue, 3 Apr 2001, Mike Watson wrote:
>
> > Well MS did it to
We discovered the fix M$ distributed doesn't work. They've know about the
bug for 5 years and never fixed it. The bug only hits when savings time
switches on 04/01. If we leave if along, it'll fix itself next week. In the
mean time, all our real-time messaging is one hour off. It can cost us B
CTED] [mailto:[EMAIL PROTECTED]]En
nombre de [EMAIL PROTECTED]
Enviado el: Miércoles, 04 de Abril de 2001 10:27
Para: [EMAIL PROTECTED]
Asunto: RE: Micro$oft strikes again!
It would all be so much easier if you ignored daylight savings time like we
do here in Saskatchewan. Queensland, Australia h
On Wed, 4 Apr 2001, Bret Hughes wrote:
> Mike Chambers wrote:
>
> > My linux box changed over but once I rebooted it went back to the other
> > time. I had to go in this morning to the BIOS and change it.
> >
> > Mike
>
> This occurs if you set your machine to "local" time rather than UCT (GMT).
You can do this with timetool (from the control-panel), but the main
thing is to make sure that /etc/sysconfig/clock has the right content.
My RH7 one is
ZONE="America/New_York"
UTC=true
ARC=false
My RH6 one is
ZONE="US/Eastern"
UTC=true
ARC=fals
"Michael R. Jinks" wrote:
>
> FWIW they announced this a month or so ago on (IIRC) BugTraq. I
> understand that it's a once-only problem, the "Y2K+1" bug. Har har har
> har har har har.
>
If I read the same article, it's not a once only problem. It said
something about it happening when April
nsland, Australia has followed our lead. Much
> less hassle :)
>
> Rob
>
> > -Original Message-
> > From: Mikkel L. Ellertson [mailto:[EMAIL PROTECTED]]
> > Sent: Wednesday, April 04, 2001 9:21 AM
> > To: Red Hat Mail List
> > Subject: Re: Micro$oft
2001 9:21 AM
> To: Red Hat Mail List
> Subject: Re: Micro$oft strikes again!
>
>
> On Wed, 4 Apr 2001, David Brett wrote:
>
> > When I tried setting the BIOS clock to UTC time. I was
> unable to get the
> > time displayed in local time. Not a problem with the os
On Wed, 4 Apr 2001, David Brett wrote:
> When I tried setting the BIOS clock to UTC time. I was unable to get the
> time displayed in local time. Not a problem with the os, just my
> understanding of how to make it work.
>
>
> david
>
An easy fix. Run timeconfig.
When I tried setting the BIOS clock to UTC time. I was unable to get the
time displayed in local time. Not a problem with the os, just my
understanding of how to make it work.
david
On Wed, 4 Apr 2001, Matthew Saltzman wrote:
> You wouldn't if you kept your BIOS clock set to UTC instead of lo
You wouldn't if you kept your BIOS clock set to UTC instead of local time.
Matthew Saltzman
Clemson University Math Sciences
[EMAIL PROTECTED]
On Wed, 4 Apr 2001, David Brett wrote:
> I had to set the time on all my Linux machines which were not running at
> the switch over tim
AM
Subject: Re: Micro$oft strikes again!
> On Wed, Apr 04, 2001 at 07:41:02AM -0400, David Brett wrote:
> > I had to set the time on all my Linux machines which were not running at
> > the switch over time.
>
> You did? I'd have to check again to be sure, but I am s
On Wed, Apr 04, 2001 at 07:41:02AM -0400, David Brett wrote:
> I had to set the time on all my Linux machines which were not running at
> the switch over time.
You did? I'd have to check again to be sure, but I am sure that my old
machine handled the timechange correctly, and it wasn't running
I had to set the time on all my Linux machines which were not running at
the switch over time.
david
On Tue, 3 Apr 2001, Mike Watson wrote:
> Well MS did it to us again. NT4.0 has a bug for switching to savings time.
> MS missed the date by a week! We had to manually set the time offset
> m
Well MS did it to us again. NT4.0 has a bug for switching to savings time.
MS missed the date by a week! We had to manually set the time offset
manually. In a week, we'll have to set it back when NT correctly figures
out that savings time has arrived. Appears to only occur on servers
though.
17 matches
Mail list logo
