| blob | 149aa627f034a65704bb8e56d502095f8eeeffae |
1 <?xml version="1.0" encoding="iso-8859-1"?>
2 <!DOCTYPE refentry
3 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
4 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
6 <refentry id="ctdbd.conf.5">
8 <refmeta>
9 <refentrytitle>ctdbd.conf</refentrytitle>
10 <manvolnum>5</manvolnum>
11 <refmiscinfo class="source">ctdb</refmiscinfo>
12 <refmiscinfo class="manual">CTDB - clustered TDB database</refmiscinfo>
13 </refmeta>
15 <refnamediv>
16 <refname>ctdbd.conf</refname>
17 <refpurpose>CTDB daemon configuration file</refpurpose>
18 </refnamediv>
20 <refsect1>
21 <title>DESCRIPTION</title>
23 <para>
24 This file contains CTDB configuration variables that are affect
25 the operation of CTDB. The default location of this file is
26 <filename>/etc/ctdb/ctdbd.conf</filename>.
27 </para>
29 <para>
30 This file is a shell script (see
31 <citerefentry><refentrytitle>sh</refentrytitle>
32 <manvolnum>1</manvolnum></citerefentry>) but is usually limited
33 to simple variable assignments and shell-style comments.
34 </para>
36 <para>
37 CTDB configuration variables are grouped into several categories below.
38 </para>
40 <para>
41 Variables defined in this document can also be set in a
42 distribution-specific configuration file such as
43 <filename>/etc/sysconfig/ctdb</filename> (Red Hat) or
44 <filename>/etc/default/ctdb</filename> (Debian). However, these
45 files should be reserved for variables used by the initscript.
46 A historical alternative is
47 <filename>/etc/ctdb/sysconfig/ctdb</filename> - this is
48 deprecated.
49 </para>
51 </refsect1>
53 <refsect1>
54 <title>
55 INITSCRIPT CONFIGURATION
56 </title>
58 <para>
59 Some options must be available to the initscript so they need to
60 be set in the distribution-specific initscript configuration,
61 such as <filename>/etc/sysconfig/ctdb</filename> or
62 <filename>/etc/default/ctdb</filename>.
63 </para>
65 <variablelist>
67 <varlistentry>
68 <term>CTDB_PIDFILE=<parameter>FILENAME</parameter></term>
69 <listitem>
70 <para>
71 FILENAME is the name of the file used to contain the
72 process ID (PID) of the main CTDB daemon when it is
73 running. This is passed from the initscript to
74 <citerefentry><refentrytitle>ctdbd_wrapper</refentrytitle>
75 <manvolnum>1</manvolnum></citerefentry>.
76 </para>
78 <para>
79 Default is <filename>/var/run/ctdb/ctdbd.pid</filename>.
80 Corresponds to <option>--pidfile</option>.
81 </para>
82 </listitem>
83 </varlistentry>
85 </variablelist>
86 </refsect1>
88 <refsect1>
89 <title>
90 GLOBAL CONFIGURATION
91 </title>
93 <para>
94 These options may be used in the initscripts, daemon and
95 scripts.
96 </para>
98 <variablelist>
100 <varlistentry>
101 <term>CTDB_BASE=<parameter>DIRECTORY</parameter></term>
102 <listitem>
103 <para>
104 DIRECTORY containing CTDB scripts and configuration files.
105 </para>
106 </listitem>
107 </varlistentry>
109 <varlistentry>
110 <term>CTDB_VARDIR=<parameter>DIRECTORY</parameter></term>
111 <listitem>
112 <para>
113 DIRECTORY containing CTDB files that are modified at
114 runtime.
115 </para>
116 <para>
117 Defaults to <filename>/var/ctdb</filename>, unless
118 <filename>/var/lib/ctdb</filename> already exists in which
119 case it is used.
120 </para>
121 </listitem>
122 </varlistentry>
125 </variablelist>
126 </refsect1>
128 <refsect1>
129 <title>
130 DAEMON CONFIGURATION
131 </title>
133 <para>
134 Variables in this section are processed by
135 <citerefentry><refentrytitle>ctdbd_wrapper</refentrytitle>
136 <manvolnum>1</manvolnum></citerefentry> and are converted into
137 command-line arguments to
138 <citerefentry><refentrytitle>ctdbd</refentrytitle>
139 <manvolnum>1</manvolnum></citerefentry>. Correspondence with
140 <citerefentry><refentrytitle>ctdbd</refentrytitle>
141 <manvolnum>1</manvolnum></citerefentry> options is shown for
142 each variable. The the documentation for the relevant options
143 for more details.
144 </para>
146 <para>
147 Many of these variables are also used by event scripts.
148 </para>
150 <variablelist>
152 <varlistentry>
153 <term>CTDB_CAPABILITY_LMASTER=yes|no</term>
154 <listitem>
155 <para>
156 Defaults to yes. Corresponds to <option>--no-lmaster</option>.
157 </para>
158 </listitem>
159 </varlistentry>
161 <varlistentry>
162 <term>CTDB_CAPABILITY_RECMASTER=yes|no</term>
163 <listitem>
164 <para>
165 Defaults to yes. Corresponds to
166 <option>--no-recmaster</option>.
167 </para>
168 </listitem>
169 </varlistentry>
171 <varlistentry>
172 <term>CTDB_DBDIR=<parameter>DIRECTORY</parameter></term>
173 <listitem>
174 <para>
175 Defaults to <varname>CTDB_VARDIR</varname>. Corresponds to
176 <option>--dbdir</option>.
177 </para>
178 </listitem>
179 </varlistentry>
181 <varlistentry>
182 <term>CTDB_DBDIR_PERSISTENT=<parameter>DIRECTORY</parameter></term>
183 <listitem>
184 <para>
185 Defaults to <varname>CTDB_VARDIR</varname>/persistent.
186 Corresponds to <option>--dbdir-persistent</option>.
187 </para>
188 </listitem>
189 </varlistentry>
191 <varlistentry>
192 <term>CTDB_DBDIR_STATE=<parameter>DIRECTORY</parameter></term>
193 <listitem>
194 <para>
195 Defaults to <varname>CTDB_VARDIR</varname>/state.
196 Corresponds to <option>--dbdir-state</option>.
197 </para>
198 </listitem>
199 </varlistentry>
201 <varlistentry>
202 <term>CTDB_DEBUGLEVEL=<parameter>DEBUGLEVEL</parameter></term>
203 <listitem>
204 <para>
205 Default is ERR (0). Corresponds to <option>-d</option> or
206 <option>--debug</option>.
207 </para>
208 </listitem>
209 </varlistentry>
211 <varlistentry>
212 <term>CTDB_EVENT_SCRIPT_DIR=<parameter>DIRECTORY</parameter></term>
213 <listitem>
214 <para>
215 Default is <varname>CTDB_BASE</varname>/events.d, so usually
216 <filename>/etc/ctdb/events.d</filename>. Corresponds to
217 <option>--event-script-dir</option>.
218 </para>
219 </listitem>
220 </varlistentry>
222 <varlistentry>
223 <term>CTDB_LOGFILE=<parameter>FILENAME</parameter></term>
224 <listitem>
225 <para>
226 Defaults to <filename>/var/log/log.ctdb</filename>.
227 Corresponds to <option>--logfile</option>. See also
228 <citetitle>CTDB_SYSLOG</citetitle>.
229 </para>
230 </listitem>
231 </varlistentry>
233 <varlistentry>
234 <term>CTDB_LOG_RINGBUF_SIZE=<parameter>NUM</parameter></term>
235 <listitem>
236 <para>
237 Default is 0. Corresponds to
238 <option>--log-ringbuf-size</option>.
239 </para>
240 </listitem>
241 </varlistentry>
243 <varlistentry>
244 <term>CTDB_LVS_PUBLIC_IP=<parameter>IPADDR</parameter></term>
245 <listitem>
246 <para>
247 No default. Corresponds to "<option>--lvs</option>
248 <option>--single-public-ip IPADDR"</option>.
249 </para>
250 </listitem>
251 </varlistentry>
253 <varlistentry>
254 <term>CTDB_NODES=<parameter>FILENAME</parameter></term>
255 <listitem>
256 <para>
257 Default is <varname>CTDB_BASE</varname>/nodes, so usually
258 <filename>/etc/ctdb/nodes</filename>. Corresponds to
259 <option>--nlist</option>.
260 </para>
261 </listitem>
262 </varlistentry>
264 <varlistentry>
265 <term>CTDB_NOTIFY_SCRIPT=<parameter>FILENAME</parameter></term>
266 <listitem>
267 <para>
268 No default, usually
269 <filename>/etc/ctdb/notify.sh</filename>. Corresponds to
270 <option>--notification-script</option>.
271 </para>
272 </listitem>
273 </varlistentry>
275 <varlistentry>
276 <term>CTDB_MAX_PERSISTENT_CHECK_ERRORS=<parameter>NUM</parameter></term>
277 <listitem>
278 <para>
279 Default 0. Corresponds to
280 <option>--max-persistent-check-errors</option>.
281 </para>
282 </listitem>
283 </varlistentry>
285 <varlistentry>
286 <term>CTDB_PUBLIC_ADDRESSES=<parameter>FILENAME</parameter></term>
287 <listitem>
288 <para>
289 No default, usually
290 <filename>/etc/ctdb/public_addresses</filename>.
291 Corresponds to <option>--public-addresses</option>.
292 </para>
293 </listitem>
294 </varlistentry>
296 <varlistentry>
297 <term>CTDB_PUBLIC_INTERFACE=<parameter>INTERFACE</parameter></term>
298 <listitem>
299 <para>
300 No default. Corresponds to
301 <option>--public-interface</option>.
302 </para>
303 </listitem>
304 </varlistentry>
306 <varlistentry>
307 <term>CTDB_RECOVERY_LOCK=<parameter>FILENAME</parameter></term>
308 <listitem>
309 <para>
310 Defaults to
311 <filename>/some/place/on/shared/storage</filename>, which
312 should be change to a useful value. Corresponds to
313 <option>--reclock</option>.
314 </para>
315 </listitem>
316 </varlistentry>
318 <varlistentry>
319 <term>CTDB_SCRIPT_LOG_LEVEL=<parameter>DEBUGLEVEL</parameter></term>
320 <listitem>
321 <para>
322 Defaults to ERR (0). Corresponds to
323 <option>--script-log-level</option>.
324 </para>
325 </listitem>
326 </varlistentry>
328 <varlistentry>
329 <term>CTDB_SOCKET=<parameter>FILENAME</parameter></term>
330 <listitem>
331 <para>
332 Defaults to <filename>/tmp/ctdb.socket</filename>.
333 Corresponds to <option>--socket</option>.
334 </para>
335 <para>
336 If you change this then you probably want to set this in
337 root's enviroment (perhaps in a file in
338 <filename>/etc/profile.d</filename>) so that you can use
339 the <citerefentry><refentrytitle>ctdb</refentrytitle>
340 <manvolnum>1</manvolnum></citerefentry> command in a
341 straightforward manner.
342 </para>
343 </listitem>
344 </varlistentry>
346 <varlistentry>
347 <term>CTDB_START_AS_DISABLED=yes|no</term>
348 <listitem>
349 <para>
350 Default is no. Corresponds to
351 <option>--start-as-disabled</option>.
352 </para>
353 </listitem>
354 </varlistentry>
356 <varlistentry>
357 <term>CTDB_START_AS_STOPPED=yes|no</term>
358 <listitem>
359 <para>
360 Default is no. Corresponds to
361 <option>--start-as-stopped</option>.
362 </para>
363 </listitem>
364 </varlistentry>
366 <varlistentry>
367 <term>CTDB_SYSLOG=yes|no</term>
368 <listitem>
369 <para>
370 Default is no. Corresponds to <option>--syslog</option>.
371 </para>
372 </listitem>
373 </varlistentry>
375 <varlistentry>
376 <term>CTDB_TRANSPORT=tcp|infiniband</term>
377 <listitem>
378 <para>
379 Defaults to tcp. Corresponds to
380 <option>--transport</option>.
381 </para>
382 </listitem>
383 </varlistentry>
385 </variablelist>
387 <para>
388 While the following variables do not translate into daemon
389 options they are used by
390 <citerefentry><refentrytitle>ctdbd_wrapper</refentrytitle>
391 <manvolnum>1</manvolnum></citerefentry> when starting and
392 stopping <citerefentry><refentrytitle>ctdbd</refentrytitle>
393 <manvolnum>1</manvolnum></citerefentry>.
394 </para>
396 <variablelist>
398 <varlistentry>
399 <term>CTDB_SHUTDOWN_TIMEOUT=<parameter>NUM</parameter></term>
400 <listitem>
401 <para>
402 NUM is the number of seconds to wait for
403 <citerefentry><refentrytitle>ctdbd</refentrytitle>
404 <manvolnum>1</manvolnum></citerefentry> to shut down
405 gracefully before giving up and killing it.
406 </para>
408 <para>
409 Defaults is 30.
410 </para>
411 </listitem>
412 </varlistentry>
414 <varlistentry>
415 <term>CTDB_STARTUP_TIMEOUT=<parameter>NUM</parameter></term>
416 <listitem>
417 <para>
418 NUM is the number of seconds to wait for
419 <citerefentry><refentrytitle>ctdbd</refentrytitle>
420 <manvolnum>1</manvolnum></citerefentry> complete early
421 initialisation up to a point where it is unlikely to
422 abort. If <command>ctdbd</command> doesn't complete the
423 "setup" event before this timeout then it is killed.
424 </para>
426 <para>
427 Defaults is 10.
428 </para>
429 </listitem>
430 </varlistentry>
432 </variablelist>
433 </refsect1>
435 <refsect1>
436 <title>NETWORK CONFIGURATION</title>
438 <refsect2>
439 <title>NAT GATEWAY</title>
441 <para>
442 NAT gateway is used to configure fallback routing for nodes
443 when they do not host any public IP addresses. For example,
444 it allows unhealthy nodes to reliably communicate with
445 external infrastructure. One node in a NAT gateway group will
446 be designated as the NAT gateway master node and other (slave)
447 nodes will be configured with fallback routes via the NAT
448 gateway master node. For more information, see the
449 <citetitle>NAT GATEWAY</citetitle> section in
450 <citerefentry><refentrytitle>ctdb</refentrytitle>
451 <manvolnum>7</manvolnum></citerefentry>.
452 </para>
454 <variablelist>
456 <varlistentry>
457 <term>CTDB_NATGW_DEFAULT_GATEWAY=<parameter>IPADDR</parameter></term>
458 <listitem>
459 <para>
460 IPADDR is an alternate network gateway to use on the NAT
461 gateway master node. If set, a fallback default route
462 is added via this network gateway.
463 </para>
464 <para>
465 No default. Setting this variable is optional - if not
466 set that no route is created on the NAT gateway master
467 node.
468 </para>
469 </listitem>
470 </varlistentry>
472 <varlistentry>
473 <term>CTDB_NATGW_NODES=<parameter>FILENAME</parameter></term>
474 <listitem>
475 <para>
476 FILENAME contains the list of nodes that belong to the
477 same NAT gateway group.
478 </para>
479 <para>
480 File format:
481 <screen>
482 <parameter>IPADDR</parameter>
483 </screen>
484 </para>
485 <para>
486 No default, usually
487 <filename>/etc/ctdb/natgw_nodes</filename> when enabled.
488 </para>
489 </listitem>
490 </varlistentry>
492 <varlistentry>
493 <term>CTDB_NATGW_PRIVATE_NETWORK=<parameter>IPADDR/MASK</parameter></term>
494 <listitem>
495 <para>
496 IPADDR/MASK is the private sub-network that is
497 internally routed via the NAT gateway master node. This
498 is usually the private network that is used for node
499 addresses.
500 </para>
501 <para>
502 No default.
503 </para>
504 </listitem>
505 </varlistentry>
507 <varlistentry>
508 <term>CTDB_NATGW_PUBLIC_IFACE=<parameter>IFACE</parameter></term>
509 <listitem>
510 <para>
511 IFACE is the network interface on which the
512 CTDB_NATGW_PUBLIC_IP will be configured.
513 </para>
514 <para>
515 No default.
516 </para>
517 </listitem>
518 </varlistentry>
520 <varlistentry>
521 <term>CTDB_NATGW_PUBLIC_IP=<parameter>IPADDR/MASK</parameter></term>
522 <listitem>
523 <para>
524 IPADDR/MASK indicates the IP address that is used for
525 outgoing traffic (originating from
526 CTDB_NATGW_PRIVATE_NETWORK) on the NAT gateway master
527 node. This <emphasis>must not</emphasis> be a
528 configured public IP address.
529 </para>
530 <para>
531 No default.
532 </para>
533 </listitem>
534 </varlistentry>
536 <varlistentry>
537 <term>CTDB_NATGW_SLAVE_ONLY=yes|no</term>
538 <listitem>
539 <para>
540 When set to "yes" a node can not be a NAT gateway master
541 node. In this case
542 <varname>CTDB_NATGW_PUBLIC_IFACE</varname> and
543 <varname>CTDB_NATGW_PUBLIC_IP</varname> are optional
544 and unused.
545 </para>
546 <para>
547 Default is no.
548 </para>
549 </listitem>
550 </varlistentry>
552 <varlistentry>
553 <term>CTDB_NATGW_STATIC_ROUTES=<parameter>IPADDR/MASK[@GATEWAY]</parameter> ...</term>
554 <listitem>
555 <para>
556 Each IPADDR/MASK identifies a network or host to which
557 NATGW should create a fallback route, instead of
558 creating a single default route. This can be used when
559 there is already a default route, via an interface that
560 can not reach required infrastructure, that overrides
561 the NAT gateway default route.
562 </para>
563 <para>
564 If GATEWAY is specified then the corresponding route on
565 the NATGW master node will be via GATEWAY. Such routes
566 are created even if
567 <varname>CTDB_NATGW_DEFAULT_GATEWAY</varname> is not
568 specified. If GATEWAY is not specified for some
569 networks then routes are only created on the NATGW
570 master node for those networks if
571 <varname>CTDB_NATGW_DEFAULT_GATEWAY</varname> is
572 specified.
573 </para>
574 <para>
575 This should be used with care to avoid causing traffic
576 to unnecessarily double-hop through the NAT gateway
577 master, even when a node is hosting public IP addresses.
578 Each specified network or host should probably have a
579 corresponding automatically created link route or static
580 route to avoid this.
581 </para>
582 <para>
583 No default.
584 </para>
585 </listitem>
586 </varlistentry>
588 </variablelist>
590 <refsect3>
591 <title>Example</title>
592 <screen>
593 CTDB_NATGW_NODES=/etc/ctdb/natgw_nodes
594 CTDB_NATGW_PRIVATE_NETWORK=192.168.1.0/24
595 CTDB_NATGW_DEFAULT_GATEWAY=10.0.0.1
596 CTDB_NATGW_PUBLIC_IP=10.0.0.227/24
597 CTDB_NATGW_PUBLIC_IFACE=eth0
598 </screen>
600 <para>
601 A variation that ensures that infrastructure (ADS, DNS, ...)
602 directly attached to the public network (10.0.0.0/24) is
603 always reachable would look like this:
604 </para>
605 <screen>
606 CTDB_NATGW_NODES=/etc/ctdb/natgw_nodes
607 CTDB_NATGW_PRIVATE_NETWORK=192.168.1.0/24
608 CTDB_NATGW_PUBLIC_IP=10.0.0.227/24
609 CTDB_NATGW_PUBLIC_IFACE=eth0
610 CTDB_NATGW_STATIC_ROUTES=10.0.0.0/24
611 </screen>
612 <para>
613 Note that <varname>CTDB_NATGW_DEFAULT_GATEWAY</varname> is
614 not specified.
615 </para>
616 </refsect3>
618 </refsect2>
620 <refsect2>
621 <title>POLICY ROUTING</title>
623 <para>
624 A node running CTDB may be a component of a complex network
625 topology. In particular, public addresses may be spread
626 across several different networks (or VLANs) and it may not be
627 possible to route packets from these public addresses via the
628 system's default route. Therefore, CTDB has support for
629 policy routing via the <filename>13.per_ip_routing</filename>
630 eventscript. This allows routing to be specified for packets
631 sourced from each public address. The routes are added and
632 removed as CTDB moves public addresses between nodes.
633 </para>
635 <para>
636 For more information, see the <citetitle>POLICY
637 ROUTING</citetitle> section in
638 <citerefentry><refentrytitle>ctdb</refentrytitle>
639 <manvolnum>7</manvolnum></citerefentry>.
640 </para>
642 <variablelist>
643 <varlistentry>
644 <term>CTDB_PER_IP_ROUTING_CONF=<parameter>FILENAME</parameter></term>
645 <listitem>
646 <para>
647 FILENAME contains elements for constructing the desired
648 routes for each source address.
649 </para>
651 <para>
652 The special FILENAME value
653 <constant>__auto_link_local__</constant> indicates that no
654 configuration file is provided and that CTDB should
655 generate reasonable link-local routes for each public IP
656 address.
657 </para>
659 <para>
660 File format:
661 <screen>
662 <parameter>IPADDR</parameter> <parameter>DEST-IPADDR/MASK</parameter> <optional><parameter>GATEWAY-IPADDR</parameter></optional>
663 </screen>
664 </para>
666 <para>
667 No default, usually
668 <filename>/etc/ctdb/policy_routing</filename> when enabled.
669 </para>
670 </listitem>
671 </varlistentry>
673 <varlistentry>
674 <term>CTDB_PER_IP_ROUTING_RULE_PREF=<parameter>NUM</parameter></term>
675 <listitem>
676 <para>
677 NUM sets the priority (or preference) for the routing
678 rules that are added by CTDB.
679 </para>
681 <para>
682 This should be (strictly) greater than 0 and (strictly)
683 less than 32766. A priority of 100 is recommended, unless
684 this conflicts with a priority already in use on the
685 system. See
686 <citerefentry><refentrytitle>ip</refentrytitle>
687 <manvolnum>8</manvolnum></citerefentry>, for more details.
688 </para>
689 </listitem>
690 </varlistentry>
692 <varlistentry>
693 <term>
694 CTDB_PER_IP_ROUTING_TABLE_ID_LOW=<parameter>LOW-NUM</parameter>,
695 CTDB_PER_IP_ROUTING_TABLE_ID_HIGH=<parameter>HIGH-NUM</parameter>
696 </term>
697 <listitem>
698 <para>
699 CTDB determines a unique routing table number to use for
700 the routing related to each public address. LOW-NUM and
701 HIGH-NUM indicate the minimum and maximum routing table
702 numbers that are used.
703 </para>
705 <para>
706 <citerefentry><refentrytitle>ip</refentrytitle>
707 <manvolnum>8</manvolnum></citerefentry> uses some
708 reserved routing table numbers below 255. Therefore,
709 CTDB_PER_IP_ROUTING_TABLE_ID_LOW should be (strictly)
710 greater than 255.
711 </para>
713 <para>
714 CTDB uses the standard file
715 <filename>/etc/iproute2/rt_tables</filename> to maintain
716 a mapping between the routing table numbers and labels.
717 The label for a public address
718 <replaceable>ADDR</replaceable> will look like
719 ctdb.<replaceable>addr</replaceable>. This means that
720 the associated rules and routes are easy to read (and
721 manipulate).
722 </para>
724 <para>
725 No default, usually 1000 and 9000.
726 </para>
727 </listitem>
728 </varlistentry>
729 </variablelist>
731 <refsect3>
732 <title>Example</title>
733 <screen>
734 CTDB_PER_IP_ROUTING_CONF=/etc/ctdb/policy_routing
735 CTDB_PER_IP_ROUTING_RULE_PREF=100
736 CTDB_PER_IP_ROUTING_TABLE_ID_LOW=1000
737 CTDB_PER_IP_ROUTING_TABLE_ID_HIGH=9000
738 </screen>
739 </refsect3>
741 </refsect2>
743 <refsect2>
744 <title>MISCELLANEOUS NETWORK CONFIGURATION</title>
746 <variablelist>
748 <varlistentry>
749 <term>CTDB_PARTIALLY_ONLINE_INTERFACES=yes|no</term>
750 <listitem>
751 <para>
752 Whether one or more offline interfaces should cause a
753 monitor event to fail if there are other interfaces that
754 are up. If this is "yes" and a node has some interfaces
755 that are down then <command>ctdb status</command> will
756 display the node as "PARTIALLYONLINE".
757 </para>
759 <para>
760 Default is "no".
761 </para>
762 </listitem>
763 </varlistentry>
765 </variablelist>
766 </refsect2>
768 </refsect1>
770 <refsect1>
771 <title>SERVICE CONFIGURATION</title>
773 <para>
774 CTDB can be configured to manage and/or monitor various NAS (and
775 other) services via its eventscripts.
776 </para>
778 <para>
779 In the simplest case CTDB will manage a service. This means the
780 service will be started and stopped along with CTDB, CTDB will
781 monitor the service and CTDB will do any required
782 reconfiguration of the service when public IP addresses are
783 failed over.
784 </para>
786 <refsect2>
787 <title>SAMBA</title>
789 <refsect3>
790 <title>Eventscripts</title>
792 <simplelist>
793 <member><filename>49.winbind</filename></member>
794 <member><filename>50.samba</filename></member>
795 </simplelist>
796 </refsect3>
798 <variablelist>
800 <varlistentry>
801 <term>CTDB_MANAGES_SAMBA=yes|no</term>
802 <listitem>
803 <para>
804 Should CTDB manage Samba?
805 </para>
806 <para>
807 Default is no.
808 </para>
809 </listitem>
810 </varlistentry>
812 <varlistentry>
813 <term>CTDB_MANAGES_WINBIND=yes|no</term>
814 <listitem>
815 <para>
816 Should CTDB manage Winbind?
817 </para>
818 <para>
819 Default is no.
820 </para>
821 </listitem>
822 </varlistentry>
824 <varlistentry>
825 <term>CTDB_SAMBA_CHECK_PORTS=<parameter>PORT-LIST</parameter></term>
826 <listitem>
827 <para>
828 When monitoring Samba, check TCP ports in
829 space-separated PORT-LIST.
830 </para>
831 <para>
832 Default is to monitor ports that Samba is configured to listen on.
833 </para>
834 </listitem>
835 </varlistentry>
837 <varlistentry>
838 <term>CTDB_SAMBA_SKIP_SHARE_CHECK=yes|no</term>
839 <listitem>
840 <para>
841 As part of monitoring, should CTDB skip the check for
842 the existence of each directory configured as share in
843 Samba. This may be desirable if there is a large number
844 of shares.
845 </para>
846 <para>
847 Default is no.
848 </para>
849 </listitem>
850 </varlistentry>
852 <varlistentry>
853 <term>CTDB_SERVICE_NMB=<parameter>SERVICE</parameter></term>
854 <listitem>
855 <para>
856 Distribution specific SERVICE for managing nmbd.
857 </para>
858 <para>
859 Default is distribution-dependant.
860 </para>
861 </listitem>
862 </varlistentry>
863 <varlistentry>
864 <term>CTDB_SERVICE_SMB=<parameter>SERVICE</parameter></term>
865 <listitem>
866 <para>
867 Distribution specific SERVICE for managing smbd.
868 </para>
869 <para>
870 Default is distribution-dependant.
871 </para>
872 </listitem>
873 </varlistentry>
875 <varlistentry>
876 <term>CTDB_SERVICE_WINBIND=<parameter>SERVICE</parameter></term>
877 <listitem>
878 <para>
879 Distribution specific SERVICE for managing winbindd.
880 </para>
881 <para>
882 Default is "winbind".
883 </para>
884 </listitem>
885 </varlistentry>
887 </variablelist>
889 </refsect2>
891 <refsect2>
892 <title>NFS</title>
894 <para>
895 This includes parameters for the kernel NFS server and the
896 user-space
897 <ulink url="https://github.com/nfs-ganesha/nfs-ganesha/wiki">NFS-Ganesha</ulink>
898 server.
899 </para>
901 <refsect3>
902 <title>Eventscripts</title>
904 <simplelist>
905 <member><filename>60.nfs</filename></member>
906 <member><filename>60.ganesha</filename></member>
907 </simplelist>
908 </refsect3>
910 <variablelist>
912 <varlistentry>
913 <term>CTDB_CLUSTER_FILESYSTEM_TYPE=gpfs</term>
914 <listitem>
915 <para>
916 The type of cluster filesystem to use with NFS-ganesha.
917 Currently only "gpfs" is supported.
918 </para>
919 <para>
920 Default is "gpfs".
921 </para>
922 </listitem>
923 </varlistentry>
925 <varlistentry>
926 <term>CTDB_GANESHA_REC_SUBDIR<parameter>SUBDIR</parameter></term>
927 <listitem>
928 <para>
929 SUBDIR is the name of a top-level subdirectory in the
930 first cluster filesystem. This subdirectory is used to
931 allow communication between NFS-Ganesha and the
932 <filename>60.ganesha</filename> script.
933 </para>
934 <para>
935 Default is ".ganesha".
936 </para>
937 </listitem>
938 </varlistentry>
940 <varlistentry>
941 <term>CTDB_MANAGES_NFS=yes|no</term>
942 <listitem>
943 <para>
944 Should CTDB manage NFS?
945 </para>
946 <para>
947 Default is no.
948 </para>
949 </listitem>
950 </varlistentry>
952 <varlistentry>
953 <term>CTDB_MONITOR_NFS_THREAD_COUNT=yes|no</term>
954 <listitem>
955 <para>
956 Whether to monitor the NFS kernel server thread count.
957 </para>
958 <para>
959 This works around a limitation in some NFS initscripts
960 where some threads can be stuck in host filesystem calls
961 (perhaps due to slow storage), a restart occurs, some
962 threads don't exit, the start only adds the missing
963 number of threads, the stuck threads exit, and the
964 result is a lower than expected thread count. Note that
965 if you must also set <varname>RPCNFSDCOUNT</varname>
966 (RedHat/Debian) or <varname>USE_KERNEL_NFSD_NUMBER</varname>
967 (SUSE) in your NFS configuration so the monitoring code
968 knows how many threads there should be - if neither of
969 these are set then this option will be ignored.
970 </para>
971 <para>
972 Default is no.
973 </para>
974 </listitem>
975 </varlistentry>
977 <varlistentry>
978 <term>CTDB_NFS_DUMP_STUCK_THREADS=<parameter>NUM</parameter></term>
979 <listitem>
980 <para>
981 NUM is the number of NFS kernel server threads to dump
982 stack traces for if some are still alive after stopping
983 NFS during a restart.
984 </para>
985 <para>
986 Default is 5. Set this to 0 to disable this feature.
987 </para>
988 </listitem>
989 </varlistentry>
991 <varlistentry>
992 <term>CTDB_NFS_SERVER_MODE=kernel|ganesha</term>
993 <listitem>
994 <para>
995 Selects which NFS server to be managed.
996 </para>
997 <para>
998 This replaces the deprecated variable
999 <varname>NFS_SERVER_MODE</varname>.
1000 </para>
1001 <para>
1002 Default is "kernel".
1003 </para>
1004 </listitem>
1005 </varlistentry>
1007 <varlistentry>
1008 <term>CTDB_NFS_SKIP_KNFSD_ALIVE_CHECK=yes|no</term>
1009 <listitem>
1010 <para>
1011 During monitoring, should CTDB skip the
1012 <command>rpcinfo</command> check that is used to see if
1013 the NFS kernel server is functional.
1014 </para>
1015 <para>
1016 Default is no.
1017 </para>
1018 </listitem>
1019 </varlistentry>
1021 <varlistentry>
1022 <term>CTDB_NFS_SKIP_SHARE_CHECK=yes|no</term>
1023 <listitem>
1024 <para>
1025 As part of monitoring, should CTDB skip the check for
1026 the existence of each directory exported via NFS. This
1027 may be desirable if there is a large number of exports.
1028 </para>
1029 <para>
1030 Default is no.
1031 </para>
1032 </listitem>
1033 </varlistentry>
1035 <varlistentry>
1036 <term>CTDB_RPCINFO_LOCALHOST=<parameter>IPADDR</parameter>|<parameter>HOSTNAME</parameter></term>
1037 <listitem>
1038 <para>
1039 IPADDR or HOSTNAME indicates the address that
1040 <command>rpcinfo</command> should connect to when doing
1041 <command>rpcinfo</command> check on RPC service during
1042 monitoring. Optimally this would be "localhost".
1043 However, this can add some performance overheads.
1044 </para>
1045 <para>
1046 Default is "127.0.0.1".
1047 </para>
1048 </listitem>
1049 </varlistentry>
1051 <varlistentry>
1052 <term>CTDB_SKIP_GANESHA_NFSD_CHECK=yes|no</term>
1053 <listitem>
1054 <para>
1055 As part of monitoring, should CTDB skip the check for
1056 the existence of each directory exported via
1057 NFS-Ganesha. This may be desirable if there is a large
1058 number of exports.
1059 </para>
1060 <para>
1061 Default is no.
1062 </para>
1063 </listitem>
1064 </varlistentry>
1066 </variablelist>
1068 </refsect2>
1070 <refsect2>
1071 <title>APACHE HTTPD</title>
1073 <para>
1074 CTDB can manage the Apache web server.
1075 </para>
1077 <refsect3>
1078 <title>Eventscript</title>
1080 <simplelist>
1081 <member><filename>41.httpd</filename></member>
1082 </simplelist>
1083 </refsect3>
1085 <variablelist>
1086 <varlistentry>
1087 <term>CTDB_MANAGES_HTTPD=yes|no</term>
1088 <listitem>
1089 <para>
1090 Should CTDB manage the Apache web server?
1091 </para>
1092 <para>
1093 Default is no.
1094 </para>
1095 </listitem>
1096 </varlistentry>
1097 </variablelist>
1098 </refsect2>
1100 <refsect2>
1101 <title>CLAMAV</title>
1103 <para>
1104 CTDB has support to manage the popular anti-virus daemon
1105 ClamAV.
1106 </para>
1108 <refsect3>
1109 <title>Eventscript</title>
1111 <simplelist>
1112 <member><filename>31.clamd</filename></member>
1113 </simplelist>
1115 <para>
1116 This eventscript is not enabled by default. Use
1117 <command>ctdb enablescript</command> to enable it.
1118 </para>
1120 </refsect3>
1122 <variablelist>
1124 <varlistentry>
1125 <term>CTDB_MANAGES_CLAMD=yes|no</term>
1126 <listitem>
1127 <para>
1128 Should CTDB manage ClamAV?
1129 </para>
1130 <para>
1131 Default is no.
1132 </para>
1133 </listitem>
1134 </varlistentry>
1136 <varlistentry>
1137 <term>CTDB_CLAMD_SOCKET=<parameter>FILENAME</parameter></term>
1138 <listitem>
1139 <para>
1140 FILENAME is the socket to monitor ClamAV.
1141 </para>
1142 <para>
1143 No default.
1144 </para>
1145 </listitem>
1146 </varlistentry>
1148 </variablelist>
1150 </refsect2>
1152 <refsect2>
1153 <title>ISCSI</title>
1155 <para>
1156 CTDB has support for managing the Linux iSCSI tgtd service.
1157 </para>
1159 <refsect3>
1160 <title>Eventscript</title>
1162 <simplelist>
1163 <member><filename>70.iscsi</filename></member>
1164 </simplelist>
1165 </refsect3>
1167 <variablelist>
1169 <varlistentry>
1170 <term>CTDB_MANAGES_ISCSI=yes|no</term>
1171 <listitem>
1172 <para>
1173 Should CTDB manage iSCSI tgtd?
1174 </para>
1175 <para>
1176 Default is no.
1177 </para>
1178 </listitem>
1179 </varlistentry>
1181 <varlistentry>
1182 <term>CTDB_START_ISCSI_SCRIPTS=<parameter>DIRECTORY</parameter></term>
1183 <listitem>
1184 <para>
1185 DIRECTORY on shared storage containing scripts to start
1186 tgtd for each public IP address.
1187 </para>
1188 <para>
1189 No default.
1190 </para>
1191 </listitem>
1192 </varlistentry>
1193 </variablelist>
1194 </refsect2>
1196 <refsect2>
1197 <title>MULTIPATHD</title>
1199 <para>
1200 CTDB can monitor multipath devices to ensure that active paths
1201 are available.
1202 </para>
1204 <refsect3>
1205 <title>Eventscript</title>
1207 <simplelist>
1208 <member><filename>20.multipathd</filename></member>
1209 </simplelist>
1211 <para>
1212 This eventscript is not enabled by default. Use
1213 <command>ctdb enablescript</command> to enable it.
1214 </para>
1215 </refsect3>
1217 <variablelist>
1218 <varlistentry>
1219 <term>CTDB_MONITOR_MPDEVICES=<parameter>MP-DEVICE-LIST</parameter></term>
1220 <listitem>
1221 <para>
1222 MP-DEVICE-LIST is a list of multipath devices for CTDB to monitor?
1223 </para>
1224 <para>
1225 No default.
1226 </para>
1227 </listitem>
1228 </varlistentry>
1229 </variablelist>
1230 </refsect2>
1232 <refsect2>
1233 <title>VSFTPD</title>
1235 <para>
1236 CTDB can manage the vsftpd FTP server.
1237 </para>
1239 <refsect3>
1240 <title>Eventscript</title>
1242 <simplelist>
1243 <member><filename>40.vsftpd</filename></member>
1244 </simplelist>
1245 </refsect3>
1247 <variablelist>
1248 <varlistentry>
1249 <term>CTDB_MANAGES_VSFTPD=yes|no</term>
1250 <listitem>
1251 <para>
1252 Should CTDB manage the vsftpd FTP server?
1253 </para>
1254 <para>
1255 Default is no.
1256 </para>
1257 </listitem>
1258 </varlistentry>
1259 </variablelist>
1260 </refsect2>
1262 <refsect2>
1263 <title>
1264 SYSTEM RESOURCE MONITORING CONFIGURATION
1265 </title>
1267 <para>
1268 CTDB can experience seemingly random (performance and other)
1269 issues if system resources become too contrained. Options in
1270 this section can be enabled to allow certain system resources to
1271 be checked.
1272 </para>
1274 <refsect3>
1275 <title>Eventscripts</title>
1277 <simplelist>
1278 <member><filename>00.ctdb</filename></member>
1279 <member><filename>40.fs_use</filename></member>
1280 </simplelist>
1282 <para>
1283 Filesystem usage monitoring is in
1284 <filename>40.fs_use</filename>. This eventscript is not
1285 enabled by default. Use <command>ctdb
1286 enablescript</command> to enable it.
1287 </para>
1288 </refsect3>
1290 <variablelist>
1292 <varlistentry>
1293 <term>CTDB_CHECK_FS_USE=<parameter>FS-LIMIT-LIST</parameter></term>
1294 <listitem>
1295 <para>
1296 FS-LIMIT-LIST is a space-separated list of
1297 <parameter>FILESYSTEM</parameter>:<parameter>LIMIT</parameter>
1298 pairs indicating that a node should be flagged unhealthy
1299 if the space used on FILESYSTEM reaches LIMIT%.
1300 </para>
1302 <para>
1303 No default.
1304 </para>
1306 <para>
1307 Note that this feature uses the
1308 <filename>40.fs_use</filename> eventscript, which is not
1309 enabled by default. Use <command>ctdb
1310 enablescript</command> to enable it.
1311 </para>
1312 </listitem>
1313 </varlistentry>
1315 <varlistentry>
1316 <term>CTDB_CHECK_SWAP_IS_NOT_USED=yes|no</term>
1317 <listitem>
1318 <para>
1319 Should a warning be logged if swap space is in use.
1320 </para>
1321 <para>
1322 Default is no.
1323 </para>
1324 </listitem>
1325 </varlistentry>
1327 <varlistentry>
1328 <term>CTDB_MONITOR_FREE_MEMORY=<parameter>NUM</parameter></term>
1329 <listitem>
1330 <para>
1331 NUM is a lower limit on available system memory, expressed
1332 in megabytes. If this is set and the amount of available
1333 memory falls below this limit then some debug information
1334 will be logged, the node will be disabled and then CTDB
1335 will be shut down.
1336 </para>
1337 <para>
1338 No default.
1339 </para>
1340 </listitem>
1341 </varlistentry>
1343 <varlistentry>
1344 <term>CTDB_MONITOR_FREE_MEMORY_WARN=<parameter>NUM</parameter></term>
1345 <listitem>
1346 <para>
1347 NUM is a lower limit on available system memory, expressed
1348 in megabytes. If this is set and the amount of available
1349 memory falls below this limit then a warning will be
1350 logged.
1351 </para>
1352 <para>
1353 No default.
1354 </para>
1355 </listitem>
1356 </varlistentry>
1358 </variablelist>
1359 </refsect2>
1361 <refsect2>
1362 <title>MISCELLANEOUS SERVICE-RELATED CONFIGURATION</title>
1364 <variablelist>
1366 <varlistentry>
1367 <term>CTDB_MANAGED_SERVICES=<parameter>SERVICE-LIST</parameter></term>
1368 <listitem>
1369 <para>
1370 SERVICE-LIST is a space-separated list of SERVICEs that
1371 CTDB should manage. This can be used as an alternative
1372 to the
1373 <varname>CTDB_MANAGES_<replaceable>SERVICE</replaceable></varname>
1374 variables.
1375 </para>
1376 <para>
1377 No default.
1378 </para>
1379 </listitem>
1380 </varlistentry>
1382 <varlistentry>
1383 <term>CTDB_SERVICE_AUTOSTARTSTOP=yes|no</term>
1384 <listitem>
1385 <para>
1386 When CTDB should start and stop services if they become
1387 managed or unmanaged.
1388 </para>
1389 <para>
1390 Default is no.
1391 </para>
1392 </listitem>
1393 </varlistentry>
1395 </variablelist>
1397 </refsect2>
1399 </refsect1>
1401 <refsect1>
1402 <title>
1403 TUNABLES CONFIGURATION
1404 </title>
1406 <para>
1407 CTDB tunables (see
1408 <citerefentry><refentrytitle>ctdbd-tunables</refentrytitle>
1409 <manvolnum>7</manvolnum></citerefentry>) can be set from the
1410 configuration file. They are set as follows:
1412 <literallayout>
1413 CTDB_SET_<replaceable>TUNABLE</replaceable>=<replaceable>VALUE</replaceable>
1414 </literallayout>
1415 </para>
1417 <para>
1418 For example:
1420 <screen format="linespecific">
1421 CTDB_SET_MonitorInterval=20
1422 </screen>
1423 </para>
1424 </refsect1>
1426 <refsect1>
1427 <title>
1428 DEBUG AND TEST
1429 </title>
1431 <para>
1432 Variable in this section are for debugging and testing CTDB.
1433 They should not generally be needed.
1434 </para>
1436 <variablelist>
1438 <varlistentry>
1439 <term>CTDB_DEBUG_HUNG_SCRIPT=<parameter>FILENAME</parameter></term>
1440 <listitem>
1441 <para>
1442 FILENAME is a script to run to log debug information when
1443 an event script times out.
1444 </para>
1445 <para>
1446 Default is <filename><varname>CTDB_BASE</varname>/debug-hung-script.sh</filename>.
1447 </para>
1448 </listitem>
1449 </varlistentry>
1451 <varlistentry>
1452 <term>CTDB_DEBUG_HUNG_SCRIPT_LOGFILE=<parameter>FILENAME</parameter></term>
1453 <listitem>
1454 <para>
1455 FILENAME specifies where log messages should go when
1456 debugging hung eventscripts. This is a testing option.
1457 See also <citetitle>CTDB_DEBUG_HUNG_SCRIPT</citetitle>.
1458 </para>
1459 <para>
1460 No default. Messages go to stdout/stderr and are logged
1461 to the same place as other CTDB log messages.
1462 </para>
1463 </listitem>
1464 </varlistentry>
1466 <varlistentry>
1467 <term>CTDB_DEBUG_HUNG_SCRIPT_STACKPAT=<parameter>REGEXP</parameter></term>
1468 <listitem>
1469 <para>
1470 REGEXP specifies interesting processes for which stack
1471 traces should be logged when debugging hung eventscripts
1472 and those processes are matched in pstree output. See
1473 also <citetitle>CTDB_DEBUG_HUNG_SCRIPT</citetitle>.
1474 </para>
1475 <para>
1476 Default is "exportfs\|rpcinfo".
1477 </para>
1478 </listitem>
1479 </varlistentry>
1481 <varlistentry>
1482 <term>CTDB_DEBUG_LOCKS=<parameter>FILENAME</parameter></term>
1483 <listitem>
1484 <para>
1485 FILENAME is a script to run to log debug information when
1486 an CTDB fails to freeze databases during recovery.
1487 </para>
1488 <para>
1489 No default, usually
1490 <filename><varname>CTDB_BASE</varname>/debug_locks.sh</filename>.
1491 </para>
1492 </listitem>
1493 </varlistentry>
1495 <varlistentry>
1496 <term>CTDB_ETCDIR=<parameter>DIRECTORY</parameter></term>
1497 <listitem>
1498 <para>
1499 DIRECTORY containing system configuration files. This is
1500 used to provide alternate configuration when testing and
1501 should not need to be changed from the default.
1502 </para>
1503 <para>
1504 Default is <filename>/etc</filename>.
1505 </para>
1506 </listitem>
1507 </varlistentry>
1509 <varlistentry>
1510 <term>CTDB_INIT_STYLE=debian|redhat|suse</term>
1511 <listitem>
1512 <para>
1513 This is the init style used by the Linux distribution (or
1514 other operating system) being used. This is usually
1515 determined dynamically by checking the system. This
1516 variable is used by the initscript to determine which init
1517 system primitives to use. It is also used by some
1518 eventscripts to choose the name of initscripts for certain
1519 services, since these can vary between distributions.
1520 </para>
1521 <para>
1522 No fixed default.
1523 </para>
1524 <para>
1525 If this option needs to be changed from the calculated
1526 default for the initscript to function properly, then it
1527 must be set in the distribution-specific initscript
1528 configuration, such as
1529 <filename>/etc/sysconfig/ctdb</filename>
1530 </para>
1531 </listitem>
1532 </varlistentry>
1534 <varlistentry>
1535 <term>CTDB_MAX_CORRUPT_DB_BACKUPS=<parameter>NUM</parameter></term>
1536 <listitem>
1537 <para>
1538 NUM is the maximum number of volatile TDB database backups
1539 to be kept (for each database) when a corrupt database is
1540 found during startup. Volatile TDBs are zeroed during
1541 startup so backups are needed to debug any corruption that
1542 occurs before a restart.
1543 </para>
1544 <para>
1545 Default is 10.
1546 </para>
1547 </listitem>
1548 </varlistentry>
1550 <varlistentry>
1551 <term>CTDB_RC_LOCAL=<parameter>FILENAME</parameter></term>
1552 <listitem>
1553 <para>
1554 FILENAME is a script fragment to be sourced by the
1555 <filename>functions</filename> that is sourced by scripts.
1556 On example use would be to override function definitions
1557 in unit tests. As a sanity check, this file must be
1558 executable for it to be used.
1559 </para>
1560 <para>
1561 No default.
1562 </para>
1563 </listitem>
1564 </varlistentry>
1566 <varlistentry>
1567 <term>CTDB_RUN_TIMEOUT_MONITOR=yes|no</term>
1568 <listitem>
1569 <para>
1570 Whether CTDB should simulate timing out monitor events.
1571 This uses the <filename>99.timeout</filename> eventscript.
1572 </para>
1573 <para>
1574 Default is no.
1575 </para>
1576 </listitem>
1577 </varlistentry>
1579 <varlistentry>
1580 <term>CTDB_SCRIPT_DEBUGLEVEL=<parameter>NUM</parameter></term>
1581 <listitem>
1582 <para>
1583 NUM is the level debugging messages printed by CTDB
1584 scripts. Setting this to a higher number (e.g. 4) will
1585 cause some scripts to log more messages.
1586 </para>
1587 <para>
1588 Default is 2.
1589 </para>
1590 </listitem>
1591 </varlistentry>
1593 <varlistentry>
1594 <term>CTDB_SUPPRESS_COREFILE=yes|no</term>
1595 <listitem>
1596 <para>
1597 Whether CTDB core files should be suppressed.
1598 </para>
1599 <para>
1600 Default is no.
1601 </para>
1602 </listitem>
1603 </varlistentry>
1605 <varlistentry>
1606 <term>CTDB_VALGRIND=yes|no|<parameter>COMMAND</parameter></term>
1607 <listitem>
1608 <para>
1609 If "yes", this causes
1610 <citerefentry><refentrytitle>ctdbd</refentrytitle>
1611 <manvolnum>1</manvolnum></citerefentry> to be run under
1612 <citerefentry><refentrytitle>valgrind</refentrytitle>
1613 <manvolnum>1</manvolnum></citerefentry> with logs going to
1614 <filename>/var/log/ctdb_valgrind</filename>. If neither
1615 "yes" nor "no" then the value is assumed to be a COMMAND
1616 (e.g. a <command>valgrind</command> variation, a
1617 <citerefentry><refentrytitle>gdb</refentrytitle>
1618 <manvolnum>1</manvolnum></citerefentry> command) that is
1619 used in place of the default <command>valgrind</command>
1620 command. In either case, the <option>--valgrind</option>
1621 option is passed to <command>ctdbd</command>.
1622 </para>
1623 <para>
1624 Default is no.
1625 </para>
1626 </listitem>
1627 </varlistentry>
1629 </variablelist>
1631 </refsect1>
1634 <refsect1>
1635 <title>FILES</title>
1637 <simplelist>
1638 <member><filename>/etc/ctdb/ctdbd.conf</filename></member>
1639 <member><filename>/etc/sysconfig/ctdb</filename></member>
1640 <member><filename>/etc/default/ctdb</filename></member>
1641 <member><filename>/etc/ctdb/sysconfig/ctdb</filename></member>
1642 </simplelist>
1643 </refsect1>
1645 <refsect1>
1646 <title>SEE ALSO</title>
1647 <para>
1648 <citerefentry><refentrytitle>ctdbd</refentrytitle>
1649 <manvolnum>1</manvolnum></citerefentry>,
1651 <citerefentry><refentrytitle>ctdbd_wrapper</refentrytitle>
1652 <manvolnum>1</manvolnum></citerefentry>,
1654 <citerefentry><refentrytitle>onnode</refentrytitle>
1655 <manvolnum>1</manvolnum></citerefentry>,
1657 <citerefentry><refentrytitle>ctdb</refentrytitle>
1658 <manvolnum>7</manvolnum></citerefentry>,
1660 <citerefentry><refentrytitle>ctdb-tunables</refentrytitle>
1661 <manvolnum>7</manvolnum></citerefentry>,
1663 <ulink url="http://ctdb.samba.org/"/>
1664 </para>
1665 </refsect1>
1667 <refentryinfo>
1668 <author>
1669 <contrib>
1670 This documentation was written by
1671 Amitay Isaacs,
1672 Martin Schwenke
1673 </contrib>
1674 </author>
1676 <copyright>
1677 <year>2007</year>
1678 <holder>Andrew Tridgell</holder>
1679 <holder>Ronnie Sahlberg</holder>
1680 </copyright>
1681 <legalnotice>
1682 <para>
1683 This program is free software; you can redistribute it and/or
1684 modify it under the terms of the GNU General Public License as
1685 published by the Free Software Foundation; either version 3 of
1686 the License, or (at your option) any later version.
1687 </para>
1688 <para>
1689 This program is distributed in the hope that it will be
1690 useful, but WITHOUT ANY WARRANTY; without even the implied
1691 warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
1692 PURPOSE. See the GNU General Public License for more details.
1693 </para>
1694 <para>
1695 You should have received a copy of the GNU General Public
1696 License along with this program; if not, see
1697 <ulink url="http://www.gnu.org/licenses"/>.
1698 </para>
1699 </legalnotice>
1700 </refentryinfo>
1702 </refentry>