[nut-Bugs][310987] Docs incorrect on slave shutdown synchronization

nut-bugs at alioth.debian.org nut-bugs at alioth.debian.org
Sun Aug 3 16:11:13 UTC 2008


Bugs item #310987, was opened at 2008-08-03 17:07
Status: Open
>Priority: 1
Submitted By: Jeff Dairiki (dairiki-guest)
>Assigned to: Arjen de Korte (adkorte-guest)
Summary: Docs incorrect on slave shutdown synchronization 
Category: None
Group: None
Resolution: None


Initial Comment:
The docs state that, when a slave upsmon sees an FSD, it runs SHUTDOWNCMD, and then finally disconnects "when killed by init".  (See, e.g., step 4 in http://eu1.networkupstools.org/doc/2.2.0/shutdown.html.)

This is incorrect.   The slave upsmon exits immediately after it runs SHUTDOWNCMD.

Either the docs or upsmon should be fixed so that they agree.

I would much prefer that upsmon be changed to behave as the docs describe.
This would make it possible for the master to wait for all slaves to shutdown --- this would be particularly useful when some of the slaves may have lengthy shutdown sequences (e.g. stopping several xen domains.)

Thank you all for your work on NUT!



----------------------------------------------------------------------

You can respond by visiting: 
http://alioth.debian.org/tracker/?func=detail&atid=411542&aid=310987&group_id=30602



More information about the NUT-tracker mailing list