mvordeme;429196 Wrote: > The current logic unfortunately requires both an idle and a not idle > signal to be written to the registry, but it probably would not hurt to > renew the not idle signal now and then if that is easier to implement. > The good thing about the registry solution is that you can choose for > the server to standby, hibernate or shut down, so apart from the timer > features, it can replace SCPowerTool completely. OK, I've had second thoughts. Forgetting the "not idle" signal, if the shutdown/restart/suspend/hibernate commands point to an executable or script that signals the "is idle" state in the registry and tells LightsOut what the appropriate next action should be, then really no changes to SrvrPowerCtrl are required at all. The user would just set SrvrPowerCtrl's on-idle time-out to a very short value and LightsOut's longer idle countdown will take up the slack. The only case where this wouldn't work is if the on-idle action is shutdown. In that case, SrvrPowerCtrl actually kills SqueezeCenter in order to help ensure a clean db close. I imagine that most folks don't force a complete hardware shutdown on idle, though.
If you can get me the full documentation on what LightsOut wants to see in the registry, I'll write the executable and we can begin testing. What about scheduled server wake-ups for alarms and such? Does LightsOut handle this too? Or should SCPowerTool continue performing this chore? -- 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
