Sorry, I'm not entirely familiar with D-bus architecture, but does it run when X isn't running? Most servers won't bother starting X.
As for the difference in shutdown times between USB/serial and networked UPSes, we can take advantage of the shutdown delay variables on most UPSes. On the UPSes I'm using, there's a variable that determines the delay between receiving the output power shutdown signal and the actual event of shutting down outlet power. Most delays are configured between 90s and 270s, so it is plenty of time for us.
Even if a USB/serial connected UPS is signalled to shutdown before the networking service is stopped, it will still have time to shutdown. In my particular case, networking is shutdown immediately after the outlet shutdown signal is sent, and immediately before halt is called. Our servers have 270s to shutdown networking and call halt, which should be plenty of time for everyone.
Sorry, I'm not entirely familiar with D-bus architecture, but does it run when X isn't running? Most servers won't bother starting X.
As for the difference in shutdown times between USB/serial and networked UPSes, we can take advantage of the shutdown delay variables on most UPSes. On the UPSes I'm using, there's a variable that determines the delay between receiving the output power shutdown signal and the actual event of shutting down outlet power. Most delays are configured between 90s and 270s, so it is plenty of time for us.
Even if a USB/serial connected UPS is signalled to shutdown before the networking service is stopped, it will still have time to shutdown. In my particular case, networking is shutdown immediately after the outlet shutdown signal is sent, and immediately before halt is called. Our servers have 270s to shutdown networking and call halt, which should be plenty of time for everyone.
Matt