gharris999;434782 Wrote: > 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.That is bad. The only reason why I need the "not idle" action is that I may resume playing music before the server hibernates. Otherwise it would have been enough to issue the "not idle" action at wake-up and the hibernate action after the idle timeout.
gharris999;434782 Wrote: > 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?LightsOut is > an energy manager for WHS. I find it quite embarrassing that something like LightsOut is not included in the first place. LightsOut has a calendar where you can schedule up and down times, it will automatically wake the server during the configured backup window, but most importantly, it will keep the server running while any WHS clients are connected, and hibernate the system when after an idle timeout no clients are connected, no up time is scheduled and no backup is currently running. The only problem with LightsOut is that it does not recognize SqueezeCenter clients, so if all your PCs are shut down, it will hibernate the server even if you are currently playing music. The ideal way for SPC to interface with LightsOut would be to register as another client, so LO would not hibernate the server as long as SPC signals an active client. Unfortunately, there is no interface that allows registration of additional clients. The current workaround is to change the timeout action setting for LightsOut. In the LightsOut configuration, you can choose what to do when the server is no longer needed. You can do nothing, suspend, hibernate or shut down. This choice is stored in the registry and constantly monitored by LightsOut. The VB script I wrote changes this value, so when LightsOut wants to send the system to bed while there is still music being played, the configured action will be "do nothing". As soon as SPC's idle timeout has been exceeded, the value will be changed to "hibernate" (or whatever else you choose to configure), and LightsOut appears to pick up the change pretty much instantly and send the server sleeping if there are no other known activities. gharris999;434782 Wrote: > 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.That appears to be the case, anyway, > and cannot be configured. gharris999;434782 Wrote: > 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).That was my first thought before I saw the tools at work, but the timeout value configure in LightsOut only refers to active clients and not to modifications of the timeout action setting. A change of the timeout setting will take effect, immediately. gharris999;434782 Wrote: > 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.This is an option if anybody actually > needs the IsIdleWaiting_cmd. gharris999;434782 Wrote: > 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?Can't you arrange for the watchdog to > wake up when a player starts streaming music? Or as an alternative, you could make the disabling of the watchdog after the idle timeout optional. gharris999;434782 Wrote: > This sort of approach ... will clutter up the settings pageTrue. -- mvordeme 'last.fm' (http://www.last.fm/user/mvordeme) | scaleo home server 2105 | squeezecenter 7.3.3 | server power control 20090622.17 | squeezebox boom & duet | rotel rsp-1066 | rotel rmb-100 | phonar p-5 ------------------------------------------------------------------------ mvordeme's Profile: http://forums.slimdevices.com/member.php?userid=22892 View this thread: http://forums.slimdevices.com/showthread.php?t=48521 _______________________________________________ plugins mailing list plugins@lists.slimdevices.com http://lists.slimdevices.com/mailman/listinfo/plugins
