Hi team, I've found some misleading terms in the /etc/conf.d/hwclock file which I think should be changed to prevent confusion. *********************************************************************** # 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" *********************************************************************** Why wouldn't you need this if you run an ntp daemon? I run an ntp daemon and I still want my hardware clock to be up-to-date. *********************************************************************** # 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="YES" *********************************************************************** As for the above, what part of setting clock_hctosys to "YES" has anything to do with saving the _software_ clock to the _hardware_ clock? Apparently if I set that value to "NO", it will never save the software clock to the hardware clock: "the system time will never be saved to the hardware clock". This is misleading and/or incorrect because if I set it to "YES", it won't do that either; this parameter is strictly HC to SYS *only*. Here are my suggestions: * remove (or elaborate) # You normally don't need to do this if you run a ntp daemon. * remove or reword # 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. Reproducible: Always
This is fixed in commit a21a2c3. Thanks for the report.
