On Mon, Feb 6, 2012 at 1:46 PM, Dale <[email protected]> wrote:
> [email protected] wrote:
>> Hi,
>>
>> to get the correct system time I use ntp-client in the boot process.
>> Furthermore in /etc/conf.d/hwclock I set:
>>
>>     # Set CLOCK to "UTC" if your Hardware Clock is set to UTC (also known as
>>     # Greenwich Mean Time).  If that clock is set to the local time, then
>>     # set CLOCK to "local".  Note that if you dual boot with Windows, then
>>     # you should set it to "local".
>>     clock="UTC"
>>
>>     # If you want to set the Hardware Clock to the current System Time
>>     # (software clock) during shutdown, then say "YES" here.
>>     # You normally don't need to do this if you run a ntp daemon.
>>     clock_systohc="YES"
>>
>>     # If you want to set the system time to the current hardware clock
>>     # during bootup, then say "YES" here. You do not need this if you are
>>     # running a modern kernel with CONFIG_RTC_HCTOSYS set to y.
>>     # Also, be aware that if you set this to "NO", the system time will
>>     # never be saved to the hardware clock unless you set
>>     # clock_systohc="YES" above.
>>     clock_hctosys="NO"
>>
>>     # If you wish to pass any other arguments to hwclock during bootup,
>>     # you may do so here. Alpha users may wish to use --arc or --srm here.
>>     clock_args=""
>>
>> In the kernel config file I had set:
>>
>>     CONFIG_RTC_HCTOSYS=y
>>     CONFIG_RTC_HCTOSYS_DEVICE="rtc0"
>>
>> I would exspect that after a reboot of the system which system time is
>> correctly set via ntp-client that the hwclock and system time only
>> differ in a small amount of time.
>>
>> But:
>> solfire:/home/mccramer>hwclock
>> Mon Feb  6 19:05:11 2012  -0.172569 seconds
>> solfire:/home/mccramer>date
>> Mon Feb  6 18:49:37 CET 2012
>> solfire:/home/mccramer>
>>
>> Is there anything else which I have to tweak to acchieve what I want?
>>
>> Thank you very much in advance for any help!
>>
>> Best regards,
>> mcc
>>
>> PS: I need a correct hwclock since I want to wake the system via the
>> hwclock.
>>
>>
>>
>>
>
>
> I ran into some issues when I rebooted and I had to set both
> clock_systohc & clock_hctosys to yes.  That worked for me at least.  One
> sets the BIOS at shutdown and the other loads from the BIOS when
> rebooting.
>
> Yours may need something else but if nothing else works, try that.

I think he's trying to depend on the kernel keeping the hw clock in
sync with the sw clock, and that part's not working for some reason.

It's a reasonable thing to desire, since an unplanned or ungraceful
shutdown could miss the sw-to-hw step.

-- 
:wq

Reply via email to