Hi all,
After poking around a bit I ended up just going the
/etc/ntp/step-tickers route to resolve the issue and have the time
in-sync as soon as the OS comes up.
Thanks for all the help!
On Sat, Aug 11, 2012 at 7:15 PM, Gordon Messmer yiny...@eburg.com wrote:
On 08/09/2012 12:33 PM, Russell
On 08/09/2012 12:33 PM, Russell Jones wrote:
The hardware clock is configured in local time. /etc/sysconfig/clock
is set to UTC=false and ZONE=America/Chicago.
What other settings are in that file?
The system is treating your hardware clock as if it were UTC. Actually
setting it to UTC is
Hello Mark,
On Thu, 2012-08-09 at 17:03 -0400, m.r...@5-cent.us wrote:
Russell Jones wrote:
Also in case it wasn't clear, I have ran hwclock --systohc after
date shows the correct time.
Please don't top post.
I do agree. However Mark, perhaps *you* could trim your post too.
Regards,
Hello Russell,
On Thu, 2012-08-09 at 14:33 -0500, Russell Jones wrote:
After the system is up. hwclock works fine. hwclock --debug does not
show any error at all.
Have you tried adding --debug to CLOCKFLAGS in rc.sysinit to see if it
reports anything for the first invocation?
Regards,
On 9 Aug 2012, at 22:03, m.r...@5-cent.us m.r...@5-cent.us wrote:
Please don't top post.
Please trim your replies.
Ben
___
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
Hi all,
I am having an issue with some older CentOS 5.3 servers. Every time
the server boots, it gives the error Cannot access the hardware clock
by any known method, and then promptly sets the time 5 hours behind
the hardware clock, down to the second.
After the system is up. hwclock works
Russell Jones wrote:
Hi all,
I am having an issue with some older CentOS 5.3 servers. Every time
the server boots, it gives the error Cannot access the hardware clock
by any known method, and then promptly sets the time 5 hours behind
the hardware clock, down to the second.
So, it's
Thanks for the reply.
The hwclock can be set properly from the OS. No BIOS permissions to
even set for the clock, it's just a standard old 24 hour clock.
On Thu, Aug 9, 2012 at 2:43 PM, m.r...@5-cent.us wrote:
Russell Jones wrote:
Hi all,
I am having an issue with some older CentOS 5.3
On Aug 9, 2012, at 12:33 PM, Russell Jones wrote:
Hi all,
I am having an issue with some older CentOS 5.3 servers. Every time
the server boots, it gives the error Cannot access the hardware clock
by any known method, and then promptly sets the time 5 hours behind
the hardware clock, down
Thanks, I tried again, rebooted, still 5 hours off slow. The second I
do hwclock --hctosys the time is fine. That's silly to have to do
that though, I feel like I am missing a configuration parameter
somewhere.
[root@nod705 ~]# date
Thu Aug 9 10:06:36 CDT 2012
[root@nod705 ~]# hwclock
Thu 09
until you set your clock so that 'date' gives the right time, don't bother
doing anything else. Once you get it set, then execute the hwclock --systohc
Craig
On Aug 9, 2012, at 1:08 PM, Russell Jones wrote:
Thanks, I tried again, rebooted, still 5 hours off slow. The second I
do hwclock
Craig,
Let me clarify. I correct the time, and both date and hwclock both
show the correct time. I reboot the server and date is again 5 hours
slow.
On Thu, Aug 9, 2012 at 3:22 PM, Craig White craig.wh...@ttiltd.com wrote:
until you set your clock so that 'date' gives the right time, don't
Also in case it wasn't clear, I have ran hwclock --systohc after
date shows the correct time.
On Thu, Aug 9, 2012 at 3:30 PM, Russell Jones arjone...@gmail.com wrote:
Craig,
Let me clarify. I correct the time, and both date and hwclock both
show the correct time. I reboot the server and
Russell Jones wrote:
Also in case it wasn't clear, I have ran hwclock --systohc after
date shows the correct time.
Please don't top post.
Here's a question: run hwclock, then, when you reboot, go into the BIOS,
and see what the time is.
mark
On Thu, Aug 9, 2012 at 3:30 PM, Russell
Here's a question: run hwclock, then, when you reboot, go into the BIOS,
and see what the time is.
mark
Thanks Mark. hwclock showed the right time before reboot. After
reboot, entering BIOS it still showed the correct local time. After
the server came up, date is slow by 5 hours.
Russell Jones wrote:
Here's a question: run hwclock, then, when you reboot, go into the BIOS,
and see what the time is.
Thanks Mark. hwclock showed the right time before reboot. After
reboot, entering BIOS it still showed the correct local time. After
the server came up, date is slow by 5
On Thu, Aug 9, 2012 at 4:30 PM, m.r...@5-cent.us wrote:
Russell Jones wrote:
Here's a question: run hwclock, then, when you reboot, go into the BIOS,
and see what the time is.
Thanks Mark. hwclock showed the right time before reboot. After
reboot, entering BIOS it still showed the correct
on 8/9/2012 12:33 PM Russell Jones spake the following:
Hi all,
I am having an issue with some older CentOS 5.3 servers. Every time
the server boots, it gives the error Cannot access the hardware clock
by any known method, and then promptly sets the time 5 hours behind
the hardware clock,
On Thu, 2012-08-09 at 15:35 -0700, Scott Silva wrote:
on 8/9/2012 12:33 PM Russell Jones spake the following:
Hi all,
I am having an issue with some older CentOS 5.3 servers. Every time
the server boots, it gives the error Cannot access the hardware clock
by any known method, and then
On Aug 9, 2012, at 2:26 PM, Russell Jones wrote:
Here's a question: run hwclock, then, when you reboot, go into the BIOS,
and see what the time is.
mark
Thanks Mark. hwclock showed the right time before reboot. After
reboot, entering BIOS it still showed the correct local
On 08/09/2012 02:33 PM, Russell Jones wrote:
Hi all,
I am having an issue with some older CentOS 5.3 servers. Every time
the server boots, it gives the error Cannot access the hardware clock
by any known method, and then promptly sets the time 5 hours behind
the hardware clock, down to the
On Thu, Aug 09, 2012 at 04:40:19PM -0700, Craig White wrote:
On Aug 9, 2012, at 2:26 PM, Russell Jones wrote:
Here's a question: run hwclock, then, when you reboot, go into the BIOS,
and see what the time is.
mark
Thanks Mark. hwclock showed the right time before
On Thu, Aug 9, 2012 at 6:59 PM, Woodchuck mar...@pennswoods.net wrote:
On Thu, Aug 09, 2012 at 04:40:19PM -0700, Craig White wrote:
On Aug 9, 2012, at 2:26 PM, Russell Jones wrote:
Here's a question: run hwclock, then, when you reboot, go into the BIOS,
and see what the time is.
On Thu, Aug 09, 2012 at 07:11:02PM -0500, Russell Jones wrote:
On Thu, Aug 9, 2012 at 6:59 PM, Woodchuck mar...@pennswoods.net wrote:
Thanks for the help!
Dave: There are no options for time zones in the BIOS clock. The time
is just there to be set. It is currently set to 7:08 PM, which is
24 matches
Mail list logo
