Timeline for Who sets date/time automatically from the hardware clock at boot?
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 11 at 2:09 | history | edited | Seamus | CC BY-SA 4.0 | add information |
| Feb 11 at 1:56 | comment | added | Seamus | @Daniel: Have you actually tried Method 2? I ask b/c it seems to be a solution to a problem I've been having with an "embedded/SBC" system. And the hwclock-set script makes sense to me as it includes: /sbin/hwclock --rtc=$dev --hctosys. The if condition you mention is done early in the boot cycle & the system file has not yet been created. This (AIUI) is necessary for adjusting the system clock from the hardware clock IAW warnings in man hwclock. | |
| Feb 11 at 1:30 | history | edited | Seamus | CC BY-SA 4.0 | add information |
| Jul 11, 2023 at 15:04 | vote | accept | arminb | ||
| Jul 10, 2023 at 14:35 | comment | added | Daniel | That folder is being created early (much earlier than udev starts) so that script is useless. Moreover, commenting out that condition, will cause access denied errors on "hwclock" calls (when the script is called by udev). So it seems totally useless. | |
| Jul 10, 2023 at 14:34 | comment | added | Daniel | hwclock-set script has a condition for ".../system" folder. When it does exist, the script exits, leaving the clock intact. | |
| S Dec 10, 2021 at 15:30 | review | First answers | |||
| Dec 10, 2021 at 15:49 | |||||
| S Dec 10, 2021 at 15:30 | history | answered | arminb | CC BY-SA 4.0 |