Network UPS Tools (as of v2.8.2)
Power Devices support
Table of Contents
Note
Two NUT websites

This version of the page reflects NUT release v2.8.2 with codebase commited 440ca2348 at 2024-04-01T22:07:23+02:00

Options, features and capabilities in current development (and future releases) are detailed on the main site and may differ from ones described here.

This section presents the different methods to download NUT.

Source code

Note

You should always use PGP/GPG to verify the signatures before using any source code.

You can use the following procedure to do so.

Stable tree: 2.8

You can also browse the stable source directory.

Development tree:

Code repository

The development tree is available through a Git repository hosted at GitHub.

To retrieve the current development tree, use the following command:

$ git clone git://github.com/networkupstools/nut.git

The configure script and its dependencies are not stored in Git. To generate them, ensure that autoconf, automake and libtool are installed, then run the following script in the directory you just checked out:

$ ./autogen.sh
Note it is optionally recommended to have Python 2.x or 3.x, and Perl, to generate some files included into the configure script, presence is checked by autotools when it is generated. Neutered files can be just "touched" to pass the autogen.sh if these interpreters are not available, and effectively skip those parts of the build later on — autogen.sh will then advise which special environment variables to export in your situation and re-run it.

Then refer to the NUT user manual for more information.

Browse code

You can browse the "vanilla NUT" code at the Main GitHub repository for NUT sources, and some possibly modified copies as part of packaging recipe sources of operating system distributions, as listed below.

Snapshots

GitHub has several download links for repository snapshots (for particular tags or branches), but you will need a number of tools such as autoconf, automake and libtool to use these snapshots to generate the configure script and some other files.

After you configure the source workspace, a make dist-hash recipe would create the snapshot tarballs which do not require the auto* tools, and their checksum files, such as those available on the NUT website and attached to GitHub Releases page.

Older versions

Browse source directory

Binary packages

Note The only official releases from this project are source code.

NUT is already available in the following operating systems (and likely more):

Java packages

Virtualization packages

VMware