[SCM] CTDB repository - branch master updated - ctdb-1.13-330-g6871415

Amitay Isaacs amitay at samba.org
Tue Oct 23 19:43:09 MDT 2012


The branch, master has been updated
       via  6871415f6cb50c4f9753067359f0e264d3f93871 (commit)
       via  f3888712298f1de7cc7eb51f50c22080fa64e3c0 (commit)
       via  0019291371af1e63ee132ed173ba7f52a0291a44 (commit)
       via  19fb26346567d2249b1237f92d871022db2ba8cd (commit)
       via  69f0473b72aadab5bd5791ccff2facd0cd469d43 (commit)
       via  3274cffe2052953b34141a82de6053b747532a88 (commit)
       via  db987eeb3c6e10552a1c1334bf263eb66fcad9ab (commit)
       via  b3eac871895cc586bcc671835e882b136e466b98 (commit)
       via  12e4a3e2953842b4c3842bf920fe2086df4fe46c (commit)
       via  4250c7ebe369e73cf29ff910bb9bfc929735408c (commit)
      from  c18ec8ec234cb71da6cc77b1aadc398f57187947 (commit)

http://gitweb.samba.org/?p=ctdb.git;a=shortlog;h=master


- Log -----------------------------------------------------------------
commit 6871415f6cb50c4f9753067359f0e264d3f93871
Author: Amitay Isaacs <amitay at gmail.com>
Date:   Mon Oct 22 18:04:09 2012 +1100

    packaging: Bundle README, COPYING and html version of manpages
    
    Signed-off-by: Amitay Isaacs <amitay at gmail.com>

commit f3888712298f1de7cc7eb51f50c22080fa64e3c0
Author: Amitay Isaacs <amitay at gmail.com>
Date:   Mon Oct 22 17:43:32 2012 +1100

    doc: Do not keep the built version of manpages in version control
    
    Generated docs will be bundled with release tarballs. No need to keep
    them in git. This avoids the need to commit the generated doc version
    if source xml is modified.
    
    Signed-off-by: Amitay Isaacs <amitay at gmail.com>

commit 0019291371af1e63ee132ed173ba7f52a0291a44
Author: Amitay Isaacs <amitay at gmail.com>
Date:   Mon Oct 22 15:12:50 2012 +1100

    packaging: Use common code to generate VERSION string
    
    Signed-off-by: Amitay Isaacs <amitay at gmail.com>

commit 19fb26346567d2249b1237f92d871022db2ba8cd
Author: Amitay Isaacs <amitay at gmail.com>
Date:   Mon Oct 22 15:08:41 2012 +1100

    packaging: Factor out the code to genreate VERSION string
    
    Signed-off-by: Amitay Isaacs <amitay at gmail.com>

commit 69f0473b72aadab5bd5791ccff2facd0cd469d43
Author: Amitay Isaacs <amitay at gmail.com>
Date:   Mon Oct 22 15:55:33 2012 +1100

    packaging: Build docs and include them in tarball
    
    Signed-off-by: Amitay Isaacs <amitay at gmail.com>

commit 3274cffe2052953b34141a82de6053b747532a88
Author: Amitay Isaacs <amitay at gmail.com>
Date:   Wed Oct 17 10:09:26 2012 +1100

    build: Extract building of manpages in a separate Makefile
    
    This can then be used to build manpages/html when creating tarball.
    Do not build docs during a regular build, but only for install.
    
    Signed-off-by: Amitay Isaacs <amitay at gmail.com>

commit db987eeb3c6e10552a1c1334bf263eb66fcad9ab
Author: Amitay Isaacs <amitay at gmail.com>
Date:   Mon Oct 22 10:52:06 2012 +1100

    doc: README - add information about CTDB, license and website

commit b3eac871895cc586bcc671835e882b136e466b98
Author: Amitay Isaacs <amitay at gmail.com>
Date:   Wed Oct 17 11:27:32 2012 +1100

    web: Add posix locking information to prerequisites
    
    Signed-off-by: Amitay Isaacs <amitay at gmail.com>

commit 12e4a3e2953842b4c3842bf920fe2086df4fe46c
Author: Amitay Isaacs <amitay at gmail.com>
Date:   Wed Oct 17 11:26:52 2012 +1100

    web: Add the links to ftp/http ctdb download area
    
    Signed-off-by: Amitay Isaacs <amitay at gmail.com>

