User's Manual UPS control system
Table Of Contents
- Apcupsd User's Manual
- Release Notes
- How To Use This Manual
- Basic User's Guide
- Planning Your Installation
- Building and Installing apcupsd
- After Installation
- Configuration Examples
- Testing Apcupsd
- Troubleshooting Your Installation
- Monitoring and Tuning your UPS
- Maintaining Your UPS
- Frequently-Asked Questions
- Apcupsd Bugs
- Advanced topics
- Customizing Event Handling
- Master/Slave Configurations
- Controlling Multiple UPSes on one Machine
- Support for SNMP UPSes
- Alternate Ways To Run The Network Information Server
- apcupsd System Logging
- Installation: Windows
- Windows Version of apcupsd
- Installation: Serial-Line UPSes
- Overview of Serial-Interface UPSes
- Connecting a Serial-Line UPS to a USB Port
- Connecting a APC USB UPS to either a PC USB or Serial Port
- Cables
- Smart-Custom Cable for SmartUPSes
- Smart Signalling Cable for BackUPS CS Models
- Voltage-Signalling Cable for "dumb" UPSes
- Other APC Cables that apcupsd Supports
- Voltage Signalling Features Supported by Apcupsd for Various Cables
- Voltage Signalling
- Back-UPS Office 500 signals
- Analyses of APC Cables
- Win32 Implementation Restrictions for Simple UPSes
- Internal Apcupsd Actions for Simple Cables
- RS232 Wiring and Signal Conventions
- Pin Assignment for the Serial Port (RS-232C), 25-pin and 9-pin, Female End
- Ioctl to RS232 Correspondence
- Testing Serial-Line UPSes
- Troubleshooting Serial Line communications
- Recalibrating the UPS Runtime
- DATA Logging
- Technical Reference
- Configuration Directive Reference
- apcupsd Status Logging
- Shutown Sequence and its Discontents
- APC smart protocol
- Apcupsd --- RPM Packaging FAQ
- Credits
- Kernel Config
The purpose of modifying the system halt files is so that apcupsd will be
recalled after the system is in a stable state. At that point, apcupsd will
instruct the UPS to shut off the power. This is necessary if you wish your
system to automatically reboot when the mains power is restored. If you
prefer to manually reboot your system, you can skip this final system depen-
dent installation step by specifying the disable-install-distdir option
on the ./configure command (see below for more details).
The above pertains to Red Hat systems only. There are significant differ-
ences in the procedures on each system, as well as the location of the halt
script. Also, the information that is inserted in your halt script varies from
system to system. Other systems such as Solaris require you the make the
changes manually, which has the advantage that you won’t have any un-
pleasant surprises in your halt script should things go wrong. Please consult
the specific system dependent README files for more details.
Please note that if you install from RPMs for a slave machine, you will need
to remove the changes that the RPM install script made (similar to what is
noted above) to the halt script. This is because on a slave machine there is
no connection to the UPS, so there is no need to attempt to power off the
UPS. That will be done by the master.
Configure Options
All the available configure options can be printed by entering:
./configure --help
When specifying options for ./configure, if in doubt, don’t put anything,
since normally the configuration process will determine the proper settings
for your system. The advantage of these options is that it permits you to
customize your version of apcupsd. If you save the ./configure command
that you use to create apcupsd, you can quickly reset the same customization
in the next version of apcupsd by simply re-using the same ./configure
command.
The following command line options are available for configure to cus-
tomize your installation.
—prefix=<path> This defines the directory for the non-executable files
such as the manuals. The default is /usr.
35










