[Nut-upsdev] CENTOS 6.6 NUT RPM BUILD ISSUES
Eric_Cobb at tripplite.com
Mon Apr 6 17:58:25 UTC 2015
That worked out just fine. What I am currently running into are conditions where I am getting the following error that I figured I would share.
libusb_get_interrupt() returned 0 instead of 8 while sending 3a 4d b2 0d 00 00 00 00 '.M......'
Conditions: upsdrvctl start via Init Script at Boottime. If I run the init script after boot, I do not receive this error.
ekcobb at tripplite.com
From: Charles Lepple [mailto:clepple at gmail.com]
Sent: Thursday, March 26, 2015 8:59 PM
To: Eric Cobb
Cc: nut-upsdev at lists.alioth.debian.org
Subject: Re: CENTOS 6.6 NUT RPM BUILD ISSUES
On Mar 26, 2015, at 11:16 AM, Eric Cobb <Eric_Cobb at tripplite.com<mailto:Eric_Cobb at tripplite.com>> wrote:
The init script no longer works so a new script needs to be written to enable and disable the ups functionality, however it is communicating with the UPS properly. The question I have at this point is, is there a way I can set this so that once Line Power is disrupted it starts the shutdown command on the system versus waiting for the UPS battery to be "critical"?
I would probably just raise the low battery threshold, but to trigger the shutdown immediately, you could write a NOTIFYCMD script for upsmon that looks for the ONBATT event (corresponds to "OB" for ups.status):
clepple at gmail
This message is for the addressee's use only. It may contain confidential information. If you receive this message in error, please delete it and notify the sender. Tripp Lite disclaims all warranties and liabilities, and assumes no responsibility for viruses which may infect an email sent to you from Tripp Lite and which damage your electronic systems or information. It is your responsibility to maintain virus detection systems to prevent damage to your electronic systems and information.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Nut-upsdev