66
edits
Changes
From SME Server
Jump to navigationJump to searchno edit summary
service nut restart
service nut restart
{{Note box|To disabled the admin user once you have changed the UPS parameters or issued commands as required, issue the commands
{{Note box|To disabled the administrative privileges once you have changed the UPS parameters or issued commands as required, issue the commands
config setprop nut AdminUser disabled
config setprop nut AdminUser disabled
/sbin/e-smith/expand-template /etc/ups/upsd.users
/sbin/e-smith/expand-template /etc/ups/upsd.users
upsc UPS
upsc UPS
After you are done, clean up by disabling the '''upsd''' administrative user '''admin''':
After you are done, clean up by disabling the '''upsc''' administrative privileges:
{{Warning box|Make sure you understand the meaning or the UPS variables and their available setting options. Verify that your changes meet your intended behaviour!}}
{{Warning box|Make sure you understand the meaning or the UPS variables and their available setting options. Verify that your changes meet your intended behaviour!}}
Where the command '''test.battery.start''' is a valid command for your UPS as previously determined by '''upscmd -l UPS'''. Depending upon the command issued you may get broadcast messages and emails relating to and confirming what the UPS is doing.
Where the command '''test.battery.start''' is a valid command for your UPS as previously determined by '''upscmd -l UPS'''. Depending upon the command issued you may get broadcast messages and emails relating to and confirming what the UPS is doing.
After you are done, clean up by disabling the '''upsd''' administrative user '''admin''':
After you are done, clean up by disabling the '''upsc''' administrative privileges:
{{Warning box|Before issuing any commands verify what they do for your particular UPS via the relevant documentation and ensure that the command meets your intended behavioural requirement!
{{Warning box|Before issuing any commands verify what they do for your particular UPS via the relevant documentation and ensure that the command meets your intended behavioural requirement!
