wakeup with seconds works perfectly - but using a time it is behaving strange.
hwclock is UCT: Thu Jun 27 19:20:31 2013 0.000000 seconds
date (system time) is local: Thu Jun 27 21:20:52 CEST 2013
I try:
Quote:
timestp=`date +%s`
let timestp+=30
echo `date`
/mnt/onboard/busybox_kobo rtcwake -u -t $timestp -m mem
|
output:
Thu Jun 27 21:13:45 CEST 2013
wakeup from "mem" at Thu Jun 27 21:14:15 2013
no wakeup
wakeup from "mem" at Thu Jun 27 21:14:15 2013
but also no wakeup
my assumption: rtcwake is using the hwclock
but when I adjust the system time backwards with hwclock -s -l (instead of -s -u like in rcS):
hwclock is UTC: Thu Jun 27 19:29:48 2013 0.000000 seconds
date is: Thu Jun 27 19:30:16 CEST 2013
Then I execute
Quote:
timestp=`date +%s`
let timestp+=30
echo `date`
/mnt/onboard/busybox_kobo rtcwake -a -t $timestp -m mem
|
output:
Thu Jun 27 19:29:03 CEST 2013
wakeup from "mem" at Thu Jun 27 19:29:33 2013
and yes - a wakeup
seems to work - but now the issue is, that cron does not work anymore because it is using the system time -which is now 2hrs off
any idea?