Tests now deviate from the compile-time default by setting CTDB_BASE.
Signed-off-by: Martin Schwenke <martin@meltin.net>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>
# what you are doing.
# CTDB_RECOVERY_LOCK=/some/place/on/shared/storage
-# List of nodes in the cluster. Default is below.
-# CTDB_NODES=/etc/ctdb/nodes
-
# What services should CTDB manage? Default is none.
# CTDB_MANAGES_SAMBA=yes
# CTDB_MANAGES_WINBIND=yes
# build up ctdb_options variable from optional parameters
maybe_set "--logging" "$CTDB_LOGGING"
- maybe_set "--nlist" "$CTDB_NODES"
maybe_set "--listen" "$CTDB_NODE_ADDRESS"
maybe_set "--dbdir" "$CTDB_DBDIR"
maybe_set "--dbdir-persistent" "$CTDB_DBDIR_PERSISTENT"
the cluster and is the address that CTDB daemons will use to
communicate with the CTDB daemons on other nodes.
</para>
+
<para>
- Private addresses are listed in the file specified by the
- <varname>CTDB_NODES</varname> configuration variable (see
- <citerefentry><refentrytitle>ctdbd.conf</refentrytitle>
- <manvolnum>5</manvolnum></citerefentry>, default
- <filename>/usr/local/etc/ctdb/nodes</filename>). This file contains the
- list of private addresses for all nodes in the cluster, one
- per line. This file must be the same on all nodes in the
- cluster.
+ Private addresses are listed in the file
+ <filename>/usr/local/etc/ctdb/nodes</filename>). This file
+ contains the list of private addresses for all nodes in the
+ cluster, one per line. This file must be the same on all nodes
+ in the cluster.
</para>
+
+ <para>
+ Some users like to put this configuration file in their
+ cluster filesystem. A symbolic link should be used in this
+ case.
+ </para>
+
<para>
Private addresses should not be used by clients to connect to
services provided by the cluster.
</listitem>
</varlistentry>
- <varlistentry>
- <term>CTDB_NODES=<parameter>FILENAME</parameter></term>
- <listitem>
- <para>
- Default is <varname>CTDB_BASE</varname>/nodes, so usually
- <filename>/usr/local/etc/ctdb/nodes</filename>. Corresponds to
- <option>--nlist</option>.
- </para>
- </listitem>
- </varlistentry>
-
<varlistentry>
<term>CTDB_NOSETSCHED=yes|no</term>
<listitem>
</para>
<para>
By default ctdbd will select the first address from the
- nodes list that in can bind to. See also
- <citetitle>CTDB_NODES</citetitle>.
+ nodes list that in can bind to. See also the
+ <citetitle>Private address</citetitle> section in
+ <citerefentry><refentrytitle>ctdb</refentrytitle>
+ <manvolnum>7</manvolnum></citerefentry>.
</para>
<para>
This option is only required when automatic address
# 192.168.1.3
# ---------- /etc/ctdb/nodes ----------
#
-CTDB_NODES=/etc/ctdb/nodes
-
#
# Public addresses configuration
#
# 192.168.1.3
# ---------- /etc/ctdb/nodes ----------
#
-CTDB_NODES=/etc/ctdb/nodes
-
# Enable logging to syslog
CTDB_LOGGING=syslog
# 192.168.1.3
# ---------- /etc/ctdb/nodes ----------
#
-CTDB_NODES=/etc/ctdb/nodes
-
#
# Public addresses configuration
#
<listitem>
<para>
Specify an alternative nodes FILENAME to use instead of
- the default. This option overrides the CTDB_NODES
- variable. See the discussion of
+ the default. See the discussion of
<filename>/usr/local/etc/ctdb/nodes</filename> in the
FILES section for more details.
</para>
also searched for in the <filename>$CTDB_BASE</filename>
directory.
</para>
- <para>
- If <envar>CTDB_NODES</envar> is set in configuration then the
- file pointed to by <envar>CTDB_NODES</envar> is used.
- </para>
<para>
Otherwise the default is
- <filename>$CTDB_BASE/nodes</filename>, where
- <envar>CTDB_BASE</envar> defaults to
- <filename>/usr/local/etc/ctdb</filename>.
+ <filename>/usr/local/etc/ctdb/nodes</filename>.
</para>
</listitem>
</varlistentry>
# $f is relative, try in $CTDB_BASE
f="${CTDB_BASE}/${f}"
fi
- elif [ -n "$CTDB_NODES" ] ; then
- f="$CTDB_NODES"
fi
if [ ! -r "$f" ] ; then