ctdb.sysconfig — CTDB daemon configuration file
This file contains configuration that affects the operation of
CTDB. This is a distribution-specific service configuration
file such as /etc/sysconfig/ctdb (Red Hat)
or /etc/default/ctdb (Debian) and is a
shell script (see
sh(1)).
This is the init style used by the Linux distribution (or other operating system) being used. This is usually determined dynamically by checking the system. This variable is used by the initscript to determine which init system primitives to use. It is also used by some eventscripts to choose the name of initscripts for certain services, since these can vary between distributions.
If using CTDB's event scripts are unable to determine an appropriate default then this option can also be placed in a relevant ctdb-script.options(5) file.
Default: NONE. Guessed, based on features of distribution.
NUMNUM is the number of seconds to wait for ctdbd(1) complete early initialisation up to a point where it is unlikely to abort. If ctdbd doesn't complete the "setup" event before this timeout then it is killed.
Defaults: 10
CTDB can use a lot of file descriptors, especially when used with Samba. If there are thousands of smbd processes connected to CTDB when this can mean that thousands of file descriptors are used. For CTDB, it is often necessary to increase limit on the maximum number of open files.
The maximum number of open files should be configured using an operating system mechanism.
The
LimitNOFILE=
option can be used in a unit/service file increase the
maximum number of open files. See
systemd.exec(5) for details.
LIMIT
Use a command like ulimit -n
LIMIT to increase the maximum
number of open files. This command can be put in the
relevant distribution-specific service configuration file.
Many distributions do not allow core dump files to be generated by default. To assist with debugging, core files can be enabled. This should be configured using an operating system mechanism.
The LimitCORE=0|unlimited option can
be used in a unit/service file. 0
disallows core files, unlimited
allows them. maximum number of open files. See
systemd.exec(5) for details.
Use a command like ulimit -c 0|unlimited to disable or enable core files as required. This command can be put in the relevant distribution-specific service configuration file.