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
Does a printf ‘‘UPS battery runtime limit exceeded. Doing
shutdown.\n’’ | wall then exits. After completing this event,
apcupsd will immediately initiate a doshutdown event.
startselftest This event is generated when apcupsd detects a self test by
the UPS. Normally due to the 6 second onbattery delay default time,
self test events are not detected.
This is called when apcupsd detects that the UPS is doing a self test.
No action is taken.
endselftest This event is generated when the end of a self test is detected.
This is called when apcupsd determines that a self test has been com-
pleted. No action is taken.
mastertimeout This event is generated when a slave detects that a master
has not contacted it in a reasonable time, or when a slave polls a master
and gets no response in 30 seconds. This event applies only to the old
master/slave networking code and not to the NIS server/slave mode.
No action is taken.
masterconnect This event is generated when the slave and the master
reconnect. This event applies only to the old master/slave networking
code and not to the NIS server/slave mode.
No action is taken.
To write your own routine for the powerout action, you create shell script
named powerout and put it in the lib directory (normally /etc/apcupsd).
When the powerout action is invoked by apcupsd, apccontrol will first give
control to your script. If you want apccontrol to continue with the default
action, simply exit your script with an exit status of zero. If you do not
want apccontrol to continue with the default action, your script should exit
with the special exit code of 99. However, in this case, please be aware that
you must ensure proper shutdown of your machine if necessary.
Some sample scripts (onbattery and mainsback) that email power failure
messages can be found in the examples directory of the source code.
Master/Slave Configurations
If you have two or more computers that are powered by the same UPS
and they are connected by a network, you can configure apcupsd so that
the computer that controls the UPS (connected by the serial port or USB
105










