02.12.2015 Views

Network UPS Tools User Manual

Network UPS Tools User Manual

Network UPS Tools User Manual

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Network</strong> <strong>UPS</strong> <strong>Tools</strong> <strong>User</strong> <strong>Manual</strong> 4 / 84<br />

2.8.4 <strong>UPS</strong> Shutdowns<br />

upsdrvctl can also shut down (power down) all of your <strong>UPS</strong> hardware.<br />

Warning<br />

if you play around with this command, expect your filesystems to die. Don’t power off your computers unless they’re<br />

ready for it:<br />

/usr/local/ups/sbin/upsdrvctl shutdown<br />

/usr/local/ups/sbin/upsdrvctl shutdown sparky<br />

You should read the Configuring automatic <strong>UPS</strong> shutdowns chapter to learn more about when to use this feature. If called at the<br />

wrong time, you may cause data loss by turning off a system with a filesystem mounted read-write.<br />

2.8.5 Power distribution unit management<br />

NUT also provides an advanced support for power distribution units.<br />

You should read the Configuring automatic <strong>UPS</strong> shutdowns chapter to learn more about when to use this feature.<br />

2.9 <strong>Network</strong> Server<br />

upsd is responsible for passing data from the drivers to the client programs via the network. It should be run immediately after<br />

upsdrvctl in your system’s startup scripts.<br />

upsd should be kept running whenever possible, as it is the only source of status information for the monitoring clients like<br />

upsmon.<br />

2.10 Monitoring client<br />

upsmon provides the essential feature that you expect to find in <strong>UPS</strong> monitoring software: safe shutdowns when the power fails.<br />

In the layered scheme of NUT software, it is a client. It has this separate section in the documentation since it is so important.<br />

You configure it by telling it about <strong>UPS</strong>es that you want to monitor in upsmon.conf. Each <strong>UPS</strong> can be defined as one of two<br />

possible types:<br />

2.10.1 Master<br />

This <strong>UPS</strong> supplies power to the system running upsmon, and this system is also responsible for shutting it down when the<br />

battery is depleted. This occurs after any slave systems have disconnected safely.<br />

If your <strong>UPS</strong> is plugged directly into a system’s serial port, the upsmon process on that system should define that <strong>UPS</strong> as a<br />

master.<br />

For a typical home user, there’s one computer connected to one <strong>UPS</strong>. That means you run a driver, upsd, and upsmon in master<br />

mode.<br />

2.10.2 Slave<br />

This <strong>UPS</strong> may supply power to the system running upsmon, but this system can’t shut it down directly.<br />

Use this mode when you run multiple computers on the same <strong>UPS</strong>. Obviously, only one can be connected to the serial port on<br />

the <strong>UPS</strong>, and that system is the master. Everything else is a slave.<br />

For a typical home user, there’s one computer connected to one <strong>UPS</strong>. That means you run a driver, upsd, and upsmon in master<br />

mode.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!