| blob | e316abb4124b5decaaf46cd6c727deb62b618340 |
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_LVS_PUBLIC_IP=<parameter>IPADDR</parameter></term>
235 <listitem>
236 <para>
237 No default. Corresponds to "<option>--lvs</option>
238 <option>--single-public-ip IPADDR"</option>.
239 </para>
240 </listitem>
241 </varlistentry>
243 <varlistentry>
244 <term>CTDB_NODES=<parameter>FILENAME</parameter></term>
245 <listitem>
246 <para>
247 Default is <varname>CTDB_BASE</varname>/nodes, so usually
248 <filename>/etc/ctdb/nodes</filename>. Corresponds to
249 <option>--nlist</option>.
250 </para>
251 </listitem>
252 </varlistentry>
254 <varlistentry>
255 <term>CTDB_NOTIFY_SCRIPT=<parameter>FILENAME</parameter></term>
256 <listitem>
257 <para>
258 No default, usually
259 <filename>/etc/ctdb/notify.sh</filename>. Corresponds to
260 <option>--notification-script</option>.
261 </para>
262 </listitem>
263 </varlistentry>
265 <varlistentry>
266 <term>CTDB_MAX_PERSISTENT_CHECK_ERRORS=<parameter>NUM</parameter></term>
267 <listitem>
268 <para>
269 Default 0. Corresponds to
270 <option>--max-persistent-check-errors</option>.
271 </para>
272 </listitem>
273 </varlistentry>
275 <varlistentry>
276 <term>CTDB_PUBLIC_ADDRESSES=<parameter>FILENAME</parameter></term>
277 <listitem>
278 <para>
279 No default, usually
280 <filename>/etc/ctdb/public_addresses</filename>.
281 Corresponds to <option>--public-addresses</option>.
282 </para>
283 </listitem>
284 </varlistentry>
286 <varlistentry>
287 <term>CTDB_PUBLIC_INTERFACE=<parameter>INTERFACE</parameter></term>
288 <listitem>
289 <para>
290 No default. Corresponds to
291 <option>--public-interface</option>.
292 </para>
293 </listitem>
294 </varlistentry>
296 <varlistentry>
297 <term>CTDB_RECOVERY_LOCK=<parameter>FILENAME</parameter></term>
298 <listitem>
299 <para>
300 Defaults to
301 <filename>/some/place/on/shared/storage</filename>, which
302 should be change to a useful value. Corresponds to
303 <option>--reclock</option>.
304 </para>
305 </listitem>
306 </varlistentry>
308 <varlistentry>
309 <term>CTDB_SCRIPT_LOG_LEVEL=<parameter>DEBUGLEVEL</parameter></term>
310 <listitem>
311 <para>
312 Defaults to ERR (0). Corresponds to
313 <option>--script-log-level</option>.
314 </para>
315 </listitem>
316 </varlistentry>
318 <varlistentry>
319 <term>CTDB_SOCKET=<parameter>FILENAME</parameter></term>
320 <listitem>
321 <para>
322 Defaults to <filename>/tmp/ctdb.socket</filename>.
323 Corresponds to <option>--socket</option>.
324 </para>
325 <para>
326 If you change this then you probably want to set this in
327 root's enviroment (perhaps in a file in
328 <filename>/etc/profile.d</filename>) so that you can use
329 the <citerefentry><refentrytitle>ctdb</refentrytitle>
330 <manvolnum>1</manvolnum></citerefentry> command in a
331 straightforward manner.
332 </para>
333 </listitem>
334 </varlistentry>
336 <varlistentry>
337 <term>CTDB_START_AS_DISABLED=yes|no</term>
338 <listitem>
339 <para>
340 Default is no. Corresponds to
341 <option>--start-as-disabled</option>.
342 </para>
343 </listitem>
344 </varlistentry>
346 <varlistentry>
347 <term>CTDB_START_AS_STOPPED=yes|no</term>
348 <listitem>
349 <para>
350 Default is no. Corresponds to
351 <option>--start-as-stopped</option>.
352 </para>
353 </listitem>
354 </varlistentry>
356 <varlistentry>
357 <term>CTDB_SYSLOG=yes|no</term>
358 <listitem>
359 <para>
360 Default is no. Corresponds to <option>--syslog</option>.
361 </para>
362 </listitem>
363 </varlistentry>
365 <varlistentry>
366 <term>CTDB_TRANSPORT=tcp|infiniband</term>
367 <listitem>
368 <para>
369 Defaults to tcp. Corresponds to
370 <option>--transport</option>.
371 </para>
372 </listitem>
373 </varlistentry>
375 </variablelist>
377 <para>
378 While the following variables do not translate into daemon
379 options they are used by
380 <citerefentry><refentrytitle>ctdbd_wrapper</refentrytitle>
381 <manvolnum>1</manvolnum></citerefentry> when starting and
382 stopping <citerefentry><refentrytitle>ctdbd</refentrytitle>
383 <manvolnum>1</manvolnum></citerefentry>.
384 </para>
386 <variablelist>
388 <varlistentry>
389 <term>CTDB_SHUTDOWN_TIMEOUT=<parameter>NUM</parameter></term>
390 <listitem>
391 <para>
392 NUM is the number of seconds to wait for
393 <citerefentry><refentrytitle>ctdbd</refentrytitle>
394 <manvolnum>1</manvolnum></citerefentry> to shut down
395 gracefully before giving up and killing it.
396 </para>
398 <para>
399 Defaults is 30.
400 </para>
401 </listitem>
402 </varlistentry>
404 <varlistentry>
405 <term>CTDB_STARTUP_TIMEOUT=<parameter>NUM</parameter></term>
406 <listitem>
407 <para>
408 NUM is the number of seconds to wait for
409 <citerefentry><refentrytitle>ctdbd</refentrytitle>
410 <manvolnum>1</manvolnum></citerefentry> complete early
411 initialisation up to a point where it is unlikely to
412 abort. If <command>ctdbd</command> doesn't complete the
413 "setup" event before this timeout then it is killed.
414 </para>
416 <para>
417 Defaults is 10.
418 </para>
419 </listitem>
420 </varlistentry>
422 </variablelist>
423 </refsect1>
425 <refsect1>
426 <title>NETWORK CONFIGURATION</title>
428 <refsect2>
429 <title>NAT GATEWAY</title>
431 <para>
432 NAT gateway is used to configure fallback routing for nodes
433 when they do not host any public IP addresses. For example,
434 it allows unhealthy nodes to reliably communicate with
435 external infrastructure. One node in a NAT gateway group will
436 be designated as the NAT gateway master node and other (slave)
437 nodes will be configured with fallback routes via the NAT
438 gateway master node. For more information, see the
439 <citetitle>NAT GATEWAY</citetitle> section in
440 <citerefentry><refentrytitle>ctdb</refentrytitle>
441 <manvolnum>7</manvolnum></citerefentry>.
442 </para>
444 <variablelist>
446 <varlistentry>
447 <term>CTDB_NATGW_DEFAULT_GATEWAY=<parameter>IPADDR</parameter></term>
448 <listitem>
449 <para>
450 IPADDR is an alternate network gateway to use on the NAT
451 gateway master node. If set, a fallback default route
452 is added via this network gateway.
453 </para>
454 <para>
455 No default. Setting this variable is optional - if not
456 set that no route is created on the NAT gateway master
457 node.
458 </para>
459 </listitem>
460 </varlistentry>
462 <varlistentry>
463 <term>CTDB_NATGW_NODES=<parameter>FILENAME</parameter></term>
464 <listitem>
465 <para>
466 FILENAME contains the list of nodes that belong to the
467 same NAT gateway group.
468 </para>
469 <para>
470 File format:
471 <screen>
472 <parameter>IPADDR</parameter>
473 </screen>
474 </para>
475 <para>
476 No default, usually
477 <filename>/etc/ctdb/natgw_nodes</filename> when enabled.
478 </para>
479 </listitem>
480 </varlistentry>
482 <varlistentry>
483 <term>CTDB_NATGW_PRIVATE_NETWORK=<parameter>IPADDR/MASK</parameter></term>
484 <listitem>
485 <para>
486 IPADDR/MASK is the private sub-network that is
487 internally routed via the NAT gateway master node. This
488 is usually the private network that is used for node
489 addresses.
490 </para>
491 <para>
492 No default.
493 </para>
494 </listitem>
495 </varlistentry>
497 <varlistentry>
498 <term>CTDB_NATGW_PUBLIC_IFACE=<parameter>IFACE</parameter></term>
499 <listitem>
500 <para>
501 IFACE is the network interface on which the
502 CTDB_NATGW_PUBLIC_IP will be configured.
503 </para>
504 <para>
505 No default.
506 </para>
507 </listitem>
508 </varlistentry>
510 <varlistentry>
511 <term>CTDB_NATGW_PUBLIC_IP=<parameter>IPADDR/MASK</parameter></term>
512 <listitem>
513 <para>
514 IPADDR/MASK indicates the IP address that is used for
515 outgoing traffic (originating from
516 CTDB_NATGW_PRIVATE_NETWORK) on the NAT gateway master
517 node. This <emphasis>must not</emphasis> be a
518 configured public IP address.
519 </para>
520 <para>
521 No default.
522 </para>
523 </listitem>
524 </varlistentry>
526 <varlistentry>
527 <term>CTDB_NATGW_SLAVE_ONLY=yes|no</term>
528 <listitem>
529 <para>
530 When set to "yes" a node can not be a NAT gateway master
531 node. In this case
532 <varname>CTDB_NATGW_PUBLIC_IFACE</varname> and
533 <varname>CTDB_NATGW_PUBLIC_IP</varname> are optional
534 and unused.
535 </para>
536 <para>
537 Default is no.
538 </para>
539 </listitem>
540 </varlistentry>
542 <varlistentry>
543 <term>CTDB_NATGW_STATIC_ROUTES=<parameter>IPADDR/MASK[@GATEWAY]</parameter> ...</term>
544 <listitem>
545 <para>
546 Each IPADDR/MASK identifies a network or host to which
547 NATGW should create a fallback route, instead of
548 creating a single default route. This can be used when
549 there is already a default route, via an interface that
550 can not reach required infrastructure, that overrides
551 the NAT gateway default route.
552 </para>
553 <para>
554 If GATEWAY is specified then the corresponding route on
555 the NATGW master node will be via GATEWAY. Such routes
556 are created even if
557 <varname>CTDB_NATGW_DEFAULT_GATEWAY</varname> is not
558 specified. If GATEWAY is not specified for some
559 networks then routes are only created on the NATGW
560 master node for those networks if
561 <varname>CTDB_NATGW_DEFAULT_GATEWAY</varname> is
562 specified.
563 </para>
564 <para>
565 This should be used with care to avoid causing traffic
566 to unnecessarily double-hop through the NAT gateway
567 master, even when a node is hosting public IP addresses.
568 Each specified network or host should probably have a
569 corresponding automatically created link route or static
570 route to avoid this.
571 </para>
572 <para>
573 No default.
574 </para>
575 </listitem>
576 </varlistentry>
578 </variablelist>
580 <refsect3>
581 <title>Example</title>
582 <screen>
583 CTDB_NATGW_NODES=/etc/ctdb/natgw_nodes
584 CTDB_NATGW_PRIVATE_NETWORK=192.168.1.0/24
585 CTDB_NATGW_DEFAULT_GATEWAY=10.0.0.1
586 CTDB_NATGW_PUBLIC_IP=10.0.0.227/24
587 CTDB_NATGW_PUBLIC_IFACE=eth0
588 </screen>
590 <para>
591 A variation that ensures that infrastructure (ADS, DNS, ...)
592 directly attached to the public network (10.0.0.0/24) is
593 always reachable would look like this:
594 </para>
595 <screen>
596 CTDB_NATGW_NODES=/etc/ctdb/natgw_nodes
597 CTDB_NATGW_PRIVATE_NETWORK=192.168.1.0/24
598 CTDB_NATGW_PUBLIC_IP=10.0.0.227/24
599 CTDB_NATGW_PUBLIC_IFACE=eth0
600 CTDB_NATGW_STATIC_ROUTES=10.0.0.0/24
601 </screen>
602 <para>
603 Note that <varname>CTDB_NATGW_DEFAULT_GATEWAY</varname> is
604 not specified.
605 </para>
606 </refsect3>
608 </refsect2>
610 <refsect2>
611 <title>POLICY ROUTING</title>
613 <para>
614 A node running CTDB may be a component of a complex network
615 topology. In particular, public addresses may be spread
616 across several different networks (or VLANs) and it may not be
617 possible to route packets from these public addresses via the
618 system's default route. Therefore, CTDB has support for
619 policy routing via the <filename>13.per_ip_routing</filename>
620 eventscript. This allows routing to be specified for packets
621 sourced from each public address. The routes are added and
622 removed as CTDB moves public addresses between nodes.
623 </para>
625 <para>
626 For more information, see the <citetitle>POLICY
627 ROUTING</citetitle> section in
628 <citerefentry><refentrytitle>ctdb</refentrytitle>
629 <manvolnum>7</manvolnum></citerefentry>.
630 </para>
632 <variablelist>
633 <varlistentry>
634 <term>CTDB_PER_IP_ROUTING_CONF=<parameter>FILENAME</parameter></term>
635 <listitem>
636 <para>
637 FILENAME contains elements for constructing the desired
638 routes for each source address.
639 </para>
641 <para>
642 The special FILENAME value
643 <constant>__auto_link_local__</constant> indicates that no
644 configuration file is provided and that CTDB should
645 generate reasonable link-local routes for each public IP
646 address.
647 </para>
649 <para>
650 File format:
651 <screen>
652 <parameter>IPADDR</parameter> <parameter>DEST-IPADDR/MASK</parameter> <optional><parameter>GATEWAY-IPADDR</parameter></optional>
653 </screen>
654 </para>
656 <para>
657 No default, usually
658 <filename>/etc/ctdb/policy_routing</filename> when enabled.
659 </para>
660 </listitem>
661 </varlistentry>
663 <varlistentry>
664 <term>CTDB_PER_IP_ROUTING_RULE_PREF=<parameter>NUM</parameter></term>
665 <listitem>
666 <para>
667 NUM sets the priority (or preference) for the routing
668 rules that are added by CTDB.
669 </para>
671 <para>
672 This should be (strictly) greater than 0 and (strictly)
673 less than 32766. A priority of 100 is recommended, unless
674 this conflicts with a priority already in use on the
675 system. See
676 <citerefentry><refentrytitle>ip</refentrytitle>
677 <manvolnum>8</manvolnum></citerefentry>, for more details.
678 </para>
679 </listitem>
680 </varlistentry>
682 <varlistentry>
683 <term>
684 CTDB_PER_IP_ROUTING_TABLE_ID_LOW=<parameter>LOW-NUM</parameter>,
685 CTDB_PER_IP_ROUTING_TABLE_ID_HIGH=<parameter>HIGH-NUM</parameter>
686 </term>
687 <listitem>
688 <para>
689 CTDB determines a unique routing table number to use for
690 the routing related to each public address. LOW-NUM and
691 HIGH-NUM indicate the minimum and maximum routing table
692 numbers that are used.
693 </para>
695 <para>
696 <citerefentry><refentrytitle>ip</refentrytitle>
697 <manvolnum>8</manvolnum></citerefentry> uses some
698 reserved routing table numbers below 255. Therefore,
699 CTDB_PER_IP_ROUTING_TABLE_ID_LOW should be (strictly)
700 greater than 255.
701 </para>
703 <para>
704 CTDB uses the standard file
705 <filename>/etc/iproute2/rt_tables</filename> to maintain
706 a mapping between the routing table numbers and labels.
707 The label for a public address
708 <replaceable>ADDR</replaceable> will look like
709 ctdb.<replaceable>addr</replaceable>. This means that
710 the associated rules and routes are easy to read (and
711 manipulate).
712 </para>
714 <para>
715 No default, usually 1000 and 9000.
716 </para>
717 </listitem>
718 </varlistentry>
719 </variablelist>
721 <refsect3>
722 <title>Example</title>
723 <screen>
724 CTDB_PER_IP_ROUTING_CONF=/etc/ctdb/policy_routing
725 CTDB_PER_IP_ROUTING_RULE_PREF=100
726 CTDB_PER_IP_ROUTING_TABLE_ID_LOW=1000
727 CTDB_PER_IP_ROUTING_TABLE_ID_HIGH=9000
728 </screen>
729 </refsect3>
731 </refsect2>
733 <refsect2>
734 <title>MISCELLANEOUS NETWORK CONFIGURATION</title>
736 <variablelist>
738 <varlistentry>
739 <term>CTDB_PARTIALLY_ONLINE_INTERFACES=yes|no</term>
740 <listitem>
741 <para>
742 Whether one or more offline interfaces should cause a
743 monitor event to fail if there are other interfaces that
744 are up. If this is "yes" and a node has some interfaces
745 that are down then <command>ctdb status</command> will
746 display the node as "PARTIALLYONLINE".
747 </para>
749 <para>
750 Default is "no".
751 </para>
752 </listitem>
753 </varlistentry>
755 </variablelist>
756 </refsect2>
758 </refsect1>
760 <refsect1>
761 <title>SERVICE CONFIGURATION</title>
763 <para>
764 CTDB can be configured to manage and/or monitor various NAS (and
765 other) services via its eventscripts.
766 </para>
768 <para>
769 In the simplest case CTDB will manage a service. This means the
770 service will be started and stopped along with CTDB, CTDB will
771 monitor the service and CTDB will do any required
772 reconfiguration of the service when public IP addresses are
773 failed over.
774 </para>
776 <refsect2>
777 <title>SAMBA</title>
779 <refsect3>
780 <title>Eventscripts</title>
782 <simplelist>
783 <member><filename>49.winbind</filename></member>
784 <member><filename>50.samba</filename></member>
785 </simplelist>
786 </refsect3>
788 <variablelist>
790 <varlistentry>
791 <term>CTDB_MANAGES_SAMBA=yes|no</term>
792 <listitem>
793 <para>
794 Should CTDB manage Samba?
795 </para>
796 <para>
797 Default is no.
798 </para>
799 </listitem>
800 </varlistentry>
802 <varlistentry>
803 <term>CTDB_MANAGES_WINBIND=yes|no</term>
804 <listitem>
805 <para>
806 Should CTDB manage Winbind?
807 </para>
808 <para>
809 Default is no.
810 </para>
811 </listitem>
812 </varlistentry>
814 <varlistentry>
815 <term>CTDB_SAMBA_CHECK_PORTS=<parameter>PORT-LIST</parameter></term>
816 <listitem>
817 <para>
818 When monitoring Samba, check TCP ports in
819 space-separated PORT-LIST.
820 </para>
821 <para>
822 Default is to monitor ports that Samba is configured to listen on.
823 </para>
824 </listitem>
825 </varlistentry>
827 <varlistentry>
828 <term>CTDB_SAMBA_SKIP_SHARE_CHECK=yes|no</term>
829 <listitem>
830 <para>
831 As part of monitoring, should CTDB skip the check for
832 the existence of each directory configured as share in
833 Samba. This may be desirable if there is a large number
834 of shares.
835 </para>
836 <para>
837 Default is no.
838 </para>
839 </listitem>
840 </varlistentry>
842 <varlistentry>
843 <term>CTDB_SERVICE_NMB=<parameter>SERVICE</parameter></term>
844 <listitem>
845 <para>
846 Distribution specific SERVICE for managing nmbd.
847 </para>
848 <para>
849 Default is distribution-dependant.
850 </para>
851 </listitem>
852 </varlistentry>
853 <varlistentry>
854 <term>CTDB_SERVICE_SMB=<parameter>SERVICE</parameter></term>
855 <listitem>
856 <para>
857 Distribution specific SERVICE for managing smbd.
858 </para>
859 <para>
860 Default is distribution-dependant.
861 </para>
862 </listitem>
863 </varlistentry>
865 <varlistentry>
866 <term>CTDB_SERVICE_WINBIND=<parameter>SERVICE</parameter></term>
867 <listitem>
868 <para>
869 Distribution specific SERVICE for managing winbindd.
870 </para>
871 <para>
872 Default is "winbind".
873 </para>
874 </listitem>
875 </varlistentry>
877 </variablelist>
879 </refsect2>
881 <refsect2>
882 <title>NFS</title>
884 <para>
885 This includes parameters for the kernel NFS server and the
886 user-space
887 <ulink url="https://github.com/nfs-ganesha/nfs-ganesha/wiki">NFS-Ganesha</ulink>
888 server.
889 </para>
891 <refsect3>
892 <title>Eventscripts</title>
894 <simplelist>
895 <member><filename>60.nfs</filename></member>
896 <member><filename>60.ganesha</filename></member>
897 </simplelist>
898 </refsect3>
900 <variablelist>
902 <varlistentry>
903 <term>CTDB_CLUSTER_FILESYSTEM_TYPE=gpfs</term>
904 <listitem>
905 <para>
906 The type of cluster filesystem to use with NFS-ganesha.
907 Currently only "gpfs" is supported.
908 </para>
909 <para>
910 Default is "gpfs".
911 </para>
912 </listitem>
913 </varlistentry>
915 <varlistentry>
916 <term>CTDB_GANESHA_REC_SUBDIR<parameter>SUBDIR</parameter></term>
917 <listitem>
918 <para>
919 SUBDIR is the name of a top-level subdirectory in the
920 first cluster filesystem. This subdirectory is used to
921 allow communication between NFS-Ganesha and the
922 <filename>60.ganesha</filename> script.
923 </para>
924 <para>
925 Default is ".ganesha".
926 </para>
927 </listitem>
928 </varlistentry>
930 <varlistentry>
931 <term>CTDB_MANAGES_NFS=yes|no</term>
932 <listitem>
933 <para>
934 Should CTDB manage NFS?
935 </para>
936 <para>
937 Default is no.
938 </para>
939 </listitem>
940 </varlistentry>
942 <varlistentry>
943 <term>CTDB_MONITOR_NFS_THREAD_COUNT=yes|no</term>
944 <listitem>
945 <para>
946 Whether to monitor the NFS kernel server thread count.
947 </para>
948 <para>
949 This works around a limitation in some NFS initscripts
950 where some threads can be stuck in host filesystem calls
951 (perhaps due to slow storage), a restart occurs, some
952 threads don't exit, the start only adds the missing
953 number of threads, the stuck threads exit, and the
954 result is a lower than expected thread count. Note that
955 if you must also set <varname>RPCNFSDCOUNT</varname>
956 (RedHat/Debian) or <varname>USE_KERNEL_NFSD_NUMBER</varname>
957 (SUSE) in your NFS configuration so the monitoring code
958 knows how many threads there should be - if neither of
959 these are set then this option will be ignored.
960 </para>
961 <para>
962 Default is no.
963 </para>
964 </listitem>
965 </varlistentry>
967 <varlistentry>
968 <term>CTDB_NFS_DUMP_STUCK_THREADS=<parameter>NUM</parameter></term>
969 <listitem>
970 <para>
971 NUM is the number of NFS kernel server threads to dump
972 stack traces for if some are still alive after stopping
973 NFS during a restart.
974 </para>
975 <para>
976 Default is 5. Set this to 0 to disable this feature.
977 </para>
978 </listitem>
979 </varlistentry>
981 <varlistentry>
982 <term>CTDB_NFS_SERVER_MODE=kernel|ganesha</term>
983 <listitem>
984 <para>
985 Selects which NFS server to be managed.
986 </para>
987 <para>
988 This replaces the deprecated variable
989 <varname>NFS_SERVER_MODE</varname>.
990 </para>
991 <para>
992 Default is "kernel".
993 </para>
994 </listitem>
995 </varlistentry>
997 <varlistentry>
998 <term>CTDB_NFS_SKIP_KNFSD_ALIVE_CHECK=yes|no</term>
999 <listitem>
1000 <para>
1001 During monitoring, should CTDB skip the
1002 <command>rpcinfo</command> check that is used to see if
1003 the NFS kernel server is functional.
1004 </para>
1005 <para>
1006 Default is no.
1007 </para>
1008 </listitem>
1009 </varlistentry>
1011 <varlistentry>
1012 <term>CTDB_NFS_SKIP_SHARE_CHECK=yes|no</term>
1013 <listitem>
1014 <para>
1015 As part of monitoring, should CTDB skip the check for
1016 the existence of each directory exported via NFS. This
1017 may be desirable if there is a large number of exports.
1018 </para>
1019 <para>
1020 Default is no.
1021 </para>
1022 </listitem>
1023 </varlistentry>
1025 <varlistentry>
1026 <term>CTDB_RPCINFO_LOCALHOST=<parameter>IPADDR</parameter>|<parameter>HOSTNAME</parameter></term>
1027 <listitem>
1028 <para>
1029 IPADDR or HOSTNAME indicates the address that
1030 <command>rpcinfo</command> should connect to when doing
1031 <command>rpcinfo</command> check on RPC service during
1032 monitoring. Optimally this would be "localhost".
1033 However, this can add some performance overheads.
1034 </para>
1035 <para>
1036 Default is "127.0.0.1".
1037 </para>
1038 </listitem>
1039 </varlistentry>
1041 <varlistentry>
1042 <term>CTDB_SKIP_GANESHA_NFSD_CHECK=yes|no</term>
1043 <listitem>
1044 <para>
1045 As part of monitoring, should CTDB skip the check for
1046 the existence of each directory exported via
1047 NFS-Ganesha. This may be desirable if there is a large
1048 number of exports.
1049 </para>
1050 <para>
1051 Default is no.
1052 </para>
1053 </listitem>
1054 </varlistentry>
1056 </variablelist>
1058 </refsect2>
1060 <refsect2>
1061 <title>APACHE HTTPD</title>
1063 <para>
1064 CTDB can manage the Apache web server.
1065 </para>
1067 <refsect3>
1068 <title>Eventscript</title>
1070 <simplelist>
1071 <member><filename>41.httpd</filename></member>
1072 </simplelist>
1073 </refsect3>
1075 <variablelist>
1076 <varlistentry>
1077 <term>CTDB_MANAGES_HTTPD=yes|no</term>
1078 <listitem>
1079 <para>
1080 Should CTDB manage the Apache web server?
1081 </para>
1082 <para>
1083 Default is no.
1084 </para>
1085 </listitem>
1086 </varlistentry>
1087 </variablelist>
1088 </refsect2>
1090 <refsect2>
1091 <title>CLAMAV</title>
1093 <para>
1094 CTDB has support to manage the popular anti-virus daemon
1095 ClamAV.
1096 </para>
1098 <refsect3>
1099 <title>Eventscript</title>
1101 <simplelist>
1102 <member><filename>31.clamd</filename></member>
1103 </simplelist>
1105 <para>
1106 This eventscript is not enabled by default. Use
1107 <command>ctdb enablescript</command> to enable it.
1108 </para>
1110 </refsect3>
1112 <variablelist>
1114 <varlistentry>
1115 <term>CTDB_MANAGES_CLAMD=yes|no</term>
1116 <listitem>
1117 <para>
1118 Should CTDB manage ClamAV?
1119 </para>
1120 <para>
1121 Default is no.
1122 </para>
1123 </listitem>
1124 </varlistentry>
1126 <varlistentry>
1127 <term>CTDB_CLAMD_SOCKET=<parameter>FILENAME</parameter></term>
1128 <listitem>
1129 <para>
1130 FILENAME is the socket to monitor ClamAV.
1131 </para>
1132 <para>
1133 No default.
1134 </para>
1135 </listitem>
1136 </varlistentry>
1138 </variablelist>
1140 </refsect2>
1142 <refsect2>
1143 <title>ISCSI</title>
1145 <para>
1146 CTDB has support for managing the Linux iSCSI tgtd service.
1147 </para>
1149 <refsect3>
1150 <title>Eventscript</title>
1152 <simplelist>
1153 <member><filename>70.iscsi</filename></member>
1154 </simplelist>
1155 </refsect3>
1157 <variablelist>
1159 <varlistentry>
1160 <term>CTDB_MANAGES_ISCSI=yes|no</term>
1161 <listitem>
1162 <para>
1163 Should CTDB manage iSCSI tgtd?
1164 </para>
1165 <para>
1166 Default is no.
1167 </para>
1168 </listitem>
1169 </varlistentry>
1171 <varlistentry>
1172 <term>CTDB_START_ISCSI_SCRIPTS=<parameter>DIRECTORY</parameter></term>
1173 <listitem>
1174 <para>
1175 DIRECTORY on shared storage containing scripts to start
1176 tgtd for each public IP address.
1177 </para>
1178 <para>
1179 No default.
1180 </para>
1181 </listitem>
1182 </varlistentry>
1183 </variablelist>
1184 </refsect2>
1186 <refsect2>
1187 <title>MULTIPATHD</title>
1189 <para>
1190 CTDB can monitor multipath devices to ensure that active paths
1191 are available.
1192 </para>
1194 <refsect3>
1195 <title>Eventscript</title>
1197 <simplelist>
1198 <member><filename>20.multipathd</filename></member>
1199 </simplelist>
1201 <para>
1202 This eventscript is not enabled by default. Use
1203 <command>ctdb enablescript</command> to enable it.
1204 </para>
1205 </refsect3>
1207 <variablelist>
1208 <varlistentry>
1209 <term>CTDB_MONITOR_MPDEVICES=<parameter>MP-DEVICE-LIST</parameter></term>
1210 <listitem>
1211 <para>
1212 MP-DEVICE-LIST is a list of multipath devices for CTDB to monitor?
1213 </para>
1214 <para>
1215 No default.
1216 </para>
1217 </listitem>
1218 </varlistentry>
1219 </variablelist>
1220 </refsect2>
1222 <refsect2>
1223 <title>VSFTPD</title>
1225 <para>
1226 CTDB can manage the vsftpd FTP server.
1227 </para>
1229 <refsect3>
1230 <title>Eventscript</title>
1232 <simplelist>
1233 <member><filename>40.vsftpd</filename></member>
1234 </simplelist>
1235 </refsect3>
1237 <variablelist>
1238 <varlistentry>
1239 <term>CTDB_MANAGES_VSFTPD=yes|no</term>
1240 <listitem>
1241 <para>
1242 Should CTDB manage the vsftpd FTP server?
1243 </para>
1244 <para>
1245 Default is no.
1246 </para>
1247 </listitem>
1248 </varlistentry>
1249 </variablelist>
1250 </refsect2>
1252 <refsect2>
1253 <title>
1254 SYSTEM RESOURCE MONITORING CONFIGURATION
1255 </title>
1257 <para>
1258 CTDB can experience seemingly random (performance and other)
1259 issues if system resources become too contrained. Options in
1260 this section can be enabled to allow certain system resources to
1261 be checked.
1262 </para>
1264 <refsect3>
1265 <title>Eventscripts</title>
1267 <simplelist>
1268 <member><filename>00.ctdb</filename></member>
1269 <member><filename>40.fs_use</filename></member>
1270 </simplelist>
1272 <para>
1273 Filesystem usage monitoring is in
1274 <filename>40.fs_use</filename>. This eventscript is not
1275 enabled by default. Use <command>ctdb
1276 enablescript</command> to enable it.
1277 </para>
1278 </refsect3>
1280 <variablelist>
1282 <varlistentry>
1283 <term>CTDB_CHECK_FS_USE=<parameter>FS-LIMIT-LIST</parameter></term>
1284 <listitem>
1285 <para>
1286 FS-LIMIT-LIST is a space-separated list of
1287 <parameter>FILESYSTEM</parameter>:<parameter>LIMIT</parameter>
1288 pairs indicating that a node should be flagged unhealthy
1289 if the space used on FILESYSTEM reaches LIMIT%.
1290 </para>
1292 <para>
1293 No default.
1294 </para>
1296 <para>
1297 Note that this feature uses the
1298 <filename>40.fs_use</filename> eventscript, which is not
1299 enabled by default. Use <command>ctdb
1300 enablescript</command> to enable it.
1301 </para>
1302 </listitem>
1303 </varlistentry>
1305 <varlistentry>
1306 <term>CTDB_CHECK_SWAP_IS_NOT_USED=yes|no</term>
1307 <listitem>
1308 <para>
1309 Should a warning be logged if swap space is in use.
1310 </para>
1311 <para>
1312 Default is no.
1313 </para>
1314 </listitem>
1315 </varlistentry>
1317 <varlistentry>
1318 <term>CTDB_MONITOR_FREE_MEMORY=<parameter>NUM</parameter></term>
1319 <listitem>
1320 <para>
1321 NUM is a lower limit on available system memory, expressed
1322 in megabytes. If this is set and the amount of available
1323 memory falls below this limit then some debug information
1324 will be logged, the node will be disabled and then CTDB
1325 will be shut down.
1326 </para>
1327 <para>
1328 No default.
1329 </para>
1330 </listitem>
1331 </varlistentry>
1333 <varlistentry>
1334 <term>CTDB_MONITOR_FREE_MEMORY_WARN=<parameter>NUM</parameter></term>
1335 <listitem>
1336 <para>
1337 NUM is a lower limit on available system memory, expressed
1338 in megabytes. If this is set and the amount of available
1339 memory falls below this limit then a warning will be
1340 logged.
1341 </para>
1342 <para>
1343 No default.
1344 </para>
1345 </listitem>
1346 </varlistentry>
1348 </variablelist>
1349 </refsect2>
1351 <refsect2>
1352 <title>MISCELLANEOUS SERVICE-RELATED CONFIGURATION</title>
1354 <variablelist>
1356 <varlistentry>
1357 <term>CTDB_MANAGED_SERVICES=<parameter>SERVICE-LIST</parameter></term>
1358 <listitem>
1359 <para>
1360 SERVICE-LIST is a space-separated list of SERVICEs that
1361 CTDB should manage. This can be used as an alternative
1362 to the
1363 <varname>CTDB_MANAGES_<replaceable>SERVICE</replaceable></varname>
1364 variables.
1365 </para>
1366 <para>
1367 No default.
1368 </para>
1369 </listitem>
1370 </varlistentry>
1372 <varlistentry>
1373 <term>CTDB_SERVICE_AUTOSTARTSTOP=yes|no</term>
1374 <listitem>
1375 <para>
1376 When CTDB should start and stop services if they become
1377 managed or unmanaged.
1378 </para>
1379 <para>
1380 Default is no.
1381 </para>
1382 </listitem>
1383 </varlistentry>
1385 </variablelist>
1387 </refsect2>
1389 </refsect1>
1391 <refsect1>
1392 <title>
1393 TUNABLES CONFIGURATION
1394 </title>
1396 <para>
1397 CTDB tunables (see
1398 <citerefentry><refentrytitle>ctdbd-tunables</refentrytitle>
1399 <manvolnum>7</manvolnum></citerefentry>) can be set from the
1400 configuration file. They are set as follows:
1402 <literallayout>
1403 CTDB_SET_<replaceable>TUNABLE</replaceable>=<replaceable>VALUE</replaceable>
1404 </literallayout>
1405 </para>
1407 <para>
1408 For example:
1410 <screen format="linespecific">
1411 CTDB_SET_MonitorInterval=20
1412 </screen>
1413 </para>
1414 </refsect1>
1416 <refsect1>
1417 <title>
1418 DEBUG AND TEST
1419 </title>
1421 <para>
1422 Variable in this section are for debugging and testing CTDB.
1423 They should not generally be needed.
1424 </para>
1426 <variablelist>
1428 <varlistentry>
1429 <term>CTDB_DEBUG_HUNG_SCRIPT=<parameter>FILENAME</parameter></term>
1430 <listitem>
1431 <para>
1432 FILENAME is a script to run to log debug information when
1433 an event script times out.
1434 </para>
1435 <para>
1436 Default is <filename><varname>CTDB_BASE</varname>/debug-hung-script.sh</filename>.
1437 </para>
1438 </listitem>
1439 </varlistentry>
1441 <varlistentry>
1442 <term>CTDB_DEBUG_HUNG_SCRIPT_LOGFILE=<parameter>FILENAME</parameter></term>
1443 <listitem>
1444 <para>
1445 FILENAME specifies where log messages should go when
1446 debugging hung eventscripts. This is a testing option.
1447 See also <citetitle>CTDB_DEBUG_HUNG_SCRIPT</citetitle>.
1448 </para>
1449 <para>
1450 No default. Messages go to stdout/stderr and are logged
1451 to the same place as other CTDB log messages.
1452 </para>
1453 </listitem>
1454 </varlistentry>
1456 <varlistentry>
1457 <term>CTDB_DEBUG_HUNG_SCRIPT_STACKPAT=<parameter>REGEXP</parameter></term>
1458 <listitem>
1459 <para>
1460 REGEXP specifies interesting processes for which stack
1461 traces should be logged when debugging hung eventscripts
1462 and those processes are matched in pstree output. See
1463 also <citetitle>CTDB_DEBUG_HUNG_SCRIPT</citetitle>.
1464 </para>
1465 <para>
1466 Default is "exportfs\|rpcinfo".
1467 </para>
1468 </listitem>
1469 </varlistentry>
1471 <varlistentry>
1472 <term>CTDB_DEBUG_LOCKS=<parameter>FILENAME</parameter></term>
1473 <listitem>
1474 <para>
1475 FILENAME is a script to run to log debug information when
1476 an CTDB fails to freeze databases during recovery.
1477 </para>
1478 <para>
1479 No default, usually
1480 <filename><varname>CTDB_BASE</varname>/debug_locks.sh</filename>.
1481 </para>
1482 </listitem>
1483 </varlistentry>
1485 <varlistentry>
1486 <term>CTDB_ETCDIR=<parameter>DIRECTORY</parameter></term>
1487 <listitem>
1488 <para>
1489 DIRECTORY containing system configuration files. This is
1490 used to provide alternate configuration when testing and
1491 should not need to be changed from the default.
1492 </para>
1493 <para>
1494 Default is <filename>/etc</filename>.
1495 </para>
1496 </listitem>
1497 </varlistentry>
1499 <varlistentry>
1500 <term>CTDB_INIT_STYLE=debian|redhat|suse</term>
1501 <listitem>
1502 <para>
1503 This is the init style used by the Linux distribution (or
1504 other operating system) being used. This is usually
1505 determined dynamically by checking the system. This
1506 variable is used by the initscript to determine which init
1507 system primitives to use. It is also used by some
1508 eventscripts to choose the name of initscripts for certain
1509 services, since these can vary between distributions.
1510 </para>
1511 <para>
1512 No fixed default.
1513 </para>
1514 <para>
1515 If this option needs to be changed from the calculated
1516 default for the initscript to function properly, then it
1517 must be set in the distribution-specific initscript
1518 configuration, such as
1519 <filename>/etc/sysconfig/ctdb</filename>
1520 </para>
1521 </listitem>
1522 </varlistentry>
1524 <varlistentry>
1525 <term>CTDB_MAX_CORRUPT_DB_BACKUPS=<parameter>NUM</parameter></term>
1526 <listitem>
1527 <para>
1528 NUM is the maximum number of volatile TDB database backups
1529 to be kept (for each database) when a corrupt database is
1530 found during startup. Volatile TDBs are zeroed during
1531 startup so backups are needed to debug any corruption that
1532 occurs before a restart.
1533 </para>
1534 <para>
1535 Default is 10.
1536 </para>
1537 </listitem>
1538 </varlistentry>
1540 <varlistentry>
1541 <term>CTDB_RC_LOCAL=<parameter>FILENAME</parameter></term>
1542 <listitem>
1543 <para>
1544 FILENAME is a script fragment to be sourced by the
1545 <filename>functions</filename> that is sourced by scripts.
1546 On example use would be to override function definitions
1547 in unit tests. As a sanity check, this file must be
1548 executable for it to be used.
1549 </para>
1550 <para>
1551 No default.
1552 </para>
1553 </listitem>
1554 </varlistentry>
1556 <varlistentry>
1557 <term>CTDB_RUN_TIMEOUT_MONITOR=yes|no</term>
1558 <listitem>
1559 <para>
1560 Whether CTDB should simulate timing out monitor events.
1561 This uses the <filename>99.timeout</filename> eventscript.
1562 </para>
1563 <para>
1564 Default is no.
1565 </para>
1566 </listitem>
1567 </varlistentry>
1569 <varlistentry>
1570 <term>CTDB_SCRIPT_DEBUGLEVEL=<parameter>NUM</parameter></term>
1571 <listitem>
1572 <para>
1573 NUM is the level debugging messages printed by CTDB
1574 scripts. Setting this to a higher number (e.g. 4) will
1575 cause some scripts to log more messages.
1576 </para>
1577 <para>
1578 Default is 2.
1579 </para>
1580 </listitem>
1581 </varlistentry>
1583 <varlistentry>
1584 <term>CTDB_SUPPRESS_COREFILE=yes|no</term>
1585 <listitem>
1586 <para>
1587 Whether CTDB core files should be suppressed.
1588 </para>
1589 <para>
1590 Default is no.
1591 </para>
1592 </listitem>
1593 </varlistentry>
1595 <varlistentry>
1596 <term>CTDB_VALGRIND=yes|no|<parameter>COMMAND</parameter></term>
1597 <listitem>
1598 <para>
1599 If "yes", this causes
1600 <citerefentry><refentrytitle>ctdbd</refentrytitle>
1601 <manvolnum>1</manvolnum></citerefentry> to be run under
1602 <citerefentry><refentrytitle>valgrind</refentrytitle>
1603 <manvolnum>1</manvolnum></citerefentry> with logs going to
1604 <filename>/var/log/ctdb_valgrind</filename>. If neither
1605 "yes" nor "no" then the value is assumed to be a COMMAND
1606 (e.g. a <command>valgrind</command> variation, a
1607 <citerefentry><refentrytitle>gdb</refentrytitle>
1608 <manvolnum>1</manvolnum></citerefentry> command) that is
1609 used in place of the default <command>valgrind</command>
1610 command. In either case, the <option>--valgrind</option>
1611 option is passed to <command>ctdbd</command>.
1612 </para>
1613 <para>
1614 Default is no.
1615 </para>
1616 </listitem>
1617 </varlistentry>
1619 </variablelist>
1621 </refsect1>
1624 <refsect1>
1625 <title>FILES</title>
1627 <simplelist>
1628 <member><filename>/etc/ctdb/ctdbd.conf</filename></member>
1629 <member><filename>/etc/sysconfig/ctdb</filename></member>
1630 <member><filename>/etc/default/ctdb</filename></member>
1631 <member><filename>/etc/ctdb/sysconfig/ctdb</filename></member>
1632 </simplelist>
1633 </refsect1>
1635 <refsect1>
1636 <title>SEE ALSO</title>
1637 <para>
1638 <citerefentry><refentrytitle>ctdbd</refentrytitle>
1639 <manvolnum>1</manvolnum></citerefentry>,
1641 <citerefentry><refentrytitle>ctdbd_wrapper</refentrytitle>
1642 <manvolnum>1</manvolnum></citerefentry>,
1644 <citerefentry><refentrytitle>onnode</refentrytitle>
1645 <manvolnum>1</manvolnum></citerefentry>,
1647 <citerefentry><refentrytitle>ctdb</refentrytitle>
1648 <manvolnum>7</manvolnum></citerefentry>,
1650 <citerefentry><refentrytitle>ctdb-tunables</refentrytitle>
1651 <manvolnum>7</manvolnum></citerefentry>,
1653 <ulink url="http://ctdb.samba.org/"/>
1654 </para>
1655 </refsect1>
1657 <refentryinfo>
1658 <author>
1659 <contrib>
1660 This documentation was written by
1661 Amitay Isaacs,
1662 Martin Schwenke
1663 </contrib>
1664 </author>
1666 <copyright>
1667 <year>2007</year>
1668 <holder>Andrew Tridgell</holder>
1669 <holder>Ronnie Sahlberg</holder>
1670 </copyright>
1671 <legalnotice>
1672 <para>
1673 This program is free software; you can redistribute it and/or
1674 modify it under the terms of the GNU General Public License as
1675 published by the Free Software Foundation; either version 3 of
1676 the License, or (at your option) any later version.
1677 </para>
1678 <para>
1679 This program is distributed in the hope that it will be
1680 useful, but WITHOUT ANY WARRANTY; without even the implied
1681 warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
1682 PURPOSE. See the GNU General Public License for more details.
1683 </para>
1684 <para>
1685 You should have received a copy of the GNU General Public
1686 License along with this program; if not, see
1687 <ulink url="http://www.gnu.org/licenses"/>.
1688 </para>
1689 </legalnotice>
1690 </refentryinfo>
1692 </refentry>