commit 4250c7ebe369e73cf29ff910bb9bfc929735408c
Author: Amitay Isaacs <amitay at gmail.com>
Date:   Wed Oct 17 11:25:46 2012 +1100

    web: Remove reference to non-existent config files
    
    Signed-off-by: Amitay Isaacs <amitay at gmail.com>

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

Summary of changes:
 Makefile.in                |   26 +-
 README                     |    8 +
 doc/Makefile               |   16 +
 doc/ctdb.1                 | 1053 -----------------------------------------
 doc/ctdb.1.html            |  812 --------------------------------
 doc/ctdbd.1                | 1117 --------------------------------------------
 doc/ctdbd.1.html           |  995 ---------------------------------------
 doc/ltdbtool.1             |  258 ----------
 doc/ltdbtool.1.html        |   84 ----
 doc/onnode.1               |  239 ----------
 doc/onnode.1.html          |  129 -----
 doc/ping_pong.1            |  110 -----
 doc/ping_pong.1.html       |   37 --
 packaging/RPM/ctdb.spec.in |    7 +
 packaging/RPM/makerpms.sh  |   30 +-
 packaging/maketarball.sh   |   27 +-
 packaging/mkversion.sh     |   50 ++
 web/configuring.html       |    4 +-
 web/download.html          |   11 +-
 web/prerequisites.html     |   22 +-
 20 files changed, 135 insertions(+), 4900 deletions(-)
 create mode 100644 README
 create mode 100644 doc/Makefile
 delete mode 100644 doc/ctdb.1
 delete mode 100644 doc/ctdb.1.html
 delete mode 100644 doc/ctdbd.1
 delete mode 100644 doc/ctdbd.1.html
 delete mode 100644 doc/ltdbtool.1
 delete mode 100644 doc/ltdbtool.1.html
 delete mode 100644 doc/onnode.1
 delete mode 100644 doc/onnode.1.html
 delete mode 100644 doc/ping_pong.1
 delete mode 100644 doc/ping_pong.1.html
 create mode 100755 packaging/mkversion.sh


Changeset truncated at 500 lines:

diff --git a/Makefile.in b/Makefile.in
index efc6622..3294503 100755
--- a/Makefile.in
+++ b/Makefile.in
@@ -110,9 +110,9 @@ SBINS = bin/ctdbd
 
 DIRS = lib bin tests/bin
 
-.SUFFIXES: .c .o .h .1 .1.xml .1.html
+.SUFFIXES: .c .o .h
 
-all: showflags dirs doc $(CTDB_SERVER_OBJ) $(CTDB_CLIENT_OBJ) $(CTDB_LIB_OBJ) $(BINS) $(SBINS) $(TEST_BINS)
+all: showflags dirs $(CTDB_SERVER_OBJ) $(CTDB_CLIENT_OBJ) $(CTDB_LIB_OBJ) $(BINS) $(SBINS) $(TEST_BINS)
 
 showflags:
 	@echo 'ctdb will be compiled with flags:'
@@ -285,17 +285,8 @@ tests/bin/ibwrapper_test: $(CTDB_CLIENT_OBJ) ib/ibwrapper_test.o
 	@echo Linking $@
 	@$(CC) $(CFLAGS) -o $@ ib/ibwrapper_test.o $(CTDB_CLIENT_OBJ) $(LIB_FLAGS)
 
-.1.xml.1:
-	-test -z "$(XSLTPROC)" || $(XSLTPROC) -o $@ http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl $<
-
-.1.xml.1.html:
-	-test -z "$(XSLTPROC)" || $(XSLTPROC) -o $@ http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl $<
-
-doc: doc/ctdb.1 doc/ctdb.1.html \
-	doc/ctdbd.1 doc/ctdbd.1.html \
-	doc/onnode.1 doc/onnode.1.html \
-	doc/ltdbtool.1 doc/ltdbtool.1.html \
-	doc/ping_pong.1 doc/ping_pong.1.html
+manpages:
+	$(MAKE) -C doc
 
 clean:
 	rm -f *.o */*.o */*.a */*/*.o */*~
@@ -308,7 +299,7 @@ distclean: clean
 	rm -f config.log config.status config.cache config.h
 	rm -f Makefile
 
