2007-05-30 06:37:03 +04:00
# Options to ctdbd. This is read by /etc/init.d/ctdb
2007-05-28 19:38:04 +04:00
2007-06-02 05:36:42 +04:00
# you must specify the location of a shared lock file across all the
# nodes. This must be on shared storage
# there is no default
# CTDB_RECOVERY_LOCK="/some/place/on/shared/storage"
2007-09-10 09:09:28 +04:00
# when doing IP takeover you also may specify what network interface
# to use by default for the public addresses. Otherwise you must
# specify an interface on each line of the public addresses file
# there is no default
# CTDB_PUBLIC_INTERFACE=eth0
2007-09-04 03:50:07 +04:00
# Should ctdb do IP takeover? If it should, then specify a file
2007-06-02 12:51:05 +04:00
# containing the list of public IP addresses that ctdb will manage
# Note that these IPs must be different from those in $NODES above
2007-09-04 03:50:07 +04:00
# there is no default.
# The syntax is one line per public address of the form :
# <ipaddress>/<netmask> <interface>
# Example: 10.1.1.1/24 eth0
#
2007-06-04 09:44:52 +04:00
# CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses
2007-06-02 12:51:05 +04:00
2007-10-10 03:42:32 +04:00
# Should ctdb implement a single public ip address across the entire cluster
# and multiplex incoming connections across the connected nodes
# When using a single public ip you must also specify the public interface!
# This makes all incoming traffic go through a single ctdb node which
# will then forward the packets out acros the other nodes. This will
# impact performance.
# CTDB_SINGLE_PUBLIC_IP=10.1.1.1
2007-06-02 12:51:05 +04:00
# should ctdb manage starting/stopping the Samba service for you?
# default is to not manage Samba
# CTDB_MANAGES_SAMBA=yes
2007-06-02 05:36:42 +04:00
2007-11-14 08:17:52 +03:00
# should ctdb manage starting/stopping Winbind service?
2007-11-18 07:14:54 +03:00
# if left comented out then it will be autodetected based on smb.conf
2007-11-14 08:17:52 +03:00
# CTDB_MANAGES_WINBIND=yes
2007-06-05 09:18:37 +04:00
# you may wish to raise the file descriptor limit for ctdb
# use a ulimit command here. ctdb needs one file descriptor per
# connected client (ie. one per connected client in Samba)
# ulimit -n 10000
2007-05-30 06:37:03 +04:00
# the NODES file must be specified or ctdb won't start
# it should contain a list of IPs that ctdb will use
# it must be exactly the same on all cluster nodes
# defaults to /etc/ctdb/nodes
2007-06-04 09:44:52 +04:00
# CTDB_NODES=/etc/ctdb/nodes
2007-05-30 06:37:03 +04:00
# the directory to put the local ctdb database files in
# defaults to /var/ctdb
2007-06-04 09:44:52 +04:00
# CTDB_DBDIR=/var/ctdb
2007-05-30 06:37:03 +04:00
2007-09-21 10:12:04 +04:00
# the directory to put the local persistent ctdb database files in
# defaults to /var/ctdb/persistent
# CTDB_DBDIR_PERSISTENT=/var/ctdb/persistent
2007-08-15 08:44:03 +04:00
# the directory where service specific event scripts are stored
# defaults to /etc/ctdb/events.d
# CTDB_EVENT_SCRIPT_DIR=/etc/ctdb/events.d
2007-05-30 06:37:03 +04:00
# the location of the local ctdb socket
# defaults to /tmp/ctdb.socket
2007-05-29 10:02:02 +04:00
# CTDB_SOCKET=/tmp/ctdb.socket
2007-05-30 06:37:03 +04:00
# what transport to use. Only tcp is currently supported
# defaults to tcp
2007-06-04 09:44:52 +04:00
# CTDB_TRANSPORT="tcp"
2007-05-30 06:37:03 +04:00
# where to log messages
# the default is /var/log/log.ctdb
2007-06-04 09:44:52 +04:00
# CTDB_LOGFILE=/var/log/log.ctdb
2007-05-30 06:37:03 +04:00
# what debug level to run at. Higher means more verbose
# the default is 0
2007-06-04 09:44:52 +04:00
# CTDB_DEBUGLEVEL=0
2007-05-29 10:02:02 +04:00
2007-06-04 14:05:31 +04:00
# set any default tuning options for ctdb
# use CTDB_SET_XXXX=value where XXXX is the name of the tuning
# variable
# for example
# CTDB_SET_TRAVERSETIMEOUT=60
# you can get a list of variables using "ctdb listvars"
2007-05-30 06:37:03 +04:00
# any other options you might want. Run ctdbd --help for a list
2007-05-29 10:02:02 +04:00
# CTDB_OPTIONS=