On May 25, 2016, at 9:42 PM, Larry Fahnoe <[email protected]> wrote: > > So the current NUT can't cause this UPS to power off the load while it is on > line power, correct? I will update the nut-server init script with the > sleep/reboot logic per FAQ #51.
Correct. > My larger concern is testing the UPS to ensure it shuts down correctly and > comes back up correctly as well. My concern is driven by my observation that > with older versions of NUT using the tripplite_usb driver, this UPS has *not* > correctly shut down while on battery, thus the batteries drained and the UPS > never supplied load power once line power had been restored. To be honest, most of my testing with Raspbian has been just debugging drivers during normal operation, not with the shutdown scripts. I also haven't had much of a chance to test with systemd. Even stranger, someone else saw the opposite problem with the same .deb version in Debian/x86: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799849 > I assume the next logical test would be to do the same test > (/lib/nut/tripplite_usb -a tripplite -k -DDD) while the UPS is on battery? Yes. > Are the serial drivers any better at this sort of thing than the USB driver > for these older Tripplite UPS systems? Not sure - the OMNIVS1000 that I used to test tripplite_usb does not have a serial port. There seem to be some options to force the UPS to reboot, but it is unclear which protocol number the serial driver was written for. -- Charles Lepple clepple@gmail _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
