macOS
brew install apcupsdlocal Homebrew formula metadata
sudo port install apcupsdMacPorts ports tree · sysutils/apcupsd/Portfile · source: api.github.com
brew
Daemon for controlling APC UPSes. Version 3.14.14 via Homebrew; verified from local package data.
install
brew install apcupsdlocal Homebrew formula metadata
sudo port install apcupsdMacPorts ports tree · sysutils/apcupsd/Portfile · source: api.github.com
sudo apk add apcupsdAlpine Linux edge package indexes · apcupsd · source: dl-cdn.alpinelinux.org
sudo apt install apcupsdDebian stable package indexes · apcupsd · source: deb.debian.org
sudo dnf install apcupsdFedora Rawhide package metadata · apcupsd · source: dl.fedoraproject.org
nix profile install nixpkgs#apcupsdnixpkgs package indexes · pkgs/by-name/ap/apcupsd/package.nix · source: api.github.com
sudo pacman -S apcupsdArch Linux sync databases · apcupsd · source: geo.mirror.pkgbuild.com
sudo zypper install apcupsdopenSUSE Tumbleweed package metadata · apcupsd · source: download.opensuse.org
overview
Daemon for controlling APC UPSes
history
apcupsd is a daemon and command-line toolset for monitoring and controlling APC UPS devices. It is one of those infrastructure packages that quietly matters because it can shut systems down cleanly when power fails.
The apcupsd project dates to the long-running Unix tradition of hardware daemons: small background services that translate a device protocol into system policy. Its official manual documents operation with APC UPS hardware, configuration through `apcupsd.conf`, status querying through `apcaccess`, and testing through `apctest`.
The project has historically lived on SourceForge, with source control exposed through the official SourceForge project tree. That hosting history matches many mature system utilities that predate GitHub-centered development.
apcupsd's adoption is strongest in server, NAS, homelab, and workstation environments where APC UPS hardware is common and a lightweight local daemon is preferable to a larger management suite.
The supplied package data shows broad Unix-like packaging: Alpine, Homebrew, Debian, Fedora/dnf, MacPorts, Nix, Arch/pacman, Ubuntu, and openSUSE/zypper. That breadth is the package-history signal: administrators expect it to be available from the native package manager on almost any Unix-like system.
Typical usage is to configure `/etc/apcupsd/apcupsd.conf`, run the `apcupsd` daemon, inspect UPS state with `apcaccess`, and test device communication with `apctest`. Scripts and service managers then use the daemon's events to perform clean shutdowns or notifications.
The package is hardware-facing, so installation alone is not the whole story. Correct cable/device selection, daemon privileges, and shutdown policy matter more than application-level credentials.
apcupsd is package-nerd significant because it represents the unglamorous layer where packaging meets physical infrastructure. A good package has to install a daemon, config file, service integration, helper commands, and documentation without hiding the hardware-specific knobs.
It also illustrates why old system packages remain valuable: power events are rare, but when they happen the daemon must already be installed, configured, and boringly reliable.
security posture
narrow executable package without higher-risk signals.
green risk · low confidence · appliance
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
local files
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Config paths the tool may read or write during local use.
/etc/apcupsd/apcupsd.confexecutables
| Command | Kind | Exposure | Note |
|---|---|---|---|
apcaccess | cli | global executable | |
apctest | cli | global executable | |
apcupsd | cli | global executable | |
apcupsd-start | cli | global executable | |
smtp | cli | global executable |
freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
install metadata
| Package key | brew:apcupsd |
|---|---|
| Version | 3.14.14 |
| Package manager | Homebrew |
| Package manager page | https://formulae.brew.sh/formula/apcupsd |
| Homepage | http://www.apcupsd.org |
| Repository | https://sourceforge.net/p/apcupsd/svn/HEAD/tree |
| Upstream docs | http://www.apcupsd.org/manual |
| License | GPL-2.0-only |
| Source archive | https://downloads.sourceforge.net/project/apcupsd/apcupsd%20-%20Stable/3.14.14/apcupsd-3.14.14.tar.gz |
| Dependencies | gd, libusb-compat |
| Bottle | available (on arm64_big_sur, arm64_linux, arm64_monterey, arm64_sequoia, arm64_sonoma, arm64_tahoe, arm64_ventura, big_sur, catalina, monterey, sonoma, ventura, x86_64_linux) |
| Homebrew post-install | not defined |
| Service | none declared |
| Caveats | For apcupsd to be able to communicate with UPSes connected via USB, the kernel extension must be installed by the root user: sudo cp -pR $HOMEBREW_CELLAR/apcupsd/3.14.14/Library/Extensions/ApcupsdDummy.kext /System/Library/Extensions/ sudo chown -R root:wheel /System/Library/Extensions/ApcupsdDummy.kext sudo touch /System/Library/Extensions/ Note: The kernel extension currently does not work as expected. You will have to unplug and plug the USB cable back in after each reboot in order for apcupsd to be able to connect to the UPS. To load apcupsd at startup, activate the included Launch Daemon: sudo cp $HOMEBREW_CELLAR/apcupsd/3.14.14/lib/Library/LaunchDaemons/org.apcupsd.apcupsd.plist /Library/LaunchDaemons sudo chmod 644 /Library/LaunchDaemons/org.apcupsd.apcupsd.plist sudo launchctl load -w /Library/LaunchDaemons/org.apcupsd.apcupsd.plist If this is an upgrade and you already have the Launch Daemon loaded, you have to unload the Launch Daemon before reinstalling it: sudo launchctl unload -w /Library/LaunchDaemons/org.apcupsd.apcupsd.plist sudo rm /Library/LaunchDaemons/org.apcupsd.apcupsd.plist |
registry facts
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | apcupsd |
| Version Scheme | 0 |
| Revision | 0 |
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
source database matches
Matches are pulled from external package-manager indexes and kept separate from local Automic Vault package links.
apcupsd 3.14.14-5
APC UPS Power Management (daemon)
sudo apt install apcupsdapcupsd-cgi 3.14.14-5
APC UPS Power Management (web interface)
sudo apt install apcupsd-cgiapcupsd-doc 3.14.14-5
APC UPS Power Management (documentation/examples)
sudo apt install apcupsd-docapcupsd
nix profile install nixpkgs#apcupsdapcupsd 3.14.14-3.1build2
APC UPS Power Management (daemon)
sudo apt install apcupsdapcupsd-cgi 3.14.14-3.1build2
APC UPS Power Management (web interface)
sudo apt install apcupsd-cgiapcupsd-doc 3.14.14-3.1build2
APC UPS Power Management (documentation/examples)
sudo apt install apcupsd-docapcupsd 3.14.14-r6
A Daemon to control APC UPSes
sudo apk add apcupsdapcupsd-doc 3.14.14-r6
A Daemon to control APC UPSes (documentation)
sudo apk add apcupsd-docapcupsd-openrc 3.14.14-r6
A Daemon to control APC UPSes (OpenRC init scripts)
sudo apk add apcupsd-openrcapcupsd-webif 3.14.14-r6
A Daemon to control APC UPSes
sudo apk add apcupsd-webifapcupsd 3.14.14-41.fc44
APC UPS Power Control Daemon
sudo dnf install apcupsdapcupsd-cgi 3.14.14-41.fc44
Web interface for apcupsd
sudo dnf install apcupsd-cgiapcupsd-gui 3.14.14-41.fc44
GUI interface for apcupsd
sudo dnf install apcupsd-guiapcupsd 3.14.14-9
Power mangement and controlling most of APC's UPS models
sudo pacman -S apcupsdapcupsd 3.14.14-17.5
APC UPS Daemon (Powerful Daemon for APC UPSs)
sudo zypper install apcupsdsource trail
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
View the package source record on GitHub.