Ronnie Sahlberg f5c0539dc6 Change how NATGW is configured to allow special nodes that do not have ... network connectivity outside of the cluster to still be able to participate in a natgw group. These nodes can not become natgw master since they lack external network connectivity. These nodes are configured just the same way as for any other node with NATGW, with the following two exceptions : * we do NOT set CTDB_NATGW_PUBLIC_IFACE at all on these nodes. since these ndoes lack external network we should not check the interface for link. * we must set CTDB_NATGW_SLAVE_ONLY=yes to flag that this is a node that can not become natgw master. (This used to be ctdb commit ab7b00a37e55beffc074be95b55d8a5c7cb9eef2)		2010-09-08 09:20:16 +10:00
..
ctdb.1	iupdate the docs that ctdb freeze is no more	2010-08-05 16:35:37 +10:00
ctdb.1.html	document how to restore a backup into a different database	2010-05-20 11:44:18 +10:00
ctdb.1.xml	remove the "ctdb freeze" debugging command	2010-08-05 16:30:47 +10:00
ctdbd.1	Change how NATGW is configured to allow special nodes that do not have	2010-09-08 09:20:16 +10:00
ctdbd.1.html	Change how NATGW is configured to allow special nodes that do not have	2010-09-08 09:20:16 +10:00
ctdbd.1.xml	Change how NATGW is configured to allow special nodes that do not have	2010-09-08 09:20:16 +10:00
onnode.1	onnode documentation - update documentation to reflect recent onnode changes.	2010-02-05 15:30:39 +11:00
onnode.1.html	onnode documentation - update documentation to reflect recent onnode changes.	2010-02-05 15:30:39 +11:00
onnode.1.xml	onnode documentation - update documentation to reflect recent onnode changes.	2010-02-05 15:30:39 +11:00
recovery-process.txt	doc: join broken lines in excerpt from log.ctdb	2009-01-16 20:49:51 +11:00