1CTDB.SYSCONFIG(5) CTDB - clustered TDB database CTDB.SYSCONFIG(5)
2
6 ctdb.sysconfig - CTDB daemon configuration file
7
9 This file contains configuration that affects the operation of CTDB.
10 This is a distribution-specific service configuration file such as
11 /etc/sysconfig/ctdb (Red Hat) or /etc/default/ctdb (Debian) and is a
12 shell script (see sh(1)).
13
15 CTDB_INIT_STYLE=debian|redhat|suse
16 This is the init style used by the Linux distribution (or other
17 operating system) being used. This is usually determined
18 dynamically by checking the system. This variable is used by the
19 initscript to determine which init system primitives to use. It is
20 also used by some eventscripts to choose the name of initscripts
21 for certain services, since these can vary between distributions.
22 If using CTDB's event scripts are unable to determine an
24 appropriate default then this option can also be placed in a
25 relevant ctdb-script.options(5) file.
26 Default: NONE. Guessed, based on features of distribution.
28 CTDB_STARTUP_TIMEOUT=NUM
30 NUM is the number of seconds to wait for ctdbd(1) complete early
31 initialisation up to a point where it is unlikely to abort. If
32 ctdbd doesn't complete the "setup" event before this timeout then
33 it is killed.
34 Defaults: 10
36
38 Maximum number of open files
39 CTDB can use a lot of file descriptors, especially when used with
40 Samba. If there are thousands of smbd processes connected to CTDB when
41 this can mean that thousands of file descriptors are used. For CTDB, it
42 is often necessary to increase limit on the maximum number of open
43 files.
44 The maximum number of open files should be configured using an
46 operating system mechanism.
47 systemd
49 The LimitNOFILE=LIMIT option can be used in a unit/service file
50 increase the maximum number of open files. See systemd.exec(5) for
51 details.
52 SYSV init
54 Use a command like ulimit -n LIMIT to increase the maximum number
55 of open files. This command can be put in the relevant
56 distribution-specific service configuration file.
57 Allowing core dumps
59 Many distributions do not allow core dump files to be generated by
60 default. To assist with debugging, core files can be enabled. This
61 should be configured using an operating system mechanism.
62 systemd
64 The LimitCORE=0|unlimited option can be used in a unit/service
65 file. 0 disallows core files, unlimited allows them. maximum
66 number of open files. See systemd.exec(5) for details.
67 SYSV init
69 Use a command like ulimit -c 0|unlimited to disable or enable core
70 files as required. This command can be put in the relevant
71 distribution-specific service configuration file.
72
74 /etc/sysconfig/ctdb
75 /etc/default/ctdb
76 /etc/ctdb/script.options
77
79 ctdbd(1), ctdb-script.options(5), ctdb(7), http://ctdb.samba.org/
80
82 This documentation was written by Martin Schwenke
83
85 Copyright © 2007 Andrew Tridgell, Ronnie Sahlberg
86 This program is free software; you can redistribute it and/or modify it
88 under the terms of the GNU General Public License as published by the
89 Free Software Foundation; either version 3 of the License, or (at your
90 option) any later version.
91 This program is distributed in the hope that it will be useful, but
93 WITHOUT ANY WARRANTY; without even the implied warranty of
94 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
95 General Public License for more details.
96 You should have received a copy of the GNU General Public License along
98 with this program; if not, see http://www.gnu.org/licenses.
99ctdb 05/11/2019 CTDB.SYSCONFIG(5)