1 # Options to ctdbd. This is read by /etc/init.d/ctdb
3 # you must specify the location of a shared lock file across all the
4 # nodes. This must be on shared storage
6 # CTDB_RECOVERY_LOCK="/some/place/on/shared/storage"
8 # when doing IP takeover you also may specify what network interface
9 # to use by default for the public addresses. Otherwise you must
10 # specify an interface on each line of the public addresses file
12 # CTDB_PUBLIC_INTERFACE=eth0
14 # Should ctdb do IP takeover? If it should, then specify a file
15 # containing the list of public IP addresses that ctdb will manage
16 # Note that these IPs must be different from those in $NODES above
17 # there is no default.
18 # The syntax is one line per public address of the form :
19 # <ipaddress>/<netmask> <interface>
20 # Example: 10.1.1.1/24 eth0
22 # CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses
24 # Should CTDB present the cluster using a single public ip address to clients
25 # and multiplex clients across all CONNECTED nodes ?
26 # This is based on LVS
27 # When this is enabled, the entire cluster will present one single ip address
28 # which clients will connect to.
29 # CTDB_LVS_PUBLIC_IP=10.1.1.1
32 # IPMUX : OBSOLETE use LVS instead
33 # Should ctdb implement a single public ip address across the entire cluster
34 # and multiplex incoming connections across the connected nodes
35 # When using a single public ip you must also specify the public interface!
36 # This makes all incoming traffic go through a single ctdb node which
37 # will then forward the packets out acros the other nodes. This will
39 # CTDB_SINGLE_PUBLIC_IP=10.1.1.1
41 # should ctdb manage starting/stopping the Samba service for you?
42 # default is to not manage Samba
43 # CTDB_MANAGES_SAMBA=yes
45 # should ctdb manage starting/stopping Winbind service?
46 # if left comented out then it will be autodetected based on smb.conf
47 # CTDB_MANAGES_WINBIND=yes
49 # you may wish to raise the file descriptor limit for ctdb
50 # use a ulimit command here. ctdb needs one file descriptor per
51 # connected client (ie. one per connected client in Samba)
54 # the NODES file must be specified or ctdb won't start
55 # it should contain a list of IPs that ctdb will use
56 # it must be exactly the same on all cluster nodes
57 # defaults to /etc/ctdb/nodes
58 # CTDB_NODES=/etc/ctdb/nodes
60 # the directory to put the local ctdb database files in
61 # defaults to /var/ctdb
62 # CTDB_DBDIR=/var/ctdb
64 # the directory to put the local persistent ctdb database files in
65 # defaults to /var/ctdb/persistent
66 # CTDB_DBDIR_PERSISTENT=/var/ctdb/persistent
68 # the directory where service specific event scripts are stored
69 # defaults to /etc/ctdb/events.d
70 # CTDB_EVENT_SCRIPT_DIR=/etc/ctdb/events.d
72 # the location of the local ctdb socket
73 # defaults to /tmp/ctdb.socket
74 # CTDB_SOCKET=/tmp/ctdb.socket
76 # what transport to use. Only tcp is currently supported
78 # CTDB_TRANSPORT="tcp"
80 # where to log messages
81 # the default is /var/log/log.ctdb
82 # CTDB_LOGFILE=/var/log/log.ctdb
84 # what debug level to run at. Higher means more verbose
88 # set any default tuning options for ctdb
89 # use CTDB_SET_XXXX=value where XXXX is the name of the tuning
92 # CTDB_SET_TRAVERSETIMEOUT=60
93 # you can get a list of variables using "ctdb listvars"
96 # any other options you might want. Run ctdbd --help for a list