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
/sbin/apcnisd
The advantage of running the network information server standalone is that
if for some reason, a client causes the network server to crash, it will not
affect the operation of apcupsd.
apcupsd System Logging
The apcupsd philosophy is that all logging should be done through the sys-
log facility (see: man syslog). This is now implemented with the exceptions
that STATUS logging, for compatibility, with prior versions is still done to
a file, and EVENTS logging can be directed to a “temporary” file so that
it can be reported by the network information server.
Logging Types
apcupsd splits its logging into four separate types called:
1. DEBUG
2. DATA
3. STATUS
4. EVENTS
Debug logging consists of debug messages. Normally these are turned on
only by developers, and currently there exist very few of these debug mes-
sages.
Logging
Data logging consists of periodically logging important data concerning the
operation of the UPS. See the Data Logging (see DATA Logging) section of
this manual for more details.
Logging
Status logging consists of logging all available information known about your
UPS as a series of ASCII records. This information is also made available
by the apcupsd network information server.
118










