diff --git a/ctdb/doc/ctdb.1.xml b/ctdb/doc/ctdb.1.xml
index ce83a3efa0b..887f92d3a36 100644
--- a/ctdb/doc/ctdb.1.xml
+++ b/ctdb/doc/ctdb.1.xml
@@ -324,6 +324,71 @@ Recovery master:0
+ nodestatus [<nodespec>]
+
+ This command is similar to the status
+ command. It displays the "node status" subset of output. The
+ main differences are:
+
+
+
+
+
+ The exit code is the bitwise-OR of the flags for each
+ specified node, while ctdb status exits
+ with 0 if it was able to retrieve status for all nodes.
+
+
+
+
+
+ ctdb status provides status information
+ for all nodes. ctdb nodestatus
+ defaults to providing status for only the current node.
+ If <nodespec> is provided then status is given for
+ the indicated node(s).
+
+
+
+ By default, ctdb nodestatus gathers
+ status from the local node. However, if invoked with "-n
+ all" (or similar) then status is gathered from the given
+ node(s). In particular ctdb nodestatus
+ all and ctdb nodestatus -n
+ all will produce different output. It is
+ possible to provide 2 different nodespecs (with and
+ without "-n") but the output is usually confusing!
+
+
+
+
+
+ A common invocation in scripts is ctdb nodestatus
+ all to check whether all nodes in a cluster are
+ healthy.
+
+
+
+ Example: ctdb nodestatus
+
+ Example output:
+
+# ctdb nodestatus
+pnn:0 10.0.0.30 OK (THIS NODE)
+
+
+
+ Example: ctdb nodestatus all
+
+ Example output:
+
+# ctdb nodestatus all
+Number of nodes:2
+pnn:0 10.0.0.30 OK (THIS NODE)
+pnn:1 10.0.0.31 OK
+
+
+
recmaster
This command shows the pnn of the node which is currently the recmaster.