-install: all $(PMDA_INSTALL)
+install: all manpages $(PMDA_INSTALL)
 	mkdir -p $(DESTDIR)$(libdir)/pkgconfig
 	mkdir -p $(DESTDIR)$(bindir)
 	mkdir -p $(DESTDIR)$(sbindir)
@@ -330,6 +321,8 @@ install: all $(PMDA_INSTALL)
 	${INSTALLCMD} -m 644 include/ctdb_typesafe_cb.h $(DESTDIR)$(includedir)
 	${INSTALLCMD} -m 644 config/functions $(DESTDIR)$(etcdir)/ctdb
 	${INSTALLCMD} -m 755 config/statd-callout $(DESTDIR)$(etcdir)/ctdb
+	${INSTALLCMD} -m 644 README $(DESTDIR)$(docdir)/ctdb/README
+	${INSTALLCMD} -m 644 COPYING $(DESTDIR)$(docdir)/ctdb/COPYING
 	${INSTALLCMD} -m 644 config/events.d/README $(DESTDIR)$(docdir)/ctdb/README.eventscripts
 	${INSTALLCMD} -m 644 doc/recovery-process.txt $(DESTDIR)$(docdir)/ctdb/recovery-process.txt
 	${INSTALLCMD} -m 755 config/events.d/00.ctdb $(DESTDIR)$(etcdir)/ctdb/events.d
@@ -358,6 +351,11 @@ install: all $(PMDA_INSTALL)
 	if [ -f doc/onnode.1 ];then ${INSTALLCMD} -m 644 doc/onnode.1 $(DESTDIR)$(mandir)/man1; fi
 	if [ -f doc/ltdbtool.1 ]; then ${INSTALLCMD} -m 644 doc/ltdbtool.1 $(DESTDIR)$(mandir)/man1; fi
 	if [ -f doc/ping_pong.1 ];then ${INSTALLCMD} -m 644 doc/ping_pong.1 $(DESTDIR)$(mandir)/man1; fi
+	if [ -f doc/ctdb.1.html ];then ${INSTALLCMD} -m 644 doc/ctdb.1.html $(DESTDIR)$(docdir)/ctdb; fi
+	if [ -f doc/ctdbd.1.html ];then ${INSTALLCMD} -m 644 doc/ctdbd.1.html $(DESTDIR)$(docdir)/ctdb; fi
+	if [ -f doc/onnode.1.html ];then ${INSTALLCMD} -m 644 doc/onnode.1.html $(DESTDIR)$(docdir)/ctdb; fi
+	if [ -f doc/ltdbtool.1.html ];then ${INSTALLCMD} -m 644 doc/ltdbtool.1.html $(DESTDIR)$(docdir)/ctdb; fi
+	if [ -f doc/ping_pong.1.html ];then ${INSTALLCMD} -m 644 doc/ping_pong.1.html $(DESTDIR)$(docdir)/ctdb; fi
 	if [ ! -f $(DESTDIR)$(etcdir)/ctdb/notify.sh ];then ${INSTALLCMD} -m 755 config/notify.sh $(DESTDIR)$(etcdir)/ctdb; fi
 	${INSTALLCMD} -m 755 config/debug-hung-script.sh $(DESTDIR)$(etcdir)/ctdb
 	if [ ! -f $(DESTDIR)$(etcdir)/ctdb/ctdb-crash-cleanup.sh ];then ${INSTALLCMD} -m 755 config/ctdb-crash-cleanup.sh $(DESTDIR)$(etcdir)/ctdb; fi
