tuc;585229 Wrote: > Thanks Epoch1970, > > Yes I did miss the steps in spc-wakeup.sh completely. Sorry. > It now almost works, but not quite - the wake up occurs two hours too > late - weird > > Here is what I did: > 1) Complete the steps in spc-wakeup.sh > 2) The test command gives me the two lines: > Sun Oct 24 18:23:10 CEST 2010: /usr/local/sbin/spc-wakeup.sh > 1230493944 > Setting /sys/class/rtc/rtc0/wakealarm to 1230493944 (2008-12-28 > 19:52:24) > in in /var/log/squeezeboxserver/srvrpowerctrl.log > is this correct? > 3) I setup SrvrPowerCtrl to go to suspend mode after 45 minutes idle > time > 4) I set an alarm for 4:57 AM (I run a script at 5:01 AM from crontab) > 5) I schedule a library rescan in SBS for 4:01 AM > 6) Here is the /var/log/squeezeboxserver/srvrpowerctrl.log content: > Mon Oct 25 07:48:44 CEST 2010: /usr/local/sbin/spc-wakeup.sh > 1288065360 > Setting /sys/class/rtc/rtc0/wakealarm to 1288065360 (2010-10-26 > 03:56:00) > This corresponds to the scheduled rescan and looks right (wake up 5 > minutes before scan as set up in SrvrPowerCtrl). I don't see any entry > for the alarm (and I suppose I should) > 7) Here is what the /var/log/squeezeboxserver/server.log showed today: > [10-10-26 05:56:07.6149] > Plugins::SrvrPowerCtrl::Watchdog::OnWakeupWatchdog (347) Wakeup Call!! > [10-10-26 06:40:10.0037] Plugins::SrvrPowerCtrl::Util::SystemExecCmd > (310) Now trying to execute sudo /usr/local/sbin/spc-wakeup.sh > 1288151760 > [10-10-26 06:40:16.0039] Plugins::SrvrPowerCtrl::Util::SystemExecCmd > (310) Now trying to execute sudo /usr/sbin/pm-suspend > 8) I see no trace of my alarm set for 4:57. As far as I can tell both > the server.log and the SrvrPowerCtrl.log should show this, right? > 9) The machine did wake up for the rescan, but at 05:56:07 not at 5 > minutes before 4:01 (3:56) and the rescan did not run. My conclusion > there is a funny two hour difference between the scheduled wake up time > and the actual wake up time > 10) Running the date command from the command line gives me the correct > (local Danish) time (GMT+1) and we are still on daylight saving so > another +1 hour (=CEST) - is this an issue and how could I compensate? > > Best > -thomas Questions for you:
What operating system are you using? Is your hardware clock set to local time (as with windows and some versions of Ubuntu) or to UTC? From a terminal prompt, do: # sudo hwclock --show --debug Which variable are you using in the SrvrPowerCtrl settings for the "Schedule Wakeup Command"? %d or %l?? If your hardware clock is set to local time, then you should be using %l rather than %d. -- gharris999 ------------------------------------------------------------------------ gharris999's Profile: http://forums.slimdevices.com/member.php?userid=115 View this thread: http://forums.slimdevices.com/showthread.php?t=48521 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/plugins
