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.roth@xxxxxxxxx> wrote:
> 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 obviously setting it to GMT.
>
>> After the system is up. "hwclock" works fine. hwclock --debug does not
>> show any error at all.
>>
>> The hardware clock is configured in local time. /etc/sysconfig/clock
>> is set to UTC=false and ZONE="America/Chicago". /etc/localtime is a
>> copy of Chicago's zone file. /etc/adjtime is configured with "LOCAL"
>> as the third row. I am at a loss as to what is causing this.
>>
>> Any assistance is appreciated! Thanks!
>
> Wonder if there's some permission or ownership problem.... You might also
> check in the BIOS, if some protection is turned on.
>
> mark
>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
