Skip to content
Commits on Source (129)
Expand all Hide whitespace changes
Inline Side-by-side
VERSION
View file @ 1ed75f6f
......@@ -25,7 +25,7 @@
########################################################
SAMBA_VERSION_MAJOR=4
SAMBA_VERSION_MINOR=5
SAMBA_VERSION_RELEASE=12
SAMBA_VERSION_RELEASE=16
########################################################
# If a official release has a serious bug #
......
WHATSNEW.txt
View file @ 1ed75f6f
==============================
Release Notes for Samba 4.5.16
March 13, 2018
==============================
This is a security release in order to address the following defects:
o CVE-2018-1050 (Denial of Service Attack on external print server.)
o CVE-2018-1057 (Authenticated users can change other users' password.)
=======
Details
=======
o CVE-2018-1050:
All versions of Samba from 4.0.0 onwards are vulnerable to a denial of
service attack when the RPC spoolss service is configured to be run as
an external daemon. Missing input sanitization checks on some of the
input parameters to spoolss RPC calls could cause the print spooler
service to crash.
There is no known vulnerability associated with this error, merely a
denial of service. If the RPC spoolss service is left by default as an
internal service, all a client can do is crash its own authenticated
connection.
o CVE-2018-1057:
On a Samba 4 AD DC the LDAP server in all versions of Samba from
4.0.0 onwards incorrectly validates permissions to modify passwords
over LDAP allowing authenticated users to change any other users'
passwords, including administrative users.
Possible workarounds are described at a dedicated page in the Samba wiki:
https://wiki.samba.org/index.php/CVE-2018-1057
Changes since 4.5.15:
---------------------
o Jeremy Allison <jra@samba.org>
* BUG 11343: CVE-2018-1050: Codenomicon crashes in spoolss server code.
o Ralph Boehme <slow@samba.org>
* BUG 13272: CVE-2018-1057: Unprivileged user can change any user (and admin)
password.
o Stefan Metzmacher <metze@samba.org>
* BUG 13272: CVE-2018-1057: Unprivileged user can change any user (and admin)
password.
#######################################
Reporting bugs & Development Discussion
#######################################
Please discuss this release on the samba-technical mailing list or by
joining the #samba-technical IRC channel on irc.freenode.net.
If you do report problems then please try to send high quality
feedback. If you don't provide vital information to help us track down
the problem then you will probably be ignored. All bug reports should
be filed under the "Samba 4.1 and newer" product in the project's Bugzilla
database (https://bugzilla.samba.org/).
======================================================================
== Our Code, Our Bugs, Our Responsibility.
== The Samba Team
======================================================================
Release notes for older releases follow:
----------------------------------------
==============================
Release Notes for Samba 4.5.15
November 21, 2017
==============================
This is a security release in order to address the following defects:
o CVE-2017-14746 (Use-after-free vulnerability.)
o CVE-2017-15275 (Server heap memory information leak.)
=======
Details
=======
o CVE-2017-14746:
All versions of Samba from 4.0.0 onwards are vulnerable to a use after
free vulnerability, where a malicious SMB1 request can be used to
control the contents of heap memory via a deallocated heap pointer. It
is possible this may be used to compromise the SMB server.
o CVE-2017-15275:
All versions of Samba from 3.6.0 onwards are vulnerable to a heap
memory information leak, where server allocated heap memory may be
returned to the client without being cleared.
There is no known vulnerability associated with this error, but
uncleared heap memory may contain previously used data that may help
an attacker compromise the server via other methods. Uncleared heap
memory may potentially contain password hashes or other high-value
data.
For more details and workarounds, please see the security advisories:
o https://www.samba.org/samba/security/CVE-2017-14746.html
o https://www.samba.org/samba/security/CVE-2017-15275.html
Changes since 4.5.14:
---------------------
o Jeremy Allison <jra@samba.org>
* BUG 13041: CVE-2017-14746: s3: smbd: Fix SMB1 use-after-free crash bug.
* BUG 13077: CVE-2017-15275: s3: smbd: Chain code can return uninitialized
memory when talloc buffer is grown.
#######################################
Reporting bugs & Development Discussion
#######################################
Please discuss this release on the samba-technical mailing list or by
joining the #samba-technical IRC channel on irc.freenode.net.
If you do report problems then please try to send high quality
feedback. If you don't provide vital information to help us track down
the problem then you will probably be ignored. All bug reports should
be filed under the "Samba 4.1 and newer" product in the project's Bugzilla
database (https://bugzilla.samba.org/).
======================================================================
== Our Code, Our Bugs, Our Responsibility.
== The Samba Team
======================================================================
----------------------------------------------------------------------
==============================
Release Notes for Samba 4.5.14
September 20, 2017
==============================
This is a security release in order to address the following defects:
o CVE-2017-12150 (SMB1/2/3 connections may not require signing where they
should)
o CVE-2017-12151 (SMB3 connections don't keep encryption across DFS redirects)
o CVE-2017-12163 (Server memory information leak over SMB1)
=======
Details
=======
o CVE-2017-12150:
A man in the middle attack may hijack client connections.
o CVE-2017-12151:
A man in the middle attack can read and may alter confidential
documents transferred via a client connection, which are reached
via DFS redirect when the original connection used SMB3.
o CVE-2017-12163:
Client with write access to a share can cause server memory contents to be
written into a file or printer.
For more details and workarounds, please see the security advisories:
o https://www.samba.org/samba/security/CVE-2017-12150.html
o https://www.samba.org/samba/security/CVE-2017-12151.html
o https://www.samba.org/samba/security/CVE-2017-12163.html
Changes since 4.5.13:
---------------------
o Jeremy Allison <jra@samba.org>
* BUG 13020: CVE-2017-12163: s3:smbd: Prevent client short SMB1 write from
writing server memory to file.
o Stefan Metzmacher <metze@samba.org>
* BUG 12996: CVE-2017-12151: Keep required encryption across SMB3 dfs
redirects.
* BUG 12997: CVE-2017-12150: Some code path don't enforce smb signing
when they should.
#######################################
Reporting bugs & Development Discussion
#######################################
Please discuss this release on the samba-technical mailing list or by
joining the #samba-technical IRC channel on irc.freenode.net.
If you do report problems then please try to send high quality
feedback. If you don't provide vital information to help us track down
the problem then you will probably be ignored. All bug reports should
be filed under the "Samba 4.1 and newer" product in the project's Bugzilla
database (https://bugzilla.samba.org/).
======================================================================
== Our Code, Our Bugs, Our Responsibility.
== The Samba Team
======================================================================
----------------------------------------------------------------------
==============================
Release Notes for Samba 4.5.13
August 31, 2017
==============================
This is the latest stable release of the Samba 4.5 release series.
Changes since 4.5.12:
---------------------
o Jeremy Allison <jra@samba.org>
* BUG 12836: s3: smbd: Fix a read after free if a chained SMB1 call goes
async.
* BUG 12899: 'smbclient setmode' no longer works to clear attribute bits due
to dialect upgrade.
* BUG 12913: SMBC_setatr() initially uses an SMB1 call before falling back.
o Ralph Boehme <slow@samba.org>
* BUG 12791: Fix kernel oplock issues with named streams.
* BUG 12897: vfs_fruit: Don't use MS NFS ACEs with Windows clients.
* BUG 12910: s3/notifyd: Ensure notifyd doesn't return from
smbd_notifyd_init.
* BUG 12944: vfs_gpfs: handle EACCES when fetching DOS attributes from xattr.
* BUG 12885: Let non_widelink_open() chdir() to directories directly.
o Günther Deschner <gd@samba.org>
* BUG 12840: vfs_fruit: Add fruit:model = <modelname> parametric option.
o David Disseldorp <ddiss@samba.org>
* BUG 12911: vfs_ceph: fix cephwrap_chdir().
o Thomas Jarosch <thomas.jarosch@intra2net.com>
* BUG 12927: s3: libsmb: Fix use-after-free when accessing pointer *p.
o Stefan Metzmacher <metze@samba.org>
* BUG 12782: winbindd changes the local password and gets
NT_STATUS_WRONG_PASSWORD for the remote change.
* BUG 12890: s3:smbd: consistently use talloc_tos() memory for
rpc_pipe_open_interface().
#######################################
Reporting bugs & Development Discussion
#######################################
Please discuss this release on the samba-technical mailing list or by
joining the #samba-technical IRC channel on irc.freenode.net.
If you do report problems then please try to send high quality
feedback. If you don't provide vital information to help us track down
the problem then you will probably be ignored. All bug reports should
be filed under the "Samba 4.1 and newer" product in the project's Bugzilla
database (https://bugzilla.samba.org/).
======================================================================
== Our Code, Our Bugs, Our Responsibility.
== The Samba Team
======================================================================
----------------------------------------------------------------------
==============================
Release Notes for Samba 4.5.12
July 12, 2017
......@@ -48,8 +335,8 @@ database (https://bugzilla.samba.org/).
======================================================================
Release notes for older releases follow:
----------------------------------------
----------------------------------------------------------------------
==============================
Release Notes for Samba 4.5.11
......
auth/credentials/credentials.c
View file @ 1ed75f6f
......@@ -25,6 +25,7 @@
#include "librpc/gen_ndr/samr.h" /* for struct samrPassword */
#include "auth/credentials/credentials.h"
#include "auth/credentials/credentials_internal.h"
#include "auth/gensec/gensec.h"
#include "libcli/auth/libcli_auth.h"
#include "tevent.h"
#include "param/param.h"
......@@ -347,6 +348,8 @@ _PUBLIC_ bool cli_credentials_set_principal_callback(struct cli_credentials *cre
_PUBLIC_ bool cli_credentials_authentication_requested(struct cli_credentials *cred)
{
uint32_t gensec_features = 0;
if (cred->bind_dn) {
return true;
}
......@@ -374,6 +377,19 @@ _PUBLIC_ bool cli_credentials_authentication_requested(struct cli_credentials *c
return true;
}
gensec_features = cli_credentials_get_gensec_features(cred);
if (gensec_features & GENSEC_FEATURE_NTLM_CCACHE) {
return true;
}
if (gensec_features & GENSEC_FEATURE_SIGN) {
return true;
}
if (gensec_features & GENSEC_FEATURE_SEAL) {
return true;
}
return false;
}
......
ctdb/doc/ctdb-statistics.7
View file @ 1ed75f6f
'\" t
.\" Title: ctdb-statistics
.\" Author:
.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
.\" Date: 07/28/2016
.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 07/06/2017
.\" Manual: CTDB - clustered TDB database
.\" Source: ctdb
.\" Language: English
.\"
.TH "CTDB\-STATISTICS" "7" "07/28/2016" "ctdb" "CTDB \- clustered TDB database"
.TH "CTDB\-STATISTICS" "7" "07/06/2017" "ctdb" "CTDB \- clustered TDB database"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
......
ctdb/doc/ctdb-statistics.7.html
View file @ 1ed75f6f
This diff is collapsed.
ctdb/doc/ctdb-tunables.7
View file @ 1ed75f6f
'\" t
.\" Title: ctdb-tunables
.\" Author:
.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
.\" Date: 07/28/2016
.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 07/06/2017
.\" Manual: CTDB - clustered TDB database
.\" Source: ctdb
.\" Language: English
.\"
.TH "CTDB\-TUNABLES" "7" "07/28/2016" "ctdb" "CTDB \- clustered TDB database"
.TH "CTDB\-TUNABLES" "7" "07/06/2017" "ctdb" "CTDB \- clustered TDB database"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
......@@ -32,7 +32,8 @@ ctdb-tunables \- CTDB tunable configuration variables
.SH "DESCRIPTION"
.PP
CTDB\*(Aqs behaviour can be configured by setting run\-time tunable variables\&. This lists and describes all tunables\&. See the
\fBctdb\fR(1)\fBlistvars\fR,
\fBctdb\fR(1)
\fBlistvars\fR,
\fBsetvar\fR
and
\fBgetvar\fR
......
ctdb/doc/ctdb-tunables.7.html
View file @ 1ed75f6f
This diff is collapsed.
ctdb/doc/ctdb.1
View file @ 1ed75f6f
'\" t
.\" Title: ctdb
.\" Author:
.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
.\" Date: 07/12/2017
.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 07/06/2017
.\" Manual: CTDB - clustered TDB database
.\" Source: ctdb
.\" Language: English
.\"
.TH "CTDB" "1" "07/12/2017" "ctdb" "CTDB \- clustered TDB database"
.TH "CTDB" "1" "07/06/2017" "ctdb" "CTDB \- clustered TDB database"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
......
ctdb/doc/ctdb.1.html
View file @ 1ed75f6f
This diff is collapsed.
ctdb/doc/ctdb.7
View file @ 1ed75f6f
'\" t
.\" Title: ctdb
.\" Author:
.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
.\" Date: 07/28/2016
.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 07/06/2017
.\" Manual: CTDB - clustered TDB database
.\" Source: ctdb
.\" Language: English
.\"
.TH "CTDB" "7" "07/28/2016" "ctdb" "CTDB \- clustered TDB database"
.TH "CTDB" "7" "07/06/2017" "ctdb" "CTDB \- clustered TDB database"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
......
ctdb/doc/ctdb.7.html
View file @ 1ed75f6f
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ctdb</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry"><a name="ctdb.7"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ctdb &#8212; Clustered TDB</p></div><div class="refsect1"><a name="idp51821952"></a><h2>DESCRIPTION</h2><p>
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ctdb</title><meta name="generator" content="DocBook XSL Stylesheets V1.79.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry"><a name="ctdb.7"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ctdb &#8212; Clustered TDB</p></div><div class="refsect1"><a name="idm10"></a><h2>DESCRIPTION</h2><p>
CTDB is a clustered database component in clustered Samba that
provides a high-availability load-sharing CIFS server cluster.
</p><p>
......@@ -16,7 +16,7 @@
Combined with a cluster filesystem CTDB provides a full
high-availablity (HA) environment for services such as clustered
Samba, NFS and other services.
</p></div><div class="refsect1"><a name="idp50722832"></a><h2>ANATOMY OF A CTDB CLUSTER</h2><p>
</p></div><div class="refsect1"><a name="idm22"></a><h2>ANATOMY OF A CTDB CLUSTER</h2><p>
A CTDB cluster is a collection of nodes with 2 or more network
interfaces. All nodes provide network (usually file/NAS) services
to clients. Data served by file services is stored on shared
......@@ -25,7 +25,7 @@
</p><p>
CTDB provides an "all active" cluster, where services are load
balanced across all nodes.
</p></div><div class="refsect1"><a name="idp50157376"></a><h2>Recovery Lock</h2><p>
</p></div><div class="refsect1"><a name="idm26"></a><h2>Recovery Lock</h2><p>
CTDB uses a <span class="emphasis"><em>recovery lock</em></span> to avoid a
<span class="emphasis"><em>split brain</em></span>, where a cluster becomes
partitioned and each partition attempts to operate
......@@ -72,7 +72,7 @@
</p><p>
CTDB can run without a recovery lock but this is not recommended
as there will be no protection from split brains.
</p></div><div class="refsect1"><a name="idp53893632"></a><h2>Private vs Public addresses</h2><p>
</p></div><div class="refsect1"><a name="idm45"></a><h2>Private vs Public addresses</h2><p>
Each node in a CTDB cluster has multiple IP addresses assigned
to it:
......@@ -83,7 +83,7 @@
One or more public IP addresses that are used to provide
NAS or other services.
</p></li></ul></div><p>
</p><div class="refsect2"><a name="idp53897008"></a><h3>Private address</h3><p>
</p><div class="refsect2"><a name="idm53"></a><h3>Private address</h3><p>
Each node is configured with a unique, permanently assigned
private address. This address is configured by the operating
system. This address uniquely identifies a physical node in
......@@ -117,7 +117,7 @@
192.168.1.2
192.168.1.3
192.168.1.4
</pre></div><div class="refsect2"><a name="idp49115808"></a><h3>Public addresses</h3><p>
</pre></div><div class="refsect2"><a name="idm67"></a><h3>Public addresses</h3><p>
Public addresses are used to provide services to clients.
Public addresses are not configured at the operating system
level and are not permanently associated with a particular
......@@ -188,7 +188,7 @@ Node 3:/usr/local/etc/ctdb/public_addresses
</p><p>
The <span class="command"><strong>ctdb ip</strong></span> command can be used to view the
current assignment of public addresses to physical nodes.
</p></div></div><div class="refsect1"><a name="idp49127968"></a><h2>Node status</h2><p>
</p></div></div><div class="refsect1"><a name="idm88"></a><h2>Node status</h2><p>
The current status of each node in the cluster can be viewed by the
<span class="command"><strong>ctdb status</strong></span> command.
</p><p>
......@@ -233,7 +233,7 @@ Node 3:/usr/local/etc/ctdb/public_addresses
like a healthy (OK) node. Some interfaces to serve public
addresses are down, but at least one interface is up. See
also <span class="command"><strong>ctdb ifaces</strong></span>.
</p></dd></dl></div></div><div class="refsect1"><a name="idp49087984"></a><h2>CAPABILITIES</h2><p>
</p></dd></dl></div></div><div class="refsect1"><a name="idm128"></a><h2>CAPABILITIES</h2><p>
Cluster nodes can have several different capabilities enabled.
These are listed below.
</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">RECMASTER</span></dt><dd><p>
......@@ -252,7 +252,7 @@ Node 3:/usr/local/etc/ctdb/public_addresses
The RECMASTER and LMASTER capabilities can be disabled when CTDB
is used to create a cluster spanning across WAN links. In this
case CTDB acts as a WAN accelerator.
</p></div><div class="refsect1"><a name="idp49142256"></a><h2>LVS</h2><p>
</p></div><div class="refsect1"><a name="idm143"></a><h2>LVS</h2><p>
LVS is a mode where CTDB presents one single IP address for the
entire cluster. This is an alternative to using public IP
addresses and round-robin DNS to loadbalance clients across the
......@@ -326,7 +326,7 @@ Node 3:/usr/local/etc/ctdb/public_addresses
reachable from a node <span class="emphasis"><em>before</em></span> you enable
LVS. Also ensure that outgoing traffic to these hosts is routed
out through the configured public interface.
</p><div class="refsect2"><a name="idp49156560"></a><h3>Configuration</h3><p>
</p><div class="refsect2"><a name="idm167"></a><h3>Configuration</h3><p>
To activate LVS on a CTDB node you must specify the
<code class="varname">CTDB_LVS_PUBLIC_IFACE</code>,
<code class="varname">CTDB_LVS_PUBLIC_IP</code> and
......@@ -360,7 +360,7 @@ CTDB_LVS_NODES=/usr/local/etc/ctdb/lvs_nodes
192.168.1.2
192.168.1.3
192.168.1.4 slave-only
</pre></div></div><div class="refsect1"><a name="idp55056864"></a><h2>TRACKING AND RESETTING TCP CONNECTIONS</h2><p>
</pre></div></div><div class="refsect1"><a name="idm183"></a><h2>TRACKING AND RESETTING TCP CONNECTIONS</h2><p>
CTDB tracks TCP connections from clients to public IP addresses,
on known ports. When an IP address moves from one node to
another, all existing TCP connections to that IP address are
......@@ -373,7 +373,7 @@ CTDB_LVS_NODES=/usr/local/etc/ctdb/lvs_nodes
a release and take of a public IP address on the same node.
Such connections can get out of sync with sequence and ACK
numbers, potentially causing a disruptive ACK storm.
</p></div><div class="refsect1"><a name="idp55059632"></a><h2>NAT GATEWAY</h2><p>
</p></div><div class="refsect1"><a name="idm187"></a><h2>NAT GATEWAY</h2><p>
NAT gateway (NATGW) is an optional feature that is used to
configure fallback routing for nodes. This allows cluster nodes
to connect to external services (e.g. DNS, AD, NIS and LDAP)
......@@ -390,7 +390,7 @@ CTDB_LVS_NODES=/usr/local/etc/ctdb/lvs_nodes
extra static IP address to a public interface on every node.
This is simpler but it uses an extra IP address per node, while
NAT gateway generally uses only one extra IP address.
</p><div class="refsect2"><a name="idp55062320"></a><h3>Operation</h3><p>
</p><div class="refsect2"><a name="idm192"></a><h3>Operation</h3><p>
One extra NATGW public address is assigned on the public
network to each NATGW group. Each NATGW group is a set of
nodes in the cluster that shares the same NATGW address to
......@@ -411,7 +411,7 @@ CTDB_LVS_NODES=/usr/local/etc/ctdb/lvs_nodes
public IP address and routes outgoing connections from
slave nodes via this IP address. It also establishes a
fallback default route.
</p></div><div class="refsect2"><a name="idp55065328"></a><h3>Configuration</h3><p>
</p></div><div class="refsect2"><a name="idm197"></a><h3>Configuration</h3><p>
NATGW is usually configured similar to the following example configuration:
</p><pre class="screen">
CTDB_NATGW_NODES=/usr/local/etc/ctdb/natgw_nodes
......@@ -430,7 +430,7 @@ CTDB_NATGW_DEFAULT_GATEWAY=10.0.0.1
See the <em class="citetitle">NAT GATEWAY</em> section in
<span class="citerefentry"><span class="refentrytitle">ctdbd.conf</span>(5)</span> for more details of
NATGW configuration.
</p></div><div class="refsect2"><a name="idp55070096"></a><h3>Implementation details</h3><p>
</p></div><div class="refsect2"><a name="idm208"></a><h3>Implementation details</h3><p>
When the NATGW functionality is used, one of the nodes is
selected to act as a NAT gateway for all the other nodes in
the group when they need to communicate with the external
......@@ -465,7 +465,7 @@ CTDB_NATGW_DEFAULT_GATEWAY=10.0.0.1
eventscript. Please see the eventscript file and the
<em class="citetitle">NAT GATEWAY</em> section in
<span class="citerefentry"><span class="refentrytitle">ctdbd.conf</span>(5)</span> for more details.
</p></div></div><div class="refsect1"><a name="idp55077920"></a><h2>POLICY ROUTING</h2><p>
</p></div></div><div class="refsect1"><a name="idm225"></a><h2>POLICY ROUTING</h2><p>
Policy routing is an optional CTDB feature to support complex
network topologies. Public addresses may be spread across
several different networks (or VLANs) and it may not be possible
......@@ -475,7 +475,7 @@ CTDB_NATGW_DEFAULT_GATEWAY=10.0.0.1
This allows routing to be specified for packets sourced from
each public address. The routes are added and removed as CTDB
moves public addresses between nodes.
</p><div class="refsect2"><a name="idp55080144"></a><h3>Configuration variables</h3><p>
</p><div class="refsect2"><a name="idm229"></a><h3>Configuration variables</h3><p>
There are 4 configuration variables related to policy routing:
<code class="varname">CTDB_PER_IP_ROUTING_CONF</code>,
<code class="varname">CTDB_PER_IP_ROUTING_RULE_PREF</code>,
......@@ -483,7 +483,7 @@ CTDB_NATGW_DEFAULT_GATEWAY=10.0.0.1
<code class="varname">CTDB_PER_IP_ROUTING_TABLE_ID_HIGH</code>. See the
<em class="citetitle">POLICY ROUTING</em> section in
<span class="citerefentry"><span class="refentrytitle">ctdbd.conf</span>(5)</span> for more details.
</p></div><div class="refsect2"><a name="idp55084112"></a><h3>Configuration</h3><p>
</p></div><div class="refsect2"><a name="idm240"></a><h3>Configuration</h3><p>
The format of each line of
<code class="varname">CTDB_PER_IP_ROUTING_CONF</code> is:
</p><pre class="screen">
......@@ -545,7 +545,7 @@ CTDB_NATGW_DEFAULT_GATEWAY=10.0.0.1
</p><pre class="screen">
192.168.1.0/24 dev eth2 scope link
default via 192.168.1.1 dev eth2
</pre></div><div class="refsect2"><a name="idp55099328"></a><h3>Sample configuration</h3><p>
</pre></div><div class="refsect2"><a name="idm268"></a><h3>Sample configuration</h3><p>
Here is a more complete example configuration.
</p><pre class="screen">
/usr/local/etc/ctdb/public_addresses:
......@@ -565,7 +565,7 @@ CTDB_NATGW_DEFAULT_GATEWAY=10.0.0.1
The routes local packets as expected, the default route is as
previously discussed, but packets to 192.168.200.0/24 are
routed via the alternate gateway 192.168.1.254.
</p></div></div><div class="refsect1"><a name="idp55102192"></a><h2>NOTIFICATION SCRIPT</h2><p>
</p></div></div><div class="refsect1"><a name="idm273"></a><h2>NOTIFICATION SCRIPT</h2><p>
When certain state changes occur in CTDB, it can be configured
to perform arbitrary actions via a notification script. For
example, sending SNMP traps or emails when a node becomes
......@@ -581,9 +581,9 @@ CTDB_NATGW_DEFAULT_GATEWAY=10.0.0.1
</p><p>
CTDB currently generates notifications after CTDB changes to
these states:
</p><table border="0" summary="Simple list" class="simplelist"><tr><td>init</td></tr><tr><td>setup</td></tr><tr><td>startup</td></tr><tr><td>healthy</td></tr><tr><td>unhealthy</td></tr></table></div><div class="refsect1"><a name="idp55109136"></a><h2>DEBUG LEVELS</h2><p>
</p><table border="0" summary="Simple list" class="simplelist"><tr><td>init</td></tr><tr><td>setup</td></tr><tr><td>startup</td></tr><tr><td>healthy</td></tr><tr><td>unhealthy</td></tr></table></div><div class="refsect1"><a name="idm288"></a><h2>DEBUG LEVELS</h2><p>
Valid values for DEBUGLEVEL are:
</p><table border="0" summary="Simple list" class="simplelist"><tr><td>ERR (0)</td></tr><tr><td>WARNING (1)</td></tr><tr><td>NOTICE (2)</td></tr><tr><td>INFO (3)</td></tr><tr><td>DEBUG (4)</td></tr></table></div><div class="refsect1"><a name="idp55112832"></a><h2>REMOTE CLUSTER NODES</h2><p>
</p><table border="0" summary="Simple list" class="simplelist"><tr><td>ERR (0)</td></tr><tr><td>WARNING (1)</td></tr><tr><td>NOTICE (2)</td></tr><tr><td>INFO (3)</td></tr><tr><td>DEBUG (4)</td></tr></table></div><div class="refsect1"><a name="idm297"></a><h2>REMOTE CLUSTER NODES</h2><p>
It is possible to have a CTDB cluster that spans across a WAN link.
For example where you have a CTDB cluster in your datacentre but you also
want to have one additional CTDB node located at a remote branch site.
......@@ -612,7 +612,7 @@ CTDB_CAPABILITY_RECMASTER=no
</p><p>
Verify with the command "ctdb getcapabilities" that that node no longer
has the recmaster or the lmaster capabilities.
</p></div><div class="refsect1"><a name="idp55118080"></a><h2>SEE ALSO</h2><p>
</p></div><div class="refsect1"><a name="idm305"></a><h2>SEE ALSO</h2><p>
<span class="citerefentry"><span class="refentrytitle">ctdb</span>(1)</span>,
<span class="citerefentry"><span class="refentrytitle">ctdbd</span>(1)</span>,
......
ctdb/doc/ctdb_diagnostics.1
View file @ 1ed75f6f
'\" t
.\" Title: ctdb_diagnostics
.\" Author:
.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
.\" Date: 07/28/2016
.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 07/06/2017
.\" Manual: CTDB - clustered TDB database
.\" Source: ctdb
.\" Language: English
.\"
.TH "CTDB_DIAGNOSTICS" "1" "07/28/2016" "ctdb" "CTDB \- clustered TDB database"
.TH "CTDB_DIAGNOSTICS" "1" "07/06/2017" "ctdb" "CTDB \- clustered TDB database"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
......
ctdb/doc/ctdb_diagnostics.1.html
View file @ 1ed75f6f
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ctdb_diagnostics</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry"><a name="ctdb_diagnostics.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ctdb_diagnostics &#8212; dump diagnostic information about CTDB/Samba installation</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="command">ctdb_diagnostics</code> [OPTIONS] ... </p></div></div><div class="refsect1"><a name="idp53382064"></a><h2>DESCRIPTION</h2><p>
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ctdb_diagnostics</title><meta name="generator" content="DocBook XSL Stylesheets V1.79.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry"><a name="ctdb_diagnostics.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ctdb_diagnostics &#8212; dump diagnostic information about CTDB/Samba installation</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="command">ctdb_diagnostics</code> [OPTIONS] ... </p></div></div><div class="refsect1"><a name="idm15"></a><h2>DESCRIPTION</h2><p>
ctdb_diagnostics is used to dump diagnostic information about a
clustered Samba installation. This includes configuration
files, output of relevant commands and logs. This information
can be used to check the correctness of the configuration and to
diagnose problems.
</p></div><div class="refsect1"><a name="idp53996944"></a><h2>OPTIONS</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term">-n &lt;nodes&gt;</span></dt><dd><p>
</p></div><div class="refsect1"><a name="idm18"></a><h2>OPTIONS</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term">-n &lt;nodes&gt;</span></dt><dd><p>
Comma separated list of nodes to operate on
</p></dd><dt><span class="term">-c</span></dt><dd><p>
Ignore comment lines (starting with '#') in file comparisons
......@@ -12,7 +12,7 @@
Ignore whitespace in file comparisons
</p></dd><dt><span class="term">--no-ads</span></dt><dd><p>
Do not use commands that assume an Active Directory Server
</p></dd></dl></div></div><div class="refsect1"><a name="idp53724064"></a><h2>SEE ALSO</h2><p>
</p></dd></dl></div></div><div class="refsect1"><a name="idm37"></a><h2>SEE ALSO</h2><p>
<span class="citerefentry"><span class="refentrytitle">ctdb</span>(1)</span>,
<span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span>,
<a class="ulink" href="https://ctdb.samba.org/" target="_top">https://ctdb.samba.org/</a>
......
ctdb/doc/ctdbd.1
View file @ 1ed75f6f
'\" t
.\" Title: ctdbd
.\" Author:
.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
.\" Date: 07/28/2016
.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 07/06/2017
.\" Manual: CTDB - clustered TDB database
.\" Source: ctdb
.\" Language: English
.\"
.TH "CTDBD" "1" "07/28/2016" "ctdb" "CTDB \- clustered TDB database"
.TH "CTDBD" "1" "07/06/2017" "ctdb" "CTDB \- clustered TDB database"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
......
ctdb/doc/ctdbd.1.html
View file @ 1ed75f6f
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ctdbd</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry"><a name="ctdbd.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ctdbd &#8212; The CTDB cluster daemon</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="command">ctdbd</code> [<em class="replaceable"><code>OPTION</code></em>...]</p></div></div><div class="refsect1"><a name="idp54334608"></a><h2>DESCRIPTION</h2><p>
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ctdbd</title><meta name="generator" content="DocBook XSL Stylesheets V1.79.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry"><a name="ctdbd.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ctdbd &#8212; The CTDB cluster daemon</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="command">ctdbd</code> [<em class="replaceable"><code>OPTION</code></em>...]</p></div></div><div class="refsect1"><a name="idm15"></a><h2>DESCRIPTION</h2><p>
ctdbd is the main CTDB daemon.
</p><p>
Note that ctdbd is not usually invoked directly. It is invoked
via <span class="citerefentry"><span class="refentrytitle">ctdbd_wrapper</span>(1)</span> or via the initscript.
</p><p>
See <span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span> for an overview of CTDB.
</p></div><div class="refsect1"><a name="idp50549952"></a><h2>GENERAL OPTIONS</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term">-d, --debug=<em class="parameter"><code>DEBUGLEVEL</code></em></span></dt><dd><p>
</p></div><div class="refsect1"><a name="idm26"></a><h2>GENERAL OPTIONS</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term">-d, --debug=<em class="parameter"><code>DEBUGLEVEL</code></em></span></dt><dd><p>
This option sets the debug level to DEBUGLEVEL, which
controls what will be written by the logging
subsystem. The default is 2.
......@@ -193,7 +193,7 @@
The "infiniband" support is not regularly tested.
</p></dd><dt><span class="term">-?, --help</span></dt><dd><p>
Display a summary of options.
</p></dd></dl></div></div><div class="refsect1"><a name="idp55831584"></a><h2>DEBUGGING OPTIONS</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term">-i, --interactive</span></dt><dd><p>
</p></dd></dl></div></div><div class="refsect1"><a name="idm223"></a><h2>DEBUGGING OPTIONS</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term">-i, --interactive</span></dt><dd><p>
Enable interactive mode. This will make ctdbd run in the
foreground and not detach from the terminal. By default
ctdbd will detach itself and run in the background as a
......@@ -250,7 +250,7 @@
This is a debugging option. This option is only used when
debugging ctdbd. This enables additional debugging
capabilities and implies --nosetsched.
</p></dd></dl></div></div><div class="refsect1"><a name="idp55853072"></a><h2>SEE ALSO</h2><p>
</p></dd></dl></div></div><div class="refsect1"><a name="idm273"></a><h2>SEE ALSO</h2><p>
<span class="citerefentry"><span class="refentrytitle">ctdb</span>(1)</span>,
<span class="citerefentry"><span class="refentrytitle">ctdbd_wrapper</span>(1)</span>,
......
ctdb/doc/ctdbd.conf.5
View file @ 1ed75f6f
'\" t
.\" Title: ctdbd.conf
.\" Author:
.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
.\" Date: 07/28/2016
.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 07/06/2017
.\" Manual: CTDB - clustered TDB database
.\" Source: ctdb
.\" Language: English
.\"
.TH "CTDBD\&.CONF" "5" "07/28/2016" "ctdb" "CTDB \- clustered TDB database"
.TH "CTDBD\&.CONF" "5" "07/06/2017" "ctdb" "CTDB \- clustered TDB database"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
......
ctdb/doc/ctdbd.conf.5.html
View file @ 1ed75f6f
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ctdbd.conf</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry"><a name="ctdbd.conf.5"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ctdbd.conf &#8212; CTDB daemon configuration file</p></div><div class="refsect1"><a name="idp51821952"></a><h2>DESCRIPTION</h2><p>
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ctdbd.conf</title><meta name="generator" content="DocBook XSL Stylesheets V1.79.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry"><a name="ctdbd.conf.5"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ctdbd.conf &#8212; CTDB daemon configuration file</p></div><div class="refsect1"><a name="idm10"></a><h2>DESCRIPTION</h2><p>
This file contains CTDB configuration variables that are affect
the operation of CTDB. The default location of this file is
<code class="filename">/usr/local/etc/ctdb/ctdbd.conf</code>.
......@@ -17,7 +17,7 @@
A historical alternative is
<code class="filename">/usr/local/etc/ctdb/sysconfig/ctdb</code> - this is
deprecated.
</p></div><div class="refsect1"><a name="idp50156576"></a><h2>
</p></div><div class="refsect1"><a name="idm23"></a><h2>
INITSCRIPT CONFIGURATION
</h2><p>
Some options must be available to the initscript so they need to
......@@ -32,14 +32,14 @@
</p><p>
Default is <code class="filename">/usr/local/var/run/ctdb/ctdbd.pid</code>.
Corresponds to <code class="option">--pidfile</code>.
</p></dd></dl></div></div><div class="refsect1"><a name="idp53890800"></a><h2>
</p></dd></dl></div></div><div class="refsect1"><a name="idm40"></a><h2>
GLOBAL CONFIGURATION
</h2><p>
These options may be used in the initscripts, daemon and
scripts.
</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">CTDB_BASE=<em class="parameter"><code>DIRECTORY</code></em></span></dt><dd><p>
DIRECTORY containing CTDB scripts and configuration files.
</p></dd></dl></div></div><div class="refsect1"><a name="idp53894512"></a><h2>
</p></dd></dl></div></div><div class="refsect1"><a name="idm49"></a><h2>
DAEMON CONFIGURATION
</h2><p>
Variables in this section are processed by
......@@ -214,7 +214,7 @@
"setup" event before this timeout then it is killed.
</p><p>
Defaults is 10.
</p></dd></dl></div></div><div class="refsect1"><a name="idp55068560"></a><h2>NETWORK CONFIGURATION</h2><div class="refsect2"><a name="idp55069200"></a><h3>NAT GATEWAY</h3><p>
</p></dd></dl></div></div><div class="refsect1"><a name="idm277"></a><h2>NETWORK CONFIGURATION</h2><div class="refsect2"><a name="idm279"></a><h3>NAT GATEWAY</h3><p>
NAT gateway is used to configure fallback routing for nodes
when they do not host any public IP addresses. For example,
it allows unhealthy nodes to reliably communicate with
......@@ -298,7 +298,7 @@
route to avoid this.
</p><p>
No default.
</p></dd></dl></div><div class="refsect3"><a name="idp55095424"></a><h4>Example</h4><pre class="screen">
</p></dd></dl></div><div class="refsect3"><a name="idm337"></a><h4>Example</h4><pre class="screen">
CTDB_NATGW_NODES=/usr/local/etc/ctdb/natgw_nodes
CTDB_NATGW_PRIVATE_NETWORK=192.168.1.0/24
CTDB_NATGW_DEFAULT_GATEWAY=10.0.0.1
......@@ -317,7 +317,7 @@ CTDB_NATGW_STATIC_ROUTES=10.0.0.0/24
</pre><p>
Note that <code class="varname">CTDB_NATGW_DEFAULT_GATEWAY</code> is
not specified.
</p></div></div><div class="refsect2"><a name="idp55099328"></a><h3>POLICY ROUTING</h3><p>
</p></div></div><div class="refsect2"><a name="idm344"></a><h3>POLICY ROUTING</h3><p>
A node running CTDB may be a component of a complex network
topology. In particular, public addresses may be spread
across several different networks (or VLANs) and it may not be
......@@ -381,15 +381,15 @@ CTDB_NATGW_STATIC_ROUTES=10.0.0.0/24
manipulate).
</p><p>
No default, usually 1000 and 9000.
</p></dd></dl></div><div class="refsect3"><a name="idp55121264"></a><h4>Example</h4><pre class="screen">
</p></dd></dl></div><div class="refsect3"><a name="idm393"></a><h4>Example</h4><pre class="screen">
CTDB_PER_IP_ROUTING_CONF=/usr/local/etc/ctdb/policy_routing
CTDB_PER_IP_ROUTING_RULE_PREF=100
CTDB_PER_IP_ROUTING_TABLE_ID_LOW=1000
CTDB_PER_IP_ROUTING_TABLE_ID_HIGH=9000
</pre></div></div><div class="refsect2"><a name="idp55122976"></a><h3>LVS</h3><p>
</pre></div></div><div class="refsect2"><a name="idm396"></a><h3>LVS</h3><p>
For a general description see the <em class="citetitle">LVS</em>
section in <span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span>.
</p><div class="refsect3"><a name="idp55125280"></a><h4>Eventscript</h4><table border="0" summary="Simple list" class="simplelist"><tr><td><code class="filename">91.lvs</code></td></tr></table></div><div class="variablelist"><dl class="variablelist"><dt><span class="term">CTDB_LVS_NODES=<em class="parameter"><code>FILENAME</code></em></span></dt><dd><p>
</p><div class="refsect3"><a name="idm403"></a><h4>Eventscript</h4><table border="0" summary="Simple list" class="simplelist"><tr><td><code class="filename">91.lvs</code></td></tr></table></div><div class="variablelist"><dl class="variablelist"><dt><span class="term">CTDB_LVS_NODES=<em class="parameter"><code>FILENAME</code></em></span></dt><dd><p>
FILENAME contains the list of nodes that belong to the
same LVS group.
</p><p>
......@@ -417,7 +417,7 @@ CTDB_PER_IP_ROUTING_TABLE_ID_HIGH=9000
</p></dd><dt><span class="term">CTDB_LVS_PUBLIC_IP=<em class="parameter"><code>IPADDR</code></em></span></dt><dd><p>
CTDB_LVS_PUBLIC_IP is the LVS public address. No
default.
</p></dd></dl></div></div><div class="refsect2"><a name="idp55139536"></a><h3>MISCELLANEOUS NETWORK CONFIGURATION</h3><div class="variablelist"><dl class="variablelist"><dt><span class="term">CTDB_PARTIALLY_ONLINE_INTERFACES=yes|no</span></dt><dd><p>
</p></dd></dl></div></div><div class="refsect2"><a name="idm435"></a><h3>MISCELLANEOUS NETWORK CONFIGURATION</h3><div class="variablelist"><dl class="variablelist"><dt><span class="term">CTDB_PARTIALLY_ONLINE_INTERFACES=yes|no</span></dt><dd><p>
Whether one or more offline interfaces should cause a
monitor event to fail if there are other interfaces that
are up. If this is "yes" and a node has some interfaces
......@@ -430,7 +430,7 @@ CTDB_PER_IP_ROUTING_TABLE_ID_HIGH=9000
to be up.
</p><p>
Default is "no".
</p></dd></dl></div></div></div><div class="refsect1"><a name="idp55144288"></a><h2>SERVICE CONFIGURATION</h2><p>
</p></dd></dl></div></div></div><div class="refsect1"><a name="idm445"></a><h2>SERVICE CONFIGURATION</h2><p>
CTDB can be configured to manage and/or monitor various NAS (and
other) services via its eventscripts.
</p><p>
......@@ -439,7 +439,7 @@ CTDB_PER_IP_ROUTING_TABLE_ID_HIGH=9000
monitor the service and CTDB will do any required
reconfiguration of the service when public IP addresses are
failed over.
</p><div class="refsect2"><a name="idp55146144"></a><h3>SAMBA</h3><div class="refsect3"><a name="idp55146784"></a><h4>Eventscripts</h4><table border="0" summary="Simple list" class="simplelist"><tr><td><code class="filename">49.winbind</code></td></tr><tr><td><code class="filename">50.samba</code></td></tr></table></div><div class="variablelist"><dl class="variablelist"><dt><span class="term">CTDB_MANAGES_SAMBA=yes|no</span></dt><dd><p>
</p><div class="refsect2"><a name="idm449"></a><h3>SAMBA</h3><div class="refsect3"><a name="idm451"></a><h4>Eventscripts</h4><table border="0" summary="Simple list" class="simplelist"><tr><td><code class="filename">49.winbind</code></td></tr><tr><td><code class="filename">50.samba</code></td></tr></table></div><div class="variablelist"><dl class="variablelist"><dt><span class="term">CTDB_MANAGES_SAMBA=yes|no</span></dt><dd><p>
Should CTDB manage Samba?
</p><p>
Default is no.
......@@ -471,11 +471,11 @@ CTDB_PER_IP_ROUTING_TABLE_ID_HIGH=9000
Distribution specific SERVICE for managing winbindd.
</p><p>
Default is "winbind".
</p></dd></dl></div></div><div class="refsect2"><a name="idp55166288"></a><h3>NFS</h3><p>
</p></dd></dl></div></div><div class="refsect2"><a name="idm498"></a><h3>NFS</h3><p>
This includes parameters for the kernel NFS server.
Alternative NFS subsystems (such as <a class="ulink" href="https://github.com/nfs-ganesha/nfs-ganesha/wiki" target="_top">NFS-Ganesha</a>)
can be integrated using <code class="varname">CTDB_NFS_CALLOUT</code>.
</p><div class="refsect3"><a name="idp55168432"></a><h4>Eventscript</h4><table border="0" summary="Simple list" class="simplelist"><tr><td><code class="filename">60.nfs</code></td></tr></table></div><div class="variablelist"><dl class="variablelist"><dt><span class="term">CTDB_MANAGES_NFS=yes|no</span></dt><dd><p>
</p><div class="refsect3"><a name="idm503"></a><h4>Eventscript</h4><table border="0" summary="Simple list" class="simplelist"><tr><td><code class="filename">60.nfs</code></td></tr></table></div><div class="variablelist"><dl class="variablelist"><dt><span class="term">CTDB_MANAGES_NFS=yes|no</span></dt><dd><p>
Should CTDB manage NFS?
</p><p>
Default is no.
......@@ -515,16 +515,16 @@ CTDB_PER_IP_ROUTING_TABLE_ID_HIGH=9000
</p></dd><dt><span class="term">CTDB_NFS_STATE_MNT=<em class="parameter"><code>DIR</code></em></span></dt><dd><p>
The directory where a clustered NFS' shared state will be
located. No default.
</p></dd></dl></div></div><div class="refsect2"><a name="idp55191744"></a><h3>APACHE HTTPD</h3><p>
</p></dd></dl></div></div><div class="refsect2"><a name="idm554"></a><h3>APACHE HTTPD</h3><p>
CTDB can manage the Apache web server.
</p><div class="refsect3"><a name="idp55192768"></a><h4>Eventscript</h4><table border="0" summary="Simple list" class="simplelist"><tr><td><code class="filename">41.httpd</code></td></tr></table></div><div class="variablelist"><dl class="variablelist"><dt><span class="term">CTDB_MANAGES_HTTPD=yes|no</span></dt><dd><p>
</p><div class="refsect3"><a name="idm557"></a><h4>Eventscript</h4><table border="0" summary="Simple list" class="simplelist"><tr><td><code class="filename">41.httpd</code></td></tr></table></div><div class="variablelist"><dl class="variablelist"><dt><span class="term">CTDB_MANAGES_HTTPD=yes|no</span></dt><dd><p>
Should CTDB manage the Apache web server?
</p><p>
Default is no.
</p></dd></dl></div></div><div class="refsect2"><a name="idp55197344"></a><h3>CLAMAV</h3><p>
</p></dd></dl></div></div><div class="refsect2"><a name="idm568"></a><h3>CLAMAV</h3><p>
CTDB has support to manage the popular anti-virus daemon
ClamAV.
</p><div class="refsect3"><a name="idp55198464"></a><h4>Eventscript</h4><table border="0" summary="Simple list" class="simplelist"><tr><td><code class="filename">31.clamd</code></td></tr></table><p>
</p><div class="refsect3"><a name="idm571"></a><h4>Eventscript</h4><table border="0" summary="Simple list" class="simplelist"><tr><td><code class="filename">31.clamd</code></td></tr></table><p>
This eventscript is not enabled by default. Use
<span class="command"><strong>ctdb enablescript</strong></span> to enable it.
</p></div><div class="variablelist"><dl class="variablelist"><dt><span class="term">CTDB_MANAGES_CLAMD=yes|no</span></dt><dd><p>
......@@ -535,9 +535,9 @@ CTDB_PER_IP_ROUTING_TABLE_ID_HIGH=9000
FILENAME is the socket to monitor ClamAV.
</p><p>
No default.
</p></dd></dl></div></div><div class="refsect2"><a name="idp55206544"></a><h3>ISCSI</h3><p>
</p></dd></dl></div></div><div class="refsect2"><a name="idm590"></a><h3>ISCSI</h3><p>
CTDB has support for managing the Linux iSCSI tgtd service.
</p><div class="refsect3"><a name="idp55207648"></a><h4>Eventscript</h4><table border="0" summary="Simple list" class="simplelist"><tr><td><code class="filename">70.iscsi</code></td></tr></table></div><div class="variablelist"><dl class="variablelist"><dt><span class="term">CTDB_MANAGES_ISCSI=yes|no</span></dt><dd><p>
</p><div class="refsect3"><a name="idm593"></a><h4>Eventscript</h4><table border="0" summary="Simple list" class="simplelist"><tr><td><code class="filename">70.iscsi</code></td></tr></table></div><div class="variablelist"><dl class="variablelist"><dt><span class="term">CTDB_MANAGES_ISCSI=yes|no</span></dt><dd><p>
Should CTDB manage iSCSI tgtd?
</p><p>
Default is no.
......@@ -546,23 +546,23 @@ CTDB_PER_IP_ROUTING_TABLE_ID_HIGH=9000
tgtd for each public IP address.
</p><p>
No default.
</p></dd></dl></div></div><div class="refsect2"><a name="idp55214768"></a><h3>MULTIPATHD</h3><p>
</p></dd></dl></div></div><div class="refsect2"><a name="idm610"></a><h3>MULTIPATHD</h3><p>
CTDB can monitor multipath devices to ensure that active paths
are available.
</p><div class="refsect3"><a name="idp55215888"></a><h4>Eventscript</h4><table border="0" summary="Simple list" class="simplelist"><tr><td><code class="filename">20.multipathd</code></td></tr></table><p>
</p><div class="refsect3"><a name="idm613"></a><h4>Eventscript</h4><table border="0" summary="Simple list" class="simplelist"><tr><td><code class="filename">20.multipathd</code></td></tr></table><p>
This eventscript is not enabled by default. Use
<span class="command"><strong>ctdb enablescript</strong></span> to enable it.
</p></div><div class="variablelist"><dl class="variablelist"><dt><span class="term">CTDB_MONITOR_MPDEVICES=<em class="parameter"><code>MP-DEVICE-LIST</code></em></span></dt><dd><p>
MP-DEVICE-LIST is a list of multipath devices for CTDB to monitor?
</p><p>
No default.
</p></dd></dl></div></div><div class="refsect2"><a name="idp55222144"></a><h3>VSFTPD</h3><p>
</p></dd></dl></div></div><div class="refsect2"><a name="idm627"></a><h3>VSFTPD</h3><p>
CTDB can manage the vsftpd FTP server.
</p><div class="refsect3"><a name="idp55223168"></a><h4>Eventscript</h4><table border="0" summary="Simple list" class="simplelist"><tr><td><code class="filename">40.vsftpd</code></td></tr></table></div><div class="variablelist"><dl class="variablelist"><dt><span class="term">CTDB_MANAGES_VSFTPD=yes|no</span></dt><dd><p>
</p><div class="refsect3"><a name="idm630"></a><h4>Eventscript</h4><table border="0" summary="Simple list" class="simplelist"><tr><td><code class="filename">40.vsftpd</code></td></tr></table></div><div class="variablelist"><dl class="variablelist"><dt><span class="term">CTDB_MANAGES_VSFTPD=yes|no</span></dt><dd><p>
Should CTDB manage the vsftpd FTP server?
</p><p>
Default is no.
</p></dd></dl></div></div><div class="refsect2"><a name="idp55227744"></a><h3>
</p></dd></dl></div></div><div class="refsect2"><a name="idm641"></a><h3>
SYSTEM RESOURCE MONITORING CONFIGURATION
</h3><p>
CTDB can experience seemingly random (performance and other)
......@@ -575,7 +575,7 @@ CTDB_PER_IP_ROUTING_TABLE_ID_HIGH=9000
Some checks are enabled by default. It is recommended that
these checks remain enabled or are augmented by extra checks.
There is no supported way of completely disabling the checks.
</p><div class="refsect3"><a name="idp55229728"></a><h4>Eventscripts</h4><table border="0" summary="Simple list" class="simplelist"><tr><td><code class="filename">05.system</code></td></tr></table><p>
</p><div class="refsect3"><a name="idm645"></a><h4>Eventscripts</h4><table border="0" summary="Simple list" class="simplelist"><tr><td><code class="filename">05.system</code></td></tr></table><p>
Filesystem and memory usage monitoring is in
<code class="filename">05.system</code>.
</p></div><div class="variablelist"><dl class="variablelist"><dt><span class="term">CTDB_MONITOR_FILESYSTEM_USAGE=<em class="parameter"><code>FS-LIMIT-LIST</code></em></span></dt><dd><p>
......@@ -614,7 +614,7 @@ CTDB_PER_IP_ROUTING_TABLE_ID_HIGH=9000
</p><p>
Default is 25, so warnings will be logged when swap
usage reaches 25%.
</p></dd></dl></div></div><div class="refsect2"><a name="idp55247888"></a><h3>MISCELLANEOUS SERVICE-RELATED CONFIGURATION</h3><div class="variablelist"><dl class="variablelist"><dt><span class="term">CTDB_MANAGED_SERVICES=<em class="parameter"><code>SERVICE-LIST</code></em></span></dt><dd><p>
</p></dd></dl></div></div><div class="refsect2"><a name="idm684"></a><h3>MISCELLANEOUS SERVICE-RELATED CONFIGURATION</h3><div class="variablelist"><dl class="variablelist"><dt><span class="term">CTDB_MANAGED_SERVICES=<em class="parameter"><code>SERVICE-LIST</code></em></span></dt><dd><p>
SERVICE-LIST is a space-separated list of SERVICEs that
CTDB should manage. This can be used as an alternative
to the
......@@ -627,7 +627,7 @@ CTDB_PER_IP_ROUTING_TABLE_ID_HIGH=9000
managed or unmanaged.
</p><p>
Default is no.
</p></dd></dl></div></div></div><div class="refsect1"><a name="idp55254416"></a><h2>
</p></dd></dl></div></div></div><div class="refsect1"><a name="idm700"></a><h2>
TUNABLES CONFIGURATION
</h2><p>
CTDB tunables (see
......@@ -643,7 +643,7 @@ CTDB_SET_<em class="replaceable"><code>TUNABLE</code></em>=<em class="replaceabl
</p><pre class="screen">
CTDB_SET_MonitorInterval=20
</pre><p>
</p></div><div class="refsect1"><a name="idp55259200"></a><h2>
</p></div><div class="refsect1"><a name="idm711"></a><h2>
DEBUG AND TEST
</h2><p>
Variable in this section are for debugging and testing CTDB.
......@@ -750,7 +750,7 @@ CTDB_SET_MonitorInterval=20
runtime.
</p><p>
Defaults to <code class="filename">/usr/local/var/lib/ctdb</code>.
</p></dd></dl></div></div><div class="refsect1"><a name="idp55307616"></a><h2>FILES</h2><table border="0" summary="Simple list" class="simplelist"><tr><td><code class="filename">/usr/local/etc/ctdb/ctdbd.conf</code></td></tr><tr><td><code class="filename">/etc/sysconfig/ctdb</code></td></tr><tr><td><code class="filename">/etc/default/ctdb</code></td></tr><tr><td><code class="filename">/usr/local/etc/ctdb/sysconfig/ctdb</code></td></tr></table></div><div class="refsect1"><a name="idp55312016"></a><h2>SEE ALSO</h2><p>
</p></dd></dl></div></div><div class="refsect1"><a name="idm822"></a><h2>FILES</h2><table border="0" summary="Simple list" class="simplelist"><tr><td><code class="filename">/usr/local/etc/ctdb/ctdbd.conf</code></td></tr><tr><td><code class="filename">/etc/sysconfig/ctdb</code></td></tr><tr><td><code class="filename">/etc/default/ctdb</code></td></tr><tr><td><code class="filename">/usr/local/etc/ctdb/sysconfig/ctdb</code></td></tr></table></div><div class="refsect1"><a name="idm833"></a><h2>SEE ALSO</h2><p>
<span class="citerefentry"><span class="refentrytitle">ctdbd</span>(1)</span>,
<span class="citerefentry"><span class="refentrytitle">ctdbd_wrapper</span>(1)</span>,
......
ctdb/doc/ctdbd_wrapper.1
View file @ 1ed75f6f
'\" t
.\" Title: ctdbd_wrapper
.\" Author:
.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
.\" Date: 07/28/2016
.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 07/06/2017
.\" Manual: CTDB - clustered TDB database
.\" Source: ctdb
.\" Language: English
.\"
.TH "CTDBD_WRAPPER" "1" "07/28/2016" "ctdb" "CTDB \- clustered TDB database"
.TH "CTDBD_WRAPPER" "1" "07/06/2017" "ctdb" "CTDB \- clustered TDB database"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
......
ctdb/doc/ctdbd_wrapper.1.html
View file @ 1ed75f6f
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ctdbd_wrapper</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry"><a name="ctdbd_wrapper.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ctdbd_wrapper &#8212; Wrapper for ctdbd</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="command">ctdbd_wrapper</code> {<em class="replaceable"><code>PIDFILE</code></em>} { start | stop }</p></div></div><div class="refsect1"><a name="idp53021808"></a><h2>DESCRIPTION</h2><p>
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ctdbd_wrapper</title><meta name="generator" content="DocBook XSL Stylesheets V1.79.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry"><a name="ctdbd_wrapper.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ctdbd_wrapper &#8212; Wrapper for ctdbd</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="command">ctdbd_wrapper</code> {<em class="replaceable"><code>PIDFILE</code></em>} { start | stop }</p></div></div><div class="refsect1"><a name="idm18"></a><h2>DESCRIPTION</h2><p>
ctdbd_wrapper is used to start or stop the main CTDB daemon.
</p><p>
<em class="replaceable"><code>PIDFILE</code></em> specifies the location of the
......@@ -9,7 +9,7 @@
<span class="citerefentry"><span class="refentrytitle">ctdbd.conf</span>(5)</span>.
</p><p>
See <span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span> for an overview of CTDB.
</p></div><div class="refsect1"><a name="idp54553952"></a><h2>SEE ALSO</h2><p>
</p></div><div class="refsect1"><a name="idm31"></a><h2>SEE ALSO</h2><p>
<span class="citerefentry"><span class="refentrytitle">ctdbd</span>(1)</span>,
<span class="citerefentry"><span class="refentrytitle">ctdbd.conf</span>(5)</span>,
......
ctdb/doc/ltdbtool.1
View file @ 1ed75f6f
'\" t
.\" Title: ltdbtool
.\" Author:
.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
.\" Date: 07/28/2016
.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\" Date: 07/06/2017
.\" Manual: CTDB - clustered TDB database
.\" Source: ctdb
.\" Language: English
.\"
.TH "LTDBTOOL" "1" "07/28/2016" "ctdb" "CTDB \- clustered TDB database"
.TH "LTDBTOOL" "1" "07/06/2017" "ctdb" "CTDB \- clustered TDB database"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
......