diff --git a/README b/README
new file mode 100644
index 0000000..3099a6d
--- /dev/null
+++ b/README
@@ -0,0 +1,8 @@
+This is the release version of CTDB, a clustered implementation of TDB
+database used by Samba and other projects to store temporary data.
+
+This software is freely distributable under the GNU public license,
+a copy of which you should have received with this software (in a file
+called COPYING).
+
+For documentation on CTDB, please visit CTDB website http://ctdb.samba.org.
diff --git a/doc/Makefile b/doc/Makefile
new file mode 100644
index 0000000..2f7d41d
--- /dev/null
+++ b/doc/Makefile
@@ -0,0 +1,16 @@
+DOCS = ctdb.1 ctdb.1.html \
+	ctdbd.1 ctdbd.1.html \
+	onnode.1 onnode.1.html \
+	ltdbtool.1 ltdbtool.1.html \
+	ping_pong.1 ping_pong.1.html
+
+all: $(DOCS)
+
+%.1: %.1.xml
+	xsltproc -o $@ http://docbook.sourceforge.net/release/xsl/current/manpages/docbook.xsl $<
+
+%.1.html: %.1.xml
+	xsltproc -o $@ http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl $<
+
+distclean:
+	rm -f $(DOCS)
diff --git a/doc/ctdb.1 b/doc/ctdb.1
deleted file mode 100644
index 74086fa..0000000
--- a/doc/ctdb.1
+++ /dev/null
@@ -1,1053 +0,0 @@
-'\" t
-.\"     Title: ctdb
-.\"    Author: [FIXME: author] [see http://docbook.sf.net/el/author]
-.\" Generator: DocBook XSL Stylesheets v1.76.1 <http://docbook.sf.net/>
-.\"      Date: 10/22/2012
-.\"    Manual: CTDB - clustered TDB database
-.\"    Source: ctdb
-.\"  Language: English
-.\"
-.TH "CTDB" "1" "10/22/2012" "ctdb" "CTDB \- clustered TDB database"
-.\" -----------------------------------------------------------------
-.\" * Define some portability stuff
-.\" -----------------------------------------------------------------
-.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-.\" http://bugs.debian.org/507673
-.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
-.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-.ie \n(.g .ds Aq \(aq
-.el       .ds Aq '
-.\" -----------------------------------------------------------------
-.\" * set default formatting
-.\" -----------------------------------------------------------------
-.\" disable hyphenation
-.nh
-.\" disable justification (adjust text to left margin only)
-.ad l
-.\" -----------------------------------------------------------------
-.\" * MAIN CONTENT STARTS HERE *
-.\" -----------------------------------------------------------------
-.SH "NAME"
-ctdb \- clustered tdb database management utility
-.SH "SYNOPSIS"
-.HP \w'\fBctdb\ [\ OPTIONS\ ]\ COMMAND\ \&.\&.\&.\fR\ 'u
-\fBctdb [ OPTIONS ] COMMAND \&.\&.\&.\fR
-.HP \w'\fBctdb\fR\ 'u
-\fBctdb\fR [\-n\ <node>] [\-Y] [\-t\ <timeout>] [\-T\ <timelimit>] [\-?\ \-\-help] [\-\-usage] [\-d\ \-\-debug=<INTEGER>] [\-\-socket=<filename>] [\-\-print\-emptyrecords] [\-\-print\-datasize] [\-\-print\-lmaster] [\-\-print\-hash] [\-\-print\-recordflags]
-.SH "DESCRIPTION"
-.PP
-ctdb is a utility to view and manage a ctdb cluster\&.
-.SH "OPTIONS"
-.PP
-\-n <pnn>
-.RS 4
-This specifies the physical node number on which to execute the command\&. Default is to run the command on the daemon running on the local host\&.
-.sp
-The physical node number is an integer that describes the node in the cluster\&. The first node has physical node number 0\&.
-.RE
-.PP
-\-Y
-.RS 4
-Produce output in machine readable form for easier parsing by scripts\&. Not all commands support this option\&.
-.RE
-.PP
-\-t <timeout>
-.RS 4
-How long should ctdb wait for the local ctdb daemon to respond to a command before timing out\&. Default is 3 seconds\&.
-.RE
-.PP
-\-T <timelimit>
-.RS 4
-A limit on how long the ctdb command will run for before it will be aborted\&. When this timelimit has been exceeded the ctdb command will terminate\&.
-.RE
-.PP
-\-? \-\-help
-.RS 4
-Print some help text to the screen\&.
-.RE
-.PP
-\-\-usage
-.RS 4
-Print useage information to the screen\&.
-.RE
-.PP
-\-d \-\-debug=<debuglevel>
-.RS 4
-Change the debug level for the command\&. Default is 0\&.
-.RE
-.PP
-\-\-socket=<filename>
-.RS 4
-Specify the socketname to use when connecting to the local ctdb daemon\&. The default is /tmp/ctdb\&.socket \&.
-.sp
-You only need to specify this parameter if you run multiple ctdb daemons on the same physical host and thus can not use the default name for the domain socket\&.
-.RE
-.PP
-\-\-print\-emptyrecords
-.RS 4
-This enables printing of empty records when dumping databases with the catdb, cattbd and dumpdbbackup commands\&. Records with empty data segment are considered deleted by ctdb and cleaned by the vacuuming mechanism, so this switch can come in handy for debugging the vacuuming behaviour\&.
-.RE
-.PP
-\-\-print\-datasize
-.RS 4
-This lets database dumps (catdb, cattdb, dumpdbbackup) print the size of the record data instead of dumping the data contents\&.
-.RE
-.PP
-\-\-print\-lmaster
-.RS 4
-This lets catdb print the lmaster for each record\&.
-.RE
-.PP
-\-\-print\-hash
-.RS 4
-This lets database dumps (catdb, cattdb, dumpdbbackup) print the hash for each record\&.
-.RE
-.PP
-\-\-print\-recordflags
-.RS 4
-This lets catdb and dumpdbbackup print the record flags for each record\&. Note that cattdb always prints the flags\&.
-.RE
-.SH "ADMINISTRATIVE COMMANDS"
-.PP
-These are commands used to monitor and administrate a CTDB cluster\&.
-.SS "pnn"
-.PP
-This command displays the pnn of the current node\&.
-.SS "status"
-.PP
-This command shows the current status of the ctdb node\&.
-.sp
-.it 1 an-trap
-.nr an-no-space-flag 1
-.nr an-break-flag 1
-.br
-.ps +1
-\fBnode status\fR
-.RS 4
-.PP
-Node status reflects the current status of the node\&. There are five possible states:
-.PP
-OK \- This node is fully functional\&.
-.PP
-DISCONNECTED \- This node could not be connected through the network and is currently not participating in the cluster\&. If there is a public IP address associated with this node it should have been taken over by a different node\&. No services are running on this node\&.
-.PP
-DISABLED \- This node has been administratively disabled\&. This node is still functional and participates in the CTDB cluster but its IP addresses have been taken over by a different node and no services are currently being hosted\&.
-.PP
-UNHEALTHY \- A service provided by this node is malfunctioning and should be investigated\&. The CTDB daemon itself is operational and participates in the cluster\&. Its public IP address has been taken over by a different node and no services are currnetly being hosted\&. All unhealthy nodes should be investigated and require an administrative action to rectify\&.
-.PP
-BANNED \- This node failed too many recovery attempts and has been banned from participating in the cluster for a period of RecoveryBanPeriod seconds\&. Any public IP address has been taken over by other nodes\&. This node does not provide any services\&. All banned nodes should be investigated and require an administrative action to rectify\&. This node does not perticipate in the CTDB cluster but can still be communicated with\&. I\&.e\&. ctdb commands can be sent to it\&.
-.PP
-STOPPED \- A node that is stopped does not host any public ip addresses, nor is it part of the VNNMAP\&. A stopped node can not become LVSMASTER, RECMASTER or NATGW\&. This node does not perticipate in the CTDB cluster but can still be communicated with\&. I\&.e\&. ctdb commands can be sent to it\&.
-.PP
-PARTIALLYONLINE \- A node that is partially online participates in a cluster like a node that is ok\&. Some interfaces to serve public ip addresses are down, but at least one interface is up\&. See also "ctdb ifaces"\&.
-.RE
-.sp
-.it 1 an-trap
-.nr an-no-space-flag 1
-.nr an-break-flag 1
-.br
-.ps +1
-\fBgeneration\fR
-.RS 4
-.PP
-The generation id is a number that indicates the current generation of a cluster instance\&. Each time a cluster goes through a reconfiguration or a recovery its generation id will be changed\&.
-.PP
-This number does not have any particular meaning other than to keep track of when a cluster has gone through a recovery\&. It is a random number that represents the current instance of a ctdb cluster and its databases\&. CTDBD uses this number internally to be able to tell when commands to operate on the cluster and the databases was issued in a different generation of the cluster, to ensure that commands that operate on the databases will not survive across a cluster database recovery\&. After a recovery, all old outstanding commands will automatically become invalid\&.
-.PP
-Sometimes this number will be shown as "INVALID"\&. This only means that the ctdbd daemon has started but it has not yet merged with the cluster through a recovery\&. All nodes start with generation "INVALID" and are not assigned a real generation id until they have successfully been merged with a cluster through a recovery\&.
-.RE
-.sp
-.it 1 an-trap
-.nr an-no-space-flag 1
-.nr an-break-flag 1
-.br
-.ps +1
-\fBVNNMAP\fR
-.RS 4
-.PP
-The list of Virtual Node Numbers\&. This is a list of all nodes that actively participates in the cluster and that share the workload of hosting the Clustered TDB database records\&. Only nodes that are participating in the vnnmap can become lmaster or dmaster for a database record\&.
-.RE
-.sp
-.it 1 an-trap
-.nr an-no-space-flag 1
-.nr an-break-flag 1
-.br
-.ps +1
-\fBRecovery mode\fR
-.RS 4
-.PP
-This is the current recovery mode of the cluster\&. There are two possible modes:
-.PP
-NORMAL \- The cluster is fully operational\&.
-.PP
-RECOVERY \- The cluster databases have all been frozen, pausing all services while the cluster awaits a recovery process to complete\&. A recovery process should finish within seconds\&. If a cluster is stuck in the RECOVERY state this would indicate a cluster malfunction which needs to be investigated\&.
-.PP
-Once the recovery master detects an inconsistency, for example a node becomes disconnected/connected, the recovery daemon will trigger a cluster recovery process, where all databases are remerged across the cluster\&. When this process starts, the recovery master will first "freeze" all databases to prevent applications such as samba from accessing the databases and it will also mark the recovery mode as RECOVERY\&.
-.PP
-When CTDBD starts up, it will start in RECOVERY mode\&. Once the node has been merged into a cluster and all databases have been recovered, the node mode will change into NORMAL mode and the databases will be "thawed", allowing samba to access the databases again\&.
-.RE
-.sp
-.it 1 an-trap
-.nr an-no-space-flag 1
-.nr an-break-flag 1
-.br
-.ps +1
-\fBRecovery master\fR
-.RS 4
-.PP
-This is the cluster node that is currently designated as the recovery master\&. This node is responsible of monitoring the consistency of the cluster and to perform the actual recovery process when reqired\&.
-.PP
-Only one node at a time can be the designated recovery master\&. Which node is designated the recovery master is decided by an election process in the recovery daemons running on each node\&.
-.RE
-.PP
-Example: ctdb status
-.PP
-Example output:
-.sp
-.if n \{\
-.RS 4
-.\}
-.nf
-Number of nodes:4
-pnn:0 11\&.1\&.2\&.200       OK (THIS NODE)
-pnn:1 11\&.1\&.2\&.201       OK
-pnn:2 11\&.1\&.2\&.202       OK
-pnn:3 11\&.1\&.2\&.203       OK
-Generation:1362079228
-Size:4
-hash:0 lmaster:0
-hash:1 lmaster:1
-hash:2 lmaster:2
-hash:3 lmaster:3
-Recovery mode:NORMAL (0)
-Recovery master:0
-      
-.fi
-.if n \{\
-.RE
-.\}
-.SS "recmaster"
-.PP
-This command shows the pnn of the node which is currently the recmaster\&.
-.SS "uptime"
-.PP
-This command shows the uptime for the ctdb daemon\&. When the last recovery or ip\-failover completed and how long it took\&. If the "duration" is shown as a negative number, this indicates that there is a recovery/failover in progress and it started that many seconds ago\&.
-.PP
-Example: ctdb uptime
-.PP
-Example output:
-.sp
-.if n \{\
-.RS 4
-.\}
-.nf
-Current time of node          :                Thu Oct 29 10:38:54 2009
-Ctdbd start time              : (000 16:54:28) Wed Oct 28 17:44:26 2009
-Time of last recovery/failover: (000 16:53:31) Wed Oct 28 17:45:23 2009
-Duration of last recovery/failover: 2\&.248552 seconds
-      
-.fi
-.if n \{\
-.RE
-.\}
-.SS "listnodes"
-.PP
-This command shows lists the ip addresses of all the nodes in the cluster\&.
-.PP
-Example: ctdb listnodes
-.PP
-Example output:
-.sp
-.if n \{\
-.RS 4
-.\}
-.nf
-10\&.0\&.0\&.71
-10\&.0\&.0\&.72
-10\&.0\&.0\&.73
-10\&.0\&.0\&.74
-      
-.fi
-.if n \{\
-.RE
-.\}
-.SS "ping"
-.PP
-This command will "ping" all CTDB daemons in the cluster to verify that they are processing commands correctly\&.
-.PP
-Example: ctdb ping
-.PP
-Example output:
-.sp
-.if n \{\
-.RS 4
-.\}
-.nf
-response from 0 time=0\&.000054 sec  (3 clients)
-response from 1 time=0\&.000144 sec  (2 clients)
-response from 2 time=0\&.000105 sec  (2 clients)
-response from 3 time=0\&.000114 sec  (2 clients)
-      
-.fi
-.if n \{\
-.RE
-.\}
-.SS "ifaces"
-.PP
-This command will display the list of network interfaces, which could host public addresses, along with their status\&.
-.PP
-Example: ctdb ifaces
-.PP
-Example output:
-.sp
-.if n \{\
-.RS 4
-.\}
-.nf
-Interfaces on node 0
-name:eth5 link:up references:2
-name:eth4 link:down references:0
-name:eth3 link:up references:1
-name:eth2 link:up references:1
-      
-.fi
-.if n \{\
-.RE
-.\}
-.PP
-Example: ctdb ifaces \-Y
-.PP
-Example output:
-.sp
-.if n \{\
-.RS 4
-.\}
-.nf
-:Name:LinkStatus:References:
-:eth5:1:2
-:eth4:0:0
-:eth3:1:1
-:eth2:1:1
-      
-.fi
-.if n \{\
-.RE
-.\}
-.SS "setifacelink <iface> <status>"
-.PP
-This command will set the status of a network interface\&. The status needs to be "up" or "down"\&. This is typically used in the 10\&.interfaces script in the "monitor" event\&.
-.PP
-Example: ctdb setifacelink eth0 up
-.SS "ip"
-.PP
-This command will display the list of public addresses that are provided by the cluster and which physical node is currently serving this ip\&. By default this command will ONLY show those public addresses that are known to the node itself\&. To see the full list of all public ips across the cluster you must use "ctdb ip \-n all"\&.
-.PP
-Example: ctdb ip
-.PP
-Example output:
-.sp
-.if n \{\
-.RS 4
-.\}
-.nf
-Public IPs on node 0
-172\&.31\&.91\&.82 node[1] active[] available[eth2,eth3] configured[eth2,eth3]
-172\&.31\&.91\&.83 node[0] active[eth3] available[eth2,eth3] configured[eth2,eth3]
-172\&.31\&.91\&.84 node[1] active[] available[eth2,eth3] configured[eth2,eth3]
-172\&.31\&.91\&.85 node[0] active[eth2] available[eth2,eth3] configured[eth2,eth3]
-172\&.31\&.92\&.82 node[1] active[] available[eth5] configured[eth4,eth5]
-172\&.31\&.92\&.83 node[0] active[eth5] available[eth5] configured[eth4,eth5]
-172\&.31\&.92\&.84 node[1] active[] available[eth5] configured[eth4,eth5]
-172\&.31\&.92\&.85 node[0] active[eth5] available[eth5] configured[eth4,eth5]
-      
-.fi
-.if n \{\
-.RE
-.\}
-.PP
-Example: ctdb ip \-Y
-.PP
-Example output:
-.sp
-.if n \{\
-.RS 4
-.\}
-.nf
-:Public IP:Node:ActiveInterface:AvailableInterfaces:ConfiguredInterfaces:
-:172\&.31\&.91\&.82:1::eth2,eth3:eth2,eth3:
-:172\&.31\&.91\&.83:0:eth3:eth2,eth3:eth2,eth3:
-:172\&.31\&.91\&.84:1::eth2,eth3:eth2,eth3:
-:172\&.31\&.91\&.85:0:eth2:eth2,eth3:eth2,eth3:
-:172\&.31\&.92\&.82:1::eth5:eth4,eth5:
-:172\&.31\&.92\&.83:0:eth5:eth5:eth4,eth5:
-:172\&.31\&.92\&.84:1::eth5:eth4,eth5:
-:172\&.31\&.92\&.85:0:eth5:eth5:eth4,eth5:
-      
-.fi
-.if n \{\
-.RE
-.\}
-.SS "ipinfo <ip>"
-.PP
-This command will display details about the specified public addresses\&.


-- 
CTDB repository


More information about the samba-cvs mailing list