software:nut:master
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
software:nut:master [2025/04/14 18:26] – rodolico | software:nut:master [2025/04/14 22:32] (current) – rodolico | ||
---|---|---|---|
Line 9: | Line 9: | ||
* One opnSense firewall/ | * One opnSense firewall/ | ||
* One FreeBSD NAS | * One FreeBSD NAS | ||
+ | |||
+ | **Note:** a Raspberry Pi works very well as a stand alone NUT server. See https:// | ||
===== Set up UPS ===== | ===== Set up UPS ===== | ||
Line 114: | Line 116: | ||
upsc ups1@localhost | upsc ups1@localhost | ||
</ | </ | ||
+ | |||
+ | ==== NUT ups commands ==== | ||
+ | * upsc - lightweight UPS client. Really, set up to be an example of what you can create, but very useful. <code bash> | ||
+ | * upscmd - send commands to UPS if it will accept. Try <code bash> | ||
+ | * upsd - This is the primary daemon that should always run to provide information about one or more UPS'. Generally auto started by the init system | ||
+ | * upsdrvctl - standard interface to the UPS drivers. Not generally needed unless you are writing/ | ||
+ | * upslog - A tool designed to read one or more UPS' and log the readings. Very useful for upssched if you want a nice log of how your UPS is working. | ||
+ | * upsmon - A daemon which monitors all UPS' defined in upsmon.conf | ||
+ | * upsrw - allows you to change some variables //on the ups itself// if the ups allows it. | ||
+ | * upssched - scheduler to run commands listed in upssched.conf. This is called by upsmon and should not be used directly. | ||
+ | * upssched-cmd - A sample upssched file. A simple shell script that performs commands in response to upssched. | ||
+ | |||
+ | ===== Links ===== | ||
+ | * https:// | ||
+ | * https:// | ||
+ | * https:// | ||
+ | * |
software/nut/master.1744673212.txt.gz · Last modified: 2025/04/14 18:26 by rodolico