search for: systemdshutdowndir

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

...ts 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`" This experiment also coincides with the delivery and installation of my new Cyberpower CP1500PFCLCD. Slightly hampered by the nut-scanner problem, I grabbed the USB ids from lsusb. It came up without any issues: [root at monster system]# upsc nutdev1 battery.charge: 100 batter...

I see, so you kept the load.on.delay command but removed the check to see if it was handled. Did you do the same thing for the shutdown.stayoff logic? https://github.com/networkupstools/nut/blob/master/drivers/usbhid-ups.c#L562 This might be a dumb question but did this require you to recompile the kernel? These types of changes are way beyond my depth. Thank you for the direction! On Thu, Jan

.../usr/lib/cgi-bin/nut \ --with-htmlpath=/usr/share/nut/www \ --with-pidpath=/run/nut \ --datadir=/usr/share/nut \ --with-pkgconfig-dir=/usr/lib/`gcc -print-multiarch`/pkgconfig \ --with-user=nut \ --with-group=nut \ --with-udev-dir=/lib/udev \ --with-systemdsystemunitdir=/lib/systemd/system \ --with-systemdshutdowndir=/lib/systemd/system-shutdown make make check VERBOSE=1 cd ~/nut/drivers sudo upsdrvctl stop sudo make install sudo apt remove nut-build-deps sudo apt remove devscripts sudo apt autoremove sudo upsdrvctl start On Sat, Jan 4, 2020 at 5:15 PM Ken Olum <kdo at cosmos.phy.tufts.edu> wrote: >...