Martin Schwenke b5ebff6931 tools/ctdb: "ctdb runstate" now accepts optional expected run state arguments ... If one or more run states are specified then "ctdb runstate" succeeds only if ctdbd is in one of those run states. At the moment, if the "setup" event fails then the initscript succeeds but ctdbd exits almost immediately. This behaviour isn't very friendly. The initscript now waits until ctdbd is in "startup" or "running" run state via the use of "ctdb runstate startup running", meaning that ctdbd has successfully passed the "setup" event. The "setup" event code in 00.ctdb now waits until ctdbd is in the "setup" run state before proceeding via the use of "ctdb runstate setup". Signed-off-by: Martin Schwenke <martin@meltin.net> Pair-programmed-with: Amitay Isaacs <amitay@gmail.com> (This used to be ctdb commit 4a2effcc455be67ff4a779a59ca81ba584312cd6)		2013-05-24 14:08:07 +10:00
..
ctdb.1.xml	tools/ctdb: "ctdb runstate" now accepts optional expected run state arguments	2013-05-24 14:08:07 +10:00
ctdbd.1.xml	recoverd: Fix tunable NoIPTakeoverOnDisabled, rename to NoIPHostOnAllDisabled	2013-05-07 16:20:46 +10:00
ltdbtool.1.xml	ltdbtool: add manpage	2011-05-04 14:38:22 +02:00
Makefile	build: Extract building of manpages in a separate Makefile	2012-10-22 18:15:17 +11:00
onnode.1.xml	doc: Document the new onnode -P option	2012-07-30 15:34:41 +10:00
ping_pong.1.xml	doc: Update ping_pong documentation to add -c option	2012-11-21 19:40:22 +11:00
readonlyrecords.txt	Fix some documentation typos	2012-02-21 10:52:57 +01:00
recovery-process.txt	doc: join broken lines in excerpt from log.ctdb	2009-01-16 20:49:51 +11:00