In order to compile collectd's nut plugin (not shipped with current collectd package from the community repo) --with-dev configure option is needed.
This will install header and pkg-config files.
Search Criteria
Package Details: network-ups-tools 2.7.4-3
| Git Clone URL: | https://aur-dev.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: | |
| Submitter: | Atsutane |
| Maintainer: | The-Compiler |
| Last Packager: | The-Compiler |
| Votes: | 69 |
| Popularity: | 1.732719 |
| First Submitted: | 2010-09-21 19:10 |
| Last Updated: | 2016-11-22 09:45 |
Dependencies (6)
- libltdl (libtool)
- libusb-compat (libusb0)
- neon (neon-threadsafe)
- net-snmp
- openssl (openssl-via-padlock, openssl-no-aesni, libressl-git, openssl102, openssl-chacha20, libressl, openssl-purify)
- asciidoc (asciidoc-fake, asciidoc-git) (make)
Required by (2)
Sources (1)
Latest Comments
The-Compiler commented on 2016-11-22 09:46
fry commented on 2016-11-20 22:12
hexadecagram commented on 2016-07-05 08:53
The-Compiler commented on 2016-07-05 08:39
@hexadecagram I suggest suggesting this in the upstream bugtracker: https://github.com/networkupstools/nut/issues
I'd rather avoid applying patches which aren't coming from upstream.
hexadecagram commented on 2016-07-05 08:37
If I use udev to set different permission on the device node for my USB, nut-driver.service doesn't start up on boot. If I then login and restart nut-driver.service, it works.
The systemd functionality described in this blog supposedly worked at one time (I never tried it myself):
https://www.kepstin.ca/blog/networkupstoolsnutandsystemd/
After much trial and error, I set After=network-online.target and Requires=network-online.target for both nut-driver.service and nut-server.service (the latter of which should have those configurations regardless, because upsd will fail to start if the network is not online). Boom, it works. I tried quite a few unit files before that, all the way up the chain to upower.service. Nothing else worked.
I think a more appropriate fix would be to add something like the following in nut-driver.service. This will work for now but I think the ideal solution would to be to remove the nut-driver.service dependency in nut-server.service and work it into udev so that drivers are reloaded when devices are hotplugged.
[Service]
Restart=on-failure
RestartSec=10
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.
@fry, added in -3