Package Details: network-ups-tools 2.7.4-2

Git Clone URL: https://aur.archlinux.org/network-ups-tools.git (read-only)
Package Base: network-ups-tools
Description: NUT is a collection of programs for monitoring and administering UPS hardware
Upstream URL: http://www.networkupstools.org/
Licenses: GPL2
Submitter: Atsutane
Maintainer: The-Compiler
Last Packager: The-Compiler
Votes: 64
Popularity: 2.616516
First Submitted: 2010-09-21 19:10
Last Updated: 2016-05-30 13:43

Latest Comments

precurse commented on 2016-06-05 02:00

Much thanks The-Compiler :)

The-Compiler commented on 2016-05-30 13:47

@hexadecagram Thanks for bringing this up again, must've gotten lost in all the mails I get last time ;) -2 now installs them there, I agree that sounds like the right location.

@precurse @augiedoggie @lulingar @travesh Okay, I give up, I added armv6h and armv7h, even though they aren't official architectures...

hexadecagram commented on 2016-05-26 08:00

This package still conflicts with the rhino package, even though this was first reported in 2012!

To get the ball rolling, all it would take is a simple one-line edit of PKGBUILD so that the build() step calls ./configure with --with-drvpath=/usr/lib/network-ups-tools (my recommendation for where the binaries should go, in accordance with the hier manpage).

precurse commented on 2016-05-22 23:41

I've successfully compiled and used this with RP1 and RP2.. armv6h and armv7h.

augiedoggie commented on 2016-04-22 00:59

I agree with @lulingar, it would be nice to have armv7h added to the architectures. The package runs fine on my Pandaboard ES.

lulingar commented on 2016-04-05 19:09

The architecture armv7h might be added as well. I have successfully built and installed the package on a Raspberry Pi 2.

The-Compiler commented on 2016-01-04 09:28

Sorry for the delay - I added the patch to the package now.

Let me know if anything else is missing!

zman0900 commented on 2015-12-19 20:18

nut-driver.service is not starting as expected in new installs. It is supposed to be started automatically by nut-server.service. It still works for older installs because the links in /etc/systemd/system/multi-user.target.want/ still exists for nut-driver. Looks like this was broken when upstream removed the Requires= from nut-server.service. It was fixed by adding a Wants= instead:

https://github.com/networkupstools/nut/commit/c98fab9f5dec993aa9f5e0a3e79de53ae9ecd32b

Can this patch be added to this package?

precurse commented on 2015-10-20 06:20

In case anyone wants to know..

This was the fix for me: https://github.com/networkupstools/nut/commit/c98fab9f5dec993aa9f5e0a3e79de53ae9ecd32b

precurse commented on 2015-10-12 07:28

nut-driver refuses to start for me unless I run "upsdrvctl start" manually even though upsmon and upsd start without issue. It also lets me start the driver (manually) if I change the systemd service to "StopWhenUnneeded=no" and running the systemctl start nut-driver. Systemd keeps unloading it saying it's no longer needed otherwise.

Anyone else seeing this issue?

All comments