Technically, looking at `git blame docs/man/nut.conf.txt` - the option was documented since 2009 at least, it seems.
I believe that entry is more about having a common approach to this problem that is to be addressed by distros and packagers per their SYSV/SMF/systemd/init.d/rc.local/upstart/..... hassles. While for some time NUT does provide "reference" or "sample" contributed scripts, it is more of a convenience to custom builders doing a `make install` and hacking their OS shutdown handling per FAQ and other lore (key words: power race condition avoidance). While we hope that distros benefit from them, no idea if they actually do - or roll their own. That said, I agree it could be publicised better in `nut.conf.sample` installed to systems, at least those who do deliver support for it during shutdowns - and so should be used in the example shutdown-handling scripts for various systems and certain man pages. Jim On Mon, Jun 19, 2023, 22:10 Robert Nichols via Nut-upsdev < [email protected]> wrote: > The 2.8.0 release notes mention adding POWEROFF_WAIT to enhance systemd > support, but this option is not provided in nut.conf or documented > anywhere. It appears that the test of this variable in > /usr/lib/systemd/system-shutdown/nutshutdown would do the right thing > (force a reboot after "upsdrvctl shutdown"), but only if the variable has > been set in nut.conf. > > OS: Rocky Linux 8.8 > nut-2.8.0-3.el8.x86_64 > > -- > Bob Nichols "NOSPAM" is really part of my email address. > Do NOT delete it. > > _______________________________________________ > Nut-upsdev mailing list > [email protected] > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev >
_______________________________________________ Nut-upsdev mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsdev
