Fake-hwclock is an hour out

[Jack Yaz]

Suspect it's caused by my location (UK) using BST. Do I need to make any changes to fake-hwclock to account for this?

 

[Cycle Mycle]

Suspect it's caused by my location (UK) using BST. Do I need to make any changes to fake-hwclock to account for this?

This has never worked for me (also UK) but it's possible to configure it to adjust for daylight saving manually and that works fine. You need to keep an eye on the calendar though as sometimes there are four Sundays in March or October and sometimes there are five e.g. set it for the 5th Sunday for October this year.

 

[GoNz0]

This has never worked for me (also UK) but it's possible to configure it to adjust for daylight saving manually and that works fine. You need to keep an eye on the calendar though as sometimes there are four Sundays in March or October and sometimes there are five e.g. set it for the 5th Sunday for October this year.

It's a shame they don't have a "last" option for the week as some of my other hardware has for the time change.

 

[redhat27]

fake is the keyword. It saves the system time to a persistent storage when called with "save" param. This would typically only save when your router is being rebooted. When your router comes up, the fake-hwclock is called with "load" that loads that saved time (with the time that your router was last seen when shutting down) the /opt/etc/init.d/S01fake-hwclock does this automatically as part of stopping and starting services.