danco;482410 Wrote: > Fair enough. > > I don't put my server to sleep when the SB is idle. In fact, I would > regard that as inconvenient, as I might well be doing something on my > computer at a time when the SB is idle. Rather,when the SB becomes idle > I stop the program that prevents sleep, so that other action on the > computer determines whether or not it sleeps. > > I would, on the whole, prefer something that did not trigger the "when > not idle" action on wake-up unless the SB was actually doing something. > But maybe this is hard to achieve. > > As I said, for my own needs it's fine, once I realised what was > happening. But it might affect others. In your post, you refer both to a 'server' and a 'computer'. Are they one and the same machine? Or are you running SBS on a server that serves up other content for other purposes?
SrvrPowerCtrl really has only taken baby steps in the direction of being a 'full service' power manager. Really, it's always been about managing power states for a dedicated, headless Squeezebox Server computer. Epoch1970 has suggested expanding SrvrPowerCtrl's 'portfolio' in the past..but I've been resistant...mainly out of concern for the complexities in implementing and supporting system-level activity monitoring (disk, network, keyboard, mouse, etc) on four different platforms (debian, redhat, osx, windows). The only tippy-toe I've dipped into actual system programming on this project has been to write SCPowerTool for windows...and that code is 'one-way'...i.e. it carries out commands on behalf of the plugin...but doesn't report system info back to the plugin. As an intermediate step, there is the 'auto-block on login' script for OSX. Epoch1970 has posted some code that ought to enable that behavior on Linux distros too, but I have yet to be able to test that. I do hope to get his work incorporated into SrvrPowerCtrl sometime in the next few weeks. And I'd like to figure out how to do the same for windows too. How useful would you find such a feature? In this scenario, when you are logged in, SrvrPowerCtrl gets automatically blocked and won't take any actions. Once you logout and the system is waiting for the next user logon, SrvrPowerCtrl is active and will take action after idle periods expire, etc. Again, this feature would be purely optional and operates by hooking the system logon event, triggering a script that sets a SrvrPowerCtrl block, clearing it on logoff. Obviously, for folks who prefer to have their machines autologon and keep the same user logged in permanently, such a feature is pretty useless...as it would be on headless servers too. -- 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
