On 10/5/2016 10:59 PM, Jeff Bowman wrote:
>
>>> How does this work in conjunction with the UPS hardware? Does NUT
>>> immediately send a command to the UPS to wait for 300 seconds and then
>>> shut itself down, thereby allowing the server enough time to safely
>>> shut itself down as well?
>>
>> Y
> The "upsdrvctl shutdown" command is designed to be run late in the shutdown
> sequence, and has to be run after the rest of NUT (drivers, upsd, etc) has
> been stopped. It does, in fact, restart the driver with the "-k" option to
> kill the UPS rather than monitor it. (If I understand Roger's di
On Oct 5, 2016, at 10:59 PM, Jeff Bowman wrote:
>
>> The command is "upsdrvctl shutdown".
>
> That's what I thought, but I get this:
>
> Can't claim USB device [051d:0003]: libusb0-dll:err [claim_interface] could
> not
> claim interface 0, win error: The requested resource is in use.
>
> Dr
> > How does this work in conjunction with the UPS hardware? Does NUT
> > immediately send a command to the UPS to wait for 300 seconds and then
> > shut itself down, thereby allowing the server enough time to safely
> > shut itself down as well?
>
> Yes.
Very good, thank you.
> The command i
On Wed, 5 Oct 2016, Jeff Bowman wrote:
I’m trying to better understand OffDelay and OnDelay:
http://networkupstools.org/docs/man/usbhid-ups.html#_extra_arguments
My server requires ~3½ minutes to shut itself down. Considering this I’m
comfortable setting OffDelay to 300 (five minutes).
How
I'm trying to better understand OffDelay and OnDelay:
http://networkupstools.org/docs/man/usbhid-ups.html#_extra_arguments
My server requires ~3½ minutes to shut itself down. Considering this I'm
comfortable setting OffDelay to 300 (five minutes).
How does this work in conjunction with the UPS
6 matches
Mail list logo