From: Daniel Dickinson <[email protected]>

On systems that have an RTC prefer it to the file-based time fixup (i.e.
use hwclock when there is a permanent clock instead of the faked up time
logic that is needed when there is not RTC).

We can't rely on hctosys kernel feature either as we're usually using
RTC as kernel modules which are usually being loaded after hctosys was
run, leading in the following error:

  hctosys: unable to open rtc device (rtc0)

Signed-off-by: Daniel Dickinson <[email protected]>
Signed-off-by: Petr Štetiar <[email protected]>
---
 Changes in v4:
 * simplified with using start() in boot() (blogic)

 package/base-files/files/etc/init.d/sysfixtime |   14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/package/base-files/files/etc/init.d/sysfixtime 
b/package/base-files/files/etc/init.d/sysfixtime
index 4010e06..ab946f6 100755
--- a/package/base-files/files/etc/init.d/sysfixtime
+++ b/package/base-files/files/etc/init.d/sysfixtime
@@ -2,10 +2,24 @@
 # Copyright (C) 2013-2014 OpenWrt.org
 
 START=00
+STOP=90
+
+RTC_DEV=/dev/rtc0
+HWCLOCK=/sbin/hwclock
 
 boot() {
+       start && exit 0
+
        local curtime="$(date +%s)"
        local maxtime="$(find /etc -type f -exec date -r {} +%s \; | sort -nr | 
head -n1)"
        [ $curtime -lt $maxtime ] && date -s @$maxtime
 }
 
+start() {
+       [ -e "$RTC_DEV" ] && [ -e "$HWCLOCK" ] && $HWCLOCK -s -f $RTC_DEV
+}
+
+stop() {
+       [ -e "$RTC_DEV" ] && [ -e "$HWCLOCK" ] && $HWCLOCK -w -f $RTC_DEV && \
+               logger -t sysfixtime "saved '$(date)' to $RTC_DEV"
+}
-- 
1.7.9.5
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Reply via email to