search for: systemdsystemshutdowndir

nut hardcodes systemdsystemshutdowndir to ${libdir}/systemd/system-shutdown. This is not valid: - Executable helpers are installed to ${libexecdir}, which is different from ${libdir} on bi-arch systems. - Even if nut will use ${libexecdir}, it could be different from systemd libexecdir. That is why it is better to check systemd.pc...

...ora 27, running commit 2999c95f0: # nut-scanner Cannot load USB library (/usr/lib64/libusb-1.0.so.0.1.0) : /usr/lib64/libusb-1.0.so.0.1.0: undefined symbol: usb_get_string_simple. USB search disabled. There's also a bug in the configure script on 64 bit Fedora. The configure script sets systemdsystemshutdowndir to /usr/lib64/systemd/systemd-shutdown which misses the mark, a little bit. The fix: if test -n "${systemdsystemunitdir}"; then - systemdsystemshutdowndir="${libdir}/systemd/system-shutdown" + systemdsystemshutdowndir="`$PKG_CONFIG --variable=systemdshutdowndir systemd`...

Hi all, I am doing some final testing of the libusb-1.0 branch (specifically https://github.com/zykh/nut.git branch libusb-1.0+0.1 @ dfd514e7), and I am running across a regression in usbhid-ups relative to the previous libusb-0.1 code running on FreeBSD. Basically, the master (2.7.4+; c703fa75) code was able to start running as root, drop privileges (usually to uucp, the default for the ports

...with a small shell script that parses the output of lsusb, this shouldn't be too hard to fix. Logged, in case it is not as simple as it looks: https://github.com/networkupstools/nut/issues/499 > > There's also a bug in the configure script on 64 bit Fedora. The configure script sets systemdsystemshutdowndir to /usr/lib64/systemd/systemd-shutdown which misses the mark, a little bit. The fix: Agreed - looks like we will have that after a merge from master: https://github.com/networkupstools/nut/pull/496/commits/491d088af70a67b6ed1d2a6a6711d83be71dd911