| 1 |
On 15/11/2014 16:47, Daniel Frey wrote: |
| 2 |
> If the above fails (if the above does indeed fail, some troubleshooting |
| 3 |
> should happen to try to figure out why it doesn't work), KILLDELAY is |
| 4 |
> the parameter you likely seek, but it is dangerous. If you set this it |
| 5 |
> will wait x seconds after a shutdown was requested and forcibly shut |
| 6 |
> down the UPS power. |
| 7 |
> |
| 8 |
> However, in the even that power is restored between the UPS kill and the |
| 9 |
> time it actually turns off the mains will still not be cycled. But |
| 10 |
> theoretically this window should be pretty small. |
| 11 |
> |
| 12 |
> Dan |
| 13 |
> |
| 14 |
> |
| 15 |
|
| 16 |
it does seem as though this hits the issue - that when power fails, the |
| 17 |
ups triggers a shutdown, but the power doesn't fail hard enough to wind |
| 18 |
down the ups too, in which case the machine that is waiting for the |
| 19 |
"offbattery" event is fast asleep and misses the message. it's a shame |
| 20 |
the killpower command does nothing for you. |
| 21 |
|
| 22 |
the only way forward that i see would be to get a small device a la |
| 23 |
raspberry pi, and have that run apcupsd on it. you can then have that |
| 24 |
device run wake on lan if it detects the power is good, and trigger |
| 25 |
remote shutdown when not. |
Archives