[Nut-upsuser] ordered shutdown

[Lars Täuber]

Hallo Arjen,

Arjen de Korte <nut+users at de-korte.org> schrieb:
> Citeren Lars Täuber <taeuber at bbaw.de>:
> 
> [...]
> The above values would be an extremely bad idea and this is also not  
> how NUT works. See the FAQ.
> 
[...] 
> What you describe is not how NUT works. Until the UPS signals that the  
> battery is low, it is business as usual (see the FAQ for the reasons  
> behind this). Once the UPS signals battery low, all timers are started  
> at the same time and there is no way to stop the following sequence of  
> events. The systems *will* go down. If the power returns during the  
> shutdown sequence, the shutdown sequence will be completed and NUT  
> will power-cycle the UPS to make sure the connected systems are  
> restarted.

it seems I understood how NUT works now. But then it is not the solution for us. The reason simply is we have one big ups for so many servers. And it's a bad idea to have one point in time to shutdown all servers. So one »battery low« signal for all servers is not what we need.
There are some servers that should  work as long as possible and shut down shortly (2 minutes) before the ups shuts off. But these server also should try to shut down and that's why they need the connection to the ups too.
Is it possible with NUT to tell upsd to initiate a shutdown by the means of upssched? As long as I understood upssched doesn't run as root. So it can't be used to initiate a shutdown directly.

Thanks
Lars