diff options
| author | Martin Schwenke <martin@meltin.net> | 2013-01-11 14:09:14 +1100 |
|---|---|---|
| committer | Amitay Isaacs <amitay@gmail.com> | 2013-05-24 14:08:07 +1000 |
| commit | b5ebff6931adf0564bb1cbb98a9283382c578564 (patch) | |
| tree | 99743532faf52b1b502a9612309b70cddb1c9794 /ctdb/doc | |
| parent | 87eb70180aad04dc353c008f48b3b5fe652fa87c (diff) | |
| download | samba-b5ebff6931adf0564bb1cbb98a9283382c578564.tar.gz samba-b5ebff6931adf0564bb1cbb98a9283382c578564.tar.xz samba-b5ebff6931adf0564bb1cbb98a9283382c578564.zip | |
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)
Diffstat (limited to 'ctdb/doc')
| -rw-r--r-- | ctdb/doc/ctdb.1.xml | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/ctdb/doc/ctdb.1.xml b/ctdb/doc/ctdb.1.xml index d1734b7c8f..7242f3aa29 100644 --- a/ctdb/doc/ctdb.1.xml +++ b/ctdb/doc/ctdb.1.xml @@ -382,13 +382,18 @@ response from 3 time=0.000114 sec (2 clients) </screen> </refsect2> - <refsect2><title>runstate</title> + <refsect2><title>runstate [setup|startup|running]</title> <para> Print the runstate of the specified node. Runstates are used to serialise important state transitions in CTDB, particularly during startup. </para> <para> + If one or more optional runstate arguments are specified then + the node must be in one of these runstates for the command to + succeed. + </para> + <para> Example: ctdb runstate </para> <para> |