to a solution.
John
> -Original Message-
> From: Vidiot [mailto:[EMAIL PROTECTED]]
> Sent: Monday, November 06, 2000 10:48 AM
> To: [EMAIL PROTECTED]
> Subject: Re: System clock still not right
>
>
> >I had the same problem. Turned out I'd been hacked and one
>I had the same problem. Turned out I'd been hacked and one of its traits was
>file creating had the wrong stamp on it.
I have no other symptoms of being hacked.
This is just plain strange.
MB
--
e-mail: [EMAIL PROTECTED]
Bart: Hey, why is it destroying other toys? Lisa: They must have
I had the same problem. Turned out I'd been hacked and one of its traits was
file creating had the wrong stamp on it.
- Original Message -
From: "Vidiot" <[EMAIL PROTECTED]>
To: "RedHat main mail list" <[EMAIL PROTECTED]>
Sent: Monday, November 06, 2000 1:50 AM
Subject: System clock still
>assuming that you want the hw clock to run local time, then
>edit /etc/sysconfig/clock manually as follows:
>
>ZONE="your timezone" (taken from /usr/share/zoneinfo/, e.g. "US/Central")
>UTC=false
>ARC=false
>
>reboot after saving the file.
Been there, done that. It was originally the above and
>is /etc/localtime correct ?
It is a copy of /usr/share/zoneinfo/CST6CDT, which is indeed my timezone.
MB
--
e-mail: [EMAIL PROTECTED]
Bart: Hey, why is it destroying other toys? Lisa: They must have
programmed it to eliminate the competition. Bart: You mean like
Microsoft? Lisa:
On 06-Nov-00 Vidiot wrote:
>>I believe that is by design. One is supposed to use programs that are
>>smart enough to adjust for localtime when looking at file datestamps.
>>If they wrote the actual localtime to the bits on the hard drive, then
>>when you copy those bits to another computer that
On 06-Nov-00 Vidiot wrote:
>>If you have UTC true.. then you need to set the hardware clock to GMT. For
>>US/Central (GMT-6) if your localtime were, say, 12:00 then the hardware
>>clock should be 18:00. As far as why you're not getting the right dates on
>>stuff.. I'm sure it's something simple w
>I believe that is by design. One is supposed to use programs that are
>smart enough to adjust for localtime when looking at file datestamps.
>If they wrote the actual localtime to the bits on the hard drive, then
>when you copy those bits to another computer that is in a different
>timezone, it
>If you have UTC true.. then you need to set the hardware clock to GMT. For
>US/Central (GMT-6) if your localtime were, say, 12:00 then the hardware
>clock should be 18:00. As far as why you're not getting the right dates on
>stuff.. I'm sure it's something simple which someone will figure out. I
> What is wrong? All files are created with UTC/GMT time,
> instead of local
> time. Date shows localtime, as well as the OpenWindows
> clock. Yet, any
> file that is created is created with GMT time.
I believe that is by design. One is supposed to use programs that are
smart enough to adjust
If you have UTC true.. then you need to set the hardware clock to GMT. For
US/Central (GMT-6) if your localtime were, say, 12:00 then the hardware
clock should be 18:00. As far as why you're not getting the right dates on
stuff.. I'm sure it's something simple which someone will figure out. I
just
11 matches
Mail list logo
