On Wed, 26 Jun 2002, Tom Pollerman wrote:
>See 'man hwclock.'
> " hwclock --systohc
> Set the Hardware Clock to the current System Time."
>
>If your hardware clock was correct, and your system clock was 4
> hours off, your
>
> From: "Robert P. J. Day" <[EMAIL PROTECTED]>
>
>
> i am getting increasingly baffled with what my HW clock and system
> clock are doing on my dell inspiron.
>
> i started with both clocks set to 11 am wednesday and, on my dell,
> i can pop
i am getting increasingly baffled with what my HW clock and system
clock are doing on my dell inspiron.
i started with both clocks set to 11 am wednesday and, on my dell,
i can pop into the bios whenever i want to see the HW clock. it
agreed with both "date" and "hwcloc
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 0
>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
I installed a KVM, so I had my Linux box down.
I've played with the settings to try and get the time information to be
correct, but no luck.
/etc/sysconfig/clock:
ZONE="US/Central"
UTC=true
ARC=false
I've tried it with UTC also set to false. No change. I've set the ha
At 12:18 AM 12/1/99 -0800, Todd A. Jacobs wrote:
>My system clock always reads 30 minutes fast after a reboot. I set my
>system clock daily using rdate, followed by setclock to set the hardware
>clock. I don't experience any significant time slippage when the system is
>running
On Wed, 1 Dec 1999, Todd A. Jacobs wrote:
> My system clock always reads 30 minutes fast after a reboot. I set my
> system clock daily using rdate, followed by setclock to set the hardware
> clock. I don't experience any significant time slippage when the system is
> running
My system clock always reads 30 minutes fast after a reboot. I set my
system clock daily using rdate, followed by setclock to set the hardware
clock. I don't experience any significant time slippage when the system is
running normally. However, after any reboot, the time is always arou
One thing you will have to take into acount when changing the system time
is that deamons which rely on time information can get "confused" when
they find files that are made in the future for example, so
better not change the system time of a running system!!! set up all the
timezone stuff and th
clock -a sets the system time from the CMOS clock. clock -w sets the CMOS
clock from the system time.
Gene
On Wed, 10 Jun 1998, Mauricio Teixeira wrote:
> Hi!
>
> I had a Slackware system here, but switched to RedHat 4.2, but
> since them the system clock has been set to
On Wed, 10 Jun 1998, Mauricio Teixeira wrote:
> Hi!
>
> I had a Slackware system here, but switched to RedHat 4.2, but
> since them the system clock has been set to 2 hours more than the BIOS
> clock, I mean: BIOS=12pm System=14pm.
>
> How do I make my syst
Hi!
I had a Slackware system here, but switched to RedHat 4.2, but
since them the system clock has been set to 2 hours more than the BIOS
clock, I mean: BIOS=12pm System=14pm.
How do I make my system clock use the same time as the BIOS clock
>On Mon, Mar 23, 1998 at 04:32:05PM -0600, Vidiot wrote:
>>
>> I don't know what is part of the "nist" package, but the protocol to go
>> out over the net to obtain the time is "ntp" (Network Time Protocol) and
>> it uses the TCP and UDP port 123.
>>
>a simple "telnet hostname 13" will get time
On Mon, Mar 23, 1998 at 04:32:05PM -0600, Vidiot wrote:
>
> I don't know what is part of the "nist" package, but the protocol to go
> out over the net to obtain the time is "ntp" (Network Time Protocol) and
> it uses the TCP and UDP port 123.
>
a simple "telnet hostname 13" will get time of day
>On Sun, Mar 22, 1998 at 05:52:40PM +, Gee Gwaltney wrote:
>> I'm looking for rdate or something similar to have the National Standard
>> update the system clock. Would someone point me to where I can find rdate?
>> Thanks in advance.
>
>look for the "ni
On Sun, Mar 22, 1998 at 05:52:40PM +, Gee Gwaltney wrote:
> I'm looking for rdate or something similar to have the National Standard
> update the system clock. Would someone point me to where I can find rdate?
> Thanks in advance.
look for the "nist" rpm. i think you
Gee Gwaltney <[EMAIL PROTECTED]> on Sun, Mar 22, 1998 at 05:52:40PM +:
> I'm looking for rdate or something similar to have the National Standard
> update the system clock. Would someone point me to where I can find rdate?
> Thanks in advance.
You might also wan
I'm looking for rdate or something similar to have the National Standard
update the system clock. Would someone point me to where I can find rdate?
Thanks in advance.
Gee
--
PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /R
28 matches
Mail list logo
