[Nut-upsuser] NUT 2.0.4-4 - Debian stable - /etc/killpower not created?

Arjen de Korte nut+users at de-korte.org
Tue Apr 29 13:07:55 UTC 2008

> I'm testing the functionality of my NUT-setup (NUT 2.0.4-4 - Debian
> stable). The system is connected to the UPS, but is not powered by it.

Good idea when you're testing your setup.

> When running "upsmon -c fsd", upsmon says "Auto logout and shutdown
> proceeding". This is all well and good, but I never see the machine
> waiting for the UPS to cut the power. Instead it shuts down.
> It's my understanding that upsmon should create /etc/killpower, report
> this found in the syslog, and then wait for the power to be cut.
> Maybe I have misunderstood something?

You have. NUT will indeed create this flag and provided you've made the
necessary changes in your system 'halt' script, this in turn will call
'upsdrvctl shutdown'. Depending on the driver you're using, the actual
shutdown of the UPS may take next to no time at all or up to a minute (or
more) to happen. In the mean time, it is a good idea to not hang around in
the halt script, but to power-off the system in the normal way. The reason
for doing so, is that not all hardware will shutdown without problems if
the power is suddenly cut, even if you've sync'ed your filesystems and/or
(re)mounted them read-only. Therefor, the default behaviour for most
drivers is to shutdown the UPS with a delay to allow the halt script to do
its thing.

Best regards, Arjen
Eindhoven - The Netherlands
Key fingerprint - 66 4E 03 2C 9D B5 CB 9B  7A FE 7E C1 EE 88 BC 57

More information about the Nut-upsuser mailing list