[% PROCESS helpheader.html %]
SrvrPowerCtrl's job is to help you control power states (sleeping / waking / etc.) on your Squeezebox Server hardware. To do that, SrvrPowerCtrl needs to be able use some “helper” applications on your server. These applications differ according to which operating system you are using on the Squeezebox Server machine. But whatever your server setup, you'll need to do a certain amount of manual tweaking of those helper applications and SrvrPowerCtrl's settings in order to get things working as they ought. Hopefully, these instructions will help you get everything set “just right.”
To finish installing SrvrPowerCtrl for RedHat and like distros, you'll need to make sure that the following command is available from a terminal prompt:
Additionally, to support suspend and hibernation, the pm-utils package must be installed. Check to see that these commands are run-able from a terminal prompt as well:
Not all linux distros include those commands in a default installation. Consult your distro's documentation for adding (if necessary) the sudo, shutdown and pm-utils packages.
To finish installing the plugin for Redhat, Fedora, CentOS and other like distributions, do the following:
Open a terminal window: Applications→System Tools→Terminal.
Do the following: make the setup script file executable and then execute it by copying and pasting these commands into the terminal window:
Next, verify that the '[% sbsuser %]' user now has permission to shutdown the system without raising any prompts. We'll do this by running a test script which performs a FAKE shutdown...your system won't actually halt, but we will be able to test to see that permissions have been correctly set. In the terminal window, try executing the following command:
The sudo command may prompt you for YOUR password, which is appropriate in this case. If the script responds with SUCCESS!, then the plugin ought to be able to shutdown/restart/etc your system from the [% sbsservername %] service. If, however, the script responds with ERROR!, then something is amiss. If this is the case, try running the setup script again. Remember, the test script won't actually shutdown your system.
Finally, your hardware may require adding “quirks” to the pm-suspend command line in order for S3 sleep/suspend and resume to function properly. Unfortunately, this can only be determined by trial and error. See the Sleep Quirk Debugger page for more information. If your testing shows that
“quirks” are required by your server hardware, then be sure to add them to the pm-suspend command line at [% sbsservername %]→Settings→Plugins→SrvrPowerCtrl→Settings→Suspend Command:
If your distro is not RedHat or Fedora, it may use different commands to initiate a shutdown/restart/suspend/hibernation. If so, edit the command lines on the [% sbsservername %]→Settings→Plugins→Server Power Control→Settings page accordingly.
If you'd prefer to make your linux system settings changes manually (rather than using the above setup script) please consult the readme.txt file for steps you'll need to carry out.
[% "PLUGIN_SRVRPOWERCTRL_BACKTO_HELP_PAGE" | string %] | [% "PLUGIN_SRVRPOWERCTRL_TROUBLESHOOTING_HELP_PAGE" | string %] | [% "PLUGIN_SRVRPOWERCTRL_HOME_PAGE" | string %] |