mvordeme;434771 Wrote: > Does the dog bark as well when I start playing music again before the > server hibernates? This was the reason why the "not idle" command was > needed in the first place. I actually liked the idea that the hibernate > action was repeated occasionally, just in case someone else had been > playing with the LightsOut configuration in the mean time. The idle-watchdog would only get disabled at the expiration of the idle-timeout. Anytime between the last not-idle and idle-expire, if you start playing music, the idle-watchdog catches it. If there is significant lag time between sending the suspend/hibernation command and LightsOut actually putting the system to sleep...the idle-watchdog would be disabled and wouldn't hear any music playing and thus wouldn't catch it.
mvordeme;434771 Wrote: > At the moment, I am not sure what I would expect from a generic > watchdog, whether it should submit busy actions during the idle > countdown and whether it should repeat the hibernate action or not. In > the context of LightsOut, though, it would be nice if no busy actions > were submitted during countdown and if the hibernate would occasionally > be repeated. Maybe we should discuss this with the other potential > beneficiaries of the new SPC features. Tell me more about how LightsOut works. What's the function of the "not-idle" message you're writing to the registry? How quickly does LightsOut react to the "time to sleep" message in the registry? If LightsOut's reaction to the "time to sleep" message is configurable, then why not configure it to react as quickly as possible? Let the count-down delay happen in SrvrPowerCtrl. Or, if it makes more sense to have the delay-before-sleep countdown happening in LightsOut, then set SrvrPowerCtrl's idle-countdown to 0. (This will require a code change to allow values lower than 5, I believe). I could also make it so that there are three different custom idle-state commands: Playing: NotIdle_cmd gets executed. Not playing, but still counting down: IsIdleWaiting_cmd fires off. Countdown expired: IsIdle_cmd gets run. As soon as the IsIdle_cmd gets run, the idle-watchdog gets disabled and remains so until the wakeup-watchdog detects that the system has resumed. In cases where the system never goes to sleep, we could make it so that the idle-watchdog is automatically re-enabled after a suitable time out...e.g. 10 minutes? You could just configure the IsIdleWaiting_cmd as empty...so nothing happens. This sort of approach, while it will clutter up the settings page, would potentially give you more control. -- 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
