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
Acknowledgements
The apcupsd has a rather long and tormented history. Many thanks to the
guys that, with time, contributed to the general public knowledge.
Pavel Korensky <pavelk at dator3.anet.cz>, Andre M. Hedrick <hedrick
at suse.de>, Christopher J. Reimer <reimer at doe.carleton.ca>, Kevin D.
Smolkowski <kevins at trigger.oslc.org>, Werner Panocha <wpanocha at
t-online.de>, Steven Freed, Russell Kroll.
additions by: Kern Sibbald <apcupsd-users at lists.sourceforge.net>
Apcupsd — RPM Packaging FAQ
Answers
How do I build Apcupsd for platform xxx? The apcupsd spec file
contains defines to build for several platforms: RedHat 7.x (rh7), Red-
Hat 8.0 (rh8), RedHat 9 (rh9), Fedora Core 1 (fc1), and Whitebox
Enterprise Linux 3.0 (wb3). The package build is controlled by a
define set at the beginning of the file. These defines basically just
control the dependancy information that gets coded into the finished
rpm package. So while you could technically build a package without
defining a platform, or with an incorrect platform, and have it install
and run it would not contain correct dependancy information for the
rpm database. The platform define may be edited in the spec file di-
rectly (by default all defines are set to 0 or “not set”). For example,
to build the RedHat 7.x package find the line in the spec file which
reads
%define rh7 0
and edit it to read
%define rh7 1
Alternately you may pass the define on the command line when calling
rpmbuild:
200










