It may be necessary to change the configuration information in the file /etc/apcupsd/apcupsd.conf to meet your needs and to correspond to your configuration. This file is a plain ASCII file and you can use your favorite editor to change it.
Configuration directives in /etc/apcupsd/apcupsd.conf are:
Keyword | APC Model | Signaling | Status |
---|---|---|---|
backups | BackUPS | Simple | Supported |
sharebasic | ShareUPS Basic Port | Simple | Supported |
backupspro | BackUPS Pro | SubSmart | Supported |
smartvsups | SmartUPS VS | SubSmart | Supported |
newbackupspro | Smarter BackUPS Pro | SubSmart | Supported |
backupspropnp | Smarter BackUPS Pro | SubSmart | Supported |
smartups | SmartUPS | Smart | Supported |
matrixups | MatrixUPS | Smart | Supported |
sharesmart | ShareUPS Advanced Port | Smart | Being tested |
The values specified with the following directives are only used if the --configure option is specified on the apcupsd command line, and the UPS is capable of internal EPROM programming. In that case, apcupsd attempts to set the values into the UPSes EPROM.
Under normal operations, the values for these parameters specified in the configuration file are not used. Instead, they are read from the UPS EPROM by apcupsd. See the EEPROM programming section of this manual for further details.
For normal standalone operations, you will set UPSMODE to disable to indicate that you are disabling the master/slave networking.
However, if you are using a single UPS to power several computers and you have configured master and slave computers, then set this value to net.
A different port number for the Network Information Server is specified with the SERVERPORT configuration directive.
The slave machine will be shutdown whichever occurs first: either at the request of the master when it does a shutdown or when the values you have specified for TIMEOUT, BATTERYLEVEL, or MINUTES expire (these should work but have not been fully tested). Consequently, if you want the slaves to begin shutting down before the master, you can do so by adjusting the values in the configuration file. If you want the slave to remain up until the master shuts down, you should set TIMEOUT, BATTERYLEVEL, and MINUTES all to zero.
For proper functioning of the slave, you must specify the same UPSTYPE in the slave configuration file as is in the master configuration file.
It should be noted that the master and slaves continue to communicate over the network even after the master has issued a shutdown command to the slaves. This is because the master apcupsd continues to run until it receives the shutdown signal from the system. This is important to ensure that all the slaves have been properly notified of the shutdown.
We recommend that the machine names used on the MASTER and SLAVE directives be put in your /etc/hosts file so that apcupsd will be able to resolve the machine name during startup and shutdown even if DNS is not running. Alternatively, you can use IP addresses on the MASTER and SLAVE directives, but this is less flexible.
As noted above the master and slaves continue to communicate over the network even after the master has issued a shutdown command to the slaves. This is because the master apcupsd continues to run until it receives the shutdown signal from the system. This is important to ensure that all the slaves have been properly notified of the shutdown.
We recommend that the machine names used on the MASTER and SLAVE directives be put in your /etc/hosts file so that apcupsd will be able to resolve the machine name during startup and shutdown even if DNS is not running. Alternatively, you can use IP addresses on the MASTER and SLAVE directives, but this is less flexible.