On Feb 2, 2018, at 8:07 AM, Roger Price wrote:
>
>> # check to see if we need to actually shutdown the UPS then do it
>> /usr/sbin/upsmon -K >/dev/null 2>&1 && /usr/sbin/upsdrvctl shutdown
>
> I don't have NUT + systemd + CentOS/RHEL, but I'm confused by your script.
> "upsdrvctl" is
On Thu, 1 Feb 2018, Lee Damon wrote:
I've "fixed" this problem by modifying the nutshutdown script:
#!/bin/sh
# stop nut driver to free up access to the device
/sbin/systemctl stop nut-driver
# make sure it has time to die
sleep 2
# check to see
> NUT takes charge of sending the required commands through the driver; the
> default values are load.off.delay 20 and load.on.delay 30. These values can
> be
> changed by adding lines such as
>
> offdelay = 30
> ondelay = 100
>
> to the corresponding UPS section in file
On Fri, 2 Feb 2018, nut.user.u...@neverbox.com wrote:
I have an older box set up this way for continuous integration, and it needs
to see more than a few seconds of power loss for the "always turn
on" BIOS setting to work. I forget how many different intervals I tried,
but 30
> I have an older box set up this way for continuous integration, and it needs
> to see more than a few seconds of power loss for the "always turn on" BIOS
> setting to work. I forget how many different intervals I tried, but 30
> seconds of off time is reliable for that particular box.
5 matches
Mail list logo
