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 v2: * use short form for file existence testing * use /dev/rtc0 instead of /dev/rtc for RTC checking * additionaly check for hwclock binary existence also * tell hwclock explicitly which device to use as RTC source * inform about the RTC time change in the log package/base-files/files/etc/init.d/sysfixtime | 15 +++++++++++++++ 1 file changed, 15 insertions(+) diff --git a/package/base-files/files/etc/init.d/sysfixtime b/package/base-files/files/etc/init.d/sysfixtime index 4010e06..ec04d1a 100755 --- a/package/base-files/files/etc/init.d/sysfixtime +++ b/package/base-files/files/etc/init.d/sysfixtime @@ -2,10 +2,25 @@ # Copyright (C) 2013-2014 OpenWrt.org START=00 +STOP=90 + +rtc_dev=/dev/rtc0 +hwclock=/sbin/hwclock boot() { + [ -e "$rtc_dev" ] && [ -e "$hwclock" ] && $hwclock -s -f $rtc_dev && 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
