Specify name of the UPS which will provide the protection. Where powerware - UPS manufacturer, 5110 - model. Grep -i -E 'powerware.*5110' /usr/share/nut/driver.list In it used and configured only the component of the third level upsmon. Slave - managed computer receives information about UPS status from service upsd on "master" system. The settings are similar to the system of "Simple" configuration except network settings access the service upsd. Master - control computer which has connected to the UPS communication, provides information about his condition all slave computers. One UPS provides protection for multiple computers. In It used and configured components of all three levels - driver, upsd service and upsmon. Using and customizing the component depends from connect UPS to the protected equipment, see Monitoring diagrams "Simple" configuration
CGI programs - scripts for Web administration: upsset.cgi, upsstats.cgi, upsimage.cgi (installed as a separate package).Monitor - UPS monitor and shutdown controller, ( man upsmon).This strategy is preferred in case of bad power supply quality (very frequent input power outages), because allows you to save battery power sufficient to properly shutting down the server. When input power comes back, start the server, but to remain in readiness to shutdown again as soon, as the input power fails again. Pessimistic: While the input power failure, the server must be shutdown as soon, as possible.When input power comes back, start the server, and hope, that input power will be available long enough to, at least partially, charge the battery. When battery charge low, the server must be shutdown.
Optimistic: Keep going as long, as possible with the available battery charge.There are two basic strategies for stopping a server when the input power source fails: