chris.mason;507758 Wrote: > Gordon, > > Apologies for not getting back to you with logging info on the issue > with CLI issued blocks not being cleared, and automated shutdown not > working. > > I had to rebuild my server in the end, and installed Ubuntu 9.10, and > SBS 7.4.2, and am hence using the beta version of SrvrPowerControl. > > I'm using the Monitor Idle Players facility to suspend the server on > player inactivity (I'm able to do this, because I have FINALLY figured > out how to get WOL from suspend working, so restarting takes 5 seconds > instead of a minute). > > I also use the End of Day facility, to shutdown the server, and switch > the players to MySqueezeBox.com. > > It occurred to me that Idle, and EOD facilties could clash, so I've > been exploring how to set RTC wakeup times (stimulated by your helper > scripts). > > I noticed when checking /proc/driver/rtc (and also the srvrpowercontrol > log file) that an alarm had been set for 10:19pm, 1 minute before I have > EOD start to check for idle players. In my testing, I have been using > the "Alarm interactions" facility to wake up the server before an alarm > (which works very well, even if the server is shutdown - S5), and I'd > set that to wake 1 minute before the alarm. > > Maybe it is a coincidence, but have you tied Monitor Idle and EOD using > the Alarm Interactions facility? Fantastic if you have, saves me some > work! > > Chris. Yes. If the EOD (End of Day) action is set to a custom script or if the EOD action is not equal to the regular idle action, then the EOD start time is treated as an alarm.
Typical use case for me: my EOD time starts at 2am, ends at 2:05, has the 'allowed idle time' set to 0 (zero), and has the action command set to run a custom script. That script performs operating system updates, Squeezebox Server updates (via svn) and other chores. When the previous on-idle suspend occurred, the plugin set a alarm wake-up so that the server would wake up at 1:55 in order to "service" the EOD action. At the end of my custom EOD action script, the server gets rebooted. Because I have the 'allowed idle time' for the EOD set to 0 (zero), when the server restarts, the plugin "sees" that it's already within the EOD period and so it doesn't fire off the custom script a 2nd or 3rd time. This is a special case: EOD_idle_time == 0 means that a EOD action gets called just once. I will eventually tweak this behavior one more time. The new behavior that I'm planning will call for the EOD watchdog to ignore the custom command (if present) and instead call the action selected in the EOD idle-action drop down list. That will allow me to extend the EOD period and have the server suspend sooner after the custom script chores have completed. The Idle Player Monitor and the End of Day monitor should never conflict. While the plugin senses that it is "in" the EOD period, it just checks the EOD watchdog, and ignores the idle watchdog. -- 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
