[Pkg-samba-maint] [samba] 19/19: Imported Upstream version 4.3.3+dfsg

Jelmer Vernooij jelmer at moszumanska.debian.org
Fri Dec 18 13:08:31 UTC 2015


This is an automated email from the git hooks/post-receive script.

jelmer pushed a commit to branch upstream_4.3
in repository samba.

commit bad8819ef254386e7935720bbe78e0ee8b6fd696
Merge: 5c1d413 b7676d1
Author: Jelmer Vernooij <jelmer at jelmer.uk>
Date:   Fri Dec 18 01:18:00 2015 +0000

    Imported Upstream version 4.3.3+dfsg

 VERSION                                           |   2 +-
 WHATSNEW.txt                                      | 151 ++++++++++++++-
 ctdb/doc/ctdb-statistics.7                        |   4 +-
 ctdb/doc/ctdb-statistics.7.html                   | 134 +++++++-------
 ctdb/doc/ctdb-tunables.7                          |   4 +-
 ctdb/doc/ctdb-tunables.7.html                     | 106 +++++------
 ctdb/doc/ctdb.1                                   |   4 +-
 ctdb/doc/ctdb.1.html                              | 216 +++++++++++-----------
 ctdb/doc/ctdb.7                                   |   4 +-
 ctdb/doc/ctdb.7.html                              |  44 ++---
 ctdb/doc/ctdbd.1                                  |   4 +-
 ctdb/doc/ctdbd.1.html                             |   8 +-
 ctdb/doc/ctdbd.conf.5                             |   4 +-
 ctdb/doc/ctdbd.conf.5.html                        |  58 +++---
 ctdb/doc/ctdbd_wrapper.1                          |   4 +-
 ctdb/doc/ctdbd_wrapper.1.html                     |   4 +-
 ctdb/doc/ltdbtool.1                               |   4 +-
 ctdb/doc/ltdbtool.1.html                          |  10 +-
 ctdb/doc/onnode.1                                 |   4 +-
 ctdb/doc/onnode.1.html                            |  14 +-
 ctdb/doc/ping_pong.1                              |   4 +-
 ctdb/doc/ping_pong.1.html                         |   8 +-
 docs/manpages/dbwrap_tool.1                       |   4 +-
 docs/manpages/eventlogadm.8                       |   4 +-
 docs/manpages/findsmb.1                           |   4 +-
 docs/manpages/idmap_ad.8                          |   4 +-
 docs/manpages/idmap_autorid.8                     |   4 +-
 docs/manpages/idmap_hash.8                        |   4 +-
 docs/manpages/idmap_ldap.8                        |   4 +-
 docs/manpages/idmap_nss.8                         |   4 +-
 docs/manpages/idmap_rfc2307.8                     |   4 +-
 docs/manpages/idmap_rid.8                         |   4 +-
 docs/manpages/idmap_script.8                      |   4 +-
 docs/manpages/idmap_tdb.8                         |   4 +-
 docs/manpages/idmap_tdb2.8                        |   4 +-
 docs/manpages/libsmbclient.7                      |   4 +-
 docs/manpages/lmhosts.5                           |   4 +-
 docs/manpages/log2pcap.1                          |   4 +-
 docs/manpages/net.8                               |   4 +-
 docs/manpages/nmbd.8                              |   4 +-
 docs/manpages/nmblookup.1                         |   4 +-
 docs/manpages/ntlm_auth.1                         |   4 +-
 docs/manpages/pam_winbind.8                       |   4 +-
 docs/manpages/pam_winbind.conf.5                  |   4 +-
 docs/manpages/pdbedit.8                           |   4 +-
 docs/manpages/profiles.1                          |   4 +-
 docs/manpages/rpcclient.1                         |   4 +-
 docs/manpages/samba-regedit.8                     |   4 +-
 docs/manpages/samba-tool.8                        |   4 +-
 docs/manpages/samba.7                             |   4 +-
 docs/manpages/samba.8                             |   4 +-
 docs/manpages/sharesec.1                          |   4 +-
 docs/manpages/smb.conf.5                          |   4 +-
 docs/manpages/smbcacls.1                          |   4 +-
 docs/manpages/smbclient.1                         |   4 +-
 docs/manpages/smbcontrol.1                        |   4 +-
 docs/manpages/smbcquotas.1                        |   4 +-
 docs/manpages/smbd.8                              |   4 +-
 docs/manpages/smbget.1                            |   4 +-
 docs/manpages/smbgetrc.5                          |   4 +-
 docs/manpages/smbpasswd.5                         |   4 +-
 docs/manpages/smbpasswd.8                         |   4 +-
 docs/manpages/smbspool.8                          |   4 +-
 docs/manpages/smbstatus.1                         |   4 +-
 docs/manpages/smbta-util.8                        |   4 +-
 docs/manpages/smbtar.1                            |   4 +-
 docs/manpages/smbtree.1                           |   4 +-
 docs/manpages/testparm.1                          |   4 +-
 docs/manpages/vfs_acl_tdb.8                       |   4 +-
 docs/manpages/vfs_acl_xattr.8                     |   4 +-
 docs/manpages/vfs_aio_fork.8                      |   4 +-
 docs/manpages/vfs_aio_linux.8                     |   4 +-
 docs/manpages/vfs_aio_pthread.8                   |   4 +-
 docs/manpages/vfs_audit.8                         |   4 +-
 docs/manpages/vfs_btrfs.8                         |   4 +-
 docs/manpages/vfs_cacheprime.8                    |   4 +-
 docs/manpages/vfs_cap.8                           |   4 +-
 docs/manpages/vfs_catia.8                         |   4 +-
 docs/manpages/vfs_ceph.8                          |   4 +-
 docs/manpages/vfs_commit.8                        |   4 +-
 docs/manpages/vfs_crossrename.8                   |   4 +-
 docs/manpages/vfs_default_quota.8                 |   4 +-
 docs/manpages/vfs_dirsort.8                       |   4 +-
 docs/manpages/vfs_extd_audit.8                    |   4 +-
 docs/manpages/vfs_fake_perms.8                    |   4 +-
 docs/manpages/vfs_fileid.8                        |   4 +-
 docs/manpages/vfs_fruit.8                         |   4 +-
 docs/manpages/vfs_full_audit.8                    |   4 +-
 docs/manpages/vfs_glusterfs.8                     |   4 +-
 docs/manpages/vfs_gpfs.8                          |   4 +-
 docs/manpages/vfs_linux_xfs_sgid.8                |   4 +-
 docs/manpages/vfs_media_harmony.8                 |   4 +-
 docs/manpages/vfs_netatalk.8                      |   4 +-
 docs/manpages/vfs_prealloc.8                      |   4 +-
 docs/manpages/vfs_preopen.8                       |   4 +-
 docs/manpages/vfs_readahead.8                     |   4 +-
 docs/manpages/vfs_readonly.8                      |   4 +-
 docs/manpages/vfs_recycle.8                       |   4 +-
 docs/manpages/vfs_scannedonly.8                   |   4 +-
 docs/manpages/vfs_shadow_copy.8                   |   4 +-
 docs/manpages/vfs_shadow_copy2.8                  |   4 +-
 docs/manpages/vfs_shell_snap.8                    |   4 +-
 docs/manpages/vfs_smb_traffic_analyzer.8          |   4 +-
 docs/manpages/vfs_snapper.8                       |   4 +-
 docs/manpages/vfs_streams_depot.8                 |   4 +-
 docs/manpages/vfs_streams_xattr.8                 |   4 +-
 docs/manpages/vfs_syncops.8                       |   4 +-
 docs/manpages/vfs_time_audit.8                    |   4 +-
 docs/manpages/vfs_tsmsm.8                         |   4 +-
 docs/manpages/vfs_unityed_media.8                 |   4 +-
 docs/manpages/vfs_worm.8                          |   4 +-
 docs/manpages/vfs_xattr_tdb.8                     |   4 +-
 docs/manpages/vfs_zfsacl.8                        |   4 +-
 docs/manpages/vfstest.1                           |   4 +-
 docs/manpages/wbinfo.1                            |   4 +-
 docs/manpages/winbind_krb5_locator.7              |   4 +-
 docs/manpages/winbindd.8                          |   4 +-
 lib/ldb/common/ldb_dn.c                           |  67 ++++---
 lib/ldb/common/ldb_match.c                        |  33 +++-
 lib/ldb/wscript                                   |   5 +-
 lib/util/charset/charset.h                        |   9 +-
 lib/util/charset/codepoints.c                     |  29 ++-
 lib/util/charset/util_str.c                       |   3 +-
 lib/util/charset/util_unistr.c                    |   6 +-
 libcli/smb/smbXcli_base.c                         |  11 ++
 script/autobuild.py                               |   2 +-
 source3/libsmb/clidfs.c                           |   7 +-
 source3/libsmb/libsmb_server.c                    |  15 +-
 source3/modules/vfs_shadow_copy2.c                |  45 +++++
 source3/smbd/vfs.c                                |  13 +-
 source4/dsdb/samdb/ldb_modules/samldb.c           |  24 ++-
 source4/dsdb/tests/python/user_account_control.py |  63 ++++++-
 132 files changed, 917 insertions(+), 590 deletions(-)

diff --cc ctdb/doc/ctdb-statistics.7
index e84de24,0000000..fd48f62
mode 100644,000000..100644
--- a/ctdb/doc/ctdb-statistics.7
+++ b/ctdb/doc/ctdb-statistics.7
@@@ -1,528 -1,0 +1,528 @@@
 +'\" t
 +.\"     Title: ctdb-statistics
 +.\"    Author: 
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 09/08/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: CTDB - clustered TDB database
 +.\"    Source: ctdb
 +.\"  Language: English
 +.\"
- .TH "CTDB\-STATISTICS" "7" "09/08/2015" "ctdb" "CTDB \- clustered TDB database"
++.TH "CTDB\-STATISTICS" "7" "12/10/2015" "ctdb" "CTDB \- clustered TDB database"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +ctdb-statistics \- CTDB statistics output
 +.SH "OVERALL STATISTICS"
 +.PP
 +CTDB maintains information about various messages communicated and some of the important operations per node\&. See the
 +\fBctdb\fR(1)
 +commands
 +\fBstatistics\fR
 +and
 +\fBstatisticsreset\fR
 +for displaying statistics\&.
 +.SS "Example: ctdb statistics"
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +CTDB version 1
 +Current time of statistics  :                Fri Sep 12 13:32:32 2014
 +Statistics collected since  : (000 01:49:20) Fri Sep 12 11:43:12 2014
 + num_clients                        6
 + frozen                             0
 + recovering                         0
 + num_recoveries                     2
 + client_packets_sent           281293
 + client_packets_recv           296317
 + node_packets_sent             452387
 + node_packets_recv             182394
 + keepalive_packets_sent          3927
 + keepalive_packets_recv          3928
 + node
 +     req_call                   48605
 +     reply_call                     1
 +     req_dmaster                23404
 +     reply_dmaster              24917
 +     reply_error                    0
 +     req_message                  958
 +     req_control               197513
 +     reply_control             153705
 + client
 +     req_call                  130866
 +     req_message                  770
 +     req_control               168921
 + timeouts
 +     call                           0
 +     control                        0
 +     traverse                       0
 + locks
 +     num_calls                    220
 +     num_current                    0
 +     num_pending                    0
 +     num_failed                     0
 + total_calls                   130866
 + pending_calls                      0
 + childwrite_calls                   1
 + pending_childwrite_calls             0
 + memory_used                   334490
 + max_hop_count                     18
 + total_ro_delegations               2
 + total_ro_revokes                   2
 + hop_count_buckets: 42816 5464 26 1 0 0 0 0 0 0 0 0 0 0 0 0
 + lock_buckets: 9 165 14 15 7 2 2 0 0 0 0 0 0 0 0 0
 + locks_latency      MIN/AVG/MAX     0\&.000685/0\&.160302/6\&.369342 sec out of 214
 + reclock_ctdbd      MIN/AVG/MAX     0\&.004940/0\&.004969/0\&.004998 sec out of 2
 + reclock_recd       MIN/AVG/MAX     0\&.000000/0\&.000000/0\&.000000 sec out of 0
 + call_latency       MIN/AVG/MAX     0\&.000006/0\&.000719/4\&.562991 sec out of 126626
 + childwrite_latency MIN/AVG/MAX     0\&.014527/0\&.014527/0\&.014527 sec out of 1
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.SS "CTDB version"
 +.PP
 +Version of the ctdb protocol used by the node\&.
 +.SS "Current time of statistics"
 +.PP
 +Time when the statistics are generated\&.
 +.PP
 +This is useful when collecting statistics output periodically for post\-processing\&.
 +.SS "Statistics collected since"
 +.PP
 +Time when ctdb was started or the last time statistics was reset\&. The output shows the duration and the timestamp\&.
 +.SS "num_clients"
 +.PP
 +Number of processes currently connected to CTDB\*(Aqs unix socket\&. This includes recovery daemon, ctdb tool and samba processes (smbd, winbindd)\&.
 +.SS "frozen"
 +.PP
 +1 if the the databases are currently frozen, 0 otherwise\&.
 +.SS "recovering"
 +.PP
 +1 if recovery is active, 0 otherwise\&.
 +.SS "num_recoveries"
 +.PP
 +Number of recoveries since the start of ctdb or since the last statistics reset\&.
 +.SS "client_packets_sent"
 +.PP
 +Number of packets sent to client processes via unix domain socket\&.
 +.SS "client_packets_recv"
 +.PP
 +Number of packets received from client processes via unix domain socket\&.
 +.SS "node_packets_sent"
 +.PP
 +Number of packets sent to the other nodes in the cluster via TCP\&.
 +.SS "node_packets_recv"
 +.PP
 +Number of packets received from the other nodes in the cluster via TCP\&.
 +.SS "keepalive_packets_sent"
 +.PP
 +Number of keepalive messages sent to other nodes\&.
 +.PP
 +CTDB periodically sends keepalive messages to other nodes\&. See
 +KeepaliveInterval
 +tunable in
 +\fBctdb-tunables\fR(7)
 +for more details\&.
 +.SS "keepalive_packets_recv"
 +.PP
 +Number of keepalive messages received from other nodes\&.
 +.SS "node"
 +.PP
 +This section lists various types of messages processed which originated from other nodes via TCP\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBreq_call\fR
 +.RS 4
 +.PP
 +Number of REQ_CALL messages from the other nodes\&.
 +.RE
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBreply_call\fR
 +.RS 4
 +.PP
 +Number of REPLY_CALL messages from the other nodes\&.
 +.RE
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBreq_dmaster\fR
 +.RS 4
 +.PP
 +Number of REQ_DMASTER messages from the other nodes\&.
 +.RE
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBreply_dmaster\fR
 +.RS 4
 +.PP
 +Number of REPLY_DMASTER messages from the other nodes\&.
 +.RE
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBreply_error\fR
 +.RS 4
 +.PP
 +Number of REPLY_ERROR messages from the other nodes\&.
 +.RE
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBreq_message\fR
 +.RS 4
 +.PP
 +Number of REQ_MESSAGE messages from the other nodes\&.
 +.RE
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBreq_control\fR
 +.RS 4
 +.PP
 +Number of REQ_CONTROL messages from the other nodes\&.
 +.RE
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBreply_control\fR
 +.RS 4
 +.PP
 +Number of REPLY_CONTROL messages from the other nodes\&.
 +.RE
 +.SS "client"
 +.PP
 +This section lists various types of messages processed which originated from clients via unix domain socket\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBreq_call\fR
 +.RS 4
 +.PP
 +Number of REQ_CALL messages from the clients\&.
 +.RE
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBreq_message\fR
 +.RS 4
 +.PP
 +Number of REQ_MESSAGE messages from the clients\&.
 +.RE
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBreq_control\fR
 +.RS 4
 +.PP
 +Number of REQ_CONTROL messages from the clients\&.
 +.RE
 +.SS "timeouts"
 +.PP
 +This section lists timeouts occurred when sending various messages\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBcall\fR
 +.RS 4
 +.PP
 +Number of timeouts for REQ_CALL messages\&.
 +.RE
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBcontrol\fR
 +.RS 4
 +.PP
 +Number of timeouts for REQ_CONTROL messages\&.
 +.RE
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBtraverse\fR
 +.RS 4
 +.PP
 +Number of timeouts for database traverse operations\&.
 +.RE
 +.SS "locks"
 +.PP
 +This section lists locking statistics\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBnum_calls\fR
 +.RS 4
 +.PP
 +Number of completed lock calls\&. This includes database locks and record locks\&.
 +.RE
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBnum_current\fR
 +.RS 4
 +.PP
 +Number of scheduled lock calls\&. This includes database locks and record locks\&.
 +.RE
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBnum_pending\fR
 +.RS 4
 +.PP
 +Number of queued lock calls\&. This includes database locks and record locks\&.
 +.RE
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBnum_failed\fR
 +.RS 4
 +.PP
 +Number of failed lock calls\&. This includes database locks and record locks\&.
 +.RE
 +.SS "total_calls"
 +.PP
 +Number of req_call messages processed from clients\&. This number should be same as client \-\-> req_call\&.
 +.SS "pending_calls"
 +.PP
 +Number of req_call messages which are currenly being processed\&. This number indicates the number of record migrations in flight\&.
 +.SS "childwrite_calls"
 +.PP
 +Number of record update calls\&. Record update calls are used to update a record under a transaction\&.
 +.SS "pending_childwrite_calls"
 +.PP
 +Number of record update calls currently active\&.
 +.SS "memory_used"
 +.PP
 +The amount of memory in bytes currently used by CTDB using talloc\&. This includes all the memory used for CTDB\*(Aqs internal data structures\&. This does not include the memory mapped TDB databases\&.
 +.SS "max_hop_count"
 +.PP
 +The maximum number of hops required for a record migration request to obtain the record\&. High numbers indicate record contention\&.
 +.SS "total_ro_delegations"
 +.PP
 +Number of readonly delegations created\&.
 +.SS "total_ro_revokes"
 +.PP
 +Number of readonly delegations that were revoked\&. The difference between total_ro_revokes and total_ro_delegations gives the number of currently active readonly delegations\&.
 +.SS "hop_count_buckets"
 +.PP
 +Distribution of migration requests based on hop counts values\&. Buckets are 1, < 4, < 8, < 16, < 32, < 64, < 128, < 256, < 512, ≥ 512\&.
 +.SS "lock_buckets"
 +.PP
 +Distribution of record lock requests based on time required to obtain locks\&. Buckets are < 1ms, < 10ms, < 100ms, < 1s, < 2s, < 4s, < 8s, < 16s, < 32s, < 64s, ≥ 64s\&.
 +.SS "locks_latency"
 +.PP
 +The minimum, the average and the maximum time (in seconds) required to obtain record locks\&.
 +.SS "reclock_ctdbd"
 +.PP
 +The minimum, the average and the maximum time (in seconds) required to check if recovery lock is still held by recovery daemon when recovery mode is changed\&. This check is done in ctdb daemon\&.
 +.SS "reclock_recd"
 +.PP
 +The minimum, the average and the maximum time (in seconds) required to check if recovery lock is still held by recovery daemon during recovery\&. This check is done in recovery daemon\&.
 +.SS "call_latency"
 +.PP
 +The minimum, the average and the maximum time (in seconds) required to process a REQ_CALL message from client\&. This includes the time required to migrate a record from remote node, if the record is not available on the local node\&.
 +.SS "childwrite_latency"
 +.PP
 +Default: 0
 +.PP
 +The minimum, the average and the maximum time (in seconds) required to update records under a transaction\&.
 +.SH "DATABASE STATISTICS"
 +.PP
 +CTDB maintains per database statistics about important operations\&. See the
 +\fBctdb\fR(1)
 +command
 +\fBdbstatistics\fR
 +for displaying database statistics\&.
 +.SS "Example: ctdb dbstatistics notify_index\&.tdb"
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +DB Statistics: notify_index\&.tdb
 + ro_delegations                     0
 + ro_revokes                         0
 + locks
 +     total                        131
 +     failed                         0
 +     current                        0
 +     pending                        0
 + hop_count_buckets: 9890 5454 26 1 0 0 0 0 0 0 0 0 0 0 0 0
 + lock_buckets: 4 117 10 0 0 0 0 0 0 0 0 0 0 0 0 0
 + locks_latency      MIN/AVG/MAX     0\&.000683/0\&.004198/0\&.014730 sec out of 131
 + Num Hot Keys:     3
 +     Count:7 Key:2f636c75737465726673
 +     Count:18 Key:2f636c757374657266732f64617461
 +     Count:7 Key:2f636c757374657266732f646174612f636c69656e7473
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.SS "DB Statistics"
 +.PP
 +Name of the database\&.
 +.SS "ro_delegations"
 +.PP
 +Number of readonly delegations created in the database\&.
 +.SS "ro_revokes"
 +.PP
 +Number of readonly delegations revoked\&. The difference in ro_delegations and ro_revokes indicates the currently active readonly delegations\&.
 +.SS "locks"
 +.PP
 +This section lists locking statistics\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBtotal\fR
 +.RS 4
 +.PP
 +Number of completed lock calls\&. This includes database locks and record locks\&.
 +.RE
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBfailed\fR
 +.RS 4
 +.PP
 +Number of failed lock calls\&. This includes database locks and record locks\&.
 +.RE
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBcurrent\fR
 +.RS 4
 +.PP
 +Number of scheduled lock calls\&. This includes database locks and record locks\&.
 +.RE
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBpending\fR
 +.RS 4
 +.PP
 +Number of queued lock calls\&. This includes database locks and record locks\&.
 +.RE
 +.SS "hop_count_buckets"
 +.PP
 +Distribution of migration requests based on hop counts values\&. Buckets are 1, < 4, < 8, < 16, < 32, < 64, < 128, < 256, < 512, ≥ 512\&.
 +.SS "lock_buckets"
 +.PP
 +Distribution of record lock requests based on time required to obtain locks\&. Buckets are < 1ms, < 10ms, < 100ms, < 1s, < 2s, < 4s, < 8s, < 16s, < 32s, < 64s, ≥ 64s\&.
 +.SS "locks_latency"
 +.PP
 +The minimum, the average and the maximum time (in seconds) required to obtain record locks\&.
 +.SS "Num Hot Keys"
 +.PP
 +Number of contended records determined by hop count\&. CTDB keeps track of top 10 hot records and the output shows hex encoded keys for the hot records\&.
 +.SH "SEE ALSO"
 +.PP
 +\fBctdb\fR(1),
 +\fBctdbd\fR(1),
 +\fBctdb-tunables\fR(7),
 +\m[blue]\fB\%http://ctdb.samba.org/\fR\m[]
 +.SH "AUTHOR"
 +.br
 +.PP
 +This documentation was written by Amitay Isaacs, Martin Schwenke
 +.SH "COPYRIGHT"
 +.br
 +Copyright \(co 2007 Andrew Tridgell, Ronnie Sahlberg
 +.br
 +.PP
 +This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version\&.
 +.PP
 +This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE\&. See the GNU General Public License for more details\&.
 +.PP
 +You should have received a copy of the GNU General Public License along with this program; if not, see
 +\m[blue]\fB\%http://www.gnu.org/licenses\fR\m[]\&.
 +.sp
diff --cc ctdb/doc/ctdb-statistics.7.html
index b30db18,0000000..3ee766a
mode 100644,000000..100644
--- a/ctdb/doc/ctdb-statistics.7.html
+++ b/ctdb/doc/ctdb-statistics.7.html
@@@ -1,264 -1,0 +1,264 @@@
- <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ctdb-statistics</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-statistics.7"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ctdb-statistics — CTDB statistics output</p></div><div class="refsect1"><a name="idp52593184"> [...]
++<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ctdb-statistics</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-statistics.7"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ctdb-statistics — CTDB statistics output</p></div><div class="refsect1"><a name="idp53041024"> [...]
 +      CTDB maintains information about various messages communicated
 +      and some of the important operations per node.  See the
 +      <span class="citerefentry"><span class="refentrytitle">ctdb</span>(1)</span> commands
 +      <span class="command"><strong>statistics</strong></span> and <span class="command"><strong>statisticsreset</strong></span>
 +      for displaying statistics.
-     </p><div class="refsect2"><a name="idp50959184"></a><h3>Example: ctdb statistics</h3><pre class="screen">
++    </p><div class="refsect2"><a name="idp50875296"></a><h3>Example: ctdb statistics</h3><pre class="screen">
 +CTDB version 1
 +Current time of statistics  :                Fri Sep 12 13:32:32 2014
 +Statistics collected since  : (000 01:49:20) Fri Sep 12 11:43:12 2014
 + num_clients                        6
 + frozen                             0
 + recovering                         0
 + num_recoveries                     2
 + client_packets_sent           281293
 + client_packets_recv           296317
 + node_packets_sent             452387
 + node_packets_recv             182394
 + keepalive_packets_sent          3927
 + keepalive_packets_recv          3928
 + node
 +     req_call                   48605
 +     reply_call                     1
 +     req_dmaster                23404
 +     reply_dmaster              24917
 +     reply_error                    0
 +     req_message                  958
 +     req_control               197513
 +     reply_control             153705
 + client
 +     req_call                  130866
 +     req_message                  770
 +     req_control               168921
 + timeouts
 +     call                           0
 +     control                        0
 +     traverse                       0
 + locks
 +     num_calls                    220
 +     num_current                    0
 +     num_pending                    0
 +     num_failed                     0
 + total_calls                   130866
 + pending_calls                      0
 + childwrite_calls                   1
 + pending_childwrite_calls             0
 + memory_used                   334490
 + max_hop_count                     18
 + total_ro_delegations               2
 + total_ro_revokes                   2
 + hop_count_buckets: 42816 5464 26 1 0 0 0 0 0 0 0 0 0 0 0 0
 + lock_buckets: 9 165 14 15 7 2 2 0 0 0 0 0 0 0 0 0
 + locks_latency      MIN/AVG/MAX     0.000685/0.160302/6.369342 sec out of 214
 + reclock_ctdbd      MIN/AVG/MAX     0.004940/0.004969/0.004998 sec out of 2
 + reclock_recd       MIN/AVG/MAX     0.000000/0.000000/0.000000 sec out of 0
 + call_latency       MIN/AVG/MAX     0.000006/0.000719/4.562991 sec out of 126626
 + childwrite_latency MIN/AVG/MAX     0.014527/0.014527/0.014527 sec out of 1
- 	</pre></div><div class="refsect2"><a name="idp50299696"></a><h3>CTDB version</h3><p>
++	</pre></div><div class="refsect2"><a name="idp53698272"></a><h3>CTDB version</h3><p>
 +        Version of the ctdb protocol used by the node.
-       </p></div><div class="refsect2"><a name="idp52535200"></a><h3>Current time of statistics</h3><p>
++      </p></div><div class="refsect2"><a name="idp53531952"></a><h3>Current time of statistics</h3><p>
 +        Time when the statistics are generated.
 +      </p><p>
 +        This is useful when collecting statistics output periodically
 +        for post-processing.
-       </p></div><div class="refsect2"><a name="idp52703200"></a><h3>Statistics collected since</h3><p>
++      </p></div><div class="refsect2"><a name="idp51198640"></a><h3>Statistics collected since</h3><p>
 +	Time when ctdb was started or the last time statistics was reset.
 +	The output shows the duration and the timestamp.
-       </p></div><div class="refsect2"><a name="idp53915040"></a><h3>num_clients</h3><p>
++      </p></div><div class="refsect2"><a name="idp53599296"></a><h3>num_clients</h3><p>
 +        Number of processes currently connected to CTDB's unix socket.
 +        This includes recovery daemon, ctdb tool and samba processes
 +        (smbd, winbindd).
-       </p></div><div class="refsect2"><a name="idp51935744"></a><h3>frozen</h3><p>
++      </p></div><div class="refsect2"><a name="idp54074992"></a><h3>frozen</h3><p>
 +	1 if the the databases are currently frozen, 0 otherwise.
-       </p></div><div class="refsect2"><a name="idp52761584"></a><h3>recovering</h3><p>
++      </p></div><div class="refsect2"><a name="idp50448784"></a><h3>recovering</h3><p>
 +	1 if recovery is active, 0 otherwise.
-       </p></div><div class="refsect2"><a name="idp49231152"></a><h3>num_recoveries</h3><p>
++      </p></div><div class="refsect2"><a name="idp52810576"></a><h3>num_recoveries</h3><p>
 +	Number of recoveries since the start of ctdb or since the last
 +	statistics reset.
-       </p></div><div class="refsect2"><a name="idp49232448"></a><h3>client_packets_sent</h3><p>
++      </p></div><div class="refsect2"><a name="idp52880800"></a><h3>client_packets_sent</h3><p>
 +	Number of packets sent to client processes via unix domain socket.
-       </p></div><div class="refsect2"><a name="idp49233632"></a><h3>client_packets_recv</h3><p>
++      </p></div><div class="refsect2"><a name="idp53416128"></a><h3>client_packets_recv</h3><p>
 +	Number of packets received from client processes via unix domain socket.
-       </p></div><div class="refsect2"><a name="idp50191056"></a><h3>node_packets_sent</h3><p>
++      </p></div><div class="refsect2"><a name="idp54195824"></a><h3>node_packets_sent</h3><p>
 +	Number of packets sent to the other nodes in the cluster via TCP.
-       </p></div><div class="refsect2"><a name="idp50192240"></a><h3>node_packets_recv</h3><p>
++      </p></div><div class="refsect2"><a name="idp52658384"></a><h3>node_packets_recv</h3><p>
 +	Number of packets received from the other nodes in the cluster via TCP.
-       </p></div><div class="refsect2"><a name="idp50193424"></a><h3>keepalive_packets_sent</h3><p>
++      </p></div><div class="refsect2"><a name="idp53067152"></a><h3>keepalive_packets_sent</h3><p>
 +	Number of keepalive messages sent to other nodes.
 +      </p><p>
 +	CTDB periodically sends keepalive messages to other nodes.
 +	See <em class="citetitle">KeepaliveInterval</em> tunable in
 +	<span class="citerefentry"><span class="refentrytitle">ctdb-tunables</span>(7)</span> for more details.
-       </p></div><div class="refsect2"><a name="idp50196416"></a><h3>keepalive_packets_recv</h3><p>
++      </p></div><div class="refsect2"><a name="idp49083072"></a><h3>keepalive_packets_recv</h3><p>
 +	Number of keepalive messages received from other nodes.
-       </p></div><div class="refsect2"><a name="idp50197600"></a><h3>node</h3><p>
++      </p></div><div class="refsect2"><a name="idp49084256"></a><h3>node</h3><p>
 +	This section lists various types of messages processed which
 +	originated from other nodes via TCP.
-       </p><div class="refsect3"><a name="idp50198784"></a><h4>req_call</h4><p>
++      </p><div class="refsect3"><a name="idp49004400"></a><h4>req_call</h4><p>
 +        Number of REQ_CALL messages from the other nodes.
-       </p></div><div class="refsect3"><a name="idp50199968"></a><h4>reply_call</h4><p>
++      </p></div><div class="refsect3"><a name="idp49005584"></a><h4>reply_call</h4><p>
 +        Number of REPLY_CALL messages from the other nodes.
-       </p></div><div class="refsect3"><a name="idp50201152"></a><h4>req_dmaster</h4><p>
++      </p></div><div class="refsect3"><a name="idp49006768"></a><h4>req_dmaster</h4><p>
 +        Number of REQ_DMASTER messages from the other nodes.
-       </p></div><div class="refsect3"><a name="idp50202336"></a><h4>reply_dmaster</h4><p>
++      </p></div><div class="refsect3"><a name="idp49007952"></a><h4>reply_dmaster</h4><p>
 +        Number of REPLY_DMASTER messages from the other nodes.
-       </p></div><div class="refsect3"><a name="idp50203520"></a><h4>reply_error</h4><p>
++      </p></div><div class="refsect3"><a name="idp49009136"></a><h4>reply_error</h4><p>
 +        Number of REPLY_ERROR messages from the other nodes.
-       </p></div><div class="refsect3"><a name="idp50204704"></a><h4>req_message</h4><p>
++      </p></div><div class="refsect3"><a name="idp49010320"></a><h4>req_message</h4><p>
 +        Number of REQ_MESSAGE messages from the other nodes.
-       </p></div><div class="refsect3"><a name="idp50205888"></a><h4>req_control</h4><p>
++      </p></div><div class="refsect3"><a name="idp49011504"></a><h4>req_control</h4><p>
 +        Number of REQ_CONTROL messages from the other nodes.
-       </p></div><div class="refsect3"><a name="idp50207152"></a><h4>reply_control</h4><p>
++      </p></div><div class="refsect3"><a name="idp49134368"></a><h4>reply_control</h4><p>
 +        Number of REPLY_CONTROL messages from the other nodes.
-       </p></div></div><div class="refsect2"><a name="idp49112400"></a><h3>client</h3><p>
++      </p></div></div><div class="refsect2"><a name="idp49135680"></a><h3>client</h3><p>
 +	This section lists various types of messages processed which
 +	originated from clients via unix domain socket.
-       </p><div class="refsect3"><a name="idp49113584"></a><h4>req_call</h4><p>
++      </p><div class="refsect3"><a name="idp49136864"></a><h4>req_call</h4><p>
 +        Number of REQ_CALL messages from the clients.
-       </p></div><div class="refsect3"><a name="idp49114848"></a><h4>req_message</h4><p>
++      </p></div><div class="refsect3"><a name="idp49138048"></a><h4>req_message</h4><p>
 +        Number of REQ_MESSAGE messages from the clients.
-       </p></div><div class="refsect3"><a name="idp49116112"></a><h4>req_control</h4><p>
++      </p></div><div class="refsect3"><a name="idp49139232"></a><h4>req_control</h4><p>
 +        Number of REQ_CONTROL messages from the clients.
-       </p></div></div><div class="refsect2"><a name="idp49117504"></a><h3>timeouts</h3><p>
++      </p></div></div><div class="refsect2"><a name="idp49140544"></a><h3>timeouts</h3><p>
 +	This section lists timeouts occurred when sending various messages.
-       </p><div class="refsect3"><a name="idp49118656"></a><h4>call</h4><p>
++      </p><div class="refsect3"><a name="idp49141696"></a><h4>call</h4><p>
 +        Number of timeouts for REQ_CALL messages.
-       </p></div><div class="refsect3"><a name="idp49119920"></a><h4>control</h4><p>
++      </p></div><div class="refsect3"><a name="idp49142880"></a><h4>control</h4><p>
 +        Number of timeouts for REQ_CONTROL messages.
-       </p></div><div class="refsect3"><a name="idp49121184"></a><h4>traverse</h4><p>
++      </p></div><div class="refsect3"><a name="idp49144064"></a><h4>traverse</h4><p>
 +        Number of timeouts for database traverse operations.
-       </p></div></div><div class="refsect2"><a name="idp49122576"></a><h3>locks</h3><p>
++      </p></div></div><div class="refsect2"><a name="idp49145456"></a><h3>locks</h3><p>
 +	This section lists locking statistics.
-       </p><div class="refsect3"><a name="idp49123632"></a><h4>num_calls</h4><p>
++      </p><div class="refsect3"><a name="idp49146512"></a><h4>num_calls</h4><p>
 +        Number of completed lock calls.  This includes database locks
 +        and record locks.
-       </p></div><div class="refsect3"><a name="idp49124928"></a><h4>num_current</h4><p>
++      </p></div><div class="refsect3"><a name="idp49147696"></a><h4>num_current</h4><p>
 +        Number of scheduled lock calls.  This includes database locks
 +        and record locks.
-       </p></div><div class="refsect3"><a name="idp49126224"></a><h4>num_pending</h4><p>
++      </p></div><div class="refsect3"><a name="idp49148992"></a><h4>num_pending</h4><p>
 +        Number of queued lock calls.  This includes database locks and
 +        record locks.
-       </p></div><div class="refsect3"><a name="idp49127520"></a><h4>num_failed</h4><p>
++      </p></div><div class="refsect3"><a name="idp48962640"></a><h4>num_failed</h4><p>
 +        Number of failed lock calls.  This includes database locks and
 +        record locks.
-       </p></div></div><div class="refsect2"><a name="idp49133712"></a><h3>total_calls</h3><p>
++      </p></div></div><div class="refsect2"><a name="idp48964064"></a><h3>total_calls</h3><p>
 +	Number of req_call messages processed from clients.  This number
 +	should be same as client --> req_call.
-       </p></div><div class="refsect2"><a name="idp49135024"></a><h3>pending_calls</h3><p>
++      </p></div><div class="refsect2"><a name="idp48965376"></a><h3>pending_calls</h3><p>
 +	Number of req_call messages which are currenly being processed.
 +	This number indicates the number of record migrations in flight.
-       </p></div><div class="refsect2"><a name="idp49136368"></a><h3>childwrite_calls</h3><p>
++      </p></div><div class="refsect2"><a name="idp48966720"></a><h3>childwrite_calls</h3><p>
 +	Number of record update calls.	Record update calls are used to
 +	update a record under a transaction.
-       </p></div><div class="refsect2"><a name="idp49137680"></a><h3>pending_childwrite_calls</h3><p>
++      </p></div><div class="refsect2"><a name="idp48968032"></a><h3>pending_childwrite_calls</h3><p>
 +	Number of record update calls currently active.
-       </p></div><div class="refsect2"><a name="idp49138960"></a><h3>memory_used</h3><p>
++      </p></div><div class="refsect2"><a name="idp48969264"></a><h3>memory_used</h3><p>
 +	The amount of memory in bytes currently used by CTDB using
 +	talloc.  This includes all the memory used for CTDB's internal
 +	data structures.  This does not include the memory mapped TDB
 +	databases.
-       </p></div><div class="refsect2"><a name="idp49140368"></a><h3>max_hop_count</h3><p>
++      </p></div><div class="refsect2"><a name="idp48970672"></a><h3>max_hop_count</h3><p>
 +	The maximum number of hops required for a record migration request
 +	to obtain the record.  High numbers indicate record contention.
-       </p></div><div class="refsect2"><a name="idp49141712"></a><h3>total_ro_delegations</h3><p>
++      </p></div><div class="refsect2"><a name="idp48972016"></a><h3>total_ro_delegations</h3><p>
 +	Number of readonly delegations created.
-       </p></div><div class="refsect2"><a name="idp49142896"></a><h3>total_ro_revokes</h3><p>
++      </p></div><div class="refsect2"><a name="idp48973200"></a><h3>total_ro_revokes</h3><p>
 +	Number of readonly delegations that were revoked.  The difference
 +	between total_ro_revokes and total_ro_delegations gives the
 +	number of currently active readonly delegations.
-       </p></div><div class="refsect2"><a name="idp49144288"></a><h3>hop_count_buckets</h3><p>
++      </p></div><div class="refsect2"><a name="idp48974592"></a><h3>hop_count_buckets</h3><p>
 +	Distribution of migration requests based on hop counts values.
 +	Buckets are 1, < 4, < 8, < 16, < 32, < 64, <
 +	128, < 256, < 512, ≥ 512.
-       </p></div><div class="refsect2"><a name="idp49145712"></a><h3>lock_buckets</h3><p>
++      </p></div><div class="refsect2"><a name="idp48975856"></a><h3>lock_buckets</h3><p>
 +	Distribution of record lock requests based on time required to
 +	obtain locks.  Buckets are < 1ms, < 10ms, < 100ms,
 +	< 1s, < 2s, < 4s, < 8s, < 16s, < 32s, <
 +	64s, ≥ 64s.
-       </p></div><div class="refsect2"><a name="idp49147104"></a><h3>locks_latency</h3><p>
++      </p></div><div class="refsect2"><a name="idp48977664"></a><h3>locks_latency</h3><p>
 +	The minimum, the average and the maximum time (in seconds)
 +	required to obtain record locks.
-       </p></div><div class="refsect2"><a name="idp49148368"></a><h3>reclock_ctdbd</h3><p>
++      </p></div><div class="refsect2"><a name="idp48978928"></a><h3>reclock_ctdbd</h3><p>
 +	The minimum, the average and the maximum time (in seconds)
 +	required to check if recovery lock is still held by recovery
 +	daemon when recovery mode is changed.  This check is done in ctdb daemon.
-       </p></div><div class="refsect2"><a name="idp49149744"></a><h3>reclock_recd</h3><p>
++      </p></div><div class="refsect2"><a name="idp48980304"></a><h3>reclock_recd</h3><p>
 +        The minimum, the average and the maximum time (in seconds)
 +        required to check if recovery lock is still held by recovery
 +        daemon during recovery.  This check is done in recovery daemon.
-       </p></div><div class="refsect2"><a name="idp49151888"></a><h3>call_latency</h3><p>
++      </p></div><div class="refsect2"><a name="idp48990560"></a><h3>call_latency</h3><p>
 +	The minimum, the average and the maximum time (in seconds) required
 +	to process a REQ_CALL message from client.  This includes the time
 +	required to migrate a record from remote node, if the record is
 +	not available on the local node.
-       </p></div><div class="refsect2"><a name="idp49153328"></a><h3>childwrite_latency</h3><p>Default: 0</p><p>
++      </p></div><div class="refsect2"><a name="idp48992000"></a><h3>childwrite_latency</h3><p>Default: 0</p><p>
 +	The minimum, the average and the maximum time (in seconds)
 +	required to update records under a transaction.
-       </p></div></div><div class="refsect1"><a name="idp49155184"></a><h2>DATABASE STATISTICS</h2><p>
++      </p></div></div><div class="refsect1"><a name="idp48993856"></a><h2>DATABASE STATISTICS</h2><p>
 +      CTDB maintains per database statistics about important operations.
 +      See the <span class="citerefentry"><span class="refentrytitle">ctdb</span>(1)</span> command
 +      <span class="command"><strong>dbstatistics</strong></span> for displaying database statistics.
-     </p><div class="refsect2"><a name="idp55072880"></a><h3>Example: ctdb dbstatistics notify_index.tdb</h3><pre class="screen">
++    </p><div class="refsect2"><a name="idp48983600"></a><h3>Example: ctdb dbstatistics notify_index.tdb</h3><pre class="screen">
 +DB Statistics: notify_index.tdb
 + ro_delegations                     0
 + ro_revokes                         0
 + locks
 +     total                        131
 +     failed                         0
 +     current                        0
 +     pending                        0
 + hop_count_buckets: 9890 5454 26 1 0 0 0 0 0 0 0 0 0 0 0 0
 + lock_buckets: 4 117 10 0 0 0 0 0 0 0 0 0 0 0 0 0
 + locks_latency      MIN/AVG/MAX     0.000683/0.004198/0.014730 sec out of 131
 + Num Hot Keys:     3
 +     Count:7 Key:2f636c75737465726673
 +     Count:18 Key:2f636c757374657266732f64617461
 +     Count:7 Key:2f636c757374657266732f646174612f636c69656e7473
- 	</pre></div><div class="refsect2"><a name="idp55074912"></a><h3>DB Statistics</h3><p>
++	</pre></div><div class="refsect2"><a name="idp48985664"></a><h3>DB Statistics</h3><p>
 +	Name of the database.
-       </p></div><div class="refsect2"><a name="idp55076064"></a><h3>ro_delegations</h3><p>
++      </p></div><div class="refsect2"><a name="idp48986848"></a><h3>ro_delegations</h3><p>
 +	Number of readonly delegations created in the database.
-       </p></div><div class="refsect2"><a name="idp55077216"></a><h3>ro_revokes</h3><p>
++      </p></div><div class="refsect2"><a name="idp48988032"></a><h3>ro_revokes</h3><p>
 +	Number of readonly delegations revoked.  The difference in
 +	ro_delegations and ro_revokes indicates the currently active
 +	readonly delegations.
-       </p></div><div class="refsect2"><a name="idp55078544"></a><h3>locks</h3><p>
++      </p></div><div class="refsect2"><a name="idp48989392"></a><h3>locks</h3><p>
 +	This section lists locking statistics.
-       </p><div class="refsect3"><a name="idp55079568"></a><h4>total</h4><p>
++      </p><div class="refsect3"><a name="idp54477424"></a><h4>total</h4><p>
 +        Number of completed lock calls.  This includes database locks
 +        and record locks.
-       </p></div><div class="refsect3"><a name="idp55080832"></a><h4>failed</h4><p>
++      </p></div><div class="refsect3"><a name="idp54478688"></a><h4>failed</h4><p>
 +        Number of failed lock calls.  This includes database locks and
 +        record locks.
-       </p></div><div class="refsect3"><a name="idp55082096"></a><h4>current</h4><p>
++      </p></div><div class="refsect3"><a name="idp54479952"></a><h4>current</h4><p>
 +        Number of scheduled lock calls.  This includes database locks
 +        and record locks.
-       </p></div><div class="refsect3"><a name="idp55083360"></a><h4>pending</h4><p>
++      </p></div><div class="refsect3"><a name="idp54481216"></a><h4>pending</h4><p>
 +        Number of queued lock calls.  This includes database locks and
 +        record locks.
-       </p></div></div><div class="refsect2"><a name="idp55084752"></a><h3>hop_count_buckets</h3><p>
++      </p></div></div><div class="refsect2"><a name="idp54482608"></a><h3>hop_count_buckets</h3><p>
 +	Distribution of migration requests based on hop counts values.
 +	Buckets are 1, < 4, < 8, < 16, < 32, < 64, <
 +	128, < 256, < 512, ≥ 512.
-       </p></div><div class="refsect2"><a name="idp55086112"></a><h3>lock_buckets</h3><p>
++      </p></div><div class="refsect2"><a name="idp54483968"></a><h3>lock_buckets</h3><p>
 +	Distribution of record lock requests based on time required to
 +	obtain locks.  Buckets are < 1ms, < 10ms, < 100ms,
 +	< 1s, < 2s, < 4s, < 8s, < 16s, < 32s, <
 +	64s, ≥ 64s.
-       </p></div><div class="refsect2"><a name="idp55087536"></a><h3>locks_latency</h3><p>
++      </p></div><div class="refsect2"><a name="idp54485392"></a><h3>locks_latency</h3><p>
 +	The minimum, the average and the maximum time (in seconds)
 +	required to obtain record locks.
-       </p></div><div class="refsect2"><a name="idp55088800"></a><h3>Num Hot Keys</h3><p>
++      </p></div><div class="refsect2"><a name="idp54486656"></a><h3>Num Hot Keys</h3><p>
 +        Number of contended records determined by hop count.  CTDB keeps
 +        track of top 10 hot records and the output shows hex encoded
 +        keys for the hot records.
-       </p></div></div><div class="refsect1"><a name="idp55090272"></a><h2>SEE ALSO</h2><p>
++      </p></div></div><div class="refsect1"><a name="idp54488128"></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>,
 +
 +      <span class="citerefentry"><span class="refentrytitle">ctdb-tunables</span>(7)</span>,
 +
 +      <a class="ulink" href="http://ctdb.samba.org/" target="_top">http://ctdb.samba.org/</a>
 +    </p></div></div></body></html>
diff --cc ctdb/doc/ctdb-tunables.7
index 999e90a,0000000..f830b02
mode 100644,000000..100644
--- a/ctdb/doc/ctdb-tunables.7
+++ b/ctdb/doc/ctdb-tunables.7
@@@ -1,359 -1,0 +1,359 @@@
 +'\" t
 +.\"     Title: ctdb-tunables
 +.\"    Author: 
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 09/08/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: CTDB - clustered TDB database
 +.\"    Source: ctdb
 +.\"  Language: English
 +.\"
- .TH "CTDB\-TUNABLES" "7" "09/08/2015" "ctdb" "CTDB \- clustered TDB database"
++.TH "CTDB\-TUNABLES" "7" "12/10/2015" "ctdb" "CTDB \- clustered TDB database"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +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,
 +\fBsetvar\fR
 +and
 +\fBgetvar\fR
 +commands for more details\&.
 +.SS "MaxRedirectCount"
 +.PP
 +Default: 3
 +.PP
 +If we are not the DMASTER and need to fetch a record across the network we first send the request to the LMASTER after which the record is passed onto the current DMASTER\&. If the DMASTER changes before the request has reached that node, the request will be passed onto the "next" DMASTER\&. For very hot records that migrate rapidly across the cluster this can cause a request to "chase" the record for many hops before it catches up with the record\&. this is how many hops we allow tryin [...]
 +.PP
 +When chasing a record, this is how many hops we will chase the record for before going back to the LMASTER to ask for new guidance\&.
 +.SS "SeqnumInterval"
 +.PP
 +Default: 1000
 +.PP
 +Some databases have seqnum tracking enabled, so that samba will be able to detect asynchronously when there has been updates to the database\&. Everytime a database is updated its sequence number is increased\&.
 +.PP
 +This tunable is used to specify in \*(Aqms\*(Aq how frequently ctdb will send out updates to remote nodes to inform them that the sequence number is increased\&.
 +.SS "ControlTimeout"
 +.PP
 +Default: 60
 +.PP
 +This is the default setting for timeout for when sending a control message to either the local or a remote ctdb daemon\&.
 +.SS "TraverseTimeout"
 +.PP
 +Default: 20
 +.PP
 +This setting controls how long we allow a traverse process to run\&. After this timeout triggers, the main ctdb daemon will abort the traverse if it has not yet finished\&.
 +.SS "KeepaliveInterval"
 +.PP
 +Default: 5
 +.PP
 +How often in seconds should the nodes send keepalives to eachother\&.
 +.SS "KeepaliveLimit"
 +.PP
 +Default: 5
 +.PP
 +After how many keepalive intervals without any traffic should a node wait until marking the peer as DISCONNECTED\&.
 +.PP
 +If a node has hung, it can thus take KeepaliveInterval*(KeepaliveLimit+1) seconds before we determine that the node is DISCONNECTED and that we require a recovery\&. This limitshould not be set too high since we want a hung node to be detectec, and expunged from the cluster well before common CIFS timeouts (45\-90 seconds) kick in\&.
 +.SS "RecoverTimeout"
 +.PP
 +Default: 20
 +.PP
 +This is the default setting for timeouts for controls when sent from the recovery daemon\&. We allow longer control timeouts from the recovery daemon than from normal use since the recovery dameon often use controls that can take a lot longer than normal controls\&.
 +.SS "RecoverInterval"
 +.PP
 +Default: 1
 +.PP
 +How frequently in seconds should the recovery daemon perform the consistency checks that determine if we need to perform a recovery or not\&.
 +.SS "ElectionTimeout"
 +.PP
 +Default: 3
 +.PP
 +When electing a new recovery master, this is how many seconds we allow the election to take before we either deem the election finished or we fail the election and start a new one\&.
 +.SS "TakeoverTimeout"
 +.PP
 +Default: 9
 +.PP
 +This is how many seconds we allow controls to take for IP failover events\&.
 +.SS "MonitorInterval"
 +.PP
 +Default: 15
 +.PP
 +How often should ctdb run the event scripts to check for a nodes health\&.
 +.SS "TickleUpdateInterval"
 +.PP
 +Default: 20
 +.PP
 +How often will ctdb record and store the "tickle" information used to kickstart stalled tcp connections after a recovery\&.
 +.SS "EventScriptTimeout"
 +.PP
 +Default: 20
 +.PP
 +How long should ctdb let an event script run before aborting it and marking the node unhealthy\&.
 +.SS "EventScriptTimeoutCount"
 +.PP
 +Default: 1
 +.PP
 +How many events in a row needs to timeout before we flag the node UNHEALTHY\&. This setting is useful if your scripts can not be written so that they do not hang for benign reasons\&.
 +.SS "EventScriptUnhealthyOnTimeout"
 +.PP
 +Default: 0
 +.PP
 +This setting can be be used to make ctdb never become UNHEALTHY if your eventscripts keep hanging/timing out\&.
 +.SS "RecoveryGracePeriod"
 +.PP
 +Default: 120
 +.PP
 +During recoveries, if a node has not caused recovery failures during the last grace period, any records of transgressions that the node has caused recovery failures will be forgiven\&. This resets the ban\-counter back to zero for that node\&.
 +.SS "RecoveryBanPeriod"
 +.PP
 +Default: 300
 +.PP
 +If a node becomes banned causing repetitive recovery failures\&. The node will eventually become banned from the cluster\&. This controls how long the culprit node will be banned from the cluster before it is allowed to try to join the cluster again\&. Don\*(Aqt set to small\&. A node gets banned for a reason and it is usually due to real problems with the node\&.
 +.SS "DatabaseHashSize"
 +.PP
 +Default: 100001
 +.PP
 +Size of the hash chains for the local store of the tdbs that ctdb manages\&.
 +.SS "DatabaseMaxDead"
 +.PP
 +Default: 5
 +.PP
 +How many dead records per hashchain in the TDB database do we allow before the freelist needs to be processed\&.
 +.SS "RerecoveryTimeout"
 +.PP
 +Default: 10
 +.PP
 +Once a recovery has completed, no additional recoveries are permitted until this timeout has expired\&.
 +.SS "EnableBans"
 +.PP
 +Default: 1
 +.PP
 +When set to 0, this disables BANNING completely in the cluster and thus nodes can not get banned, even it they break\&. Don\*(Aqt set to 0 unless you know what you are doing\&. You should set this to the same value on all nodes to avoid unexpected behaviour\&.
 +.SS "DeterministicIPs"
 +.PP
 +Default: 0
 +.PP
 +When enabled, this tunable makes ctdb try to keep public IP addresses locked to specific nodes as far as possible\&. This makes it easier for debugging since you can know that as long as all nodes are healthy public IP X will always be hosted by node Y\&.
 +.PP
 +The cost of using deterministic IP address assignment is that it disables part of the logic where ctdb tries to reduce the number of public IP assignment changes in the cluster\&. This tunable may increase the number of IP failover/failbacks that are performed on the cluster by a small margin\&.
 +.SS "LCP2PublicIPs"
 +.PP
 +Default: 1
 +.PP
 +When enabled this switches ctdb to use the LCP2 ip allocation algorithm\&.
 +.SS "ReclockPingPeriod"
 +.PP
 +Default: x
 +.PP
 +Obsolete
 +.SS "NoIPFailback"
 +.PP
 +Default: 0
 +.PP
 +When set to 1, ctdb will not perform failback of IP addresses when a node becomes healthy\&. Ctdb WILL perform failover of public IP addresses when a node becomes UNHEALTHY, but when the node becomes HEALTHY again, ctdb will not fail the addresses back\&.
 +.PP
 +Use with caution! Normally when a node becomes available to the cluster ctdb will try to reassign public IP addresses onto the new node as a way to distribute the workload evenly across the clusternode\&. Ctdb tries to make sure that all running nodes have approximately the same number of public addresses it hosts\&.
 +.PP
 +When you enable this tunable, CTDB will no longer attempt to rebalance the cluster by failing IP addresses back to the new nodes\&. An unbalanced cluster will therefore remain unbalanced until there is manual intervention from the administrator\&. When this parameter is set, you can manually fail public IP addresses over to the new node(s) using the \*(Aqctdb moveip\*(Aq command\&.
 +.SS "DisableIPFailover"
 +.PP
 +Default: 0
 +.PP
 +When enabled, ctdb will not perform failover or failback\&. Even if a node fails while holding public IPs, ctdb will not recover the IPs or assign them to another node\&.
 +.PP
 +When you enable this tunable, CTDB will no longer attempt to recover the cluster by failing IP addresses over to other nodes\&. This leads to a service outage until the administrator has manually performed failover to replacement nodes using the \*(Aqctdb moveip\*(Aq command\&.
 +.SS "NoIPTakeover"
 +.PP
 +Default: 0
 +.PP
 +When set to 1, ctdb will not allow IP addresses to be failed over onto this node\&. Any IP addresses that the node currently hosts will remain on the node but no new IP addresses can be failed over to the node\&.
 +.SS "NoIPHostOnAllDisabled"
 +.PP
 +Default: 0
 +.PP
 +If no nodes are healthy then by default ctdb will happily host public IPs on disabled (unhealthy or administratively disabled) nodes\&. This can cause problems, for example if the underlying cluster filesystem is not mounted\&. When set to 1 on a node and that node is disabled it, any IPs hosted by this node will be released and the node will not takeover any IPs until it is no longer disabled\&.
 +.SS "DBRecordCountWarn"
 +.PP
 +Default: 100000
 +.PP
 +When set to non\-zero, ctdb will log a warning when we try to recover a database with more than this many records\&. This will produce a warning if a database grows uncontrollably with orphaned records\&.
 +.SS "DBRecordSizeWarn"
 +.PP
 +Default: 10000000
 +.PP
 +When set to non\-zero, ctdb will log a warning when we try to recover a database where a single record is bigger than this\&. This will produce a warning if a database record grows uncontrollably with orphaned sub\-records\&.
 +.SS "DBSizeWarn"
 +.PP
 +Default: 1000000000
 +.PP
 +When set to non\-zero, ctdb will log a warning when we try to recover a database bigger than this\&. This will produce a warning if a database grows uncontrollably\&.
 +.SS "VerboseMemoryNames"
 +.PP
 +Default: 0
 +.PP
 +This feature consumes additional memory\&. when used the talloc library will create more verbose names for all talloc allocated objects\&.
 +.SS "RecdPingTimeout"
 +.PP
 +Default: 60
 +.PP
 +If the main dameon has not heard a "ping" from the recovery dameon for this many seconds, the main dameon will log a message that the recovery daemon is potentially hung\&.
 +.SS "RecdFailCount"
 +.PP
 +Default: 10
 +.PP
 +If the recovery daemon has failed to ping the main dameon for this many consecutive intervals, the main daemon will consider the recovery daemon as hung and will try to restart it to recover\&.
 +.SS "LogLatencyMs"
 +.PP
 +Default: 0
 +.PP
 +When set to non\-zero, this will make the main daemon log any operation that took longer than this value, in \*(Aqms\*(Aq, to complete\&. These include "how long time a lockwait child process needed", "how long time to write to a persistent database" but also "how long did it take to get a response to a CALL from a remote node"\&.
 +.SS "RecLockLatencyMs"
 +.PP
 +Default: 1000
 +.PP
 +When using a reclock file for split brain prevention, if set to non\-zero this tunable will make the recovery dameon log a message if the fcntl() call to lock/testlock the recovery file takes longer than this number of ms\&.
 +.SS "RecoveryDropAllIPs"
 +.PP
 +Default: 120
 +.PP
 +If we have been stuck in recovery, or stopped, or banned, mode for this many seconds we will force drop all held public addresses\&.
 +.SS "VacuumInterval"
 +.PP
 +Default: 10
 +.PP
 +Periodic interval in seconds when vacuuming is triggered for volatile databases\&.
 +.SS "VacuumMaxRunTime"
 +.PP
 +Default: 120
 +.PP
 +The maximum time in seconds for which the vacuuming process is allowed to run\&. If vacuuming process takes longer than this value, then the vacuuming process is terminated\&.
 +.SS "RepackLimit"
 +.PP
 +Default: 10000
 +.PP
 +During vacuuming, if the number of freelist records are more than
 +\fIRepackLimit\fR, then databases are repacked to get rid of the freelist records to avoid fragmentation\&.
 +.PP
 +Databases are repacked only if both
 +\fIRepackLimit\fR
 +and
 +\fIVacuumLimit\fR
 +are exceeded\&.
 +.SS "VacuumLimit"
 +.PP
 +Default: 5000
 +.PP
 +During vacuuming, if the number of deleted records are more than
 +\fIVacuumLimit\fR, then databases are repacked to avoid fragmentation\&.
 +.PP
 +Databases are repacked only if both
 +\fIRepackLimit\fR
 +and
 +\fIVacuumLimit\fR
 +are exceeded\&.
 +.SS "VacuumFastPathCount"
 +.PP
 +Default: 60
 +.PP
 +When a record is deleted, it is marked for deletion during vacuuming\&. Vacuuming process usually processes this list to purge the records from the database\&. If the number of records marked for deletion are more than VacuumFastPathCount, then vacuuming process will scan the complete database for empty records instead of using the list of records marked for deletion\&.
 +.SS "DeferredAttachTO"
 +.PP
 +Default: 120
 +.PP
 +When databases are frozen we do not allow clients to attach to the databases\&. Instead of returning an error immediately to the application the attach request from the client is deferred until the database becomes available again at which stage we respond to the client\&.
 +.PP
 +This timeout controls how long we will defer the request from the client before timing it out and returning an error to the client\&.
 +.SS "HopcountMakeSticky"
 +.PP
 +Default: 50
 +.PP
 +If the database is set to \*(AqSTICKY\*(Aq mode, using the \*(Aqctdb setdbsticky\*(Aq command, any record that is seen as very hot and migrating so fast that hopcount surpasses 50 is set to become a STICKY record for StickyDuration seconds\&. This means that after each migration the record will be kept on the node and prevented from being migrated off the node\&.
 +.PP
 +This setting allows one to try to identify such records and stop them from migrating across the cluster so fast\&. This will improve performance for certain workloads, such as locking\&.tdb if many clients are opening/closing the same file concurrently\&.
 +.SS "StickyDuration"
 +.PP
 +Default: 600
 +.PP
 +Once a record has been found to be fetch\-lock hot and has been flagged to become STICKY, this is for how long, in seconds, the record will be flagged as a STICKY record\&.
 +.SS "StickyPindown"
 +.PP
 +Default: 200
 +.PP
 +Once a STICKY record has been migrated onto a node, it will be pinned down on that node for this number of ms\&. Any request from other nodes to migrate the record off the node will be deferred until the pindown timer expires\&.
 +.SS "StatHistoryInterval"
 +.PP
 +Default: 1
 +.PP
 +Granularity of the statistics collected in the statistics history\&.
 +.SS "AllowClientDBAttach"
 +.PP
 +Default: 1
 +.PP
 +When set to 0, clients are not allowed to attach to any databases\&. This can be used to temporarily block any new processes from attaching to and accessing the databases\&.
 +.SS "RecoverPDBBySeqNum"
 +.PP
 +Default: 1
 +.PP
 +When set to zero, database recovery for persistent databases is record\-by\-record and recovery process simply collects the most recent version of every individual record\&.
 +.PP
 +When set to non\-zero, persistent databases will instead be recovered as a whole db and not by individual records\&. The node that contains the highest value stored in the record "__db_sequence_number__" is selected and the copy of that nodes database is used as the recovered database\&.
 +.PP
 +By default, recovery of persistent databses is done using __db_sequence_number__ record\&.
 +.SS "FetchCollapse"
 +.PP
 +Default: 1
 +.PP
 +When many clients across many nodes try to access the same record at the same time this can lead to a fetch storm where the record becomes very active and bounces between nodes very fast\&. This leads to high CPU utilization of the ctdbd daemon, trying to bounce that record around very fast, and poor performance\&.
 +.PP
 +This parameter is used to activate a fetch\-collapse\&. A fetch\-collapse is when we track which records we have requests in flight so that we only keep one request in flight from a certain node, even if multiple smbd processes are attemtping to fetch the record at the same time\&. This can improve performance and reduce CPU utilization for certain workloads\&.
 +.PP
 +This timeout controls if we should collapse multiple fetch operations of the same record into a single request and defer all duplicates or not\&.
 +.SS "Samba3AvoidDeadlocks"
 +.PP
 +Default: 0
 +.PP
 +Enable code that prevents deadlocks with Samba (only for Samba 3\&.x)\&.
 +.PP
 +This should be set to 1 when using Samba version 3\&.x to enable special code in CTDB to avoid deadlock with Samba version 3\&.x\&. This code is not required for Samba version 4\&.x and must not be enabled for Samba 4\&.x\&.
 +.SH "SEE ALSO"
 +.PP
 +\fBctdb\fR(1),
 +\fBctdbd\fR(1),
 +\fBctdbd.conf\fR(5),
 +\fBctdb\fR(7),
 +\m[blue]\fB\%http://ctdb.samba.org/\fR\m[]
 +.SH "AUTHOR"
 +.br
 +.PP
 +This documentation was written by Ronnie Sahlberg, Amitay Isaacs, Martin Schwenke
 +.SH "COPYRIGHT"
 +.br
 +Copyright \(co 2007 Andrew Tridgell, Ronnie Sahlberg
 +.br
 +.PP
 +This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version\&.
 +.PP
 +This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE\&. See the GNU General Public License for more details\&.
 +.PP
 +You should have received a copy of the GNU General Public License along with this program; if not, see
 +\m[blue]\fB\%http://www.gnu.org/licenses\fR\m[]\&.
 +.sp
diff --cc ctdb/doc/ctdb-tunables.7.html
index 4ca22b2,0000000..84efc84
mode 100644,000000..100644
--- a/ctdb/doc/ctdb-tunables.7.html
+++ b/ctdb/doc/ctdb-tunables.7.html
@@@ -1,306 -1,0 +1,306 @@@
- <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ctdb-tunables</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-tunables.7"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ctdb-tunables — CTDB tunable configuration variables</p></div><div class="refsect1"><a name="idp52 [...]
++<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ctdb-tunables</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-tunables.7"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ctdb-tunables — CTDB tunable configuration variables</p></div><div class="refsect1"><a name="idp53 [...]
 +      CTDB's behaviour can be configured by setting run-time tunable
 +      variables.  This lists and describes all tunables.  See the
 +      <span class="citerefentry"><span class="refentrytitle">ctdb</span>(1)</span>
 +      <span class="command"><strong>listvars</strong></span>, <span class="command"><strong>setvar</strong></span> and
 +      <span class="command"><strong>getvar</strong></span> commands for more details.
-     </p><div class="refsect2"><a name="idp52814352"></a><h3>MaxRedirectCount</h3><p>Default: 3</p><p>
++    </p><div class="refsect2"><a name="idp53113904"></a><h3>MaxRedirectCount</h3><p>Default: 3</p><p>
 +	If we are not the DMASTER and need to fetch a record across the network
 +	we first send the request to the LMASTER after which the record
 +	is passed onto the current DMASTER. If the DMASTER changes before
 +	the request has reached that node, the request will be passed onto the
 +	"next" DMASTER. For very hot records that migrate rapidly across the
 +	cluster this can cause a request to "chase" the record for many hops
 +	before it catches up with the record.
 +
 +	this is how many hops we allow trying to chase the DMASTER before we
 +	switch back to the LMASTER again to ask for new directions.
 +      </p><p>
 +	When chasing a record, this is how many hops we will chase the record
 +	for before going back to the LMASTER to ask for new guidance.
-       </p></div><div class="refsect2"><a name="idp52373680"></a><h3>SeqnumInterval</h3><p>Default: 1000</p><p>
++      </p></div><div class="refsect2"><a name="idp53710496"></a><h3>SeqnumInterval</h3><p>Default: 1000</p><p>
 +	Some databases have seqnum tracking enabled, so that samba will be able
 +	to detect asynchronously when there has been updates to the database.
 +	Everytime a database is updated its sequence number is increased.
 +      </p><p>
 +	This tunable is used to specify in 'ms' how frequently ctdb will
 +	send out updates to remote nodes to inform them that the sequence
 +	number is increased.
-       </p></div><div class="refsect2"><a name="idp52121072"></a><h3>ControlTimeout</h3><p>Default: 60</p><p>
++      </p></div><div class="refsect2"><a name="idp52645584"></a><h3>ControlTimeout</h3><p>Default: 60</p><p>
 +	This is the default
 +	setting for timeout for when sending a control message to either the
 +	local or a remote ctdb daemon.
-       </p></div><div class="refsect2"><a name="idp52632480"></a><h3>TraverseTimeout</h3><p>Default: 20</p><p>
++      </p></div><div class="refsect2"><a name="idp54101312"></a><h3>TraverseTimeout</h3><p>Default: 20</p><p>
 +	This setting controls how long we allow a traverse process to run.
 +	After this timeout triggers, the main ctdb daemon will abort the
 +	traverse if it has not yet finished.
-       </p></div><div class="refsect2"><a name="idp51611984"></a><h3>KeepaliveInterval</h3><p>Default: 5</p><p>
++      </p></div><div class="refsect2"><a name="idp53520528"></a><h3>KeepaliveInterval</h3><p>Default: 5</p><p>
 +	How often in seconds should the nodes send keepalives to eachother.
-       </p></div><div class="refsect2"><a name="idp49647792"></a><h3>KeepaliveLimit</h3><p>Default: 5</p><p>
++      </p></div><div class="refsect2"><a name="idp52258400"></a><h3>KeepaliveLimit</h3><p>Default: 5</p><p>
 +	After how many keepalive intervals without any traffic should a node
 +	wait until marking the peer as DISCONNECTED.
 +      </p><p>
 +	If a node has hung, it can thus take KeepaliveInterval*(KeepaliveLimit+1)
 +	seconds before we determine that the node is DISCONNECTED and that we
 +	require a recovery. This limitshould not be set too high since we want
 +	a hung node to be detectec, and expunged from the cluster well before
 +	common CIFS timeouts (45-90 seconds) kick in.
-       </p></div><div class="refsect2"><a name="idp49650272"></a><h3>RecoverTimeout</h3><p>Default: 20</p><p>
++      </p></div><div class="refsect2"><a name="idp53046368"></a><h3>RecoverTimeout</h3><p>Default: 20</p><p>
 +	This is the default setting for timeouts for controls when sent from the
 +	recovery daemon. We allow longer control timeouts from the recovery daemon
 +	than from normal use since the recovery dameon often use controls that 
 +	can take a lot longer than normal controls.
-       </p></div><div class="refsect2"><a name="idp48671376"></a><h3>RecoverInterval</h3><p>Default: 1</p><p>
++      </p></div><div class="refsect2"><a name="idp50061840"></a><h3>RecoverInterval</h3><p>Default: 1</p><p>
 +	How frequently in seconds should the recovery daemon perform the
 +	consistency checks that determine if we need to perform a recovery or not.
-       </p></div><div class="refsect2"><a name="idp48673136"></a><h3>ElectionTimeout</h3><p>Default: 3</p><p>
++      </p></div><div class="refsect2"><a name="idp49094448"></a><h3>ElectionTimeout</h3><p>Default: 3</p><p>
 +	When electing a new recovery master, this is how many seconds we allow
 +	the election to take before we either deem the election finished
 +	or we fail the election and start a new one.
-       </p></div><div class="refsect2"><a name="idp48674944"></a><h3>TakeoverTimeout</h3><p>Default: 9</p><p>
++      </p></div><div class="refsect2"><a name="idp49096224"></a><h3>TakeoverTimeout</h3><p>Default: 9</p><p>
 +	This is how many seconds we allow controls to take for IP failover events.
-       </p></div><div class="refsect2"><a name="idp48676544"></a><h3>MonitorInterval</h3><p>Default: 15</p><p>
++      </p></div><div class="refsect2"><a name="idp49146688"></a><h3>MonitorInterval</h3><p>Default: 15</p><p>
 +	How often should ctdb run the event scripts to check for a nodes health.
-       </p></div><div class="refsect2"><a name="idp48678144"></a><h3>TickleUpdateInterval</h3><p>Default: 20</p><p>
++      </p></div><div class="refsect2"><a name="idp49148288"></a><h3>TickleUpdateInterval</h3><p>Default: 20</p><p>
 +	How often will ctdb record and store the "tickle" information used to
 +	kickstart stalled tcp connections after a recovery.
-       </p></div><div class="refsect2"><a name="idp50525952"></a><h3>EventScriptTimeout</h3><p>Default: 20</p><p>
++      </p></div><div class="refsect2"><a name="idp49150032"></a><h3>EventScriptTimeout</h3><p>Default: 20</p><p>
 +	How long should ctdb let an event script run before aborting it and
 +	marking the node unhealthy.
-       </p></div><div class="refsect2"><a name="idp50527680"></a><h3>EventScriptTimeoutCount</h3><p>Default: 1</p><p>
++      </p></div><div class="refsect2"><a name="idp49151760"></a><h3>EventScriptTimeoutCount</h3><p>Default: 1</p><p>
 +	How many events in a row needs to timeout before we flag the node UNHEALTHY.
 +	This setting is useful if your scripts can not be written so that they
 +	do not hang for benign reasons.
-       </p></div><div class="refsect2"><a name="idp50529488"></a><h3>EventScriptUnhealthyOnTimeout</h3><p>Default: 0</p><p>
++      </p></div><div class="refsect2"><a name="idp49153568"></a><h3>EventScriptUnhealthyOnTimeout</h3><p>Default: 0</p><p>
 +	This setting can be be used to make ctdb never become UNHEALTHY if your
 +	eventscripts keep hanging/timing out.
-       </p></div><div class="refsect2"><a name="idp50531232"></a><h3>RecoveryGracePeriod</h3><p>Default: 120</p><p>
++      </p></div><div class="refsect2"><a name="idp49155312"></a><h3>RecoveryGracePeriod</h3><p>Default: 120</p><p>
 +	During recoveries, if a node has not caused recovery failures during the
 +	last grace period, any records of transgressions that the node has caused
 +	recovery failures will be forgiven. This resets the ban-counter back to 
 +	zero for that node.
-       </p></div><div class="refsect2"><a name="idp48555472"></a><h3>RecoveryBanPeriod</h3><p>Default: 300</p><p>
++      </p></div><div class="refsect2"><a name="idp49157184"></a><h3>RecoveryBanPeriod</h3><p>Default: 300</p><p>
 +	If a node becomes banned causing repetitive recovery failures. The node will
 +	eventually become banned from the cluster.
 +	This controls how long the culprit node will be banned from the cluster
 +	before it is allowed to try to join the cluster again.
 +	Don't set to small. A node gets banned for a reason and it is usually due
 +	to real problems with the node.
-       </p></div><div class="refsect2"><a name="idp48557456"></a><h3>DatabaseHashSize</h3><p>Default: 100001</p><p>
++      </p></div><div class="refsect2"><a name="idp49159168"></a><h3>DatabaseHashSize</h3><p>Default: 100001</p><p>
 +	Size of the hash chains for the local store of the tdbs that ctdb manages.
-       </p></div><div class="refsect2"><a name="idp48559056"></a><h3>DatabaseMaxDead</h3><p>Default: 5</p><p>
++      </p></div><div class="refsect2"><a name="idp49160768"></a><h3>DatabaseMaxDead</h3><p>Default: 5</p><p>
 +	How many dead records per hashchain in the TDB database do we allow before
 +	the freelist needs to be processed.
-       </p></div><div class="refsect2"><a name="idp48560800"></a><h3>RerecoveryTimeout</h3><p>Default: 10</p><p>
++      </p></div><div class="refsect2"><a name="idp49162512"></a><h3>RerecoveryTimeout</h3><p>Default: 10</p><p>
 +	Once a recovery has completed, no additional recoveries are permitted
 +	until this timeout has expired.
-       </p></div><div class="refsect2"><a name="idp48562528"></a><h3>EnableBans</h3><p>Default: 1</p><p>
++      </p></div><div class="refsect2"><a name="idp48975664"></a><h3>EnableBans</h3><p>Default: 1</p><p>
 +	When set to 0, this disables BANNING completely in the cluster and thus
 +	nodes can not get banned, even it they break. Don't set to 0 unless you
 +	know what you are doing.  You should set this to the same value on
 +	all nodes to avoid unexpected behaviour.
-       </p></div><div class="refsect2"><a name="idp48564400"></a><h3>DeterministicIPs</h3><p>Default: 0</p><p>
++      </p></div><div class="refsect2"><a name="idp48977536"></a><h3>DeterministicIPs</h3><p>Default: 0</p><p>
 +	When enabled, this tunable makes ctdb try to keep public IP addresses
 +	locked to specific nodes as far as possible. This makes it easier for
 +	debugging since you can know that as long as all nodes are healthy
 +	public IP X will always be hosted by node Y. 
 +      </p><p>
 +	The cost of using deterministic IP address assignment is that it
 +	disables part of the logic where ctdb tries to reduce the number of
 +	public IP assignment changes in the cluster. This tunable may increase
 +	the number of IP failover/failbacks that are performed on the cluster
 +	by a small margin.
-       </p></div><div class="refsect2"><a name="idp48566992"></a><h3>LCP2PublicIPs</h3><p>Default: 1</p><p>
++      </p></div><div class="refsect2"><a name="idp48980128"></a><h3>LCP2PublicIPs</h3><p>Default: 1</p><p>
 +	When enabled this switches ctdb to use the LCP2 ip allocation
 +	algorithm.
-       </p></div><div class="refsect2"><a name="idp48568592"></a><h3>ReclockPingPeriod</h3><p>Default: x</p><p>
++      </p></div><div class="refsect2"><a name="idp48981824"></a><h3>ReclockPingPeriod</h3><p>Default: x</p><p>
 +	Obsolete
-       </p></div><div class="refsect2"><a name="idp48570224"></a><h3>NoIPFailback</h3><p>Default: 0</p><p>
++      </p></div><div class="refsect2"><a name="idp48983456"></a><h3>NoIPFailback</h3><p>Default: 0</p><p>
 +	When set to 1, ctdb will not perform failback of IP addresses when a node
 +	becomes healthy. Ctdb WILL perform failover of public IP addresses when a
 +	node becomes UNHEALTHY, but when the node becomes HEALTHY again, ctdb
 +	will not fail the addresses back.
 +      </p><p>
 +	Use with caution! Normally when a node becomes available to the cluster
 +	ctdb will try to reassign public IP addresses onto the new node as a way
 +	to distribute the workload evenly across the clusternode. Ctdb tries to
 +	make sure that all running nodes have approximately the same number of
 +	public addresses it hosts.
 +      </p><p>
 +	When you enable this tunable, CTDB will no longer attempt to rebalance
 +	the cluster by failing IP addresses back to the new nodes. An unbalanced
 +	cluster will therefore remain unbalanced until there is manual
 +	intervention from the administrator. When this parameter is set, you can
 +	manually fail public IP addresses over to the new node(s) using the
 +	'ctdb moveip' command.
-       </p></div><div class="refsect2"><a name="idp48578544"></a><h3>DisableIPFailover</h3><p>Default: 0</p><p>
++      </p></div><div class="refsect2"><a name="idp48986832"></a><h3>DisableIPFailover</h3><p>Default: 0</p><p>
 +	When enabled, ctdb will not perform failover or failback. Even if a
 +	node fails while holding public IPs, ctdb will not recover the IPs or
 +	assign them to another node.
 +      </p><p>
 +	When you enable this tunable, CTDB will no longer attempt to recover
 +	the cluster by failing IP addresses over to other nodes. This leads to
 +	a service outage until the administrator has manually performed failover
 +	to replacement nodes using the 'ctdb moveip' command.
-       </p></div><div class="refsect2"><a name="idp48581008"></a><h3>NoIPTakeover</h3><p>Default: 0</p><p>
++      </p></div><div class="refsect2"><a name="idp48989296"></a><h3>NoIPTakeover</h3><p>Default: 0</p><p>
 +	When set to 1, ctdb will not allow IP addresses to be failed over
 +	onto this node. Any IP addresses that the node currently hosts
 +	will remain on the node but no new IP addresses can be failed over
 +	to the node.
-       </p></div><div class="refsect2"><a name="idp48582848"></a><h3>NoIPHostOnAllDisabled</h3><p>Default: 0</p><p>
++      </p></div><div class="refsect2"><a name="idp48995728"></a><h3>NoIPHostOnAllDisabled</h3><p>Default: 0</p><p>
 +	If no nodes are healthy then by default ctdb will happily host
 +	public IPs on disabled (unhealthy or administratively disabled)
 +	nodes.  This can cause problems, for example if the underlying
 +	cluster filesystem is not mounted.  When set to 1 on a node and
 +	that node is disabled it, any IPs hosted by this node will be
 +	released and the node will not takeover any IPs until it is no
 +	longer disabled.
-       </p></div><div class="refsect2"><a name="idp48584880"></a><h3>DBRecordCountWarn</h3><p>Default: 100000</p><p>
++      </p></div><div class="refsect2"><a name="idp48997760"></a><h3>DBRecordCountWarn</h3><p>Default: 100000</p><p>
 +	When set to non-zero, ctdb will log a warning when we try to recover a
 +	database with more than this many records. This will produce a warning
 +	if a database grows uncontrollably with orphaned records.
-       </p></div><div class="refsect2"><a name="idp48586704"></a><h3>DBRecordSizeWarn</h3><p>Default: 10000000</p><p>
++      </p></div><div class="refsect2"><a name="idp48999584"></a><h3>DBRecordSizeWarn</h3><p>Default: 10000000</p><p>
 +	When set to non-zero, ctdb will log a warning when we try to recover a
 +	database where a single record is bigger than this. This will produce
 +	a warning if a database record grows uncontrollably with orphaned
 +	sub-records.
-       </p></div><div class="refsect2"><a name="idp48588544"></a><h3>DBSizeWarn</h3><p>Default: 1000000000</p><p>
++      </p></div><div class="refsect2"><a name="idp49001424"></a><h3>DBSizeWarn</h3><p>Default: 1000000000</p><p>
 +	When set to non-zero, ctdb will log a warning when we try to recover a
 +	database bigger than this. This will produce
 +	a warning if a database grows uncontrollably.
-       </p></div><div class="refsect2"><a name="idp48590336"></a><h3>VerboseMemoryNames</h3><p>Default: 0</p><p>
++      </p></div><div class="refsect2"><a name="idp49003216"></a><h3>VerboseMemoryNames</h3><p>Default: 0</p><p>
 +	This feature consumes additional memory. when used the talloc library
 +	will create more verbose names for all talloc allocated objects.
-       </p></div><div class="refsect2"><a name="idp48592096"></a><h3>RecdPingTimeout</h3><p>Default: 60</p><p>
++      </p></div><div class="refsect2"><a name="idp49004976"></a><h3>RecdPingTimeout</h3><p>Default: 60</p><p>
 +	If the main dameon has not heard a "ping" from the recovery dameon for
 +	this many seconds, the main dameon will log a message that the recovery
 +	daemon is potentially hung.
-       </p></div><div class="refsect2"><a name="idp48593888"></a><h3>RecdFailCount</h3><p>Default: 10</p><p>
++      </p></div><div class="refsect2"><a name="idp49006768"></a><h3>RecdFailCount</h3><p>Default: 10</p><p>
 +	If the recovery daemon has failed to ping the main dameon for this many
 +	consecutive intervals, the main daemon will consider the recovery daemon
 +	as hung and will try to restart it to recover.
-       </p></div><div class="refsect2"><a name="idp48595712"></a><h3>LogLatencyMs</h3><p>Default: 0</p><p>
++      </p></div><div class="refsect2"><a name="idp49008592"></a><h3>LogLatencyMs</h3><p>Default: 0</p><p>
 +	When set to non-zero, this will make the main daemon log any operation that
 +	took longer than this value, in 'ms', to complete.
 +	These include "how long time a lockwait child process needed", 
 +	"how long time to write to a persistent database" but also
 +	"how long did it take to get a response to a CALL from a remote node".
-       </p></div><div class="refsect2"><a name="idp48597664"></a><h3>RecLockLatencyMs</h3><p>Default: 1000</p><p>
++      </p></div><div class="refsect2"><a name="idp49010544"></a><h3>RecLockLatencyMs</h3><p>Default: 1000</p><p>
 +	When using a reclock file for split brain prevention, if set to non-zero
 +	this tunable will make the recovery dameon log a message if the fcntl()
 +	call to lock/testlock the recovery file takes longer than this number of 
 +	ms.
-       </p></div><div class="refsect2"><a name="idp48599520"></a><h3>RecoveryDropAllIPs</h3><p>Default: 120</p><p>
++      </p></div><div class="refsect2"><a name="idp49012400"></a><h3>RecoveryDropAllIPs</h3><p>Default: 120</p><p>
 +	If we have been stuck in recovery, or stopped, or banned, mode for
 +	this many seconds we will force drop all held public addresses.
-       </p></div><div class="refsect2"><a name="idp54515792"></a><h3>VacuumInterval</h3><p>Default: 10</p><p>
++      </p></div><div class="refsect2"><a name="idp49014160"></a><h3>VacuumInterval</h3><p>Default: 10</p><p>
 +        Periodic interval in seconds when vacuuming is triggered for
 +        volatile databases.
-       </p></div><div class="refsect2"><a name="idp54517456"></a><h3>VacuumMaxRunTime</h3><p>Default: 120</p><p>
++      </p></div><div class="refsect2"><a name="idp49015888"></a><h3>VacuumMaxRunTime</h3><p>Default: 120</p><p>
 +        The maximum time in seconds for which the vacuuming process is
 +        allowed to run.  If vacuuming process takes longer than this
 +        value, then the vacuuming process is terminated.
-       </p></div><div class="refsect2"><a name="idp54519216"></a><h3>RepackLimit</h3><p>Default: 10000</p><p>
++      </p></div><div class="refsect2"><a name="idp49017712"></a><h3>RepackLimit</h3><p>Default: 10000</p><p>
 +        During vacuuming, if the number of freelist records are more
 +        than <code class="varname">RepackLimit</code>, then databases are
 +        repacked to get rid of the freelist records to avoid
 +        fragmentation.
 +      </p><p>
 +        Databases are repacked only if both
 +        <code class="varname">RepackLimit</code> and
 +        <code class="varname">VacuumLimit</code> are exceeded.
-       </p></div><div class="refsect2"><a name="idp54522416"></a><h3>VacuumLimit</h3><p>Default: 5000</p><p>
++      </p></div><div class="refsect2"><a name="idp54490736"></a><h3>VacuumLimit</h3><p>Default: 5000</p><p>
 +        During vacuuming, if the number of deleted records are more
 +        than <code class="varname">VacuumLimit</code>, then databases are
 +        repacked to avoid fragmentation.
 +      </p><p>
 +        Databases are repacked only if both
 +        <code class="varname">RepackLimit</code> and
 +        <code class="varname">VacuumLimit</code> are exceeded.
-       </p></div><div class="refsect2"><a name="idp54525584"></a><h3>VacuumFastPathCount</h3><p>Default: 60</p><p>
++      </p></div><div class="refsect2"><a name="idp54493808"></a><h3>VacuumFastPathCount</h3><p>Default: 60</p><p>
 +        When a record is deleted, it is marked for deletion during
 +        vacuuming.  Vacuuming process usually processes this list to purge
 +        the records from the database.  If the number of records marked
 +        for deletion are more than VacuumFastPathCount, then vacuuming
 +	process will scan the complete database for empty records instead
 +	of using the list of records marked for deletion.
-       </p></div><div class="refsect2"><a name="idp54527552"></a><h3>DeferredAttachTO</h3><p>Default: 120</p><p>
++      </p></div><div class="refsect2"><a name="idp54495776"></a><h3>DeferredAttachTO</h3><p>Default: 120</p><p>
 +	When databases are frozen we do not allow clients to attach to the
 +	databases. Instead of returning an error immediately to the application
 +	the attach request from the client is deferred until the database
 +	becomes available again at which stage we respond to the client.
 +      </p><p>
 +	This timeout controls how long we will defer the request from the client
 +	before timing it out and returning an error to the client.
-       </p></div><div class="refsect2"><a name="idp54529936"></a><h3>HopcountMakeSticky</h3><p>Default: 50</p><p>
++      </p></div><div class="refsect2"><a name="idp54498160"></a><h3>HopcountMakeSticky</h3><p>Default: 50</p><p>
 +	If the database is set to 'STICKY' mode, using the 'ctdb setdbsticky' 
 +	command, any record that is seen as very hot and migrating so fast that
 +	hopcount surpasses 50 is set to become a STICKY record for StickyDuration
 +	seconds. This means that after each migration the record will be kept on
 +	the node and prevented from being migrated off the node.
 +      </p><p>
 +	This setting allows one to try to identify such records and stop them from
 +	migrating across the cluster so fast. This will improve performance for
 +	certain workloads, such as locking.tdb if many clients are opening/closing
 +	the same file concurrently.
-       </p></div><div class="refsect2"><a name="idp54532496"></a><h3>StickyDuration</h3><p>Default: 600</p><p>
++      </p></div><div class="refsect2"><a name="idp54500720"></a><h3>StickyDuration</h3><p>Default: 600</p><p>
 +	Once a record has been found to be fetch-lock hot and has been flagged to
 +	become STICKY, this is for how long, in seconds, the record will be 
 +	flagged as a STICKY record.
-       </p></div><div class="refsect2"><a name="idp54534224"></a><h3>StickyPindown</h3><p>Default: 200</p><p>
++      </p></div><div class="refsect2"><a name="idp54502448"></a><h3>StickyPindown</h3><p>Default: 200</p><p>
 +	Once a STICKY record has been migrated onto a node, it will be pinned down
 +	on that node for this number of ms. Any request from other nodes to migrate
 +	the record off the node will be deferred until the pindown timer expires.
-       </p></div><div class="refsect2"><a name="idp54536016"></a><h3>StatHistoryInterval</h3><p>Default: 1</p><p>
++      </p></div><div class="refsect2"><a name="idp54504240"></a><h3>StatHistoryInterval</h3><p>Default: 1</p><p>
 +	Granularity of the statistics collected in the statistics history.
-       </p></div><div class="refsect2"><a name="idp54537648"></a><h3>AllowClientDBAttach</h3><p>Default: 1</p><p>
++      </p></div><div class="refsect2"><a name="idp54505872"></a><h3>AllowClientDBAttach</h3><p>Default: 1</p><p>
 +	When set to 0, clients are not allowed to attach to any databases.
 +	This can be used to temporarily block any new processes from attaching
 +	to and accessing the databases.
-       </p></div><div class="refsect2"><a name="idp54539376"></a><h3>RecoverPDBBySeqNum</h3><p>Default: 1</p><p>
++      </p></div><div class="refsect2"><a name="idp54507600"></a><h3>RecoverPDBBySeqNum</h3><p>Default: 1</p><p>
 +	When set to zero, database recovery for persistent databases
 +	is record-by-record and recovery process simply collects the
 +	most recent version of every individual record.
 +      </p><p>
 +	When set to non-zero, persistent databases will instead be
 +	recovered as a whole db and not by individual records. The
 +	node that contains the highest value stored in the record
 +	"__db_sequence_number__" is selected and the copy of that
 +	nodes database is used as the recovered database.
 +      </p><p>
 +	By default, recovery of persistent databses is done using
 +	__db_sequence_number__ record.
-       </p></div><div class="refsect2"><a name="idp54542304"></a><h3>FetchCollapse</h3><p>Default: 1</p><p>
++      </p></div><div class="refsect2"><a name="idp54510528"></a><h3>FetchCollapse</h3><p>Default: 1</p><p>
 +	When many clients across many nodes try to access the same record at the
 +	same time this can lead to a fetch storm where the record becomes very
 +	active and bounces between nodes very fast. This leads to high CPU
 +	utilization of the ctdbd daemon, trying to bounce that record around
 +	very fast, and poor performance.
 +      </p><p>
 +	This parameter is used to activate a fetch-collapse. A fetch-collapse
 +	is when we track which records we have requests in flight so that we only
 +	keep one request in flight from a certain node, even if multiple smbd
 +	processes are attemtping to fetch the record at the same time. This 
 +	can improve performance and reduce CPU utilization for certain
 +	workloads.
 +      </p><p>
 +	This timeout controls if we should collapse multiple fetch operations
 +	of the same record into a single request and defer all duplicates or not.
-       </p></div><div class="refsect2"><a name="idp54545504"></a><h3>Samba3AvoidDeadlocks</h3><p>Default: 0</p><p>
++      </p></div><div class="refsect2"><a name="idp54513728"></a><h3>Samba3AvoidDeadlocks</h3><p>Default: 0</p><p>
 +	Enable code that prevents deadlocks with Samba (only for Samba 3.x).
 +      </p><p>
 +	This should be set to 1 when using Samba version 3.x to enable special
 +	code in CTDB to avoid deadlock with Samba version 3.x.  This code
 +	is not required for Samba version 4.x and must not be enabled for
 +	Samba 4.x.
-       </p></div></div><div class="refsect1"><a name="idp54547888"></a><h2>SEE ALSO</h2><p>
++      </p></div></div><div class="refsect1"><a name="idp54516112"></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>,
 +
 +      <span class="citerefentry"><span class="refentrytitle">ctdbd.conf</span>(5)</span>,
 +
 +      <span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span>,
 +
 +      <a class="ulink" href="http://ctdb.samba.org/" target="_top">http://ctdb.samba.org/</a>
 +    </p></div></div></body></html>
diff --cc ctdb/doc/ctdb.1
index 8566abb,0000000..5b961b9
mode 100644,000000..100644
--- a/ctdb/doc/ctdb.1
+++ b/ctdb/doc/ctdb.1
@@@ -1,1289 -1,0 +1,1289 @@@
 +'\" t
 +.\"     Title: ctdb
 +.\"    Author: 
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 09/08/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: CTDB - clustered TDB database
 +.\"    Source: ctdb
 +.\"  Language: English
 +.\"
- .TH "CTDB" "1" "09/08/2015" "ctdb" "CTDB \- clustered TDB database"
++.TH "CTDB" "1" "12/10/2015" "ctdb" "CTDB \- clustered TDB database"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +ctdb \- CTDB management utility
 +.SH "SYNOPSIS"
 +.HP \w'\fBctdb\fR\ 'u
 +\fBctdb\fR [\fIOPTION\fR...] {\fICOMMAND\fR} [\fICOMMAND\-ARGS\fR]
 +.SH "DESCRIPTION"
 +.PP
 +ctdb is a utility to view and manage a CTDB cluster\&.
 +.PP
 +The following terms are used when referring to nodes in a cluster:
 +.PP
 +PNN
 +.RS 4
 +Physical Node Number\&. The physical node number is an integer that describes the node in the cluster\&. The first node has physical node number 0\&. in a cluster\&.
 +.RE
 +.PP
 +PNN\-LIST
 +.RS 4
 +This is either a single PNN, a comma\-separate list of PNNs or "all"\&.
 +.RE
 +.PP
 +Commands that reference a database use the following terms:
 +.PP
 +DB
 +.RS 4
 +This is either a database name, such as
 +locking\&.tdb
 +or a database ID such as "0x42fe72c5"\&.
 +.RE
 +.PP
 +DB\-LIST
 +.RS 4
 +A space separated list of at least one
 +\fIDB\fR\&.
 +.RE
 +.SH "OPTIONS"
 +.PP
 +\-n \fIPNN\-LIST\fR
 +.RS 4
 +The nodes specified by PNN\-LIST should be queried for the requested information\&. Default is to query the daemon running on the local host\&.
 +.RE
 +.PP
 +\-Y
 +.RS 4
 +Produce output in machine readable form for easier parsing by scripts\&. This uses a field delimiter of \*(Aq:\*(Aq\&. Not all commands support this option\&.
 +.RE
 +.PP
 +\-x \fISEPARATOR\fR
 +.RS 4
 +Use SEPARATOR to delimit fields in machine readable output\&. This implies \-Y\&.
 +.RE
 +.PP
 +\-X
 +.RS 4
 +Produce output in machine readable form for easier parsing by scripts\&. This uses a field delimiter of \*(Aq|\*(Aq\&. Not all commands support this option\&.
 +.sp
 +This is equivalent to "\-x|" and avoids some shell quoting issues\&.
 +.RE
 +.PP
 +\-t \fITIMEOUT\fR
 +.RS 4
 +Indicates that ctdb should wait up to TIMEOUT seconds for a response to most commands sent to the CTDB daemon\&. The default is 10 seconds\&.
 +.RE
 +.PP
 +\-T \fITIMELIMIT\fR
 +.RS 4
 +Indicates that TIMELIMIT is the maximum run time (in seconds) for the ctdb command\&. When TIMELIMIT is exceeded the ctdb command will terminate with an error\&. The default is 120 seconds\&.
 +.RE
 +.PP
 +\-? \-\-help
 +.RS 4
 +Print some help text to the screen\&.
 +.RE
 +.PP
 +\-\-usage
 +.RS 4
 +Print useage information to the screen\&.
 +.RE
 +.PP
 +\-d \-\-debug=\fIDEBUGLEVEL\fR
 +.RS 4
 +Change the debug level for the command\&. Default is NOTICE (2)\&.
 +.RE
 +.PP
 +\-\-socket=\fIFILENAME\fR
 +.RS 4
 +Specify that FILENAME is the name of the Unix domain socket to use when connecting to the local CTDB daemon\&. The default is
 +/tmp/ctdb\&.socket\&.
 +.RE
 +.SH "ADMINISTRATIVE COMMANDS"
 +.PP
 +These are commands used to monitor and administer a CTDB cluster\&.
 +.SS "pnn"
 +.PP
 +This command displays the PNN of the current node\&.
 +.SS "xpnn"
 +.PP
 +This command displays the PNN of the current node without contacting the CTDB daemon\&. It parses the nodes file directly, so can produce unexpected output if the nodes file has been edited but has not been reloaded\&.
 +.SS "status"
 +.PP
 +This command shows the current status of all CTDB nodes based on information from the queried node\&.
 +.PP
 +Note: If the the queried node is INACTIVE then the status might not be current\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBNode status\fR
 +.RS 4
 +.PP
 +This includes the number of physical nodes and the status of each node\&. See
 +\fBctdb\fR(7)
 +for information about node states\&.
 +.RE
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBGeneration\fR
 +.RS 4
 +.PP
 +The generation id is a number that indicates the current generation of a cluster instance\&. Each time a cluster goes through a reconfiguration or a recovery its generation id will be changed\&.
 +.PP
 +This number does not have any particular meaning other than to keep track of when a cluster has gone through a recovery\&. It is a random number that represents the current instance of a ctdb cluster and its databases\&. The CTDB daemon uses this number internally to be able to tell when commands to operate on the cluster and the databases was issued in a different generation of the cluster, to ensure that commands that operate on the databases will not survive across a cluster database [...]
 +.PP
 +Sometimes this number will be shown as "INVALID"\&. This only means that the ctdbd daemon has started but it has not yet merged with the cluster through a recovery\&. All nodes start with generation "INVALID" and are not assigned a real generation id until they have successfully been merged with a cluster through a recovery\&.
 +.RE
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBVirtual Node Number (VNN) map\fR
 +.RS 4
 +.PP
 +Consists of the number of virtual nodes and mapping from virtual node numbers to physical node numbers\&. Virtual nodes host CTDB databases\&. Only nodes that are participating in the VNN map can become lmaster or dmaster for database records\&.
 +.RE
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBRecovery mode\fR
 +.RS 4
 +.PP
 +This is the current recovery mode of the cluster\&. There are two possible modes:
 +.PP
 +NORMAL \- The cluster is fully operational\&.
 +.PP
 +RECOVERY \- The cluster databases have all been frozen, pausing all services while the cluster awaits a recovery process to complete\&. A recovery process should finish within seconds\&. If a cluster is stuck in the RECOVERY state this would indicate a cluster malfunction which needs to be investigated\&.
 +.PP
 +Once the recovery master detects an inconsistency, for example a node becomes disconnected/connected, the recovery daemon will trigger a cluster recovery process, where all databases are remerged across the cluster\&. When this process starts, the recovery master will first "freeze" all databases to prevent applications such as samba from accessing the databases and it will also mark the recovery mode as RECOVERY\&.
 +.PP
 +When the CTDB daemon starts up, it will start in RECOVERY mode\&. Once the node has been merged into a cluster and all databases have been recovered, the node mode will change into NORMAL mode and the databases will be "thawed", allowing samba to access the databases again\&.
 +.RE
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBRecovery master\fR
 +.RS 4
 +.PP
 +This is the cluster node that is currently designated as the recovery master\&. This node is responsible of monitoring the consistency of the cluster and to perform the actual recovery process when reqired\&.
 +.PP
 +Only one node at a time can be the designated recovery master\&. Which node is designated the recovery master is decided by an election process in the recovery daemons running on each node\&.
 +.RE
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBExample\fR
 +.RS 4
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +# ctdb status
 +Number of nodes:4
 +pnn:0 192\&.168\&.2\&.200       OK (THIS NODE)
 +pnn:1 192\&.168\&.2\&.201       OK
 +pnn:2 192\&.168\&.2\&.202       OK
 +pnn:3 192\&.168\&.2\&.203       OK
 +Generation:1362079228
 +Size:4
 +hash:0 lmaster:0
 +hash:1 lmaster:1
 +hash:2 lmaster:2
 +hash:3 lmaster:3
 +Recovery mode:NORMAL (0)
 +Recovery master:0
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.SS "nodestatus [\fIPNN\-LIST\fR]"
 +.PP
 +This command is similar to the
 +\fBstatus\fR
 +command\&. It displays the "node status" subset of output\&. The main differences are:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +The exit code is the bitwise\-OR of the flags for each specified node, while
 +\fBctdb status\fR
 +exits with 0 if it was able to retrieve status for all nodes\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fBctdb status\fR
 +provides status information for all nodes\&.
 +\fBctdb nodestatus\fR
 +defaults to providing status for only the current node\&. If PNN\-LIST is provided then status is given for the indicated node(s)\&.
 +.sp
 +By default,
 +\fBctdb nodestatus\fR
 +gathers status from the local node\&. However, if invoked with "\-n all" (or similar) then status is gathered from the given node(s)\&. In particular
 +\fBctdb nodestatus all\fR
 +and
 +\fBctdb nodestatus \-n all\fR
 +will produce different output\&. It is possible to provide 2 different nodespecs (with and without "\-n") but the output is usually confusing!
 +.RE
 +.PP
 +A common invocation in scripts is
 +\fBctdb nodestatus all\fR
 +to check whether all nodes in a cluster are healthy\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBExample\fR
 +.RS 4
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +# ctdb nodestatus
 +pnn:0 10\&.0\&.0\&.30        OK (THIS NODE)
 +
 +# ctdb nodestatus all
 +Number of nodes:2
 +pnn:0 10\&.0\&.0\&.30        OK (THIS NODE)
 +pnn:1 10\&.0\&.0\&.31        OK
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.SS "recmaster"
 +.PP
 +This command shows the pnn of the node which is currently the recmaster\&.
 +.PP
 +Note: If the the queried node is INACTIVE then the status might not be current\&.
 +.SS "uptime"
 +.PP
 +This command shows the uptime for the ctdb daemon\&. When the last recovery or ip\-failover completed and how long it took\&. If the "duration" is shown as a negative number, this indicates that there is a recovery/failover in progress and it started that many seconds ago\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBExample\fR
 +.RS 4
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +# ctdb uptime
 +Current time of node          :                Thu Oct 29 10:38:54 2009
 +Ctdbd start time              : (000 16:54:28) Wed Oct 28 17:44:26 2009
 +Time of last recovery/failover: (000 16:53:31) Wed Oct 28 17:45:23 2009
 +Duration of last recovery/failover: 2\&.248552 seconds
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.SS "listnodes"
 +.PP
 +This command shows lists the ip addresses of all the nodes in the cluster\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBExample\fR
 +.RS 4
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +# ctdb listnodes
 +192\&.168\&.2\&.200
 +192\&.168\&.2\&.201
 +192\&.168\&.2\&.202
 +192\&.168\&.2\&.203
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.SS "natgwlist"
 +.PP
 +Show the current NAT gateway master and the status of all nodes in the current NAT gateway group\&. See the
 +NAT GATEWAY
 +section in
 +\fBctdb\fR(7)
 +for more details\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBExample\fR
 +.RS 4
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +# ctdb natgwlist
 +0 192\&.168\&.2\&.200
 +Number of nodes:4
 +pnn:0 192\&.168\&.2\&.200       OK (THIS NODE)
 +pnn:1 192\&.168\&.2\&.201       OK
 +pnn:2 192\&.168\&.2\&.202       OK
 +pnn:3 192\&.168\&.2\&.203       OK
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.SS "ping"
 +.PP
 +This command will "ping" specified CTDB nodes in the cluster to verify that they are running\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBExample\fR
 +.RS 4
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +# ctdb ping \-n all
 +response from 0 time=0\&.000054 sec  (3 clients)
 +response from 1 time=0\&.000144 sec  (2 clients)
 +response from 2 time=0\&.000105 sec  (2 clients)
 +response from 3 time=0\&.000114 sec  (2 clients)
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.SS "ifaces"
 +.PP
 +This command will display the list of network interfaces, which could host public addresses, along with their status\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBExample\fR
 +.RS 4
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +# ctdb ifaces
 +Interfaces on node 0
 +name:eth5 link:up references:2
 +name:eth4 link:down references:0
 +name:eth3 link:up references:1
 +name:eth2 link:up references:1
 +
 +# ctdb \-X ifaces
 +|Name|LinkStatus|References|
 +|eth5|1|2|
 +|eth4|0|0|
 +|eth3|1|1|
 +|eth2|1|1|
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.SS "ip"
 +.PP
 +This command will display the list of public addresses that are provided by the cluster and which physical node is currently serving this ip\&. By default this command will ONLY show those public addresses that are known to the node itself\&. To see the full list of all public ips across the cluster you must use "ctdb ip \-n all"\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBExample\fR
 +.RS 4
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +# ctdb ip \-v
 +Public IPs on node 0
 +172\&.31\&.91\&.82 node[1] active[] available[eth2,eth3] configured[eth2,eth3]
 +172\&.31\&.91\&.83 node[0] active[eth3] available[eth2,eth3] configured[eth2,eth3]
 +172\&.31\&.91\&.84 node[1] active[] available[eth2,eth3] configured[eth2,eth3]
 +172\&.31\&.91\&.85 node[0] active[eth2] available[eth2,eth3] configured[eth2,eth3]
 +172\&.31\&.92\&.82 node[1] active[] available[eth5] configured[eth4,eth5]
 +172\&.31\&.92\&.83 node[0] active[eth5] available[eth5] configured[eth4,eth5]
 +172\&.31\&.92\&.84 node[1] active[] available[eth5] configured[eth4,eth5]
 +172\&.31\&.92\&.85 node[0] active[eth5] available[eth5] configured[eth4,eth5]
 +
 +# ctdb \-X ip \-v
 +|Public IP|Node|ActiveInterface|AvailableInterfaces|ConfiguredInterfaces|
 +|172\&.31\&.91\&.82|1||eth2,eth3|eth2,eth3|
 +|172\&.31\&.91\&.83|0|eth3|eth2,eth3|eth2,eth3|
 +|172\&.31\&.91\&.84|1||eth2,eth3|eth2,eth3|
 +|172\&.31\&.91\&.85|0|eth2|eth2,eth3|eth2,eth3|
 +|172\&.31\&.92\&.82|1||eth5|eth4,eth5|
 +|172\&.31\&.92\&.83|0|eth5|eth5|eth4,eth5|
 +|172\&.31\&.92\&.84|1||eth5|eth4,eth5|
 +|172\&.31\&.92\&.85|0|eth5|eth5|eth4,eth5|
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.SS "ipinfo \fIIP\fR"
 +.PP
 +This command will display details about the specified public addresses\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBExample\fR
 +.RS 4
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +# ctdb ipinfo 172\&.31\&.92\&.85
 +Public IP[172\&.31\&.92\&.85] info on node 0
 +IP:172\&.31\&.92\&.85
 +CurrentNode:0
 +NumInterfaces:2
 +Interface[1]: Name:eth4 Link:down References:0
 +Interface[2]: Name:eth5 Link:up References:2 (active)
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.SS "scriptstatus"
 +.PP
 +This command displays which scripts where run in the previous monitoring cycle and the result of each script\&. If a script failed with an error, causing the node to become unhealthy, the output from that script is also shown\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBExample\fR
 +.RS 4
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +# ctdb scriptstatus
 +7 scripts were executed last monitoring cycle
 +00\&.ctdb              Status:OK    Duration:0\&.056 Tue Mar 24 18:56:57 2009
 +10\&.interface         Status:OK    Duration:0\&.077 Tue Mar 24 18:56:57 2009
 +11\&.natgw             Status:OK    Duration:0\&.039 Tue Mar 24 18:56:57 2009
 +20\&.multipathd        Status:OK    Duration:0\&.038 Tue Mar 24 18:56:57 2009
 +31\&.clamd             Status:DISABLED
 +40\&.vsftpd            Status:OK    Duration:0\&.045 Tue Mar 24 18:56:57 2009
 +41\&.httpd             Status:OK    Duration:0\&.039 Tue Mar 24 18:56:57 2009
 +50\&.samba             Status:ERROR    Duration:0\&.082 Tue Mar 24 18:56:57 2009
 +OUTPUT:ERROR: Samba tcp port 445 is not responding
 +      
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.SS "disablescript \fISCRIPT\fR"
 +.PP
 +This command is used to disable an eventscript\&.
 +.PP
 +This will take effect the next time the eventscripts are being executed so it can take a short while until this is reflected in \*(Aqscriptstatus\*(Aq\&.
 +.SS "enablescript \fISCRIPT\fR"
 +.PP
 +This command is used to enable an eventscript\&.
 +.PP
 +This will take effect the next time the eventscripts are being executed so it can take a short while until this is reflected in \*(Aqscriptstatus\*(Aq\&.
 +.SS "listvars"
 +.PP
 +List all tuneable variables, except the values of the obsolete tunables like VacuumMinInterval\&. The obsolete tunables can be retrieved only explicitly with the "ctdb getvar" command\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBExample\fR
 +.RS 4
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +# ctdb listvars
 +MaxRedirectCount        = 3
 +SeqnumInterval          = 1000
 +ControlTimeout          = 60
 +TraverseTimeout         = 20
 +KeepaliveInterval       = 5
 +KeepaliveLimit          = 5
 +RecoverTimeout          = 20
 +RecoverInterval         = 1
 +ElectionTimeout         = 3
 +TakeoverTimeout         = 9
 +MonitorInterval         = 15
 +TickleUpdateInterval    = 20
 +EventScriptTimeout      = 30
 +EventScriptTimeoutCount = 1
 +RecoveryGracePeriod     = 120
 +RecoveryBanPeriod       = 300
 +DatabaseHashSize        = 100001
 +DatabaseMaxDead         = 5
 +RerecoveryTimeout       = 10
 +EnableBans              = 1
 +DeterministicIPs        = 0
 +LCP2PublicIPs           = 1
 +ReclockPingPeriod       = 60
 +NoIPFailback            = 0
 +DisableIPFailover       = 0
 +VerboseMemoryNames      = 0
 +RecdPingTimeout         = 60
 +RecdFailCount           = 10
 +LogLatencyMs            = 0
 +RecLockLatencyMs        = 1000
 +RecoveryDropAllIPs      = 120
 +VacuumInterval          = 10
 +VacuumMaxRunTime        = 30
 +RepackLimit             = 10000
 +VacuumLimit             = 5000
 +VacuumFastPathCount     = 60
 +MaxQueueDropMsg         = 1000000
 +UseStatusEvents         = 0
 +AllowUnhealthyDBRead    = 0
 +StatHistoryInterval     = 1
 +DeferredAttachTO        = 120
 +AllowClientDBAttach     = 1
 +RecoverPDBBySeqNum      = 0
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.SS "getvar \fINAME\fR"
 +.PP
 +Get the runtime value of a tuneable variable\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBExample\fR
 +.RS 4
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +# ctdb getvar MaxRedirectCount
 +MaxRedirectCount    = 3
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.SS "setvar \fINAME\fR \fIVALUE\fR"
 +.PP
 +Set the runtime value of a tuneable variable\&.
 +.PP
 +Example: ctdb setvar MaxRedirectCount 5
 +.SS "lvsmaster"
 +.PP
 +This command shows which node is currently the LVSMASTER\&. The LVSMASTER is the node in the cluster which drives the LVS system and which receives all incoming traffic from clients\&.
 +.PP
 +LVS is the mode where the entire CTDB/Samba cluster uses a single ip address for the entire cluster\&. In this mode all clients connect to one specific node which will then multiplex/loadbalance the clients evenly onto the other nodes in the cluster\&. This is an alternative to using public ip addresses\&. See the manpage for ctdbd for more information about LVS\&.
 +.SS "lvs"
 +.PP
 +This command shows which nodes in the cluster are currently active in the LVS configuration\&. I\&.e\&. which nodes we are currently loadbalancing the single ip address across\&.
 +.PP
 +LVS will by default only loadbalance across those nodes that are both LVS capable and also HEALTHY\&. Except if all nodes are UNHEALTHY in which case LVS will loadbalance across all UNHEALTHY nodes as well\&. LVS will never use nodes that are DISCONNECTED, STOPPED, BANNED or DISABLED\&.
 +.PP
 +Example output:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +2:10\&.0\&.0\&.13
 +3:10\&.0\&.0\&.14
 +      
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.SS "getcapabilities"
 +.PP
 +This command shows the capabilities of the current node\&. See the
 +CAPABILITIES
 +section in
 +\fBctdb\fR(7)
 +for more details\&.
 +.PP
 +Example output:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +RECMASTER: YES
 +LMASTER: YES
 +LVS: NO
 +NATGW: YES
 +      
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.SS "statistics"
 +.PP
 +Collect statistics from the CTDB daemon about how many calls it has served\&. Information about various fields in statistics can be found in
 +\fBctdb-statistics\fR(7)\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBExample\fR
 +.RS 4
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +# ctdb statistics
 +CTDB version 1
 +num_clients                        3
 +frozen                             0
 +recovering                         0
 +client_packets_sent           360489
 +client_packets_recv           360466
 +node_packets_sent             480931
 +node_packets_recv             240120
 +keepalive_packets_sent             4
 +keepalive_packets_recv             3
 +node
 +req_call                       2
 +reply_call                     2
 +req_dmaster                    0
 +reply_dmaster                  0
 +reply_error                    0
 +req_message                   42
 +req_control               120408
 +reply_control             360439
 +client
 +req_call                       2
 +req_message                   24
 +req_control               360440
 +timeouts
 +call                           0
 +control                        0
 +traverse                       0
 +total_calls                        2
 +pending_calls                      0
 +lockwait_calls                     0
 +pending_lockwait_calls             0
 +memory_used                     5040
 +max_hop_count                      0
 +max_call_latency                   4\&.948321 sec
 +max_lockwait_latency               0\&.000000 sec
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.SS "statisticsreset"
 +.PP
 +This command is used to clear all statistics counters in a node\&.
 +.PP
 +Example: ctdb statisticsreset
 +.SS "dbstatistics \fIDB\fR"
 +.PP
 +Display statistics about the database DB\&. Information about various fields in dbstatistics can be found in
 +\fBctdb-statistics\fR(7)\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBExample\fR
 +.RS 4
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +# ctdb dbstatistics locking\&.tdb
 +DB Statistics: locking\&.tdb
 + ro_delegations                     0
 + ro_revokes                         0
 + locks
 +     total                      14356
 +     failed                         0
 +     current                        0
 +     pending                        0
 + hop_count_buckets: 28087 2 1 0 0 0 0 0 0 0 0 0 0 0 0 0
 + lock_buckets: 0 14188 38 76 32 19 3 0 0 0 0 0 0 0 0 0
 + locks_latency      MIN/AVG/MAX     0\&.001066/0\&.012686/4\&.202292 sec out of 14356
 + Num Hot Keys:     1
 +     Count:8 Key:ff5bd7cb3ee3822edc1f0000000000000000000000000000
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.SS "getreclock"
 +.PP
 +Show the name of the recovery lock file, if any\&.
 +.PP
 +Example output:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	Reclock file:/clusterfs/\&.ctdb/recovery\&.lock
 +      
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.SS "setreclock [\fIFILE\fR]"
 +.PP
 +FILE specifies the name of the recovery lock file\&. If the recovery lock file is changed at run\-time then this will cause a recovery, which in turn causes the recovery lock to be retaken\&.
 +.PP
 +If no FILE is specified then a recovery lock file will no longer be used\&.
 +.PP
 +This command only affects the run\-time setting of a single CTDB node\&. This setting
 +\fImust\fR
 +be changed on all nodes simultaneously by specifying
 +\fB\-n all\fR
 +(or similar)\&. For information about configuring the recovery lock file please see the
 +CTDB_RECOVERY_LOCK
 +entry in
 +\fBctdbd.conf\fR(5)
 +and the
 +\-\-reclock
 +entry in
 +\fBctdbd\fR(1)\&. For information about the recovery lock please see the
 +RECOVERY LOCK
 +section in
 +\fBctdb\fR(7)\&.
 +.SS "getdebug"
 +.PP
 +Get the current debug level for the node\&. the debug level controls what information is written to the log file\&.
 +.PP
 +The debug levels are mapped to the corresponding syslog levels\&. When a debug level is set, only those messages at that level and higher levels will be printed\&.
 +.PP
 +The list of debug levels from highest to lowest are :
 +.PP
 +ERR WARNING NOTICE INFO DEBUG
 +.SS "setdebug \fIDEBUGLEVEL\fR"
 +.PP
 +Set the debug level of a node\&. This controls what information will be logged\&.
 +.PP
 +The debuglevel is one of ERR WARNING NOTICE INFO DEBUG
 +.SS "getpid"
 +.PP
 +This command will return the process id of the ctdb daemon\&.
 +.SS "disable"
 +.PP
 +This command is used to administratively disable a node in the cluster\&. A disabled node will still participate in the cluster and host clustered TDB records but its public ip address has been taken over by a different node and it no longer hosts any services\&.
 +.SS "enable"
 +.PP
 +Re\-enable a node that has been administratively disabled\&.
 +.SS "stop"
 +.PP
 +This command is used to administratively STOP a node in the cluster\&. A STOPPED node is connected to the cluster but will not host any public ip addresse, nor does it participate in the VNNMAP\&. The difference between a DISABLED node and a STOPPED node is that a STOPPED node does not host any parts of the database which means that a recovery is required to stop/continue nodes\&.
 +.SS "continue"
 +.PP
 +Re\-start a node that has been administratively stopped\&.
 +.SS "addip \fIIPADDR\fR/\fImask\fR \fIIFACE\fR"
 +.PP
 +This command is used to add a new public ip to a node during runtime\&. This allows public addresses to be added to a cluster without having to restart the ctdb daemons\&.
 +.PP
 +Note that this only updates the runtime instance of ctdb\&. Any changes will be lost next time ctdb is restarted and the public addresses file is re\-read\&. If you want this change to be permanent you must also update the public addresses file manually\&.
 +.SS "delip \fIIPADDR\fR"
 +.PP
 +This command is used to remove a public ip from a node during runtime\&. If this public ip is currently hosted by the node it being removed from, the ip will first be failed over to another node, if possible, before it is removed\&.
 +.PP
 +Note that this only updates the runtime instance of ctdb\&. Any changes will be lost next time ctdb is restarted and the public addresses file is re\-read\&. If you want this change to be permanent you must also update the public addresses file manually\&.
 +.SS "moveip \fIIPADDR\fR \fIPNN\fR"
 +.PP
 +This command can be used to manually fail a public ip address to a specific node\&.
 +.PP
 +In order to manually override the "automatic" distribution of public ip addresses that ctdb normally provides, this command only works when you have changed the tunables for the daemon to:
 +.PP
 +DeterministicIPs = 0
 +.PP
 +NoIPFailback = 1
 +.SS "shutdown"
 +.PP
 +This command will shutdown a specific CTDB daemon\&.
 +.SS "setlmasterrole on|off"
 +.PP
 +This command is used ot enable/disable the LMASTER capability for a node at runtime\&. This capability determines whether or not a node can be used as an LMASTER for records in the database\&. A node that does not have the LMASTER capability will not show up in the vnnmap\&.
 +.PP
 +Nodes will by default have this capability, but it can be stripped off nodes by the setting in the sysconfig file or by using this command\&.
 +.PP
 +Once this setting has been enabled/disabled, you need to perform a recovery for it to take effect\&.
 +.PP
 +See also "ctdb getcapabilities"
 +.SS "setrecmasterrole on|off"
 +.PP
 +This command is used ot enable/disable the RECMASTER capability for a node at runtime\&. This capability determines whether or not a node can be used as an RECMASTER for the cluster\&. A node that does not have the RECMASTER capability can not win a recmaster election\&. A node that already is the recmaster for the cluster when the capability is stripped off the node will remain the recmaster until the next cluster election\&.
 +.PP
 +Nodes will by default have this capability, but it can be stripped off nodes by the setting in the sysconfig file or by using this command\&.
 +.PP
 +See also "ctdb getcapabilities"
 +.SS "reloadnodes"
 +.PP
 +This command is used when adding new nodes, or removing existing nodes from an existing cluster\&.
 +.PP
 +Procedure to add a node:
 +.PP
 +1, To expand an existing cluster, first ensure with \*(Aqctdb status\*(Aq that all nodes are up and running and that they are all healthy\&. Do not try to expand a cluster unless it is completely healthy!
 +.PP
 +2, On all nodes, edit /etc/ctdb/nodes and add the new node as the last entry to the file\&. The new node MUST be added to the end of this file!
 +.PP
 +3, Verify that all the nodes have identical /etc/ctdb/nodes files after you edited them and added the new node!
 +.PP
 +4, Run \*(Aqctdb reloadnodes\*(Aq to force all nodes to reload the nodesfile\&.
 +.PP
 +5, Use \*(Aqctdb status\*(Aq on all nodes and verify that they now show the additional node\&.
 +.PP
 +6, Install and configure the new node and bring it online\&.
 +.PP
 +Procedure to remove a node:
 +.PP
 +1, To remove a node from an existing cluster, first ensure with \*(Aqctdb status\*(Aq that all nodes, except the node to be deleted, are up and running and that they are all healthy\&. Do not try to remove a node from a cluster unless the cluster is completely healthy!
 +.PP
 +2, Shutdown and poweroff the node to be removed\&.
 +.PP
 +3, On all other nodes, edit the /etc/ctdb/nodes file and comment out the node to be removed\&. Do not delete the line for that node, just comment it out by adding a \*(Aq#\*(Aq at the beginning of the line\&.
 +.PP
 +4, Run \*(Aqctdb reloadnodes\*(Aq to force all nodes to reload the nodesfile\&.
 +.PP
 +5, Use \*(Aqctdb status\*(Aq on all nodes and verify that the deleted node no longer shows up in the list\&.\&.
 +.PP
 +.SS "reloadips [\fIPNN\-LIST\fR]"
 +.PP
 +This command reloads the public addresses configuration file on the specified nodes\&. When it completes addresses will be reconfigured and reassigned across the cluster as necessary\&.
 +.SS "getdbmap"
 +.PP
 +This command lists all clustered TDB databases that the CTDB daemon has attached to\&. Some databases are flagged as PERSISTENT, this means that the database stores data persistently and the data will remain across reboots\&. One example of such a database is secrets\&.tdb where information about how the cluster was joined to the domain is stored\&.
 +.PP
 +If a PERSISTENT database is not in a healthy state the database is flagged as UNHEALTHY\&. If there\*(Aqs at least one completely healthy node running in the cluster, it\*(Aqs possible that the content is restored by a recovery run automaticly\&. Otherwise an administrator needs to analyze the problem\&.
 +.PP
 +See also "ctdb getdbstatus", "ctdb backupdb", "ctdb restoredb", "ctdb dumpbackup", "ctdb wipedb", "ctdb setvar AllowUnhealthyDBRead 1" and (if samba or tdb\-utils are installed) "tdbtool check"\&.
 +.PP
 +Most databases are not persistent and only store the state information that the currently running samba daemons need\&. These databases are always wiped when ctdb/samba starts and when a node is rebooted\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBExample\fR
 +.RS 4
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +# ctdb getdbmap
 +Number of databases:10
 +dbid:0x435d3410 name:notify\&.tdb path:/var/ctdb/notify\&.tdb\&.0 
 +dbid:0x42fe72c5 name:locking\&.tdb path:/var/ctdb/locking\&.tdb\&.0
 +dbid:0x1421fb78 name:brlock\&.tdb path:/var/ctdb/brlock\&.tdb\&.0 
 +dbid:0x17055d90 name:connections\&.tdb path:/var/ctdb/connections\&.tdb\&.0 
 +dbid:0xc0bdde6a name:sessionid\&.tdb path:/var/ctdb/sessionid\&.tdb\&.0 
 +dbid:0x122224da name:test\&.tdb path:/var/ctdb/test\&.tdb\&.0 
 +dbid:0x2672a57f name:idmap2\&.tdb path:/var/ctdb/persistent/idmap2\&.tdb\&.0 PERSISTENT
 +dbid:0xb775fff6 name:secrets\&.tdb path:/var/ctdb/persistent/secrets\&.tdb\&.0 PERSISTENT
 +dbid:0xe98e08b6 name:group_mapping\&.tdb path:/var/ctdb/persistent/group_mapping\&.tdb\&.0 PERSISTENT
 +dbid:0x7bbbd26c name:passdb\&.tdb path:/var/ctdb/persistent/passdb\&.tdb\&.0 PERSISTENT
 +
 +# ctdb getdbmap  # example for unhealthy database
 +Number of databases:1
 +dbid:0xb775fff6 name:secrets\&.tdb path:/var/ctdb/persistent/secrets\&.tdb\&.0 PERSISTENT UNHEALTHY
 +
 +# ctdb \-X getdbmap
 +|ID|Name|Path|Persistent|Unhealthy|
 +|0x7bbbd26c|passdb\&.tdb|/var/ctdb/persistent/passdb\&.tdb\&.0|1|0|
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.SS "backupdb \fIDB\fR \fIFILE\fR"
 +.PP
 +Copy the contents of database DB to FILE\&. FILE can later be read back using
 +\fBrestoredb\fR\&. This is mainly useful for backing up persistent databases such as
 +secrets\&.tdb
 +and similar\&.
 +.SS "restoredb \fIFILE\fR [\fIDB\fR]"
 +.PP
 +This command restores a persistent database that was previously backed up using backupdb\&. By default the data will be restored back into the same database as it was created from\&. By specifying dbname you can restore the data into a different database\&.
 +.SS "setdbreadonly \fIDB\fR"
 +.PP
 +This command will enable the read\-only record support for a database\&. This is an experimental feature to improve performance for contended records primarily in locking\&.tdb and brlock\&.tdb\&. When enabling this feature you must set it on all nodes in the cluster\&.
 +.SS "setdbsticky \fIDB\fR"
 +.PP
 +This command will enable the sticky record support for the specified database\&. This is an experimental feature to improve performance for contended records primarily in locking\&.tdb and brlock\&.tdb\&. When enabling this feature you must set it on all nodes in the cluster\&.
 +.SH "INTERNAL COMMANDS"
 +.PP
 +Internal commands are used by CTDB\*(Aqs scripts and are not required for managing a CTDB cluster\&. Their parameters and behaviour are subject to change\&.
 +.SS "gettickles \fIIPADDR\fR"
 +.PP
 +Show TCP connections that are registered with CTDB to be "tickled" if there is a failover\&.
 +.SS "gratiousarp \fIIPADDR\fR \fIINTERFACE\fR"
 +.PP
 +Send out a gratious ARP for the specified interface through the specified interface\&. This command is mainly used by the ctdb eventscripts\&.
 +.SS "killtcp"
 +.PP
 +Read a list of TCP connections, one per line, from standard input and terminate each connection\&. A connection is specified as:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	\fISRC\-IPADDR\fR:\fISRC\-PORT\fR \fIDST\-IPADDR\fR:\fIDST\-PORT\fR
 +      
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +Each connection is terminated by issuing a TCP RST to the SRC\-IPADDR:SRC\-PORT endpoint\&.
 +.PP
 +A single connection can be specified on the command\-line rather than on standard input\&.
 +.SS "pdelete \fIDB\fR \fIKEY\fR"
 +.PP
 +Delete KEY from DB\&.
 +.SS "pfetch \fIDB\fR \fIKEY\fR"
 +.PP
 +Print the value associated with KEY in DB\&.
 +.SS "pstore \fIDB\fR \fIKEY\fR \fIFILE\fR"
 +.PP
 +Store KEY in DB with contents of FILE as the associated value\&.
 +.SS "ptrans \fIDB\fR [\fIFILE\fR]"
 +.PP
 +Read a list of key\-value pairs, one per line from FILE, and store them in DB using a single transaction\&. An empty value is equivalent to deleting the given key\&.
 +.PP
 +The key and value should be separated by spaces or tabs\&. Each key/value should be a printable string enclosed in double\-quotes\&.
 +.SS "runstate [setup|first_recovery|startup|running]"
 +.PP
 +Print the runstate of the specified node\&. Runstates are used to serialise important state transitions in CTDB, particularly during startup\&.
 +.PP
 +If one or more optional runstate arguments are specified then the node must be in one of these runstates for the command to succeed\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBExample\fR
 +.RS 4
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +# ctdb runstate
 +RUNNING
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.SS "setifacelink \fIIFACE\fR up|down"
 +.PP
 +Set the internal state of network interface IFACE\&. This is typically used in the
 +10\&.interface
 +script in the "monitor" event\&.
 +.PP
 +Example: ctdb setifacelink eth0 up
 +.SS "setnatgwstate on|off"
 +.PP
 +Enable or disable the NAT gateway master capability on a node\&.
 +.SS "tickle \fISRC\-IPADDR\fR:\fISRC\-PORT\fR \fIDST\-IPADDR\fR:\fIDST\-PORT\fR"
 +.PP
 +Send a TCP tickle to the source host for the specified TCP connection\&. A TCP tickle is a TCP ACK packet with an invalid sequence and acknowledge number and will when received by the source host result in it sending an immediate correct ACK back to the other end\&.
 +.PP
 +TCP tickles are useful to "tickle" clients after a IP failover has occured since this will make the client immediately recognize the TCP connection has been disrupted and that the client will need to reestablish\&. This greatly speeds up the time it takes for a client to detect and reestablish after an IP failover in the ctdb cluster\&.
 +.SS "version"
 +.PP
 +Display the CTDB version\&.
 +.SH "DEBUGGING COMMANDS"
 +.PP
 +These commands are primarily used for CTDB development and testing and should not be used for normal administration\&.
 +.SS "OPTIONS"
 +.PP
 +\-\-print\-emptyrecords
 +.RS 4
 +This enables printing of empty records when dumping databases with the catdb, cattbd and dumpdbbackup commands\&. Records with empty data segment are considered deleted by ctdb and cleaned by the vacuuming mechanism, so this switch can come in handy for debugging the vacuuming behaviour\&.
 +.RE
 +.PP
 +\-\-print\-datasize
 +.RS 4
 +This lets database dumps (catdb, cattdb, dumpdbbackup) print the size of the record data instead of dumping the data contents\&.
 +.RE
 +.PP
 +\-\-print\-lmaster
 +.RS 4
 +This lets catdb print the lmaster for each record\&.
 +.RE
 +.PP
 +\-\-print\-hash
 +.RS 4
 +This lets database dumps (catdb, cattdb, dumpdbbackup) print the hash for each record\&.
 +.RE
 +.PP
 +\-\-print\-recordflags
 +.RS 4
 +This lets catdb and dumpdbbackup print the record flags for each record\&. Note that cattdb always prints the flags\&.
 +.RE
 +.SS "process\-exists \fIPID\fR"
 +.PP
 +This command checks if a specific process exists on the CTDB host\&. This is mainly used by Samba to check if remote instances of samba are still running or not\&.
 +.SS "getdbstatus \fIDB\fR"
 +.PP
 +This command displays more details about a database\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBExample\fR
 +.RS 4
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +# ctdb getdbstatus test\&.tdb\&.0
 +dbid: 0x122224da
 +name: test\&.tdb
 +path: /var/ctdb/test\&.tdb\&.0
 +PERSISTENT: no
 +HEALTH: OK
 +
 +# ctdb getdbstatus registry\&.tdb  # with a corrupted TDB
 +dbid: 0xf2a58948
 +name: registry\&.tdb
 +path: /var/ctdb/persistent/registry\&.tdb\&.0
 +PERSISTENT: yes
 +HEALTH: NO\-HEALTHY\-NODES \- ERROR \- Backup of corrupted TDB in \*(Aq/var/ctdb/persistent/registry\&.tdb\&.0\&.corrupted\&.20091208091949\&.0Z\*(Aq
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.SS "catdb \fIDB\fR"
 +.PP
 +Print a dump of the clustered TDB database DB\&.
 +.SS "cattdb \fIDB\fR"
 +.PP
 +Print a dump of the contents of the local TDB database DB\&.
 +.SS "dumpdbbackup \fIFILE\fR"
 +.PP
 +Print a dump of the contents from database backup FILE, similar to
 +\fBcatdb\fR\&.
 +.SS "wipedb \fIDB\fR"
 +.PP
 +Remove all contents of database DB\&.
 +.SS "recover"
 +.PP
 +This command will trigger the recovery daemon to do a cluster recovery\&.
 +.SS "ipreallocate, sync"
 +.PP
 +This command will force the recovery master to perform a full ip reallocation process and redistribute all ip addresses\&. This is useful to "reset" the allocations back to its default state if they have been changed using the "moveip" command\&. While a "recover" will also perform this reallocation, a recovery is much more hevyweight since it will also rebuild all the databases\&.
 +.SS "getmonmode"
 +.PP
 +This command returns the monutoring mode of a node\&. The monitoring mode is either ACTIVE or DISABLED\&. Normally a node will continuously monitor that all other nodes that are expected are in fact connected and that they respond to commands\&.
 +.PP
 +ACTIVE \- This is the normal mode\&. The node is actively monitoring all other nodes, both that the transport is connected and also that the node responds to commands\&. If a node becomes unavailable, it will be marked as DISCONNECTED and a recovery is initiated to restore the cluster\&.
 +.PP
 +DISABLED \- This node is not monitoring that other nodes are available\&. In this mode a node failure will not be detected and no recovery will be performed\&. This mode is useful when for debugging purposes one wants to attach GDB to a ctdb process but wants to prevent the rest of the cluster from marking this node as DISCONNECTED and do a recovery\&.
 +.SS "setmonmode 0|1"
 +.PP
 +This command can be used to explicitly disable/enable monitoring mode on a node\&. The main purpose is if one wants to attach GDB to a running ctdb daemon but wants to prevent the other nodes from marking it as DISCONNECTED and issuing a recovery\&. To do this, set monitoring mode to 0 on all nodes before attaching with GDB\&. Remember to set monitoring mode back to 1 afterwards\&.
 +.SS "attach \fIDBNAME\fR [persistent]"
 +.PP
 +Create a new CTDB database called DBNAME and attach to it on all nodes\&.
 +.SS "detach \fIDB\-LIST\fR"
 +.PP
 +Detach specified non\-persistent database(s) from the cluster\&. This command will disconnect specified database(s) on all nodes in the cluster\&. This command should only be used when none of the specified database(s) are in use\&.
 +.PP
 +All nodes should be active and tunable AllowClientDBAccess should be disabled on all nodes before detaching databases\&.
 +.SS "dumpmemory"
 +.PP
 +This is a debugging command\&. This command will make the ctdb daemon to write a fill memory allocation map to standard output\&.
 +.SS "rddumpmemory"
 +.PP
 +This is a debugging command\&. This command will dump the talloc memory allocation tree for the recovery daemon to standard output\&.
 +.SS "thaw"
 +.PP
 +Thaw a previously frozen node\&.
 +.SS "eventscript \fIARGUMENTS\fR"
 +.PP
 +This is a debugging command\&. This command can be used to manually invoke and run the eventscritps with arbitrary arguments\&.
 +.SS "ban \fIBANTIME\fR"
 +.PP
 +Administratively ban a node for BANTIME seconds\&. The node will be unbanned after BANTIME seconds have elapsed\&.
 +.PP
 +A banned node does not participate in the cluster\&. It does not host any records for the clustered TDB and does not host any public IP addresses\&.
 +.PP
 +Nodes are automatically banned if they misbehave\&. For example, a node may be banned if it causes too many cluster recoveries\&.
 +.PP
 +To administratively exclude a node from a cluster use the
 +\fBstop\fR
 +command\&.
 +.SS "unban"
 +.PP
 +This command is used to unban a node that has either been administratively banned using the ban command or has been automatically banned\&.
 +.SS "rebalancenode [\fIPNN\-LIST\fR]"
 +.PP
 +This command marks the given nodes as rebalance targets in the LCP2 IP allocation algorithm\&. The
 +\fBreloadips\fR
 +command will do this as necessary so this command should not be needed\&.
 +.SS "check_srvids \fISRVID\fR \&.\&.\&."
 +.PP
 +This command checks whether a set of srvid message ports are registered on the node or not\&. The command takes a list of values to check\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBExample\fR
 +.RS 4
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +# ctdb check_srvids 1 2 3 14765
 +Server id 0:1 does not exist
 +Server id 0:2 does not exist
 +Server id 0:3 does not exist
 +Server id 0:14765 exists
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.SH "SEE ALSO"
 +.PP
 +\fBctdbd\fR(1),
 +\fBonnode\fR(1),
 +\fBctdb\fR(7),
 +\fBctdb-statistics\fR(7),
 +\fBctdb-tunables\fR(7),
 +\m[blue]\fB\%http://ctdb.samba.org/\fR\m[]
 +.SH "AUTHOR"
 +.br
 +.PP
 +This documentation was written by Ronnie Sahlberg, Amitay Isaacs, Martin Schwenke
 +.SH "COPYRIGHT"
 +.br
 +Copyright \(co 2007 Andrew Tridgell, Ronnie Sahlberg
 +.br
 +.PP
 +This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version\&.
 +.PP
 +This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE\&. See the GNU General Public License for more details\&.
 +.PP
 +You should have received a copy of the GNU General Public License along with this program; if not, see
 +\m[blue]\fB\%http://www.gnu.org/licenses\fR\m[]\&.
 +.sp
diff --cc ctdb/doc/ctdb.1.html
index b931c34,0000000..cef0592
mode 100644,000000..100644
--- a/ctdb/doc/ctdb.1.html
+++ b/ctdb/doc/ctdb.1.html
@@@ -1,882 -1,0 +1,882 @@@
- <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.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ctdb — CTDB management utility</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><co [...]
++<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.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ctdb — CTDB management utility</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><co [...]
 +      ctdb is a utility to view and manage a CTDB cluster.
 +    </p><p>
 +      The following terms are used when referring to nodes in a
 +      cluster:
 +      </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">PNN</span></dt><dd><p>
 +	      Physical Node Number.  The physical node number is an
 +	      integer that describes the node in the cluster. The
 +	      first node has physical node number 0.  in a cluster.
 +	    </p></dd><dt><span class="term">PNN-LIST</span></dt><dd><p>
 +	      This is either a single PNN, a comma-separate list of PNNs
 +	      or "all".
 +	    </p></dd></dl></div><p>
 +    </p><p>
 +      Commands that reference a database use the following terms:
 +      </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">DB</span></dt><dd><p>
 +	      This is either a database name, such as
 +	      <code class="filename">locking.tdb</code> or a database ID such
 +	      as "0x42fe72c5".
 +	    </p></dd><dt><span class="term">DB-LIST</span></dt><dd><p>
 +	      A space separated list of at least one
 +	      <em class="parameter"><code>DB</code></em>.
 +	    </p></dd></dl></div><p>
-     </p></div><div class="refsect1"><a name="idp49160128"></a><h2>OPTIONS</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term">-n <em class="parameter"><code>PNN-LIST</code></em></span></dt><dd><p>
++    </p></div><div class="refsect1"><a name="idp49137312"></a><h2>OPTIONS</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term">-n <em class="parameter"><code>PNN-LIST</code></em></span></dt><dd><p>
 +	  The nodes specified by PNN-LIST should be queried for the
 +	  requested information.  Default is to query the daemon
 +	  running on the local host.
 +	</p></dd><dt><span class="term">-Y</span></dt><dd><p>
 +	  Produce output in machine readable form for easier parsing
 +	  by scripts. This uses a field delimiter of ':'.  Not all
 +	  commands support this option.
 +	</p></dd><dt><span class="term">-x <em class="parameter"><code>SEPARATOR</code></em></span></dt><dd><p>
 +	  Use SEPARATOR to delimit fields in machine readable output.
 +	  This implies -Y.
 +	</p></dd><dt><span class="term">-X</span></dt><dd><p>
 +	  Produce output in machine readable form for easier parsing
 +	  by scripts. This uses a field delimiter of '|'.  Not all
 +	  commands support this option.
 +	</p><p>
 +	  This is equivalent to "-x|" and avoids some shell quoting
 +	  issues.
 +	</p></dd><dt><span class="term">-t <em class="parameter"><code>TIMEOUT</code></em></span></dt><dd><p>
 +	  Indicates that ctdb should wait up to TIMEOUT seconds for
 +	  a response to most commands sent to the CTDB daemon.  The
 +	  default is 10 seconds.
 +	</p></dd><dt><span class="term">-T <em class="parameter"><code>TIMELIMIT</code></em></span></dt><dd><p>
 +	  Indicates that TIMELIMIT is the maximum run time (in
 +	  seconds) for the ctdb command.  When TIMELIMIT is exceeded
 +	  the ctdb command will terminate with an error.  The default
 +	  is 120 seconds.
 +	</p></dd><dt><span class="term">-? --help</span></dt><dd><p>
 +	  Print some help text to the screen.
 +	</p></dd><dt><span class="term">--usage</span></dt><dd><p>
 +	  Print useage information to the screen.
 +	</p></dd><dt><span class="term">-d --debug=<em class="parameter"><code>DEBUGLEVEL</code></em></span></dt><dd><p>
 +	  Change the debug level for the command. Default is NOTICE (2).
 +	</p></dd><dt><span class="term">--socket=<em class="parameter"><code>FILENAME</code></em></span></dt><dd><p>
 +	  Specify that FILENAME is the name of the Unix domain
 +	  socket to use when connecting to the local CTDB
 +	  daemon. The default is
 +	  <code class="filename">/tmp/ctdb.socket</code>.
- 	</p></dd></dl></div></div><div class="refsect1"><a name="idp49115488"></a><h2>ADMINISTRATIVE COMMANDS</h2><p>
++	</p></dd></dl></div></div><div class="refsect1"><a name="idp48970304"></a><h2>ADMINISTRATIVE COMMANDS</h2><p>
 +      These are commands used to monitor and administer a CTDB cluster.
-     </p><div class="refsect2"><a name="idp49116640"></a><h3>pnn</h3><p>
++    </p><div class="refsect2"><a name="idp48971360"></a><h3>pnn</h3><p>
 +	This command displays the PNN of the current node.
-       </p></div><div class="refsect2"><a name="idp49117792"></a><h3>xpnn</h3><p>
++      </p></div><div class="refsect2"><a name="idp48972512"></a><h3>xpnn</h3><p>
 +	This command displays the PNN of the current node without
 +	contacting the CTDB daemon.  It parses the nodes file
 +	directly, so can produce unexpected output if the nodes file
 +	has been edited but has not been reloaded.
-       </p></div><div class="refsect2"><a name="idp49119216"></a><h3>status</h3><p>
++      </p></div><div class="refsect2"><a name="idp48973936"></a><h3>status</h3><p>
 +	This command shows the current status of all CTDB nodes based
 +	on information from the queried node.
 +      </p><p>
 +	Note: If the the queried node is INACTIVE then the status
 +	might not be current.
-       </p><div class="refsect3"><a name="idp49120896"></a><h4>Node status</h4><p>
++      </p><div class="refsect3"><a name="idp48975616"></a><h4>Node status</h4><p>
 +	  This includes the number of physical nodes and the status of
 +	  each node.  See <span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span> for information
 +	  about node states.
- 	</p></div><div class="refsect3"><a name="idp49123152"></a><h4>Generation</h4><p>
++	</p></div><div class="refsect3"><a name="idp48977872"></a><h4>Generation</h4><p>
 +	  The generation id is a number that indicates the current generation 
 +	  of a cluster instance. Each time a cluster goes through a 
 +	  reconfiguration or a recovery its generation id will be changed.
 +	</p><p>
 +	  This number does not have any particular meaning other than
 +	  to keep track of when a cluster has gone through a
 +	  recovery. It is a random number that represents the current
 +	  instance of a ctdb cluster and its databases.  The CTDB
 +	  daemon uses this number internally to be able to tell when
 +	  commands to operate on the cluster and the databases was
 +	  issued in a different generation of the cluster, to ensure
 +	  that commands that operate on the databases will not survive
 +	  across a cluster database recovery.  After a recovery, all
 +	  old outstanding commands will automatically become invalid.
 +	</p><p>
 +	  Sometimes this number will be shown as "INVALID". This only means that
 +	  the ctdbd daemon has started but it has not yet merged with the cluster through a recovery.
 +	  All nodes start with generation "INVALID" and are not assigned a real
 +	  generation id until they have successfully been merged with a cluster
 +	  through a recovery.
- 	</p></div><div class="refsect3"><a name="idp49126928"></a><h4>Virtual Node Number (VNN) map</h4><p>
++	</p></div><div class="refsect3"><a name="idp48980400"></a><h4>Virtual Node Number (VNN) map</h4><p>
 +	  Consists of the number of virtual nodes and mapping from
 +	  virtual node numbers to physical node numbers.  Virtual
 +	  nodes host CTDB databases.  Only nodes that are
 +	  participating in the VNN map can become lmaster or dmaster
 +	  for database records.
- 	</p></div><div class="refsect3"><a name="idp49128400"></a><h4>Recovery mode</h4><p>
++	</p></div><div class="refsect3"><a name="idp48987952"></a><h4>Recovery mode</h4><p>
 +	  This is the current recovery mode of the cluster. There are two possible modes:
 +	</p><p>
 +	  NORMAL - The cluster is fully operational.
 +	</p><p>
 +	  RECOVERY - The cluster databases have all been frozen, pausing all services while the cluster awaits a recovery process to complete. A recovery process should finish within seconds. If a cluster is stuck in the RECOVERY state this would indicate a cluster malfunction which needs to be investigated.
 +	</p><p>
 +	  Once the recovery master detects an inconsistency, for example a node 
 +	  becomes disconnected/connected, the recovery daemon will trigger a 
 +	  cluster recovery process, where all databases are remerged across the
 +	  cluster. When this process starts, the recovery master will first
 +	  "freeze" all databases to prevent applications such as samba from 
 +	  accessing the databases and it will also mark the recovery mode as
 +	  RECOVERY.
 +	</p><p>
 +	  When the CTDB daemon starts up, it will start in RECOVERY
 +	  mode.  Once the node has been merged into a cluster and all
 +	  databases have been recovered, the node mode will change into
 +	  NORMAL mode and the databases will be "thawed", allowing samba
 +	  to access the databases again.
- 	</p></div><div class="refsect3"><a name="idp49132304"></a><h4>Recovery master</h4><p>
++	</p></div><div class="refsect3"><a name="idp48991760"></a><h4>Recovery master</h4><p>
 +	  This is the cluster node that is currently designated as the recovery master. This node is responsible of monitoring the consistency of the cluster and to perform the actual recovery process when reqired.
 +	</p><p>
 +	  Only one node at a time can be the designated recovery master. Which
 +	  node is designated the recovery master is decided by an election
 +	  process in the recovery daemons running on each node.
- 	</p></div><div class="refsect3"><a name="idp49134304"></a><h4>Example</h4><pre class="screen">
++	</p></div><div class="refsect3"><a name="idp48993760"></a><h4>Example</h4><pre class="screen">
 +# ctdb status
 +Number of nodes:4
 +pnn:0 192.168.2.200       OK (THIS NODE)
 +pnn:1 192.168.2.201       OK
 +pnn:2 192.168.2.202       OK
 +pnn:3 192.168.2.203       OK
 +Generation:1362079228
 +Size:4
 +hash:0 lmaster:0
 +hash:1 lmaster:1
 +hash:2 lmaster:2
 +hash:3 lmaster:3
 +Recovery mode:NORMAL (0)
 +Recovery master:0
- 	</pre></div></div><div class="refsect2"><a name="idp49136208"></a><h3>nodestatus [<span class="optional"><em class="parameter"><code>PNN-LIST</code></em></span>]</h3><p>
++	</pre></div></div><div class="refsect2"><a name="idp48995664"></a><h3>nodestatus [<span class="optional"><em class="parameter"><code>PNN-LIST</code></em></span>]</h3><p>
 +	This command is similar to the <span class="command"><strong>status</strong></span>
 +	command.  It displays the "node status" subset of output.  The
 +	main differences are:
 +      </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
 +	    The exit code is the bitwise-OR of the flags for each
 +	    specified node, while <span class="command"><strong>ctdb status</strong></span> exits
 +	    with 0 if it was able to retrieve status for all nodes.
 +	  </p></li><li class="listitem"><p>
 +	    <span class="command"><strong>ctdb status</strong></span> provides status information
 +	    for all nodes.  <span class="command"><strong>ctdb nodestatus</strong></span>
 +	    defaults to providing status for only the current node.
 +	    If PNN-LIST is provided then status is given for
 +	    the indicated node(s).
 +	  </p><p>
 +	    By default, <span class="command"><strong>ctdb nodestatus</strong></span> gathers
 +	    status from the local node.  However, if invoked with "-n
 +	    all" (or similar) then status is gathered from the given
 +	    node(s).  In particular <span class="command"><strong>ctdb nodestatus
 +	    all</strong></span> and <span class="command"><strong>ctdb nodestatus -n
 +	    all</strong></span> will produce different output.  It is
 +	    possible to provide 2 different nodespecs (with and
 +	    without "-n") but the output is usually confusing!
 +	  </p></li></ul></div><p>
 +	A common invocation in scripts is <span class="command"><strong>ctdb nodestatus
 +	all</strong></span> to check whether all nodes in a cluster are
 +	healthy.
-       </p><div class="refsect3"><a name="idp55806208"></a><h4>Example</h4><pre class="screen">
++      </p><div class="refsect3"><a name="idp49006608"></a><h4>Example</h4><pre class="screen">
 +# ctdb nodestatus
 +pnn:0 10.0.0.30        OK (THIS NODE)
 +
 +# ctdb nodestatus all
 +Number of nodes:2
 +pnn:0 10.0.0.30        OK (THIS NODE)
 +pnn:1 10.0.0.31        OK
- 	</pre></div></div><div class="refsect2"><a name="idp55807904"></a><h3>recmaster</h3><p>
++	</pre></div></div><div class="refsect2"><a name="idp49008368"></a><h3>recmaster</h3><p>
 +	This command shows the pnn of the node which is currently the recmaster.
 +      </p><p>
 +	Note: If the the queried node is INACTIVE then the status
 +	might not be current.
-       </p></div><div class="refsect2"><a name="idp55809648"></a><h3>uptime</h3><p>
++      </p></div><div class="refsect2"><a name="idp54721184"></a><h3>uptime</h3><p>
 +	This command shows the uptime for the ctdb daemon. When the last recovery or ip-failover completed and how long it took. If the "duration" is shown as a negative number, this indicates that there is a recovery/failover in progress and it started that many seconds ago.
-       </p><div class="refsect3"><a name="idp55810960"></a><h4>Example</h4><pre class="screen">
++      </p><div class="refsect3"><a name="idp54722496"></a><h4>Example</h4><pre class="screen">
 +# ctdb uptime
 +Current time of node          :                Thu Oct 29 10:38:54 2009
 +Ctdbd start time              : (000 16:54:28) Wed Oct 28 17:44:26 2009
 +Time of last recovery/failover: (000 16:53:31) Wed Oct 28 17:45:23 2009
 +Duration of last recovery/failover: 2.248552 seconds
- 	</pre></div></div><div class="refsect2"><a name="idp55812784"></a><h3>listnodes</h3><p>
++	</pre></div></div><div class="refsect2"><a name="idp54724320"></a><h3>listnodes</h3><p>
 +	This command shows lists the ip addresses of all the nodes in the cluster.
-       </p><div class="refsect3"><a name="idp55813904"></a><h4>Example</h4><pre class="screen">
++      </p><div class="refsect3"><a name="idp54725440"></a><h4>Example</h4><pre class="screen">
 +# ctdb listnodes
 +192.168.2.200
 +192.168.2.201
 +192.168.2.202
 +192.168.2.203
- 	</pre></div></div><div class="refsect2"><a name="idp55815520"></a><h3>natgwlist</h3><p>
++	</pre></div></div><div class="refsect2"><a name="idp54727056"></a><h3>natgwlist</h3><p>
 +	Show the current NAT gateway master and the status of all
 +	nodes in the current NAT gateway group.  See the
 +	<em class="citetitle">NAT GATEWAY</em> section in
 +	<span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span> for more details.
-       </p><div class="refsect3"><a name="idp55817952"></a><h4>Example</h4><pre class="screen">
++      </p><div class="refsect3"><a name="idp54729488"></a><h4>Example</h4><pre class="screen">
 +# ctdb natgwlist
 +0 192.168.2.200
 +Number of nodes:4
 +pnn:0 192.168.2.200       OK (THIS NODE)
 +pnn:1 192.168.2.201       OK
 +pnn:2 192.168.2.202       OK
 +pnn:3 192.168.2.203       OK
- 	</pre></div></div><div class="refsect2"><a name="idp55819664"></a><h3>ping</h3><p>
++	</pre></div></div><div class="refsect2"><a name="idp54731200"></a><h3>ping</h3><p>
 +	This command will "ping" specified CTDB nodes in the cluster
 +	to verify that they are running.
-       </p><div class="refsect3"><a name="idp55820800"></a><h4>Example</h4><pre class="screen">
++      </p><div class="refsect3"><a name="idp54732336"></a><h4>Example</h4><pre class="screen">
 +# ctdb ping -n all
 +response from 0 time=0.000054 sec  (3 clients)
 +response from 1 time=0.000144 sec  (2 clients)
 +response from 2 time=0.000105 sec  (2 clients)
 +response from 3 time=0.000114 sec  (2 clients)
- 	</pre></div></div><div class="refsect2"><a name="idp55822544"></a><h3>ifaces</h3><p>
++	</pre></div></div><div class="refsect2"><a name="idp54734080"></a><h3>ifaces</h3><p>
 +	This command will display the list of network interfaces, which could
 +	host public addresses, along with their status.
-       </p><div class="refsect3"><a name="idp55823712"></a><h4>Example</h4><pre class="screen">
++      </p><div class="refsect3"><a name="idp54735248"></a><h4>Example</h4><pre class="screen">
 +# ctdb ifaces
 +Interfaces on node 0
 +name:eth5 link:up references:2
 +name:eth4 link:down references:0
 +name:eth3 link:up references:1
 +name:eth2 link:up references:1
 +
 +# ctdb -X ifaces
 +|Name|LinkStatus|References|
 +|eth5|1|2|
 +|eth4|0|0|
 +|eth3|1|1|
 +|eth2|1|1|
- 	</pre></div></div><div class="refsect2"><a name="idp55825504"></a><h3>ip</h3><p>
++	</pre></div></div><div class="refsect2"><a name="idp54737040"></a><h3>ip</h3><p>
 +	This command will display the list of public addresses that are provided by the cluster and which physical node is currently serving this ip. By default this command will ONLY show those public addresses that are known to the node itself. To see the full list of all public ips across the cluster you must use "ctdb ip -n all".
-       </p><div class="refsect3"><a name="idp55827216"></a><h4>Example</h4><pre class="screen">
++      </p><div class="refsect3"><a name="idp54738752"></a><h4>Example</h4><pre class="screen">
 +# ctdb ip -v
 +Public IPs on node 0
 +172.31.91.82 node[1] active[] available[eth2,eth3] configured[eth2,eth3]
 +172.31.91.83 node[0] active[eth3] available[eth2,eth3] configured[eth2,eth3]
 +172.31.91.84 node[1] active[] available[eth2,eth3] configured[eth2,eth3]
 +172.31.91.85 node[0] active[eth2] available[eth2,eth3] configured[eth2,eth3]
 +172.31.92.82 node[1] active[] available[eth5] configured[eth4,eth5]
 +172.31.92.83 node[0] active[eth5] available[eth5] configured[eth4,eth5]
 +172.31.92.84 node[1] active[] available[eth5] configured[eth4,eth5]
 +172.31.92.85 node[0] active[eth5] available[eth5] configured[eth4,eth5]
 +
 +# ctdb -X ip -v
 +|Public IP|Node|ActiveInterface|AvailableInterfaces|ConfiguredInterfaces|
 +|172.31.91.82|1||eth2,eth3|eth2,eth3|
 +|172.31.91.83|0|eth3|eth2,eth3|eth2,eth3|
 +|172.31.91.84|1||eth2,eth3|eth2,eth3|
 +|172.31.91.85|0|eth2|eth2,eth3|eth2,eth3|
 +|172.31.92.82|1||eth5|eth4,eth5|
 +|172.31.92.83|0|eth5|eth5|eth4,eth5|
 +|172.31.92.84|1||eth5|eth4,eth5|
 +|172.31.92.85|0|eth5|eth5|eth4,eth5|
- 	</pre></div></div><div class="refsect2"><a name="idp55829760"></a><h3>ipinfo <em class="parameter"><code>IP</code></em></h3><p>
++	</pre></div></div><div class="refsect2"><a name="idp54741296"></a><h3>ipinfo <em class="parameter"><code>IP</code></em></h3><p>
 +	This command will display details about the specified public addresses.
-       </p><div class="refsect3"><a name="idp55831376"></a><h4>Example</h4><pre class="screen">
++      </p><div class="refsect3"><a name="idp54742912"></a><h4>Example</h4><pre class="screen">
 +# ctdb ipinfo 172.31.92.85
 +Public IP[172.31.92.85] info on node 0
 +IP:172.31.92.85
 +CurrentNode:0
 +NumInterfaces:2
 +Interface[1]: Name:eth4 Link:down References:0
 +Interface[2]: Name:eth5 Link:up References:2 (active)
- 	</pre></div></div><div class="refsect2"><a name="idp55833120"></a><h3>scriptstatus</h3><p>
++	</pre></div></div><div class="refsect2"><a name="idp54744656"></a><h3>scriptstatus</h3><p>
 +	This command displays which scripts where run in the previous monitoring cycle and the result of each script. If a script failed with an error, causing the node to become unhealthy, the output from that script is also shown.
-       </p><div class="refsect3"><a name="idp55834400"></a><h4>Example</h4><pre class="screen">
++      </p><div class="refsect3"><a name="idp54745936"></a><h4>Example</h4><pre class="screen">
 +# ctdb scriptstatus
 +7 scripts were executed last monitoring cycle
 +00.ctdb              Status:OK    Duration:0.056 Tue Mar 24 18:56:57 2009
 +10.interface         Status:OK    Duration:0.077 Tue Mar 24 18:56:57 2009
 +11.natgw             Status:OK    Duration:0.039 Tue Mar 24 18:56:57 2009
 +20.multipathd        Status:OK    Duration:0.038 Tue Mar 24 18:56:57 2009
 +31.clamd             Status:DISABLED
 +40.vsftpd            Status:OK    Duration:0.045 Tue Mar 24 18:56:57 2009
 +41.httpd             Status:OK    Duration:0.039 Tue Mar 24 18:56:57 2009
 +50.samba             Status:ERROR    Duration:0.082 Tue Mar 24 18:56:57 2009
 +OUTPUT:ERROR: Samba tcp port 445 is not responding
-       </pre></div></div><div class="refsect2"><a name="idp55836624"></a><h3>disablescript <em class="parameter"><code>SCRIPT</code></em></h3><p>
++      </pre></div></div><div class="refsect2"><a name="idp54748160"></a><h3>disablescript <em class="parameter"><code>SCRIPT</code></em></h3><p>
 +	This command is used to disable an eventscript.
 +      </p><p>
 +	This will take effect the next time the eventscripts are being executed so it can take a short while until this is reflected in 'scriptstatus'.
-       </p></div><div class="refsect2"><a name="idp55838832"></a><h3>enablescript <em class="parameter"><code>SCRIPT</code></em></h3><p>
++      </p></div><div class="refsect2"><a name="idp54750368"></a><h3>enablescript <em class="parameter"><code>SCRIPT</code></em></h3><p>
 +	This command is used to enable an eventscript.
 +      </p><p>
 +	This will take effect the next time the eventscripts are being executed so it can take a short while until this is reflected in 'scriptstatus'.
-       </p></div><div class="refsect2"><a name="idp55841040"></a><h3>listvars</h3><p>
++      </p></div><div class="refsect2"><a name="idp54752576"></a><h3>listvars</h3><p>
 +	List all tuneable variables, except the values of the obsolete tunables
 +	like VacuumMinInterval. The obsolete tunables can be retrieved only
 +	explicitly with the "ctdb getvar" command.
-       </p><div class="refsect3"><a name="idp55842272"></a><h4>Example</h4><pre class="screen">
++      </p><div class="refsect3"><a name="idp54753808"></a><h4>Example</h4><pre class="screen">
 +# ctdb listvars
 +MaxRedirectCount        = 3
 +SeqnumInterval          = 1000
 +ControlTimeout          = 60
 +TraverseTimeout         = 20
 +KeepaliveInterval       = 5
 +KeepaliveLimit          = 5
 +RecoverTimeout          = 20
 +RecoverInterval         = 1
 +ElectionTimeout         = 3
 +TakeoverTimeout         = 9
 +MonitorInterval         = 15
 +TickleUpdateInterval    = 20
 +EventScriptTimeout      = 30
 +EventScriptTimeoutCount = 1
 +RecoveryGracePeriod     = 120
 +RecoveryBanPeriod       = 300
 +DatabaseHashSize        = 100001
 +DatabaseMaxDead         = 5
 +RerecoveryTimeout       = 10
 +EnableBans              = 1
 +DeterministicIPs        = 0
 +LCP2PublicIPs           = 1
 +ReclockPingPeriod       = 60
 +NoIPFailback            = 0
 +DisableIPFailover       = 0
 +VerboseMemoryNames      = 0
 +RecdPingTimeout         = 60
 +RecdFailCount           = 10
 +LogLatencyMs            = 0
 +RecLockLatencyMs        = 1000
 +RecoveryDropAllIPs      = 120
 +VacuumInterval          = 10
 +VacuumMaxRunTime        = 30
 +RepackLimit             = 10000
 +VacuumLimit             = 5000
 +VacuumFastPathCount     = 60
 +MaxQueueDropMsg         = 1000000
 +UseStatusEvents         = 0
 +AllowUnhealthyDBRead    = 0
 +StatHistoryInterval     = 1
 +DeferredAttachTO        = 120
 +AllowClientDBAttach     = 1
 +RecoverPDBBySeqNum      = 0
- 	</pre></div></div><div class="refsect2"><a name="idp55846336"></a><h3>getvar <em class="parameter"><code>NAME</code></em></h3><p>
++	</pre></div></div><div class="refsect2"><a name="idp54757872"></a><h3>getvar <em class="parameter"><code>NAME</code></em></h3><p>
 +	Get the runtime value of a tuneable variable.
-       </p><div class="refsect3"><a name="idp55847856"></a><h4>Example</h4><pre class="screen">
++      </p><div class="refsect3"><a name="idp54759392"></a><h4>Example</h4><pre class="screen">
 +# ctdb getvar MaxRedirectCount
 +MaxRedirectCount    = 3
- 	</pre></div></div><div class="refsect2"><a name="idp55849376"></a><h3>setvar <em class="parameter"><code>NAME</code></em> <em class="parameter"><code>VALUE</code></em></h3><p>
++	</pre></div></div><div class="refsect2"><a name="idp54760912"></a><h3>setvar <em class="parameter"><code>NAME</code></em> <em class="parameter"><code>VALUE</code></em></h3><p>
 +	Set the runtime value of a tuneable variable.
 +      </p><p>
 +	Example: ctdb setvar MaxRedirectCount 5
-       </p></div><div class="refsect2"><a name="idp55852032"></a><h3>lvsmaster</h3><p>
++      </p></div><div class="refsect2"><a name="idp54763568"></a><h3>lvsmaster</h3><p>
 +	This command shows which node is currently the LVSMASTER. The
 +	LVSMASTER is the node in the cluster which drives the LVS system and
 +	which receives all incoming traffic from clients.
 +      </p><p>
 +	LVS is the mode where the entire CTDB/Samba cluster uses a single
 +	ip address for the entire cluster. In this mode all clients connect to
 +	one specific node which will then multiplex/loadbalance the clients
 +	evenly onto the other nodes in the cluster. This is an alternative to using
 +	public ip addresses. See the manpage for ctdbd for more information
 +	about LVS.
-       </p></div><div class="refsect2"><a name="idp55854160"></a><h3>lvs</h3><p>
++      </p></div><div class="refsect2"><a name="idp54765696"></a><h3>lvs</h3><p>
 +	This command shows which nodes in the cluster are currently active in the
 +	LVS configuration. I.e. which nodes we are currently loadbalancing
 +	the single ip address across.
 +      </p><p>
 +	LVS will by default only loadbalance across those nodes that are both
 +	LVS capable and also HEALTHY. Except if all nodes are UNHEALTHY in which
 +	case LVS will loadbalance across all UNHEALTHY nodes as well.
 +	LVS will never use nodes that are DISCONNECTED, STOPPED, BANNED or
 +	DISABLED.
 +      </p><p>
 +	Example output:
 +      </p><pre class="screen">
 +2:10.0.0.13
 +3:10.0.0.14
-       </pre></div><div class="refsect2"><a name="idp55857200"></a><h3>getcapabilities</h3><p>
++      </pre></div><div class="refsect2"><a name="idp54768736"></a><h3>getcapabilities</h3><p>
 +	This command shows the capabilities of the current node.  See
 +	the <em class="citetitle">CAPABILITIES</em> section in
 +	<span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span> for more details.
 +      </p><p>
 +	Example output:
 +      </p><pre class="screen">
 +RECMASTER: YES
 +LMASTER: YES
 +LVS: NO
 +NATGW: YES
-       </pre></div><div class="refsect2"><a name="idp55860720"></a><h3>statistics</h3><p>
++      </pre></div><div class="refsect2"><a name="idp54772176"></a><h3>statistics</h3><p>
 +        Collect statistics from the CTDB daemon about
 +        how many calls it has served.  Information about
 +        various fields in statistics can be found in
 +	<span class="citerefentry"><span class="refentrytitle">ctdb-statistics</span>(7)</span>.
-       </p><div class="refsect3"><a name="idp55862816"></a><h4>Example</h4><pre class="screen">
++      </p><div class="refsect3"><a name="idp54774272"></a><h4>Example</h4><pre class="screen">
 +# ctdb statistics
 +CTDB version 1
 +num_clients                        3
 +frozen                             0
 +recovering                         0
 +client_packets_sent           360489
 +client_packets_recv           360466
 +node_packets_sent             480931
 +node_packets_recv             240120
 +keepalive_packets_sent             4
 +keepalive_packets_recv             3
 +node
 +req_call                       2
 +reply_call                     2
 +req_dmaster                    0
 +reply_dmaster                  0
 +reply_error                    0
 +req_message                   42
 +req_control               120408
 +reply_control             360439
 +client
 +req_call                       2
 +req_message                   24
 +req_control               360440
 +timeouts
 +call                           0
 +control                        0
 +traverse                       0
 +total_calls                        2
 +pending_calls                      0
 +lockwait_calls                     0
 +pending_lockwait_calls             0
 +memory_used                     5040
 +max_hop_count                      0
 +max_call_latency                   4.948321 sec
 +max_lockwait_latency               0.000000 sec
- 	</pre></div></div><div class="refsect2"><a name="idp55865520"></a><h3>statisticsreset</h3><p>
++	</pre></div></div><div class="refsect2"><a name="idp54776976"></a><h3>statisticsreset</h3><p>
 +	This command is used to clear all statistics counters in a node.
 +      </p><p>
 +	Example: ctdb statisticsreset
-       </p></div><div class="refsect2"><a name="idp55867152"></a><h3>dbstatistics <em class="parameter"><code>DB</code></em></h3><p>
++      </p></div><div class="refsect2"><a name="idp54778608"></a><h3>dbstatistics <em class="parameter"><code>DB</code></em></h3><p>
 +	Display statistics about the database DB.  Information
 +	about various fields in dbstatistics can be found in
 +	<span class="citerefentry"><span class="refentrytitle">ctdb-statistics</span>(7)</span>.
-       </p><div class="refsect3"><a name="idp55869696"></a><h4>Example</h4><pre class="screen">
++      </p><div class="refsect3"><a name="idp54781152"></a><h4>Example</h4><pre class="screen">
 +# ctdb dbstatistics locking.tdb
 +DB Statistics: locking.tdb
 + ro_delegations                     0
 + ro_revokes                         0
 + locks
 +     total                      14356
 +     failed                         0
 +     current                        0
 +     pending                        0
 + hop_count_buckets: 28087 2 1 0 0 0 0 0 0 0 0 0 0 0 0 0
 + lock_buckets: 0 14188 38 76 32 19 3 0 0 0 0 0 0 0 0 0
 + locks_latency      MIN/AVG/MAX     0.001066/0.012686/4.202292 sec out of 14356
 + Num Hot Keys:     1
 +     Count:8 Key:ff5bd7cb3ee3822edc1f0000000000000000000000000000
- 	</pre></div></div><div class="refsect2"><a name="idp55871808"></a><h3>getreclock</h3><p>
++	</pre></div></div><div class="refsect2"><a name="idp54783264"></a><h3>getreclock</h3><p>
 +	Show the name of the recovery lock file, if any.
 +      </p><p>
 +	Example output:
 +      </p><pre class="screen">
 +	Reclock file:/clusterfs/.ctdb/recovery.lock
-       </pre></div><div class="refsect2"><a name="idp55874048"></a><h3>
++      </pre></div><div class="refsect2"><a name="idp54785424"></a><h3>
 +	setreclock [<span class="optional"><em class="parameter"><code>FILE</code></em></span>]
 +      </h3><p>
 +	FILE specifies the name of the recovery lock file.  If the
 +	recovery lock file is changed at run-time then this will cause
 +	a recovery, which in turn causes the recovery lock to be
 +	retaken.
 +      </p><p>
 +	If no FILE is specified then a recovery lock file will no
 +	longer be used.
 +      </p><p>
 +	This command only affects the run-time setting of a single
 +	CTDB node.  This setting <span class="emphasis"><em>must</em></span> be changed
 +	on all nodes simultaneously by specifying <code class="option">-n
 +	all</code> (or similar).  For information about configuring
 +	the recovery lock file please see the
 +	<em class="citetitle">CTDB_RECOVERY_LOCK</em> entry in
 +	<span class="citerefentry"><span class="refentrytitle">ctdbd.conf</span>(5)</span> and the
 +	<em class="citetitle">--reclock</em> entry in
 +	<span class="citerefentry"><span class="refentrytitle">ctdbd</span>(1)</span>.  For information
 +	about the recovery lock please see the <em class="citetitle">RECOVERY
 +	LOCK</em> section in
 +	<span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span>.
-       </p></div><div class="refsect2"><a name="idp55881920"></a><h3>getdebug</h3><p>
++      </p></div><div class="refsect2"><a name="idp54793296"></a><h3>getdebug</h3><p>
 +	Get the current debug level for the node. the debug level controls what information is written to the log file.
 +      </p><p>
 +	The debug levels are mapped to the corresponding syslog levels.
 +	When a debug level is set, only those messages at that level and higher
 +	levels will be printed.
 +      </p><p>
 +	The list of debug levels from highest to lowest are :
 +      </p><p>
 +	ERR WARNING NOTICE INFO DEBUG
-       </p></div><div class="refsect2"><a name="idp55884640"></a><h3>setdebug <em class="parameter"><code>DEBUGLEVEL</code></em></h3><p>
++      </p></div><div class="refsect2"><a name="idp54796016"></a><h3>setdebug <em class="parameter"><code>DEBUGLEVEL</code></em></h3><p>
 +	Set the debug level of a node. This controls what information will be logged.
 +      </p><p>
 +	The debuglevel is one of ERR WARNING NOTICE INFO DEBUG
-       </p></div><div class="refsect2"><a name="idp55886848"></a><h3>getpid</h3><p>
++      </p></div><div class="refsect2"><a name="idp54798224"></a><h3>getpid</h3><p>
 +	This command will return the process id of the ctdb daemon.
-       </p></div><div class="refsect2"><a name="idp55888080"></a><h3>disable</h3><p>
++      </p></div><div class="refsect2"><a name="idp54799456"></a><h3>disable</h3><p>
 +	This command is used to administratively disable a node in the cluster.
 +	A disabled node will still participate in the cluster and host
 +	clustered TDB records but its public ip address has been taken over by
 +	a different node and it no longer hosts any services.
-       </p></div><div class="refsect2"><a name="idp55889520"></a><h3>enable</h3><p>
++      </p></div><div class="refsect2"><a name="idp54800896"></a><h3>enable</h3><p>
 +	Re-enable a node that has been administratively disabled.
-       </p></div><div class="refsect2"><a name="idp55890752"></a><h3>stop</h3><p>
++      </p></div><div class="refsect2"><a name="idp54802128"></a><h3>stop</h3><p>
 +	This command is used to administratively STOP a node in the cluster.
 +	A STOPPED node is connected to the cluster but will not host any
 +	public ip addresse, nor does it participate in the VNNMAP.
 +	The difference between a DISABLED node and a STOPPED node is that
 +	a STOPPED node does not host any parts of the database which means
 +	that a recovery is required to stop/continue nodes.
-       </p></div><div class="refsect2"><a name="idp55892304"></a><h3>continue</h3><p>
++      </p></div><div class="refsect2"><a name="idp54803680"></a><h3>continue</h3><p>
 +	Re-start a node that has been administratively stopped.
-       </p></div><div class="refsect2"><a name="idp55893536"></a><h3>addip <em class="parameter"><code>IPADDR</code></em>/<em class="parameter"><code>mask</code></em> <em class="parameter"><code>IFACE</code></em></h3><p>
++      </p></div><div class="refsect2"><a name="idp54804912"></a><h3>addip <em class="parameter"><code>IPADDR</code></em>/<em class="parameter"><code>mask</code></em> <em class="parameter"><code>IFACE</code></em></h3><p>
 +	This command is used to add a new public ip to a node during runtime.
 +	This allows public addresses to be added to a cluster without having
 +	to restart the ctdb daemons.
 +      </p><p>
 +	Note that this only updates the runtime instance of ctdb. Any changes will be lost next time ctdb is restarted and the public addresses file is re-read.
 +	If you want this change to be permanent you must also update the public addresses file manually.
-       </p></div><div class="refsect2"><a name="idp55897280"></a><h3>delip <em class="parameter"><code>IPADDR</code></em></h3><p>
++      </p></div><div class="refsect2"><a name="idp54808656"></a><h3>delip <em class="parameter"><code>IPADDR</code></em></h3><p>
 +	This command is used to remove a public ip from a node during runtime.
 +	If this public ip is currently hosted by the node it being removed from, the ip will first be failed over to another node, if possible, before it is removed.
 +      </p><p>
 +	Note that this only updates the runtime instance of ctdb. Any changes will be lost next time ctdb is restarted and the public addresses file is re-read.
 +	If you want this change to be permanent you must also update the public addresses file manually.
-       </p></div><div class="refsect2"><a name="idp55899840"></a><h3>moveip <em class="parameter"><code>IPADDR</code></em> <em class="parameter"><code>PNN</code></em></h3><p>
++      </p></div><div class="refsect2"><a name="idp54811216"></a><h3>moveip <em class="parameter"><code>IPADDR</code></em> <em class="parameter"><code>PNN</code></em></h3><p>
 +	This command can be used to manually fail a public ip address to a
 +	specific node.
 +      </p><p>
 +	In order to manually override the "automatic" distribution of public 
 +	ip addresses that ctdb normally provides, this command only works
 +	when you have changed the tunables for the daemon to:
 +      </p><p>
 +	DeterministicIPs = 0
 +      </p><p>
 +	NoIPFailback = 1
-       </p></div><div class="refsect2"><a name="idp55903600"></a><h3>shutdown</h3><p>
++      </p></div><div class="refsect2"><a name="idp54814976"></a><h3>shutdown</h3><p>
 +	This command will shutdown a specific CTDB daemon.
-       </p></div><div class="refsect2"><a name="idp55904832"></a><h3>setlmasterrole on|off</h3><p>
++      </p></div><div class="refsect2"><a name="idp54816208"></a><h3>setlmasterrole on|off</h3><p>
 +	This command is used ot enable/disable the LMASTER capability for a node at runtime. This capability determines whether or not a node can be used as an LMASTER for records in the database. A node that does not have the LMASTER capability will not show up in the vnnmap.
 +      </p><p>
 +	Nodes will by default have this capability, but it can be stripped off nodes by the setting in the sysconfig file or by using this command.
 +      </p><p>
 +	Once this setting has been enabled/disabled, you need to perform a recovery for it to take effect.
 +      </p><p>
 +	See also "ctdb getcapabilities"
-       </p></div><div class="refsect2"><a name="idp55907712"></a><h3>setrecmasterrole on|off</h3><p>
++      </p></div><div class="refsect2"><a name="idp54819088"></a><h3>setrecmasterrole on|off</h3><p>
 +	This command is used ot enable/disable the RECMASTER capability for a node at runtime. This capability determines whether or not a node can be used as an RECMASTER for the cluster. A node that does not have the RECMASTER capability can not win a recmaster election. A node that already is the recmaster for the cluster when the capability is stripped off the node will remain the recmaster until the next cluster election.
 +      </p><p>
 +	Nodes will by default have this capability, but it can be stripped off nodes by the setting in the sysconfig file or by using this command.
 +      </p><p>
 +	See also "ctdb getcapabilities"
-       </p></div><div class="refsect2"><a name="idp55910240"></a><h3>reloadnodes</h3><p>
++      </p></div><div class="refsect2"><a name="idp54821616"></a><h3>reloadnodes</h3><p>
 +	This command is used when adding new nodes, or removing existing nodes from an existing cluster.
 +      </p><p>
 +	Procedure to add a node:
 +      </p><p>
 +	1, To expand an existing cluster, first ensure with 'ctdb status' that
 +	all nodes are up and running and that they are all healthy.
 +	Do not try to expand a cluster unless it is completely healthy!
 +      </p><p>
 +	2, On all nodes, edit /etc/ctdb/nodes and add the new node as the last
 +	entry to the file. The new node MUST be added to the end of this file!
 +      </p><p>
 +	3, Verify that all the nodes have identical /etc/ctdb/nodes files after you edited them and added the new node!
 +      </p><p>
 +	4, Run 'ctdb reloadnodes' to force all nodes to reload the nodesfile.
 +      </p><p>
 +	5, Use 'ctdb status' on all nodes and verify that they now show the additional node.
 +      </p><p>
 +	6, Install and configure the new node and bring it online.
 +      </p><p>
 +	Procedure to remove a node:
 +      </p><p>
 +	1, To remove a node from an existing cluster, first ensure with 'ctdb status' that
 +	all nodes, except the node to be deleted, are up and running and that they are all healthy.
 +	Do not try to remove a node from a cluster unless the cluster is completely healthy!
 +      </p><p>
 +	2, Shutdown and poweroff the node to be removed.
 +      </p><p>
 +	3, On all other nodes, edit the /etc/ctdb/nodes file and comment out the node to be removed. Do not delete the line for that node, just comment it out by adding a '#' at the beginning of the line.
 +      </p><p>
 +	4, Run 'ctdb reloadnodes' to force all nodes to reload the nodesfile.
 +      </p><p>
 +	5, Use 'ctdb status' on all nodes and verify that the deleted node no longer shows up in the list..
 +      </p><p>
-       </p></div><div class="refsect2"><a name="idp55918528"></a><h3>
++      </p></div><div class="refsect2"><a name="idp54829904"></a><h3>
 +	reloadips
 +	[<span class="optional"><em class="parameter"><code>PNN-LIST</code></em></span>]
 +      </h3><p>
 +	This command reloads the public addresses configuration file
 +	on the specified nodes.  When it completes addresses will be
 +	reconfigured and reassigned across the cluster as necessary.
-       </p></div><div class="refsect2"><a name="idp55920640"></a><h3>getdbmap</h3><p>
++      </p></div><div class="refsect2"><a name="idp54832016"></a><h3>getdbmap</h3><p>
 +	This command lists all clustered TDB databases that the CTDB daemon has attached to. Some databases are flagged as PERSISTENT, this means that the database stores data persistently and the data will remain across reboots. One example of such a database is secrets.tdb where information about how the cluster was joined to the domain is stored.
 +      </p><p>
 +	If a PERSISTENT database is not in a healthy state the database is
 +	flagged as UNHEALTHY. If there's at least one completely healthy node running in
 +	the cluster, it's possible that the content is restored by a recovery
 +	run automaticly. Otherwise an administrator needs to analyze the
 +	problem.
 +      </p><p>
 +	See also "ctdb getdbstatus", "ctdb backupdb", "ctdb restoredb",
 +	"ctdb dumpbackup", "ctdb wipedb", "ctdb setvar AllowUnhealthyDBRead 1"
 +	and (if samba or tdb-utils are installed) "tdbtool check".
 +      </p><p>
 +	Most databases are not persistent and only store the state information that the currently running samba daemons need. These databases are always wiped when ctdb/samba starts and when a node is rebooted.
-       </p><div class="refsect3"><a name="idp55923952"></a><h4>Example</h4><pre class="screen">
++      </p><div class="refsect3"><a name="idp54835328"></a><h4>Example</h4><pre class="screen">
 +# ctdb getdbmap
 +Number of databases:10
 +dbid:0x435d3410 name:notify.tdb path:/var/ctdb/notify.tdb.0 
 +dbid:0x42fe72c5 name:locking.tdb path:/var/ctdb/locking.tdb.0
 +dbid:0x1421fb78 name:brlock.tdb path:/var/ctdb/brlock.tdb.0 
 +dbid:0x17055d90 name:connections.tdb path:/var/ctdb/connections.tdb.0 
 +dbid:0xc0bdde6a name:sessionid.tdb path:/var/ctdb/sessionid.tdb.0 
 +dbid:0x122224da name:test.tdb path:/var/ctdb/test.tdb.0 
 +dbid:0x2672a57f name:idmap2.tdb path:/var/ctdb/persistent/idmap2.tdb.0 PERSISTENT
 +dbid:0xb775fff6 name:secrets.tdb path:/var/ctdb/persistent/secrets.tdb.0 PERSISTENT
 +dbid:0xe98e08b6 name:group_mapping.tdb path:/var/ctdb/persistent/group_mapping.tdb.0 PERSISTENT
 +dbid:0x7bbbd26c name:passdb.tdb path:/var/ctdb/persistent/passdb.tdb.0 PERSISTENT
 +
 +# ctdb getdbmap  # example for unhealthy database
 +Number of databases:1
 +dbid:0xb775fff6 name:secrets.tdb path:/var/ctdb/persistent/secrets.tdb.0 PERSISTENT UNHEALTHY
 +
 +# ctdb -X getdbmap
 +|ID|Name|Path|Persistent|Unhealthy|
 +|0x7bbbd26c|passdb.tdb|/var/ctdb/persistent/passdb.tdb.0|1|0|
- 	</pre></div></div><div class="refsect2"><a name="idp55926544"></a><h3>
++	</pre></div></div><div class="refsect2"><a name="idp54837920"></a><h3>
 +	backupdb
 +	<em class="parameter"><code>DB</code></em>
 +	<em class="parameter"><code>FILE</code></em>
 +      </h3><p>
 +	Copy the contents of database DB to FILE.  FILE can later be
 +	read back using <span class="command"><strong>restoredb</strong></span>.  This is mainly
 +	useful for backing up persistent databases such as
 +	<code class="filename">secrets.tdb</code> and similar.
-       </p></div><div class="refsect2"><a name="idp55930368"></a><h3>
++      </p></div><div class="refsect2"><a name="idp54841744"></a><h3>
 +	restoredb
 +	<em class="parameter"><code>FILE</code></em>
 +	[<span class="optional"><em class="parameter"><code>DB</code></em></span>]
 +      </h3><p>
 +	This command restores a persistent database that was
 +	previously backed up using backupdb.  By default the data will
 +	be restored back into the same database as it was created
 +	from. By specifying dbname you can restore the data into a
 +	different database.
-       </p></div><div class="refsect2"><a name="idp55933184"></a><h3>setdbreadonly <em class="parameter"><code>DB</code></em></h3><p>
++      </p></div><div class="refsect2"><a name="idp54844560"></a><h3>setdbreadonly <em class="parameter"><code>DB</code></em></h3><p>
 +	This command will enable the read-only record support for a
 +	database.  This is an experimental feature to improve
 +	performance for contended records primarily in locking.tdb and
 +	brlock.tdb.  When enabling this feature you must set it on all
 +	nodes in the cluster.
-       </p></div><div class="refsect2"><a name="idp55935120"></a><h3>setdbsticky <em class="parameter"><code>DB</code></em></h3><p>
++      </p></div><div class="refsect2"><a name="idp54846496"></a><h3>setdbsticky <em class="parameter"><code>DB</code></em></h3><p>
 +	This command will enable the sticky record support for the
 +	specified database.  This is an experimental feature to
 +	improve performance for contended records primarily in
 +	locking.tdb and brlock.tdb.  When enabling this feature you
 +	must set it on all nodes in the cluster.
-       </p></div></div><div class="refsect1"><a name="idp55937200"></a><h2>INTERNAL COMMANDS</h2><p>
++      </p></div></div><div class="refsect1"><a name="idp54848576"></a><h2>INTERNAL COMMANDS</h2><p>
 +      Internal commands are used by CTDB's scripts and are not
 +      required for managing a CTDB cluster.  Their parameters and
 +      behaviour are subject to change.
-     </p><div class="refsect2"><a name="idp55938416"></a><h3>gettickles <em class="parameter"><code>IPADDR</code></em></h3><p>
++    </p><div class="refsect2"><a name="idp54849792"></a><h3>gettickles <em class="parameter"><code>IPADDR</code></em></h3><p>
 +	Show TCP connections that are registered with CTDB to be
 +	"tickled" if there is a failover.
-       </p></div><div class="refsect2"><a name="idp55940176"></a><h3>gratiousarp <em class="parameter"><code>IPADDR</code></em> <em class="parameter"><code>INTERFACE</code></em></h3><p>
++      </p></div><div class="refsect2"><a name="idp54851552"></a><h3>gratiousarp <em class="parameter"><code>IPADDR</code></em> <em class="parameter"><code>INTERFACE</code></em></h3><p>
 +	Send out a gratious ARP for the specified interface through
 +	the specified interface. This command is mainly used by the
 +	ctdb eventscripts.
-       </p></div><div class="refsect2"><a name="idp55942608"></a><h3>killtcp</h3><p>
++      </p></div><div class="refsect2"><a name="idp54853984"></a><h3>killtcp</h3><p>
 +	Read a list of TCP connections, one per line, from standard
 +	input and terminate each connection.  A connection is
 +	specified as:
 +      </p><pre class="synopsis">
 +	<em class="parameter"><code>SRC-IPADDR</code></em>:<em class="parameter"><code>SRC-PORT</code></em> <em class="parameter"><code>DST-IPADDR</code></em>:<em class="parameter"><code>DST-PORT</code></em>
 +      </pre><p>
 +	Each connection is terminated by issuing a TCP RST to the
 +	SRC-IPADDR:SRC-PORT endpoint.
 +      </p><p>
 +	A single connection can be specified on the command-line
 +	rather than on standard input.
-       </p></div><div class="refsect2"><a name="idp55948032"></a><h3>
++      </p></div><div class="refsect2"><a name="idp54859408"></a><h3>
 +	pdelete <em class="parameter"><code>DB</code></em> <em class="parameter"><code>KEY</code></em>
 +      </h3><p>
 +	Delete KEY from DB.
-       </p></div><div class="refsect2"><a name="idp55950432"></a><h3>
++      </p></div><div class="refsect2"><a name="idp54861808"></a><h3>
 +	pfetch <em class="parameter"><code>DB</code></em> <em class="parameter"><code>KEY</code></em>
 +      </h3><p>
 +	Print the value associated with KEY in DB.
-       </p></div><div class="refsect2"><a name="idp55952832"></a><h3>
++      </p></div><div class="refsect2"><a name="idp54864208"></a><h3>
 +	pstore
 +	<em class="parameter"><code>DB</code></em>
 +	<em class="parameter"><code>KEY</code></em>
 +	<em class="parameter"><code>FILE</code></em>
 +      </h3><p>
 +	Store KEY in DB with contents of FILE as the associated value.
-       </p></div><div class="refsect2"><a name="idp55955936"></a><h3>
++      </p></div><div class="refsect2"><a name="idp54867312"></a><h3>
 +	ptrans
 +	<em class="parameter"><code>DB</code></em>
 +	[<span class="optional"><em class="parameter"><code>FILE</code></em></span>]
 +      </h3><p>
 +	Read a list of key-value pairs, one per line from FILE, and
 +	store them in DB using a single transaction.  An empty value
 +	is equivalent to deleting the given key.
 +      </p><p>
 +	The key and value should be separated by spaces or tabs. Each
 +	key/value should be a printable string enclosed in
 +	double-quotes.
-       </p></div><div class="refsect2"><a name="idp55959200"></a><h3>runstate [setup|first_recovery|startup|running]</h3><p>
++      </p></div><div class="refsect2"><a name="idp54870576"></a><h3>runstate [setup|first_recovery|startup|running]</h3><p>
 +	Print the runstate of the specified node.  Runstates are used
 +	to serialise important state transitions in CTDB, particularly
 +	during startup.
 +      </p><p>
 +	If one or more optional runstate arguments are specified then
 +	the node must be in one of these runstates for the command to
 +	succeed.
-       </p><div class="refsect3"><a name="idp55960928"></a><h4>Example</h4><pre class="screen">
++      </p><div class="refsect3"><a name="idp54872304"></a><h4>Example</h4><pre class="screen">
 +# ctdb runstate
 +RUNNING
- 	</pre></div></div><div class="refsect2"><a name="idp55962448"></a><h3>setifacelink <em class="parameter"><code>IFACE</code></em> up|down</h3><p>
++	</pre></div></div><div class="refsect2"><a name="idp54873824"></a><h3>setifacelink <em class="parameter"><code>IFACE</code></em> up|down</h3><p>
 +	Set the internal state of network interface IFACE.  This is
 +	typically used in the <code class="filename">10.interface</code> script
 +	in the "monitor" event.
 +      </p><p>
 +	Example: ctdb setifacelink eth0 up
-       </p></div><div class="refsect2"><a name="idp55965328"></a><h3>setnatgwstate on|off</h3><p>
++      </p></div><div class="refsect2"><a name="idp54876704"></a><h3>setnatgwstate on|off</h3><p>
 +	Enable or disable the NAT gateway master capability on a node.
-       </p></div><div class="refsect2"><a name="idp55966560"></a><h3>tickle <em class="parameter"><code>SRC-IPADDR</code></em>:<em class="parameter"><code>SRC-PORT</code></em> <em class="parameter"><code>DST-IPADDR</code></em>:<em class="parameter"><code>DST-PORT</code></em></h3><p>
++      </p></div><div class="refsect2"><a name="idp54877936"></a><h3>tickle <em class="parameter"><code>SRC-IPADDR</code></em>:<em class="parameter"><code>SRC-PORT</code></em> <em class="parameter"><code>DST-IPADDR</code></em>:<em class="parameter"><code>DST-PORT</code></em></h3><p>
 +	Send a TCP tickle to the source host for the specified TCP
 +	connection.  A TCP tickle is a TCP ACK packet with an invalid
 +	sequence and acknowledge number and will when received by the
 +	source host result in it sending an immediate correct ACK back
 +	to the other end.
 +      </p><p>
 +	TCP tickles are useful to "tickle" clients after a IP failover has
 +	occured since this will make the client immediately recognize the
 +	TCP connection has been disrupted and that the client will need
 +	to reestablish. This greatly speeds up the time it takes for a client
 +	to detect and reestablish after an IP failover in the ctdb cluster.
-       </p></div><div class="refsect2"><a name="idp55971120"></a><h3>version</h3><p>
++      </p></div><div class="refsect2"><a name="idp54882496"></a><h3>version</h3><p>
 +	Display the CTDB version.
-       </p></div></div><div class="refsect1"><a name="idp55972400"></a><h2>DEBUGGING COMMANDS</h2><p>
++      </p></div></div><div class="refsect1"><a name="idp54883776"></a><h2>DEBUGGING COMMANDS</h2><p>
 +      These commands are primarily used for CTDB development and testing and
 +      should not be used for normal administration.
-     </p><div class="refsect2"><a name="idp55973568"></a><h3>OPTIONS</h3><div class="variablelist"><dl class="variablelist"><dt><span class="term">--print-emptyrecords</span></dt><dd><p>
++    </p><div class="refsect2"><a name="idp54884944"></a><h3>OPTIONS</h3><div class="variablelist"><dl class="variablelist"><dt><span class="term">--print-emptyrecords</span></dt><dd><p>
 +	    This enables printing of empty records when dumping databases
 +	    with the catdb, cattbd and dumpdbbackup commands. Records with
 +	    empty data segment are considered deleted by ctdb and cleaned
 +	    by the vacuuming mechanism, so this switch can come in handy for
 +	    debugging the vacuuming behaviour.
 +	  </p></dd><dt><span class="term">--print-datasize</span></dt><dd><p>
 +	    This lets database dumps (catdb, cattdb, dumpdbbackup) print the
 +	    size of the record data instead of dumping the data contents.
 +	  </p></dd><dt><span class="term">--print-lmaster</span></dt><dd><p>
 +	    This lets catdb print the lmaster for each record.
 +	  </p></dd><dt><span class="term">--print-hash</span></dt><dd><p>
 +	    This lets database dumps (catdb, cattdb, dumpdbbackup) print the
 +	    hash for each record.
 +	  </p></dd><dt><span class="term">--print-recordflags</span></dt><dd><p>
 +	    This lets catdb and dumpdbbackup print the
 +	    record flags for each record. Note that cattdb always
 +	    prints the flags.
- 	  </p></dd></dl></div></div><div class="refsect2"><a name="idp55982592"></a><h3>process-exists <em class="parameter"><code>PID</code></em></h3><p>
++	  </p></dd></dl></div></div><div class="refsect2"><a name="idp54893968"></a><h3>process-exists <em class="parameter"><code>PID</code></em></h3><p>
 +	This command checks if a specific process exists on the CTDB host. This is mainly used by Samba to check if remote instances of samba are still running or not.
-       </p></div><div class="refsect2"><a name="idp55984432"></a><h3>getdbstatus <em class="parameter"><code>DB</code></em></h3><p>
++      </p></div><div class="refsect2"><a name="idp54895808"></a><h3>getdbstatus <em class="parameter"><code>DB</code></em></h3><p>
 +	This command displays more details about a database.
-       </p><div class="refsect3"><a name="idp55986032"></a><h4>Example</h4><pre class="screen">
++      </p><div class="refsect3"><a name="idp54897408"></a><h4>Example</h4><pre class="screen">
 +# ctdb getdbstatus test.tdb.0
 +dbid: 0x122224da
 +name: test.tdb
 +path: /var/ctdb/test.tdb.0
 +PERSISTENT: no
 +HEALTH: OK
 +
 +# ctdb getdbstatus registry.tdb  # with a corrupted TDB
 +dbid: 0xf2a58948
 +name: registry.tdb
 +path: /var/ctdb/persistent/registry.tdb.0
 +PERSISTENT: yes
 +HEALTH: NO-HEALTHY-NODES - ERROR - Backup of corrupted TDB in '/var/ctdb/persistent/registry.tdb.0.corrupted.20091208091949.0Z'
- 	</pre></div></div><div class="refsect2"><a name="idp55987968"></a><h3>catdb <em class="parameter"><code>DB</code></em></h3><p>
++	</pre></div></div><div class="refsect2"><a name="idp54899344"></a><h3>catdb <em class="parameter"><code>DB</code></em></h3><p>
 +	Print a dump of the clustered TDB database DB.
-       </p></div><div class="refsect2"><a name="idp55989616"></a><h3>cattdb <em class="parameter"><code>DB</code></em></h3><p>
++      </p></div><div class="refsect2"><a name="idp54900992"></a><h3>cattdb <em class="parameter"><code>DB</code></em></h3><p>
 +	Print a dump of the contents of the local TDB database DB.
-       </p></div><div class="refsect2"><a name="idp55991344"></a><h3>dumpdbbackup <em class="parameter"><code>FILE</code></em></h3><p>
++      </p></div><div class="refsect2"><a name="idp54902720"></a><h3>dumpdbbackup <em class="parameter"><code>FILE</code></em></h3><p>
 +	Print a dump of the contents from database backup FILE,
 +	similar to <span class="command"><strong>catdb</strong></span>.
-       </p></div><div class="refsect2"><a name="idp55993696"></a><h3>wipedb <em class="parameter"><code>DB</code></em></h3><p>
++      </p></div><div class="refsect2"><a name="idp54905072"></a><h3>wipedb <em class="parameter"><code>DB</code></em></h3><p>
 +	Remove all contents of database DB.
-       </p></div><div class="refsect2"><a name="idp55995344"></a><h3>recover</h3><p>
++      </p></div><div class="refsect2"><a name="idp54906720"></a><h3>recover</h3><p>
 +	This command will trigger the recovery daemon to do a cluster
 +	recovery.
-       </p></div><div class="refsect2"><a name="idp55996592"></a><h3>ipreallocate, sync</h3><p>
++      </p></div><div class="refsect2"><a name="idp54907968"></a><h3>ipreallocate, sync</h3><p>
 +	This command will force the recovery master to perform a full ip reallocation process and redistribute all ip addresses. This is useful to "reset" the allocations back to its default state if they have been changed using the "moveip" command. While a "recover" will also perform this reallocation, a recovery is much more hevyweight since it will also rebuild all the databases.
-       </p></div><div class="refsect2"><a name="idp49074288"></a><h3>getmonmode</h3><p>
++      </p></div><div class="refsect2"><a name="idp48922336"></a><h3>getmonmode</h3><p>
 +	This command returns the monutoring mode of a node. The monitoring mode is either ACTIVE or DISABLED. Normally a node will continuously monitor that all other nodes that are expected are in fact connected and that they respond to commands.
 +      </p><p>
 +	ACTIVE - This is the normal mode. The node is actively monitoring all other nodes, both that the transport is connected and also that the node responds to commands. If a node becomes unavailable, it will be marked as DISCONNECTED and a recovery is initiated to restore the cluster.
 +      </p><p>
 +	DISABLED - This node is not monitoring that other nodes are available. In this mode a node failure will not be detected and no recovery will be performed. This mode is useful when for debugging purposes one wants to attach GDB to a ctdb process but wants to prevent the rest of the cluster from marking this node as DISCONNECTED and do a recovery.
-       </p></div><div class="refsect2"><a name="idp49077184"></a><h3>setmonmode 0|1</h3><p>
++      </p></div><div class="refsect2"><a name="idp48925200"></a><h3>setmonmode 0|1</h3><p>
 +	This command can be used to explicitly disable/enable monitoring mode on a node. The main purpose is if one wants to attach GDB to a running ctdb daemon but wants to prevent the other nodes from marking it as DISCONNECTED and issuing a recovery. To do this, set monitoring mode to 0 on all nodes before attaching with GDB. Remember to set monitoring mode back to 1 afterwards.
-       </p></div><div class="refsect2"><a name="idp49078768"></a><h3>attach <em class="parameter"><code>DBNAME</code></em> [persistent]</h3><p>
++      </p></div><div class="refsect2"><a name="idp48926784"></a><h3>attach <em class="parameter"><code>DBNAME</code></em> [persistent]</h3><p>
 +	Create a new CTDB database called DBNAME and attach to it on
 +	all nodes.
-       </p></div><div class="refsect2"><a name="idp49080768"></a><h3>detach <em class="parameter"><code>DB-LIST</code></em></h3><p>
++      </p></div><div class="refsect2"><a name="idp48928784"></a><h3>detach <em class="parameter"><code>DB-LIST</code></em></h3><p>
 +	Detach specified non-persistent database(s) from the cluster. This
 +	command will disconnect specified database(s) on all nodes in
 +	the cluster.  This command should only be used when none of the
 +	specified database(s) are in use.
 +      </p><p>
 +	All nodes should be active and tunable AllowClientDBAccess should
 +	be disabled on all nodes before detaching databases.
-       </p></div><div class="refsect2"><a name="idp49083296"></a><h3>dumpmemory</h3><p>
++      </p></div><div class="refsect2"><a name="idp48931312"></a><h3>dumpmemory</h3><p>
 +	This is a debugging command. This command will make the ctdb
 +	daemon to write a fill memory allocation map to standard output.
-       </p></div><div class="refsect2"><a name="idp49084624"></a><h3>rddumpmemory</h3><p>
++      </p></div><div class="refsect2"><a name="idp48932640"></a><h3>rddumpmemory</h3><p>
 +	This is a debugging command. This command will dump the talloc memory
 +	allocation tree for the recovery daemon to standard output.
-       </p></div><div class="refsect2"><a name="idp49085968"></a><h3>thaw</h3><p>
++      </p></div><div class="refsect2"><a name="idp48933984"></a><h3>thaw</h3><p>
 +	Thaw a previously frozen node.
-       </p></div><div class="refsect2"><a name="idp49087200"></a><h3>eventscript <em class="parameter"><code>ARGUMENTS</code></em></h3><p>
++      </p></div><div class="refsect2"><a name="idp48935216"></a><h3>eventscript <em class="parameter"><code>ARGUMENTS</code></em></h3><p>
 +	This is a debugging command. This command can be used to manually
 +	invoke and run the eventscritps with arbitrary arguments.
-       </p></div><div class="refsect2"><a name="idp49089088"></a><h3>ban <em class="parameter"><code>BANTIME</code></em></h3><p>
++      </p></div><div class="refsect2"><a name="idp48937104"></a><h3>ban <em class="parameter"><code>BANTIME</code></em></h3><p>
 +	Administratively ban a node for BANTIME seconds.  The node
 +	will be unbanned after BANTIME seconds have elapsed.
 +      </p><p>
 +	A banned node does not participate in the cluster.  It does
 +	not host any records for the clustered TDB and does not host
 +	any public IP addresses.
 +      </p><p>
 +	Nodes are automatically banned if they misbehave.  For
 +	example, a node may be banned if it causes too many cluster
 +	recoveries.
 +      </p><p>
 +	To administratively exclude a node from a cluster use the
 +	<span class="command"><strong>stop</strong></span> command.
-       </p></div><div class="refsect2"><a name="idp56032816"></a><h3>unban</h3><p>
++      </p></div><div class="refsect2"><a name="idp54944192"></a><h3>unban</h3><p>
 +	This command is used to unban a node that has either been
 +	administratively banned using the ban command or has been
 +	automatically banned.
-       </p></div><div class="refsect2"><a name="idp56034128"></a><h3>
++      </p></div><div class="refsect2"><a name="idp54945504"></a><h3>
 +	rebalancenode
 +	[<span class="optional"><em class="parameter"><code>PNN-LIST</code></em></span>]
 +      </h3><p>
 +	This command marks the given nodes as rebalance targets in the
 +	LCP2 IP allocation algorithm.  The
 +	<span class="command"><strong>reloadips</strong></span> command will do this as necessary
 +	so this command should not be needed.
-       </p></div><div class="refsect2"><a name="idp56036864"></a><h3>check_srvids <em class="parameter"><code>SRVID</code></em> ...</h3><p>
++      </p></div><div class="refsect2"><a name="idp54948240"></a><h3>check_srvids <em class="parameter"><code>SRVID</code></em> ...</h3><p>
 +	This command checks whether a set of srvid message ports are
 +	registered on the node or not. The command takes a list of
 +	values to check.
-       </p><div class="refsect3"><a name="idp56038672"></a><h4>Example</h4><pre class="screen">
++      </p><div class="refsect3"><a name="idp54950048"></a><h4>Example</h4><pre class="screen">
 +# ctdb check_srvids 1 2 3 14765
 +Server id 0:1 does not exist
 +Server id 0:2 does not exist
 +Server id 0:3 does not exist
 +Server id 0:14765 exists
- 	</pre></div></div></div><div class="refsect1"><a name="idp56040608"></a><h2>SEE ALSO</h2><p>
++	</pre></div></div></div><div class="refsect1"><a name="idp54951984"></a><h2>SEE ALSO</h2><p>
 +      <span class="citerefentry"><span class="refentrytitle">ctdbd</span>(1)</span>,
 +
 +      <span class="citerefentry"><span class="refentrytitle">onnode</span>(1)</span>,
 +
 +      <span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span>,
 +
 +      <span class="citerefentry"><span class="refentrytitle">ctdb-statistics</span>(7)</span>,
 +
 +      <span class="citerefentry"><span class="refentrytitle">ctdb-tunables</span>(7)</span>,
 +
 +      <a class="ulink" href="http://ctdb.samba.org/" target="_top">http://ctdb.samba.org/</a>
 +    </p></div></div></body></html>
diff --cc ctdb/doc/ctdb.7
index 91107cc,0000000..5a5211f
mode 100644,000000..100644
--- a/ctdb/doc/ctdb.7
+++ b/ctdb/doc/ctdb.7
@@@ -1,745 -1,0 +1,745 @@@
 +'\" t
 +.\"     Title: ctdb
 +.\"    Author: 
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 09/08/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: CTDB - clustered TDB database
 +.\"    Source: ctdb
 +.\"  Language: English
 +.\"
- .TH "CTDB" "7" "09/08/2015" "ctdb" "CTDB \- clustered TDB database"
++.TH "CTDB" "7" "12/10/2015" "ctdb" "CTDB \- clustered TDB database"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +ctdb \- Clustered TDB
 +.SH "DESCRIPTION"
 +.PP
 +CTDB is a clustered database component in clustered Samba that provides a high\-availability load\-sharing CIFS server cluster\&.
 +.PP
 +The main functions of CTDB are:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +Provide a clustered version of the TDB database with automatic rebuild/recovery of the databases upon node failures\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +Monitor nodes in the cluster and services running on each node\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +Manage a pool of public IP addresses that are used to provide services to clients\&. Alternatively, CTDB can be used with LVS\&.
 +.RE
 +.PP
 +Combined with a cluster filesystem CTDB provides a full high\-availablity (HA) environment for services such as clustered Samba, NFS and other services\&.
 +.SH "ANATOMY OF A CTDB CLUSTER"
 +.PP
 +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 storage (usually a cluster filesystem) that is accessible by all nodes\&.
 +.PP
 +CTDB provides an "all active" cluster, where services are load balanced across all nodes\&.
 +.SH "RECOVERY LOCK"
 +.PP
 +CTDB uses a
 +\fIrecovery lock\fR
 +to avoid a
 +\fIsplit brain\fR, where a cluster becomes partitioned and each partition attempts to operate independently\&. Issues that can result from a split brain include file data corruption, because file locking metadata may not be tracked correctly\&.
 +.PP
 +CTDB uses a
 +\fIcluster leader and follower\fR
 +model of cluster management\&. All nodes in a cluster elect one node to be the leader\&. The leader node coordinates privileged operations such as database recovery and IP address failover\&. CTDB refers to the leader node as the
 +\fIrecovery master\fR\&. This node takes and holds the recovery lock to assert its privileged role in the cluster\&.
 +.PP
 +The recovery lock is implemented using a file residing in shared storage (usually) on a cluster filesystem\&. To support a recovery lock the cluster filesystem must support lock coherence\&. See
 +\fBping_pong\fR(1)
 +for more details\&.
 +.PP
 +If a cluster becomes partitioned (for example, due to a communication failure) and a different recovery master is elected by the nodes in each partition, then only one of these recovery masters will be able to take the recovery lock\&. The recovery master in the "losing" partition will not be able to take the recovery lock and will be excluded from the cluster\&. The nodes in the "losing" partition will elect each node in turn as their recovery master so eventually all the nodes in that [...]
 +.PP
 +CTDB does sanity checks to ensure that the recovery lock is held as expected\&.
 +.PP
 +CTDB can run without a recovery lock but this is not recommended as there will be no protection from split brains\&.
 +.SH "PRIVATE VS PUBLIC ADDRESSES"
 +.PP
 +Each node in a CTDB cluster has multiple IP addresses assigned to it:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +A single private IP address that is used for communication between nodes\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +One or more public IP addresses that are used to provide NAS or other services\&.
 +.RE
 +.sp
 +.SS "Private address"
 +.PP
 +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 the cluster and is the address that CTDB daemons will use to communicate with the CTDB daemons on other nodes\&.
 +.PP
 +Private addresses are listed in the file specified by the
 +\fICTDB_NODES\fR
 +configuration variable (see
 +\fBctdbd.conf\fR(5), default
 +/etc/ctdb/nodes)\&. This file contains the list of private addresses for all nodes in the cluster, one per line\&. This file must be the same on all nodes in the cluster\&.
 +.PP
 +Private addresses should not be used by clients to connect to services provided by the cluster\&.
 +.PP
 +It is strongly recommended that the private addresses are configured on a private network that is separate from client networks\&.
 +.PP
 +Example
 +/etc/ctdb/nodes
 +for a four node cluster:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +192\&.168\&.1\&.1
 +192\&.168\&.1\&.2
 +192\&.168\&.1\&.3
 +192\&.168\&.1\&.4
 +      
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.SS "Public addresses"
 +.PP
 +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 node\&. Instead, they are managed by CTDB and are assigned to interfaces on physical nodes at runtime\&.
 +.PP
 +The CTDB cluster will assign/reassign these public addresses across the available healthy nodes in the cluster\&. When one node fails, its public addresses will be taken over by one or more other nodes in the cluster\&. This ensures that services provided by all public addresses are always available to clients, as long as there are nodes available capable of hosting this address\&.
 +.PP
 +The public address configuration is stored in a file on each node specified by the
 +\fICTDB_PUBLIC_ADDRESSES\fR
 +configuration variable (see
 +\fBctdbd.conf\fR(5), recommended
 +/etc/ctdb/public_addresses)\&. This file contains a list of the public addresses that the node is capable of hosting, one per line\&. Each entry also contains the netmask and the interface to which the address should be assigned\&.
 +.PP
 +Example
 +/etc/ctdb/public_addresses
 +for a node that can host 4 public addresses, on 2 different interfaces:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +10\&.1\&.1\&.1/24 eth1
 +10\&.1\&.1\&.2/24 eth1
 +10\&.1\&.2\&.1/24 eth2
 +10\&.1\&.2\&.2/24 eth2
 +      
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +In many cases the public addresses file will be the same on all nodes\&. However, it is possible to use different public address configurations on different nodes\&.
 +.PP
 +Example: 4 nodes partitioned into two subgroups:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +Node 0:/etc/ctdb/public_addresses
 +	10\&.1\&.1\&.1/24 eth1
 +	10\&.1\&.1\&.2/24 eth1
 +
 +Node 1:/etc/ctdb/public_addresses
 +	10\&.1\&.1\&.1/24 eth1
 +	10\&.1\&.1\&.2/24 eth1
 +
 +Node 2:/etc/ctdb/public_addresses
 +	10\&.1\&.2\&.1/24 eth2
 +	10\&.1\&.2\&.2/24 eth2
 +
 +Node 3:/etc/ctdb/public_addresses
 +	10\&.1\&.2\&.1/24 eth2
 +	10\&.1\&.2\&.2/24 eth2
 +      
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +In this example nodes 0 and 1 host two public addresses on the 10\&.1\&.1\&.x network while nodes 2 and 3 host two public addresses for the 10\&.1\&.2\&.x network\&.
 +.PP
 +Public address 10\&.1\&.1\&.1 can be hosted by either of nodes 0 or 1 and will be available to clients as long as at least one of these two nodes are available\&.
 +.PP
 +If both nodes 0 and 1 become unavailable then public address 10\&.1\&.1\&.1 also becomes unavailable\&. 10\&.1\&.1\&.1 can not be failed over to nodes 2 or 3 since these nodes do not have this public address configured\&.
 +.PP
 +The
 +\fBctdb ip\fR
 +command can be used to view the current assignment of public addresses to physical nodes\&.
 +.SH "NODE STATUS"
 +.PP
 +The current status of each node in the cluster can be viewed by the
 +\fBctdb status\fR
 +command\&.
 +.PP
 +A node can be in one of the following states:
 +.PP
 +OK
 +.RS 4
 +This node is healthy and fully functional\&. It hosts public addresses to provide services\&.
 +.RE
 +.PP
 +DISCONNECTED
 +.RS 4
 +This node is not reachable by other nodes via the private network\&. It is not currently participating in the cluster\&. It
 +\fIdoes not\fR
 +host public addresses to provide services\&. It might be shut down\&.
 +.RE
 +.PP
 +DISABLED
 +.RS 4
 +This node has been administratively disabled\&. This node is partially functional and participates in the cluster\&. However, it
 +\fIdoes not\fR
 +host public addresses to provide services\&.
 +.RE
 +.PP
 +UNHEALTHY
 +.RS 4
 +A service provided by this node has failed a health check and should be investigated\&. This node is partially functional and participates in the cluster\&. However, it
 +\fIdoes not\fR
 +host public addresses to provide services\&. Unhealthy nodes should be investigated and may require an administrative action to rectify\&.
 +.RE
 +.PP
 +BANNED
 +.RS 4
 +CTDB is not behaving as designed on this node\&. For example, it may have failed too many recovery attempts\&. Such nodes are banned from participating in the cluster for a configurable time period before they attempt to rejoin the cluster\&. A banned node
 +\fIdoes not\fR
 +host public addresses to provide services\&. All banned nodes should be investigated and may require an administrative action to rectify\&.
 +.RE
 +.PP
 +STOPPED
 +.RS 4
 +This node has been administratively exclude from the cluster\&. A stopped node does no participate in the cluster and
 +\fIdoes not\fR
 +host public addresses to provide services\&. This state can be used while performing maintenance on a node\&.
 +.RE
 +.PP
 +PARTIALLYONLINE
 +.RS 4
 +A node that is partially online participates in a cluster like a healthy (OK) node\&. Some interfaces to serve public addresses are down, but at least one interface is up\&. See also
 +\fBctdb ifaces\fR\&.
 +.RE
 +.SH "CAPABILITIES"
 +.PP
 +Cluster nodes can have several different capabilities enabled\&. These are listed below\&.
 +.PP
 +RECMASTER
 +.RS 4
 +Indicates that a node can become the CTDB cluster recovery master\&. The current recovery master is decided via an election held by all active nodes with this capability\&.
 +.sp
 +Default is YES\&.
 +.RE
 +.PP
 +LMASTER
 +.RS 4
 +Indicates that a node can be the location master (LMASTER) for database records\&. The LMASTER always knows which node has the latest copy of a record in a volatile database\&.
 +.sp
 +Default is YES\&.
 +.RE
 +.PP
 +LVS
 +.RS 4
 +Indicates that a node is configued in Linux Virtual Server (LVS) mode\&. In this mode the entire CTDB cluster uses one single public address for the entire cluster instead of using multiple public addresses in failover mode\&. This is an alternative to using a load\-balancing layer\-4 switch\&. See the
 +LVS
 +section for more details\&.
 +.RE
 +.PP
 +NATGW
 +.RS 4
 +Indicates that this node is configured to become the NAT gateway master in a NAT gateway group\&. See the
 +NAT GATEWAY
 +section for more details\&.
 +.RE
 +.PP
 +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\&.
 +.SH "LVS"
 +.PP
 +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 cluster\&.
 +.PP
 +This is similar to using a layer\-4 loadbalancing switch but with some restrictions\&.
 +.PP
 +In this mode the cluster selects a set of nodes in the cluster and loadbalance all client access to the LVS address across this set of nodes\&. This set of nodes are all LVS capable nodes that are HEALTHY, or if no HEALTHY nodes exists all LVS capable nodes regardless of health status\&. LVS will however never loadbalance traffic to nodes that are BANNED, STOPPED, DISABLED or DISCONNECTED\&. The
 +\fBctdb lvs\fR
 +command is used to show which nodes are currently load\-balanced across\&.
 +.PP
 +One of the these nodes are elected as the LVSMASTER\&. This node receives all traffic from clients coming in to the LVS address and multiplexes it across the internal network to one of the nodes that LVS is using\&. When responding to the client, that node will send the data back directly to the client, bypassing the LVSMASTER node\&. The command
 +\fBctdb lvsmaster\fR
 +will show which node is the current LVSMASTER\&.
 +.PP
 +The path used for a client I/O is:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04' 1.\h'+01'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP "  1." 4.2
 +.\}
 +Client sends request packet to LVSMASTER\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04' 2.\h'+01'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP "  2." 4.2
 +.\}
 +LVSMASTER passes the request on to one node across the internal network\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04' 3.\h'+01'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP "  3." 4.2
 +.\}
 +Selected node processes the request\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04' 4.\h'+01'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP "  4." 4.2
 +.\}
 +Node responds back to client\&.
 +.RE
 +.PP
 +This means that all incoming traffic to the cluster will pass through one physical node, which limits scalability\&. You can send more data to the LVS address that one physical node can multiplex\&. This means that you should not use LVS if your I/O pattern is write\-intensive since you will be limited in the available network bandwidth that node can handle\&. LVS does work wery well for read\-intensive workloads where only smallish READ requests are going through the LVSMASTER bottlene [...]
 +.PP
 +Note: you can use LVS and public addresses at the same time\&.
 +.PP
 +If you use LVS, you must have a permanent address configured for the public interface on each node\&. This address must be routable and the cluster nodes must be configured so that all traffic back to client hosts are routed through this interface\&. This is also required in order to allow samba/winbind on the node to talk to the domain controller\&. This LVS IP address can not be used to initiate outgoing traffic\&.
 +.PP
 +Make sure that the domain controller and the clients are reachable from a node
 +\fIbefore\fR
 +you enable LVS\&. Also ensure that outgoing traffic to these hosts is routed out through the configured public interface\&.
 +.SS "Configuration"
 +.PP
 +To activate LVS on a CTDB node you must specify the
 +\fICTDB_PUBLIC_INTERFACE\fR
 +and
 +\fICTDB_LVS_PUBLIC_IP\fR
 +configuration variables\&. Setting the latter variable also enables the LVS capability on the node at startup\&.
 +.PP
 +Example:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +CTDB_PUBLIC_INTERFACE=eth1
 +CTDB_LVS_PUBLIC_IP=10\&.1\&.1\&.237
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.sp
 +.SH "NAT GATEWAY"
 +.PP
 +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) when they do not host any public addresses (e\&.g\&. when they are unhealthy)\&.
 +.PP
 +This also applies to node startup because CTDB marks nodes as UNHEALTHY until they have passed a "monitor" event\&. In this context, NAT gateway helps to avoid a "chicken and egg" situation where a node needs to access an external service to become healthy\&.
 +.PP
 +Another way of solving this type of problem is to assign an 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\&.
 +.SS "Operation"
 +.PP
 +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 talk to the outside world\&. Normally there would only be one NATGW group spanning an entire cluster, but in situations where one CTDB cluster spans multiple physical sites it might be useful to have one NATGW group for each site\&.
 +.PP
 +There can be multiple NATGW groups in a cluster but each node can only be member of one NATGW group\&.
 +.PP
 +In each NATGW group, one of the nodes is selected by CTDB to be the NATGW master and the other nodes are consider to be NATGW slaves\&. NATGW slaves establish a fallback default route to the NATGW master via the private network\&. When a NATGW slave hosts no public IP addresses then it will use this route for outbound connections\&. The NATGW master hosts the NATGW public IP address and routes outgoing connections from slave nodes via this IP address\&. It also establishes a fallback de [...]
 +.SS "Configuration"
 +.PP
 +NATGW is usually configured similar to the following example configuration:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +CTDB_NATGW_NODES=/etc/ctdb/natgw_nodes
 +CTDB_NATGW_PRIVATE_NETWORK=192\&.168\&.1\&.0/24
 +CTDB_NATGW_PUBLIC_IP=10\&.0\&.0\&.227/24
 +CTDB_NATGW_PUBLIC_IFACE=eth0
 +CTDB_NATGW_DEFAULT_GATEWAY=10\&.0\&.0\&.1
 +      
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +Normally any node in a NATGW group can act as the NATGW master\&. Some configurations may have special nodes that lack connectivity to a public network\&. In such cases,
 +\fICTDB_NATGW_SLAVE_ONLY\fR
 +can be used to limit the NATGW functionality of thos nodes\&.
 +.PP
 +See the
 +NAT GATEWAY
 +section in
 +\fBctdb.conf\fR(5)
 +for more details of NATGW configuration\&.
 +.SS "Implementation details"
 +.PP
 +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 services\&. The NATGW master is selected to be a node that is most likely to have usable networks\&.
 +.PP
 +The NATGW master hosts the NATGW public IP address
 +\fICTDB_NATGW_PUBLIC_IP\fR
 +on the configured public interfaces
 +\fICTDB_NATGW_PUBLIC_IFACE\fR
 +and acts as a router, masquerading outgoing connections from slave nodes via this IP address\&. If
 +\fICTDB_NATGW_DEFAULT_GATEWAY\fR
 +is set then it also establishes a fallback default route to the configured this gateway with a metric of 10\&. A metric 10 route is used so it can co\-exist with other default routes that may be available\&.
 +.PP
 +A NATGW slave establishes its fallback default route to the NATGW master via the private network
 +\fICTDB_NATGW_PRIVATE_NETWORK\fRwith a metric of 10\&. This route is used for outbound connections when no other default route is available because the node hosts no public addresses\&. A metric 10 routes is used so that it can co\-exist with other default routes that may be available when the node is hosting public addresses\&.
 +.PP
 +\fICTDB_NATGW_STATIC_ROUTES\fR
 +can be used to have NATGW create more specific routes instead of just default routes\&.
 +.PP
 +This is implemented in the
 +11\&.natgw
 +eventscript\&. Please see the eventscript file and the
 +NAT GATEWAY
 +section in
 +\fBctdbd.conf\fR(5)
 +for more details\&.
 +.SH "POLICY ROUTING"
 +.PP
 +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 to route packets from these public addresses via the system\*(Aqs default route\&. Therefore, CTDB has support for policy routing via the
 +13\&.per_ip_routing
 +eventscript\&. 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\&.
 +.SS "Configuration variables"
 +.PP
 +There are 4 configuration variables related to policy routing:
 +\fICTDB_PER_IP_ROUTING_CONF\fR,
 +\fICTDB_PER_IP_ROUTING_RULE_PREF\fR,
 +\fICTDB_PER_IP_ROUTING_TABLE_ID_LOW\fR,
 +\fICTDB_PER_IP_ROUTING_TABLE_ID_HIGH\fR\&. See the
 +POLICY ROUTING
 +section in
 +\fBctdbd.conf\fR(5)
 +for more details\&.
 +.SS "Configuration"
 +.PP
 +The format of each line of
 +\fICTDB_PER_IP_ROUTING_CONF\fR
 +is:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +<public_address> <network> [ <gateway> ]
 +      
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +Leading whitespace is ignored and arbitrary whitespace may be used as a separator\&. Lines that have a "public address" item that doesn\*(Aqt match an actual public address are ignored\&. This means that comment lines can be added using a leading character such as \*(Aq#\*(Aq, since this will never match an IP address\&.
 +.PP
 +A line without a gateway indicates a link local route\&.
 +.PP
 +For example, consider the configuration line:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +  192\&.168\&.1\&.99	192\&.168\&.1\&.1/24
 +      
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +If the corresponding public_addresses line is:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +  192\&.168\&.1\&.99/24     eth2,eth3
 +      
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +\fICTDB_PER_IP_ROUTING_RULE_PREF\fR
 +is 100, and CTDB adds the address to eth2 then the following routing information is added:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +  ip rule add from 192\&.168\&.1\&.99 pref 100 table ctdb\&.192\&.168\&.1\&.99
 +  ip route add 192\&.168\&.1\&.0/24 dev eth2 table ctdb\&.192\&.168\&.1\&.99
 +      
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +This causes traffic from 192\&.168\&.1\&.1 to 192\&.168\&.1\&.0/24 go via eth2\&.
 +.PP
 +The
 +\fBip rule\fR
 +command will show (something like \- depending on other public addresses and other routes on the system):
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +  0:		from all lookup local 
 +  100:		from 192\&.168\&.1\&.99 lookup ctdb\&.192\&.168\&.1\&.99
 +  32766:	from all lookup main 
 +  32767:	from all lookup default 
 +      
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +\fBip route show table ctdb\&.192\&.168\&.1\&.99\fR
 +will show:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +  192\&.168\&.1\&.0/24 dev eth2 scope link
 +      
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +The usual use for a line containing a gateway is to add a default route corresponding to a particular source address\&. Consider this line of configuration:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +  192\&.168\&.1\&.99	0\&.0\&.0\&.0/0	192\&.168\&.1\&.1
 +      
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +In the situation described above this will cause an extra routing command to be executed:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +  ip route add 0\&.0\&.0\&.0/0 via 192\&.168\&.1\&.1 dev eth2 table ctdb\&.192\&.168\&.1\&.99
 +      
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +With both configuration lines,
 +\fBip route show table ctdb\&.192\&.168\&.1\&.99\fR
 +will show:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +  192\&.168\&.1\&.0/24 dev eth2 scope link 
 +  default via 192\&.168\&.1\&.1 dev eth2 
 +      
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.SS "Sample configuration"
 +.PP
 +Here is a more complete example configuration\&.
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +/etc/ctdb/public_addresses:
 +
 +  192\&.168\&.1\&.98	eth2,eth3
 +  192\&.168\&.1\&.99	eth2,eth3
 +
 +/etc/ctdb/policy_routing:
 +
 +  192\&.168\&.1\&.98 192\&.168\&.1\&.0/24
 +  192\&.168\&.1\&.98 192\&.168\&.200\&.0/24	192\&.168\&.1\&.254
 +  192\&.168\&.1\&.98 0\&.0\&.0\&.0/0 	192\&.168\&.1\&.1
 +  192\&.168\&.1\&.99 192\&.168\&.1\&.0/24
 +  192\&.168\&.1\&.99 192\&.168\&.200\&.0/24	192\&.168\&.1\&.254
 +  192\&.168\&.1\&.99 0\&.0\&.0\&.0/0 	192\&.168\&.1\&.1
 +      
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +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\&.
 +.SH "NOTIFICATION SCRIPT"
 +.PP
 +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 unhealthy or similar\&.
 +.PP
 +This is activated by setting the
 +\fICTDB_NOTIFY_SCRIPT\fR
 +configuration variable\&. The specified script must be executable\&.
 +.PP
 +Use of the provided
 +/etc/ctdb/notify\&.sh
 +script is recommended\&. It executes files in
 +/etc/ctdb/notify\&.d/\&.
 +.PP
 +CTDB currently generates notifications after CTDB changes to these states:
 +.RS 4
 +init
 +.RE
 +.RS 4
 +setup
 +.RE
 +.RS 4
 +startup
 +.RE
 +.RS 4
 +healthy
 +.RE
 +.RS 4
 +unhealthy
 +.RE
 +.SH "DEBUG LEVELS"
 +.PP
 +Valid values for DEBUGLEVEL are:
 +.RS 4
 +ERR (0)
 +.RE
 +.RS 4
 +WARNING (1)
 +.RE
 +.RS 4
 +NOTICE (2)
 +.RE
 +.RS 4
 +INFO (3)
 +.RE
 +.RS 4
 +DEBUG (4)
 +.RE
 +.SH "REMOTE CLUSTER NODES"
 +.PP
 +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\&. This is similar to how a WAN accelerator works but with the difference that while a WAN\-accelerator often acts as a Proxy or a MitM, in the ctdb remote cluster node configuration the Samba instance at the remote site IS the genuine server, not a proxy and not a MitM, and t [...]
 +.PP
 +See the cluster as one single multihomed samba server where one of the NICs (the remote node) is very far away\&.
 +.PP
 +NOTE: This does require that the cluster filesystem you use can cope with WAN\-link latencies\&. Not all cluster filesystems can handle WAN\-link latencies! Whether this will provide very good WAN\-accelerator performance or it will perform very poorly depends entirely on how optimized your cluster filesystem is in handling high latency for data and metadata operations\&.
 +.PP
 +To activate a node as being a remote cluster node you need to set the following two parameters in /etc/sysconfig/ctdb for the remote node:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +CTDB_CAPABILITY_LMASTER=no
 +CTDB_CAPABILITY_RECMASTER=no
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +Verify with the command "ctdb getcapabilities" that that node no longer has the recmaster or the lmaster capabilities\&.
 +.SH "SEE ALSO"
 +.PP
 +\fBctdb\fR(1),
 +\fBctdbd\fR(1),
 +\fBctdbd_wrapper\fR(1),
 +\fBltdbtool\fR(1),
 +\fBonnode\fR(1),
 +\fBping_pong\fR(1),
 +\fBctdbd.conf\fR(5),
 +\fBctdb-statistics\fR(7),
 +\fBctdb-tunables\fR(7),
 +\m[blue]\fB\%http://ctdb.samba.org/\fR\m[]
 +.SH "AUTHOR"
 +.br
 +.PP
 +This documentation was written by Ronnie Sahlberg, Amitay Isaacs, Martin Schwenke
 +.SH "COPYRIGHT"
 +.br
 +Copyright \(co 2007 Andrew Tridgell, Ronnie Sahlberg
 +.br
 +.PP
 +This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version\&.
 +.PP
 +This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE\&. See the GNU General Public License for more details\&.
 +.PP
 +You should have received a copy of the GNU General Public License along with this program; if not, see
 +\m[blue]\fB\%http://www.gnu.org/licenses\fR\m[]\&.
 +.sp
diff --cc ctdb/doc/ctdb.7.html
index dd8ad96,0000000..a318425
mode 100644,000000..100644
--- a/ctdb/doc/ctdb.7.html
+++ b/ctdb/doc/ctdb.7.html
@@@ -1,589 -1,0 +1,589 @@@
- <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 — Clustered TDB</p></div><div class="refsect1"><a name="idp52417760"></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.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 — Clustered TDB</p></div><div class="refsect1"><a name="idp51979744"></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>
 +    The main functions of CTDB are:
 +  </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
 +	Provide a clustered version of the TDB database with automatic
 +	rebuild/recovery of the databases upon node failures.
 +      </p></li><li class="listitem"><p>
 +      Monitor nodes in the cluster and services running on each node.
 +      </p></li><li class="listitem"><p>
 +	Manage a pool of public IP addresses that are used to provide
 +	services to clients.  Alternatively, CTDB can be used with
 +	LVS.
 +      </p></li></ul></div><p>
 +    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="idp52041536"></a><h2>ANATOMY OF A CTDB CLUSTER</h2><p>
++  </p></div><div class="refsect1"><a name="idp52619776"></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
 +    storage (usually a cluster filesystem) that is accessible by all
 +    nodes.
 +  </p><p>
 +    CTDB provides an "all active" cluster, where services are load
 +    balanced across all nodes.
-   </p></div><div class="refsect1"><a name="idp50203392"></a><h2>Recovery Lock</h2><p>
++  </p></div><div class="refsect1"><a name="idp52982864"></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
 +      independently.  Issues that can result from a split brain
 +      include file data corruption, because file locking metadata may
 +      not be tracked correctly.
 +    </p><p>
 +      CTDB uses a <span class="emphasis"><em>cluster leader and follower</em></span>
 +      model of cluster management.  All nodes in a cluster elect one
 +      node to be the leader.  The leader node coordinates privileged
 +      operations such as database recovery and IP address failover.
 +      CTDB refers to the leader node as the <span class="emphasis"><em>recovery
 +      master</em></span>.  This node takes and holds the recovery lock
 +      to assert its privileged role in the cluster.
 +    </p><p>
 +      The recovery lock is implemented using a file residing in shared
 +      storage (usually) on a cluster filesystem.  To support a
 +      recovery lock the cluster filesystem must support lock
 +      coherence.  See
 +      <span class="citerefentry"><span class="refentrytitle">ping_pong</span>(1)</span> for more details.
 +    </p><p>
 +      If a cluster becomes partitioned (for example, due to a
 +      communication failure) and a different recovery master is
 +      elected by the nodes in each partition, then only one of these
 +      recovery masters will be able to take the recovery lock.  The
 +      recovery master in the "losing" partition will not be able to
 +      take the recovery lock and will be excluded from the cluster.
 +      The nodes in the "losing" partition will elect each node in turn
 +      as their recovery master so eventually all the nodes in that
 +      partition will be excluded.
 +    </p><p>
 +      CTDB does sanity checks to ensure that the recovery lock is held
 +      as expected.
 +    </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="idp54722544"></a><h2>Private vs Public addresses</h2><p>
++    </p></div><div class="refsect1"><a name="idp49232144"></a><h2>Private vs Public addresses</h2><p>
 +      Each node in a CTDB cluster has multiple IP addresses assigned
 +      to it:
 +
 +      </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
 +	    A single private IP address that is used for communication
 +	    between nodes.
 +	  </p></li><li class="listitem"><p>
 +	    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="idp54725920"></a><h3>Private address</h3><p>
++    </p><div class="refsect2"><a name="idp53885408"></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
 +        the cluster and is the address that CTDB daemons will use to
 +        communicate with the CTDB daemons on other nodes.
 +      </p><p>
 +        Private addresses are listed in the file specified by the
 +        <code class="varname">CTDB_NODES</code> configuration variable (see
 +        <span class="citerefentry"><span class="refentrytitle">ctdbd.conf</span>(5)</span>, default
 +        <code class="filename">/etc/ctdb/nodes</code>).  This file contains the
 +        list of private addresses for all nodes in the cluster, one
 +        per line. This file must be the same on all nodes in the
 +        cluster.
 +      </p><p>
 +	Private addresses should not be used by clients to connect to
 +	services provided by the cluster.
 +      </p><p>
 +        It is strongly recommended that the private addresses are
 +        configured on a private network that is separate from client
 +        networks.
 +      </p><p>
 +	Example <code class="filename">/etc/ctdb/nodes</code> for a four node
 +	cluster:
 +      </p><pre class="screen">
 +192.168.1.1
 +192.168.1.2
 +192.168.1.3
 +192.168.1.4
-       </pre></div><div class="refsect2"><a name="idp54733024"></a><h3>Public addresses</h3><p>
++      </pre></div><div class="refsect2"><a name="idp53892560"></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
 +	node.  Instead, they are managed by CTDB and are assigned to
 +	interfaces on physical nodes at runtime.
 +      </p><p>
 +        The CTDB cluster will assign/reassign these public addresses
 +        across the available healthy nodes in the cluster. When one
 +        node fails, its public addresses will be taken over by one or
 +        more other nodes in the cluster.  This ensures that services
 +        provided by all public addresses are always available to
 +        clients, as long as there are nodes available capable of
 +        hosting this address.
 +      </p><p>
 +	The public address configuration is stored in a file on each
 +	node specified by the <code class="varname">CTDB_PUBLIC_ADDRESSES</code>
 +	configuration variable (see
 +	<span class="citerefentry"><span class="refentrytitle">ctdbd.conf</span>(5)</span>, recommended
 +	<code class="filename">/etc/ctdb/public_addresses</code>).  This file
 +	contains a list of the public addresses that the node is
 +	capable of hosting, one per line.  Each entry also contains
 +	the netmask and the interface to which the address should be
 +	assigned.
 +      </p><p>
 +	Example <code class="filename">/etc/ctdb/public_addresses</code> for a
 +	node that can host 4 public addresses, on 2 different
 +	interfaces:
 +      </p><pre class="screen">
 +10.1.1.1/24 eth1
 +10.1.1.2/24 eth1
 +10.1.2.1/24 eth2
 +10.1.2.2/24 eth2
 +      </pre><p>
 +	In many cases the public addresses file will be the same on
 +	all nodes.  However, it is possible to use different public
 +	address configurations on different nodes.
 +      </p><p>
 +	Example: 4 nodes partitioned into two subgroups:
 +      </p><pre class="screen">
 +Node 0:/etc/ctdb/public_addresses
 +	10.1.1.1/24 eth1
 +	10.1.1.2/24 eth1
 +
 +Node 1:/etc/ctdb/public_addresses
 +	10.1.1.1/24 eth1
 +	10.1.1.2/24 eth1
 +
 +Node 2:/etc/ctdb/public_addresses
 +	10.1.2.1/24 eth2
 +	10.1.2.2/24 eth2
 +
 +Node 3:/etc/ctdb/public_addresses
 +	10.1.2.1/24 eth2
 +	10.1.2.2/24 eth2
 +      </pre><p>
 +	In this example nodes 0 and 1 host two public addresses on the
 +	10.1.1.x network while nodes 2 and 3 host two public addresses
 +	for the 10.1.2.x network.
 +      </p><p>
 +	Public address 10.1.1.1 can be hosted by either of nodes 0 or
 +	1 and will be available to clients as long as at least one of
 +	these two nodes are available.
 +      </p><p>
 +	If both nodes 0 and 1 become unavailable then public address
 +	10.1.1.1 also becomes unavailable. 10.1.1.1 can not be failed
 +	over to nodes 2 or 3 since these nodes do not have this public
 +	address configured.
 +      </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="idp49118112"></a><h2>Node status</h2><p>
++      </p></div></div><div class="refsect1"><a name="idp49114720"></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>
 +      A node can be in one of the following states:
 +    </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">OK</span></dt><dd><p>
 +	    This node is healthy and fully functional.  It hosts public
 +	    addresses to provide services.
 +	  </p></dd><dt><span class="term">DISCONNECTED</span></dt><dd><p>
 +	    This node is not reachable by other nodes via the private
 +	    network.  It is not currently participating in the cluster.
 +	    It <span class="emphasis"><em>does not</em></span> host public addresses to
 +	    provide services.  It might be shut down.
 +	  </p></dd><dt><span class="term">DISABLED</span></dt><dd><p>
 +	    This node has been administratively disabled. This node is
 +	    partially functional and participates in the cluster.
 +	    However, it <span class="emphasis"><em>does not</em></span> host public
 +	    addresses to provide services.
 +	  </p></dd><dt><span class="term">UNHEALTHY</span></dt><dd><p>
 +	    A service provided by this node has failed a health check
 +	    and should be investigated.  This node is partially
 +	    functional and participates in the cluster.  However, it
 +	    <span class="emphasis"><em>does not</em></span> host public addresses to
 +	    provide services.  Unhealthy nodes should be investigated
 +	    and may require an administrative action to rectify.
 +	  </p></dd><dt><span class="term">BANNED</span></dt><dd><p>
 +	    CTDB is not behaving as designed on this node.  For example,
 +	    it may have failed too many recovery attempts.  Such nodes
 +	    are banned from participating in the cluster for a
 +	    configurable time period before they attempt to rejoin the
 +	    cluster.  A banned node <span class="emphasis"><em>does not</em></span> host
 +	    public addresses to provide services.  All banned nodes
 +	    should be investigated and may require an administrative
 +	    action to rectify.
 +	  </p></dd><dt><span class="term">STOPPED</span></dt><dd><p>
 +	    This node has been administratively exclude from the
 +	    cluster.  A stopped node does no participate in the cluster
 +	    and <span class="emphasis"><em>does not</em></span> host public addresses to
 +	    provide services.  This state can be used while performing
 +	    maintenance on a node.
 +	  </p></dd><dt><span class="term">PARTIALLYONLINE</span></dt><dd><p>
 +	    A node that is partially online participates in a cluster
 +	    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="idp49141264"></a><h2>CAPABILITIES</h2><p>
++	  </p></dd></dl></div></div><div class="refsect1"><a name="idp49137968"></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>
 +	    Indicates that a node can become the CTDB cluster recovery
 +	    master.  The current recovery master is decided via an
 +	    election held by all active nodes with this capability.
 +	  </p><p>
 +	    Default is YES.
 +	  </p></dd><dt><span class="term">LMASTER</span></dt><dd><p>
 +	    Indicates that a node can be the location master (LMASTER)
 +	    for database records.  The LMASTER always knows which node
 +	    has the latest copy of a record in a volatile database.
 +	  </p><p>
 +	    Default is YES.
 +	  </p></dd><dt><span class="term">LVS</span></dt><dd><p>
 +	    Indicates that a node is configued in Linux Virtual Server
 +	    (LVS) mode.  In this mode the entire CTDB cluster uses one
 +	    single public address for the entire cluster instead of
 +	    using multiple public addresses in failover mode.  This is
 +	    an alternative to using a load-balancing layer-4 switch.
 +	    See the <em class="citetitle">LVS</em> section for more
 +	    details.
 +	  </p></dd><dt><span class="term">NATGW</span></dt><dd><p>
 +	    Indicates that this node is configured to become the NAT
 +	    gateway master in a NAT gateway group.  See the
 +	    <em class="citetitle">NAT GATEWAY</em> section for more
 +	    details.
 +	  </p></dd></dl></div><p>
 +      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="idp49152512"></a><h2>LVS</h2><p>
++    </p></div><div class="refsect1"><a name="idp49149168"></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
 +      cluster.
 +    </p><p>
 +      This is similar to using a layer-4 loadbalancing switch but with
 +      some restrictions.
 +    </p><p>
 +      In this mode the cluster selects a set of nodes in the cluster
 +      and loadbalance all client access to the LVS address across this
 +      set of nodes. This set of nodes are all LVS capable nodes that
 +      are HEALTHY, or if no HEALTHY nodes exists all LVS capable nodes
 +      regardless of health status.  LVS will however never loadbalance
 +      traffic to nodes that are BANNED, STOPPED, DISABLED or
 +      DISCONNECTED. The <span class="command"><strong>ctdb lvs</strong></span> command is used to
 +      show which nodes are currently load-balanced across.
 +    </p><p>
 +      One of the these nodes are elected as the LVSMASTER. This node
 +      receives all traffic from clients coming in to the LVS address
 +      and multiplexes it across the internal network to one of the
 +      nodes that LVS is using.  When responding to the client, that
 +      node will send the data back directly to the client, bypassing
 +      the LVSMASTER node.  The command <span class="command"><strong>ctdb
 +      lvsmaster</strong></span> will show which node is the current
 +      LVSMASTER.
 +    </p><p>
 +      The path used for a client I/O is:
 +      </p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>
 +	    Client sends request packet to LVSMASTER.
 +	  </p></li><li class="listitem"><p>
 +	    LVSMASTER passes the request on to one node across the
 +	    internal network.
 +	  </p></li><li class="listitem"><p>
 +	    Selected node processes the request.
 +	  </p></li><li class="listitem"><p>
 +	    Node responds back to client.
 +	  </p></li></ol></div><p>
 +    </p><p> 
 +      This means that all incoming traffic to the cluster will pass
 +      through one physical node, which limits scalability. You can
 +      send more data to the LVS address that one physical node can
 +      multiplex. This means that you should not use LVS if your I/O
 +      pattern is write-intensive since you will be limited in the
 +      available network bandwidth that node can handle.  LVS does work
 +      wery well for read-intensive workloads where only smallish READ
 +      requests are going through the LVSMASTER bottleneck and the
 +      majority of the traffic volume (the data in the read replies)
 +      goes straight from the processing node back to the clients. For
 +      read-intensive i/o patterns you can acheive very high throughput
 +      rates in this mode.
 +    </p><p>
 +      Note: you can use LVS and public addresses at the same time.
 +    </p><p>
 +      If you use LVS, you must have a permanent address configured for
 +      the public interface on each node. This address must be routable
 +      and the cluster nodes must be configured so that all traffic
 +      back to client hosts are routed through this interface. This is
 +      also required in order to allow samba/winbind on the node to
 +      talk to the domain controller.  This LVS IP address can not be
 +      used to initiate outgoing traffic.
 +    </p><p>
 +      Make sure that the domain controller and the clients are
 +      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="idp55867952"></a><h3>Configuration</h3><p>
++    </p><div class="refsect2"><a name="idp55025520"></a><h3>Configuration</h3><p>
 +	To activate LVS on a CTDB node you must specify the
 +	<code class="varname">CTDB_PUBLIC_INTERFACE</code> and
 +	<code class="varname">CTDB_LVS_PUBLIC_IP</code> configuration variables.
 +	Setting the latter variable also enables the LVS capability on
 +	the node at startup.
 +      </p><p>
 +	Example:
 +	</p><pre class="screen">
 +CTDB_PUBLIC_INTERFACE=eth1
 +CTDB_LVS_PUBLIC_IP=10.1.1.237
 +	</pre><p>
-       </p></div></div><div class="refsect1"><a name="idp55871136"></a><h2>NAT GATEWAY</h2><p>
++      </p></div></div><div class="refsect1"><a name="idp55028704"></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)
 +      when they do not host any public addresses (e.g. when they are
 +      unhealthy).
 +    </p><p>
 +      This also applies to node startup because CTDB marks nodes as
 +      UNHEALTHY until they have passed a "monitor" event.  In this
 +      context, NAT gateway helps to avoid a "chicken and egg"
 +      situation where a node needs to access an external service to
 +      become healthy.
 +    </p><p>
 +      Another way of solving this type of problem is to assign an
 +      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="idp55873824"></a><h3>Operation</h3><p>
++    </p><div class="refsect2"><a name="idp55031392"></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
 +	talk to the outside world.  Normally there would only be one
 +	NATGW group spanning an entire cluster, but in situations
 +	where one CTDB cluster spans multiple physical sites it might
 +	be useful to have one NATGW group for each site.
 +      </p><p>
 +	There can be multiple NATGW groups in a cluster but each node
 +	can only be member of one NATGW group.
 +      </p><p>
 +	In each NATGW group, one of the nodes is selected by CTDB to
 +	be the NATGW master and the other nodes are consider to be
 +	NATGW slaves.  NATGW slaves establish a fallback default route
 +	to the NATGW master via the private network.  When a NATGW
 +	slave hosts no public IP addresses then it will use this route
 +	for outbound connections.  The NATGW master hosts the NATGW
 +	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="idp55877360"></a><h3>Configuration</h3><p>
++      </p></div><div class="refsect2"><a name="idp55034928"></a><h3>Configuration</h3><p>
 +	NATGW is usually configured similar to the following example configuration:
 +      </p><pre class="screen">
 +CTDB_NATGW_NODES=/etc/ctdb/natgw_nodes
 +CTDB_NATGW_PRIVATE_NETWORK=192.168.1.0/24
 +CTDB_NATGW_PUBLIC_IP=10.0.0.227/24
 +CTDB_NATGW_PUBLIC_IFACE=eth0
 +CTDB_NATGW_DEFAULT_GATEWAY=10.0.0.1
 +      </pre><p>
 +	Normally any node in a NATGW group can act as the NATGW
 +	master.  Some configurations may have special nodes that lack
 +	connectivity to a public network.  In such cases,
 +	<code class="varname">CTDB_NATGW_SLAVE_ONLY</code> can be used to limit the
 +	NATGW functionality of thos nodes.
 +      </p><p>
 +	See the <em class="citetitle">NAT GATEWAY</em> section in
 +	<span class="citerefentry"><span class="refentrytitle">ctdb.conf</span>(5)</span> for more details of
 +	NATGW configuration.
-       </p></div><div class="refsect2"><a name="idp55882064"></a><h3>Implementation details</h3><p>
++      </p></div><div class="refsect2"><a name="idp55039632"></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
 +	services.  The NATGW master is selected to be a node that is
 +	most likely to have usable networks.
 +      </p><p>
 +	The NATGW master hosts the NATGW public IP address
 +	<code class="varname">CTDB_NATGW_PUBLIC_IP</code> on the configured public
 +	interfaces <code class="varname">CTDB_NATGW_PUBLIC_IFACE</code> and acts as
 +	a router, masquerading outgoing connections from slave nodes
 +	via this IP address.  If
 +	<code class="varname">CTDB_NATGW_DEFAULT_GATEWAY</code> is set then it
 +	also establishes a fallback default route to the configured
 +	this gateway with a metric of 10.  A metric 10 route is used
 +	so it can co-exist with other default routes that may be
 +	available.
 +      </p><p>
 +	A NATGW slave establishes its fallback default route to the
 +	NATGW master via the private network
 +	<code class="varname">CTDB_NATGW_PRIVATE_NETWORK</code>with a metric of 10.
 +	This route is used for outbound connections when no other
 +	default route is available because the node hosts no public
 +	addresses.  A metric 10 routes is used so that it can co-exist
 +	with other default routes that may be available when the node
 +	is hosting public addresses.
 +      </p><p>
 +	<code class="varname">CTDB_NATGW_STATIC_ROUTES</code> can be used to
 +	have NATGW create more specific routes instead of just default
 +	routes.
 +      </p><p>
 +	This is implemented in the <code class="filename">11.natgw</code>
 +	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="idp55889888"></a><h2>POLICY ROUTING</h2><p>
++      </p></div></div><div class="refsect1"><a name="idp55047456"></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
 +      to route packets from these public addresses via the system's
 +      default route.  Therefore, CTDB has support for policy routing
 +      via the <code class="filename">13.per_ip_routing</code> eventscript.
 +      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="idp55892112"></a><h3>Configuration variables</h3><p>
++    </p><div class="refsect2"><a name="idp55049680"></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>,
 +	<code class="varname">CTDB_PER_IP_ROUTING_TABLE_ID_LOW</code>,
 +	<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="idp55896080"></a><h3>Configuration</h3><p>
++      </p></div><div class="refsect2"><a name="idp55053648"></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">
 +<public_address> <network> [ <gateway> ]
 +      </pre><p>
 +	Leading whitespace is ignored and arbitrary whitespace may be
 +	used as a separator.  Lines that have a "public address" item
 +	that doesn't match an actual public address are ignored.  This
 +	means that comment lines can be added using a leading
 +	character such as '#', since this will never match an IP
 +	address.
 +      </p><p>
 +	A line without a gateway indicates a link local route.
 +      </p><p>
 +	For example, consider the configuration line:
 +      </p><pre class="screen">
 +  192.168.1.99	192.168.1.1/24
 +      </pre><p>
 +	If the corresponding public_addresses line is:
 +      </p><pre class="screen">
 +  192.168.1.99/24     eth2,eth3
 +      </pre><p>
 +	<code class="varname">CTDB_PER_IP_ROUTING_RULE_PREF</code> is 100, and
 +	CTDB adds the address to eth2 then the following routing
 +	information is added:
 +      </p><pre class="screen">
 +  ip rule add from 192.168.1.99 pref 100 table ctdb.192.168.1.99
 +  ip route add 192.168.1.0/24 dev eth2 table ctdb.192.168.1.99
 +      </pre><p>  
 +	This causes traffic from 192.168.1.1 to 192.168.1.0/24 go via
 +	eth2.
 +      </p><p>
 +	The <span class="command"><strong>ip rule</strong></span> command will show (something
 +	like - depending on other public addresses and other routes on
 +	the system):
 +      </p><pre class="screen">
 +  0:		from all lookup local 
 +  100:		from 192.168.1.99 lookup ctdb.192.168.1.99
 +  32766:	from all lookup main 
 +  32767:	from all lookup default 
 +      </pre><p>
 +	<span class="command"><strong>ip route show table ctdb.192.168.1.99</strong></span> will show:
 +      </p><pre class="screen">
 +  192.168.1.0/24 dev eth2 scope link
 +      </pre><p>
 +	The usual use for a line containing a gateway is to add a
 +	default route corresponding to a particular source address.
 +	Consider this line of configuration:
 +      </p><pre class="screen">
 +  192.168.1.99	0.0.0.0/0	192.168.1.1
 +      </pre><p>
 +	In the situation described above this will cause an extra
 +	routing command to be executed:
 +      </p><pre class="screen">
 +  ip route add 0.0.0.0/0 via 192.168.1.1 dev eth2 table ctdb.192.168.1.99
 +      </pre><p>
 +	With both configuration lines, <span class="command"><strong>ip route show table
 +	ctdb.192.168.1.99</strong></span> will show:
 +      </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="idp55911376"></a><h3>Sample configuration</h3><p>
++      </pre></div><div class="refsect2"><a name="idp55068864"></a><h3>Sample configuration</h3><p>
 +	Here is a more complete example configuration.
 +      </p><pre class="screen">
 +/etc/ctdb/public_addresses:
 +
 +  192.168.1.98	eth2,eth3
 +  192.168.1.99	eth2,eth3
 +
 +/etc/ctdb/policy_routing:
 +
 +  192.168.1.98 192.168.1.0/24
 +  192.168.1.98 192.168.200.0/24	192.168.1.254
 +  192.168.1.98 0.0.0.0/0 	192.168.1.1
 +  192.168.1.99 192.168.1.0/24
 +  192.168.1.99 192.168.200.0/24	192.168.1.254
 +  192.168.1.99 0.0.0.0/0 	192.168.1.1
 +      </pre><p>
 +	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="idp55914208"></a><h2>NOTIFICATION SCRIPT</h2><p>
++      </p></div></div><div class="refsect1"><a name="idp55071696"></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
 +      unhealthy or similar.
 +    </p><p>
 +      This is activated by setting the
 +      <code class="varname">CTDB_NOTIFY_SCRIPT</code> configuration variable.
 +      The specified script must be executable.  
 +    </p><p>
 +      Use of the provided <code class="filename">/etc/ctdb/notify.sh</code>
 +      script is recommended.  It executes files in
 +      <code class="filename">/etc/ctdb/notify.d/</code>.
 +    </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="idp55921232"></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="idp55078640"></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="idp55924928"></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="idp55082336"></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.
 +This is similar to how a WAN accelerator works but with the difference 
 +that while a WAN-accelerator often acts as a Proxy or a MitM, in 
 +the ctdb remote cluster node configuration the Samba instance at the remote site
 +IS the genuine server, not a proxy and not a MitM, and thus provides 100%
 +correct CIFS semantics to clients.
 +    </p><p>
 +	See the cluster as one single multihomed samba server where one of
 +	the NICs (the remote node) is very far away.
 +    </p><p>
 +	NOTE: This does require that the cluster filesystem you use can cope
 +	with WAN-link latencies. Not all cluster filesystems can handle
 +	WAN-link latencies! Whether this will provide very good WAN-accelerator
 +	performance or it will perform very poorly depends entirely
 +	on how optimized your cluster filesystem is in handling high latency
 +	for data and metadata operations.
 +    </p><p>
 +	To activate a node as being a remote cluster node you need to set
 +	the following two parameters in /etc/sysconfig/ctdb  for the remote node:
 +        </p><pre class="screen">
 +CTDB_CAPABILITY_LMASTER=no
 +CTDB_CAPABILITY_RECMASTER=no
 +	</pre><p>
 +    </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="idp55929712"></a><h2>SEE ALSO</h2><p>
++    </p></div><div class="refsect1"><a name="idp55087120"></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>,
 +
 +      <span class="citerefentry"><span class="refentrytitle">ctdbd_wrapper</span>(1)</span>,
 +
 +      <span class="citerefentry"><span class="refentrytitle">ltdbtool</span>(1)</span>,
 +
 +      <span class="citerefentry"><span class="refentrytitle">onnode</span>(1)</span>,
 +
 +      <span class="citerefentry"><span class="refentrytitle">ping_pong</span>(1)</span>,
 +
 +      <span class="citerefentry"><span class="refentrytitle">ctdbd.conf</span>(5)</span>,
 +
 +      <span class="citerefentry"><span class="refentrytitle">ctdb-statistics</span>(7)</span>,
 +
 +      <span class="citerefentry"><span class="refentrytitle">ctdb-tunables</span>(7)</span>,
 +
 +      <a class="ulink" href="http://ctdb.samba.org/" target="_top">http://ctdb.samba.org/</a>
 +    </p></div></div></body></html>
diff --cc ctdb/doc/ctdbd.1
index f719e74,0000000..f6928f4
mode 100644,000000..100644
--- a/ctdb/doc/ctdbd.1
+++ b/ctdb/doc/ctdbd.1
@@@ -1,386 -1,0 +1,386 @@@
 +'\" t
 +.\"     Title: ctdbd
 +.\"    Author: 
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 09/08/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: CTDB - clustered TDB database
 +.\"    Source: ctdb
 +.\"  Language: English
 +.\"
- .TH "CTDBD" "1" "09/08/2015" "ctdb" "CTDB \- clustered TDB database"
++.TH "CTDBD" "1" "12/10/2015" "ctdb" "CTDB \- clustered TDB database"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +ctdbd \- The CTDB cluster daemon
 +.SH "SYNOPSIS"
 +.HP \w'\fBctdbd\fR\ 'u
 +\fBctdbd\fR [\fIOPTION\fR...]
 +.SH "DESCRIPTION"
 +.PP
 +ctdbd is the main CTDB daemon\&.
 +.PP
 +Note that ctdbd is not usually invoked directly\&. It is invoked via
 +\fBctdbd_wrapper\fR(1)
 +or via the initscript\&.
 +.PP
 +See
 +\fBctdb\fR(7)
 +for an overview of CTDB\&.
 +.SH "GENERAL OPTIONS"
 +.PP
 +\-d, \-\-debug=\fIDEBUGLEVEL\fR
 +.RS 4
 +This option sets the debug level to DEBUGLEVEL, which controls what will be written by the logging subsystem\&. The default is 2\&.
 +.sp
 +See the
 +DEBUG LEVELS
 +section in
 +\fBctdb\fR(7)
 +for more information\&.
 +.RE
 +.PP
 +\-\-dbdir=\fIDIRECTORY\fR
 +.RS 4
 +DIRECTORY on local storage where ctdbd keeps a local copy of TDB databases\&. This directory is local for each node and should not be stored on the shared cluster filesystem\&.
 +.sp
 +This directory would usually be
 +/var/lib/ctdb
 +.RE
 +.PP
 +\-\-dbdir\-persistent=\fIDIRECTORY\fR
 +.RS 4
 +DIRECTORY on local storage where ctdbd keeps a local copy of persistent TDB databases\&. This directory is local for each node and should not be stored on the shared cluster filesystem\&.
 +.sp
 +This directory would usually be
 +/var/lib/ctdb/persistent
 +.RE
 +.PP
 +\-\-dbdir\-state=\fIDIRECTORY\fR
 +.RS 4
 +DIRECTORY on local storage where ctdbd keep internal state TDB files\&. This directory is local for each node and should not be stored on the shared cluster filesystem\&.
 +.sp
 +This directory would usually be
 +/var/lib/ctdb/state
 +.RE
 +.PP
 +\-\-event\-script\-dir=\fIDIRECTORY\fR
 +.RS 4
 +DIRECTORY where the CTDB event scripts are stored\&. See the
 +EVENT SCRIPTS
 +section in
 +\fBctdb\fR(7)
 +for more information\&.
 +.sp
 +Default is
 +\fBCTDB_BASE\fR/events\&.d, so usually
 +/etc/ctdb/events\&.d, which is part of the CTDB installation\&.
 +.RE
 +.PP
 +\-\-listen=\fIIPADDR\fR
 +.RS 4
 +IPADDR is the private IP address that ctdbd will bind to\&.
 +.sp
 +By default ctdbd will select the first address from the nodes list that in can bind to\&. See also
 +\-\-nlist\&.
 +.sp
 +This option is only required when automatic address detection can not be used\&. This can be the case when running multiple ctdbd daemons/nodes on the same physical host (usually for testing), using InfiniBand for the private network or on Linux when sysctl net\&.ipv4\&.ip_nonlocal_bind=1\&.
 +.RE
 +.PP
 +\-\-logging=\fISTRING\fR
 +.RS 4
 +STRING specifies where ctdbd will write its log\&. The default is file:/var/log/log\&.ctdb
 +or similar \- the prefix may differ depending on how CTDB was built\&.
 +.sp
 +Valid values are:
 +.PP
 +file:\fIFILENAME\fR
 +.RS 4
 +FILENAME where ctdbd will write its log\&. This is usually
 +/var/log/log\&.ctdb\&.
 +.RE
 +.PP
 +syslog[:\fIMETHOD\fR]
 +.RS 4
 +CTDB will log to syslog\&. By default this will use the syslog(3) API\&.
 +.sp
 +Under heavy loads syslog(3) can block if the syslog daemon processes messages too slowly\&. This can cause CTDB to block when logging\&.
 +.sp
 +If METHOD is specified then it specifies an extension that causes logging to be done in a non\-blocking mode\&. Note that
 +\fIthis may cause messages to be dropped\fR\&. METHOD must be one of:
 +.PP
 +nonblocking
 +.RS 4
 +CTDB will log to syslog via
 +/dev/log
 +in non\-blocking mode\&.
 +.RE
 +.PP
 +udp
 +.RS 4
 +CTDB will log to syslog via UDP to localhost:514\&. The syslog daemon must be configured to listen on (at least) localhost:514\&. Most syslog daemons will log the messages with hostname "localhost" \- this is a limitation of the implementation, for compatibility with more syslog daemons\&.
 +.RE
 +.PP
 +udp\-rfc5424
 +.RS 4
 +As with "udp" but messages are sent in RFC5424 format\&. This method will log the correct hostname but is not as widely implemented in syslog daemons\&.
 +.RE
 +.RE
 +.RE
 +.PP
 +\-\-lvs
 +.RS 4
 +This option is used to activate the LVS capability on a CTDB node\&. Please see the
 +LVS
 +section in
 +\fBctdb\fR(7)
 +for more information\&.
 +.RE
 +.PP
 +\-\-max\-persistent\-check\-errors=\fINUM\fR
 +.RS 4
 +NUM specifies the maximum number of health check failures allowed for persistent databases during startup\&.
 +.sp
 +The default value is 0\&. Setting this to non\-zero allows a node with unhealthy persistent databases to startup and join the cluster as long as there is another node with healthy persistent databases\&.
 +.RE
 +.PP
 +\-\-nlist=\fIFILENAME\fR
 +.RS 4
 +FILENAME containing a list of the private IP addresses, one per line, for each node in the cluster\&. This file
 +\fImust be the same on each node\fR
 +in the cluster\&.
 +.sp
 +Default is
 +\fBCTDB_BASE\fR/nodes, so usually
 +/etc/ctdb/nodes\&.
 +.RE
 +.PP
 +\-\-no\-lmaster
 +.RS 4
 +This argument specifies that this node can NOT become an lmaster for records in the database\&. This means that it will never show up in the vnnmap\&. This feature is primarily used for making a cluster span across a WAN link and use CTDB as a WAN\-accelerator\&.
 +.sp
 +Please see the
 +REMOTE CLUSTER NODES
 +section in
 +\fBctdb\fR(7)
 +for more information\&.
 +.RE
 +.PP
 +\-\-no\-recmaster
 +.RS 4
 +This argument specifies that this node can NOT become a recmaster for the database\&. This feature is primarily used for making a cluster span across a WAN link and use CTDB as a WAN\-accelerator\&.
 +.sp
 +Please see the
 +REMOTE CLUSTER NODES
 +section in
 +\fBctdb\fR(7)
 +for more information\&.
 +.RE
 +.PP
 +\-\-notification\-script=\fIFILENAME\fR
 +.RS 4
 +FILENAME specifying a script to be invoked by ctdbd when certain state changes occur\&.
 +.sp
 +This file is usually
 +/etc/ctdb/notify\&.sh\&.
 +.sp
 +Please see the
 +NOTIFICATION SCRIPT
 +section in
 +\fBctdb\fR(7)
 +for more information\&.
 +.RE
 +.PP
 +\-\-pidfile=\fIFILENAME\fR
 +.RS 4
 +FILENAME for file containing process ID of main CTDB daemon\&. This file is automatically created and removed by CTDB\&.
 +.sp
 +The default is to not create a PID file\&.
 +.RE
 +.PP
 +\-\-public_addresses=\fIFILENAME\fR
 +.RS 4
 +FILENAME specifying a file containing the public IP addresses to use on the cluster when CTDB should use IP takeover\&. This file contains a list of IP addresses, netmasks and interfaces\&. CTDB will distribute these public IP addresses appropriately across the available nodes\&.
 +.sp
 +The IP addresses specified in this file can differ across nodes\&.
 +.sp
 +This is usually the file
 +/etc/ctdb/public_addresses
 +.RE
 +.PP
 +\-\-public\-interface=\fIINTERFACE\fR
 +.RS 4
 +INTERFACE on which to attach public IP addresses or on which to attach the single\-public\-ip when used\&.
 +.sp
 +When using public IP addresses, this is only required if interfaces are not explicitly specified in the public addresses file\&.
 +.RE
 +.PP
 +\-\-reclock=\fIFILE\fR
 +.RS 4
 +FILE is the name of the recovery lock file, stored in
 +\fIshared storage\fR, that CTDB uses to prevent split brains\&.
 +.sp
 +For information about the recovery lock please see the
 +RECOVERY LOCK
 +section in
 +\fBctdb\fR(7)\&.
 +.RE
 +.PP
 +\-\-single\-public\-ip=\fIIPADDR\fR
 +.RS 4
 +IPADDR specifies the single IP that CTDB will use in conjuction with LVS\&.
 +.sp
 +Please see the
 +LVS
 +section in
 +\fBctdb\fR(7)
 +for more information\&.
 +.RE
 +.PP
 +\-\-start\-as\-disabled
 +.RS 4
 +This makes ctdbd start in the DISABLED state\&.
 +.sp
 +To allow the node to host public IP addresses and services, it must be manually enabled using the
 +\fBctdb enable\fR
 +command\&.
 +.sp
 +Please see the
 +NODE STATES
 +section in
 +\fBctdb\fR(7)
 +for more information about the DISABLED state\&.
 +.RE
 +.PP
 +\-\-start\-as\-stopped
 +.RS 4
 +This makes ctdbd start in the STOPPED state\&.
 +.sp
 +To allow the node to take part in the cluster it must be manually continued with the the
 +\fBctdb enable\fR
 +command\&.
 +.sp
 +Please see the
 +NODE STATES
 +section in
 +\fBctdb\fR(7)
 +for more information about the STOPPED state\&.
 +.RE
 +.PP
 +\-\-syslog
 +.RS 4
 +Send log messages to syslog instead of the CTDB logfile\&. This option overrides \-\-logfile\&. The default is to log to a file\&.
 +.RE
 +.PP
 +\-\-transport=tcp|infiniband
 +.RS 4
 +This option specifies which transport to use for ctdbd internode communications\&. The default is "tcp"\&.
 +.sp
 +The "infiniband" support is not regularly tested\&.
 +.RE
 +.PP
 +\-?, \-\-help
 +.RS 4
 +Display a summary of options\&.
 +.RE
 +.SH "DEBUGGING OPTIONS"
 +.PP
 +\-i, \-\-interactive
 +.RS 4
 +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 daemon\&.
 +.RE
 +.PP
 +\-\-nopublicipcheck
 +.RS 4
 +This option is used when testing with multiple local daemons on a single machine\&. It disables checks related to public IP addresses\&.
 +.RE
 +.PP
 +\-\-nosetsched
 +.RS 4
 +This is a debugging option\&. This option is only used when debugging ctdbd\&.
 +.sp
 +Normally ctdbd will change its scheduler to run as a real\-time process\&. This is the default mode for a normal ctdbd operation to gurarantee that ctdbd always gets the CPU cycles that it needs\&.
 +.sp
 +This option is used to tell ctdbd to
 +\fInot\fR
 +run as a real\-time process and instead run ctdbd as a normal userspace process\&. This is useful for debugging and when you want to run ctdbd under valgrind or gdb\&. (You don\*(Aqt want to attach valgrind or gdb to a real\-time process\&.)
 +.RE
 +.PP
 +\-\-socket=\fIFILENAME\fR
 +.RS 4
 +FILENAME specifies the name of the Unix domain socket that ctdbd will create\&. This socket is used by local clients to communicate with ctdbd\&.
 +.sp
 +The default is
 +/tmp/ctdb\&.socket
 +\&. You only need to use this option if you plan to run multiple ctdbd daemons on the same physical host, usually for testing\&.
 +.RE
 +.PP
 +\-\-script\-log\-level=\fIDEBUGLEVEL\fR
 +.RS 4
 +This option sets the debug level of event script output to DEBUGLEVEL\&. The default is ERR (0)\&.
 +.sp
 +See the
 +DEBUG LEVELS
 +section in
 +\fBctdb\fR(7)
 +for more information\&.
 +.RE
 +.PP
 +\-\-sloppy\-start
 +.RS 4
 +This is debugging option\&. This speeds up the initial recovery during startup at the expense of some consistency checking\&.
 +\fIDon\*(Aqt use this option in production\fR\&.
 +.RE
 +.PP
 +\-\-torture
 +.RS 4
 +This option is only used for development and testing of CTDB\&. It adds artificial errors and failures to the common codepaths in ctdbd to verify that ctdbd can recover correctly from failures\&.
 +.sp
 +\fIDo not use this option\fR
 +unless you are developing and testing new functionality in CTDB\&.
 +.RE
 +.PP
 +\-\-valgrinding
 +.RS 4
 +This is a debugging option\&. This option is only used when debugging ctdbd\&. This enables additional debugging capabilities and implies \-\-nosetsched\&.
 +.RE
 +.SH "SEE ALSO"
 +.PP
 +\fBctdb\fR(1),
 +\fBctdbd_wrapper\fR(1),
 +\fBonnode\fR(1),
 +\fBctdb\fR(7),
 +\fBctdb-tunables\fR(7),
 +\m[blue]\fB\%http://ctdb.samba.org/\fR\m[]
 +.SH "AUTHOR"
 +.br
 +.PP
 +This documentation was written by Ronnie Sahlberg, Amitay Isaacs, Martin Schwenke
 +.SH "COPYRIGHT"
 +.br
 +Copyright \(co 2007 Andrew Tridgell, Ronnie Sahlberg
 +.br
 +.PP
 +This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version\&.
 +.PP
 +This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE\&. See the GNU General Public License for more details\&.
 +.PP
 +You should have received a copy of the GNU General Public License along with this program; if not, see
 +\m[blue]\fB\%http://www.gnu.org/licenses\fR\m[]\&.
 +.sp
diff --cc ctdb/doc/ctdbd.1.html
index 13d230b,0000000..87b6712
mode 100644,000000..100644
--- a/ctdb/doc/ctdbd.1.html
+++ b/ctdb/doc/ctdbd.1.html
@@@ -1,286 -1,0 +1,286 @@@
- <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 — The CTDB cluster daemon</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><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.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 — The CTDB cluster daemon</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><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="idp52119744"></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="idp52972944"></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.
 +	  </p><p>
 +	    See the <em class="citetitle">DEBUG LEVELS</em> section in
 +	    <span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span> for more
 +	    information.
 +	  </p></dd><dt><span class="term">--dbdir=<em class="parameter"><code>DIRECTORY</code></em></span></dt><dd><p>
 +	    DIRECTORY on local storage where ctdbd keeps a local copy of
 +	    TDB databases.  This directory is local for each node and
 +	    should not be stored on the shared cluster filesystem.
 +	  </p><p>
 +	    This directory would usually be <code class="filename">/var/lib/ctdb</code>
 +	  </p></dd><dt><span class="term">--dbdir-persistent=<em class="parameter"><code>DIRECTORY</code></em></span></dt><dd><p>
 +	    DIRECTORY on local storage where ctdbd keeps a local copy of
 +	    persistent TDB databases.  This directory is local for each
 +	    node and should not be stored on the shared cluster
 +	    filesystem.
 +	  </p><p>
 +	    This directory would usually be
 +	    <code class="filename">/var/lib/ctdb/persistent</code>
 +	  </p></dd><dt><span class="term">--dbdir-state=<em class="parameter"><code>DIRECTORY</code></em></span></dt><dd><p>
 +	    DIRECTORY on local storage where ctdbd keep internal state
 +	    TDB files.  This directory is local for each node and
 +	    should not be stored on the shared cluster filesystem.
 +	  </p><p>
 +	    This directory would usually be
 +	    <code class="filename">/var/lib/ctdb/state</code>
 +	  </p></dd><dt><span class="term">--event-script-dir=<em class="parameter"><code>DIRECTORY</code></em></span></dt><dd><p>
 +	    DIRECTORY where the CTDB event scripts are stored.  See the
 +	    <em class="citetitle">EVENT SCRIPTS</em> section in
 +	    <span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span> for more information.
 +	  </p><p>
 +	    Default is <code class="envar">CTDB_BASE</code>/events.d, so usually
 +	    <code class="filename">/etc/ctdb/events.d</code>, which is part of
 +	    the CTDB installation.
 +	  </p></dd><dt><span class="term">--listen=<em class="parameter"><code>IPADDR</code></em></span></dt><dd><p>
 +	    IPADDR is the private IP address that ctdbd will bind to.
 +	  </p><p>
 +	    By default ctdbd will select the first address from the
 +	    nodes list that in can bind to.  See also
 +	    <em class="citetitle">--nlist</em>.
 +	  </p><p>
 +	    This option is only required when automatic address
 +	    detection can not be used.  This can be the case when
 +	    running multiple ctdbd daemons/nodes on the same physical
 +	    host (usually for testing), using InfiniBand for the
 +	    private network or on Linux when sysctl
 +	    net.ipv4.ip_nonlocal_bind=1.
 +	  </p></dd><dt><span class="term">--logging=<em class="parameter"><code>STRING</code></em></span></dt><dd><p>
 +	    STRING specifies where ctdbd will write its log. The
 +	    default is file:<code class="filename">/var/log/log.ctdb</code> or
 +	    similar - the prefix may differ depending on how CTDB was
 +	    built.
 +	  </p><p>
 +	    Valid values are:
 +	  </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">file:<em class="parameter"><code>FILENAME</code></em></span></dt><dd><p>
 +		  FILENAME where ctdbd will write its log. This is usually
 +		  <code class="filename">/var/log/log.ctdb</code>.
 +		</p></dd><dt><span class="term">syslog[<span class="optional">:<em class="parameter"><code>METHOD</code></em></span>]</span></dt><dd><p>
 +		  CTDB will log to syslog.  By default this will use
 +		  the syslog(3) API.
 +                </p><p>
 +		  Under heavy loads syslog(3) can block if the syslog
 +		  daemon processes messages too slowly.  This can
 +		  cause CTDB to block when logging.
 +		</p><p>
 +		  If METHOD is specified then it specifies an
 +		  extension that causes logging to be done in a
 +		  non-blocking mode.  Note that <span class="emphasis"><em>this may
 +		  cause messages to be dropped</em></span>.  METHOD
 +		  must be one of:
 +		</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">nonblocking</span></dt><dd><p>
 +			CTDB will log to syslog via
 +			<code class="filename">/dev/log</code> in non-blocking
 +			mode.
 +		      </p></dd><dt><span class="term">udp</span></dt><dd><p>
 +			CTDB will log to syslog via UDP to
 +			localhost:514.  The syslog daemon must be
 +			configured to listen on (at least)
 +			localhost:514.  Most syslog daemons will log
 +			the messages with hostname "localhost" - this
 +			is a limitation of the implementation, for
 +			compatibility with more syslog daemons.
 +		      </p></dd><dt><span class="term">udp-rfc5424</span></dt><dd><p>
 +			As with "udp" but messages are sent in RFC5424
 +			format.  This method will log the correct
 +			hostname but is not as widely implemented in
 +			syslog daemons.
 +		      </p></dd></dl></div></dd></dl></div></dd><dt><span class="term">--lvs</span></dt><dd><p>
 +	    This option is used to activate the LVS capability on a CTDB
 +	    node.  Please see the <em class="citetitle">LVS</em> section in
 +	    <span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span> for more
 +	    information.
 +	  </p></dd><dt><span class="term">--max-persistent-check-errors=<em class="parameter"><code>NUM</code></em></span></dt><dd><p>
 +	    NUM specifies the maximum number of health check failures
 +	    allowed for persistent databases during startup.
 +	  </p><p>
 +	    The default value is 0.  Setting this to non-zero allows a
 +	    node with unhealthy persistent databases to startup and
 +	    join the cluster as long as there is another node with
 +	    healthy persistent databases.
 +	  </p></dd><dt><span class="term">--nlist=<em class="parameter"><code>FILENAME</code></em></span></dt><dd><p>
 +	    FILENAME containing a list of the private IP addresses, one
 +	    per line, for each node in the cluster.  This file
 +	    <span class="emphasis"><em>must be the same on each node</em></span> in the
 +	    cluster.
 +	  </p><p>
 +	    Default is <code class="envar">CTDB_BASE</code>/nodes, so usually
 +	    <code class="filename">/etc/ctdb/nodes</code>.
 +	  </p></dd><dt><span class="term">--no-lmaster</span></dt><dd><p>
 +	    This argument specifies that this node can NOT become an lmaster
 +	    for records in the database. This means that it will never show up
 +	    in the vnnmap. This feature is primarily used for making a cluster
 +	    span across a WAN link and use CTDB as a WAN-accelerator.
 +	  </p><p>
 +	    Please see the <em class="citetitle">REMOTE CLUSTER NODES</em>
 +	    section in <span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span> for more
 +	    information.
 +	  </p></dd><dt><span class="term">--no-recmaster</span></dt><dd><p>
 +	    This argument specifies that this node can NOT become a recmaster
 +	    for the database. This feature is primarily used for making a cluster
 +	    span across a WAN link and use CTDB as a WAN-accelerator.
 +	  </p><p>
 +	    Please see the <em class="citetitle">REMOTE CLUSTER NODES</em>
 +	    section in <span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span> for more
 +	    information.
 +	  </p></dd><dt><span class="term">--notification-script=<em class="parameter"><code>FILENAME</code></em></span></dt><dd><p>
 +	    FILENAME specifying a script to be invoked by ctdbd when
 +	    certain state changes occur.
 +	  </p><p>
 +	    This file is usually
 +	    <code class="filename">/etc/ctdb/notify.sh</code>.
 +	  </p><p>
 +	    Please see the <em class="citetitle">NOTIFICATION SCRIPT</em>
 +	    section in <span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span> for more
 +	    information.
 +	  </p></dd><dt><span class="term">--pidfile=<em class="parameter"><code>FILENAME</code></em></span></dt><dd><p>
 +	    FILENAME for file containing process ID of main CTDB
 +	    daemon.  This file is automatically created and removed by
 +	    CTDB.
 +	  </p><p>
 +	    The default is to not create a PID file.
 +	  </p></dd><dt><span class="term">--public_addresses=<em class="parameter"><code>FILENAME</code></em></span></dt><dd><p>
 +	    FILENAME specifying a file containing the public IP
 +	    addresses to use on the cluster when CTDB should use IP
 +	    takeover. This file contains a list of IP addresses,
 +	    netmasks and interfaces.  CTDB will distribute these public
 +	    IP addresses appropriately across the available nodes.
 +	  </p><p>
 +	    The IP addresses specified in this file can differ across
 +	    nodes.
 +	  </p><p>
 +	    This is usually the file
 +	    <code class="filename">/etc/ctdb/public_addresses</code>
 +	  </p></dd><dt><span class="term">--public-interface=<em class="parameter"><code>INTERFACE</code></em></span></dt><dd><p>
 +	    INTERFACE on which to attach public IP addresses or on which
 +	    to attach the single-public-ip when used.
 +	  </p><p>
 +	    When using public IP addresses, this is only required if
 +	    interfaces are not explicitly specified in the public
 +	    addresses file.
 +	  </p></dd><dt><span class="term">--reclock=<em class="parameter"><code>FILE</code></em></span></dt><dd><p>
 +	    FILE is the name of the recovery lock file, stored in
 +	    <span class="emphasis"><em>shared storage</em></span>, that CTDB uses to
 +	    prevent split brains.
 +	  </p><p>
 +	    For information about the recovery lock please see the
 +	    <em class="citetitle">RECOVERY LOCK</em> section in
 +	    <span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span>.
 +	  </p></dd><dt><span class="term">--single-public-ip=<em class="parameter"><code>IPADDR</code></em></span></dt><dd><p>
 +	    IPADDR specifies the single IP that CTDB will use in
 +	    conjuction with LVS.
 +	  </p><p>
 +	    Please see the <em class="citetitle">LVS</em> section in
 +	    <span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span> for more
 +	    information.
 +	  </p></dd><dt><span class="term">--start-as-disabled</span></dt><dd><p>
 +	    This makes ctdbd start in the DISABLED state.
 +	  </p><p>
 +	    To allow the node to host public IP addresses and
 +	    services, it must be manually enabled using the
 +	    <span class="command"><strong>ctdb enable</strong></span> command.
 +	  </p><p>
 +	    Please see the <em class="citetitle">NODE STATES</em> section
 +	    in <span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span> for more
 +	    information about the DISABLED state.
 +	  </p></dd><dt><span class="term">--start-as-stopped</span></dt><dd><p>
 +	    This makes ctdbd start in the STOPPED state.
 +	  </p><p>
 +	    To allow the node to take part in the cluster it must be
 +	    manually continued with the the <span class="command"><strong>ctdb
 +	    enable</strong></span> command.
 +	  </p><p>
 +	    Please see the <em class="citetitle">NODE STATES</em> section
 +	    in <span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span> for more
 +	    information about the STOPPED state.
 +	  </p></dd><dt><span class="term">--syslog</span></dt><dd><p>
 +	    Send log messages to syslog instead of the CTDB logfile.
 +	    This option overrides --logfile.  The default is to log to
 +	    a file.
 +	  </p></dd><dt><span class="term">--transport=tcp|infiniband</span></dt><dd><p>
 +	    This option specifies which transport to use for ctdbd
 +	    internode communications. The default is "tcp".
 +	  </p><p>
 +	    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="idp54951424"></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="idp54745248"></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
 +	    daemon.
 +	  </p></dd><dt><span class="term">--nopublicipcheck</span></dt><dd><p>
 +	    This option is used when testing with multiple local
 +	    daemons on a single machine.  It disables checks related
 +	    to public IP addresses.
 +	  </p></dd><dt><span class="term">--nosetsched</span></dt><dd><p>
 +	    This is a debugging option. This option is only used when
 +	    debugging ctdbd.
 +	  </p><p>
 +	    Normally ctdbd will change its scheduler to run as a
 +	    real-time process. This is the default mode for a normal
 +	    ctdbd operation to gurarantee that ctdbd always gets the CPU
 +	    cycles that it needs.
 +	  </p><p>
 +	    This option is used to tell ctdbd to
 +	    <span class="emphasis"><em>not</em></span> run as a real-time process and
 +	    instead run ctdbd as a normal userspace process.  This is
 +	    useful for debugging and when you want to run ctdbd under
 +	    valgrind or gdb. (You don't want to attach valgrind or gdb
 +	    to a real-time process.)
 +	  </p></dd><dt><span class="term">--socket=<em class="parameter"><code>FILENAME</code></em></span></dt><dd><p>
 +	    FILENAME specifies the name of the Unix domain socket that
 +	    ctdbd will create. This socket is used by local clients to
 +	    communicate with ctdbd.
 +	  </p><p>
 +	    The default is <code class="filename">/tmp/ctdb.socket</code> . You
 +	    only need to use this option if you plan to run multiple
 +	    ctdbd daemons on the same physical host, usually for
 +	    testing.
 +	  </p></dd><dt><span class="term">--script-log-level=<em class="parameter"><code>DEBUGLEVEL</code></em></span></dt><dd><p>
 +	    This option sets the debug level of event script output to
 +	    DEBUGLEVEL.  The default is ERR (0).
 +	  </p><p>
 +	    See the <em class="citetitle">DEBUG LEVELS</em> section in
 +	    <span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span> for more
 +	    information.
 +	  </p></dd><dt><span class="term">--sloppy-start</span></dt><dd><p>
 +	    This is debugging option.  This speeds up the initial
 +	    recovery during startup at the expense of some consistency
 +	    checking.  <span class="emphasis"><em>Don't use this option in
 +	    production</em></span>.
 +	  </p></dd><dt><span class="term">--torture</span></dt><dd><p>
 +	    This option is only used for development and testing of
 +	    CTDB.  It adds artificial errors and failures to the
 +	    common codepaths in ctdbd to verify that ctdbd can recover
 +	    correctly from failures.
 +	  </p><p>
 +	    <span class="emphasis"><em>Do not use this option</em></span> unless you are
 +	    developing and testing new functionality in CTDB.
 +	  </p></dd><dt><span class="term">--valgrinding</span></dt><dd><p>
 +	    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="idp54972912"></a><h2>SEE ALSO</h2><p>
++	  </p></dd></dl></div></div><div class="refsect1"><a name="idp54766736"></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>,
 +
 +      <span class="citerefentry"><span class="refentrytitle">onnode</span>(1)</span>,
 +
 +      <span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span>,
 +
 +      <span class="citerefentry"><span class="refentrytitle">ctdb-tunables</span>(7)</span>,
 +
 +      <a class="ulink" href="http://ctdb.samba.org/" target="_top">http://ctdb.samba.org/</a>
 +    </p></div></div></body></html>
diff --cc ctdb/doc/ctdbd.conf.5
index e022f84,0000000..e62e3a6
mode 100644,000000..100644
--- a/ctdb/doc/ctdbd.conf.5
+++ b/ctdb/doc/ctdbd.conf.5
@@@ -1,1064 -1,0 +1,1064 @@@
 +'\" t
 +.\"     Title: ctdbd.conf
 +.\"    Author: 
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 09/08/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: CTDB - clustered TDB database
 +.\"    Source: ctdb
 +.\"  Language: English
 +.\"
- .TH "CTDBD\&.CONF" "5" "09/08/2015" "ctdb" "CTDB \- clustered TDB database"
++.TH "CTDBD\&.CONF" "5" "12/10/2015" "ctdb" "CTDB \- clustered TDB database"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +ctdbd.conf \- CTDB daemon configuration file
 +.SH "DESCRIPTION"
 +.PP
 +This file contains CTDB configuration variables that are affect the operation of CTDB\&. The default location of this file is
 +/etc/ctdb/ctdbd\&.conf\&.
 +.PP
 +This file is a shell script (see
 +\fBsh\fR(1)) but is usually limited to simple variable assignments and shell\-style comments\&.
 +.PP
 +CTDB configuration variables are grouped into several categories below\&.
 +.PP
 +Variables defined in this document can also be set in a distribution\-specific configuration file such as
 +/etc/sysconfig/ctdb
 +(Red Hat) or
 +/etc/default/ctdb
 +(Debian)\&. However, these files should be reserved for variables used by the initscript\&. A historical alternative is
 +/etc/ctdb/sysconfig/ctdb
 +\- this is deprecated\&.
 +.SH "INITSCRIPT CONFIGURATION"
 +.PP
 +Some options must be available to the initscript so they need to be set in the distribution\-specific initscript configuration, such as
 +/etc/sysconfig/ctdb
 +or
 +/etc/default/ctdb\&.
 +.PP
 +CTDB_PIDFILE=\fIFILENAME\fR
 +.RS 4
 +FILENAME is the name of the file used to contain the process ID (PID) of the main CTDB daemon when it is running\&. This is passed from the initscript to
 +\fBctdbd_wrapper\fR(1)\&.
 +.sp
 +Default is
 +/var/run/ctdb/ctdbd\&.pid\&. Corresponds to
 +\fB\-\-pidfile\fR\&.
 +.RE
 +.SH "GLOBAL CONFIGURATION"
 +.PP
 +These options may be used in the initscripts, daemon and scripts\&.
 +.PP
 +CTDB_BASE=\fIDIRECTORY\fR
 +.RS 4
 +DIRECTORY containing CTDB scripts and configuration files\&.
 +.RE
 +.PP
 +CTDB_VARDIR=\fIDIRECTORY\fR
 +.RS 4
 +DIRECTORY containing CTDB files that are modified at runtime\&.
 +.sp
 +Defaults to
 +/var/ctdb, unless
 +/var/lib/ctdb
 +already exists in which case it is used\&.
 +.RE
 +.SH "DAEMON CONFIGURATION"
 +.PP
 +Variables in this section are processed by
 +\fBctdbd_wrapper\fR(1)
 +and are converted into command\-line arguments to
 +\fBctdbd\fR(1)\&. Correspondence with
 +\fBctdbd\fR(1)
 +options is shown for each variable\&. The the documentation for the relevant options for more details\&.
 +.PP
 +Many of these variables are also used by event scripts\&.
 +.PP
 +CTDB_CAPABILITY_LMASTER=yes|no
 +.RS 4
 +Defaults to yes\&. Corresponds to
 +\fB\-\-no\-lmaster\fR\&.
 +.RE
 +.PP
 +CTDB_CAPABILITY_RECMASTER=yes|no
 +.RS 4
 +Defaults to yes\&. Corresponds to
 +\fB\-\-no\-recmaster\fR\&.
 +.RE
 +.PP
 +CTDB_DBDIR=\fIDIRECTORY\fR
 +.RS 4
 +Defaults to
 +\fICTDB_VARDIR\fR\&. Corresponds to
 +\fB\-\-dbdir\fR\&.
 +.RE
 +.PP
 +CTDB_DBDIR_PERSISTENT=\fIDIRECTORY\fR
 +.RS 4
 +Defaults to
 +\fICTDB_VARDIR\fR/persistent\&. Corresponds to
 +\fB\-\-dbdir\-persistent\fR\&.
 +.RE
 +.PP
 +CTDB_DBDIR_STATE=\fIDIRECTORY\fR
 +.RS 4
 +Defaults to
 +\fICTDB_VARDIR\fR/state\&. Corresponds to
 +\fB\-\-dbdir\-state\fR\&.
 +.RE
 +.PP
 +CTDB_DEBUGLEVEL=\fIDEBUGLEVEL\fR
 +.RS 4
 +Default is NOTICE (2)\&. Corresponds to
 +\fB\-d\fR
 +or
 +\fB\-\-debug\fR\&.
 +.RE
 +.PP
 +CTDB_EVENT_SCRIPT_DIR=\fIDIRECTORY\fR
 +.RS 4
 +Default is
 +\fICTDB_BASE\fR/events\&.d, so usually
 +/etc/ctdb/events\&.d\&. Corresponds to
 +\fB\-\-event\-script\-dir\fR\&.
 +.RE
 +.PP
 +CTDB_LOGGING=\fISTRING\fR
 +.RS 4
 +STRING specifies where ctdbd will write its log\&. The default is file:/var/log/log\&.ctdb
 +or similar \- the prefix may differ depending on how CTDB was built\&. Corresponds to
 +\fB\-\-logging\fR\&.
 +.sp
 +Valid values are:
 +.PP
 +file:\fIFILENAME\fR
 +.RS 4
 +FILENAME where ctdbd will write its log\&. This is usually
 +/var/log/log\&.ctdb\&.
 +.RE
 +.PP
 +syslog[:\fIMETHOD\fR]
 +.RS 4
 +CTDB will log to syslog\&. By default this will use the syslog(3) API\&.
 +.sp
 +If METHOD is specified then it specifies an extension that causes logging to be done in a non\-blocking fashion\&. This can be useful under heavy loads that might cause the syslog daemon to dequeue messages too slowly, which would otherwise cause CTDB to block when logging\&. METHOD must be one of:
 +.PP
 +nonblocking
 +.RS 4
 +CTDB will log to syslog via
 +/dev/log
 +in non\-blocking mode\&.
 +.RE
 +.PP
 +udp
 +.RS 4
 +CTDB will log to syslog via UDP to localhost:514\&. The syslog daemon must be configured to listen on (at least) localhost:514\&. Most implementations will log the messages against hostname "localhost" \- this is a limit of the implementation for compatibility with more syslog daemon implementations\&.
 +.RE
 +.PP
 +udp\-rfc5424
 +.RS 4
 +As with "udp" but messages are sent in RFC5424 format\&. This method will log the correct hostname but is not as widely implemented in syslog daemons\&.
 +.RE
 +.RE
 +.RE
 +.PP
 +CTDB_LVS_PUBLIC_IP=\fIIPADDR\fR
 +.RS 4
 +No default\&. Corresponds to "\fB\-\-lvs\fR\fB\-\-single\-public\-ip IPADDR"\fR\&.
 +.RE
 +.PP
 +CTDB_NODES=\fIFILENAME\fR
 +.RS 4
 +Default is
 +\fICTDB_BASE\fR/nodes, so usually
 +/etc/ctdb/nodes\&. Corresponds to
 +\fB\-\-nlist\fR\&.
 +.RE
 +.PP
 +CTDB_NOTIFY_SCRIPT=\fIFILENAME\fR
 +.RS 4
 +No default, usually
 +/etc/ctdb/notify\&.sh\&. Corresponds to
 +\fB\-\-notification\-script\fR\&.
 +.RE
 +.PP
 +CTDB_MAX_PERSISTENT_CHECK_ERRORS=\fINUM\fR
 +.RS 4
 +Default 0\&. Corresponds to
 +\fB\-\-max\-persistent\-check\-errors\fR\&.
 +.RE
 +.PP
 +CTDB_NODE_ADDRESS=\fIFILENAME\fR
 +.RS 4
 +IPADDR is the private IP address that ctdbd will bind to\&. Corresponds to
 +\fB\-\-listen\fR\&.
 +.sp
 +By default ctdbd will select the first address from the nodes list that in can bind to\&. See also
 +CTDB_NODES\&.
 +.sp
 +This option is only required when automatic address detection can not be used\&. This can be the case when running multiple ctdbd daemons/nodes on the same physical host (usually for testing), using InfiniBand for the private network or on Linux when sysctl net\&.ipv4\&.ip_nonlocal_bind=1\&.
 +.RE
 +.PP
 +CTDB_PUBLIC_ADDRESSES=\fIFILENAME\fR
 +.RS 4
 +No default, usually
 +/etc/ctdb/public_addresses\&. Corresponds to
 +\fB\-\-public\-addresses\fR\&.
 +.RE
 +.PP
 +CTDB_PUBLIC_INTERFACE=\fIINTERFACE\fR
 +.RS 4
 +No default\&. Corresponds to
 +\fB\-\-public\-interface\fR\&.
 +.RE
 +.PP
 +CTDB_RECOVERY_LOCK=\fIFILENAME\fR
 +.RS 4
 +Defaults to
 +/some/place/on/shared/storage, which should be change to a useful value\&. Corresponds to
 +\fB\-\-reclock\fR\&.
 +.sp
 +For information about the recovery lock please see the
 +RECOVERY LOCK
 +section in
 +\fBctdb\fR(7)\&.
 +.RE
 +.PP
 +CTDB_SCRIPT_LOG_LEVEL=\fIDEBUGLEVEL\fR
 +.RS 4
 +Defaults to ERR (0)\&. Corresponds to
 +\fB\-\-script\-log\-level\fR\&.
 +.RE
 +.PP
 +CTDB_SOCKET=\fIFILENAME\fR
 +.RS 4
 +Defaults to
 +/tmp/ctdb\&.socket\&. Corresponds to
 +\fB\-\-socket\fR\&.
 +.sp
 +If you change this then you probably want to set this in root\*(Aqs enviroment (perhaps in a file in
 +/etc/profile\&.d) so that you can use the
 +\fBctdb\fR(1)
 +command in a straightforward manner\&.
 +.RE
 +.PP
 +CTDB_START_AS_DISABLED=yes|no
 +.RS 4
 +Default is no\&. Corresponds to
 +\fB\-\-start\-as\-disabled\fR\&.
 +.RE
 +.PP
 +CTDB_START_AS_STOPPED=yes|no
 +.RS 4
 +Default is no\&. Corresponds to
 +\fB\-\-start\-as\-stopped\fR\&.
 +.RE
 +.PP
 +CTDB_TRANSPORT=tcp|infiniband
 +.RS 4
 +Defaults to tcp\&. Corresponds to
 +\fB\-\-transport\fR\&.
 +.RE
 +.PP
 +While the following variables do not translate into daemon options they are used by
 +\fBctdbd_wrapper\fR(1)
 +when starting and stopping
 +\fBctdbd\fR(1)\&.
 +.PP
 +CTDB_SHUTDOWN_TIMEOUT=\fINUM\fR
 +.RS 4
 +NUM is the number of seconds to wait for
 +\fBctdbd\fR(1)
 +to shut down gracefully before giving up and killing it\&.
 +.sp
 +Defaults is 30\&.
 +.RE
 +.PP
 +CTDB_STARTUP_TIMEOUT=\fINUM\fR
 +.RS 4
 +NUM is the number of seconds to wait for
 +\fBctdbd\fR(1)
 +complete early initialisation up to a point where it is unlikely to abort\&. If
 +\fBctdbd\fR
 +doesn\*(Aqt complete the "setup" event before this timeout then it is killed\&.
 +.sp
 +Defaults is 10\&.
 +.RE
 +.SH "NETWORK CONFIGURATION"
 +.SS "NAT GATEWAY"
 +.PP
 +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 external infrastructure\&. One node in a NAT gateway group will be designated as the NAT gateway master node and other (slave) nodes will be configured with fallback routes via the NAT gateway master node\&. For more information, see the
 +NAT GATEWAY
 +section in
 +\fBctdb\fR(7)\&.
 +.PP
 +CTDB_NATGW_DEFAULT_GATEWAY=\fIIPADDR\fR
 +.RS 4
 +IPADDR is an alternate network gateway to use on the NAT gateway master node\&. If set, a fallback default route is added via this network gateway\&.
 +.sp
 +No default\&. Setting this variable is optional \- if not set that no route is created on the NAT gateway master node\&.
 +.RE
 +.PP
 +CTDB_NATGW_NODES=\fIFILENAME\fR
 +.RS 4
 +FILENAME contains the list of nodes that belong to the same NAT gateway group\&.
 +.sp
 +File format:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +\fIIPADDR\fR
 +	      
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.sp
 +No default, usually
 +/etc/ctdb/natgw_nodes
 +when enabled\&.
 +.RE
 +.PP
 +CTDB_NATGW_PRIVATE_NETWORK=\fIIPADDR/MASK\fR
 +.RS 4
 +IPADDR/MASK is the private sub\-network that is internally routed via the NAT gateway master node\&. This is usually the private network that is used for node addresses\&.
 +.sp
 +No default\&.
 +.RE
 +.PP
 +CTDB_NATGW_PUBLIC_IFACE=\fIIFACE\fR
 +.RS 4
 +IFACE is the network interface on which the CTDB_NATGW_PUBLIC_IP will be configured\&.
 +.sp
 +No default\&.
 +.RE
 +.PP
 +CTDB_NATGW_PUBLIC_IP=\fIIPADDR/MASK\fR
 +.RS 4
 +IPADDR/MASK indicates the IP address that is used for outgoing traffic (originating from CTDB_NATGW_PRIVATE_NETWORK) on the NAT gateway master node\&. This
 +\fImust not\fR
 +be a configured public IP address\&.
 +.sp
 +No default\&.
 +.RE
 +.PP
 +CTDB_NATGW_SLAVE_ONLY=yes|no
 +.RS 4
 +When set to "yes" a node can not be a NAT gateway master node\&. In this case
 +\fICTDB_NATGW_PUBLIC_IFACE\fR
 +and
 +\fICTDB_NATGW_PUBLIC_IP\fR
 +are optional and unused\&.
 +.sp
 +Default is no\&.
 +.RE
 +.PP
 +CTDB_NATGW_STATIC_ROUTES=\fIIPADDR/MASK[@GATEWAY]\fR \&.\&.\&.
 +.RS 4
 +Each IPADDR/MASK identifies a network or host to which NATGW should create a fallback route, instead of creating a single default route\&. This can be used when there is already a default route, via an interface that can not reach required infrastructure, that overrides the NAT gateway default route\&.
 +.sp
 +If GATEWAY is specified then the corresponding route on the NATGW master node will be via GATEWAY\&. Such routes are created even if
 +\fICTDB_NATGW_DEFAULT_GATEWAY\fR
 +is not specified\&. If GATEWAY is not specified for some networks then routes are only created on the NATGW master node for those networks if
 +\fICTDB_NATGW_DEFAULT_GATEWAY\fR
 +is specified\&.
 +.sp
 +This should be used with care to avoid causing traffic to unnecessarily double\-hop through the NAT gateway master, even when a node is hosting public IP addresses\&. Each specified network or host should probably have a corresponding automatically created link route or static route to avoid this\&.
 +.sp
 +No default\&.
 +.RE
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBExample\fR
 +.RS 4
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +CTDB_NATGW_NODES=/etc/ctdb/natgw_nodes
 +CTDB_NATGW_PRIVATE_NETWORK=192\&.168\&.1\&.0/24
 +CTDB_NATGW_DEFAULT_GATEWAY=10\&.0\&.0\&.1
 +CTDB_NATGW_PUBLIC_IP=10\&.0\&.0\&.227/24
 +CTDB_NATGW_PUBLIC_IFACE=eth0
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +A variation that ensures that infrastructure (ADS, DNS, \&.\&.\&.) directly attached to the public network (10\&.0\&.0\&.0/24) is always reachable would look like this:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +CTDB_NATGW_NODES=/etc/ctdb/natgw_nodes
 +CTDB_NATGW_PRIVATE_NETWORK=192\&.168\&.1\&.0/24
 +CTDB_NATGW_PUBLIC_IP=10\&.0\&.0\&.227/24
 +CTDB_NATGW_PUBLIC_IFACE=eth0
 +CTDB_NATGW_STATIC_ROUTES=10\&.0\&.0\&.0/24
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +Note that
 +\fICTDB_NATGW_DEFAULT_GATEWAY\fR
 +is not specified\&.
 +.RE
 +.SS "POLICY ROUTING"
 +.PP
 +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 possible to route packets from these public addresses via the system\*(Aqs default route\&. Therefore, CTDB has support for policy routing via the
 +13\&.per_ip_routing
 +eventscript\&. 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\&.
 +.PP
 +For more information, see the
 +POLICY ROUTING
 +section in
 +\fBctdb\fR(7)\&.
 +.PP
 +CTDB_PER_IP_ROUTING_CONF=\fIFILENAME\fR
 +.RS 4
 +FILENAME contains elements for constructing the desired routes for each source address\&.
 +.sp
 +The special FILENAME value
 +\fB__auto_link_local__\fR
 +indicates that no configuration file is provided and that CTDB should generate reasonable link\-local routes for each public IP address\&.
 +.sp
 +File format:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +\fIIPADDR\fR \fIDEST\-IPADDR/MASK\fR [\fIGATEWAY\-IPADDR\fR]
 +	      
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.sp
 +No default, usually
 +/etc/ctdb/policy_routing
 +when enabled\&.
 +.RE
 +.PP
 +CTDB_PER_IP_ROUTING_RULE_PREF=\fINUM\fR
 +.RS 4
 +NUM sets the priority (or preference) for the routing rules that are added by CTDB\&.
 +.sp
 +This should be (strictly) greater than 0 and (strictly) less than 32766\&. A priority of 100 is recommended, unless this conflicts with a priority already in use on the system\&. See
 +\fBip\fR(8), for more details\&.
 +.RE
 +.PP
 +CTDB_PER_IP_ROUTING_TABLE_ID_LOW=\fILOW\-NUM\fR, CTDB_PER_IP_ROUTING_TABLE_ID_HIGH=\fIHIGH\-NUM\fR
 +.RS 4
 +CTDB determines a unique routing table number to use for the routing related to each public address\&. LOW\-NUM and HIGH\-NUM indicate the minimum and maximum routing table numbers that are used\&.
 +.sp
 +\fBip\fR(8)
 +uses some reserved routing table numbers below 255\&. Therefore, CTDB_PER_IP_ROUTING_TABLE_ID_LOW should be (strictly) greater than 255\&.
 +.sp
 +CTDB uses the standard file
 +/etc/iproute2/rt_tables
 +to maintain a mapping between the routing table numbers and labels\&. The label for a public address
 +\fIADDR\fR
 +will look like ctdb\&.\fIaddr\fR\&. This means that the associated rules and routes are easy to read (and manipulate)\&.
 +.sp
 +No default, usually 1000 and 9000\&.
 +.RE
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBExample\fR
 +.RS 4
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +CTDB_PER_IP_ROUTING_CONF=/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
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.SS "MISCELLANEOUS NETWORK CONFIGURATION"
 +.PP
 +CTDB_PARTIALLY_ONLINE_INTERFACES=yes|no
 +.RS 4
 +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 that are down then
 +\fBctdb status\fR
 +will display the node as "PARTIALLYONLINE"\&.
 +.sp
 +Default is "no"\&.
 +.RE
 +.SH "SERVICE CONFIGURATION"
 +.PP
 +CTDB can be configured to manage and/or monitor various NAS (and other) services via its eventscripts\&.
 +.PP
 +In the simplest case CTDB will manage a service\&. This means the service will be started and stopped along with CTDB, CTDB will monitor the service and CTDB will do any required reconfiguration of the service when public IP addresses are failed over\&.
 +.SS "SAMBA"
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBEventscripts\fR
 +.RS 4
 +.RS 4
 +49\&.winbind
 +.RE
 +.RS 4
 +50\&.samba
 +.RE
 +.RE
 +.PP
 +CTDB_MANAGES_SAMBA=yes|no
 +.RS 4
 +Should CTDB manage Samba?
 +.sp
 +Default is no\&.
 +.RE
 +.PP
 +CTDB_MANAGES_WINBIND=yes|no
 +.RS 4
 +Should CTDB manage Winbind?
 +.sp
 +Default is no\&.
 +.RE
 +.PP
 +CTDB_SAMBA_CHECK_PORTS=\fIPORT\-LIST\fR
 +.RS 4
 +When monitoring Samba, check TCP ports in space\-separated PORT\-LIST\&.
 +.sp
 +Default is to monitor ports that Samba is configured to listen on\&.
 +.RE
 +.PP
 +CTDB_SAMBA_SKIP_SHARE_CHECK=yes|no
 +.RS 4
 +As part of monitoring, should CTDB skip the check for the existence of each directory configured as share in Samba\&. This may be desirable if there is a large number of shares\&.
 +.sp
 +Default is no\&.
 +.RE
 +.PP
 +CTDB_SERVICE_NMB=\fISERVICE\fR
 +.RS 4
 +Distribution specific SERVICE for managing nmbd\&.
 +.sp
 +Default is distribution\-dependant\&.
 +.RE
 +.PP
 +CTDB_SERVICE_SMB=\fISERVICE\fR
 +.RS 4
 +Distribution specific SERVICE for managing smbd\&.
 +.sp
 +Default is distribution\-dependant\&.
 +.RE
 +.PP
 +CTDB_SERVICE_WINBIND=\fISERVICE\fR
 +.RS 4
 +Distribution specific SERVICE for managing winbindd\&.
 +.sp
 +Default is "winbind"\&.
 +.RE
 +.SS "NFS"
 +.PP
 +This includes parameters for the kernel NFS server\&. Alternative NFS subsystems (such as
 +\m[blue]\fBNFS\-Ganesha\fR\m[]\&\s-2\u[1]\d\s+2) can be integrated using
 +\fICTDB_NFS_CALLOUT\fR\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBEventscript\fR
 +.RS 4
 +.RS 4
 +60\&.nfs
 +.RE
 +.RE
 +.PP
 +CTDB_CLUSTER_FILESYSTEM_TYPE=gpfs
 +.RS 4
 +The type of cluster filesystem to use with NFS\-ganesha\&. Currently only "gpfs" is supported\&.
 +.sp
 +Default is "gpfs"\&.
 +.RE
 +.PP
 +CTDB_MANAGES_NFS=yes|no
 +.RS 4
 +Should CTDB manage NFS?
 +.sp
 +Default is no\&.
 +.RE
 +.PP
 +CTDB_NFS_CALLOUT=\fICOMMAND\fR
 +.RS 4
 +COMMAND specifies the path to a callout to handle interactions with the configured NFS system, including startup, shutdown, monitoring\&.
 +.sp
 +Default is the included
 +\fBnfs\-linux\-kernel\-callout\fR\&.
 +.RE
 +.PP
 +CTDB_NFS_SKIP_SHARE_CHECK=yes|no
 +.RS 4
 +As part of monitoring, should CTDB skip the check for the existence of each directory exported via NFS\&. This may be desirable if there is a large number of exports\&.
 +.sp
 +Default is no\&.
 +.RE
 +.PP
 +CTDB_RPCINFO_LOCALHOST=\fIIPADDR\fR|\fIHOSTNAME\fR
 +.RS 4
 +IPADDR or HOSTNAME indicates the address that
 +\fBrpcinfo\fR
 +should connect to when doing
 +\fBrpcinfo\fR
 +check on IPv4 RPC service during monitoring\&. Optimally this would be "localhost"\&. However, this can add some performance overheads\&.
 +.sp
 +Default is "127\&.0\&.0\&.1"\&.
 +.RE
 +.PP
 +CTDB_RPCINFO_LOCALHOST6=\fIIPADDR\fR|\fIHOSTNAME\fR
 +.RS 4
 +IPADDR or HOSTNAME indicates the address that
 +\fBrpcinfo\fR
 +should connect to when doing
 +\fBrpcinfo\fR
 +check on IPv6 RPC service during monitoring\&. Optimally this would be "localhost6" (or similar)\&. However, this can add some performance overheads\&.
 +.sp
 +Default is "::1"\&.
 +.RE
 +.SS "APACHE HTTPD"
 +.PP
 +CTDB can manage the Apache web server\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBEventscript\fR
 +.RS 4
 +.RS 4
 +41\&.httpd
 +.RE
 +.RE
 +.PP
 +CTDB_MANAGES_HTTPD=yes|no
 +.RS 4
 +Should CTDB manage the Apache web server?
 +.sp
 +Default is no\&.
 +.RE
 +.SS "CLAMAV"
 +.PP
 +CTDB has support to manage the popular anti\-virus daemon ClamAV\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBEventscript\fR
 +.RS 4
 +.RS 4
 +31\&.clamd
 +.RE
 +.PP
 +This eventscript is not enabled by default\&. Use
 +\fBctdb enablescript\fR
 +to enable it\&.
 +.RE
 +.PP
 +CTDB_MANAGES_CLAMD=yes|no
 +.RS 4
 +Should CTDB manage ClamAV?
 +.sp
 +Default is no\&.
 +.RE
 +.PP
 +CTDB_CLAMD_SOCKET=\fIFILENAME\fR
 +.RS 4
 +FILENAME is the socket to monitor ClamAV\&.
 +.sp
 +No default\&.
 +.RE
 +.SS "ISCSI"
 +.PP
 +CTDB has support for managing the Linux iSCSI tgtd service\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBEventscript\fR
 +.RS 4
 +.RS 4
 +70\&.iscsi
 +.RE
 +.RE
 +.PP
 +CTDB_MANAGES_ISCSI=yes|no
 +.RS 4
 +Should CTDB manage iSCSI tgtd?
 +.sp
 +Default is no\&.
 +.RE
 +.PP
 +CTDB_START_ISCSI_SCRIPTS=\fIDIRECTORY\fR
 +.RS 4
 +DIRECTORY on shared storage containing scripts to start tgtd for each public IP address\&.
 +.sp
 +No default\&.
 +.RE
 +.SS "MULTIPATHD"
 +.PP
 +CTDB can monitor multipath devices to ensure that active paths are available\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBEventscript\fR
 +.RS 4
 +.RS 4
 +20\&.multipathd
 +.RE
 +.PP
 +This eventscript is not enabled by default\&. Use
 +\fBctdb enablescript\fR
 +to enable it\&.
 +.RE
 +.PP
 +CTDB_MONITOR_MPDEVICES=\fIMP\-DEVICE\-LIST\fR
 +.RS 4
 +MP\-DEVICE\-LIST is a list of multipath devices for CTDB to monitor?
 +.sp
 +No default\&.
 +.RE
 +.SS "VSFTPD"
 +.PP
 +CTDB can manage the vsftpd FTP server\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBEventscript\fR
 +.RS 4
 +.RS 4
 +40\&.vsftpd
 +.RE
 +.RE
 +.PP
 +CTDB_MANAGES_VSFTPD=yes|no
 +.RS 4
 +Should CTDB manage the vsftpd FTP server?
 +.sp
 +Default is no\&.
 +.RE
 +.SS "SYSTEM RESOURCE MONITORING CONFIGURATION"
 +.PP
 +CTDB can experience seemingly random (performance and other) issues if system resources become too contrained\&. Options in this section can be enabled to allow certain system resources to be checked\&.
 +.sp
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBEventscripts\fR
 +.RS 4
 +.RS 4
 +00\&.ctdb
 +.RE
 +.RS 4
 +40\&.fs_use
 +.RE
 +.PP
 +Filesystem usage monitoring is in
 +40\&.fs_use\&. This eventscript is not enabled by default\&. Use
 +\fBctdb enablescript\fR
 +to enable it\&.
 +.RE
 +.PP
 +CTDB_CHECK_FS_USE=\fIFS\-LIMIT\-LIST\fR
 +.RS 4
 +FS\-LIMIT\-LIST is a space\-separated list of
 +\fIFILESYSTEM\fR:\fILIMIT\fR
 +pairs indicating that a node should be flagged unhealthy if the space used on FILESYSTEM reaches LIMIT%\&.
 +.sp
 +No default\&.
 +.sp
 +Note that this feature uses the
 +40\&.fs_use
 +eventscript, which is not enabled by default\&. Use
 +\fBctdb enablescript\fR
 +to enable it\&.
 +.RE
 +.PP
 +CTDB_CHECK_SWAP_IS_NOT_USED=yes|no
 +.RS 4
 +Should a warning be logged if swap space is in use\&.
 +.sp
 +Default is no\&.
 +.RE
 +.PP
 +CTDB_MONITOR_FREE_MEMORY=\fINUM\fR
 +.RS 4
 +NUM is a lower limit on available system memory, expressed in megabytes\&. If this is set and the amount of available memory falls below this limit then some debug information will be logged, the node will be disabled and then CTDB will be shut down\&.
 +.sp
 +No default\&.
 +.RE
 +.PP
 +CTDB_MONITOR_FREE_MEMORY_WARN=\fINUM\fR
 +.RS 4
 +NUM is a lower limit on available system memory, expressed in megabytes\&. If this is set and the amount of available memory falls below this limit then a warning will be logged\&.
 +.sp
 +No default\&.
 +.RE
 +.SS "MISCELLANEOUS SERVICE\-RELATED CONFIGURATION"
 +.PP
 +CTDB_MANAGED_SERVICES=\fISERVICE\-LIST\fR
 +.RS 4
 +SERVICE\-LIST is a space\-separated list of SERVICEs that CTDB should manage\&. This can be used as an alternative to the
 +\fICTDB_MANAGES_\fR\fI\fISERVICE\fR\fR
 +variables\&.
 +.sp
 +No default\&.
 +.RE
 +.PP
 +CTDB_SERVICE_AUTOSTARTSTOP=yes|no
 +.RS 4
 +When CTDB should start and stop services if they become managed or unmanaged\&.
 +.sp
 +Default is no\&.
 +.RE
 +.SH "TUNABLES CONFIGURATION"
 +.PP
 +CTDB tunables (see
 +\fBctdbd-tunables\fR(7)) can be set from the configuration file\&. They are set as follows:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +CTDB_SET_\fITUNABLE\fR=\fIVALUE\fR
 +      
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +For example:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +CTDB_SET_MonitorInterval=20
 +      
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.sp
 +.SH "DEBUG AND TEST"
 +.PP
 +Variable in this section are for debugging and testing CTDB\&. They should not generally be needed\&.
 +.PP
 +CTDB_DEBUG_HUNG_SCRIPT=\fIFILENAME\fR
 +.RS 4
 +FILENAME is a script to run to log debug information when an event script times out\&.
 +.sp
 +Default is
 +\fICTDB_BASE\fR/debug\-hung\-script\&.sh\&.
 +.RE
 +.PP
 +CTDB_DEBUG_HUNG_SCRIPT_LOGFILE=\fIFILENAME\fR
 +.RS 4
 +FILENAME specifies where log messages should go when debugging hung eventscripts\&. This is a testing option\&. See also
 +CTDB_DEBUG_HUNG_SCRIPT\&.
 +.sp
 +No default\&. Messages go to stdout/stderr and are logged to the same place as other CTDB log messages\&.
 +.RE
 +.PP
 +CTDB_DEBUG_HUNG_SCRIPT_STACKPAT=\fIREGEXP\fR
 +.RS 4
 +REGEXP specifies interesting processes for which stack traces should be logged when debugging hung eventscripts and those processes are matched in pstree output\&. REGEXP is an extended regexp so choices are separated by pipes (\*(Aq|\*(Aq)\&. However, REGEXP should not contain parentheses\&. See also
 +CTDB_DEBUG_HUNG_SCRIPT\&.
 +.sp
 +Default is "exportfs|rpcinfo"\&.
 +.RE
 +.PP
 +CTDB_DEBUG_LOCKS=\fIFILENAME\fR
 +.RS 4
 +FILENAME is a script to run to log debug information when an CTDB fails to freeze databases during recovery\&.
 +.sp
 +No default, usually
 +\fICTDB_BASE\fR/debug_locks\&.sh\&.
 +.RE
 +.PP
 +CTDB_ETCDIR=\fIDIRECTORY\fR
 +.RS 4
 +DIRECTORY containing system configuration files\&. This is used to provide alternate configuration when testing and should not need to be changed from the default\&.
 +.sp
 +Default is
 +/etc\&.
 +.RE
 +.PP
 +CTDB_INIT_STYLE=debian|redhat|suse
 +.RS 4
 +This is the init style used by the Linux distribution (or other operating system) being used\&. This is usually determined dynamically by checking the system\&. This variable is used by the initscript to determine which init system primitives to use\&. It is also used by some eventscripts to choose the name of initscripts for certain services, since these can vary between distributions\&.
 +.sp
 +No fixed default\&.
 +.sp
 +If this option needs to be changed from the calculated default for the initscript to function properly, then it must be set in the distribution\-specific initscript configuration, such as
 +/etc/sysconfig/ctdb
 +.RE
 +.PP
 +CTDB_MAX_CORRUPT_DB_BACKUPS=\fINUM\fR
 +.RS 4
 +NUM is the maximum number of volatile TDB database backups to be kept (for each database) when a corrupt database is found during startup\&. Volatile TDBs are zeroed during startup so backups are needed to debug any corruption that occurs before a restart\&.
 +.sp
 +Default is 10\&.
 +.RE
 +.PP
 +CTDB_MAX_OPEN_FILES=\fINUM\fR
 +.RS 4
 +NUM is the maximum number of open files\&.
 +.sp
 +There is no default\&.
 +.RE
 +.PP
 +CTDB_RC_LOCAL=\fIFILENAME\fR
 +.RS 4
 +FILENAME is a script fragment to be sourced by the
 +functions
 +that is sourced by scripts\&. On example use would be to override function definitions in unit tests\&. As a sanity check, this file must be executable for it to be used\&.
 +.sp
 +No default\&.
 +.RE
 +.PP
 +CTDB_RUN_TIMEOUT_MONITOR=yes|no
 +.RS 4
 +Whether CTDB should simulate timing out monitor events\&. This uses the
 +99\&.timeout
 +eventscript\&.
 +.sp
 +Default is no\&.
 +.RE
 +.PP
 +CTDB_SCRIPT_DEBUGLEVEL=\fINUM\fR
 +.RS 4
 +NUM is the level debugging messages printed by CTDB scripts\&. Setting this to a higher number (e\&.g\&. 4) will cause some scripts to log more messages\&.
 +.sp
 +Default is 2\&.
 +.RE
 +.PP
 +CTDB_SUPPRESS_COREFILE=yes|no
 +.RS 4
 +Whether CTDB core files should be suppressed\&.
 +.sp
 +Default is no\&.
 +.RE
 +.PP
 +CTDB_VALGRIND=yes|no|\fICOMMAND\fR
 +.RS 4
 +If "yes", this causes
 +\fBctdbd\fR(1)
 +to be run under
 +\fBvalgrind\fR(1)
 +with logs going to
 +/var/log/ctdb_valgrind\&. If neither "yes" nor "no" then the value is assumed to be a COMMAND (e\&.g\&. a
 +\fBvalgrind\fR
 +variation, a
 +\fBgdb\fR(1)
 +command) that is used in place of the default
 +\fBvalgrind\fR
 +command\&. In either case, the
 +\fB\-\-valgrind\fR
 +option is passed to
 +\fBctdbd\fR\&.
 +.sp
 +Default is no\&.
 +.RE
 +.SH "FILES"
 +.RS 4
 +/etc/ctdb/ctdbd\&.conf
 +.RE
 +.RS 4
 +/etc/sysconfig/ctdb
 +.RE
 +.RS 4
 +/etc/default/ctdb
 +.RE
 +.RS 4
 +/etc/ctdb/sysconfig/ctdb
 +.RE
 +.SH "SEE ALSO"
 +.PP
 +\fBctdbd\fR(1),
 +\fBctdbd_wrapper\fR(1),
 +\fBonnode\fR(1),
 +\fBctdb\fR(7),
 +\fBctdb-tunables\fR(7),
 +\m[blue]\fB\%http://ctdb.samba.org/\fR\m[]
 +.SH "AUTHOR"
 +.br
 +.PP
 +This documentation was written by Amitay Isaacs, Martin Schwenke
 +.SH "COPYRIGHT"
 +.br
 +Copyright \(co 2007 Andrew Tridgell, Ronnie Sahlberg
 +.br
 +.PP
 +This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version\&.
 +.PP
 +This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE\&. See the GNU General Public License for more details\&.
 +.PP
 +You should have received a copy of the GNU General Public License along with this program; if not, see
 +\m[blue]\fB\%http://www.gnu.org/licenses\fR\m[]\&.
 +.sp
 +.SH "NOTES"
 +.IP " 1." 4
 +NFS-Ganesha
 +.RS 4
 +\%https://github.com/nfs-ganesha/nfs-ganesha/wiki
 +.RE
diff --cc ctdb/doc/ctdbd.conf.5.html
index 3ba69ac,0000000..7fe0a75
mode 100644,000000..100644
--- a/ctdb/doc/ctdbd.conf.5.html
+++ b/ctdb/doc/ctdbd.conf.5.html
@@@ -1,701 -1,0 +1,701 @@@
- <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 — CTDB daemon configuration file</p></div><div class="refsect1"><a name="idp52417760"></a><h2 [...]
++<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 — CTDB daemon configuration file</p></div><div class="refsect1"><a name="idp51979744"></a><h2 [...]
 +      This file contains CTDB configuration variables that are affect
 +      the operation of CTDB.  The default location of this file is
 +      <code class="filename">/etc/ctdb/ctdbd.conf</code>.
 +    </p><p>
 +      This file is a shell script (see
 +      <span class="citerefentry"><span class="refentrytitle">sh</span>(1)</span>) but is usually limited
 +      to simple variable assignments and shell-style comments.
 +    </p><p>
 +      CTDB configuration variables are grouped into several categories below.
 +    </p><p>
 +      Variables defined in this document can also be set in a
 +      distribution-specific configuration file such as
 +      <code class="filename">/etc/sysconfig/ctdb</code> (Red Hat) or
 +      <code class="filename">/etc/default/ctdb</code> (Debian).  However, these
 +      files should be reserved for variables used by the initscript.
 +      A historical alternative is
 +      <code class="filename">/etc/ctdb/sysconfig/ctdb</code> - this is
 +      deprecated.
-     </p></div><div class="refsect1"><a name="idp50202560"></a><h2>
++    </p></div><div class="refsect1"><a name="idp51478896"></a><h2>
 +      INITSCRIPT CONFIGURATION
 +    </h2><p>
 +      Some options must be available to the initscript so they need to
 +      be set in the distribution-specific initscript configuration,
 +      such as <code class="filename">/etc/sysconfig/ctdb</code> or
 +      <code class="filename">/etc/default/ctdb</code>.
 +    </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">CTDB_PIDFILE=<em class="parameter"><code>FILENAME</code></em></span></dt><dd><p>
 +	    FILENAME is the name of the file used to contain the
 +	    process ID (PID) of the main CTDB daemon when it is
 +	    running.  This is passed from the initscript to
 +	    <span class="citerefentry"><span class="refentrytitle">ctdbd_wrapper</span>(1)</span>.
 +	  </p><p>
 +	    Default is <code class="filename">/var/run/ctdb/ctdbd.pid</code>.
 +	    Corresponds to <code class="option">--pidfile</code>.
- 	  </p></dd></dl></div></div><div class="refsect1"><a name="idp54722304"></a><h2>
++	  </p></dd></dl></div></div><div class="refsect1"><a name="idp49232048"></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><dt><span class="term">CTDB_VARDIR=<em class="parameter"><code>DIRECTORY</code></em></span></dt><dd><p>
 +	    DIRECTORY containing CTDB files that are modified at
 +	    runtime.
 +	  </p><p>
 +	    Defaults to <code class="filename">/var/ctdb</code>, unless
 +	    <code class="filename">/var/lib/ctdb</code> already exists in which
 +	    case it is used.
- 	  </p></dd></dl></div></div><div class="refsect1"><a name="idp54730016"></a><h2>
++	  </p></dd></dl></div></div><div class="refsect1"><a name="idp53889648"></a><h2>
 +      DAEMON CONFIGURATION
 +    </h2><p>
 +      Variables in this section are processed by
 +      <span class="citerefentry"><span class="refentrytitle">ctdbd_wrapper</span>(1)</span> and are converted into
 +      command-line arguments to
 +      <span class="citerefentry"><span class="refentrytitle">ctdbd</span>(1)</span>.  Correspondence with
 +      <span class="citerefentry"><span class="refentrytitle">ctdbd</span>(1)</span> options is shown for
 +      each variable.  The the documentation for the relevant options
 +      for more details.
 +    </p><p>
 +      Many of these variables are also used by event scripts.
 +    </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">CTDB_CAPABILITY_LMASTER=yes|no</span></dt><dd><p>
 +	    Defaults to yes.  Corresponds to <code class="option">--no-lmaster</code>.
 +	  </p></dd><dt><span class="term">CTDB_CAPABILITY_RECMASTER=yes|no</span></dt><dd><p>
 +	    Defaults to yes.  Corresponds to
 +	    <code class="option">--no-recmaster</code>.
 +	  </p></dd><dt><span class="term">CTDB_DBDIR=<em class="parameter"><code>DIRECTORY</code></em></span></dt><dd><p>
 +	    Defaults to <code class="varname">CTDB_VARDIR</code>.  Corresponds to
 +	    <code class="option">--dbdir</code>.
 +	  </p></dd><dt><span class="term">CTDB_DBDIR_PERSISTENT=<em class="parameter"><code>DIRECTORY</code></em></span></dt><dd><p>
 +	    Defaults to <code class="varname">CTDB_VARDIR</code>/persistent.
 +	    Corresponds to <code class="option">--dbdir-persistent</code>.
 +	  </p></dd><dt><span class="term">CTDB_DBDIR_STATE=<em class="parameter"><code>DIRECTORY</code></em></span></dt><dd><p>
 +	    Defaults to <code class="varname">CTDB_VARDIR</code>/state.
 +	    Corresponds to <code class="option">--dbdir-state</code>.
 +	  </p></dd><dt><span class="term">CTDB_DEBUGLEVEL=<em class="parameter"><code>DEBUGLEVEL</code></em></span></dt><dd><p>
 +	    Default is NOTICE (2).  Corresponds to <code class="option">-d</code> or
 +	    <code class="option">--debug</code>.
 +	  </p></dd><dt><span class="term">CTDB_EVENT_SCRIPT_DIR=<em class="parameter"><code>DIRECTORY</code></em></span></dt><dd><p>
 +	    Default is <code class="varname">CTDB_BASE</code>/events.d, so usually
 +	    <code class="filename">/etc/ctdb/events.d</code>.  Corresponds to
 +	    <code class="option">--event-script-dir</code>.
 +	  </p></dd><dt><span class="term">CTDB_LOGGING=<em class="parameter"><code>STRING</code></em></span></dt><dd><p>
 +	    STRING specifies where ctdbd will write its log. The
 +	    default is file:<code class="filename">/var/log/log.ctdb</code> or
 +	    similar - the prefix may differ depending on how CTDB was
 +	    built.  Corresponds to <code class="option">--logging</code>.
 +	  </p><p>
 +	    Valid values are:
 +	  </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">file:<em class="parameter"><code>FILENAME</code></em></span></dt><dd><p>
 +		  FILENAME where ctdbd will write its log. This is usually
 +		  <code class="filename">/var/log/log.ctdb</code>.
 +		</p></dd><dt><span class="term">syslog[<span class="optional">:<em class="parameter"><code>METHOD</code></em></span>]</span></dt><dd><p>
 +		  CTDB will log to syslog.  By default this will use
 +		  the syslog(3) API.
 +                </p><p>
 +		  If METHOD is specified then it specifies an
 +		  extension that causes logging to be done in a
 +		  non-blocking fashion.  This can be useful under
 +		  heavy loads that might cause the syslog daemon to
 +		  dequeue messages too slowly, which would otherwise
 +		  cause CTDB to block when logging.  METHOD must be
 +		  one of:
 +		</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">nonblocking</span></dt><dd><p>
 +			CTDB will log to syslog via
 +			<code class="filename">/dev/log</code> in non-blocking
 +			mode.
 +		      </p></dd><dt><span class="term">udp</span></dt><dd><p>
 +			CTDB will log to syslog via UDP to
 +			localhost:514.  The syslog daemon must be
 +			configured to listen on (at least)
 +			localhost:514.  Most implementations will log
 +			the messages against hostname "localhost" -
 +			this is a limit of the implementation for
 +			compatibility with more syslog daemon
 +			implementations.
 +		      </p></dd><dt><span class="term">udp-rfc5424</span></dt><dd><p>
 +			As with "udp" but messages are sent in RFC5424
 +			format.  This method will log the correct
 +			hostname but is not as widely implemented in
 +			syslog daemons.
 +		      </p></dd></dl></div></dd></dl></div></dd><dt><span class="term">CTDB_LVS_PUBLIC_IP=<em class="parameter"><code>IPADDR</code></em></span></dt><dd><p>
 +	    No default.  Corresponds to "<code class="option">--lvs</code>
 +	    <code class="option">--single-public-ip IPADDR"</code>.
 +	  </p></dd><dt><span class="term">CTDB_NODES=<em class="parameter"><code>FILENAME</code></em></span></dt><dd><p>
 +	    Default is <code class="varname">CTDB_BASE</code>/nodes, so usually
 +	    <code class="filename">/etc/ctdb/nodes</code>.  Corresponds to
 +	    <code class="option">--nlist</code>.
 +	  </p></dd><dt><span class="term">CTDB_NOTIFY_SCRIPT=<em class="parameter"><code>FILENAME</code></em></span></dt><dd><p>
 +	    No default, usually
 +	    <code class="filename">/etc/ctdb/notify.sh</code>.  Corresponds to
 +	    <code class="option">--notification-script</code>.
 +	  </p></dd><dt><span class="term">CTDB_MAX_PERSISTENT_CHECK_ERRORS=<em class="parameter"><code>NUM</code></em></span></dt><dd><p>
 +	    Default 0.  Corresponds to
 +	    <code class="option">--max-persistent-check-errors</code>.
 +	  </p></dd><dt><span class="term">CTDB_NODE_ADDRESS=<em class="parameter"><code>FILENAME</code></em></span></dt><dd><p>
 +	    IPADDR is the private IP address that ctdbd will bind to.
 +	    Corresponds to <code class="option">--listen</code>.
 +	  </p><p>
 +	    By default ctdbd will select the first address from the
 +	    nodes list that in can bind to.  See also
 +	    <em class="citetitle">CTDB_NODES</em>.
 +	  </p><p>
 +	    This option is only required when automatic address
 +	    detection can not be used.  This can be the case when
 +	    running multiple ctdbd daemons/nodes on the same physical
 +	    host (usually for testing), using InfiniBand for the
 +	    private network or on Linux when sysctl
 +	    net.ipv4.ip_nonlocal_bind=1.
 +	  </p></dd><dt><span class="term">CTDB_PUBLIC_ADDRESSES=<em class="parameter"><code>FILENAME</code></em></span></dt><dd><p>
 +	    No default, usually
 +	    <code class="filename">/etc/ctdb/public_addresses</code>.
 +	    Corresponds to <code class="option">--public-addresses</code>.
 +	  </p></dd><dt><span class="term">CTDB_PUBLIC_INTERFACE=<em class="parameter"><code>INTERFACE</code></em></span></dt><dd><p>
 +	    No default.  Corresponds to
 +	    <code class="option">--public-interface</code>.
 +	  </p></dd><dt><span class="term">CTDB_RECOVERY_LOCK=<em class="parameter"><code>FILENAME</code></em></span></dt><dd><p>
 +	    Defaults to
 +	    <code class="filename">/some/place/on/shared/storage</code>, which
 +	    should be change to a useful value.  Corresponds to
 +	    <code class="option">--reclock</code>.
 +	  </p><p>
 +	    For information about the recovery lock please see the
 +	    <em class="citetitle">RECOVERY LOCK</em> section in
 +	    <span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span>.
 +	  </p></dd><dt><span class="term">CTDB_SCRIPT_LOG_LEVEL=<em class="parameter"><code>DEBUGLEVEL</code></em></span></dt><dd><p>
 +	    Defaults to ERR (0).  Corresponds to
 +	    <code class="option">--script-log-level</code>.
 +	  </p></dd><dt><span class="term">CTDB_SOCKET=<em class="parameter"><code>FILENAME</code></em></span></dt><dd><p>
 +	    Defaults to <code class="filename">/tmp/ctdb.socket</code>.
 +	    Corresponds to <code class="option">--socket</code>.
 +	  </p><p>
 +	    If you change this then you probably want to set this in
 +	    root's enviroment (perhaps in a file in
 +	    <code class="filename">/etc/profile.d</code>) so that you can use
 +	    the <span class="citerefentry"><span class="refentrytitle">ctdb</span>(1)</span> command in a
 +	    straightforward manner.
 +	  </p></dd><dt><span class="term">CTDB_START_AS_DISABLED=yes|no</span></dt><dd><p>
 +	    Default is no.  Corresponds to
 +	    <code class="option">--start-as-disabled</code>.
 +	  </p></dd><dt><span class="term">CTDB_START_AS_STOPPED=yes|no</span></dt><dd><p>
 +	    Default is no.  Corresponds to
 +	    <code class="option">--start-as-stopped</code>.
 +	  </p></dd><dt><span class="term">CTDB_TRANSPORT=tcp|infiniband</span></dt><dd><p>
 +	    Defaults to tcp.  Corresponds to
 +	    <code class="option">--transport</code>.
 +	  </p></dd></dl></div><p>
 +      While the following variables do not translate into daemon
 +      options they are used by
 +      <span class="citerefentry"><span class="refentrytitle">ctdbd_wrapper</span>(1)</span> when starting and
 +      stopping <span class="citerefentry"><span class="refentrytitle">ctdbd</span>(1)</span>.
 +    </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">CTDB_SHUTDOWN_TIMEOUT=<em class="parameter"><code>NUM</code></em></span></dt><dd><p>
 +	    NUM is the number of seconds to wait for
 +	    <span class="citerefentry"><span class="refentrytitle">ctdbd</span>(1)</span> to shut down
 +	    gracefully before giving up and killing it.
 +	  </p><p>
 +	    Defaults is 30.
 +	  </p></dd><dt><span class="term">CTDB_STARTUP_TIMEOUT=<em class="parameter"><code>NUM</code></em></span></dt><dd><p>
 +	    NUM is the number of seconds to wait for
 +	    <span class="citerefentry"><span class="refentrytitle">ctdbd</span>(1)</span> complete early
 +	    initialisation up to a point where it is unlikely to
 +	    abort.  If <span class="command"><strong>ctdbd</strong></span> doesn't complete the
 +	    "setup" event before this timeout then it is killed.
 +	  </p><p>
 +	    Defaults is 10.
- 	  </p></dd></dl></div></div><div class="refsect1"><a name="idp55902528"></a><h2>NETWORK CONFIGURATION</h2><div class="refsect2"><a name="idp55903168"></a><h3>NAT GATEWAY</h3><p>
++	  </p></dd></dl></div></div><div class="refsect1"><a name="idp55060688"></a><h2>NETWORK CONFIGURATION</h2><div class="refsect2"><a name="idp55061328"></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
 +	external infrastructure.  One node in a NAT gateway group will
 +	be designated as the NAT gateway master node and other (slave)
 +	nodes will be configured with fallback routes via the NAT
 +	gateway master node.  For more information, see the
 +	<em class="citetitle">NAT GATEWAY</em> section in
 +	<span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span>.
 +      </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">CTDB_NATGW_DEFAULT_GATEWAY=<em class="parameter"><code>IPADDR</code></em></span></dt><dd><p>
 +	      IPADDR is an alternate network gateway to use on the NAT
 +	      gateway master node.  If set, a fallback default route
 +	      is added via this network gateway.
 +	    </p><p>
 +	      No default.  Setting this variable is optional - if not
 +	      set that no route is created on the NAT gateway master
 +	      node.
 +	    </p></dd><dt><span class="term">CTDB_NATGW_NODES=<em class="parameter"><code>FILENAME</code></em></span></dt><dd><p>
 +	      FILENAME contains the list of nodes that belong to the
 +	      same NAT gateway group.
 +	    </p><p>
 +	      File format:
 +	      </p><pre class="screen">
 +<em class="parameter"><code>IPADDR</code></em>
 +	      </pre><p>
 +	    </p><p>
 +	      No default, usually
 +	      <code class="filename">/etc/ctdb/natgw_nodes</code> when enabled.
 +	    </p></dd><dt><span class="term">CTDB_NATGW_PRIVATE_NETWORK=<em class="parameter"><code>IPADDR/MASK</code></em></span></dt><dd><p>
 +	      IPADDR/MASK is the private sub-network that is
 +	      internally routed via the NAT gateway master node.  This
 +	      is usually the private network that is used for node
 +	      addresses.
 +	    </p><p>
 +	      No default.
 +	    </p></dd><dt><span class="term">CTDB_NATGW_PUBLIC_IFACE=<em class="parameter"><code>IFACE</code></em></span></dt><dd><p>
 +	      IFACE is the network interface on which the
 +	      CTDB_NATGW_PUBLIC_IP will be configured.
 +	    </p><p>
 +	      No default.
 +	    </p></dd><dt><span class="term">CTDB_NATGW_PUBLIC_IP=<em class="parameter"><code>IPADDR/MASK</code></em></span></dt><dd><p>
 +	      IPADDR/MASK indicates the IP address that is used for
 +	      outgoing traffic (originating from
 +	      CTDB_NATGW_PRIVATE_NETWORK) on the NAT gateway master
 +	      node.  This <span class="emphasis"><em>must not</em></span> be a
 +	      configured public IP address.
 +	    </p><p>
 +	      No default.
 +	    </p></dd><dt><span class="term">CTDB_NATGW_SLAVE_ONLY=yes|no</span></dt><dd><p>
 +	      When set to "yes" a node can not be a NAT gateway master
 +	      node.  In this case
 +	      <code class="varname">CTDB_NATGW_PUBLIC_IFACE</code> and
 +	      <code class="varname">CTDB_NATGW_PUBLIC_IP</code> are optional
 +	      and unused.
 +	    </p><p>
 +	      Default is no.
 +	    </p></dd><dt><span class="term">CTDB_NATGW_STATIC_ROUTES=<em class="parameter"><code>IPADDR/MASK[@GATEWAY]</code></em> ...</span></dt><dd><p>
 +	      Each IPADDR/MASK identifies a network or host to which
 +	      NATGW should create a fallback route, instead of
 +	      creating a single default route.  This can be used when
 +	      there is already a default route, via an interface that
 +	      can not reach required infrastructure, that overrides
 +	      the NAT gateway default route.
 +	    </p><p>
 +	      If GATEWAY is specified then the corresponding route on
 +	      the NATGW master node will be via GATEWAY.  Such routes
 +	      are created even if
 +	      <code class="varname">CTDB_NATGW_DEFAULT_GATEWAY</code> is not
 +	      specified.  If GATEWAY is not specified for some
 +	      networks then routes are only created on the NATGW
 +	      master node for those networks if
 +	      <code class="varname">CTDB_NATGW_DEFAULT_GATEWAY</code> is
 +	      specified.
 +	    </p><p>
 +	      This should be used with care to avoid causing traffic
 +	      to unnecessarily double-hop through the NAT gateway
 +	      master, even when a node is hosting public IP addresses.
 +	      Each specified network or host should probably have a
 +	      corresponding automatically created link route or static
 +	      route to avoid this.
 +	    </p><p>
 +	      No default.
- 	    </p></dd></dl></div><div class="refsect3"><a name="idp55930016"></a><h4>Example</h4><pre class="screen">
++	    </p></dd></dl></div><div class="refsect3"><a name="idp55088176"></a><h4>Example</h4><pre class="screen">
 +CTDB_NATGW_NODES=/etc/ctdb/natgw_nodes
 +CTDB_NATGW_PRIVATE_NETWORK=192.168.1.0/24
 +CTDB_NATGW_DEFAULT_GATEWAY=10.0.0.1
 +CTDB_NATGW_PUBLIC_IP=10.0.0.227/24
 +CTDB_NATGW_PUBLIC_IFACE=eth0
 +	</pre><p>
 +	  A variation that ensures that infrastructure (ADS, DNS, ...)
 +	  directly attached to the public network (10.0.0.0/24) is
 +	  always reachable would look like this:
 +	</p><pre class="screen">
 +CTDB_NATGW_NODES=/etc/ctdb/natgw_nodes
 +CTDB_NATGW_PRIVATE_NETWORK=192.168.1.0/24
 +CTDB_NATGW_PUBLIC_IP=10.0.0.227/24
 +CTDB_NATGW_PUBLIC_IFACE=eth0
 +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="idp55933904"></a><h3>POLICY ROUTING</h3><p>
++	</p></div></div><div class="refsect2"><a name="idp55092064"></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
 +	possible to route packets from these public addresses via the
 +	system's default route.  Therefore, CTDB has support for
 +	policy routing via the <code class="filename">13.per_ip_routing</code>
 +	eventscript.  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><p>
 +	For more information, see the <em class="citetitle">POLICY
 +	ROUTING</em> section in
 +	<span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span>.
 +      </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">CTDB_PER_IP_ROUTING_CONF=<em class="parameter"><code>FILENAME</code></em></span></dt><dd><p>
 +	      FILENAME contains elements for constructing the desired
 +	      routes for each source address.
 +	    </p><p>
 +	      The special FILENAME value
 +	      <code class="constant">__auto_link_local__</code> indicates that no
 +	      configuration file is provided and that CTDB should
 +	      generate reasonable link-local routes for each public IP
 +	      address.
 +	    </p><p>
 +	      File format:
 +	      </p><pre class="screen">
 +<em class="parameter"><code>IPADDR</code></em> <em class="parameter"><code>DEST-IPADDR/MASK</code></em> [<span class="optional"><em class="parameter"><code>GATEWAY-IPADDR</code></em></span>]
 +	      </pre><p>
 +	    </p><p>
 +	      No default, usually
 +	      <code class="filename">/etc/ctdb/policy_routing</code> when enabled.
 +	    </p></dd><dt><span class="term">CTDB_PER_IP_ROUTING_RULE_PREF=<em class="parameter"><code>NUM</code></em></span></dt><dd><p>
 +	    NUM sets the priority (or preference) for the routing
 +	    rules that are added by CTDB.
 +	  </p><p>
 +	    This should be (strictly) greater than 0 and (strictly)
 +	    less than 32766.  A priority of 100 is recommended, unless
 +	    this conflicts with a priority already in use on the
 +	    system.  See
 +	    <span class="citerefentry"><span class="refentrytitle">ip</span>(8)</span>, for more details.
 +	  </p></dd><dt><span class="term">
 +	    CTDB_PER_IP_ROUTING_TABLE_ID_LOW=<em class="parameter"><code>LOW-NUM</code></em>,
 +	    CTDB_PER_IP_ROUTING_TABLE_ID_HIGH=<em class="parameter"><code>HIGH-NUM</code></em>
 +	  </span></dt><dd><p>
 +	      CTDB determines a unique routing table number to use for
 +	      the routing related to each public address.  LOW-NUM and
 +	      HIGH-NUM indicate the minimum and maximum routing table
 +	      numbers that are used.
 +	    </p><p>
 +	      <span class="citerefentry"><span class="refentrytitle">ip</span>(8)</span> uses some
 +	      reserved routing table numbers below 255.  Therefore,
 +	      CTDB_PER_IP_ROUTING_TABLE_ID_LOW should be (strictly)
 +	      greater than 255.
 +	    </p><p>
 +	      CTDB uses the standard file
 +	      <code class="filename">/etc/iproute2/rt_tables</code> to maintain
 +	      a mapping between the routing table numbers and labels.
 +	      The label for a public address
 +	      <em class="replaceable"><code>ADDR</code></em> will look like
 +	      ctdb.<em class="replaceable"><code>addr</code></em>.  This means that
 +	      the associated rules and routes are easy to read (and
 +	      manipulate).
 +	    </p><p>
 +	      No default, usually 1000 and 9000.
- 	    </p></dd></dl></div><div class="refsect3"><a name="idp55955840"></a><h4>Example</h4><pre class="screen">
++	    </p></dd></dl></div><div class="refsect3"><a name="idp55114000"></a><h4>Example</h4><pre class="screen">
 +CTDB_PER_IP_ROUTING_CONF=/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="idp55957536"></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>
++	</pre></div></div><div class="refsect2"><a name="idp55115696"></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
 +	      that are down then <span class="command"><strong>ctdb status</strong></span> will
 +	      display the node as "PARTIALLYONLINE".
 +	    </p><p>
 +	      Default is "no".
- 	    </p></dd></dl></div></div></div><div class="refsect1"><a name="idp55961680"></a><h2>SERVICE CONFIGURATION</h2><p>
++	    </p></dd></dl></div></div></div><div class="refsect1"><a name="idp55119760"></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>
 +      In the simplest case CTDB will manage a service.  This means the
 +      service will be started and stopped along with CTDB, CTDB will
 +      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="idp55963536"></a><h3>SAMBA</h3><div class="refsect3"><a name="idp55964176"></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="idp55121616"></a><h3>SAMBA</h3><div class="refsect3"><a name="idp55122256"></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.
 +	    </p></dd><dt><span class="term">CTDB_MANAGES_WINBIND=yes|no</span></dt><dd><p>
 +	      Should CTDB manage Winbind?
 +	    </p><p>
 +	      Default is no.
 +	    </p></dd><dt><span class="term">CTDB_SAMBA_CHECK_PORTS=<em class="parameter"><code>PORT-LIST</code></em></span></dt><dd><p>
 +	      When monitoring Samba, check TCP ports in
 +	      space-separated PORT-LIST.
 +	    </p><p>
 +	      Default is to monitor ports that Samba is configured to listen on.
 +	    </p></dd><dt><span class="term">CTDB_SAMBA_SKIP_SHARE_CHECK=yes|no</span></dt><dd><p>
 +	      As part of monitoring, should CTDB skip the check for
 +	      the existence of each directory configured as share in
 +	      Samba.  This may be desirable if there is a large number
 +	      of shares.
 +	    </p><p>
 +	      Default is no.
 +	    </p></dd><dt><span class="term">CTDB_SERVICE_NMB=<em class="parameter"><code>SERVICE</code></em></span></dt><dd><p>
 +	      Distribution specific SERVICE for managing nmbd.
 +	    </p><p>
 +	      Default is distribution-dependant.
 +	    </p></dd><dt><span class="term">CTDB_SERVICE_SMB=<em class="parameter"><code>SERVICE</code></em></span></dt><dd><p>
 +	      Distribution specific SERVICE for managing smbd.
 +	    </p><p>
 +	      Default is distribution-dependant.
 +	    </p></dd><dt><span class="term">CTDB_SERVICE_WINBIND=<em class="parameter"><code>SERVICE</code></em></span></dt><dd><p>
 +	      Distribution specific SERVICE for managing winbindd.
 +	    </p><p>
 +	      Default is "winbind".
- 	    </p></dd></dl></div></div><div class="refsect2"><a name="idp55983680"></a><h3>NFS</h3><p>
++	    </p></dd></dl></div></div><div class="refsect2"><a name="idp55141680"></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="idp55985824"></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_CLUSTER_FILESYSTEM_TYPE=gpfs</span></dt><dd><p>
++      </p><div class="refsect3"><a name="idp55143824"></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_CLUSTER_FILESYSTEM_TYPE=gpfs</span></dt><dd><p>
 +	      The type of cluster filesystem to use with NFS-ganesha.
 +	      Currently only "gpfs" is supported.
 +	    </p><p>
 +	      Default is "gpfs".
 +	    </p></dd><dt><span class="term">CTDB_MANAGES_NFS=yes|no</span></dt><dd><p>
 +	      Should CTDB manage NFS?
 +	    </p><p>
 +	      Default is no.
 +	    </p></dd><dt><span class="term">CTDB_NFS_CALLOUT=<em class="parameter"><code>COMMAND</code></em></span></dt><dd><p>
 +	      COMMAND specifies the path to a callout to handle
 +	      interactions with the configured NFS system, including
 +	      startup, shutdown, monitoring.
 +	    </p><p>
 +	      Default is the included
 +	      <span class="command"><strong>nfs-linux-kernel-callout</strong></span>.
 +	    </p></dd><dt><span class="term">CTDB_NFS_SKIP_SHARE_CHECK=yes|no</span></dt><dd><p>
 +	      As part of monitoring, should CTDB skip the check for
 +	      the existence of each directory exported via NFS.  This
 +	      may be desirable if there is a large number of exports.
 +	    </p><p>
 +	      Default is no.
 +	    </p></dd><dt><span class="term">CTDB_RPCINFO_LOCALHOST=<em class="parameter"><code>IPADDR</code></em>|<em class="parameter"><code>HOSTNAME</code></em></span></dt><dd><p>
 +	      IPADDR or HOSTNAME indicates the address that
 +	      <span class="command"><strong>rpcinfo</strong></span> should connect to when doing
 +	      <span class="command"><strong>rpcinfo</strong></span> check on IPv4 RPC service during
 +	      monitoring.  Optimally this would be "localhost".
 +	      However, this can add some performance overheads.
 +	    </p><p>
 +	      Default is "127.0.0.1".
 +	    </p></dd><dt><span class="term">CTDB_RPCINFO_LOCALHOST6=<em class="parameter"><code>IPADDR</code></em>|<em class="parameter"><code>HOSTNAME</code></em></span></dt><dd><p>
 +	      IPADDR or HOSTNAME indicates the address that
 +	      <span class="command"><strong>rpcinfo</strong></span> should connect to when doing
 +	      <span class="command"><strong>rpcinfo</strong></span> check on IPv6 RPC service
 +	      during monitoring.  Optimally this would be "localhost6"
 +	      (or similar).  However, this can add some performance
 +	      overheads.
 +	    </p><p>
 +	      Default is "::1".
- 	    </p></dd></dl></div></div><div class="refsect2"><a name="idp56006896"></a><h3>APACHE HTTPD</h3><p>
++	    </p></dd></dl></div></div><div class="refsect2"><a name="idp55164896"></a><h3>APACHE HTTPD</h3><p>
 +	CTDB can manage the Apache web server.
-       </p><div class="refsect3"><a name="idp56007920"></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="idp55165920"></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="idp56012496"></a><h3>CLAMAV</h3><p>
++	    </p></dd></dl></div></div><div class="refsect2"><a name="idp55170496"></a><h3>CLAMAV</h3><p>
 +	CTDB has support to manage the popular anti-virus daemon
 +	ClamAV.
-       </p><div class="refsect3"><a name="idp56013616"></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="idp55171616"></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>
 +	      Should CTDB manage ClamAV?
 +	    </p><p>
 +	      Default is no.
 +	    </p></dd><dt><span class="term">CTDB_CLAMD_SOCKET=<em class="parameter"><code>FILENAME</code></em></span></dt><dd><p>
 +	      FILENAME is the socket to monitor ClamAV.
 +	    </p><p>
 +	      No default.
- 	    </p></dd></dl></div></div><div class="refsect2"><a name="idp56021696"></a><h3>ISCSI</h3><p>
++	    </p></dd></dl></div></div><div class="refsect2"><a name="idp55179696"></a><h3>ISCSI</h3><p>
 +	CTDB has support for managing the Linux iSCSI tgtd service.
-       </p><div class="refsect3"><a name="idp56022800"></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="idp55180800"></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.
 +	    </p></dd><dt><span class="term">CTDB_START_ISCSI_SCRIPTS=<em class="parameter"><code>DIRECTORY</code></em></span></dt><dd><p>
 +	      DIRECTORY on shared storage containing scripts to start
 +	      tgtd for each public IP address.
 +	    </p><p>
 +	      No default.
- 	    </p></dd></dl></div></div><div class="refsect2"><a name="idp56029920"></a><h3>MULTIPATHD</h3><p>
++	    </p></dd></dl></div></div><div class="refsect2"><a name="idp55187920"></a><h3>MULTIPATHD</h3><p>
 +	CTDB can monitor multipath devices to ensure that active paths
 +	are available.
-       </p><div class="refsect3"><a name="idp56031040"></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="idp55189040"></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="idp56037296"></a><h3>VSFTPD</h3><p>
++	    </p></dd></dl></div></div><div class="refsect2"><a name="idp55195296"></a><h3>VSFTPD</h3><p>
 +	CTDB can manage the vsftpd FTP server.
-       </p><div class="refsect3"><a name="idp56038320"></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="idp55196320"></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="idp56042896"></a><h3>
++	    </p></dd></dl></div></div><div class="refsect2"><a name="idp55200896"></a><h3>
 +	SYSTEM RESOURCE MONITORING CONFIGURATION
 +      </h3><p>
 +	CTDB can experience seemingly random (performance and other)
 +	issues if system resources become too contrained.  Options in
 +	this section can be enabled to allow certain system resources to
 +	be checked.
-       </p><div class="refsect3"><a name="idp56044144"></a><h4>Eventscripts</h4><table border="0" summary="Simple list" class="simplelist"><tr><td><code class="filename">00.ctdb</code></td></tr><tr><td><code class="filename">40.fs_use</code></td></tr></table><p>
++      </p><div class="refsect3"><a name="idp55202144"></a><h4>Eventscripts</h4><table border="0" summary="Simple list" class="simplelist"><tr><td><code class="filename">00.ctdb</code></td></tr><tr><td><code class="filename">40.fs_use</code></td></tr></table><p>
 +	  Filesystem usage monitoring is in
 +	  <code class="filename">40.fs_use</code>.  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_CHECK_FS_USE=<em class="parameter"><code>FS-LIMIT-LIST</code></em></span></dt><dd><p>
 +	      FS-LIMIT-LIST is a space-separated list of
 +	      <em class="parameter"><code>FILESYSTEM</code></em>:<em class="parameter"><code>LIMIT</code></em>
 +	      pairs indicating that a node should be flagged unhealthy
 +	      if the space used on FILESYSTEM reaches LIMIT%.
 +	    </p><p>
 +	      No default.
 +	    </p><p>
 +	      Note that this feature uses the
 +	      <code class="filename">40.fs_use</code> eventscript, which is not
 +	      enabled by default.  Use <span class="command"><strong>ctdb
 +	      enablescript</strong></span> to enable it.
 +	    </p></dd><dt><span class="term">CTDB_CHECK_SWAP_IS_NOT_USED=yes|no</span></dt><dd><p>
 +	      Should a warning be logged if swap space is in use.
 +	    </p><p>
 +	      Default is no.
 +	    </p></dd><dt><span class="term">CTDB_MONITOR_FREE_MEMORY=<em class="parameter"><code>NUM</code></em></span></dt><dd><p>
 +	      NUM is a lower limit on available system memory, expressed
 +	      in megabytes.  If this is set and the amount of available
 +	      memory falls below this limit then some debug information
 +	      will be logged, the node will be disabled and then CTDB
 +	      will be shut down.
 +	    </p><p>
 +	      No default.
 +	    </p></dd><dt><span class="term">CTDB_MONITOR_FREE_MEMORY_WARN=<em class="parameter"><code>NUM</code></em></span></dt><dd><p>
 +	      NUM is a lower limit on available system memory, expressed
 +	      in megabytes.  If this is set and the amount of available
 +	      memory falls below this limit then a warning will be
 +	      logged.
 +	    </p><p>
 +	      No default.
- 	    </p></dd></dl></div></div><div class="refsect2"><a name="idp56062144"></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="idp55220144"></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
 +	      <code class="varname">CTDB_MANAGES_<em class="replaceable"><code>SERVICE</code></em></code>
 +	      variables.
 +	    </p><p>
 +	      No default.
 +	    </p></dd><dt><span class="term">CTDB_SERVICE_AUTOSTARTSTOP=yes|no</span></dt><dd><p>
 +	      When CTDB should start and stop services if they become
 +	      managed or unmanaged.
 +	    </p><p>
 +	      Default is no.
- 	    </p></dd></dl></div></div></div><div class="refsect1"><a name="idp56068672"></a><h2>
++	    </p></dd></dl></div></div></div><div class="refsect1"><a name="idp55226672"></a><h2>
 +      TUNABLES CONFIGURATION
 +    </h2><p>
 +      CTDB tunables (see
 +      <span class="citerefentry"><span class="refentrytitle">ctdbd-tunables</span>(7)</span>) can be set from the
 +      configuration file.  They are set as follows:
 +
 +      </p><div class="literallayout"><p><br>
 +CTDB_SET_<em class="replaceable"><code>TUNABLE</code></em>=<em class="replaceable"><code>VALUE</code></em><br>
 +������</p></div><p>
 +    </p><p>
 +      For example:
 +
 +      </p><pre class="screen">
 +CTDB_SET_MonitorInterval=20
 +      </pre><p>
-     </p></div><div class="refsect1"><a name="idp56073456"></a><h2>
++    </p></div><div class="refsect1"><a name="idp55231456"></a><h2>
 +      DEBUG AND TEST
 +    </h2><p>
 +      Variable in this section are for debugging and testing CTDB.
 +      They should not generally be needed.
 +    </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">CTDB_DEBUG_HUNG_SCRIPT=<em class="parameter"><code>FILENAME</code></em></span></dt><dd><p>
 +	    FILENAME is a script to run to log debug information when
 +	    an event script times out.
 +	  </p><p>
 +	    Default is <code class="filename"><code class="varname">CTDB_BASE</code>/debug-hung-script.sh</code>.
 +	  </p></dd><dt><span class="term">CTDB_DEBUG_HUNG_SCRIPT_LOGFILE=<em class="parameter"><code>FILENAME</code></em></span></dt><dd><p>
 +	    FILENAME specifies where log messages should go when
 +	    debugging hung eventscripts.  This is a testing option.
 +	    See also <em class="citetitle">CTDB_DEBUG_HUNG_SCRIPT</em>.
 +	  </p><p>
 +	    No default.  Messages go to stdout/stderr and are logged
 +	    to the same place as other CTDB log messages.
 +	  </p></dd><dt><span class="term">CTDB_DEBUG_HUNG_SCRIPT_STACKPAT=<em class="parameter"><code>REGEXP</code></em></span></dt><dd><p>
 +	    REGEXP specifies interesting processes for which stack
 +	    traces should be logged when debugging hung eventscripts
 +	    and those processes are matched in pstree output.  REGEXP
 +	    is an extended regexp so choices are separated by pipes
 +	    ('|').  However, REGEXP should not contain parentheses.
 +	    See also <em class="citetitle">CTDB_DEBUG_HUNG_SCRIPT</em>.
 +	  </p><p>
 +	    Default is "exportfs|rpcinfo".
 +	  </p></dd><dt><span class="term">CTDB_DEBUG_LOCKS=<em class="parameter"><code>FILENAME</code></em></span></dt><dd><p>
 +	    FILENAME is a script to run to log debug information when
 +	    an CTDB fails to freeze databases during recovery.
 +	  </p><p>
 +	    No default, usually
 +	    <code class="filename"><code class="varname">CTDB_BASE</code>/debug_locks.sh</code>.
 +	  </p></dd><dt><span class="term">CTDB_ETCDIR=<em class="parameter"><code>DIRECTORY</code></em></span></dt><dd><p>
 +	    DIRECTORY containing system configuration files.  This is
 +	    used to provide alternate configuration when testing and
 +	    should not need to be changed from the default.
 +	  </p><p>
 +	    Default is <code class="filename">/etc</code>.
 +	  </p></dd><dt><span class="term">CTDB_INIT_STYLE=debian|redhat|suse</span></dt><dd><p>
 +	    This is the init style used by the Linux distribution (or
 +	    other operating system) being used.  This is usually
 +	    determined dynamically by checking the system.  This
 +	    variable is used by the initscript to determine which init
 +	    system primitives to use.  It is also used by some
 +	    eventscripts to choose the name of initscripts for certain
 +	    services, since these can vary between distributions.
 +	  </p><p>
 +	    No fixed default.
 +	  </p><p>
 +	    If this option needs to be changed from the calculated
 +	    default for the initscript to function properly, then it
 +	    must be set in the distribution-specific initscript
 +	    configuration, such as
 +	    <code class="filename">/etc/sysconfig/ctdb</code>
 +	  </p></dd><dt><span class="term">CTDB_MAX_CORRUPT_DB_BACKUPS=<em class="parameter"><code>NUM</code></em></span></dt><dd><p>
 +	    NUM is the maximum number of volatile TDB database backups
 +	    to be kept (for each database) when a corrupt database is
 +	    found during startup.  Volatile TDBs are zeroed during
 +	    startup so backups are needed to debug any corruption that
 +	    occurs before a restart.
 +	  </p><p>
 +	    Default is 10.
 +	  </p></dd><dt><span class="term">CTDB_MAX_OPEN_FILES=<em class="parameter"><code>NUM</code></em></span></dt><dd><p>
 +	    NUM is the maximum number of open files.
 +	  </p><p>
 +	    There is no default.
 +	  </p></dd><dt><span class="term">CTDB_RC_LOCAL=<em class="parameter"><code>FILENAME</code></em></span></dt><dd><p>
 +	    FILENAME is a script fragment to be sourced by the
 +	    <code class="filename">functions</code> that is sourced by scripts.
 +	    On example use would be to override function definitions
 +	    in unit tests.  As a sanity check, this file must be
 +	    executable for it to be used.
 +	  </p><p>
 +	    No default.
 +	  </p></dd><dt><span class="term">CTDB_RUN_TIMEOUT_MONITOR=yes|no</span></dt><dd><p>
 +	    Whether CTDB should simulate timing out monitor events.
 +	    This uses the <code class="filename">99.timeout</code> eventscript.
 +	  </p><p>
 +	    Default is no.
 +	  </p></dd><dt><span class="term">CTDB_SCRIPT_DEBUGLEVEL=<em class="parameter"><code>NUM</code></em></span></dt><dd><p>
 +	    NUM is the level debugging messages printed by CTDB
 +	    scripts.  Setting this to a higher number (e.g. 4) will
 +	    cause some scripts to log more messages.
 +	  </p><p>
 +	    Default is 2.
 +	  </p></dd><dt><span class="term">CTDB_SUPPRESS_COREFILE=yes|no</span></dt><dd><p>
 +	    Whether CTDB core files should be suppressed.
 +	  </p><p>
 +	    Default is no.
 +	  </p></dd><dt><span class="term">CTDB_VALGRIND=yes|no|<em class="parameter"><code>COMMAND</code></em></span></dt><dd><p>
 +	    If "yes", this causes
 +	    <span class="citerefentry"><span class="refentrytitle">ctdbd</span>(1)</span> to be run under
 +	    <span class="citerefentry"><span class="refentrytitle">valgrind</span>(1)</span> with logs going to
 +	    <code class="filename">/var/log/ctdb_valgrind</code>.  If neither
 +	    "yes" nor "no" then the value is assumed to be a COMMAND
 +	    (e.g. a <span class="command"><strong>valgrind</strong></span> variation, a
 +	    <span class="citerefentry"><span class="refentrytitle">gdb</span>(1)</span> command) that is
 +	    used in place of the default <span class="command"><strong>valgrind</strong></span>
 +	    command.  In either case, the <code class="option">--valgrind</code>
 +	    option is passed to <span class="command"><strong>ctdbd</strong></span>.
 +	  </p><p>
 +	    Default is no.
- 	  </p></dd></dl></div></div><div class="refsect1"><a name="idp56118736"></a><h2>FILES</h2><table border="0" summary="Simple list" class="simplelist"><tr><td><code class="filename">/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">/etc/ctdb/sysconfig/ctdb</code></td></tr></table></div><div class="refsect1"><a name="idp56123136"></a><h2>SEE [...]
++	  </p></dd></dl></div></div><div class="refsect1"><a name="idp55276736"></a><h2>FILES</h2><table border="0" summary="Simple list" class="simplelist"><tr><td><code class="filename">/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">/etc/ctdb/sysconfig/ctdb</code></td></tr></table></div><div class="refsect1"><a name="idp55281136"></a><h2>SEE [...]
 +      <span class="citerefentry"><span class="refentrytitle">ctdbd</span>(1)</span>,
 +
 +      <span class="citerefentry"><span class="refentrytitle">ctdbd_wrapper</span>(1)</span>,
 +
 +      <span class="citerefentry"><span class="refentrytitle">onnode</span>(1)</span>,
 +
 +      <span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span>,
 +
 +      <span class="citerefentry"><span class="refentrytitle">ctdb-tunables</span>(7)</span>,
 +
 +      <a class="ulink" href="http://ctdb.samba.org/" target="_top">http://ctdb.samba.org/</a>
 +    </p></div></div></body></html>
diff --cc ctdb/doc/ctdbd_wrapper.1
index bd56ff6,0000000..f3670c3
mode 100644,000000..100644
--- a/ctdb/doc/ctdbd_wrapper.1
+++ b/ctdb/doc/ctdbd_wrapper.1
@@@ -1,69 -1,0 +1,69 @@@
 +'\" t
 +.\"     Title: ctdbd_wrapper
 +.\"    Author: 
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 09/08/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: CTDB - clustered TDB database
 +.\"    Source: ctdb
 +.\"  Language: English
 +.\"
- .TH "CTDBD_WRAPPER" "1" "09/08/2015" "ctdb" "CTDB \- clustered TDB database"
++.TH "CTDBD_WRAPPER" "1" "12/10/2015" "ctdb" "CTDB \- clustered TDB database"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +ctdbd_wrapper \- Wrapper for ctdbd
 +.SH "SYNOPSIS"
 +.HP \w'\fBctdbd_wrapper\fR\ 'u
 +\fBctdbd_wrapper\fR {\fIPIDFILE\fR} {start | stop}
 +.SH "DESCRIPTION"
 +.PP
 +ctdbd_wrapper is used to start or stop the main CTDB daemon\&.
 +.PP
 +\fIPIDFILE\fR
 +specifies the location of the file containing the PID of the main CTDB daemon\&.
 +.PP
 +ctdbd_wrapper constructs command\-line options for ctdbd from configuration variables specified in
 +\fBctdbd.conf\fR(5)\&.
 +.PP
 +See
 +\fBctdb\fR(7)
 +for an overview of CTDB\&.
 +.SH "SEE ALSO"
 +.PP
 +\fBctdbd\fR(1),
 +\fBctdbd.conf\fR(5),
 +\fBctdb\fR(7),
 +\m[blue]\fB\%http://ctdb.samba.org/\fR\m[]
 +.SH "AUTHOR"
 +.br
 +.PP
 +This documentation was written by Amitay Isaacs, Martin Schwenke
 +.SH "COPYRIGHT"
 +.br
 +Copyright \(co 2007 Andrew Tridgell, Ronnie Sahlberg
 +.br
 +.PP
 +This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version\&.
 +.PP
 +This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE\&. See the GNU General Public License for more details\&.
 +.PP
 +You should have received a copy of the GNU General Public License along with this program; if not, see
 +\m[blue]\fB\%http://www.gnu.org/licenses\fR\m[]\&.
 +.sp
diff --cc ctdb/doc/ctdbd_wrapper.1.html
index e0f0522,0000000..a1b6613
mode 100644,000000..100644
--- a/ctdb/doc/ctdbd_wrapper.1.html
+++ b/ctdb/doc/ctdbd_wrapper.1.html
@@@ -1,20 -1,0 +1,20 @@@
- <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 — Wrapper for ctdbd</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class [...]
++<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 — Wrapper for ctdbd</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class [...]
 +      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
 +      file containing the PID of the main CTDB daemon.
 +    </p><p>
 +      ctdbd_wrapper constructs command-line options for ctdbd from
 +      configuration variables specified in
 +      <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="idp53610160"></a><h2>SEE ALSO</h2><p>
++    </p></div><div class="refsect1"><a name="idp53317216"></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>,
 +
 +      <span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span>,
 +
 +      <a class="ulink" href="http://ctdb.samba.org/" target="_top">http://ctdb.samba.org/</a>
 +    </p></div></div></body></html>
diff --cc ctdb/doc/ltdbtool.1
index dcff719,0000000..c408672
mode 100644,000000..100644
--- a/ctdb/doc/ltdbtool.1
+++ b/ctdb/doc/ltdbtool.1
@@@ -1,256 -1,0 +1,256 @@@
 +'\" t
 +.\"     Title: ltdbtool
 +.\"    Author: 
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 09/08/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: CTDB - clustered TDB database
 +.\"    Source: ctdb
 +.\"  Language: English
 +.\"
- .TH "LTDBTOOL" "1" "09/08/2015" "ctdb" "CTDB \- clustered TDB database"
++.TH "LTDBTOOL" "1" "12/10/2015" "ctdb" "CTDB \- clustered TDB database"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +ltdbtool \- manipulate CTDB\*(Aqs local TDB files
 +.SH "SYNOPSIS"
 +.HP \w'\fBltdbtool\fR\ 'u
 +\fBltdbtool\fR [\fIOPTION\fR...] {\fICOMMAND\fR} [\fICOMMAND\-ARGS\fR]
 +.SH "DESCRIPTION"
 +.PP
 +ltdbtool is a utility to manipulate CTDB\*(Aqs local TDB databases (LTDBs) without connecting to a CTDB daemon\&.
 +.PP
 +It can be used to:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +dump the contents of a LTDB, optionally printing the CTDB record header information,
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +convert between an LTDB and a non\-clustered tdb by adding or removing CTDB headers and
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +convert between 64 and 32 bit LTDBs where the CTDB record headers differ by 4 bytes of padding\&.
 +.RE
 +.SH "OPTIONS"
 +.PP
 +\-e
 +.RS 4
 +Dump empty records\&. These are normally excluded\&.
 +.RE
 +.PP
 +\-p
 +.RS 4
 +Dump with header information, similar to "ctdb catdb"\&.
 +.RE
 +.PP
 +\-s {0 | 32 | 64}
 +.RS 4
 +Specify how to determine the CTDB record header size for the input database:
 +.PP
 +0
 +.RS 4
 +no CTDB header
 +.RE
 +.PP
 +32
 +.RS 4
 +CTDB header size of a 32 bit system (20 bytes)
 +.RE
 +.PP
 +64
 +.RS 4
 +CTDB header size of a 64 bit system (24 bytes)
 +.RE
 +.sp
 +The default is 32 or 64 depending on the system architecture\&.
 +.RE
 +.PP
 +\-o {0 | 32 | 64}
 +.RS 4
 +Specify how to determine the CTDB record header size for the output database, see \-s\&.
 +.RE
 +.PP
 +\-S \fISIZE\fR
 +.RS 4
 +Explicitly specify the CTDB record header SIZE of the input database in bytes\&.
 +.RE
 +.PP
 +\-O \fISIZE\fR
 +.RS 4
 +Explicitly specify the CTDB record header SIZE for the output database in bytes\&.
 +.RE
 +.PP
 +\-h
 +.RS 4
 +Print help text\&.
 +.RE
 +.SH "COMMANDS"
 +.PP
 +help
 +.RS 4
 +Print help text\&.
 +.RE
 +.PP
 +dump \fIIDB\fR
 +.RS 4
 +Dump the contents of an LTDB input file IDB to standard output in a human\-readable format\&.
 +.RE
 +.PP
 +convert \fIIDB\fR \fIODB\fR
 +.RS 4
 +Copy an LTDB input file IDB to output file ODB, optionally adding or removing CTDB headers\&.
 +.RE
 +.SH "EXAMPLES"
 +.PP
 +Print a local tdb in "tdbdump" style:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +      ltdbtool dump idmap2\&.tdb\&.0
 +    
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +Print a local tdb with header information similar to "ctdb catdb":
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +      ltdbtool dump \-p idmap2\&.tdb\&.0
 +    
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +Strip the CTDB headers from records:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +      ltdbtool convert \-o0 idmap2\&.tdb\&.0 idmap\&.tdb
 +    
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +Strip 64 bit CTDB headers from records, running on i386:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +      ltdbtool convert \-s64 \-o0 idmap2\&.tdb\&.0 idmap\&.tdb
 +    
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +Strip the CTDB headers from records by piping through tdbrestore:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +      ltdbtool dump idmap2\&.tdb\&.0 | tdbrestore idmap\&.tdb
 +    
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +Convert a local tdb from a 64 bit system for usage on a 32 bit system:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +      ltdbtool convert \-s64 \-o32 idmap2\&.tdb\&.0 idmap2\&.tdb\&.1
 +    
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +Add a default header:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +      ltdbtool convert \-s0 idmap\&.tdb idmap2\&.tdb\&.0
 +    
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.SH "SEE ALSO"
 +.PP
 +\fBctdb\fR(1),
 +\fBtdbdump\fR(1),
 +\fBtdbrestore\fR(1),
 +\fBctdb\fR(7),
 +\m[blue]\fB\%http://ctdb.samba.org/\fR\m[]
 +.SH "AUTHOR"
 +.br
 +.PP
 +This documentation was written by Gregor Beck
 +.SH "COPYRIGHT"
 +.br
 +Copyright \(co 2011 Gregor Beck, Michael Adam
 +.br
 +.PP
 +This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version\&.
 +.PP
 +This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE\&. See the GNU General Public License for more details\&.
 +.PP
 +You should have received a copy of the GNU General Public License along with this program; if not, see
 +\m[blue]\fB\%http://www.gnu.org/licenses\fR\m[]\&.
 +.sp
diff --cc ctdb/doc/ltdbtool.1.html
index 62d7b7f,0000000..391df38
mode 100644,000000..100644
--- a/ctdb/doc/ltdbtool.1.html
+++ b/ctdb/doc/ltdbtool.1.html
@@@ -1,88 -1,0 +1,88 @@@
- <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ltdbtool</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="ltdbtool.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ltdbtool — manipulate CTDB's local TDB files</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div clas [...]
++<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ltdbtool</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="ltdbtool.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ltdbtool — manipulate CTDB's local TDB files</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div clas [...]
 +      ltdbtool is a utility to manipulate CTDB's local TDB databases
 +      (LTDBs) without connecting to a CTDB daemon.
 +    </p><p>
 +      It can be used to:
 +    </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
 +	  dump the contents of a LTDB, optionally printing the CTDB
 +	    record header information,
 +	</p></li><li class="listitem"><p>
 +	  convert between an LTDB and a non-clustered tdb
 +	  by adding or removing CTDB headers and
 +	</p></li><li class="listitem"><p>convert between 64 and 32 bit LTDBs where the CTDB record
 +	  headers differ by 4 bytes of padding.
- 	  </p></li></ul></div></div><div class="refsect1"><a name="idp49287984"></a><h2>OPTIONS</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term">-e</span></dt><dd><p>
++	  </p></li></ul></div></div><div class="refsect1"><a name="idp52723440"></a><h2>OPTIONS</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term">-e</span></dt><dd><p>
 +	    Dump empty records.  These are normally excluded.
 +	  </p></dd><dt><span class="term">-p</span></dt><dd><p>
 +	    Dump with header information, similar to "ctdb catdb".
 +	  </p></dd><dt><span class="term">
 +	  -s
 +	  { 0  |   32  |   64 }
 +	</span></dt><dd><p>
 +	    Specify how to determine the CTDB record header size
 +	    for the input database:
 +	    </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">0</span></dt><dd><p>no CTDB header</p></dd><dt><span class="term">32</span></dt><dd><p>CTDB header size of a 32 bit system (20 bytes)</p></dd><dt><span class="term">64</span></dt><dd><p>CTDB header size of a 64 bit system (24 bytes)</p></dd></dl></div><p>
 +	    The default is 32 or 64 depending on the system architecture.
 +	  </p></dd><dt><span class="term">
 +	  -o
 +	  { 0  |   32  |   64 }
 +	</span></dt><dd><p>
 +	    Specify how to determine the CTDB record header size
 +	    for the output database, see -s.
 +	  </p></dd><dt><span class="term">-S <em class="parameter"><code>SIZE</code></em></span></dt><dd><p>
 +	    Explicitly specify the CTDB record header SIZE of the
 +	    input database in bytes.
 +	  </p></dd><dt><span class="term">-O <em class="parameter"><code>SIZE</code></em></span></dt><dd><p>
 +	    Explicitly specify the CTDB record header SIZE for the
 +	    output database in bytes.
 +	  </p></dd><dt><span class="term">-h</span></dt><dd><p>
 +            Print help text.
- 	  </p></dd></dl></div></div><div class="refsect1"><a name="idp49125440"></a><h2>COMMANDS</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term">help</span></dt><dd><p>
++	  </p></dd></dl></div></div><div class="refsect1"><a name="idp52226512"></a><h2>COMMANDS</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term">help</span></dt><dd><p>
 +	    Print help text.
 +	  </p></dd><dt><span class="term">dump <em class="parameter"><code>IDB</code></em></span></dt><dd><p>
 +	    Dump the contents of an LTDB input file IDB to standard
 +	    output in a human-readable format.
 +	  </p></dd><dt><span class="term">
 +	  convert <em class="parameter"><code>IDB</code></em> <em class="parameter"><code>ODB</code></em>
 +	</span></dt><dd><p>
 +	    Copy an LTDB input file IDB to output file ODB, optionally
 +	    adding or removing CTDB headers.
- 	  </p></dd></dl></div></div><div class="refsect1"><a name="idp49138064"></a><h2>EXAMPLES</h2><p>
++	  </p></dd></dl></div></div><div class="refsect1"><a name="idp52657920"></a><h2>EXAMPLES</h2><p>
 +      Print a local tdb in "tdbdump" style:
 +    </p><pre class="screen">
 +      ltdbtool dump idmap2.tdb.0
 +    </pre><p>
 +      Print a local tdb with header information similar to "ctdb catdb":
 +    </p><pre class="screen">
 +      ltdbtool dump -p idmap2.tdb.0
 +    </pre><p>
 +      Strip the CTDB headers from records:
 +    </p><pre class="screen">
 +      ltdbtool convert -o0 idmap2.tdb.0 idmap.tdb
 +    </pre><p>
 +      Strip 64 bit CTDB headers from records, running on i386:
 +    </p><pre class="screen">
 +      ltdbtool convert -s64 -o0 idmap2.tdb.0 idmap.tdb
 +    </pre><p>
 +      Strip the CTDB headers from records by piping through tdbrestore:
 +    </p><pre class="screen">
 +      ltdbtool dump idmap2.tdb.0 | tdbrestore idmap.tdb
 +    </pre><p>
 +      Convert a local tdb from a 64 bit system for usage on a 32 bit system:
 +    </p><pre class="screen">
 +      ltdbtool convert -s64 -o32 idmap2.tdb.0 idmap2.tdb.1
 +    </pre><p>
 +      Add a default header:
 +    </p><pre class="screen">
 +      ltdbtool convert -s0 idmap.tdb idmap2.tdb.0
-     </pre></div><div class="refsect1"><a name="idp49146320"></a><h2>SEE ALSO</h2><p>
++    </pre></div><div class="refsect1"><a name="idp54544544"></a><h2>SEE ALSO</h2><p>
 +      <span class="citerefentry"><span class="refentrytitle">ctdb</span>(1)</span>,
 +
 +      <span class="citerefentry"><span class="refentrytitle">tdbdump</span>(1)</span>,
 +
 +      <span class="citerefentry"><span class="refentrytitle">tdbrestore</span>(1)</span>,
 +
 +      <span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span>,
 +
 +      <a class="ulink" href="http://ctdb.samba.org/" target="_top">http://ctdb.samba.org/</a>
 +    </p></div></div></body></html>
diff --cc ctdb/doc/onnode.1
index 67ddfcc,0000000..5076710
mode 100644,000000..100644
--- a/ctdb/doc/onnode.1
+++ b/ctdb/doc/onnode.1
@@@ -1,254 -1,0 +1,254 @@@
 +'\" t
 +.\"     Title: onnode
 +.\"    Author: 
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 09/08/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: CTDB - clustered TDB database
 +.\"    Source: ctdb
 +.\"  Language: English
 +.\"
- .TH "ONNODE" "1" "09/08/2015" "ctdb" "CTDB \- clustered TDB database"
++.TH "ONNODE" "1" "12/10/2015" "ctdb" "CTDB \- clustered TDB database"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +onnode \- run commands on CTDB cluster nodes
 +.SH "SYNOPSIS"
 +.HP \w'\fBonnode\fR\ 'u
 +\fBonnode\fR [\fIOPTION\fR...] {\fINODES\fR} {\fICOMMAND\fR}
 +.SH "DESCRIPTION"
 +.PP
 +onnode is a utility to run commands on a specific node of a CTDB cluster, or on all nodes\&.
 +.PP
 +\fINODES\fR
 +specifies which node(s) to run a command on\&. See section
 +NODES SPECIFICATION
 +for details\&.
 +.PP
 +\fICOMMAND\fR
 +can be any shell command\&. The onnode utility uses ssh or rsh to connect to the remote nodes and run the command\&.
 +.SH "OPTIONS"
 +.PP
 +\-c
 +.RS 4
 +Execute COMMAND in the current working directory on the specified nodes\&.
 +.RE
 +.PP
 +\-f \fIFILENAME\fR
 +.RS 4
 +Specify an alternative nodes FILENAME to use instead of the default\&. This option overrides the CTDB_NODES_FILE environment variable\&. See the discussion of
 +/etc/ctdb/nodes
 +in the FILES section for more details\&.
 +.RE
 +.PP
 +\-i
 +.RS 4
 +Keep standard input open, allowing data to be piped to onnode\&. Normally onnode closes stdin to avoid surprises when scripting\&. Note that this option is ignored when using
 +\fB\-p\fR
 +or if
 +\fBSSH\fR
 +is set to anything other than "ssh"\&.
 +.RE
 +.PP
 +\-n
 +.RS 4
 +Allow nodes to be specified by name rather than node numbers\&. These nodes don\*(Aqt need to be listed in the nodes file\&. You can avoid the nodes file entirely by combining this with
 +\-f /dev/null\&.
 +.RE
 +.PP
 +\-o \fIPREFIX\fR
 +.RS 4
 +Causes standard output from each node to be saved into a file with name PREFIX\&.\fIIP\fR\&.
 +.RE
 +.PP
 +\-p
 +.RS 4
 +Run COMMAND in parallel on the specified nodes\&. The default is to run COMMAND sequentially on each node\&.
 +.RE
 +.PP
 +\-P
 +.RS 4
 +Push files to nodes\&. Names of files to push are specified rather than the usual command\&. Quoting is fragile/broken \- filenames with whitespace in them are not supported\&.
 +.RE
 +.PP
 +\-q
 +.RS 4
 +Do not print node addresses\&. Normally, onnode prints informational node addresses if more than one node is specified\&. This overrides \-v\&.
 +.RE
 +.PP
 +\-v
 +.RS 4
 +Print node addresses even if only one node is specified\&. Normally, onnode prints informational node addresses when more than one node is specified\&.
 +.RE
 +.PP
 +\-h, \-\-help
 +.RS 4
 +Show a short usage guide\&.
 +.RE
 +.SH "NODES SPECIFICATION"
 +.PP
 +Nodes can be specified via numeric node numbers (from 0 to N\-1) or mnemonics\&. Multiple nodes are specified using lists of nodes, separated by commas, and ranges of numeric node numbers, separated by dashes\&. If nodes are specified multiple times then the command will be executed multiple times on those nodes\&. The order of nodes is significant\&.
 +.PP
 +The following mnemonics are available:
 +.PP
 +all
 +.RS 4
 +All nodes\&.
 +.RE
 +.PP
 +any
 +.RS 4
 +A node where ctdbd is running\&. This semi\-random but there is a bias towards choosing a low numbered node\&.
 +.RE
 +.PP
 +ok | healthy
 +.RS 4
 +All nodes that are not disconnected, banned, disabled or unhealthy\&.
 +.RE
 +.PP
 +con | connected
 +.RS 4
 +All nodes that are not disconnected\&.
 +.RE
 +.PP
 +lvs | lvsmaster
 +.RS 4
 +The current LVS master\&.
 +.RE
 +.PP
 +natgw | natgwlist
 +.RS 4
 +The current NAT gateway\&.
 +.RE
 +.PP
 +rm | recmaster
 +.RS 4
 +The current recovery master\&.
 +.RE
 +.SH "EXAMPLES"
 +.PP
 +The following command would show the process ID of ctdbd on all nodes
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +      onnode all ctdb getpid
 +    
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +The following command would show the last 5 lines of log on each node, preceded by the node\*(Aqs hostname
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +      onnode all "hostname; tail \-5 /var/log/log\&.ctdb"
 +    
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +The following command would restart the ctdb service on all nodes, in parallel\&.
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +      onnode \-p all service ctdb restart
 +    
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +The following command would run \&./foo in the current working directory, in parallel, on nodes 0, 2, 3 and 4\&.
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +      onnode \-c \-p 0,2\-4 \&./foo
 +    
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.SH "ENVIRONMENT"
 +.PP
 +\fBCTDB_BASE\fR
 +.RS 4
 +Directory containing CTDB configuration files\&. The default is
 +/etc/ctdb\&.
 +.RE
 +.PP
 +\fBCTDB_NODES_FILE\fR
 +.RS 4
 +Name of alternative nodes file to use instead of the default\&. See the
 +FILES
 +section for more details\&.
 +.RE
 +.SH "FILES"
 +.PP
 +/etc/ctdb/nodes
 +.RS 4
 +Default file containing a list of each node\*(Aqs IP address or hostname\&.
 +.sp
 +Actually, the default is
 +$CTDB_BASE/nodes, where
 +\fBCTDB_BASE\fR
 +defaults to
 +/etc/ctdb\&. If a relative path is given (via the \-f option or
 +\fBCTDB_BASE\fR) and no corresponding file exists relative to the current directory then the file is also searched for in the
 +$CTDB_BASE
 +directory\&.
 +.RE
 +.PP
 +/etc/ctdb/onnode\&.conf
 +.RS 4
 +If this file exists it is sourced by onnode\&. The main purpose is to allow the administrator to set
 +\fBSSH\fR
 +to something other than "ssh"\&. In this case the \-t option is ignored\&. For example, the administrator may choose to use use rsh instead of ssh\&.
 +.RE
 +.SH "SEE ALSO"
 +.PP
 +\fBctdb\fR(7),
 +\m[blue]\fB\%http://ctdb.samba.org/\fR\m[]
 +.SH "AUTHOR"
 +.br
 +.PP
 +This documentation was written by Andrew Tridgell, Martin Schwenke
 +.SH "COPYRIGHT"
 +.br
 +Copyright \(co 2007 Andrew Tridgell, Ronnie Sahlberg
 +.br
 +Copyright \(co 2008 Martin Schwenke
 +.br
 +.PP
 +This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version\&.
 +.PP
 +This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE\&. See the GNU General Public License for more details\&.
 +.PP
 +You should have received a copy of the GNU General Public License along with this program; if not, see
 +\m[blue]\fB\%http://www.gnu.org/licenses\fR\m[]\&.
 +.sp
diff --cc ctdb/doc/onnode.1.html
index d82a905,0000000..e3c7461
mode 100644,000000..100644
--- a/ctdb/doc/onnode.1.html
+++ b/ctdb/doc/onnode.1.html
@@@ -1,125 -1,0 +1,125 @@@
- <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>onnode</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="onnode.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>onnode — run commands on CTDB cluster nodes</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cm [...]
++<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>onnode</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="onnode.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>onnode — run commands on CTDB cluster nodes</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cm [...]
 +      onnode is a utility to run commands on a specific node of a CTDB
 +      cluster, or on all nodes.
 +    </p><p>
 +      <em class="replaceable"><code>NODES</code></em> specifies which node(s) to run
 +      a command on.  See section <em class="citetitle">NODES
 +      SPECIFICATION</em> for details.
 +    </p><p>
 +      <em class="replaceable"><code>COMMAND</code></em> can be any shell command. The
 +      onnode utility uses ssh or rsh to connect to the remote nodes
 +      and run the command.
-     </p></div><div class="refsect1"><a name="idp49287248"></a><h2>OPTIONS</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term">-c</span></dt><dd><p>
++    </p></div><div class="refsect1"><a name="idp54651424"></a><h2>OPTIONS</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term">-c</span></dt><dd><p>
 +            Execute COMMAND in the current working directory on the
 +            specified nodes.
 +	  </p></dd><dt><span class="term">-f <em class="parameter"><code>FILENAME</code></em></span></dt><dd><p>
 +            Specify an alternative nodes FILENAME to use instead of
 +            the default.  This option overrides the CTDB_NODES_FILE
 +            environment variable.  See the discussion of
 +            <code class="filename">/etc/ctdb/nodes</code> in the FILES section
 +            for more details.
 +	  </p></dd><dt><span class="term">-i</span></dt><dd><p>
 +	    Keep standard input open, allowing data to be piped to
 +	    onnode.  Normally onnode closes stdin to avoid surprises
 +	    when scripting.  Note that this option is ignored when
 +	    using <code class="option">-p</code> or if <code class="envar">SSH</code> is set
 +	    to anything other than "ssh".
 +	  </p></dd><dt><span class="term">-n</span></dt><dd><p>
 +            Allow nodes to be specified by name rather than node
 +            numbers.  These nodes don't need to be listed in the nodes
 +            file.  You can avoid the nodes file entirely by combining
 +            this with <code class="code">-f /dev/null</code>.
 +	  </p></dd><dt><span class="term">-o <em class="parameter"><code>PREFIX</code></em></span></dt><dd><p>
 +	    Causes standard output from each node to be saved into a
 +	    file with name PREFIX.<em class="replaceable"><code>IP</code></em>.
 +	  </p></dd><dt><span class="term">-p</span></dt><dd><p>
 +            Run COMMAND in parallel on the specified nodes.  The
 +            default is to run COMMAND sequentially on each node.
 +	  </p></dd><dt><span class="term">-P</span></dt><dd><p>
 +            Push files to nodes.  Names of files to push are specified
 +            rather than the usual command.  Quoting is fragile/broken
 +            - filenames with whitespace in them are not supported.
 +	  </p></dd><dt><span class="term">-q</span></dt><dd><p>
 +            Do not print node addresses.  Normally, onnode prints
 +            informational node addresses if more than one node is
 +            specified.  This overrides -v.
 +	  </p></dd><dt><span class="term">-v</span></dt><dd><p>
 +            Print node addresses even if only one node is specified.
 +            Normally, onnode prints informational node addresses when
 +            more than one node is specified.
 +	  </p></dd><dt><span class="term">-h, --help</span></dt><dd><p>
 +            Show a short usage guide.
- 	  </p></dd></dl></div></div><div class="refsect1"><a name="idp49120144"></a><h2>NODES SPECIFICATION</h2><p>
++	  </p></dd></dl></div></div><div class="refsect1"><a name="idp53082368"></a><h2>NODES SPECIFICATION</h2><p>
 +      Nodes can be specified via numeric node numbers (from 0 to N-1)
 +      or mnemonics.  Multiple nodes are specified using lists of
 +      nodes, separated by commas, and ranges of numeric node numbers,
 +      separated by dashes.  If nodes are specified multiple times then
 +      the command will be executed multiple times on those nodes.  The
 +      order of nodes is significant.
 +    </p><p>
 +      The following mnemonics are available:
 +    </p><div class="variablelist"><dl class="variablelist"><dt><span class="term">all</span></dt><dd><p>
 +            All nodes.
 +	  </p></dd><dt><span class="term">any</span></dt><dd><p>
 +             A node where ctdbd is running.  This semi-random but
 +             there is a bias towards choosing a low numbered node.
 +	  </p></dd><dt><span class="term">ok | healthy</span></dt><dd><p>
 +            All nodes that are not disconnected, banned, disabled or
 +            unhealthy.
 +	  </p></dd><dt><span class="term">con | connected</span></dt><dd><p>
 +            All nodes that are not disconnected.
 +	  </p></dd><dt><span class="term">lvs | lvsmaster</span></dt><dd><p>
 +            The current LVS master.
 +	  </p></dd><dt><span class="term">natgw | natgwlist</span></dt><dd><p>
 +            The current NAT gateway.
 +	  </p></dd><dt><span class="term">rm | recmaster</span></dt><dd><p>
 +            The current recovery master.
- 	  </p></dd></dl></div></div><div class="refsect1"><a name="idp49137680"></a><h2>EXAMPLES</h2><p>
++	  </p></dd></dl></div></div><div class="refsect1"><a name="idp51121440"></a><h2>EXAMPLES</h2><p>
 +      The following command would show the process ID of ctdbd on all nodes
 +    </p><pre class="screen">
 +      onnode all ctdb getpid
 +    </pre><p>
 +      The following command would show the last 5 lines of log on each
 +      node, preceded by the node's hostname
 +    </p><pre class="screen">
 +      onnode all "hostname; tail -5 /var/log/log.ctdb"
 +    </pre><p>
 +      The following command would restart the ctdb service on all
 +      nodes, in parallel.
 +    </p><pre class="screen">
 +      onnode -p all service ctdb restart
 +    </pre><p>
 +      The following command would run ./foo in the current working
 +      directory, in parallel, on nodes 0, 2, 3 and 4.
 +    </p><pre class="screen">
 +      onnode -c -p 0,2-4 ./foo
-     </pre></div><div class="refsect1"><a name="idp49143024"></a><h2>ENVIRONMENT</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term"><code class="envar">CTDB_BASE</code></span></dt><dd><p>
++    </pre></div><div class="refsect1"><a name="idp52830032"></a><h2>ENVIRONMENT</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term"><code class="envar">CTDB_BASE</code></span></dt><dd><p>
 +	    Directory containing CTDB configuration files.  The
 +	    default is <code class="filename">/etc/ctdb</code>.
 +	  </p></dd><dt><span class="term"><code class="envar">CTDB_NODES_FILE</code></span></dt><dd><p>
 +	    Name of alternative nodes file to use instead of the
 +	    default.  See the <em class="citetitle">FILES</em> section for
 +	    more details.
- 	  </p></dd></dl></div></div><div class="refsect1"><a name="idp49148528"></a><h2>FILES</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term"><code class="filename">/etc/ctdb/nodes</code></span></dt><dd><p>
++	  </p></dd></dl></div></div><div class="refsect1"><a name="idp51106640"></a><h2>FILES</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term"><code class="filename">/etc/ctdb/nodes</code></span></dt><dd><p>
 +            Default file containing a list of each node's IP address
 +            or hostname.
 +	  </p><p>
 +	    Actually, the default is
 +	    <code class="filename">$CTDB_BASE/nodes</code>, where
 +	    <code class="envar">CTDB_BASE</code> defaults to
 +	    <code class="filename">/etc/ctdb</code>.  If a relative path is
 +	    given (via the -f option or <code class="envar">CTDB_BASE</code>) and
 +	    no corresponding file exists relative to the current
 +	    directory then the file is also searched for in the
 +	    <code class="filename">$CTDB_BASE</code> directory.
 +	  </p></dd><dt><span class="term"><code class="filename">/etc/ctdb/onnode.conf</code></span></dt><dd><p>
 +            If this file exists it is sourced by onnode.  The main
 +            purpose is to allow the administrator to set
 +            <code class="envar">SSH</code> to something other than "ssh".  In this
 +            case the -t option is ignored.  For example, the
 +            administrator may choose to use use rsh instead of ssh.
- 	  </p></dd></dl></div></div><div class="refsect1"><a name="idp55378400"></a><h2>SEE ALSO</h2><p>
++	  </p></dd></dl></div></div><div class="refsect1"><a name="idp54619408"></a><h2>SEE ALSO</h2><p>
 +      <span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span>,
 +
 +      <a class="ulink" href="http://ctdb.samba.org/" target="_top">http://ctdb.samba.org/</a>
 +    </p></div></div></body></html>
diff --cc ctdb/doc/ping_pong.1
index aa9d1b2,0000000..69da9aa
mode 100644,000000..100644
--- a/ctdb/doc/ping_pong.1
+++ b/ctdb/doc/ping_pong.1
@@@ -1,122 -1,0 +1,122 @@@
 +'\" t
 +.\"     Title: ping_pong
 +.\"    Author: 
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 09/08/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: CTDB - clustered TDB database
 +.\"    Source: ctdb
 +.\"  Language: English
 +.\"
- .TH "PING_PONG" "1" "09/08/2015" "ctdb" "CTDB \- clustered TDB database"
++.TH "PING_PONG" "1" "12/10/2015" "ctdb" "CTDB \- clustered TDB database"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +ping_pong \- measures the ping\-pong byte range lock latency
 +.SH "SYNOPSIS"
 +.HP \w'\fBping_pong\fR\ 'u
 +\fBping_pong\fR {\-r | \-w | \-rw} [\-m] [\-c] {\fIFILENAME\fR} {\fINUM\-LOCKS\fR}
 +.SH "DESCRIPTION"
 +.PP
 +ping_pong measures the byte range lock latency\&. It is especially useful on a cluster of nodes sharing a common lock manager as it will give some indication of the lock manager\*(Aqs performance under stress\&.
 +.PP
 +FILENAME is a file on shared storage to use for byte range locking tests\&.
 +.PP
 +NUM\-LOCKS is the number of byte range locks, so needs to be (strictly) greater than the number of nodes in the cluster\&.
 +.SH "OPTIONS"
 +.PP
 +\-r
 +.RS 4
 +test read performance
 +.RE
 +.PP
 +\-w
 +.RS 4
 +test write performance
 +.RE
 +.PP
 +\-m
 +.RS 4
 +use mmap
 +.RE
 +.PP
 +\-c
 +.RS 4
 +validate the locks
 +.RE
 +.SH "EXAMPLES"
 +.PP
 +Testing lock coherence
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +      ping_pong test\&.dat N
 +    
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +Testing lock coherence with lock validation
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +      ping_pong \-c test\&.dat N
 +    
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +Testing IO coherence
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +      ping_pong \-rw test\&.dat N
 +    
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.SH "SEE ALSO"
 +.PP
 +\fBctdb\fR(7),
 +\m[blue]\fB\%https://wiki.samba.org/index.php/Ping_pong\fR\m[]
 +.SH "AUTHOR"
 +.br
 +.PP
 +This documentation was written by Mathieu Parent
 +.SH "COPYRIGHT"
 +.br
 +Copyright \(co 2002 Andrew Tridgell
 +.br
 +.PP
 +This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version\&.
 +.PP
 +This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE\&. See the GNU General Public License for more details\&.
 +.PP
 +You should have received a copy of the GNU General Public License along with this program; if not, see
 +\m[blue]\fB\%http://www.gnu.org/licenses\fR\m[]\&.
 +.sp
diff --cc ctdb/doc/ping_pong.1.html
index 9ba3db3,0000000..16a2863
mode 100644,000000..100644
--- a/ctdb/doc/ping_pong.1.html
+++ b/ctdb/doc/ping_pong.1.html
@@@ -1,37 -1,0 +1,37 @@@
- <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ping_pong</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="ping_pong.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ping_pong — measures the ping-pong byte range lock latency</p></div><div class="refsynopsisdiv"><h2>Synops [...]
++<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ping_pong</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="ping_pong.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ping_pong — measures the ping-pong byte range lock latency</p></div><div class="refsynopsisdiv"><h2>Synops [...]
 +      ping_pong measures the byte range lock latency. It is especially
 +      useful on a cluster of nodes sharing a common lock manager as it
 +      will give some indication of the lock manager's performance
 +      under stress.
 +    </p><p>
 +      FILENAME is a file on shared storage to use for byte range
 +      locking tests.
 +    </p><p>
 +      NUM-LOCKS is the number of byte range locks, so needs to be
 +      (strictly) greater than the number of nodes in the cluster.
-     </p></div><div class="refsect1"><a name="idp49283344"></a><h2>OPTIONS</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term">-r</span></dt><dd><p>
++    </p></div><div class="refsect1"><a name="idp50142544"></a><h2>OPTIONS</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term">-r</span></dt><dd><p>
 +	    test read performance
 +	  </p></dd><dt><span class="term">-w</span></dt><dd><p>
 +	    test write performance
 +	  </p></dd><dt><span class="term">-m</span></dt><dd><p>
 +	    use mmap
 +	  </p></dd><dt><span class="term">-c</span></dt><dd><p>
 +	    validate the locks
- 	  </p></dd></dl></div></div><div class="refsect1"><a name="idp49290944"></a><h2>EXAMPLES</h2><p>
++	  </p></dd></dl></div></div><div class="refsect1"><a name="idp53880944"></a><h2>EXAMPLES</h2><p>
 +      Testing lock coherence
 +    </p><pre class="screen">
 +      ping_pong test.dat N
 +    </pre><p>
 +      Testing lock coherence with lock validation
 +    </p><pre class="screen">
 +      ping_pong -c test.dat N
 +    </pre><p>
 +      Testing IO coherence
 +    </p><pre class="screen">
 +      ping_pong -rw test.dat N
-     </pre></div><div class="refsect1"><a name="idp49107120"></a><h2>SEE ALSO</h2><p>
++    </pre></div><div class="refsect1"><a name="idp53885104"></a><h2>SEE ALSO</h2><p>
 +      <span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span>,
 +
 +      <a class="ulink" href="https://wiki.samba.org/index.php/Ping_pong" target="_top">https://wiki.samba.org/index.php/Ping_pong</a>
 +
 +    </p></div></div></body></html>
diff --cc docs/manpages/dbwrap_tool.1
index 93893b0,0000000..7362765
mode 100644,000000..100644
--- a/docs/manpages/dbwrap_tool.1
+++ b/docs/manpages/dbwrap_tool.1
@@@ -1,311 -1,0 +1,311 @@@
 +'\" t
 +.\"     Title: dbwrap_tool
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: System Administration tools
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "DBWRAP_TOOL" "1" "12/01/2015" "Samba 4\&.3" "System Administration tools"
++.TH "DBWRAP_TOOL" "1" "12/10/2015" "Samba 4\&.3" "System Administration tools"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +dbwrap_tool \- low level TDB/CTDB manipulation tool using the dbwrap interface
 +.SH "SYNOPSIS"
 +.HP \w'\ 'u
 +dbwrap_tool [\-\-persistent] [\-\-non\-persistent] [\-d\ <debug\ level>] [\-s\ <config\ file>] [\-l\ <log\ file\ base>] [\-V] [\-\-option=<name>=<value>] {<database>} {<operation>} [<key>\ [<type>\ [<value>]]]
 +.SH "DESCRIPTION"
 +.PP
 +This tool is part of the
 +\fBsamba\fR(7)
 +suite\&.
 +.PP
 +The dbwrap_tool program is used to read and manipulate TDB/CTDB databases using the dbwrap interface\&.
 +.PP
 +The following database operations are available:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +fetch: fetch a record
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +store: create or modify a record
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +delete: remove a record
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +exists: test for existence of a record
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +erase: remove all records
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +listkeys: list all available records
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +listwatchers: list processes, which are waiting for changes in a record
 +.RE
 +.sp
 +.RE
 +.PP
 +The following types are available:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +int32: signed 32bit integer
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +uint32: unsigned 32bit integer
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +string: "hello world"
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +hex: hex strings like "68656C6C6F20776F726C6400" ("hello world")
 +.RE
 +.sp
 +.RE
 +.SH "OPTIONS"
 +.PP
 +\-\-persistent
 +.RS 4
 +Open the database as a persistent database\&.
 +.sp
 +Exactly one of \-\-persistent and \-\-non\-persistent must be specified\&.
 +.RE
 +.PP
 +\-\-non\-persistent
 +.RS 4
 +Open the database as a non\-persistent database\&.
 +.sp
 +Caveat: opening a database as non\-persistent when there is currently no other opener will wipe the database\&.
 +.sp
 +Exactly one of \-\-persistent and \-\-non\-persistent must be specified\&.
 +.RE
 +.PP
 +\-d|\-\-debuglevel=level
 +.RS 4
 +\fIlevel\fR
 +is an integer from 0 to 10\&. The default value if this parameter is not specified is 1\&.
 +.sp
 +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day\-to\-day running \- it generates a small amount of information about operations carried out\&.
 +.sp
 +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&.
 +.sp
 +Note that specifying this parameter here will override the
 +\m[blue]\fBlog level\fR\m[]
 +parameter in the
 +smb\&.conf
 +file\&.
 +.RE
 +.PP
 +\-V|\-\-version
 +.RS 4
 +Prints the program version number\&.
 +.RE
 +.PP
 +\-s|\-\-configfile=<configuration file>
 +.RS 4
 +The file specified contains the configuration details required by the server\&. The information in this file includes server\-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See
 +smb\&.conf
 +for more information\&. The default configuration file name is determined at compile time\&.
 +.RE
 +.PP
 +\-l|\-\-log\-basename=logdirectory
 +.RS 4
 +Base directory name for log/debug files\&. The extension
 +\fB"\&.progname"\fR
 +will be appended (e\&.g\&. log\&.smbclient, log\&.smbd, etc\&.\&.\&.)\&. The log file is never removed by the client\&.
 +.RE
 +.PP
 +\-\-option=<name>=<value>
 +.RS 4
 +Set the
 +\fBsmb.conf\fR(5)
 +option "<name>" to value "<value>" from the command line\&. This overrides compiled\-in defaults and options read from the configuration file\&.
 +.RE
 +.PP
 +\-?|\-\-help
 +.RS 4
 +Print a summary of command line options\&.
 +.RE
 +.PP
 +\-\-usage
 +.RS 4
 +Display brief usage message\&.
 +.RE
 +.SH "COMMANDS"
 +.SS "fetch"
 +.HP \w'\ 'u
 +dbwrap_tool <database> fetch <key> <type>
 +		
 +.SS "store"
 +.HP \w'\ 'u
 +dbwrap_tool <database> store <key> <type> <value>
 +		
 +.SS "delete"
 +.HP \w'\ 'u
 +dbwrap_tool <database> delete <key>
 +		
 +.SS "exists"
 +.HP \w'\ 'u
 +dbwrap_tool <database> exists <key>
 +		
 +.SS "erase"
 +.HP \w'\ 'u
 +dbwrap_tool <database> erase 
 +.SS "listkeys"
 +.HP \w'\ 'u
 +dbwrap_tool <database> listkeys
 +		
 +.SS "listwatchers"
 +.HP \w'\ 'u
 +dbwrap_tool <database> listwatchers
 +		
 +.SH "EXAMPLES"
 +.PP
 +List all keys from winbindd_idmap\&.tdb
 +.RS 4
 +dbwrap_tool
 +\-\-persistent winbindd_idmap\&.tdb listkeys
 +.RE
 +.PP
 +Fetch record with key "USER HWM" as uint32
 +.RS 4
 +dbwrap_tool
 +\-\-persistent winbindd_idmap\&.tdb fetch "USER HWM" uint32
 +.RE
 +.PP
 +Remove record with key "USER HWM"
 +.RS 4
 +dbwrap_tool
 +\-\-persistent winbindd_idmap\&.tdb remove "USER HWM"
 +.RE
 +.PP
 +Store and overwrite record "USER HWM" with value 214
 +.RS 4
 +uint32:
 +dbwrap_tool
 +\-\-persistent winbindd_idmap\&.tdb store "USER HWM" uint32 214
 +hex:
 +dbwrap_tool
 +\-\-persistent winbindd_idmap\&.tdb store "USER HWM" hex D6000000
 +.RE
 +.SH "NOTES"
 +.PP
 +Use with caution!
 +.SH "VERSION"
 +.PP
 +This man page is correct for version 3 of the Samba suite\&.
 +.SH "SEE ALSO"
 +.PP
 +\fBsmbd\fR(8),
 +\fBsamba\fR(7)
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
 +.PP
 +The dbwrap_tool manpage was written by Bjoern Baumbach\&.
diff --cc docs/manpages/eventlogadm.8
index bf6b74c,0000000..2375350
mode 100644,000000..100644
--- a/docs/manpages/eventlogadm.8
+++ b/docs/manpages/eventlogadm.8
@@@ -1,344 -1,0 +1,344 @@@
 +'\" t
 +.\"     Title: eventlogadm
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: System Administration tools
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "EVENTLOGADM" "8" "12/01/2015" "Samba 4\&.3" "System Administration tools"
++.TH "EVENTLOGADM" "8" "12/10/2015" "Samba 4\&.3" "System Administration tools"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +eventlogadm \- push records into the Samba event log store
 +.SH "SYNOPSIS"
 +.HP \w'\ 'u
 +eventlogadm [\fB\-s\fR] [\fB\-d\fR] [\fB\-h\fR] \fB\-o\fR\ addsource\ \fIEVENTLOG\fR\ \fISOURCENAME\fR\ \fIMSGFILE\fR
 +.HP \w'\ 'u
 +eventlogadm [\fB\-s\fR] [\fB\-d\fR] [\fB\-h\fR] \fB\-o\fR\ write\ \fIEVENTLOG\fR
 +.HP \w'\ 'u
 +eventlogadm [\fB\-s\fR] [\fB\-d\fR] [\fB\-h\fR] \fB\-o\fR\ dump\ \fIEVENTLOG\fR\ \fIRECORD_NUMBER\fR
 +.SH "DESCRIPTION"
 +.PP
 +This tool is part of the
 +\fBsamba\fR(1)
 +suite\&.
 +.PP
 +eventlogadm
 +is a filter that accepts formatted event log records on standard input and writes them to the Samba event log store\&. Windows client can then manipulate these record using the usual administration tools\&.
 +.SH "OPTIONS"
 +.PP
 +\fB\-s\fR \fIFILENAME\fR
 +.RS 4
 +The
 +\-s
 +option causes
 +eventlogadm
 +to load the configuration file given as FILENAME instead of the default one used by Samba\&.
 +.RE
 +.PP
 +\fB\-d\fR
 +.RS 4
 +The
 +\-d
 +option causes
 +eventlogadm
 +to emit debugging information\&.
 +.RE
 +.PP
 +\fB\-o\fR addsource \fIEVENTLOG\fR \fISOURCENAME\fR \fIMSGFILE\fR
 +.RS 4
 +The
 +\-o addsource
 +option creates a new event log source\&.
 +.RE
 +.PP
 +\fB\-o\fR write \fIEVENTLOG\fR
 +.RS 4
 +The
 +\-o write
 +reads event log records from standard input and writes them to the Samba event log store named by EVENTLOG\&.
 +.RE
 +.PP
 +\fB\-o\fR dump \fIEVENTLOG\fR \fIRECORD_NUMBER\fR
 +.RS 4
 +The
 +\-o dump
 +reads event log records from a EVENTLOG tdb and dumps them to standard output on screen\&.
 +.RE
 +.PP
 +\fB\-h\fR
 +.RS 4
 +Print usage information\&.
 +.RE
 +.SH "EVENTLOG RECORD FORMAT"
 +.PP
 +For the write operation,
 +eventlogadm
 +expects to be able to read structured records from standard input\&. These records are a sequence of lines, with the record key and data separated by a colon character\&. Records are separated by at least one or more blank line\&.
 +.PP
 +The event log record field are:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +LEN
 +\- This field should be 0, since
 +eventlogadm
 +will calculate this value\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +RS1
 +\- This must be the value 1699505740\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +RCN
 +\- This field should be 0\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +TMG
 +\- The time the eventlog record was generated; format is the number of seconds since 00:00:00 January 1, 1970, UTC\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +TMW
 +\- The time the eventlog record was written; format is the number of seconds since 00:00:00 January 1, 1970, UTC\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +EID
 +\- The eventlog ID\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +ETP
 +\- The event type \-\- one of "INFO", "ERROR", "WARNING", "AUDIT SUCCESS" or "AUDIT FAILURE"\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +ECT
 +\- The event category; this depends on the message file\&. It is primarily used as a means of filtering in the eventlog viewer\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +RS2
 +\- This field should be 0\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +CRN
 +\- This field should be 0\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +USL
 +\- This field should be 0\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +SRC
 +\- This field contains the source name associated with the event log\&. If a message file is used with an event log, there will be a registry entry for associating this source name with a message file DLL\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +SRN
 +\- The name of the machine on which the eventlog was generated\&. This is typically the host name\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +STR
 +\- The text associated with the eventlog\&. There may be more than one string in a record\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +DAT
 +\- This field should be left unset\&.
 +.RE
 +.SH "EXAMPLES"
 +.PP
 +An example of the record format accepted by
 +eventlogadm:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	LEN: 0
 +	RS1: 1699505740
 +	RCN: 0
 +	TMG: 1128631322
 +	TMW: 1128631322
 +	EID: 1000
 +	ETP: INFO
 +	ECT: 0
 +	RS2: 0
 +	CRN: 0
 +	USL: 0
 +	SRC: cron
 +	SRN: dmlinux
 +	STR: (root) CMD ( rm \-f /var/spool/cron/lastrun/cron\&.hourly)
 +	DAT:
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +Set up an eventlog source, specifying a message file DLL:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	eventlogadm \-o addsource Application MyApplication | \e\e
 +	    	%SystemRoot%/system32/MyApplication\&.dll
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +Filter messages from the system log into an event log:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	tail \-f /var/log/messages | \e\e
 +		my_program_to_parse_into_eventlog_records | \e\e
 +	      	eventlogadm SystemLogEvents
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.SH "VERSION"
 +.PP
 +This man page is correct for version 3\&.0\&.25 of the Samba suite\&.
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
diff --cc docs/manpages/findsmb.1
index 1c770f6,0000000..f1f9c6d
mode 100644,000000..100644
--- a/docs/manpages/findsmb.1
+++ b/docs/manpages/findsmb.1
@@@ -1,133 -1,0 +1,133 @@@
 +'\" t
 +.\"     Title: findsmb
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: User Commands
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "FINDSMB" "1" "12/01/2015" "Samba 4\&.3" "User Commands"
++.TH "FINDSMB" "1" "12/10/2015" "Samba 4\&.3" "User Commands"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +findsmb \- list info about machines that respond to SMB name queries on a subnet
 +.SH "SYNOPSIS"
 +.HP \w'\ 'u
 +findsmb [subnet\ broadcast\ address]
 +.SH "DESCRIPTION"
 +.PP
 +This perl script is part of the
 +\fBsamba\fR(7)
 +suite\&.
 +.PP
 +findsmb
 +is a perl script that prints out several pieces of information about machines on a subnet that respond to SMB name query requests\&. It uses
 +\fBnmblookup\fR(1)
 +and
 +\fBsmbclient\fR(1)
 +to obtain this information\&.
 +.SH "OPTIONS"
 +.PP
 +\-r
 +.RS 4
 +Controls whether
 +findsmb
 +takes bugs in Windows95 into account when trying to find a Netbios name registered of the remote machine\&. This option is disabled by default because it is specific to Windows 95 and Windows 95 machines only\&. If set,
 +\fBnmblookup\fR(1)
 +will be called with
 +\fB\-B\fR
 +option\&.
 +.RE
 +.PP
 +subnet broadcast address
 +.RS 4
 +Without this option,
 +findsmb
 +will probe the subnet of the machine where
 +\fBfindsmb\fR(1)
 +is run\&. This value is passed to
 +\fBnmblookup\fR(1)
 +as part of the
 +\fB\-B\fR
 +option\&.
 +.RE
 +.SH "EXAMPLES"
 +.PP
 +The output of
 +findsmb
 +lists the following information for all machines that respond to the initial
 +nmblookup
 +for any name: IP address, NetBIOS name, Workgroup name, operating system, and SMB server version\&.
 +.PP
 +There will be a \*(Aq+\*(Aq in front of the workgroup name for machines that are local master browsers for that workgroup\&. There will be an \*(Aq*\*(Aq in front of the workgroup name for machines that are the domain master browser for that workgroup\&. Machines that are running Windows for Workgroups, Windows 95 or Windows 98 will not show any information about the operating system or server version\&.
 +.PP
 +The command with
 +\fB\-r\fR
 +option must be run on a system without
 +\fBnmbd\fR(8)
 +running\&. If
 +nmbd
 +is running on the system, you will only get the IP address and the DNS name of the machine\&. To get proper responses from Windows 95 and Windows 98 machines, the command must be run as root and with
 +\fB\-r\fR
 +option on a machine without
 +nmbd
 +running\&.
 +.PP
 +For example, running
 +findsmb
 +without
 +\fB\-r\fR
 +option set would yield output similar to the following
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +IP ADDR         NETBIOS NAME   WORKGROUP/OS/VERSION 
 +\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- 
 +192\&.168\&.35\&.10   MINESET\-TEST1  [DMVENGR]
 +192\&.168\&.35\&.55   LINUXBOX      *[MYGROUP] [Unix] [Samba 2\&.0\&.6]
 +192\&.168\&.35\&.56   HERBNT2        [HERB\-NT]
 +192\&.168\&.35\&.63   GANDALF        [MVENGR] [Unix] [Samba 2\&.0\&.5a for IRIX]
 +192\&.168\&.35\&.65   SAUNA          [WORKGROUP] [Unix] [Samba 1\&.9\&.18p10]
 +192\&.168\&.35\&.71   FROGSTAR       [ENGR] [Unix] [Samba 2\&.0\&.0 for IRIX]
 +192\&.168\&.35\&.78   HERBDHCP1     +[HERB]
 +192\&.168\&.35\&.88   SCNT2         +[MVENGR] [Windows NT 4\&.0] [NT LAN Manager 4\&.0]
 +192\&.168\&.35\&.93   FROGSTAR\-PC    [MVENGR] [Windows 5\&.0] [Windows 2000 LAN Manager]
 +192\&.168\&.35\&.97   HERBNT1       *[HERB\-NT] [Windows NT 4\&.0] [NT LAN Manager 4\&.0]
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.SH "VERSION"
 +.PP
 +This man page is correct for version 3 of the Samba suite\&.
 +.SH "SEE ALSO"
 +.PP
 +\fBnmbd\fR(8),
 +\fBsmbclient\fR(1), and
 +\fBnmblookup\fR(1)
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
 +.PP
 +The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at
 +ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
diff --cc docs/manpages/idmap_ad.8
index 97e5bb1,0000000..313771d
mode 100644,000000..100644
--- a/docs/manpages/idmap_ad.8
+++ b/docs/manpages/idmap_ad.8
@@@ -1,78 -1,0 +1,78 @@@
 +'\" t
 +.\"     Title: idmap_ad
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: System Administration tools
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "IDMAP_AD" "8" "12/01/2015" "Samba 4\&.3" "System Administration tools"
++.TH "IDMAP_AD" "8" "12/10/2015" "Samba 4\&.3" "System Administration tools"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +idmap_ad \- Samba\*(Aqs idmap_ad Backend for Winbind
 +.SH "DESCRIPTION"
 +.PP
 +The idmap_ad plugin provides a way for Winbind to read id mappings from an AD server that uses RFC2307/SFU schema extensions\&. This module implements only the "idmap" API, and is READONLY\&. Mappings must be provided in advance by the administrator by adding the uidNumber attributes for users and gidNumber attributes for groups in the AD\&. Winbind will only map users that have a uidNumber and whose primary group have a gidNumber attribute set\&. It is however recommended that all grou [...]
 +.PP
 +Currently, the
 +\fIad\fR
 +backend does not work as the default idmap backend, but one has to configure it separately for each domain for which one wants to use it, using disjoint ranges\&. One usually needs to configure a writeable default idmap range, using for example the
 +\fItdb\fR
 +or
 +\fIldap\fR
 +backend, in order to be able to map the BUILTIN sids and possibly other trusted domains\&. The writeable default config is also needed in order to be able to create group mappings\&. This catch\-all default idmap configuration should have a range that is disjoint from any explicitly configured domain with idmap backend
 +\fIad\fR\&. See the example below\&.
 +.SH "IDMAP OPTIONS"
 +.PP
 +range = low \- high
 +.RS 4
 +Defines the available matching UID and GID range for which the backend is authoritative\&. Note that the range acts as a filter\&. If specified any UID or GID stored in AD that fall outside the range is ignored and the corresponding map is discarded\&. It is intended as a way to avoid accidental UID/GID overlaps between local and remotely defined IDs\&.
 +.RE
 +.PP
 +schema_mode = <rfc2307 | sfu | sfu20>
 +.RS 4
 +Defines the schema that idmap_ad should use when querying Active Directory regarding user and group information\&. This can be either the RFC2307 schema support included in Windows 2003 R2 or the Service for Unix (SFU) schema\&. For SFU 3\&.0 or 3\&.5 please choose "sfu", for SFU 2\&.0 please choose "sfu20"\&. Please note that primary group membership is currently always calculated via the "primaryGroupID" LDAP attribute\&.
 +.RE
 +.SH "EXAMPLES"
 +.PP
 +The following example shows how to retrieve idmappings from our principal and trusted AD domains\&. If trusted domains are present id conflicts must be resolved beforehand, there is no guarantee on the order conflicting mappings would be resolved at this point\&. This example also shows how to leave a small non conflicting range for local id allocation that may be used in internal backends like BUILTIN\&.
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	[global]
 +	workgroup = CORP
 +
 +	idmap config * : backend = tdb
 +	idmap config * : range = 1000000\-1999999
 +
 +	idmap config CORP : backend  = ad
 +	idmap config CORP : range = 1000\-999999
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
diff --cc docs/manpages/idmap_autorid.8
index 3670bd1,0000000..ec7d0b2
mode 100644,000000..100644
--- a/docs/manpages/idmap_autorid.8
+++ b/docs/manpages/idmap_autorid.8
@@@ -1,143 -1,0 +1,143 @@@
 +'\" t
 +.\"     Title: idmap_autorid
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: System Administration tools
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "IDMAP_AUTORID" "8" "12/01/2015" "Samba 4\&.3" "System Administration tools"
++.TH "IDMAP_AUTORID" "8" "12/10/2015" "Samba 4\&.3" "System Administration tools"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +idmap_autorid \- Samba\*(Aqs idmap_autorid Backend for Winbind
 +.SH "DESCRIPTION"
 +.PP
 +The idmap_autorid backend provides a way to use an algorithmic mapping scheme to map UIDs/GIDs and SIDs that is more deterministic than idmap_tdb and easier to configure than idmap_rid\&.
 +.PP
 +The module works similar to idmap_rid, but it automatically configures the range to be used for each domain, so there is no need to specify a specific range for each domain in the forest, the only configuration that is needed is the range of uid/gids that shall be used for user/group mappings and an optional size of the ranges to be used\&.
 +.PP
 +The mappings of which domain is mapped to which range is stored in autorid\&.tdb, thus you should backup this database regularly\&.
 +.PP
 +Due to the algorithm being used, it is the module that is most easy to use as it only requires a minimal configuration\&.
 +.SH "IDMAP OPTIONS"
 +.PP
 +rangesize = numberofidsperdomain
 +.RS 4
 +Defines the number of uids/gids available per domain range\&. The minimum needed value is 2000\&. SIDs with RIDs larger than this value will be mapped into extension ranges depending upon number of available ranges\&. If the autorid backend runs out of available ranges, mapping requests for new domains (or new extension ranges for domains already known) are ignored and the corresponding map is discarded\&.
 +.sp
 +Example: with rangesize set to 10000, users/groups with a RID up to 10000 will be put into the first range for the domain\&. When attempting to map the an object with a RID of 25000, an extension range will be allocated that will then be used to map all RIDs from 20000\-29999\&.
 +.sp
 +One range will be used for local users and groups and for non\-domain well\-known SIDs like Everyone (S\-1\-1\-0) or Creator Owner (S\-1\-3\-0)\&. A chosen list of well\-known SIDs will be preallocated on first start to create deterministic mappings for those\&.
 +.sp
 +Thus the number of local users and groups that can be created is limited by this option as well\&. If you plan to create a large amount of local users or groups, you will need set this parameter accordingly\&.
 +.sp
 +The default value is 100000\&.
 +.RE
 +.PP
 +read only = [ yes | no ]
 +.RS 4
 +Turn the module into read\-only mode\&. No new ranges will be allocated nor will new mappings be created in the idmap pool\&. Defaults to no\&.
 +.RE
 +.PP
 +ignore builtin = [ yes | no ]
 +.RS 4
 +Ignore any mapping requests for the BUILTIN domain\&. Defaults to no\&.
 +.RE
 +.SH "THE MAPPING FORMULAS"
 +.PP
 +The Unix ID for a RID is calculated this way:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +			ID =  REDUCED RID + IDMAP RANGE LOW VALUE + RANGE NUMBER * RANGE SIZE
 +		
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.sp
 +where REDUCED RID = RID % RANGE_SIZE and a DOMAIN RANGE INDEX = RID / RANGE_SIZE is used together with the domain sid to determine the RANGE NUMBER (stored in the database)\&.
 +.PP
 +Correspondingly, the formula for calculating the RID for a given Unix ID is this:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +			RID = (ID \- LOW ID) % RANGE SIZE + DOMAIN RANGE INDEX * RANGE SIZE
 +		
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.sp
 +Where the DOMAIN RANGE INDEX is retrieved from the database along with the domain sid by the RANGE NUMBER = (ID \- LOW ID) / RANGE SIZE \&.
 +.SH "EXAMPLES"
 +.PP
 +This example shows you the minimal configuration that will work for the principal domain and 19 trusted domains / range extensions\&.
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	[global]
 +	security = ads
 +	workgroup = CUSTOMER
 +	realm = CUSTOMER\&.COM
 +
 +	idmap config * : backend = autorid
 +	idmap config * : range = 1000000\-1999999
 +
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +This example shows how to configure idmap_autorid as default for all domains with a potentially large amount of users plus a specific configuration for a trusted domain that uses the SFU mapping scheme\&. Please note that idmap ranges and sfu ranges are not allowed to overlap\&.
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	[global]
 +	security = ads
 +	workgroup = CUSTOMER
 +	realm = CUSTOMER\&.COM
 +
 +	idmap config * : backend = autorid
 +	idmap config * : range = 1000000\-19999999
 +	idmap config * : rangesize = 1000000
 +
 +	idmap config TRUSTED : backend  = ad
 +	idmap config TRUSTED : range    = 50000 \- 99999
 +	idmap config TRUSTED : schema_mode = sfu
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
diff --cc docs/manpages/idmap_hash.8
index 20b0926,0000000..746d035
mode 100644,000000..100644
--- a/docs/manpages/idmap_hash.8
+++ b/docs/manpages/idmap_hash.8
@@@ -1,65 -1,0 +1,65 @@@
 +'\" t
 +.\"     Title: idmap_hash
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: System Administration tools
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "IDMAP_HASH" "8" "12/01/2015" "Samba 4\&.3" "System Administration tools"
++.TH "IDMAP_HASH" "8" "12/10/2015" "Samba 4\&.3" "System Administration tools"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +idmap_hash \- Samba\*(Aqs idmap_hash Backend for Winbind
 +.SH "DESCRIPTION"
 +.PP
 +The idmap_hash plugin implements a hashing algorithm used to map SIDs for domain users and groups to 31\-bit uids and gids, respectively\&. This plugin also implements the nss_info API and can be used to support a local name mapping files if enabled via the "winbind normalize names" and "winbind nss info" parameters in smb\&.conf\&.
 +.SH "IDMAP OPTIONS"
 +.PP
 +name_map
 +.RS 4
 +Specifies the absolute path to the name mapping file used by the nss_info API\&. Entries in the file are of the form "\fIunix name\fR
 +=
 +\fIqualified domain name\fR"\&. Mapping of both user and group names is supported\&.
 +.RE
 +.SH "EXAMPLES"
 +.PP
 +The following example utilizes the idmap_hash plugin for the idmap and nss_info information\&.
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	[global]
 +	idmap config * : backend = hash
 +	idmap config * : range = 1000\-4000000000
 +
 +	winbind nss info = hash
 +	winbind normalize names = yes
 +	idmap_hash:name_map = /etc/samba/name_map\&.cfg
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
diff --cc docs/manpages/idmap_ldap.8
index d448d27,0000000..4afcadc
mode 100644,000000..100644
--- a/docs/manpages/idmap_ldap.8
+++ b/docs/manpages/idmap_ldap.8
@@@ -1,106 -1,0 +1,106 @@@
 +'\" t
 +.\"     Title: idmap_ldap
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: System Administration tools
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "IDMAP_LDAP" "8" "12/01/2015" "Samba 4\&.3" "System Administration tools"
++.TH "IDMAP_LDAP" "8" "12/10/2015" "Samba 4\&.3" "System Administration tools"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +idmap_ldap \- Samba\*(Aqs idmap_ldap Backend for Winbind
 +.SH "DESCRIPTION"
 +.PP
 +The idmap_ldap plugin provides a means for Winbind to store and retrieve SID/uid/gid mapping tables in an LDAP directory service\&.
 +.PP
 +In contrast to read only backends like idmap_rid, it is an allocating backend: This means that it needs to allocate new user and group IDs in order to create new mappings\&.
 +.SH "IDMAP OPTIONS"
 +.PP
 +ldap_base_dn = DN
 +.RS 4
 +Defines the directory base suffix to use for SID/uid/gid mapping entries\&. If not defined, idmap_ldap will default to using the "ldap idmap suffix" option from smb\&.conf\&.
 +.RE
 +.PP
 +ldap_user_dn = DN
 +.RS 4
 +Defines the user DN to be used for authentication\&. The secret for authenticating this user should be stored with net idmap secret (see
 +\fBnet\fR(8))\&. If absent, the ldap credentials from the ldap passdb configuration are used, and if these are also absent, an anonymous bind will be performed as last fallback\&.
 +.RE
 +.PP
 +ldap_url = ldap://server/
 +.RS 4
 +Specifies the LDAP server to use for SID/uid/gid map entries\&. If not defined, idmap_ldap will assume that ldap://localhost/ should be used\&.
 +.RE
 +.PP
 +range = low \- high
 +.RS 4
 +Defines the available matching uid and gid range for which the backend is authoritative\&.
 +.RE
 +.SH "EXAMPLES"
 +.PP
 +The following example shows how an ldap directory is used as the default idmap backend\&. It also configures the idmap range and base directory suffix\&. The secret for the ldap_user_dn has to be set with "net idmap secret \*(Aq*\*(Aq password"\&.
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	[global]
 +	idmap config * : backend      = ldap
 +	idmap config * : range        = 1000000\-1999999
 +	idmap config * : ldap_url     = ldap://localhost/
 +	idmap config * : ldap_base_dn = ou=idmap,dc=example,dc=com
 +	idmap config * : ldap_user_dn = cn=idmap_admin,dc=example,dc=com
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +This example shows how ldap can be used as a readonly backend while tdb is the default backend used to store the mappings\&. It adds an explicit configuration for some domain DOM1, that uses the ldap idmap backend\&. Note that a range disjoint from the default range is used\&.
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	[global]
 +	# "backend = tdb" is redundant here since it is the default
 +	idmap config * : backend = tdb
 +	idmap config * : range = 1000000\-1999999
 +
 +	idmap config DOM1 : backend = ldap
 +	idmap config DOM1 : range = 2000000\-2999999
 +	idmap config DOM1 : read only = yes
 +	idmap config DOM1 : ldap_url = ldap://server/
 +	idmap config DOM1 : ldap_base_dn = ou=idmap,dc=dom1,dc=example,dc=com
 +	idmap config DOM1 : ldap_user_dn = cn=idmap_admin,dc=dom1,dc=example,dc=com
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.SH "NOTE"
 +.PP
 +In order to use authentication against ldap servers you may need to provide a DN and a password\&. To avoid exposing the password in plain text in the configuration file we store it into a security store\&. The "net idmap " command is used to store a secret for the DN specified in a specific idmap domain\&.
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
diff --cc docs/manpages/idmap_nss.8
index aa7c224,0000000..2c40f24
mode 100644,000000..100644
--- a/docs/manpages/idmap_nss.8
+++ b/docs/manpages/idmap_nss.8
@@@ -1,56 -1,0 +1,56 @@@
 +'\" t
 +.\"     Title: idmap_nss
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: System Administration tools
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "IDMAP_NSS" "8" "12/01/2015" "Samba 4\&.3" "System Administration tools"
++.TH "IDMAP_NSS" "8" "12/10/2015" "Samba 4\&.3" "System Administration tools"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +idmap_nss \- Samba\*(Aqs idmap_nss Backend for Winbind
 +.SH "DESCRIPTION"
 +.PP
 +The idmap_nss plugin provides a means to map Unix users and groups to Windows accounts and obsoletes the "winbind trusted domains only" smb\&.conf option\&. This provides a simple means of ensuring that the SID for a Unix user named jsmith is reported as the one assigned to DOMAIN\ejsmith which is necessary for reporting ACLs on files and printers stored on a Samba member server\&.
 +.SH "EXAMPLES"
 +.PP
 +This example shows how to use idmap_nss to check the local accounts for its own domain while using allocation to create new mappings for trusted domains
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	[global]
 +	idmap config * : backend = tdb
 +	idmap config * : range = 1000000\-1999999
 +
 +	idmap config SAMBA : backend  = nss
 +	idmap config SAMBA : range = 1000\-999999
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
diff --cc docs/manpages/idmap_rfc2307.8
index 336bfaf,0000000..e4478ba
mode 100644,000000..100644
--- a/docs/manpages/idmap_rfc2307.8
+++ b/docs/manpages/idmap_rfc2307.8
@@@ -1,123 -1,0 +1,123 @@@
 +'\" t
 +.\"     Title: idmap_rfc2307
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: System Administration tools
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "IDMAP_RFC2307" "8" "12/01/2015" "Samba 4\&.3" "System Administration tools"
++.TH "IDMAP_RFC2307" "8" "12/10/2015" "Samba 4\&.3" "System Administration tools"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +idmap_rfc2307 \- Samba\*(Aqs idmap_rfc2307 Backend for Winbind
 +.SH "DESCRIPTION"
 +.PP
 +The idmap_rfc2307 plugin provides a way for winbind to read id mappings from records in an LDAP server as defined in RFC 2307\&. The LDAP server can be stand\-alone or the LDAP server provided by the AD server\&. An AD server is always required to provide the mapping between name and SID, and the LDAP server is queried for the mapping between name and uid/gid\&. This module implements only the "idmap" API, and is READONLY\&.
 +.PP
 +Mappings must be provided in advance by the administrator by creating the user accounts in the Active Directory server and the posixAccount and posixGroup objects in the LDAP server\&. The names in the Active Directory server and in the LDAP server have to be the same\&.
 +.PP
 +This id mapping approach allows the reuse of existing LDAP authentication servers that store records in the RFC 2307 format\&.
 +.PP
 +When connecting to the LDAP server provided by an AD server, the parameter
 +\m[blue]\fBldap ssl ads\fR\m[]
 +determines whether SSL should be used\&. When using a stand\-alone LDAP server,
 +\m[blue]\fBldap ssl\fR\m[]
 +applies\&.
 +.SH "IDMAP OPTIONS"
 +.PP
 +range = low \- high
 +.RS 4
 +Defines the available matching UID and GID range for which the backend is authoritative\&. Note that the range acts as a filter\&. If specified any UID or GID stored in AD that fall outside the range is ignored and the corresponding map is discarded\&. It is intended as a way to avoid accidental UID/GID overlaps between local and remotely defined IDs\&.
 +.RE
 +.PP
 +ldap_server = <ad | stand\-alone >
 +.RS 4
 +Defines the type of LDAP server to use\&. This can either be the LDAP server provided by the Active Directory server (ad) or a stand\-alone LDAP server\&.
 +.RE
 +.PP
 +bind_path_user
 +.RS 4
 +Specifies the bind path where user objects can be found in the LDAP server\&.
 +.RE
 +.PP
 +bind_path_group
 +.RS 4
 +Specifies the bind path where group objects can be found in the LDAP server\&.
 +.RE
 +.PP
 +user_cn = <yes | no>
 +.RS 4
 +Query cn attribute instead of uid attribute for the user name in LDAP\&. This option is not required, the default is no\&.
 +.RE
 +.PP
 +cn_realm = <yes | no>
 +.RS 4
 +Append @realm to cn for groups (and users if user_cn is set) in LDAP\&. This option is not required, the default is no\&.
 +.RE
 +.PP
 +ldap_domain
 +.RS 4
 +When using the LDAP server in the Active Directory server, this allows to specify the domain where to access the Active Directory server\&. This allows using trust relationships while keeping all RFC 2307 records in one place\&. This parameter is optional, the default is to access the AD server in the current domain to query LDAP records\&.
 +.RE
 +.PP
 +ldap_url
 +.RS 4
 +When using a stand\-alone LDAP server, this parameter specifies the ldap URL for accessing the LDAP server\&.
 +.RE
 +.PP
 +ldap_user_dn
 +.RS 4
 +Defines the user DN to be used for authentication\&. The secret for authenticating this user should be stored with net idmap secret (see
 +\fBnet\fR(8))\&. If absent, an anonymous bind will be performed\&.
 +.RE
 +.PP
 +ldap_realm
 +.RS 4
 +Defines the realm to use in the user and group names\&. This is only required when using cn_realm together with a stand\-alone ldap server\&.
 +.RE
 +.SH "EXAMPLES"
 +.PP
 +The following example shows how to retrieve id mappings from a stand\-alone LDAP server\&. This example also shows how to leave a small non conflicting range for local id allocation that may be used in internal backends like BUILTIN\&.
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	[global]
 +	idmap config * : backend = tdb
 +	idmap config * : range = 1000000\-1999999
 +
 +	idmap config DOMAIN : backend = rfc2307
 +	idmap config DOMAIN : range = 2000000\-2999999
 +	idmap config DOMAIN : ldap_server = stand\-alone
 +	idmap config DOMAIN : ldap_url = ldap://ldap1\&.example\&.com
 +	idmap config DOMAIN : ldap_user_dn = cn=ldapmanager,dc=example,dc=com
 +	idmap config DOMAIN : bind_path_user = ou=People,dc=example,dc=com
 +	idmap config DOMAIN : bind_path_group = ou=Group,dc=example,dc=com
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
diff --cc docs/manpages/idmap_rid.8
index de69fb8,0000000..d237661
mode 100644,000000..100644
--- a/docs/manpages/idmap_rid.8
+++ b/docs/manpages/idmap_rid.8
@@@ -1,113 -1,0 +1,113 @@@
 +'\" t
 +.\"     Title: idmap_rid
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: System Administration tools
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "IDMAP_RID" "8" "12/01/2015" "Samba 4\&.3" "System Administration tools"
++.TH "IDMAP_RID" "8" "12/10/2015" "Samba 4\&.3" "System Administration tools"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +idmap_rid \- Samba\*(Aqs idmap_rid Backend for Winbind
 +.SH "DESCRIPTION"
 +.PP
 +The idmap_rid backend provides a way to use an algorithmic mapping scheme to map UIDs/GIDs and SIDs\&. No database is required in this case as the mapping is deterministic\&.
 +.PP
 +Note that the idmap_rid module has changed considerably since Samba versions 3\&.0\&. and 3\&.2\&. Currently, there should to be an explicit idmap configuration for each domain that should use the idmap_rid backend, using disjoint ranges\&. One usually needs to define a writeable default idmap range, using a backend like
 +\fItdb\fR
 +or
 +\fIldap\fR
 +that can create unix ids, in order to be able to map the BUILTIN sids and other domains, and also in order to be able to create group mappings\&. See the example below\&.
 +.PP
 +Note that the old syntax
 +\fIidmap backend = rid:"DOM1=range DOM2=range2 \&.\&.\&."\fR
 +is not supported any more since Samba version 3\&.0\&.25\&.
 +.SH "IDMAP OPTIONS"
 +.PP
 +range = low \- high
 +.RS 4
 +Defines the available matching uid and gid range for which the backend is authoritative\&. Note that the range acts as a filter\&. If algorithmically determined UID or GID fall outside the range, they are ignored and the corresponding map is discarded\&. It is intended as a way to avoid accidental UID/GID overlaps between local and remotely defined IDs\&.
 +.RE
 +.PP
 +base_rid = INTEGER
 +.RS 4
 +Defines the base integer used to build SIDs out of a UID or a GID, and to rebase the UID or GID to be obtained from a SID\&. This means SIDs with a RID less than the base rid are filtered\&. The default is not to restrict the allowed rids at all, i\&.e\&. a base_rid value of 0\&.
 +.sp
 +Use of this parameter is deprecated\&.
 +.RE
 +.SH "THE MAPPING FORMULAS"
 +.PP
 +The Unix ID for a RID is calculated this way:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +			ID = RID \- BASE_RID + LOW_RANGE_ID\&.
 +		
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +Correspondingly, the formula for calculating the RID for a given Unix ID is this:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +			RID = ID + BASE_RID \- LOW_RANGE_ID\&.
 +		
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.sp
 +.SH "EXAMPLES"
 +.PP
 +This example shows how to configure two domains with idmap_rid, the principal domain and a trusted domain, leaving the default id mapping scheme at tdb\&. The example also demonstrates the use of the base_rid parameter for the trusted domain\&.
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	[global]
 +	security = domain
 +	workgroup = MAIN
 +
 +	idmap config * : backend        = tdb
 +	idmap config * : range          = 1000000\-1999999
 +
 +	idmap config MAIN : backend     = rid
 +	idmap config MAIN : range       = 10000 \- 49999
 +
 +	idmap config TRUSTED : backend  = rid
 +	idmap config TRUSTED : range    = 50000 \- 99999
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
diff --cc docs/manpages/idmap_script.8
index 0b5501e,0000000..c12d3a5
mode 100644,000000..100644
--- a/docs/manpages/idmap_script.8
+++ b/docs/manpages/idmap_script.8
@@@ -1,139 -1,0 +1,139 @@@
 +'\" t
 +.\"     Title: idmap_script
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: System Administration tools
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "IDMAP_SCRIPT" "8" "12/01/2015" "Samba 4\&.3" "System Administration tools"
++.TH "IDMAP_SCRIPT" "8" "12/10/2015" "Samba 4\&.3" "System Administration tools"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +idmap_script \- Samba\*(Aqs idmap_script Backend for Winbind
 +.SH "DESCRIPTION"
 +.PP
 +The idmap_script plugin is a substitute for the idmap_tdb2 backend used by winbindd for storing SID/uid/gid mapping tables in clustered environments with Samba and CTDB\&. It is a read only backend that uses a script to perform mapping\&.
 +.PP
 +It was developed out of the idmap_tdb2 back end and does not store SID/uid/gid mappings in a TDB, since the winbind_cache tdb will store the mappings once they are provided\&.
 +.SH "IDMAP OPTIONS"
 +.PP
 +range = low \- high
 +.RS 4
 +Defines the available matching uid and gid range for which the backend is authoritative\&.
 +.RE
 +.PP
 +script
 +.RS 4
 +This option can be used to configure an external program for performing id mappings\&.
 +.RE
 +.SH "IDMAP SCRIPT"
 +.PP
 +The tdb2 idmap backend supports an external program for performing id mappings through the smb\&.conf option
 +\fIidmap config * : script\fR
 +or its deprecated legacy form
 +\fIidmap : script\fR\&.
 +.PP
 +The mappings obtained by the script are then stored in the idmap tdb2 database instead of mappings created by the incrementing id counters\&. It is therefore important that the script covers the complete range of SIDs that can be passed in for SID to Unix ID mapping, since otherwise SIDs unmapped by the script might get mapped to IDs that had previously been mapped by the script\&.
 +.PP
 +The script should accept the following command line options\&.
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	SIDTOID S\-1\-xxxx
 +	IDTOSID UID xxxx
 +	IDTOSID GID xxxx
 +	IDTOSID XID xxxx
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +And it should return one of the following responses as a single line of text\&.
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	UID:yyyy
 +	GID:yyyy
 +	XID:yyyy
 +	SID:ssss
 +	ERR:yyyy
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +XID indicates that the ID returned should be both a UID and a GID\&. That is, it requests an ID_TYPE_BOTH, but it is ultimately up to the script whether or not it can honor that request\&. It can choose to return a UID or a GID mapping only\&.
 +.SH "EXAMPLES"
 +.PP
 +This example shows how script is used as a the default idmap backend using an external program via the script parameter:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	[global]
 +	idmap config * : backend = script
 +	idmap config * : range = 1000000\-2000000
 +	idmap config * : script = /usr/local/samba/bin/idmap_script\&.sh
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +This shows a simple script to partially perform the task:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	#!/bin/sh
 +	#
 +	# Uncomment this if you want some logging
 +	#echo $@ >> /tmp/idmap\&.sh\&.log
 +	if [ "$1" == "SIDTOID" ]
 +	then
 +		# Note\&. The number returned has to be within the range defined
 +		#echo "Sending UID:1000005" >> /tmp/idmap\&.sh\&.log
 +		echo "UID:1000005"
 +		exit 0
 +	else
 +		#echo "Sending ERR: No idea what to do" >> /tmp/idmap\&.sh\&.log
 +		echo "ERR: No idea what to do"
 +		exit 1
 +	fi
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +Clearly, this script is not enough, as it should probably use wbinfo to determine if an incoming SID is a user or group SID and then look up the mapping in a table or use some other mechanism for mapping SIDs to UIDs and etc\&.
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
diff --cc docs/manpages/idmap_tdb.8
index 3b78597,0000000..fcc907c
mode 100644,000000..100644
--- a/docs/manpages/idmap_tdb.8
+++ b/docs/manpages/idmap_tdb.8
@@@ -1,62 -1,0 +1,62 @@@
 +'\" t
 +.\"     Title: idmap_tdb
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: System Administration tools
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "IDMAP_TDB" "8" "12/01/2015" "Samba 4\&.3" "System Administration tools"
++.TH "IDMAP_TDB" "8" "12/10/2015" "Samba 4\&.3" "System Administration tools"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +idmap_tdb \- Samba\*(Aqs idmap_tdb Backend for Winbind
 +.SH "DESCRIPTION"
 +.PP
 +The idmap_tdb plugin is the default backend used by winbindd for storing SID/uid/gid mapping tables\&.
 +.PP
 +In contrast to read only backends like idmap_rid, it is an allocating backend: This means that it needs to allocate new user and group IDs in order to create new mappings\&.
 +.SH "IDMAP OPTIONS"
 +.PP
 +range = low \- high
 +.RS 4
 +Defines the available matching uid and gid range for which the backend is authoritative\&.
 +.RE
 +.SH "EXAMPLES"
 +.PP
 +This example shows how tdb is used as a the default idmap backend\&. This configured range is used for uid and gid allocation\&.
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	[global]
 +	# "backend = tdb" is redundant here since it is the default
 +	idmap config * : backend = tdb
 +	idmap config * : range = 1000000\-2000000
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
diff --cc docs/manpages/idmap_tdb2.8
index a990565,0000000..5a987e9
mode 100644,000000..100644
--- a/docs/manpages/idmap_tdb2.8
+++ b/docs/manpages/idmap_tdb2.8
@@@ -1,121 -1,0 +1,121 @@@
 +'\" t
 +.\"     Title: idmap_tdb2
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: System Administration tools
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "IDMAP_TDB2" "8" "12/01/2015" "Samba 4\&.3" "System Administration tools"
++.TH "IDMAP_TDB2" "8" "12/10/2015" "Samba 4\&.3" "System Administration tools"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +idmap_tdb2 \- Samba\*(Aqs idmap_tdb2 Backend for Winbind
 +.SH "DESCRIPTION"
 +.PP
 +The idmap_tdb2 plugin is a substitute for the default idmap_tdb backend used by winbindd for storing SID/uid/gid mapping tables in clustered environments with Samba and CTDB\&.
 +.PP
 +In contrast to read only backends like idmap_rid, it is an allocating backend: This means that it needs to allocate new user and group IDs in order to create new mappings\&.
 +.SH "IDMAP OPTIONS"
 +.PP
 +range = low \- high
 +.RS 4
 +Defines the available matching uid and gid range for which the backend is authoritative\&.
 +.RE
 +.PP
 +script
 +.RS 4
 +This option can be used to configure an external program for performing id mappings instead of using the tdb counter\&. The mappings are then stored int tdb2 idmap database\&. For details see the section on IDMAP SCRIPT below\&.
 +.RE
 +.SH "IDMAP SCRIPT"
 +.PP
 +The tdb2 idmap backend supports an external program for performing id mappings through the smb\&.conf option
 +\fIidmap config * : script\fR
 +or its deprecated legacy form
 +\fIidmap : script\fR\&.
 +.PP
 +The mappings obtained by the script are then stored in the idmap tdb2 database instead of mappings created by the incrementing id counters\&. It is therefore important that the script covers the complete range of SIDs that can be passed in for SID to Unix ID mapping, since otherwise SIDs unmapped by the script might get mapped to IDs that had previously been mapped by the script\&.
 +.PP
 +The script should accept the following command line options\&.
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	SIDTOID S\-1\-xxxx
 +	IDTOSID UID xxxx
 +	IDTOSID GID xxxx
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +And it should return one of the following responses as a single line of text\&.
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	UID:yyyy
 +	GID:yyyy
 +	SID:yyyy
 +	ERR:yyyy
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.SH "EXAMPLES"
 +.PP
 +This example shows how tdb2 is used as a the default idmap backend\&.
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	[global]
 +	idmap config * : backend = tdb2
 +	idmap config * : range = 1000000\-2000000
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +This example shows how tdb2 is used as a the default idmap backend using an external program via the script parameter:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	[global]
 +	idmap config * : backend = tdb2
 +	idmap config * : range = 1000000\-2000000
 +	idmap config * : script = /usr/local/samba/bin/idmap_script\&.sh
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
diff --cc docs/manpages/libsmbclient.7
index aa979b9,0000000..de44485
mode 100644,000000..100644
--- a/docs/manpages/libsmbclient.7
+++ b/docs/manpages/libsmbclient.7
@@@ -1,94 -1,0 +1,94 @@@
 +'\" t
 +.\"     Title: libsmbclient
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: 7
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "LIBSMBCLIENT" "7" "12/01/2015" "Samba 4\&.3" "7"
++.TH "LIBSMBCLIENT" "7" "12/10/2015" "Samba 4\&.3" "7"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +libsmbclient \- An extension library for browsers and that can be used as a generic browsing API\&.
 +.SH "SYNOPSIS"
 +.HP \w'\ 'u
 +.PP
 +Browser URL:
 +smb://[[[domain:]user[:password@]]server[/share[/path[/file]]]] [?options]
 +.SH "DESCRIPTION"
 +.PP
 +This tool is part of the
 +\fBsamba\fR(7)
 +suite\&.
 +.PP
 +libsmbclient
 +is a library toolset that permits applications to manipulate CIFS/SMB network resources using many of the standards POSIX functions available for manipulating local UNIX/Linux files\&. It permits much more than just browsing, files can be opened and read or written, permissions changed, file times modified, attributes and ACL\*(Aqs can be manipulated, and so on\&. Of course, its functionality includes all the capabilities commonly called browsing\&.
 +.PP
 +libsmbclient
 +can not be used directly from the command line, instead it provides an extension of the capabilities of tools such as file managers and browsers\&. This man page describes the configuration options for this tool so that the user may obtain greatest utility of use\&.
 +.SH "OPTIONS"
 +.PP
 +What the URLs mean:
 +.PP
 +smb://
 +.RS 4
 +Shows all workgroups or domains that are visible in the network\&. The behavior matches that of the Microsoft Windows Explorer\&.
 +.sp
 +The method of locating the list of workgroups (domains also) varies depending on the setting of the context variable
 +(context\->options\&.browse_max_lmb_count)\&. It is the responsibility of the application that calls this library to set this to a sensible value\&. This is a compile\-time option\&. This value determines the maximum number of local master browsers to query for the list of workgroups\&. In order to ensure that the list is complete for those present on the network, all master browsers must be queried\&. If there are a large number of workgroups on the network, the time spent querying wil [...]
 +.RE
 +.PP
 +smb://name/
 +.RS 4
 +This command causes libsmbclient to perform a name look\-up\&. If the NAME<1D> or NAME<1B> exists (workgroup name), libsmbclient will list all servers in the workgroup (or domain)\&. Otherwise, a name look\-up for the NAME<20> (machine name) will be performed, and the list of shared resources on the server will be displayed\&.
 +.RE
 +.PP
 +When libsmbclient is invoked by an application it searches for a directory called
 +\&.smb
 +in the $HOME directory that is specified in the users shell environment\&. It then searches for a file called
 +smb\&.conf
 +which, if present, will fully over\-ride the system
 +/etc/samba/smb\&.conf
 +file\&. If instead libsmbclient finds a file called
 +~/\&.smb/smb\&.conf\&.append, it will read the system
 +/etc/samba/smb\&.conf
 +and then append the contents of the
 +~/\&.smb/smb\&.conf\&.append
 +to it\&.
 +.PP
 +libsmbclient
 +will check the users shell environment for the
 +USER
 +parameter and will use its value when if the
 +user
 +parameter was not included in the URL\&.
 +.SH "PROGRAMMERS GUIDE"
 +.PP
 +Watch this space for future updates\&.
 +.SH "VERSION"
 +.PP
 +This man page is correct for version 3 of the Samba suite\&.
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
 +.PP
 +The libsmbclient manpage page was written by John H Terpstra\&.
diff --cc docs/manpages/lmhosts.5
index eb238ee,0000000..4152621
mode 100644,000000..100644
--- a/docs/manpages/lmhosts.5
+++ b/docs/manpages/lmhosts.5
@@@ -1,125 -1,0 +1,125 @@@
 +'\" t
 +.\"     Title: lmhosts
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: File Formats and Conventions
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "LMHOSTS" "5" "12/01/2015" "Samba 4\&.3" "File Formats and Conventions"
++.TH "LMHOSTS" "5" "12/10/2015" "Samba 4\&.3" "File Formats and Conventions"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +lmhosts \- The Samba NetBIOS hosts file
 +.SH "SYNOPSIS"
 +.PP
 +lmhosts
 +is the
 +\fBsamba\fR(7)
 +NetBIOS name to IP address mapping file\&.
 +.SH "DESCRIPTION"
 +.PP
 +This file is part of the
 +\fBsamba\fR(7)
 +suite\&.
 +.PP
 +lmhosts
 +is the
 +\fISamba \fR
 +NetBIOS name to IP address mapping file\&. It is very similar to the
 +/etc/hosts
 +file format, except that the hostname component must correspond to the NetBIOS naming format\&.
 +.SH "FILE FORMAT"
 +.PP
 +It is an ASCII file containing one line for NetBIOS name\&. The two fields on each line are separated from each other by white space\&. Any entry beginning with \*(Aq#\*(Aq is ignored\&. Each line in the lmhosts file contains the following information:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +IP Address \- in dotted decimal format\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +NetBIOS Name \- This name format is a maximum fifteen character host name, with an optional trailing \*(Aq#\*(Aq character followed by the NetBIOS name type as two hexadecimal digits\&.
 +.sp
 +If the trailing \*(Aq#\*(Aq is omitted then the given IP address will be returned for all names that match the given name, whatever the NetBIOS name type in the lookup\&.
 +.RE
 +.sp
 +.RE
 +.PP
 +An example follows:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +#
 +# Sample Samba lmhosts file\&.
 +#
 +192\&.9\&.200\&.1	TESTPC
 +192\&.9\&.200\&.20	NTSERVER#20
 +192\&.9\&.200\&.21	SAMBASERVER
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +Contains three IP to NetBIOS name mappings\&. The first and third will be returned for any queries for the names "TESTPC" and "SAMBASERVER" respectively, whatever the type component of the NetBIOS name requested\&.
 +.PP
 +The second mapping will be returned only when the "0x20" name type for a name "NTSERVER" is queried\&. Any other name type will not be resolved\&.
 +.PP
 +The default location of the
 +lmhosts
 +file is in the same directory as the
 +\fBsmb.conf\fR(5)
 +file\&.
 +.SH "FILES"
 +.PP
 +lmhosts is loaded from the configuration directory\&. This is usually
 +/etc/samba
 +or
 +/usr/local/samba/lib\&.
 +.SH "VERSION"
 +.PP
 +This man page is correct for version 3 of the Samba suite\&.
 +.SH "SEE ALSO"
 +.PP
 +\fBsmbclient\fR(1),
 +\fBsmb.conf\fR(5), and
 +\fBsmbpasswd\fR(8)
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
 +.PP
 +The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at
 +ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 was done by Alexander Bokovoy\&.
diff --cc docs/manpages/log2pcap.1
index 8417b6f,0000000..0033027
mode 100644,000000..100644
--- a/docs/manpages/log2pcap.1
+++ b/docs/manpages/log2pcap.1
@@@ -1,124 -1,0 +1,124 @@@
 +'\" t
 +.\"     Title: log2pcap
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: User Commands
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "LOG2PCAP" "1" "12/01/2015" "Samba 4\&.3" "User Commands"
++.TH "LOG2PCAP" "1" "12/10/2015" "Samba 4\&.3" "User Commands"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +log2pcap \- Extract network traces from Samba log files
 +.SH "SYNOPSIS"
 +.HP \w'\ 'u
 +log2pcap [\-h] [\-q] [logfile] [pcap_file]
 +.SH "DESCRIPTION"
 +.PP
 +This tool is part of the
 +\fBsamba\fR(7)
 +suite\&.
 +.PP
 +log2pcap
 +reads in a samba log file and generates a pcap file (readable by most sniffers, such as ethereal or tcpdump) based on the packet dumps in the log file\&.
 +.PP
 +The log file must have a
 +\fIlog level\fR
 +of at least
 +\fB5\fR
 +to get the SMB header/parameters right,
 +\fB10\fR
 +to get the first 512 data bytes of the packet and
 +\fB50\fR
 +to get the whole packet\&.
 +.SH "OPTIONS"
 +.PP
 +\-h
 +.RS 4
 +If this parameter is specified the output file will be a hex dump, in a format that is readable by the
 +text2pcap
 +utility\&.
 +.RE
 +.PP
 +\-q
 +.RS 4
 +Be quiet\&. No warning messages about missing or incomplete data will be given\&.
 +.RE
 +.PP
 +logfile
 +.RS 4
 +Samba log file\&. log2pcap will try to read the log from stdin if the log file is not specified\&.
 +.RE
 +.PP
 +pcap_file
 +.RS 4
 +Name of the output file to write the pcap (or hexdump) data to\&. If this argument is not specified, output data will be written to stdout\&.
 +.RE
 +.PP
 +\-?|\-\-help
 +.RS 4
 +Print a summary of command line options\&.
 +.RE
 +.SH "EXAMPLES"
 +.PP
 +Extract all network traffic from all samba log files:
 +.PP
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +			$ log2pcap < /var/log/* > trace\&.pcap
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +Convert to pcap using text2pcap:
 +.PP
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	$ log2pcap \-h samba\&.log | text2pcap \-T 139,139 \- trace\&.pcap
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.SH "VERSION"
 +.PP
 +This man page is correct for version 3 of the Samba suite\&.
 +.SH "BUGS"
 +.PP
 +Only SMB data is extracted from the samba logs, no LDAP, NetBIOS lookup or other data\&.
 +.PP
 +The generated TCP and IP headers don\*(Aqt contain a valid checksum\&.
 +.SH "SEE ALSO"
 +.PP
 +\fBtext2pcap\fR(1),
 +\fBethereal\fR(1)
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
 +.PP
 +This manpage was written by Jelmer Vernooij\&.
diff --cc docs/manpages/net.8
index 93031ae,0000000..c483d78
mode 100644,000000..100644
--- a/docs/manpages/net.8
+++ b/docs/manpages/net.8
@@@ -1,1927 -1,0 +1,1927 @@@
 +'\" t
 +.\"     Title: net
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: System Administration tools
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "NET" "8" "12/01/2015" "Samba 4\&.3" "System Administration tools"
++.TH "NET" "8" "12/10/2015" "Samba 4\&.3" "System Administration tools"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +net \- Tool for administration of Samba and remote CIFS servers\&.
 +.SH "SYNOPSIS"
 +.HP \w'\ 'u
 +net {<ads|rap|rpc>} [\-h|\-\-help] [\-w|\-\-workgroup\ workgroup] [\-W|\-\-myworkgroup\ myworkgroup] [\-U|\-\-user\ user] [\-I|\-\-ipaddress\ ip\-address] [\-p|\-\-port\ port] [\-n\ myname] [\-s\ conffile] [\-S|\-\-server\ server] [\-l|\-\-long] [\-v|\-\-verbose] [\-f|\-\-force] [\-P|\-\-machine\-pass] [\-d\ debuglevel] [\-V] [\-\-request\-timeout\ seconds] [\-t|\-\-timeout\ seconds] [\-i|\-\-stdin] [\-\-tallocreport]
 +.SH "DESCRIPTION"
 +.PP
 +This tool is part of the
 +\fBsamba\fR(7)
 +suite\&.
 +.PP
 +The Samba net utility is meant to work just like the net utility available for windows and DOS\&. The first argument should be used to specify the protocol to use when executing a certain command\&. ADS is used for ActiveDirectory, RAP is using for old (Win9x/NT3) clients and RPC can be used for NT4 and Windows 2000\&. If this argument is omitted, net will try to determine it automatically\&. Not all commands are available on all protocols\&.
 +.SH "OPTIONS"
 +.PP
 +\-?|\-\-help
 +.RS 4
 +Print a summary of command line options\&.
 +.RE
 +.PP
 +\-k|\-\-kerberos
 +.RS 4
 +Try to authenticate with kerberos\&. Only useful in an Active Directory environment\&.
 +.RE
 +.PP
 +\-w|\-\-workgroup target\-workgroup
 +.RS 4
 +Sets target workgroup or domain\&. You have to specify either this option or the IP address or the name of a server\&.
 +.RE
 +.PP
 +\-W|\-\-myworkgroup workgroup
 +.RS 4
 +Sets client workgroup or domain
 +.RE
 +.PP
 +\-U|\-\-user user
 +.RS 4
 +User name to use
 +.RE
 +.PP
 +\-I|\-\-ipaddress ip\-address
 +.RS 4
 +IP address of target server to use\&. You have to specify either this option or a target workgroup or a target server\&.
 +.RE
 +.PP
 +\-p|\-\-port port
 +.RS 4
 +Port on the target server to connect to (usually 139 or 445)\&. Defaults to trying 445 first, then 139\&.
 +.RE
 +.PP
 +\-n|\-\-netbiosname <primary NetBIOS name>
 +.RS 4
 +This option allows you to override the NetBIOS name that Samba uses for itself\&. This is identical to setting the
 +\m[blue]\fBnetbios name\fR\m[]
 +parameter in the
 +smb\&.conf
 +file\&. However, a command line setting will take precedence over settings in
 +smb\&.conf\&.
 +.RE
 +.PP
 +\-s|\-\-configfile=<configuration file>
 +.RS 4
 +The file specified contains the configuration details required by the server\&. The information in this file includes server\-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See
 +smb\&.conf
 +for more information\&. The default configuration file name is determined at compile time\&.
 +.RE
 +.PP
 +\-S|\-\-server server
 +.RS 4
 +Name of target server\&. You should specify either this option or a target workgroup or a target IP address\&.
 +.RE
 +.PP
 +\-l|\-\-long
 +.RS 4
 +When listing data, give more information on each item\&.
 +.RE
 +.PP
 +\-v|\-\-verbose
 +.RS 4
 +When listing data, give more verbose information on each item\&.
 +.RE
 +.PP
 +\-f|\-\-force
 +.RS 4
 +Enforcing a net command\&.
 +.RE
 +.PP
 +\-P|\-\-machine\-pass
 +.RS 4
 +Make queries to the external server using the machine account of the local server\&.
 +.RE
 +.PP
 +\-\-request\-timeout 30
 +.RS 4
 +Let client requests timeout after 30 seconds the default is 10 seconds\&.
 +.RE
 +.PP
 +\-t|\-\-timeout 30
 +.RS 4
 +Set timeout for client operations to 30 seconds\&.
 +.RE
 +.PP
 +\-\-use\-ccache
 +.RS 4
 +Try to use the credentials cached by winbind\&.
 +.RE
 +.PP
 +\-i|\-\-stdin
 +.RS 4
 +Take input for net commands from standard input\&.
 +.RE
 +.PP
 +\-\-tallocreport
 +.RS 4
 +Generate a talloc report while processing a net command\&.
 +.RE
 +.PP
 +\-T|\-\-test
 +.RS 4
 +Only test command sequence, dry\-run\&.
 +.RE
 +.PP
 +\-F|\-\-flags FLAGS
 +.RS 4
 +Pass down integer flags to a net subcommand\&.
 +.RE
 +.PP
 +\-C|\-\-comment COMMENT
 +.RS 4
 +Pass down a comment string to a net subcommand\&.
 +.RE
 +.PP
 +\-n|\-\-myname MYNAME
 +.RS 4
 +Use MYNAME as a requester name for a net subcommand\&.
 +.RE
 +.PP
 +\-c|\-\-container CONTAINER
 +.RS 4
 +Use a specific AD container for net ads operations\&.
 +.RE
 +.PP
 +\-M|\-\-maxusers MAXUSERS
 +.RS 4
 +Fill in the maxusers field in net rpc share operations\&.
 +.RE
 +.PP
 +\-r|\-\-reboot
 +.RS 4
 +Reboot a remote machine after a command has been successfully executed (e\&.g\&. in remote join operations)\&.
 +.RE
 +.PP
 +\-\-force\-full\-repl
 +.RS 4
 +When calling "net rpc vampire keytab" this option enforces a full re\-creation of the generated keytab file\&.
 +.RE
 +.PP
 +\-\-single\-obj\-repl
 +.RS 4
 +When calling "net rpc vampire keytab" this option allows to replicate just a single object to the generated keytab file\&.
 +.RE
 +.PP
 +\-\-clean\-old\-entries
 +.RS 4
 +When calling "net rpc vampire keytab" this option allows to cleanup old entries from the generated keytab file\&.
 +.RE
 +.PP
 +\-\-db
 +.RS 4
 +Define dbfile for "net idmap" commands\&.
 +.RE
 +.PP
 +\-\-lock
 +.RS 4
 +Activates locking of the dbfile for "net idmap check" command\&.
 +.RE
 +.PP
 +\-a|\-\-auto
 +.RS 4
 +Activates noninteractive mode in "net idmap check"\&.
 +.RE
 +.PP
 +\-\-repair
 +.RS 4
 +Activates repair mode in "net idmap check"\&.
 +.RE
 +.PP
 +\-\-acls
 +.RS 4
 +Includes ACLs to be copied in "net rpc share migrate"\&.
 +.RE
 +.PP
 +\-\-attrs
 +.RS 4
 +Includes file attributes to be copied in "net rpc share migrate"\&.
 +.RE
 +.PP
 +\-\-timestamps
 +.RS 4
 +Includes timestamps to be copied in "net rpc share migrate"\&.
 +.RE
 +.PP
 +\-X|\-\-exclude DIRECTORY
 +.RS 4
 +Allows to exclude directories when copying with "net rpc share migrate"\&.
 +.RE
 +.PP
 +\-\-destination SERVERNAME
 +.RS 4
 +Defines the target servername of migration process (defaults to localhost)\&.
 +.RE
 +.PP
 +\-L|\-\-local
 +.RS 4
 +Sets the type of group mapping to local (used in "net groupmap set")\&.
 +.RE
 +.PP
 +\-D|\-\-domain
 +.RS 4
 +Sets the type of group mapping to domain (used in "net groupmap set")\&.
 +.RE
 +.PP
 +\-N|\-\-ntname NTNAME
 +.RS 4
 +Sets the ntname of a group mapping (used in "net groupmap set")\&.
 +.RE
 +.PP
 +\-R|\-\-rid RID
 +.RS 4
 +Sets the rid of a group mapping (used in "net groupmap set")\&.
 +.RE
 +.PP
 +\-\-reg\-version REG_VERSION
 +.RS 4
 +Assume database version {n|1,2,3} (used in "net registry check")\&.
 +.RE
 +.PP
 +\-o|\-\-output FILENAME
 +.RS 4
 +Output database file (used in "net registry check")\&.
 +.RE
 +.PP
 +\-\-wipe
 +.RS 4
 +Create a new database from scratch (used in "net registry check")\&.
 +.RE
 +.PP
 +\-\-precheck PRECHECK_DB_FILENAME
 +.RS 4
 +Defines filename for database prechecking (used in "net registry import")\&.
 +.RE
 +.PP
 +\-e|\-\-encrypt
 +.RS 4
 +This command line parameter requires the remote server support the UNIX extensions or that the SMB3 protocol has been selected\&. Requests that the connection be encrypted\&. Negotiates SMB encryption using either SMB3 or POSIX extensions via GSSAPI\&. Uses the given credentials for the encryption negotiation (either kerberos or NTLMv1/v2 if given domain/username/password triple\&. Fails the connection if encryption cannot be negotiated\&.
 +.RE
 +.PP
 +\-d|\-\-debuglevel=level
 +.RS 4
 +\fIlevel\fR
 +is an integer from 0 to 10\&. The default value if this parameter is not specified is 1\&.
 +.sp
 +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day\-to\-day running \- it generates a small amount of information about operations carried out\&.
 +.sp
 +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&.
 +.sp
 +Note that specifying this parameter here will override the
 +\m[blue]\fBlog level\fR\m[]
 +parameter in the
 +smb\&.conf
 +file\&.
 +.RE
 +.PP
 +\-V|\-\-version
 +.RS 4
 +Prints the program version number\&.
 +.RE
 +.PP
 +\-s|\-\-configfile=<configuration file>
 +.RS 4
 +The file specified contains the configuration details required by the server\&. The information in this file includes server\-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See
 +smb\&.conf
 +for more information\&. The default configuration file name is determined at compile time\&.
 +.RE
 +.PP
 +\-l|\-\-log\-basename=logdirectory
 +.RS 4
 +Base directory name for log/debug files\&. The extension
 +\fB"\&.progname"\fR
 +will be appended (e\&.g\&. log\&.smbclient, log\&.smbd, etc\&.\&.\&.)\&. The log file is never removed by the client\&.
 +.RE
 +.PP
 +\-\-option=<name>=<value>
 +.RS 4
 +Set the
 +\fBsmb.conf\fR(5)
 +option "<name>" to value "<value>" from the command line\&. This overrides compiled\-in defaults and options read from the configuration file\&.
 +.RE
 +.SH "COMMANDS"
 +.SS "CHANGESECRETPW"
 +.PP
 +This command allows the Samba machine account password to be set from an external application to a machine account password that has already been stored in Active Directory\&. DO NOT USE this command unless you know exactly what you are doing\&. The use of this command requires that the force flag (\-f) be used also\&. There will be NO command prompt\&. Whatever information is piped into stdin, either by typing at the command line or otherwise, will be stored as the literal machine pass [...]
 +.SS "TIME"
 +.PP
 +The
 +NET TIME
 +command allows you to view the time on a remote server or synchronise the time on the local server with the time on the remote server\&.
 +.SS "TIME"
 +.PP
 +Without any options, the
 +NET TIME
 +command displays the time on the remote server\&. The remote server must be specified with the \-S option\&.
 +.SS "TIME SYSTEM"
 +.PP
 +Displays the time on the remote server in a format ready for
 +/bin/date\&. The remote server must be specified with the \-S option\&.
 +.SS "TIME SET"
 +.PP
 +Tries to set the date and time of the local server to that on the remote server using
 +/bin/date\&. The remote server must be specified with the \-S option\&.
 +.SS "TIME ZONE"
 +.PP
 +Displays the timezone in hours from GMT on the remote server\&. The remote server must be specified with the \-S option\&.
 +.SS "[RPC|ADS] JOIN [TYPE] [\-U username[%password]] [createupn=UPN] [createcomputer=OU] [machinepass=PASS] [osName=string osVer=string] [options]"
 +.PP
 +Join a domain\&. If the account already exists on the server, and [TYPE] is MEMBER, the machine will attempt to join automatically\&. (Assuming that the machine has been created in server manager) Otherwise, a password will be prompted for, and a new account may be created\&.
 +.PP
 +[TYPE] may be PDC, BDC or MEMBER to specify the type of server joining the domain\&.
 +.PP
 +[UPN] (ADS only) set the principalname attribute during the join\&. The default format is host/netbiosname at REALM\&.
 +.PP
 +[OU] (ADS only) Precreate the computer account in a specific OU\&. The OU string reads from top to bottom without RDNs, and is delimited by a \*(Aq/\*(Aq\&. Please note that \*(Aq\e\*(Aq is used for escape by both the shell and ldap, so it may need to be doubled or quadrupled to pass through, and it is not used as a delimiter\&.
 +.PP
 +[PASS] (ADS only) Set a specific password on the computer account being created by the join\&.
 +.PP
 +[osName=string osVer=String] (ADS only) Set the operatingSystem and operatingSystemVersion attribute during the join\&. Both parameters must be specified for either to take effect\&.
 +.SS "[RPC] OLDJOIN [options]"
 +.PP
 +Join a domain\&. Use the OLDJOIN option to join the domain using the old style of domain joining \- you need to create a trust account in server manager first\&.
 +.SS "[RPC|ADS] USER"
 +.SS "[RPC|ADS] USER"
 +.PP
 +List all users
 +.SS "[RPC|ADS] USER DELETE target"
 +.PP
 +Delete specified user
 +.SS "[RPC|ADS] USER INFO target"
 +.PP
 +List the domain groups of the specified user\&.
 +.SS "[RPC|ADS] USER RENAME oldname newname"
 +.PP
 +Rename specified user\&.
 +.SS "[RPC|ADS] USER ADD name [password] [-F user flags] [-C comment]"
 +.PP
 +Add specified user\&.
 +.SS "[RPC|ADS] GROUP"
 +.SS "[RPC|ADS] GROUP [misc options] [targets]"
 +.PP
 +List user groups\&.
 +.SS "[RPC|ADS] GROUP DELETE name [misc. options]"
 +.PP
 +Delete specified group\&.
 +.SS "[RPC|ADS] GROUP ADD name [-C comment]"
 +.PP
 +Create specified group\&.
 +.SS "[RAP|RPC] SHARE"
 +.SS "[RAP|RPC] SHARE [misc. options] [targets]"
 +.PP
 +Enumerates all exported resources (network shares) on target server\&.
 +.SS "[RAP|RPC] SHARE ADD name=serverpath [-C comment] [-M maxusers] [targets]"
 +.PP
 +Adds a share from a server (makes the export active)\&. Maxusers specifies the number of users that can be connected to the share simultaneously\&.
 +.SS "SHARE DELETE sharename"
 +.PP
 +Delete specified share\&.
 +.SS "[RPC|RAP] FILE"
 +.SS "[RPC|RAP] FILE"
 +.PP
 +List all open files on remote server\&.
 +.SS "[RPC|RAP] FILE CLOSE fileid"
 +.PP
 +Close file with specified
 +\fIfileid\fR
 +on remote server\&.
 +.SS "[RPC|RAP] FILE INFO fileid"
 +.PP
 +Print information on specified
 +\fIfileid\fR\&. Currently listed are: file\-id, username, locks, path, permissions\&.
 +.SS "[RAP|RPC] FILE USER user"
 +.PP
 +List files opened by specified
 +\fIuser\fR\&. Please note that
 +net rap file user
 +does not work against Samba servers\&.
 +.SS "SESSION"
 +.SS "RAP SESSION"
 +.PP
 +Without any other options, SESSION enumerates all active SMB/CIFS sessions on the target server\&.
 +.SS "RAP SESSION DELETE|CLOSE CLIENT_NAME"
 +.PP
 +Close the specified sessions\&.
 +.SS "RAP SESSION INFO CLIENT_NAME"
 +.PP
 +Give a list with all the open files in specified session\&.
 +.SS "RAP SERVER \fIDOMAIN\fR"
 +.PP
 +List all servers in specified domain or workgroup\&. Defaults to local domain\&.
 +.SS "RAP DOMAIN"
 +.PP
 +Lists all domains and workgroups visible on the current network\&.
 +.SS "RAP PRINTQ"
 +.SS "RAP PRINTQ INFO QUEUE_NAME"
 +.PP
 +Lists the specified print queue and print jobs on the server\&. If the
 +\fIQUEUE_NAME\fR
 +is omitted, all queues are listed\&.
 +.SS "RAP PRINTQ DELETE JOBID"
 +.PP
 +Delete job with specified id\&.
 +.SS "RAP VALIDATE \fIuser\fR [\fIpassword\fR]"
 +.PP
 +Validate whether the specified user can log in to the remote server\&. If the password is not specified on the commandline, it will be prompted\&.
 +.if n \{\
 +.sp
 +.\}
 +.RS 4
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBNote\fR
 +.ps -1
 +.br
 +.PP
 +Currently NOT implemented\&.
 +.sp .5v
 +.RE
 +.SS "RAP GROUPMEMBER"
 +.SS "RAP GROUPMEMBER LIST GROUP"
 +.PP
 +List all members of the specified group\&.
 +.SS "RAP GROUPMEMBER DELETE GROUP USER"
 +.PP
 +Delete member from group\&.
 +.SS "RAP GROUPMEMBER ADD GROUP USER"
 +.PP
 +Add member to group\&.
 +.SS "RAP ADMIN \fIcommand\fR"
 +.PP
 +Execute the specified
 +\fIcommand\fR
 +on the remote server\&. Only works with OS/2 servers\&.
 +.if n \{\
 +.sp
 +.\}
 +.RS 4
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBNote\fR
 +.ps -1
 +.br
 +.PP
 +Currently NOT implemented\&.
 +.sp .5v
 +.RE
 +.SS "RAP SERVICE"
 +.SS "RAP SERVICE START NAME [arguments...]"
 +.PP
 +Start the specified service on the remote server\&. Not implemented yet\&.
 +.if n \{\
 +.sp
 +.\}
 +.RS 4
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBNote\fR
 +.ps -1
 +.br
 +.PP
 +Currently NOT implemented\&.
 +.sp .5v
 +.RE
 +.SS "RAP SERVICE STOP"
 +.PP
 +Stop the specified service on the remote server\&.
 +.if n \{\
 +.sp
 +.\}
 +.RS 4
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBNote\fR
 +.ps -1
 +.br
 +.PP
 +Currently NOT implemented\&.
 +.sp .5v
 +.RE
 +.SS "RAP PASSWORD \fIUSER\fR \fIOLDPASS\fR \fINEWPASS\fR"
 +.PP
 +Change password of
 +\fIUSER\fR
 +from
 +\fIOLDPASS\fR
 +to
 +\fINEWPASS\fR\&.
 +.SS "LOOKUP"
 +.SS "LOOKUP HOST HOSTNAME [TYPE]"
 +.PP
 +Lookup the IP address of the given host with the specified type (netbios suffix)\&. The type defaults to 0x20 (workstation)\&.
 +.SS "LOOKUP LDAP [DOMAIN]"
 +.PP
 +Give IP address of LDAP server of specified
 +\fIDOMAIN\fR\&. Defaults to local domain\&.
 +.SS "LOOKUP KDC [REALM]"
 +.PP
 +Give IP address of KDC for the specified
 +\fIREALM\fR\&. Defaults to local realm\&.
 +.SS "LOOKUP DC [DOMAIN]"
 +.PP
 +Give IP\*(Aqs of Domain Controllers for specified
 +\fI DOMAIN\fR\&. Defaults to local domain\&.
 +.SS "LOOKUP MASTER DOMAIN"
 +.PP
 +Give IP of master browser for specified
 +\fIDOMAIN\fR
 +or workgroup\&. Defaults to local domain\&.
 +.SS "CACHE"
 +.PP
 +Samba uses a general caching interface called \*(Aqgencache\*(Aq\&. It can be controlled using \*(AqNET CACHE\*(Aq\&.
 +.PP
 +All the timeout parameters support the suffixes:
 +.RS 4
 +s \- Seconds
 +.RE
 +.RS 4
 +m \- Minutes
 +.RE
 +.RS 4
 +h \- Hours
 +.RE
 +.RS 4
 +d \- Days
 +.RE
 +.RS 4
 +w \- Weeks
 +.RE
 +.SS "CACHE ADD key data time-out"
 +.PP
 +Add specified key+data to the cache with the given timeout\&.
 +.SS "CACHE DEL key"
 +.PP
 +Delete key from the cache\&.
 +.SS "CACHE SET key data time-out"
 +.PP
 +Update data of existing cache entry\&.
 +.SS "CACHE SEARCH PATTERN"
 +.PP
 +Search for the specified pattern in the cache data\&.
 +.SS "CACHE LIST"
 +.PP
 +List all current items in the cache\&.
 +.SS "CACHE FLUSH"
 +.PP
 +Remove all the current items from the cache\&.
 +.SS "GETLOCALSID [DOMAIN]"
 +.PP
 +Prints the SID of the specified domain, or if the parameter is omitted, the SID of the local server\&.
 +.SS "SETLOCALSID S\-1\-5\-21\-x\-y\-z"
 +.PP
 +Sets SID for the local server to the specified SID\&.
 +.SS "GETDOMAINSID"
 +.PP
 +Prints the local machine SID and the SID of the current domain\&.
 +.SS "SETDOMAINSID"
 +.PP
 +Sets the SID of the current domain\&.
 +.SS "GROUPMAP"
 +.PP
 +Manage the mappings between Windows group SIDs and UNIX groups\&. Common options include:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +unixgroup \- Name of the UNIX group
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +ntgroup \- Name of the Windows NT group (must be resolvable to a SID
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +rid \- Unsigned 32\-bit integer
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +sid \- Full SID in the form of "S\-1\-\&.\&.\&."
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +type \- Type of the group; either \*(Aqdomain\*(Aq, \*(Aqlocal\*(Aq, or \*(Aqbuiltin\*(Aq
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +comment \- Freeform text description of the group
 +.RE
 +.sp
 +.RE
 +.SS "GROUPMAP ADD"
 +.PP
 +Add a new group mapping entry:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +net groupmap add {rid=int|sid=string} unixgroup=string \e
 +	[type={domain|local}] [ntgroup=string] [comment=string]
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.sp
 +
 +.SS "GROUPMAP DELETE"
 +.PP
 +Delete a group mapping entry\&. If more than one group name matches, the first entry found is deleted\&.
 +.PP
 +net groupmap delete {ntgroup=string|sid=SID}
 +.SS "GROUPMAP MODIFY"
 +.PP
 +Update an existing group entry\&.
 +.PP
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +net groupmap modify {ntgroup=string|sid=SID} [unixgroup=string] \e
 +       [comment=string] [type={domain|local}]
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.sp
 +
 +.SS "GROUPMAP LIST"
 +.PP
 +List existing group mapping entries\&.
 +.PP
 +net groupmap list [verbose] [ntgroup=string] [sid=SID]
 +.SS "MAXRID"
 +.PP
 +Prints out the highest RID currently in use on the local server (by the active \*(Aqpassdb backend\*(Aq)\&.
 +.SS "RPC INFO"
 +.PP
 +Print information about the domain of the remote server, such as domain name, domain sid and number of users and groups\&.
 +.SS "[RPC|ADS] TESTJOIN"
 +.PP
 +Check whether participation in a domain is still valid\&.
 +.SS "[RPC|ADS] CHANGETRUSTPW"
 +.PP
 +Force change of domain trust password\&.
 +.SS "RPC TRUSTDOM"
 +.SS "RPC TRUSTDOM ADD DOMAIN"
 +.PP
 +Add a interdomain trust account for
 +\fIDOMAIN\fR\&. This is in fact a Samba account named
 +\fIDOMAIN$\fR
 +with the account flag
 +\fB\*(AqI\*(Aq\fR
 +(interdomain trust account)\&. This is required for incoming trusts to work\&. It makes Samba be a trusted domain of the foreign (trusting) domain\&. Users of the Samba domain will be made available in the foreign domain\&. If the command is used against localhost it has the same effect as
 +smbpasswd \-a \-i DOMAIN\&. Please note that both commands expect a appropriate UNIX account\&.
 +.SS "RPC TRUSTDOM DEL DOMAIN"
 +.PP
 +Remove interdomain trust account for
 +\fIDOMAIN\fR\&. If it is used against localhost it has the same effect as
 +smbpasswd \-x DOMAIN$\&.
 +.SS "RPC TRUSTDOM ESTABLISH DOMAIN"
 +.PP
 +Establish a trust relationship to a trusted domain\&. Interdomain account must already be created on the remote PDC\&. This is required for outgoing trusts to work\&. It makes Samba be a trusting domain of a foreign (trusted) domain\&. Users of the foreign domain will be made available in our domain\&. You\*(Aqll need winbind and a working idmap config to make them appear in your system\&.
 +.SS "RPC TRUSTDOM REVOKE DOMAIN"
 +.PP
 +Abandon relationship to trusted domain
 +.SS "RPC TRUSTDOM LIST"
 +.PP
 +List all interdomain trust relationships\&.
 +.SS "RPC TRUST"
 +.SS "RPC TRUST CREATE"
 +.PP
 +Create a trust object by calling lsaCreateTrustedDomainEx2\&. The can be done on a single server or on two servers at once with the possibility to use a random trust password\&.
 +.PP
 +\fBOptions:\fR
 +.PP
 +otherserver
 +.RS 4
 +Domain controller of the second domain
 +.RE
 +.PP
 +otheruser
 +.RS 4
 +Admin user in the second domain
 +.RE
 +.PP
 +otherdomainsid
 +.RS 4
 +SID of the second domain
 +.RE
 +.PP
 +other_netbios_domain
 +.RS 4
 +NetBIOS (short) name of the second domain
 +.RE
 +.PP
 +otherdomain
 +.RS 4
 +DNS (full) name of the second domain
 +.RE
 +.PP
 +trustpw
 +.RS 4
 +Trust password
 +.RE
 +.PP
 +\fBExamples:\fR
 +.PP
 +Create a trust object on srv1\&.dom1\&.dom for the domain dom2
 +.RS 4
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +net rpc trust create \e
 +    otherdomainsid=S\-x\-x\-xx\-xxxxxxxxxx\-xxxxxxxxxx\-xxxxxxxxx \e
 +    other_netbios_domain=dom2 \e
 +    otherdomain=dom2\&.dom \e
 +    trustpw=12345678 \e
 +    \-S srv1\&.dom1\&.dom
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.PP
 +Create a trust relationship between dom1 and dom2
 +.RS 4
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +net rpc trust create \e
 +    otherserver=srv2\&.dom2\&.test \e
 +    otheruser=dom2adm \e
 +    \-S srv1\&.dom1\&.dom
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.SS "RPC TRUST DELETE"
 +.PP
 +Delete a trust object by calling lsaDeleteTrustedDomain\&. The can be done on a single server or on two servers at once\&.
 +.PP
 +\fBOptions:\fR
 +.PP
 +otherserver
 +.RS 4
 +Domain controller of the second domain
 +.RE
 +.PP
 +otheruser
 +.RS 4
 +Admin user in the second domain
 +.RE
 +.PP
 +otherdomainsid
 +.RS 4
 +SID of the second domain
 +.RE
 +.PP
 +\fBExamples:\fR
 +.PP
 +Delete a trust object on srv1\&.dom1\&.dom for the domain dom2
 +.RS 4
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +net rpc trust delete \e
 +    otherdomainsid=S\-x\-x\-xx\-xxxxxxxxxx\-xxxxxxxxxx\-xxxxxxxxx \e
 +    \-S srv1\&.dom1\&.dom
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.PP
 +Delete a trust relationship between dom1 and dom2
 +.RS 4
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +net rpc trust delete \e
 +    otherserver=srv2\&.dom2\&.test \e
 +    otheruser=dom2adm \e
 +    \-S srv1\&.dom1\&.dom
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.SS ""
 +.SS "RPC RIGHTS"
 +.PP
 +This subcommand is used to view and manage Samba\*(Aqs rights assignments (also referred to as privileges)\&. There are three options currently available:
 +\fIlist\fR,
 +\fIgrant\fR, and
 +\fIrevoke\fR\&. More details on Samba\*(Aqs privilege model and its use can be found in the Samba\-HOWTO\-Collection\&.
 +.SS "RPC ABORTSHUTDOWN"
 +.PP
 +Abort the shutdown of a remote server\&.
 +.SS "RPC SHUTDOWN [\-t timeout] [\-r] [\-f] [\-C message]"
 +.PP
 +Shut down the remote server\&.
 +.PP
 +\-r
 +.RS 4
 +Reboot after shutdown\&.
 +.RE
 +.PP
 +\-f
 +.RS 4
 +Force shutting down all applications\&.
 +.RE
 +.PP
 +\-t timeout
 +.RS 4
 +Timeout before system will be shut down\&. An interactive user of the system can use this time to cancel the shutdown\&.
 +.RE
 +.PP
 +\-C message
 +.RS 4
 +Display the specified message on the screen to announce the shutdown\&.
 +.RE
 +.SS "RPC SAMDUMP"
 +.PP
 +Print out sam database of remote server\&. You need to run this against the PDC, from a Samba machine joined as a BDC\&.
 +.SS "RPC VAMPIRE"
 +.PP
 +Export users, aliases and groups from remote server to local server\&. You need to run this against the PDC, from a Samba machine joined as a BDC\&. This vampire command cannot be used against an Active Directory, only against an NT4 Domain Controller\&.
 +.SS "RPC VAMPIRE KEYTAB"
 +.PP
 +Dump remote SAM database to local Kerberos keytab file\&.
 +.SS "RPC VAMPIRE LDIF"
 +.PP
 +Dump remote SAM database to local LDIF file or standard output\&.
 +.SS "RPC GETSID"
 +.PP
 +Fetch domain SID and store it in the local
 +secrets\&.tdb\&.
 +.SS "ADS LEAVE"
 +.PP
 +Make the remote host leave the domain it is part of\&.
 +.SS "ADS STATUS"
 +.PP
 +Print out status of machine account of the local machine in ADS\&. Prints out quite some debug info\&. Aimed at developers, regular users should use
 +NET ADS TESTJOIN\&.
 +.SS "ADS PRINTER"
 +.SS "ADS PRINTER INFO [PRINTER] [SERVER]"
 +.PP
 +Lookup info for
 +\fIPRINTER\fR
 +on
 +\fISERVER\fR\&. The printer name defaults to "*", the server name defaults to the local host\&.
 +.SS "ADS PRINTER PUBLISH PRINTER"
 +.PP
 +Publish specified printer using ADS\&.
 +.SS "ADS PRINTER REMOVE PRINTER"
 +.PP
 +Remove specified printer from ADS directory\&.
 +.SS "ADS SEARCH \fIEXPRESSION\fR \fIATTRIBUTES\&.\&.\&.\fR"
 +.PP
 +Perform a raw LDAP search on a ADS server and dump the results\&. The expression is a standard LDAP search expression, and the attributes are a list of LDAP fields to show in the results\&.
 +.PP
 +Example:
 +\fBnet ads search \*(Aq(objectCategory=group)\*(Aq sAMAccountName\fR
 +.SS "ADS DN \fIDN\fR \fI(attributes)\fR"
 +.PP
 +Perform a raw LDAP search on a ADS server and dump the results\&. The DN standard LDAP DN, and the attributes are a list of LDAP fields to show in the result\&.
 +.PP
 +Example:
 +\fBnet ads dn \*(AqCN=administrator,CN=Users,DC=my,DC=domain\*(Aq SAMAccountName\fR
 +.SS "ADS WORKGROUP"
 +.PP
 +Print out workgroup name for specified kerberos realm\&.
 +.SS "ADS ENCTYPES"
 +.PP
 +List, modify or delete the value of the "msDS\-SupportedEncryptionTypes" attribute of an account in AD\&.
 +.PP
 +This attribute allows to control which Kerberos encryption types are used for the generation of initial and service tickets\&. The value consists of an integer bitmask with the following values:
 +.PP
 +0x00000001 DES\-CBC\-CRC
 +.PP
 +0x00000002 DES\-CBC\-MD5
 +.PP
 +0x00000004 RC4\-HMAC
 +.PP
 +0x00000008 AES128\-CTS\-HMAC\-SHA1\-96
 +.PP
 +0x00000010 AES256\-CTS\-HMAC\-SHA1\-96
 +.SS "ADS ENCTYPES LIST \fI<ACCOUNTNAME>\fR"
 +.PP
 +List the value of the "msDS\-SupportedEncryptionTypes" attribute of a given account\&.
 +.PP
 +Example:
 +\fBnet ads enctypes list Computername\fR
 +.SS "ADS ENCTYPES SET \fI<ACCOUNTNAME>\fR \fI[enctypes]\fR"
 +.PP
 +Set the value of the "msDS\-SupportedEncryptionTypes" attribute of the LDAP object of ACCOUNTNAME to a given value\&. If the value is ommitted, the value is set to 31 which enables all the currently supported encryption types\&.
 +.PP
 +Example:
 +\fBnet ads enctypes set Computername 24\fR
 +.SS "ADS ENCTYPES DELETE \fI<ACCOUNTNAME>\fR"
 +.PP
 +Deletes the "msDS\-SupportedEncryptionTypes" attribute of the LDAP object of ACCOUNTNAME\&.
 +.PP
 +Example:
 +\fBnet ads enctypes set Computername 24\fR
 +.SS "SAM CREATEBUILTINGROUP <NAME>"
 +.PP
 +(Re)Create a BUILTIN group\&. Only a wellknown set of BUILTIN groups can be created with this command\&. This is the list of currently recognized group names: Administrators, Users, Guests, Power Users, Account Operators, Server Operators, Print Operators, Backup Operators, Replicator, RAS Servers, Pre\-Windows 2000 compatible Access\&. This command requires a running Winbindd with idmap allocation properly configured\&. The group gid will be allocated out of the winbindd range\&.
 +.SS "SAM CREATELOCALGROUP <NAME>"
 +.PP
 +Create a LOCAL group (also known as Alias)\&. This command requires a running Winbindd with idmap allocation properly configured\&. The group gid will be allocated out of the winbindd range\&.
 +.SS "SAM DELETELOCALGROUP <NAME>"
 +.PP
 +Delete an existing LOCAL group (also known as Alias)\&.
 +.SS "SAM MAPUNIXGROUP <NAME>"
 +.PP
 +Map an existing Unix group and make it a Domain Group, the domain group will have the same name\&.
 +.SS "SAM UNMAPUNIXGROUP <NAME>"
 +.PP
 +Remove an existing group mapping entry\&.
 +.SS "SAM ADDMEM <GROUP> <MEMBER>"
 +.PP
 +Add a member to a Local group\&. The group can be specified only by name, the member can be specified by name or SID\&.
 +.SS "SAM DELMEM <GROUP> <MEMBER>"
 +.PP
 +Remove a member from a Local group\&. The group and the member must be specified by name\&.
 +.SS "SAM LISTMEM <GROUP>"
 +.PP
 +List Local group members\&. The group must be specified by name\&.
 +.SS "SAM LIST <users|groups|localgroups|builtin|workstations> [verbose]"
 +.PP
 +List the specified set of accounts by name\&. If verbose is specified, the rid and description is also provided for each account\&.
 +.SS "SAM RIGHTS LIST"
 +.PP
 +List all available privileges\&.
 +.SS "SAM RIGHTS GRANT <NAME> <PRIVILEGE>"
 +.PP
 +Grant one or more privileges to a user\&.
 +.SS "SAM RIGHTS REVOKE <NAME> <PRIVILEGE>"
 +.PP
 +Revoke one or more privileges from a user\&.
 +.SS "SAM SHOW <NAME>"
 +.PP
 +Show the full DOMAIN\e\eNAME the SID and the type for the corresponding account\&.
 +.SS "SAM SET HOMEDIR <NAME> <DIRECTORY>"
 +.PP
 +Set the home directory for a user account\&.
 +.SS "SAM SET PROFILEPATH <NAME> <PATH>"
 +.PP
 +Set the profile path for a user account\&.
 +.SS "SAM SET COMMENT <NAME> <COMMENT>"
 +.PP
 +Set the comment for a user or group account\&.
 +.SS "SAM SET FULLNAME <NAME> <FULL NAME>"
 +.PP
 +Set the full name for a user account\&.
 +.SS "SAM SET LOGONSCRIPT <NAME> <SCRIPT>"
 +.PP
 +Set the logon script for a user account\&.
 +.SS "SAM SET HOMEDRIVE <NAME> <DRIVE>"
 +.PP
 +Set the home drive for a user account\&.
 +.SS "SAM SET WORKSTATIONS <NAME> <WORKSTATIONS>"
 +.PP
 +Set the workstations a user account is allowed to log in from\&.
 +.SS "SAM SET DISABLE <NAME>"
 +.PP
 +Set the "disabled" flag for a user account\&.
 +.SS "SAM SET PWNOTREQ <NAME>"
 +.PP
 +Set the "password not required" flag for a user account\&.
 +.SS "SAM SET AUTOLOCK <NAME>"
 +.PP
 +Set the "autolock" flag for a user account\&.
 +.SS "SAM SET PWNOEXP <NAME>"
 +.PP
 +Set the "password do not expire" flag for a user account\&.
 +.SS "SAM SET PWDMUSTCHANGENOW <NAME> [yes|no]"
 +.PP
 +Set or unset the "password must change" flag for a user account\&.
 +.SS "SAM POLICY LIST"
 +.PP
 +List the available account policies\&.
 +.SS "SAM POLICY SHOW <account policy>"
 +.PP
 +Show the account policy value\&.
 +.SS "SAM POLICY SET <account policy> <value>"
 +.PP
 +Set a value for the account policy\&. Valid values can be: "forever", "never", "off", or a number\&.
 +.SS "SAM PROVISION"
 +.PP
 +Only available if ldapsam:editposix is set and winbindd is running\&. Properly populates the ldap tree with the basic accounts (Administrator) and groups (Domain Users, Domain Admins, Domain Guests) on the ldap tree\&.
 +.SS "IDMAP DUMP <local tdb file name>"
 +.PP
 +Dumps the mappings contained in the local tdb file specified\&. This command is useful to dump only the mappings produced by the idmap_tdb backend\&.
 +.SS "IDMAP RESTORE [input file]"
 +.PP
 +Restore the mappings from the specified file or stdin\&.
 +.SS "IDMAP SET SECRET <DOMAIN> <secret>"
 +.PP
 +Store a secret for the specified domain, used primarily for domains that use idmap_ldap as a backend\&. In this case the secret is used as the password for the user DN used to bind to the ldap server\&.
 +.SS "IDMAP SET RANGE <RANGE> <SID> [index] [\-\-db=<DB>]"
 +.PP
 +Store a domain\-range mapping for a given domain (and index) in autorid database\&.
 +.SS "IDMAP SET CONFIG <config> [\-\-db=<DB>]"
 +.PP
 +Update CONFIG entry in autorid database\&.
 +.SS "IDMAP GET RANGE <SID> [index] [\-\-db=<DB>]"
 +.PP
 +Get the range for a given domain and index from autorid database\&.
 +.SS "IDMAP GET RANGES [<SID>] [\-\-db=<DB>]"
 +.PP
 +Get ranges for all domains or for one identified by given SID\&.
 +.SS "IDMAP GET CONFIG [\-\-db=<DB>]"
 +.PP
 +Get CONFIG entry from autorid database\&.
 +.SS "IDMAP DELETE MAPPING [\-f] [\-\-db=<DB>] <ID>"
 +.PP
 +Delete a mapping sid <\-> gid or sid <\-> uid from the IDMAP database\&. The mapping is given by <ID> which may either be a sid: S\-x\-\&.\&.\&., a gid: "GID number" or a uid: "UID number"\&. Use \-f to delete an invalid partial mapping <ID> \-> xx
 +.PP
 +Use "smbcontrol all idmap \&.\&.\&." to notify running smbd instances\&. See the
 +\fBsmbcontrol\fR(1)
 +manpage for details\&.
 +.SS "IDMAP DELETE RANGE [\-f] [\-\-db=<TDB>] <RANGE>|(<SID> [<INDEX>])"
 +.PP
 +Delete a domain range mapping identified by \*(AqRANGE\*(Aq or "domain SID and INDEX" from autorid database\&. Use \-f to delete invalid mappings\&.
 +.SS "IDMAP DELETE RANGES [\-f] [\-\-db=<TDB>] <SID>"
 +.PP
 +Delete all domain range mappings for a domain identified by SID\&. Use \-f to delete invalid mappings\&.
 +.SS "IDMAP CHECK [\-v] [\-r] [\-a] [\-T] [\-f] [\-l] [\-\-db=<DB>]"
 +.PP
 +Check and repair the IDMAP database\&. If no option is given a read only check of the database is done\&. Among others an interactive or automatic repair mode may be chosen with one of the following options:
 +.PP
 +\-r|\-\-repair
 +.RS 4
 +Interactive repair mode, ask a lot of questions\&.
 +.RE
 +.PP
 +\-a|\-\-auto
 +.RS 4
 +Noninteractive repair mode, use default answers\&.
 +.RE
 +.PP
 +\-v|\-\-verbose
 +.RS 4
 +Produce more output\&.
 +.RE
 +.PP
 +\-f|\-\-force
 +.RS 4
 +Try to apply changes, even if they do not apply cleanly\&.
 +.RE
 +.PP
 +\-T|\-\-test
 +.RS 4
 +Dry run, show what changes would be made but don\*(Aqt touch anything\&.
 +.RE
 +.PP
 +\-l|\-\-lock
 +.RS 4
 +Lock the database while doing the check\&.
 +.RE
 +.PP
 +\-\-db <DB>
 +.RS 4
 +Check the specified database\&.
 +.RE
 +.PP
 +.RS 4
 +.RE
 +It reports about the finding of the following errors:
 +.PP
 +Missing reverse mapping:
 +.RS 4
 +A record with mapping A\->B where there is no B\->A\&. Default action in repair mode is to "fix" this by adding the reverse mapping\&.
 +.RE
 +.PP
 +Invalid mapping:
 +.RS 4
 +A record with mapping A\->B where B\->C\&. Default action is to "delete" this record\&.
 +.RE
 +.PP
 +Missing or invalid HWM:
 +.RS 4
 +A high water mark is not at least equal to the largest ID in the database\&. Default action is to "fix" this by setting it to the largest ID found +1\&.
 +.RE
 +.PP
 +Invalid record:
 +.RS 4
 +Something we failed to parse\&. Default action is to "edit" it in interactive and "delete" it in automatic mode\&.
 +.RE
 +.SS "USERSHARE"
 +.PP
 +Starting with version 3\&.0\&.23, a Samba server now supports the ability for non\-root users to add user defined shares to be exported using the "net usershare" commands\&.
 +.PP
 +To set this up, first set up your smb\&.conf by adding to the [global] section: usershare path = /usr/local/samba/lib/usershares Next create the directory /usr/local/samba/lib/usershares, change the owner to root and set the group owner to the UNIX group who should have the ability to create usershares, for example a group called "serverops"\&. Set the permissions on /usr/local/samba/lib/usershares to 01770\&. (Owner and group all access, no access for others, plus the sticky bit, which [...]
 +.PP
 +The usershare commands are:
 +.RS 4
 +net usershare add sharename path [comment [acl] [guest_ok=[y|n]]] \- to add or change a user defined share\&.
 +.RE
 +.RS 4
 +net usershare delete sharename \- to delete a user defined share\&.
 +.RE
 +.RS 4
 +net usershare info [\-l|\-\-long] [wildcard sharename] \- to print info about a user defined share\&.
 +.RE
 +.RS 4
 +net usershare list [\-l|\-\-long] [wildcard sharename] \- to list user defined shares\&.
 +.RE
 +.SS "USERSHARE ADD sharename path [comment] [acl] [guest_ok=[y|n]]"
 +.PP
 +Add or replace a new user defined share, with name "sharename"\&.
 +.PP
 +"path" specifies the absolute pathname on the system to be exported\&. Restrictions may be put on this, see the global smb\&.conf parameters: "usershare owner only", "usershare prefix allow list", and "usershare prefix deny list"\&.
 +.PP
 +The optional "comment" parameter is the comment that will appear on the share when browsed to by a client\&.
 +.PP
 +The optional "acl" field specifies which users have read and write access to the entire share\&. Note that guest connections are not allowed unless the smb\&.conf parameter "usershare allow guests" has been set\&. The definition of a user defined share acl is: "user:permission", where user is a valid username on the system and permission can be "F", "R", or "D"\&. "F" stands for "full permissions", ie\&. read and write permissions\&. "D" stands for "deny" for a user, ie\&. prevent this  [...]
 +.PP
 +The default if no "acl" is given is "Everyone:R", which means any authenticated user has read\-only access\&.
 +.PP
 +The optional "guest_ok" has the same effect as the parameter of the same name in smb\&.conf, in that it allows guest access to this user defined share\&. This parameter is only allowed if the global parameter "usershare allow guests" has been set to true in the smb\&.conf\&.
 +
 +
 +There is no separate command to modify an existing user defined share,
 +just use the "net usershare add [sharename]" command using the same
 +sharename as the one you wish to modify and specify the new options
 +you wish\&. The Samba smbd daemon notices user defined share modifications
 +at connect time so will see the change immediately, there is no need
 +to restart smbd on adding, deleting or changing a user defined share\&.
 +.SS "USERSHARE DELETE sharename"
 +.PP
 +Deletes the user defined share by name\&. The Samba smbd daemon immediately notices this change, although it will not disconnect any users currently connected to the deleted share\&.
 +.SS "USERSHARE INFO [-l|--long] [wildcard sharename]"
 +.PP
 +Get info on user defined shares owned by the current user matching the given pattern, or all users\&.
 +.PP
 +net usershare info on its own dumps out info on the user defined shares that were created by the current user, or restricts them to share names that match the given wildcard pattern (\*(Aq*\*(Aq matches one or more characters, \*(Aq?\*(Aq matches only one character)\&. If the \*(Aq\-l\*(Aq or \*(Aq\-\-long\*(Aq option is also given, it prints out info on user defined shares created by other users\&.
 +.PP
 +The information given about a share looks like: [foobar] path=/home/jeremy comment=testme usershare_acl=Everyone:F guest_ok=n And is a list of the current settings of the user defined share that can be modified by the "net usershare add" command\&.
 +.SS "USERSHARE LIST [-l|--long] wildcard sharename"
 +.PP
 +List all the user defined shares owned by the current user matching the given pattern, or all users\&.
 +.PP
 +net usershare list on its own list out the names of the user defined shares that were created by the current user, or restricts the list to share names that match the given wildcard pattern (\*(Aq*\*(Aq matches one or more characters, \*(Aq?\*(Aq matches only one character)\&. If the \*(Aq\-l\*(Aq or \*(Aq\-\-long\*(Aq option is also given, it includes the names of user defined shares created by other users\&.
 +.SS "[RPC] CONF"
 +.PP
 +Starting with version 3\&.2\&.0, a Samba server can be configured by data stored in registry\&. This configuration data can be edited with the new "net conf" commands\&. There is also the possibility to configure a remote Samba server by enabling the RPC conf mode and specifying the address of the remote server\&.
 +.PP
 +The deployment of this configuration data can be activated in two levels from the
 +\fIsmb\&.conf\fR
 +file: Share definitions from registry are activated by setting
 +\fIregistry shares\fR
 +to
 +\(lqyes\(rq
 +in the [global] section and global configuration options are activated by setting
 +\m[blue]\fBinclude = registry\fR\m[]
 +in the [global] section for a mixed configuration or by setting
 +\m[blue]\fBconfig backend = registry\fR\m[]
 +in the [global] section for a registry\-only configuration\&. See the
 +\fBsmb.conf\fR(5)
 +manpage for details\&.
 +.PP
 +The conf commands are:
 +.RS 4
 +net [rpc] conf list \- Dump the complete configuration in smb\&.conf like
 +format\&.
 +.RE
 +.RS 4
 +net [rpc] conf import \- Import configuration from file in smb\&.conf
 +format\&.
 +.RE
 +.RS 4
 +net [rpc] conf listshares \- List the registry shares\&.
 +.RE
 +.RS 4
 +net [rpc] conf drop \- Delete the complete configuration from
 +registry\&.
 +.RE
 +.RS 4
 +net [rpc] conf showshare \- Show the definition of a registry share\&.
 +.RE
 +.RS 4
 +net [rpc] conf addshare \- Create a new registry share\&.
 +.RE
 +.RS 4
 +net [rpc] conf delshare \- Delete a registry share\&.
 +.RE
 +.RS 4
 +net [rpc] conf setparm \- Store a parameter\&.
 +.RE
 +.RS 4
 +net [rpc] conf getparm \- Retrieve the value of a parameter\&.
 +.RE
 +.RS 4
 +net [rpc] conf delparm \- Delete a parameter\&.
 +.RE
 +.RS 4
 +net [rpc] conf getincludes \- Show the includes of a share definition\&.
 +.RE
 +.RS 4
 +net [rpc] conf setincludes \- Set includes for a share\&.
 +.RE
 +.RS 4
 +net [rpc] conf delincludes \- Delete includes from a share definition\&.
 +.RE
 +.SS "[RPC] CONF LIST"
 +.PP
 +Print the configuration data stored in the registry in a smb\&.conf\-like format to standard output\&.
 +.SS "[RPC] CONF IMPORT [--test|-T] filename [section]"
 +.PP
 +This command imports configuration from a file in smb\&.conf format\&. If a section encountered in the input file is present in registry, its contents is replaced\&. Sections of registry configuration that have no counterpart in the input file are not affected\&. If you want to delete these, you will have to use the "net conf drop" or "net conf delshare" commands\&. Optionally, a section may be specified to restrict the effect of the import command to that specific section\&. A test mod [...]
 +.SS "[RPC] CONF LISTSHARES"
 +.PP
 +List the names of the shares defined in registry\&.
 +.SS "[RPC] CONF DROP"
 +.PP
 +Delete the complete configuration data from registry\&.
 +.SS "[RPC] CONF SHOWSHARE sharename"
 +.PP
 +Show the definition of the share or section specified\&. It is valid to specify "global" as sharename to retrieve the global configuration options from registry\&.
 +.SS "[RPC] CONF ADDSHARE sharename path [writeable={y|N} [guest_ok={y|N} [comment]]] "
 +.PP
 +Create a new share definition in registry\&. The sharename and path have to be given\&. The share name may
 +\fInot\fR
 +be "global"\&. Optionally, values for the very common options "writeable", "guest ok" and a "comment" may be specified\&. The same result may be obtained by a sequence of "net conf setparm" commands\&.
 +.SS "[RPC] CONF DELSHARE sharename"
 +.PP
 +Delete a share definition from registry\&.
 +.SS "[RPC] CONF SETPARM section parameter value"
 +.PP
 +Store a parameter in registry\&. The section may be global or a sharename\&. The section is created if it does not exist yet\&.
 +.SS "[RPC] CONF GETPARM section parameter"
 +.PP
 +Show a parameter stored in registry\&.
 +.SS "[RPC] CONF DELPARM section parameter"
 +.PP
 +Delete a parameter stored in registry\&.
 +.SS "[RPC] CONF GETINCLUDES section"
 +.PP
 +Get the list of includes for the provided section (global or share)\&.
 +.PP
 +Note that due to the nature of the registry database and the nature of include directives, the includes need special treatment: Parameters are stored in registry by the parameter name as valuename, so there is only ever one instance of a parameter per share\&. Also, a specific order like in a text file is not guaranteed\&. For all real parameters, this is perfectly ok, but the include directive is rather a meta parameter, for which, in the smb\&.conf text file, the place where it is spe [...]
 +.PP
 +Further note that currently, only files can be included from registry configuration\&. In the future, there will be the ability to include configuration data from other registry keys\&.
 +.SS "[RPC] CONF SETINCLUDES section [filename]+"
 +.PP
 +Set the list of includes for the provided section (global or share) to the given list of one or more filenames\&. The filenames may contain the usual smb\&.conf macros like %I\&.
 +.SS "[RPC] CONF DELINCLUDES section"
 +.PP
 +Delete the list of includes from the provided section (global or share)\&.
 +.SS "REGISTRY"
 +.PP
 +Manipulate Samba\*(Aqs registry\&.
 +.PP
 +The registry commands are:
 +.RS 4
 +net registry enumerate   \- Enumerate registry keys and values\&.
 +.RE
 +.RS 4
 +net registry enumerate_recursive \- Enumerate registry key and its subkeys\&.
 +.RE
 +.RS 4
 +net registry createkey   \- Create a new registry key\&.
 +.RE
 +.RS 4
 +net registry deletekey   \- Delete a registry key\&.
 +.RE
 +.RS 4
 +net registry deletekey_recursive \- Delete a registry key with subkeys\&.
 +.RE
 +.RS 4
 +net registry getvalue    \- Print a registry value\&.
 +.RE
 +.RS 4
 +net registry getvalueraw \- Print a registry value (raw format)\&.
 +.RE
 +.RS 4
 +net registry setvalue    \- Set a new registry value\&.
 +.RE
 +.RS 4
 +net registry increment   \- Increment a DWORD registry value under a lock\&.
 +.RE
 +.RS 4
 +net registry deletevalue \- Delete a registry value\&.
 +.RE
 +.RS 4
 +net registry getsd       \- Get security descriptor\&.
 +.RE
 +.RS 4
 +net registry getsd_sdd1  \- Get security descriptor in sddl format\&.
 +.RE
 +.RS 4
 +net registry setsd_sdd1  \- Set security descriptor from sddl format
 +string\&.
 +.RE
 +.RS 4
 +net registry import      \- Import a registration entries (\&.reg) file\&.
 +.RE
 +.RS 4
 +net registry export      \- Export a registration entries (\&.reg) file\&.
 +.RE
 +.RS 4
 +net registry convert     \- Convert a registration entries (\&.reg) file\&.
 +.RE
 +.RS 4
 +net registry check       \- Check and repair a registry database\&.
 +.RE
 +.SS "REGISTRY ENUMERATE key "
 +.PP
 +Enumerate subkeys and values of
 +\fIkey\fR\&.
 +.SS "REGISTRY ENUMERATE_RECURSIVE key "
 +.PP
 +Enumerate values of
 +\fIkey\fR
 +and its subkeys\&.
 +.SS "REGISTRY CREATEKEY key "
 +.PP
 +Create a new
 +\fIkey\fR
 +if not yet existing\&.
 +.SS "REGISTRY DELETEKEY key "
 +.PP
 +Delete the given
 +\fIkey\fR
 +and its values from the registry, if it has no subkeys\&.
 +.SS "REGISTRY DELETEKEY_RECURSIVE key "
 +.PP
 +Delete the given
 +\fIkey\fR
 +and all of its subkeys and values from the registry\&.
 +.SS "REGISTRY GETVALUE key name"
 +.PP
 +Output type and actual value of the value
 +\fIname\fR
 +of the given
 +\fIkey\fR\&.
 +.SS "REGISTRY GETVALUERAW key name"
 +.PP
 +Output the actual value of the value
 +\fIname\fR
 +of the given
 +\fIkey\fR\&.
 +.SS "REGISTRY SETVALUE key name type value ..."
 +.PP
 +Set the value
 +\fIname\fR
 +of an existing
 +\fIkey\fR\&.
 +\fItype\fR
 +may be one of
 +\fIsz\fR,
 +\fImulti_sz\fR
 +or
 +\fIdword\fR\&. In case of
 +\fImulti_sz\fR\fIvalue\fR
 +may be given multiple times\&.
 +.SS "REGISTRY INCREMENT key name [inc]"
 +.PP
 +Increment the DWORD value
 +\fIname\fR
 +of
 +\fIkey\fR
 +by
 +\fIinc\fR
 +while holding a g_lock\&.
 +\fIinc\fR
 +defaults to 1\&.
 +.SS "REGISTRY DELETEVALUE key name"
 +.PP
 +Delete the value
 +\fIname\fR
 +of the given
 +\fIkey\fR\&.
 +.SS "REGISTRY GETSD key"
 +.PP
 +Get the security descriptor of the given
 +\fIkey\fR\&.
 +.SS "REGISTRY GETSD_SDDL key"
 +.PP
 +Get the security descriptor of the given
 +\fIkey\fR
 +as a Security Descriptor Definition Language (SDDL) string\&.
 +.SS "REGISTRY SETSD_SDDL keysd"
 +.PP
 +Set the security descriptor of the given
 +\fIkey\fR
 +from a Security Descriptor Definition Language (SDDL) string
 +\fIsd\fR\&.
 +.SS "REGISTRY IMPORT file [--precheck <check-file>] [opt]"
 +.PP
 +Import a registration entries (\&.reg)
 +\fIfile\fR\&.
 +.PP
 +The following options are available:
 +.PP
 +\-\-precheck \fIcheck\-file\fR
 +.RS 4
 +This is a mechanism to check the existence or non\-existence of certain keys or values specified in a precheck file before applying the import file\&. The import file will only be applied if the precheck succeeds\&.
 +.sp
 +The check\-file follows the normal registry file syntax with the following semantics:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +<value name>=<value> checks whether the value exists and has the given value\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +<value name>=\- checks whether the value does not exist\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +[key] checks whether the key exists\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +[\-key] checks whether the key does not exist\&.
 +.RE
 +.sp
 +.RE
 +.RE
 +.SS "REGISTRY EXPORT keyfile[opt]"
 +.PP
 +Export a
 +\fIkey\fR
 +to a registration entries (\&.reg)
 +\fIfile\fR\&.
 +.SS "REGISTRY CONVERT in out [[inopt] outopt]"
 +.PP
 +Convert a registration entries (\&.reg) file
 +\fIin\fR\&.
 +.SS "REGISTRY CHECK [-ravTl] [-o <ODB>] [--wipe] [<DB>]"
 +.PP
 +Check and repair the registry database\&. If no option is given a read only check of the database is done\&. Among others an interactive or automatic repair mode may be chosen with one of the following options
 +.PP
 +\-r|\-\-repair
 +.RS 4
 +Interactive repair mode, ask a lot of questions\&.
 +.RE
 +.PP
 +\-a|\-\-auto
 +.RS 4
 +Noninteractive repair mode, use default answers\&.
 +.RE
 +.PP
 +\-v|\-\-verbose
 +.RS 4
 +Produce more output\&.
 +.RE
 +.PP
 +\-T|\-\-test
 +.RS 4
 +Dry run, show what changes would be made but don\*(Aqt touch anything\&.
 +.RE
 +.PP
 +\-l|\-\-lock
 +.RS 4
 +Lock the database while doing the check\&.
 +.RE
 +.PP
 +\-\-reg\-version={1,2,3}
 +.RS 4
 +Specify the format of the registry database\&. If not given it defaults to the value of the binary or, if an registry\&.tdb is explizitly stated at the commandline, to the value found in the INFO/version record\&.
 +.RE
 +.PP
 +[\-\-db] <DB>
 +.RS 4
 +Check the specified database\&.
 +.RE
 +.PP
 +\-o|\-\-output <ODB>
 +.RS 4
 +Create a new registry database <ODB> instead of modifying the input\&. If <ODB> is already existing \-\-wipe may be used to overwrite it\&.
 +.RE
 +.PP
 +\-\-wipe
 +.RS 4
 +Replace the registry database instead of modifying the input or overwrite an existing output database\&.
 +.RE
 +.PP
 +.RS 4
 +.RE
 +.SS "EVENTLOG"
 +.PP
 +Starting with version 3\&.4\&.0 net can read, dump, import and export native win32 eventlog files (usually *\&.evt)\&. evt files are used by the native Windows eventviewer tools\&.
 +.PP
 +The import and export of evt files can only succeed when
 +\fIeventlog list\fR
 +is used in
 +\fIsmb\&.conf\fR
 +file\&. See the
 +\fBsmb.conf\fR(5)
 +manpage for details\&.
 +.PP
 +The eventlog commands are:
 +.RS 4
 +net eventlog dump \- Dump a eventlog *\&.evt file on the screen\&.
 +.RE
 +.RS 4
 +net eventlog import \- Import a eventlog *\&.evt into the samba internal
 +tdb based representation of eventlogs\&.
 +.RE
 +.RS 4
 +net eventlog export \- Export the samba internal tdb based representation
 +of eventlogs into an eventlog *\&.evt file\&.
 +.RE
 +.SS "EVENTLOG DUMP filename"
 +.PP
 +Prints a eventlog *\&.evt file to standard output\&.
 +.SS "EVENTLOG IMPORT filename eventlog"
 +.PP
 +Imports a eventlog *\&.evt file defined by
 +\fIfilename\fR
 +into the samba internal tdb representation of eventlog defined by
 +\fIeventlog\fR\&.
 +\fIeventlog\fR
 +needs to part of the
 +\fIeventlog list\fR
 +defined in smb\&.conf\&. See the
 +\fBsmb.conf\fR(5)
 +manpage for details\&.
 +.SS "EVENTLOG EXPORT filename eventlog"
 +.PP
 +Exports the samba internal tdb representation of eventlog defined by
 +\fIeventlog\fR
 +to a eventlog *\&.evt file defined by
 +\fIfilename\fR\&.
 +\fIeventlog\fR
 +needs to part of the
 +\fIeventlog list\fR
 +defined in smb\&.conf\&. See the
 +\fBsmb.conf\fR(5)
 +manpage for details\&.
 +.SS "DOM"
 +.PP
 +Starting with version 3\&.2\&.0 Samba has support for remote join and unjoin APIs, both client and server\-side\&. Windows supports remote join capabilities since Windows 2000\&.
 +.PP
 +In order for Samba to be joined or unjoined remotely an account must be used that is either member of the Domain Admins group, a member of the local Administrators group or a user that is granted the SeMachineAccountPrivilege privilege\&.
 +.PP
 +The client side support for remote join is implemented in the net dom commands which are:
 +.RS 4
 +net dom join \- Join a remote computer into a domain\&.
 +.RE
 +.RS 4
 +net dom unjoin \- Unjoin a remote computer from a domain\&.
 +.RE
 +.RS 4
 +net dom renamecomputer \- Renames a remote computer joined to a domain\&.
 +.RE
 +.SS "DOM JOIN	domain=DOMAIN ou=OU account=ACCOUNT password=PASSWORD reboot"
 +.PP
 +Joins a computer into a domain\&. This command supports the following additional parameters:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIDOMAIN\fR
 +can be a NetBIOS domain name (also known as short domain name) or a DNS domain name for Active Directory Domains\&. As in Windows, it is also possible to control which Domain Controller to use\&. This can be achieved by appending the DC name using the \e separator character\&. Example: MYDOM\eMYDC\&. The
 +\fIDOMAIN\fR
 +parameter cannot be NULL\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIOU\fR
 +can be set to a RFC 1779 LDAP DN, like
 +\fIou=mymachines,cn=Users,dc=example,dc=com\fR
 +in order to create the machine account in a non\-default LDAP container\&. This optional parameter is only supported when joining Active Directory Domains\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIACCOUNT\fR
 +defines a domain account that will be used to join the machine to the domain\&. This domain account needs to have sufficient privileges to join machines\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIPASSWORD\fR
 +defines the password for the domain account defined with
 +\fIACCOUNT\fR\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIREBOOT\fR
 +is an optional parameter that can be set to reboot the remote machine after successful join to the domain\&.
 +.RE
 +.sp
 +.RE
 +.PP
 +Note that you also need to use standard net parameters to connect and authenticate to the remote machine that you want to join\&. These additional parameters include: \-S computer and \-U user\&.
 +.PP
 +Example: net dom join \-S xp \-U XP\e\eadministrator%secret domain=MYDOM account=MYDOM\e\eadministrator password=topsecret reboot\&.
 +.PP
 +This example would connect to a computer named XP as the local administrator using password secret, and join the computer into a domain called MYDOM using the MYDOM domain administrator account and password topsecret\&. After successful join, the computer would reboot\&.
 +.SS "DOM UNJOIN account=ACCOUNT password=PASSWORD reboot"
 +.PP
 +Unjoins a computer from a domain\&. This command supports the following additional parameters:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIACCOUNT\fR
 +defines a domain account that will be used to unjoin the machine from the domain\&. This domain account needs to have sufficient privileges to unjoin machines\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIPASSWORD\fR
 +defines the password for the domain account defined with
 +\fIACCOUNT\fR\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIREBOOT\fR
 +is an optional parameter that can be set to reboot the remote machine after successful unjoin from the domain\&.
 +.RE
 +.sp
 +.RE
 +.PP
 +Note that you also need to use standard net parameters to connect and authenticate to the remote machine that you want to unjoin\&. These additional parameters include: \-S computer and \-U user\&.
 +.PP
 +Example: net dom unjoin \-S xp \-U XP\e\eadministrator%secret account=MYDOM\e\eadministrator password=topsecret reboot\&.
 +.PP
 +This example would connect to a computer named XP as the local administrator using password secret, and unjoin the computer from the domain using the MYDOM domain administrator account and password topsecret\&. After successful unjoin, the computer would reboot\&.
 +.SS "DOM RENAMECOMPUTER newname=NEWNAME account=ACCOUNT password=PASSWORD reboot"
 +.PP
 +Renames a computer that is joined to a domain\&. This command supports the following additional parameters:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fINEWNAME\fR
 +defines the new name of the machine in the domain\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIACCOUNT\fR
 +defines a domain account that will be used to rename the machine in the domain\&. This domain account needs to have sufficient privileges to rename machines\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIPASSWORD\fR
 +defines the password for the domain account defined with
 +\fIACCOUNT\fR\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIREBOOT\fR
 +is an optional parameter that can be set to reboot the remote machine after successful rename in the domain\&.
 +.RE
 +.sp
 +.RE
 +.PP
 +Note that you also need to use standard net parameters to connect and authenticate to the remote machine that you want to rename in the domain\&. These additional parameters include: \-S computer and \-U user\&.
 +.PP
 +Example: net dom renamecomputer \-S xp \-U XP\e\eadministrator%secret newname=XPNEW account=MYDOM\e\eadministrator password=topsecret reboot\&.
 +.PP
 +This example would connect to a computer named XP as the local administrator using password secret, and rename the joined computer to XPNEW using the MYDOM domain administrator account and password topsecret\&. After successful rename, the computer would reboot\&.
 +.SS "G_LOCK"
 +.PP
 +Manage global locks\&.
 +.SS "G_LOCK DO lockname timeout command"
 +.PP
 +Execute a shell command under a global lock\&. This might be useful to define the order in which several shell commands will be executed\&. The locking information is stored in a file called
 +g_lock\&.tdb\&. In setups with CTDB running, the locking information will be available on all cluster nodes\&.
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fILOCKNAME\fR
 +defines the name of the global lock\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fITIMEOUT\fR
 +defines the timeout\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fICOMMAND\fR
 +defines the shell command to execute\&.
 +.RE
 +.SS "G_LOCK LOCKS"
 +.PP
 +Print a list of all currently existing locknames\&.
 +.SS "G_LOCK DUMP lockname"
 +.PP
 +Dump the locking table of a certain global lock\&.
 +.SS "HELP [COMMAND]"
 +.PP
 +Gives usage information for the specified command\&.
 +.SH "VERSION"
 +.PP
 +This man page is complete for version 3 of the Samba suite\&.
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
 +.PP
 +The net manpage was written by Jelmer Vernooij\&.
diff --cc docs/manpages/nmbd.8
index 8ee409d,0000000..155c6a5
mode 100644,000000..100644
--- a/docs/manpages/nmbd.8
+++ b/docs/manpages/nmbd.8
@@@ -1,297 -1,0 +1,297 @@@
 +'\" t
 +.\"     Title: nmbd
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: System Administration tools
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "NMBD" "8" "12/01/2015" "Samba 4\&.3" "System Administration tools"
++.TH "NMBD" "8" "12/10/2015" "Samba 4\&.3" "System Administration tools"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +nmbd \- NetBIOS name server to provide NetBIOS over IP naming services to clients
 +.SH "SYNOPSIS"
 +.HP \w'\ 'u
 +nmbd [\-D|\-\-daemon] [\-F|\-\-foreground] [\-S|\-\-log\-stdout] [\-i|\-\-interactive] [\-V] [\-d\ <debug\ level>] [\-H|\-\-hosts\ <lmhosts\ file>] [\-l\ <log\ directory>] [\-p|\-\-port\ <port\ number>] [\-s\ <configuration\ file>] [\-\-no\-process\-group]
 +.SH "DESCRIPTION"
 +.PP
 +This program is part of the
 +\fBsamba\fR(7)
 +suite\&.
 +.PP
 +nmbd
 +is a server that understands and can reply to NetBIOS over IP name service requests, like those produced by SMB/CIFS clients such as Windows 95/98/ME, Windows NT, Windows 2000, Windows XP and LanManager clients\&. It also participates in the browsing protocols which make up the Windows "Network Neighborhood" view\&.
 +.PP
 +SMB/CIFS clients, when they start up, may wish to locate an SMB/CIFS server\&. That is, they wish to know what IP number a specified host is using\&.
 +.PP
 +Amongst other services,
 +nmbd
 +will listen for such requests, and if its own NetBIOS name is specified it will respond with the IP number of the host it is running on\&. Its "own NetBIOS name" is by default the primary DNS name of the host it is running on, but this can be overridden by the
 +\m[blue]\fBnetbios name\fR\m[]
 +in
 +smb\&.conf\&. Thus
 +nmbd
 +will reply to broadcast queries for its own name(s)\&. Additional names for
 +nmbd
 +to respond on can be set via parameters in the
 +\fBsmb.conf\fR(5)
 +configuration file\&.
 +.PP
 +nmbd
 +can also be used as a WINS (Windows Internet Name Server) server\&. What this basically means is that it will act as a WINS database server, creating a database from name registration requests that it receives and replying to queries from clients for these names\&.
 +.PP
 +In addition,
 +nmbd
 +can act as a WINS proxy, relaying broadcast queries from clients that do not understand how to talk the WINS protocol to a WINS server\&.
 +.SH "OPTIONS"
 +.PP
 +\-D|\-\-daemon
 +.RS 4
 +If specified, this parameter causes
 +nmbd
 +to operate as a daemon\&. That is, it detaches itself and runs in the background, fielding requests on the appropriate port\&. By default,
 +nmbd
 +will operate as a daemon if launched from a command shell\&. nmbd can also be operated from the
 +inetd
 +meta\-daemon, although this is not recommended\&.
 +.RE
 +.PP
 +\-F|\-\-foreground
 +.RS 4
 +If specified, this parameter causes the main
 +nmbd
 +process to not daemonize, i\&.e\&. double\-fork and disassociate with the terminal\&. Child processes are still created as normal to service each connection request, but the main process does not exit\&. This operation mode is suitable for running
 +nmbd
 +under process supervisors such as
 +supervise
 +and
 +svscan
 +from Daniel J\&. Bernstein\*(Aqs
 +daemontools
 +package, or the AIX process monitor\&.
 +.RE
 +.PP
 +\-S|\-\-log\-stdout
 +.RS 4
 +If specified, this parameter causes
 +nmbd
 +to log to standard output rather than a file\&.
 +.RE
 +.PP
 +\-i|\-\-interactive
 +.RS 4
 +If this parameter is specified it causes the server to run "interactively", not as a daemon, even if the server is executed on the command line of a shell\&. Setting this parameter negates the implicit daemon mode when run from the command line\&.
 +nmbd
 +also logs to standard output, as if the
 +\fB\-S\fR
 +parameter had been given\&.
 +.RE
 +.PP
 +\-?|\-\-help
 +.RS 4
 +Print a summary of command line options\&.
 +.RE
 +.PP
 +\-\-usage
 +.RS 4
 +Display brief usage message\&.
 +.RE
 +.PP
 +\-H|\-\-hosts <filename>
 +.RS 4
 +NetBIOS lmhosts file\&. The lmhosts file is a list of NetBIOS names to IP addresses that is loaded by the nmbd server and used via the name resolution mechanism
 +\m[blue]\fBname resolve order\fR\m[]
 +described in
 +\fBsmb.conf\fR(5)
 +to resolve any NetBIOS name queries needed by the server\&. Note that the contents of this file are
 +\fINOT\fR
 +used by
 +nmbd
 +to answer any name queries\&. Adding a line to this file affects name NetBIOS resolution from this host
 +\fIONLY\fR\&.
 +.sp
 +The default path to this file is compiled into Samba as part of the build process\&. Common defaults are
 +/usr/local/samba/lib/lmhosts,
 +/usr/samba/lib/lmhosts
 +or
 +/etc/samba/lmhosts\&. See the
 +\fBlmhosts\fR(5)
 +man page for details on the contents of this file\&.
 +.RE
 +.PP
 +\-d|\-\-debuglevel=level
 +.RS 4
 +\fIlevel\fR
 +is an integer from 0 to 10\&. The default value if this parameter is not specified is 0\&.
 +.sp
 +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day\-to\-day running \- it generates a small amount of information about operations carried out\&.
 +.sp
 +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&.
 +.sp
 +Note that specifying this parameter here will override the
 +\m[blue]\fBlog level\fR\m[]
 +parameter in the
 +smb\&.conf
 +file\&.
 +.RE
 +.PP
 +\-V|\-\-version
 +.RS 4
 +Prints the program version number\&.
 +.RE
 +.PP
 +\-s|\-\-configfile=<configuration file>
 +.RS 4
 +The file specified contains the configuration details required by the server\&. The information in this file includes server\-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See
 +smb\&.conf
 +for more information\&. The default configuration file name is determined at compile time\&.
 +.RE
 +.PP
 +\-l|\-\-log\-basename=logdirectory
 +.RS 4
 +Base directory name for log/debug files\&. The extension
 +\fB"\&.progname"\fR
 +will be appended (e\&.g\&. log\&.smbclient, log\&.smbd, etc\&.\&.\&.)\&. The log file is never removed by the client\&.
 +.RE
 +.PP
 +\-\-option=<name>=<value>
 +.RS 4
 +Set the
 +\fBsmb.conf\fR(5)
 +option "<name>" to value "<value>" from the command line\&. This overrides compiled\-in defaults and options read from the configuration file\&.
 +.RE
 +.PP
 +\-p|\-\-port <UDP port number>
 +.RS 4
 +UDP port number is a positive integer value\&. This option changes the default UDP port number (normally 137) that
 +nmbd
 +responds to name queries on\&. Don\*(Aqt use this option unless you are an expert, in which case you won\*(Aqt need help!
 +.RE
 +.PP
 +\-\-no\-process\-group
 +.RS 4
 +Do not create a new process group for nmbd\&.
 +.RE
 +.SH "FILES"
 +.PP
 +/etc/inetd\&.conf
 +.RS 4
 +If the server is to be run by the
 +inetd
 +meta\-daemon, this file must contain suitable startup information for the meta\-daemon\&.
 +.RE
 +.PP
 +/etc/rc
 +.RS 4
 +or whatever initialization script your system uses)\&.
 +.sp
 +If running the server as a daemon at startup, this file will need to contain an appropriate startup sequence for the server\&.
 +.RE
 +.PP
 +/etc/services
 +.RS 4
 +If running the server via the meta\-daemon
 +inetd, this file must contain a mapping of service name (e\&.g\&., netbios\-ssn) to service port (e\&.g\&., 139) and protocol type (e\&.g\&., tcp)\&.
 +.RE
 +.PP
 +/usr/local/samba/lib/smb\&.conf
 +.RS 4
 +This is the default location of the
 +\fBsmb.conf\fR(5)
 +server configuration file\&. Other common places that systems install this file are
 +/usr/samba/lib/smb\&.conf
 +and
 +/etc/samba/smb\&.conf\&.
 +.sp
 +When run as a WINS server (see the
 +\m[blue]\fBwins support\fR\m[]
 +parameter in the
 +\fBsmb.conf\fR(5)
 +man page),
 +nmbd
 +will store the WINS database in the file
 +wins\&.dat
 +in the
 +var/locks
 +directory configured under wherever Samba was configured to install itself\&.
 +.sp
 +If
 +nmbd
 +is acting as a
 +\fI browse master\fR
 +(see the
 +\m[blue]\fBlocal master\fR\m[]
 +parameter in the
 +\fBsmb.conf\fR(5)
 +man page,
 +nmbd
 +will store the browsing database in the file
 +browse\&.dat
 +in the
 +var/locks
 +directory configured under wherever Samba was configured to install itself\&.
 +.RE
 +.SH "SIGNALS"
 +.PP
 +To shut down an
 +nmbd
 +process it is recommended that SIGKILL (\-9)
 +\fINOT\fR
 +be used, except as a last resort, as this may leave the name database in an inconsistent state\&. The correct way to terminate
 +nmbd
 +is to send it a SIGTERM (\-15) signal and wait for it to die on its own\&.
 +.PP
 +nmbd
 +will accept SIGHUP, which will cause it to dump out its namelists into the file
 +namelist\&.debug
 +in the
 +/usr/local/samba/var/locks
 +directory (or the
 +var/locks
 +directory configured under wherever Samba was configured to install itself)\&. This will also cause
 +nmbd
 +to dump out its server database in the
 +log\&.nmb
 +file\&.
 +.PP
 +The debug log level of nmbd may be raised or lowered using
 +\fBsmbcontrol\fR(1)
 +(SIGUSR[1|2] signals are no longer used since Samba 2\&.2)\&. This is to allow transient problems to be diagnosed, whilst still running at a normally low log level\&.
 +.SH "VERSION"
 +.PP
 +This man page is correct for version 3 of the Samba suite\&.
 +.SH "SEE ALSO"
 +.PP
 +\fBinetd\fR(8),
 +\fBsmbd\fR(8),
 +\fBsmb.conf\fR(5),
 +\fBsmbclient\fR(1),
 +\fBtestparm\fR(1), and the Internet RFC\*(Aqs
 +rfc1001\&.txt,
 +rfc1002\&.txt\&. In addition the CIFS (formerly SMB) specification is available as a link from the Web page
 +http://samba\&.org/cifs/\&.
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
 +.PP
 +The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at
 +ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
diff --cc docs/manpages/nmblookup.1
index e8d46f9,0000000..d752790
mode 100644,000000..100644
--- a/docs/manpages/nmblookup.1
+++ b/docs/manpages/nmblookup.1
@@@ -1,228 -1,0 +1,228 @@@
 +'\" t
 +.\"     Title: nmblookup
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: User Commands
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "NMBLOOKUP" "1" "12/01/2015" "Samba 4\&.3" "User Commands"
++.TH "NMBLOOKUP" "1" "12/10/2015" "Samba 4\&.3" "User Commands"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +nmblookup \- NetBIOS over TCP/IP client used to lookup NetBIOS names
 +.SH "SYNOPSIS"
 +.HP \w'\ 'u
 +nmblookup [\-M|\-\-master\-browser] [\-R|\-\-recursion] [\-S|\-\-status] [\-r|\-\-root\-port] [\-A|\-\-lookup\-by\-ip] [\-B|\-\-broadcast\ <broadcast\ address>] [\-U|\-\-unicast\ <unicast\ address>] [\-d\ <debug\ level>] [\-s\ <smb\ config\ file>] [\-i\ <NetBIOS\ scope>] [\-T|\-\-translate] [\-f|\-\-flags] {name}
 +.SH "DESCRIPTION"
 +.PP
 +This tool is part of the
 +\fBsamba\fR(7)
 +suite\&.
 +.PP
 +nmblookup
 +is used to query NetBIOS names and map them to IP addresses in a network using NetBIOS over TCP/IP queries\&. The options allow the name queries to be directed at a particular IP broadcast area or to a particular machine\&. All queries are done over UDP\&.
 +.SH "OPTIONS"
 +.PP
 +\-M|\-\-master\-browser
 +.RS 4
 +Searches for a master browser by looking up the NetBIOS
 +\fIname\fR
 +with a type of
 +\fB0x1d\fR\&. If
 +\fI name\fR
 +is "\-" then it does a lookup on the special name
 +\fB__MSBROWSE__\fR\&. Please note that in order to use the name "\-", you need to make sure "\-" isn\*(Aqt parsed as an argument, e\&.g\&. use :
 +\fBnmblookup \-M \-\- \-\fR\&.
 +.RE
 +.PP
 +\-R|\-\-recursion
 +.RS 4
 +Set the recursion desired bit in the packet to do a recursive lookup\&. This is used when sending a name query to a machine running a WINS server and the user wishes to query the names in the WINS server\&. If this bit is unset the normal (broadcast responding) NetBIOS processing code on a machine is used instead\&. See RFC1001, RFC1002 for details\&.
 +.RE
 +.PP
 +\-S|\-\-status
 +.RS 4
 +Once the name query has returned an IP address then do a node status query as well\&. A node status query returns the NetBIOS names registered by a host\&.
 +.RE
 +.PP
 +\-r|\-\-root\-port
 +.RS 4
 +Try and bind to UDP port 137 to send and receive UDP datagrams\&. The reason for this option is a bug in Windows 95 where it ignores the source port of the requesting packet and only replies to UDP port 137\&. Unfortunately, on most UNIX systems root privilege is needed to bind to this port, and in addition, if the
 +\fBnmbd\fR(8)
 +daemon is running on this machine it also binds to this port\&.
 +.RE
 +.PP
 +\-A|\-\-lookup\-by\-ip
 +.RS 4
 +Interpret
 +\fIname\fR
 +as an IP Address and do a node status query on this address\&.
 +.RE
 +.PP
 +\-n|\-\-netbiosname <primary NetBIOS name>
 +.RS 4
 +This option allows you to override the NetBIOS name that Samba uses for itself\&. This is identical to setting the
 +\m[blue]\fBnetbios name\fR\m[]
 +parameter in the
 +smb\&.conf
 +file\&. However, a command line setting will take precedence over settings in
 +smb\&.conf\&.
 +.RE
 +.PP
 +\-i|\-\-scope <scope>
 +.RS 4
 +This specifies a NetBIOS scope that
 +nmblookup
 +will use to communicate with when generating NetBIOS names\&. For details on the use of NetBIOS scopes, see rfc1001\&.txt and rfc1002\&.txt\&. NetBIOS scopes are
 +\fIvery\fR
 +rarely used, only set this parameter if you are the system administrator in charge of all the NetBIOS systems you communicate with\&.
 +.RE
 +.PP
 +\-W|\-\-workgroup=domain
 +.RS 4
 +Set the SMB domain of the username\&. This overrides the default domain which is the domain defined in smb\&.conf\&. If the domain specified is the same as the servers NetBIOS name, it causes the client to log on using the servers local SAM (as opposed to the Domain SAM)\&.
 +.RE
 +.PP
 +\-O|\-\-socket\-options socket options
 +.RS 4
 +TCP socket options to set on the client socket\&. See the socket options parameter in the
 +smb\&.conf
 +manual page for the list of valid options\&.
 +.RE
 +.PP
 +\-?|\-\-help
 +.RS 4
 +Print a summary of command line options\&.
 +.RE
 +.PP
 +\-\-usage
 +.RS 4
 +Display brief usage message\&.
 +.RE
 +.PP
 +\-B|\-\-broadcast <broadcast address>
 +.RS 4
 +Send the query to the given broadcast address\&. Without this option the default behavior of nmblookup is to send the query to the broadcast address of the network interfaces as either auto\-detected or defined in the
 +\fIinterfaces\fR
 +parameter of the
 +\fBsmb.conf\fR(5)
 +file\&.
 +.RE
 +.PP
 +\-U|\-\-unicast <unicast address>
 +.RS 4
 +Do a unicast query to the specified address or host
 +\fIunicast address\fR\&. This option (along with the
 +\fI\-R\fR
 +option) is needed to query a WINS server\&.
 +.RE
 +.PP
 +\-d|\-\-debuglevel=level
 +.RS 4
 +\fIlevel\fR
 +is an integer from 0 to 10\&. The default value if this parameter is not specified is 0\&.
 +.sp
 +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day\-to\-day running \- it generates a small amount of information about operations carried out\&.
 +.sp
 +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&.
 +.sp
 +Note that specifying this parameter here will override the
 +\m[blue]\fBlog level\fR\m[]
 +parameter in the
 +smb\&.conf
 +file\&.
 +.RE
 +.PP
 +\-V|\-\-version
 +.RS 4
 +Prints the program version number\&.
 +.RE
 +.PP
 +\-s|\-\-configfile=<configuration file>
 +.RS 4
 +The file specified contains the configuration details required by the server\&. The information in this file includes server\-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See
 +smb\&.conf
 +for more information\&. The default configuration file name is determined at compile time\&.
 +.RE
 +.PP
 +\-l|\-\-log\-basename=logdirectory
 +.RS 4
 +Base directory name for log/debug files\&. The extension
 +\fB"\&.progname"\fR
 +will be appended (e\&.g\&. log\&.smbclient, log\&.smbd, etc\&.\&.\&.)\&. The log file is never removed by the client\&.
 +.RE
 +.PP
 +\-\-option=<name>=<value>
 +.RS 4
 +Set the
 +\fBsmb.conf\fR(5)
 +option "<name>" to value "<value>" from the command line\&. This overrides compiled\-in defaults and options read from the configuration file\&.
 +.RE
 +.PP
 +\-T|\-\-translate
 +.RS 4
 +This causes any IP addresses found in the lookup to be looked up via a reverse DNS lookup into a DNS name, and printed out before each
 +.sp
 +\fIIP address \&.\&.\&.\&. NetBIOS name\fR
 +.sp
 +pair that is the normal output\&.
 +.RE
 +.PP
 +\-f|\-\-flags
 +.RS 4
 +Show which flags apply to the name that has been looked up\&. Possible answers are zero or more of: Response, Authoritative, Truncated, Recursion_Desired, Recursion_Available, Broadcast\&.
 +.RE
 +.PP
 +name
 +.RS 4
 +This is the NetBIOS name being queried\&. Depending upon the previous options this may be a NetBIOS name or IP address\&. If a NetBIOS name then the different name types may be specified by appending \*(Aq#<type>\*(Aq to the name\&. This name may also be \*(Aq*\*(Aq, which will return all registered names within a broadcast area\&.
 +.RE
 +.SH "EXAMPLES"
 +.PP
 +nmblookup
 +can be used to query a WINS server (in the same way
 +nslookup
 +is used to query DNS servers)\&. To query a WINS server,
 +nmblookup
 +must be called like this:
 +.PP
 +nmblookup \-U server \-R \*(Aqname\*(Aq
 +.PP
 +For example, running :
 +.PP
 +nmblookup \-U samba\&.org \-R \*(AqIRIX#1B\*(Aq
 +.PP
 +would query the WINS server samba\&.org for the domain master browser (1B name type) for the IRIX workgroup\&.
 +.SH "VERSION"
 +.PP
 +This man page is correct for version 3 of the Samba suite\&.
 +.SH "SEE ALSO"
 +.PP
 +\fBnmbd\fR(8),
 +\fBsamba\fR(7), and
 +\fBsmb.conf\fR(5)\&.
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
 +.PP
 +The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at
 +ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
diff --cc docs/manpages/ntlm_auth.1
index 74e46de,0000000..b2ddd10
mode 100644,000000..100644
--- a/docs/manpages/ntlm_auth.1
+++ b/docs/manpages/ntlm_auth.1
@@@ -1,419 -1,0 +1,419 @@@
 +'\" t
 +.\"     Title: ntlm_auth
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: User Commands
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "NTLM_AUTH" "1" "12/01/2015" "Samba 4\&.3" "User Commands"
++.TH "NTLM_AUTH" "1" "12/10/2015" "Samba 4\&.3" "User Commands"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +ntlm_auth \- tool to allow external access to Winbind\*(Aqs NTLM authentication function
 +.SH "SYNOPSIS"
 +.HP \w'\ 'u
 +ntlm_auth
 +.SH "DESCRIPTION"
 +.PP
 +This tool is part of the
 +\fBsamba\fR(7)
 +suite\&.
 +.PP
 +ntlm_auth
 +is a helper utility that authenticates users using NT/LM authentication\&. It returns 0 if the users is authenticated successfully and 1 if access was denied\&. ntlm_auth uses winbind to access the user and authentication data for a domain\&. This utility is only intended to be used by other programs (currently
 +Squid
 +and
 +mod_ntlm_winbind)
 +.SH "OPERATIONAL REQUIREMENTS"
 +.PP
 +The
 +\fBwinbindd\fR(8)
 +daemon must be operational for many of these commands to function\&.
 +.PP
 +Some of these commands also require access to the directory
 +winbindd_privileged
 +in
 +$LOCKDIR\&. This should be done either by running this command as root or providing group access to the
 +winbindd_privileged
 +directory\&. For security reasons, this directory should not be world\-accessable\&.
 +.SH "OPTIONS"
 +.PP
 +\-\-helper\-protocol=PROTO
 +.RS 4
 +Operate as a stdio\-based helper\&. Valid helper protocols are:
 +.PP
 +squid\-2\&.4\-basic
 +.RS 4
 +Server\-side helper for use with Squid 2\&.4\*(Aqs basic (plaintext) authentication\&.
 +.RE
 +.PP
 +squid\-2\&.5\-basic
 +.RS 4
 +Server\-side helper for use with Squid 2\&.5\*(Aqs basic (plaintext) authentication\&.
 +.RE
 +.PP
 +squid\-2\&.5\-ntlmssp
 +.RS 4
 +Server\-side helper for use with Squid 2\&.5\*(Aqs NTLMSSP authentication\&.
 +.sp
 +Requires access to the directory
 +winbindd_privileged
 +in
 +$LOCKDIR\&. The protocol used is described here:
 +http://devel\&.squid\-cache\&.org/ntlm/squid_helper_protocol\&.html\&. This protocol has been extended to allow the NTLMSSP Negotiate packet to be included as an argument to the
 +YR
 +command\&. (Thus avoiding loss of information in the protocol exchange)\&.
 +.RE
 +.PP
 +ntlmssp\-client\-1
 +.RS 4
 +Client\-side helper for use with arbitrary external programs that may wish to use Samba\*(Aqs NTLMSSP authentication knowledge\&.
 +.sp
 +This helper is a client, and as such may be run by any user\&. The protocol used is effectively the reverse of the previous protocol\&. A
 +YR
 +command (without any arguments) starts the authentication exchange\&.
 +.RE
 +.PP
 +gss\-spnego
 +.RS 4
 +Server\-side helper that implements GSS\-SPNEGO\&. This uses a protocol that is almost the same as
 +squid\-2\&.5\-ntlmssp, but has some subtle differences that are undocumented outside the source at this stage\&.
 +.sp
 +Requires access to the directory
 +winbindd_privileged
 +in
 +$LOCKDIR\&.
 +.RE
 +.PP
 +gss\-spnego\-client
 +.RS 4
 +Client\-side helper that implements GSS\-SPNEGO\&. This also uses a protocol similar to the above helpers, but is currently undocumented\&.
 +.RE
 +.PP
 +ntlm\-server\-1
 +.RS 4
 +Server\-side helper protocol, intended for use by a RADIUS server or the \*(Aqwinbind\*(Aq plugin for pppd, for the provision of MSCHAP and MSCHAPv2 authentication\&.
 +.sp
 +This protocol consists of lines in the form:
 +Parameter: value
 +and
 +Parameter:: Base64\-encode value\&. The presence of a single period
 +\&.
 +indicates that one side has finished supplying data to the other\&. (Which in turn could cause the helper to authenticate the user)\&.
 +.sp
 +Currently implemented parameters from the external program to the helper are:
 +.PP
 +Username
 +.RS 4
 +The username, expected to be in Samba\*(Aqs
 +\m[blue]\fBunix charset\fR\m[]\&.
 +.PP
 +Examples:
 +.RS 4
 +Username: bob
 +.sp
 +Username:: Ym9i
 +.RE
 +.RE
 +.PP
 +NT\-Domain
 +.RS 4
 +The user\*(Aqs domain, expected to be in Samba\*(Aqs
 +\m[blue]\fBunix charset\fR\m[]\&.
 +.PP
 +Examples:
 +.RS 4
 +NT\-Domain: WORKGROUP
 +.sp
 +NT\-Domain:: V09SS0dST1VQ
 +.RE
 +.RE
 +.PP
 +Full\-Username
 +.RS 4
 +The fully qualified username, expected to be in Samba\*(Aqs
 +\m[blue]\fBunix charset\fR\m[]
 +and qualified with the
 +\m[blue]\fBwinbind separator\fR\m[]\&.
 +.PP
 +Examples:
 +.RS 4
 +Full\-Username: WORKGROUP\ebob
 +.sp
 +Full\-Username:: V09SS0dST1VQYm9i
 +.RE
 +.RE
 +.PP
 +LANMAN\-Challenge
 +.RS 4
 +The 8 byte
 +LANMAN Challenge
 +value, generated randomly by the server, or (in cases such as MSCHAPv2) generated in some way by both the server and the client\&.
 +.PP
 +Examples:
 +.RS 4
 +LANMAN\-Challenge: 0102030405060708
 +.RE
 +.RE
 +.PP
 +LANMAN\-Response
 +.RS 4
 +The 24 byte
 +LANMAN Response
 +value, calculated from the user\*(Aqs password and the supplied
 +LANMAN Challenge\&. Typically, this is provided over the network by a client wishing to authenticate\&.
 +.PP
 +Examples:
 +.RS 4
 +LANMAN\-Response: 0102030405060708090A0B0C0D0E0F101112131415161718
 +.RE
 +.RE
 +.PP
 +NT\-Response
 +.RS 4
 +The >= 24 byte
 +NT Response
 +calculated from the user\*(Aqs password and the supplied
 +LANMAN Challenge\&. Typically, this is provided over the network by a client wishing to authenticate\&.
 +.PP
 +Examples:
 +.RS 4
 +NT\-Response: 0102030405060708090A0B0C0D0E0F10111213141516171
 +.RE
 +.RE
 +.PP
 +Password
 +.RS 4
 +The user\*(Aqs password\&. This would be provided by a network client, if the helper is being used in a legacy situation that exposes plaintext passwords in this way\&.
 +.PP
 +Examples:
 +.RS 4
 +Password: samba2
 +.sp
 +Password:: c2FtYmEy
 +.RE
 +.RE
 +.PP
 +Request\-User\-Session\-Key
 +.RS 4
 +Upon successful authenticaiton, return the user session key associated with the login\&.
 +.PP
 +Examples:
 +.RS 4
 +Request\-User\-Session\-Key: Yes
 +.RE
 +.RE
 +.PP
 +Request\-LanMan\-Session\-Key
 +.RS 4
 +Upon successful authenticaiton, return the LANMAN session key associated with the login\&.
 +.PP
 +Examples:
 +.RS 4
 +Request\-LanMan\-Session\-Key: Yes
 +.RE
 +.RE
 +.RE
 +.sp
 +.if n \{\
 +.sp
 +.\}
 +.RS 4
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBWarning\fR
 +.ps -1
 +.br
 +Implementers should take care to base64 encode any data (such as usernames/passwords) that may contain malicous user data, such as a newline\&. They may also need to decode strings from the helper, which likewise may have been base64 encoded\&.
 +.sp .5v
 +.RE
 +.RE
 +.PP
 +\-\-username=USERNAME
 +.RS 4
 +Specify username of user to authenticate
 +.RE
 +.PP
 +\-\-domain=DOMAIN
 +.RS 4
 +Specify domain of user to authenticate
 +.RE
 +.PP
 +\-\-workstation=WORKSTATION
 +.RS 4
 +Specify the workstation the user authenticated from
 +.RE
 +.PP
 +\-\-challenge=STRING
 +.RS 4
 +NTLM challenge (in HEXADECIMAL)
 +.RE
 +.PP
 +\-\-lm\-response=RESPONSE
 +.RS 4
 +LM Response to the challenge (in HEXADECIMAL)
 +.RE
 +.PP
 +\-\-nt\-response=RESPONSE
 +.RS 4
 +NT or NTLMv2 Response to the challenge (in HEXADECIMAL)
 +.RE
 +.PP
 +\-\-password=PASSWORD
 +.RS 4
 +User\*(Aqs plaintext password
 +.sp
 +If not specified on the command line, this is prompted for when required\&.
 +.sp
 +For the NTLMSSP based server roles, this parameter specifies the expected password, allowing testing without winbindd operational\&.
 +.RE
 +.PP
 +\-\-request\-lm\-key
 +.RS 4
 +Retrieve LM session key
 +.RE
 +.PP
 +\-\-request\-nt\-key
 +.RS 4
 +Request NT key
 +.RE
 +.PP
 +\-\-diagnostics
 +.RS 4
 +Perform Diagnostics on the authentication chain\&. Uses the password from
 +\-\-password
 +or prompts for one\&.
 +.RE
 +.PP
 +\-\-require\-membership\-of={SID|Name}
 +.RS 4
 +Require that a user be a member of specified group (either name or SID) for authentication to succeed\&.
 +.RE
 +.PP
 +\-\-pam\-winbind\-conf=FILENAME
 +.RS 4
 +Define the path to the pam_winbind\&.conf file\&.
 +.RE
 +.PP
 +\-\-target\-hostname=HOSTNAME
 +.RS 4
 +Define the target hostname\&.
 +.RE
 +.PP
 +\-\-target\-service=SERVICE
 +.RS 4
 +Define the target service\&.
 +.RE
 +.PP
 +\-\-use\-cached\-creds
 +.RS 4
 +Whether to use credentials cached by winbindd\&.
 +.RE
 +.PP
 +\-\-configfile=<configuration file>
 +.RS 4
 +The file specified contains the configuration details required by the server\&. The information in this file includes server\-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See
 +smb\&.conf
 +for more information\&. The default configuration file name is determined at compile time\&.
 +.RE
 +.PP
 +\-V|\-\-version
 +.RS 4
 +Prints the program version number\&.
 +.RE
 +.PP
 +\-?|\-\-help
 +.RS 4
 +Print a summary of command line options\&.
 +.RE
 +.PP
 +\-\-usage
 +.RS 4
 +Display brief usage message\&.
 +.RE
 +.SH "EXAMPLE SETUP"
 +.PP
 +To setup ntlm_auth for use by squid 2\&.5, with both basic and NTLMSSP authentication, the following should be placed in the
 +squid\&.conf
 +file\&.
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +auth_param ntlm program ntlm_auth \-\-helper\-protocol=squid\-2\&.5\-ntlmssp
 +auth_param basic program ntlm_auth \-\-helper\-protocol=squid\-2\&.5\-basic
 +auth_param basic children 5
 +auth_param basic realm Squid proxy\-caching web server
 +auth_param basic credentialsttl 2 hours
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.if n \{\
 +.sp
 +.\}
 +.RS 4
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBNote\fR
 +.ps -1
 +.br
 +.PP
 +This example assumes that ntlm_auth has been installed into your path, and that the group permissions on
 +winbindd_privileged
 +are as described above\&.
 +.sp .5v
 +.RE
 +.PP
 +To setup ntlm_auth for use by squid 2\&.5 with group limitation in addition to the above example, the following should be added to the
 +squid\&.conf
 +file\&.
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +auth_param ntlm program ntlm_auth \-\-helper\-protocol=squid\-2\&.5\-ntlmssp \-\-require\-membership\-of=\*(AqWORKGROUP\eDomain Users\*(Aq
 +auth_param basic program ntlm_auth \-\-helper\-protocol=squid\-2\&.5\-basic \-\-require\-membership\-of=\*(AqWORKGROUP\eDomain Users\*(Aq
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.SH "TROUBLESHOOTING"
 +.PP
 +If you\*(Aqre experiencing problems with authenticating Internet Explorer running under MS Windows 9X or Millennium Edition against ntlm_auth\*(Aqs NTLMSSP authentication helper (\-\-helper\-protocol=squid\-2\&.5\-ntlmssp), then please read
 +the Microsoft Knowledge Base article #239869 and follow instructions described there\&.
 +.SH "VERSION"
 +.PP
 +This man page is correct for version 3 of the Samba suite\&.
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
 +.PP
 +The ntlm_auth manpage was written by Jelmer Vernooij and Andrew Bartlett\&.
diff --cc docs/manpages/pam_winbind.8
index 972ee07,0000000..7ae4fd9
mode 100644,000000..100644
--- a/docs/manpages/pam_winbind.8
+++ b/docs/manpages/pam_winbind.8
@@@ -1,180 -1,0 +1,180 @@@
 +'\" t
 +.\"     Title: pam_winbind
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: 8
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "PAM_WINBIND" "8" "12/01/2015" "Samba 4\&.3" "8"
++.TH "PAM_WINBIND" "8" "12/10/2015" "Samba 4\&.3" "8"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +pam_winbind \- PAM module for Winbind
 +.SH "DESCRIPTION"
 +.PP
 +This tool is part of the
 +\fBsamba\fR(7)
 +suite\&.
 +.PP
 +pam_winbind is a PAM module that can authenticate users against the local domain by talking to the Winbind daemon\&.
 +.SH "SYNOPSIS"
 +.PP
 +Edit the PAM system config /etc/pam\&.d/service and modify it as the following example shows:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +			    \&.\&.\&.
 +			    auth      required        pam_env\&.so
 +			    auth      sufficient      pam_unix2\&.so
 +			+++ auth      required        pam_winbind\&.so  use_first_pass
 +			    account   requisite       pam_unix2\&.so
 +			+++ account   required        pam_winbind\&.so  use_first_pass
 +			+++ password  sufficient      pam_winbind\&.so
 +			    password  requisite       pam_pwcheck\&.so  cracklib
 +			    password  required        pam_unix2\&.so    use_authtok
 +			    session   required        pam_unix2\&.so
 +			+++ session   required        pam_winbind\&.so
 +			    \&.\&.\&.
 +		
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.sp
 +Make sure that pam_winbind is one of the first modules in the session part\&. It may retrieve kerberos tickets which are needed by other modules\&.
 +.SH "OPTIONS"
 +.PP
 +pam_winbind supports several options which can either be set in the PAM configuration files or in the pam_winbind configuration file situated at
 +/etc/security/pam_winbind\&.conf\&. Options from the PAM configuration file take precedence to those from the configuration file\&. See
 +\fBpam_winbind.conf\fR(5)
 +for further details\&.
 +.PP
 +debug
 +.RS 4
 +Gives debugging output to syslog\&.
 +.RE
 +.PP
 +debug_state
 +.RS 4
 +Gives detailed PAM state debugging output to syslog\&.
 +.RE
 +.PP
 +require_membership_of=[SID or NAME]
 +.RS 4
 +If this option is set, pam_winbind will only succeed if the user is a member of the given SID or NAME\&. A SID can be either a group\-SID, an alias\-SID or even an user\-SID\&. It is also possible to give a NAME instead of the SID\&. That name must have the form:
 +\fIMYDOMAIN\e\emygroup\fR
 +or
 +\fIMYDOMAIN\e\emyuser\fR\&. pam_winbind will, in that case, lookup the SID internally\&. Note that NAME may not contain any spaces\&. It is thus recommended to only use SIDs\&. You can verify the list of SIDs a user is a member of with
 +wbinfo \-\-user\-sids=SID\&.
 +.sp
 +This option must only be specified on a auth module declaration, as it only operates in conjunction with password authentication\&.
 +.RE
 +.PP
 +use_first_pass
 +.RS 4
 +By default, pam_winbind tries to get the authentication token from a previous module\&. If no token is available it asks the user for the old password\&. With this option, pam_winbind aborts with an error if no authentication token from a previous module is available\&.
 +.RE
 +.PP
 +try_first_pass
 +.RS 4
 +Same as the use_first_pass option (previous item), except that if the primary password is not valid, PAM will prompt for a password\&.
 +.RE
 +.PP
 +use_authtok
 +.RS 4
 +Set the new password to the one provided by the previously stacked password module\&. If this option is not set pam_winbind will ask the user for the new password\&.
 +.RE
 +.PP
 +krb5_auth
 +.RS 4
 +pam_winbind can authenticate using Kerberos when winbindd is talking to an Active Directory domain controller\&. Kerberos authentication must be enabled with this parameter\&. When Kerberos authentication can not succeed (e\&.g\&. due to clock skew), winbindd will fallback to samlogon authentication over MSRPC\&. When this parameter is used in conjunction with
 +\fIwinbind refresh tickets\fR, winbind will keep your Ticket Granting Ticket (TGT) uptodate by refreshing it whenever necessary\&.
 +.RE
 +.PP
 +krb5_ccache_type=[type]
 +.RS 4
 +When pam_winbind is configured to try kerberos authentication by enabling the
 +\fIkrb5_auth\fR
 +option, it can store the retrieved Ticket Granting Ticket (TGT) in a credential cache\&. The type of credential cache can be set with this option\&. Currently the only supported value is:
 +\fIFILE\fR\&. In that case a credential cache in the form of /tmp/krb5cc_UID will be created, where UID is replaced with the numeric user id\&. Leave empty to just do kerberos authentication without having a ticket cache after the logon has succeeded\&.
 +.RE
 +.PP
 +cached_login
 +.RS 4
 +Winbind allows to logon using cached credentials when
 +\fIwinbind offline logon\fR
 +is enabled\&. To use this feature from the PAM module this option must be set\&.
 +.RE
 +.PP
 +silent
 +.RS 4
 +Do not emit any messages\&.
 +.RE
 +.PP
 +mkhomedir
 +.RS 4
 +Create homedirectory for a user on\-the\-fly, option is valid in PAM session block\&.
 +.RE
 +.PP
 +warn_pwd_expire
 +.RS 4
 +Defines number of days before pam_winbind starts to warn about passwords that are going to expire\&. Defaults to 14 days\&.
 +.RE
 +.SH "PAM DATA EXPORTS"
 +.PP
 +This section describes the data exported in the PAM stack which could be used in other PAM modules\&.
 +.PP
 +PAM_WINBIND_HOMEDIR
 +.RS 4
 +This is the Windows Home Directory set in the profile tab in the user settings on the Active Directory Server\&. This could be a local path or a directory on a share mapped to a drive\&.
 +.RE
 +.PP
 +PAM_WINBIND_LOGONSCRIPT
 +.RS 4
 +The path to the logon script which should be executed if a user logs in\&. This is normally a relative path to the script stored on the server\&.
 +.RE
 +.PP
 +PAM_WINBIND_LOGONSERVER
 +.RS 4
 +This exports the Active Directory server we are authenticating against\&. This can be used as a variable later\&.
 +.RE
 +.PP
 +PAM_WINBIND_PROFILEPATH
 +.RS 4
 +This is the profile path set in the profile tab in the user settings\&. Normally the home directory is synced with this directory on a share\&.
 +.RE
 +.SH "SEE ALSO"
 +.PP
 +\fBpam_winbind.conf\fR(5),
 +\fBwbinfo\fR(1),
 +\fBwinbindd\fR(8),
 +\fBsmb.conf\fR(5)
 +.SH "VERSION"
 +.PP
 +This man page is correct for version 3 of Samba\&.
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
 +.PP
 +This manpage was written by Jelmer Vernooij and Guenther Deschner\&.
diff --cc docs/manpages/pam_winbind.conf.5
index a8d2a3a,0000000..f7a3554
mode 100644,000000..100644
--- a/docs/manpages/pam_winbind.conf.5
+++ b/docs/manpages/pam_winbind.conf.5
@@@ -1,145 -1,0 +1,145 @@@
 +'\" t
 +.\"     Title: pam_winbind.conf
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: 5
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "PAM_WINBIND\&.CONF" "5" "12/01/2015" "Samba 4\&.3" "5"
++.TH "PAM_WINBIND\&.CONF" "5" "12/10/2015" "Samba 4\&.3" "5"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +pam_winbind.conf \- Configuration file of PAM module for Winbind
 +.SH "DESCRIPTION"
 +.PP
 +This configuration file is part of the
 +\fBsamba\fR(7)
 +suite\&.
 +.PP
 +pam_winbind\&.conf is the configuration file for the pam_winbind PAM module\&. See
 +\fBpam_winbind\fR(8)
 +for further details\&.
 +.SH "SYNOPSIS"
 +.PP
 +The pam_winbind\&.conf configuration file is a classic ini\-style configuration file\&. There is only one section (global) where various options are defined\&.
 +.SH "OPTIONS"
 +.PP
 +pam_winbind supports several options which can either be set in the PAM configuration files or in the pam_winbind configuration file situated at
 +/etc/security/pam_winbind\&.conf\&. Options from the PAM configuration file take precedence to those from the pam_winbind\&.conf configuration file\&.
 +.PP
 +debug = yes|no
 +.RS 4
 +Gives debugging output to syslog\&. Defaults to "no"\&.
 +.RE
 +.PP
 +debug_state = yes|no
 +.RS 4
 +Gives detailed PAM state debugging output to syslog\&. Defaults to "no"\&.
 +.RE
 +.PP
 +require_membership_of = [SID or NAME]
 +.RS 4
 +If this option is set, pam_winbind will only succeed if the user is a member of the given SID or NAME\&. A SID can be either a group\-SID, an alias\-SID or even an user\-SID\&. It is also possible to give a NAME instead of the SID\&. That name must have the form:
 +\fIMYDOMAIN\e\emygroup\fR
 +or
 +\fIMYDOMAIN\e\emyuser\fR\&. pam_winbind will, in that case, lookup the SID internally\&. Note that NAME may not contain any spaces\&. It is thus recommended to only use SIDs\&. You can verify the list of SIDs a user is a member of with
 +wbinfo \-\-user\-sids=SID\&. This setting is empty by default\&.
 +.sp
 +This option only operates during password authentication, and will not restrict access if a password is not required for any reason (such as SSH key\-based login)\&.
 +.RE
 +.PP
 +try_first_pass = yes|no
 +.RS 4
 +By default, pam_winbind tries to get the authentication token from a previous module\&. If no token is available it asks the user for the old password\&. With this option, pam_winbind aborts with an error if no authentication token from a previous module is available\&. If a primary password is not valid, PAM will prompt for a password\&. Default to "no"\&.
 +.RE
 +.PP
 +krb5_auth = yes|no
 +.RS 4
 +pam_winbind can authenticate using Kerberos when winbindd is talking to an Active Directory domain controller\&. Kerberos authentication must be enabled with this parameter\&. When Kerberos authentication can not succeed (e\&.g\&. due to clock skew), winbindd will fallback to samlogon authentication over MSRPC\&. When this parameter is used in conjunction with
 +\fIwinbind refresh tickets\fR, winbind will keep your Ticket Granting Ticket (TGT) uptodate by refreshing it whenever necessary\&. Defaults to "no"\&.
 +.RE
 +.PP
 +krb5_ccache_type = [type]
 +.RS 4
 +When pam_winbind is configured to try kerberos authentication by enabling the
 +\fIkrb5_auth\fR
 +option, it can store the retrieved Ticket Granting Ticket (TGT) in a credential cache\&. The type of credential cache can be controlled with this option\&. The supported values are:
 +\fIKEYRING\fR
 +(when supported by the system\*(Aqs Kerberos library and Kernel),
 +\fIFILE\fR
 +and
 +\fIDIR\fR
 +(when the DIR type is supported by the system\*(Aqs Kerberos library)\&. In case of FILE a credential cache in the form of /tmp/krb5cc_UID will be created \- in case of DIR you NEED to specify a directory\&. UID is replaced with the numeric user id\&.
 +.sp
 +When using the KEYRING type, the supported mechanism is
 +\(lqKEYRING:persistent:UID\(rq, which uses the Linux kernel keyring to store credentials on a per\-UID basis\&. This is the recommended choice on latest Linux distributions, as it is the most secure and predictable method\&.
 +.sp
 +It is also possible to define custom filepaths and use the "%u" pattern in order to substitue the numeric user id\&. Examples:
 +.PP
 +krb5_ccache_type = DIR:/run/user/%u/krb5cc
 +.RS 4
 +This will create a credential cache file in the specified directory\&.
 +.RE
 +.PP
 +krb5_ccache_type = FILE:/tmp/krb5cc_%u
 +.RS 4
 +This will create a credential cache file\&.
 +.RE
 +.sp
 +Leave empty to just do kerberos authentication without having a ticket cache after the logon has succeeded\&. This setting is empty by default\&.
 +.RE
 +.PP
 +cached_login = yes|no
 +.RS 4
 +Winbind allows to logon using cached credentials when
 +\fIwinbind offline logon\fR
 +is enabled\&. To use this feature from the PAM module this option must be set\&. Defaults to "no"\&.
 +.RE
 +.PP
 +silent = yes|no
 +.RS 4
 +Do not emit any messages\&. Defaults to "no"\&.
 +.RE
 +.PP
 +mkhomedir = yes|no
 +.RS 4
 +Create homedirectory for a user on\-the\-fly, option is valid in PAM session block\&. Defaults to "no"\&.
 +.RE
 +.PP
 +warn_pwd_expire = days
 +.RS 4
 +Defines number of days before pam_winbind starts to warn about passwords that are going to expire\&. Defaults to 14 days\&.
 +.RE
 +.SH "SEE ALSO"
 +.PP
 +\fBpam_winbind\fR(8),
 +\fBwbinfo\fR(1),
 +\fBwinbindd\fR(8),
 +\fBsmb.conf\fR(5)
 +.SH "VERSION"
 +.PP
 +This man page is correct for version 3 of Samba\&.
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
 +.PP
 +This manpage was written by Jelmer Vernooij and Guenther Deschner\&.
diff --cc docs/manpages/pdbedit.8
index 6ff4e19,0000000..6709a43
mode 100644,000000..100644
--- a/docs/manpages/pdbedit.8
+++ b/docs/manpages/pdbedit.8
@@@ -1,621 -1,0 +1,621 @@@
 +'\" t
 +.\"     Title: pdbedit
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: System Administration tools
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "PDBEDIT" "8" "12/01/2015" "Samba 4\&.3" "System Administration tools"
++.TH "PDBEDIT" "8" "12/10/2015" "Samba 4\&.3" "System Administration tools"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +pdbedit \- manage the SAM database (Database of Samba Users)
 +.SH "SYNOPSIS"
 +.HP \w'\ 'u
 +pdbedit [\-a] [\-b\ passdb\-backend] [\-c\ account\-control] [\-C\ value] [\-d\ debuglevel] [\-D\ drive] [\-e\ passdb\-backend] [\-f\ fullname] [\-\-force\-initialized\-passwords] [\-g] [\-h\ homedir] [\-i\ passdb\-backend] [\-I\ domain] [\-K] [\-L] [\-m] [\-M\ SID|RID] [\-N\ description] [\-P\ account\-policy] [\-p\ profile] [\-\-policies\-reset] [\-r] [\-s\ configfile] [\-S\ script] [\-t] [\-\-time\-format] [\-u\ username] [\-U\ SID|RID] [\-v] [\-V] [\-w] [\-x] [\-y] [\-z] [\-Z]
 +.SH "DESCRIPTION"
 +.PP
 +This tool is part of the
 +\fBsamba\fR(7)
 +suite\&.
 +.PP
 +The pdbedit program is used to manage the users accounts stored in the sam database and can only be run by root\&.
 +.PP
 +The pdbedit tool uses the passdb modular interface and is independent from the kind of users database used (currently there are smbpasswd, ldap, nis+ and tdb based and more can be added without changing the tool)\&.
 +.PP
 +There are five main ways to use pdbedit: adding a user account, removing a user account, modifying a user account, listing user accounts, importing users accounts\&.
 +.SH "OPTIONS"
 +.PP
 +\-L|\-\-list
 +.RS 4
 +This option lists all the user accounts present in the users database\&. This option prints a list of user/uid pairs separated by the \*(Aq:\*(Aq character\&.
 +.sp
 +Example:
 +pdbedit \-L
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +sorce:500:Simo Sorce
 +samba:45:Test User
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.PP
 +\-v|\-\-verbose
 +.RS 4
 +This option enables the verbose listing format\&. It causes pdbedit to list the users in the database, printing out the account fields in a descriptive format\&.
 +.sp
 +Example:
 +pdbedit \-L \-v
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
 +username:       sorce
 +user ID/Group:  500/500
 +user RID/GRID:  2000/2001
 +Full Name:      Simo Sorce
 +Home Directory: \e\eBERSERKER\esorce
 +HomeDir Drive:  H:
 +Logon Script:   \e\eBERSERKER\enetlogon\esorce\&.bat
 +Profile Path:   \e\eBERSERKER\eprofile
 +\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
 +username:       samba
 +user ID/Group:  45/45
 +user RID/GRID:  1090/1091
 +Full Name:      Test User
 +Home Directory: \e\eBERSERKER\esamba
 +HomeDir Drive:  
 +Logon Script:   
 +Profile Path:   \e\eBERSERKER\eprofile
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.PP
 +\-w|\-\-smbpasswd\-style
 +.RS 4
 +This option sets the "smbpasswd" listing format\&. It will make pdbedit list the users in the database, printing out the account fields in a format compatible with the
 +smbpasswd
 +file format\&. (see the
 +\fBsmbpasswd\fR(5)
 +for details)
 +.sp
 +Example:
 +pdbedit \-L \-w
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +sorce:500:508818B733CE64BEAAD3B435B51404EE:
 +          D2A2418EFC466A8A0F6B1DBB5C3DB80C:
 +          [UX         ]:LCT\-00000000:
 +samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:
 +          BC281CE3F53B6A5146629CD4751D3490:
 +          [UX         ]:LCT\-3BFA1E8D:
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.PP
 +\-u|\-\-user username
 +.RS 4
 +This option specifies the username to be used for the operation requested (listing, adding, removing)\&. It is
 +\fIrequired\fR
 +in add, remove and modify operations and
 +\fIoptional\fR
 +in list operations\&.
 +.RE
 +.PP
 +\-f|\-\-fullname fullname
 +.RS 4
 +This option can be used while adding or modifying a user account\&. It will specify the user\*(Aqs full name\&.
 +.sp
 +Example:
 +\-f "Simo Sorce"
 +.RE
 +.PP
 +\-h|\-\-homedir homedir
 +.RS 4
 +This option can be used while adding or modifying a user account\&. It will specify the user\*(Aqs home directory network path\&.
 +.sp
 +Example:
 +\-h "\e\e\e\eBERSERKER\e\esorce"
 +.RE
 +.PP
 +\-D|\-\-drive drive
 +.RS 4
 +This option can be used while adding or modifying a user account\&. It will specify the windows drive letter to be used to map the home directory\&.
 +.sp
 +Example:
 +\-D "H:"
 +.RE
 +.PP
 +\-S|\-\-script script
 +.RS 4
 +This option can be used while adding or modifying a user account\&. It will specify the user\*(Aqs logon script path\&.
 +.sp
 +Example:
 +\-S "\e\e\e\eBERSERKER\e\enetlogon\e\esorce\&.bat"
 +.RE
 +.PP
 +\-p|\-\-profile profile
 +.RS 4
 +This option can be used while adding or modifying a user account\&. It will specify the user\*(Aqs profile directory\&.
 +.sp
 +Example:
 +\-p "\e\e\e\eBERSERKER\e\enetlogon"
 +.RE
 +.PP
 +\-M|\*(Aq\-\-machine SID\*(Aq SID|rid
 +.RS 4
 +This option can be used while adding or modifying a machine account\&. It will specify the machines\*(Aq new primary group SID (Security Identifier) or rid\&.
 +.sp
 +Example:
 +\-M S\-1\-5\-21\-2447931902\-1787058256\-3961074038\-1201
 +.RE
 +.PP
 +\-U|\*(Aq\-\-user SID\*(Aq SID|rid
 +.RS 4
 +This option can be used while adding or modifying a user account\&. It will specify the users\*(Aq new SID (Security Identifier) or rid\&.
 +.sp
 +Example:
 +\-U S\-1\-5\-21\-2447931902\-1787058256\-3961074038\-5004
 +.sp
 +Example:
 +\*(Aq\-\-user SID\*(Aq S\-1\-5\-21\-2447931902\-1787058256\-3961074038\-5004
 +.sp
 +Example:
 +\-U 5004
 +.sp
 +Example:
 +\*(Aq\-\-user SID\*(Aq 5004
 +.RE
 +.PP
 +\-c|\-\-account\-control account\-control
 +.RS 4
 +This option can be used while adding or modifying a user account\&. It will specify the users\*(Aq account control property\&. Possible flags are listed below\&.
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +N: No password required
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +D: Account disabled
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +H: Home directory required
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +T: Temporary duplicate of other account
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +U: Regular user account
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +M: MNS logon user account
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +W: Workstation Trust Account
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +S: Server Trust Account
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +L: Automatic Locking
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +X: Password does not expire
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +I: Domain Trust Account
 +.RE
 +.sp
 +.RE
 +.sp
 +Example:
 +\-c "[X ]"
 +.RE
 +.PP
 +\-K|\-\-kickoff\-time
 +.RS 4
 +This option is used to modify the kickoff time for a certain user\&. Use "never" as argument to set the kickoff time to unlimited\&.
 +.sp
 +Example:
 +pdbedit \-K never user
 +.RE
 +.PP
 +\-a|\-\-create
 +.RS 4
 +This option is used to add a user into the database\&. This command needs a user name specified with the \-u switch\&. When adding a new user, pdbedit will also ask for the password to be used\&.
 +.sp
 +Example:
 +pdbedit \-a \-u sorce
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +new password:
 +retype new password
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.sp
 +.if n \{\
 +.sp
 +.\}
 +.RS 4
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBNote\fR
 +.ps -1
 +.br
 +pdbedit does not call the unix password synchronization script if
 +\m[blue]\fBunix password sync\fR\m[]
 +has been set\&. It only updates the data in the Samba user database\&.
 +.sp
 +If you wish to add a user and synchronise the password that immediately, use
 +smbpasswd\*(Aqs
 +\fB\-a\fR
 +option\&.
 +.sp .5v
 +.RE
 +.RE
 +.PP
 +\-t|\-\-password\-from\-stdin
 +.RS 4
 +This option causes pdbedit to read the password from standard input, rather than from /dev/tty (like the
 +passwd(1)
 +program does)\&. The password has to be submitted twice and terminated by a newline each\&.
 +.RE
 +.PP
 +\-r|\-\-modify
 +.RS 4
 +This option is used to modify an existing user in the database\&. This command needs a user name specified with the \-u switch\&. Other options can be specified to modify the properties of the specified user\&. This flag is kept for backwards compatibility, but it is no longer necessary to specify it\&.
 +.RE
 +.PP
 +\-m|\-\-machine
 +.RS 4
 +This option may only be used in conjunction with the
 +\fI\-a\fR
 +option\&. It will make pdbedit to add a machine trust account instead of a user account (\-u username will provide the machine name)\&.
 +.sp
 +Example:
 +pdbedit \-a \-m \-u w2k\-wks
 +.RE
 +.PP
 +\-x|\-\-delete
 +.RS 4
 +This option causes pdbedit to delete an account from the database\&. It needs a username specified with the \-u switch\&.
 +.sp
 +Example:
 +pdbedit \-x \-u bob
 +.RE
 +.PP
 +\-i|\-\-import passdb\-backend
 +.RS 4
 +Use a different passdb backend to retrieve users than the one specified in smb\&.conf\&. Can be used to import data into your local user database\&.
 +.sp
 +This option will ease migration from one passdb backend to another\&.
 +.sp
 +Example:
 +pdbedit \-i smbpasswd:/etc/smbpasswd\&.old
 +.RE
 +.PP
 +\-e|\-\-export passdb\-backend
 +.RS 4
 +Exports all currently available users to the specified password database backend\&.
 +.sp
 +This option will ease migration from one passdb backend to another and will ease backing up\&.
 +.sp
 +Example:
 +pdbedit \-e smbpasswd:/root/samba\-users\&.backup
 +.RE
 +.PP
 +\-g|\-\-group
 +.RS 4
 +If you specify
 +\fI\-g\fR, then
 +\fI\-i in\-backend \-e out\-backend\fR
 +applies to the group mapping instead of the user database\&.
 +.sp
 +This option will ease migration from one passdb backend to another and will ease backing up\&.
 +.RE
 +.PP
 +\-b|\-\-backend passdb\-backend
 +.RS 4
 +Use a different default passdb backend\&.
 +.sp
 +Example:
 +pdbedit \-b xml:/root/pdb\-backup\&.xml \-l
 +.RE
 +.PP
 +\-P|\-\-account\-policy account\-policy
 +.RS 4
 +Display an account policy
 +.sp
 +Valid policies are: minimum password age, reset count minutes, disconnect time, user must logon to change password, password history, lockout duration, min password length, maximum password age and bad lockout attempt\&.
 +.sp
 +Example:
 +pdbedit \-P "bad lockout attempt"
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +account policy value for bad lockout attempt is 0
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.PP
 +\-C|\-\-value account\-policy\-value
 +.RS 4
 +Sets an account policy to a specified value\&. This option may only be used in conjunction with the
 +\fI\-P\fR
 +option\&.
 +.sp
 +Example:
 +pdbedit \-P "bad lockout attempt" \-C 3
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +account policy value for bad lockout attempt was 0
 +account policy value for bad lockout attempt is now 3
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.RE
 +.PP
 +\-y|\-\-policies
 +.RS 4
 +If you specify
 +\fI\-y\fR, then
 +\fI\-i in\-backend \-e out\-backend\fR
 +applies to the account policies instead of the user database\&.
 +.sp
 +This option will allow to migrate account policies from their default tdb\-store into a passdb backend, e\&.g\&. an LDAP directory server\&.
 +.sp
 +Example:
 +pdbedit \-y \-i tdbsam: \-e ldapsam:ldap://my\&.ldap\&.host
 +.RE
 +.PP
 +\-\-force\-initialized\-passwords
 +.RS 4
 +This option forces all users to change their password upon next login\&.
 +.RE
 +.PP
 +\-N|\-\-account\-desc description
 +.RS 4
 +This option can be used while adding or modifying a user account\&. It will specify the user\*(Aqs description field\&.
 +.sp
 +Example:
 +\-N "test description"
 +.RE
 +.PP
 +\-Z|\-\-logon\-hours\-reset
 +.RS 4
 +This option can be used while adding or modifying a user account\&. It will reset the user\*(Aqs allowed logon hours\&. A user may login at any time afterwards\&.
 +.sp
 +Example:
 +\-Z
 +.RE
 +.PP
 +\-z|\-\-bad\-password\-count\-reset
 +.RS 4
 +This option can be used while adding or modifying a user account\&. It will reset the stored bad login counter from a specified user\&.
 +.sp
 +Example:
 +\-z
 +.RE
 +.PP
 +\-\-policies\-reset
 +.RS 4
 +This option can be used to reset the general password policies stored for a domain to their default values\&.
 +.sp
 +Example:
 +\-\-policies\-reset
 +.RE
 +.PP
 +\-I|\-\-domain
 +.RS 4
 +This option can be used while adding or modifying a user account\&. It will specify the user\*(Aqs domain field\&.
 +.sp
 +Example:
 +\-I "MYDOMAIN"
 +.RE
 +.PP
 +\-\-time\-format
 +.RS 4
 +This option is currently not being used\&.
 +.RE
 +.PP
 +\-?|\-\-help
 +.RS 4
 +Print a summary of command line options\&.
 +.RE
 +.PP
 +\-\-usage
 +.RS 4
 +Display brief usage message\&.
 +.RE
 +.PP
 +\-d|\-\-debuglevel=level
 +.RS 4
 +\fIlevel\fR
 +is an integer from 0 to 10\&. The default value if this parameter is not specified is 0\&.
 +.sp
 +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day\-to\-day running \- it generates a small amount of information about operations carried out\&.
 +.sp
 +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&.
 +.sp
 +Note that specifying this parameter here will override the
 +\m[blue]\fBlog level\fR\m[]
 +parameter in the
 +smb\&.conf
 +file\&.
 +.RE
 +.PP
 +\-V|\-\-version
 +.RS 4
 +Prints the program version number\&.
 +.RE
 +.PP
 +\-s|\-\-configfile=<configuration file>
 +.RS 4
 +The file specified contains the configuration details required by the server\&. The information in this file includes server\-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See
 +smb\&.conf
 +for more information\&. The default configuration file name is determined at compile time\&.
 +.RE
 +.PP
 +\-l|\-\-log\-basename=logdirectory
 +.RS 4
 +Base directory name for log/debug files\&. The extension
 +\fB"\&.progname"\fR
 +will be appended (e\&.g\&. log\&.smbclient, log\&.smbd, etc\&.\&.\&.)\&. The log file is never removed by the client\&.
 +.RE
 +.PP
 +\-\-option=<name>=<value>
 +.RS 4
 +Set the
 +\fBsmb.conf\fR(5)
 +option "<name>" to value "<value>" from the command line\&. This overrides compiled\-in defaults and options read from the configuration file\&.
 +.RE
 +.SH "NOTES"
 +.PP
 +This command may be used only by root\&.
 +.SH "VERSION"
 +.PP
 +This man page is correct for version 3 of the Samba suite\&.
 +.SH "SEE ALSO"
 +.PP
 +\fBsmbpasswd\fR(5),
 +\fBsamba\fR(7)
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
 +.PP
 +The pdbedit manpage was written by Simo Sorce and Jelmer Vernooij\&.
diff --cc docs/manpages/profiles.1
index 523b753,0000000..9570215
mode 100644,000000..100644
--- a/docs/manpages/profiles.1
+++ b/docs/manpages/profiles.1
@@@ -1,120 -1,0 +1,120 @@@
 +'\" t
 +.\"     Title: profiles
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: User Commands
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "PROFILES" "1" "12/01/2015" "Samba 4\&.3" "User Commands"
++.TH "PROFILES" "1" "12/10/2015" "Samba 4\&.3" "User Commands"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +profiles \- A utility to report and change SIDs in registry files
 +.SH "SYNOPSIS"
 +.HP \w'\ 'u
 +profiles [\-v] [\-c|\-\-change\-sid\ SID] [\-n|\-\-new\-sid\ SID] {file}
 +.SH "DESCRIPTION"
 +.PP
 +This tool is part of the
 +\fBsamba\fR(7)
 +suite\&.
 +.PP
 +profiles
 +is a utility that reports and changes SIDs in windows registry files\&. It currently only supports NT\&.
 +.SH "OPTIONS"
 +.PP
 +file
 +.RS 4
 +Registry file to view or edit\&.
 +.RE
 +.PP
 +\-v,\-\-verbose
 +.RS 4
 +Increases verbosity of messages\&.
 +.RE
 +.PP
 +\-c SID1 \-n SID2, \-\-change\-sid SID1 \-\-new\-sid SID2
 +.RS 4
 +Change all occurrences of SID1 in
 +file
 +by SID2\&.
 +.RE
 +.PP
 +\-d|\-\-debuglevel=level
 +.RS 4
 +\fIlevel\fR
 +is an integer from 0 to 10\&. The default value if this parameter is not specified is 1\&.
 +.sp
 +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day\-to\-day running \- it generates a small amount of information about operations carried out\&.
 +.sp
 +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&.
 +.sp
 +Note that specifying this parameter here will override the
 +\m[blue]\fBlog level\fR\m[]
 +parameter in the
 +smb\&.conf
 +file\&.
 +.RE
 +.PP
 +\-V|\-\-version
 +.RS 4
 +Prints the program version number\&.
 +.RE
 +.PP
 +\-s|\-\-configfile=<configuration file>
 +.RS 4
 +The file specified contains the configuration details required by the server\&. The information in this file includes server\-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See
 +smb\&.conf
 +for more information\&. The default configuration file name is determined at compile time\&.
 +.RE
 +.PP
 +\-l|\-\-log\-basename=logdirectory
 +.RS 4
 +Base directory name for log/debug files\&. The extension
 +\fB"\&.progname"\fR
 +will be appended (e\&.g\&. log\&.smbclient, log\&.smbd, etc\&.\&.\&.)\&. The log file is never removed by the client\&.
 +.RE
 +.PP
 +\-\-option=<name>=<value>
 +.RS 4
 +Set the
 +\fBsmb.conf\fR(5)
 +option "<name>" to value "<value>" from the command line\&. This overrides compiled\-in defaults and options read from the configuration file\&.
 +.RE
 +.PP
 +\-?|\-\-help
 +.RS 4
 +Print a summary of command line options\&.
 +.RE
 +.PP
 +\-\-usage
 +.RS 4
 +Display brief usage message\&.
 +.RE
 +.SH "VERSION"
 +.PP
 +This man page is correct for version 3 of the Samba suite\&.
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
 +.PP
 +The profiles man page was written by Jelmer Vernooij\&.
diff --cc docs/manpages/rpcclient.1
index cdafca8,0000000..a9e68f6
mode 100644,000000..100644
--- a/docs/manpages/rpcclient.1
+++ b/docs/manpages/rpcclient.1
@@@ -1,811 -1,0 +1,811 @@@
 +'\" t
 +.\"     Title: rpcclient
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: User Commands
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "RPCCLIENT" "1" "12/01/2015" "Samba 4\&.3" "User Commands"
++.TH "RPCCLIENT" "1" "12/10/2015" "Samba 4\&.3" "User Commands"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +rpcclient \- tool for executing client side MS\-RPC functions
 +.SH "SYNOPSIS"
 +.HP \w'\ 'u
 +rpcclient [\-A\ authfile] [\-c\ <command\ string>] [\-d\ debuglevel] [\-l\ logdir] [\-N] [\-s\ <smb\ config\ file>] [\-U\ username[%password]] [\-W\ workgroup] [\-I\ destinationIP] {server}
 +.SH "DESCRIPTION"
 +.PP
 +This tool is part of the
 +\fBsamba\fR(7)
 +suite\&.
 +.PP
 +rpcclient
 +is a utility initially developed to test MS\-RPC functionality in Samba itself\&. It has undergone several stages of development and stability\&. Many system administrators have now written scripts around it to manage Windows NT clients from their UNIX workstation\&.
 +.SH "OPTIONS"
 +.PP
 +server
 +.RS 4
 +NetBIOS name of Server to which to connect\&. The server can be any SMB/CIFS server\&. The name is resolved using the
 +\m[blue]\fBname resolve order\fR\m[]
 +line from
 +\fBsmb.conf\fR(5)\&.
 +.RE
 +.PP
 +\-c|\-\-command=<command string>
 +.RS 4
 +Execute semicolon separated commands (listed below)
 +.RE
 +.PP
 +\-I|\-\-dest\-ip IP\-address
 +.RS 4
 +\fIIP address\fR
 +is the address of the server to connect to\&. It should be specified in standard "a\&.b\&.c\&.d" notation\&.
 +.sp
 +Normally the client would attempt to locate a named SMB/CIFS server by looking it up via the NetBIOS name resolution mechanism described above in the
 +\fIname resolve order\fR
 +parameter above\&. Using this parameter will force the client to assume that the server is on the machine with the specified IP address and the NetBIOS name component of the resource being connected to will be ignored\&.
 +.sp
 +There is no default for this parameter\&. If not supplied, it will be determined automatically by the client as described above\&.
 +.RE
 +.PP
 +\-p|\-\-port port
 +.RS 4
 +This number is the TCP port number that will be used when making connections to the server\&. The standard (well\-known) TCP port number for an SMB/CIFS server is 139, which is the default\&.
 +.RE
 +.PP
 +\-d|\-\-debuglevel=level
 +.RS 4
 +\fIlevel\fR
 +is an integer from 0 to 10\&. The default value if this parameter is not specified is 0\&.
 +.sp
 +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day\-to\-day running \- it generates a small amount of information about operations carried out\&.
 +.sp
 +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&.
 +.sp
 +Note that specifying this parameter here will override the
 +\m[blue]\fBlog level\fR\m[]
 +parameter in the
 +smb\&.conf
 +file\&.
 +.RE
 +.PP
 +\-V|\-\-version
 +.RS 4
 +Prints the program version number\&.
 +.RE
 +.PP
 +\-s|\-\-configfile=<configuration file>
 +.RS 4
 +The file specified contains the configuration details required by the server\&. The information in this file includes server\-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See
 +smb\&.conf
 +for more information\&. The default configuration file name is determined at compile time\&.
 +.RE
 +.PP
 +\-l|\-\-log\-basename=logdirectory
 +.RS 4
 +Base directory name for log/debug files\&. The extension
 +\fB"\&.progname"\fR
 +will be appended (e\&.g\&. log\&.smbclient, log\&.smbd, etc\&.\&.\&.)\&. The log file is never removed by the client\&.
 +.RE
 +.PP
 +\-\-option=<name>=<value>
 +.RS 4
 +Set the
 +\fBsmb.conf\fR(5)
 +option "<name>" to value "<value>" from the command line\&. This overrides compiled\-in defaults and options read from the configuration file\&.
 +.RE
 +.PP
 +\-N|\-\-no\-pass
 +.RS 4
 +If specified, this parameter suppresses the normal password prompt from the client to the user\&. This is useful when accessing a service that does not require a password\&.
 +.sp
 +Unless a password is specified on the command line or this parameter is specified, the client will request a password\&.
 +.sp
 +If a password is specified on the command line and this option is also defined the password on the command line will be silently ingnored and no password will be used\&.
 +.RE
 +.PP
 +\-k|\-\-kerberos
 +.RS 4
 +Try to authenticate with kerberos\&. Only useful in an Active Directory environment\&.
 +.RE
 +.PP
 +\-C|\-\-use\-ccache
 +.RS 4
 +Try to use the credentials cached by winbind\&.
 +.RE
 +.PP
 +\-A|\-\-authentication\-file=filename
 +.RS 4
 +This option allows you to specify a file from which to read the username and password used in the connection\&. The format of the file is
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +username = <value>
 +password = <value>
 +domain   = <value>
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.sp
 +Make certain that the permissions on the file restrict access from unwanted users\&.
 +.RE
 +.PP
 +\-U|\-\-user=username[%password]
 +.RS 4
 +Sets the SMB username or username and password\&.
 +.sp
 +If %password is not specified, the user will be prompted\&. The client will first check the
 +\fBUSER\fR
 +environment variable, then the
 +\fBLOGNAME\fR
 +variable and if either exists, the string is uppercased\&. If these environmental variables are not found, the username
 +\fBGUEST\fR
 +is used\&.
 +.sp
 +A third option is to use a credentials file which contains the plaintext of the username and password\&. This option is mainly provided for scripts where the admin does not wish to pass the credentials on the command line or via environment variables\&. If this method is used, make certain that the permissions on the file restrict access from unwanted users\&. See the
 +\fI\-A\fR
 +for more details\&.
 +.sp
 +Be cautious about including passwords in scripts\&. Also, on many systems the command line of a running process may be seen via the
 +ps
 +command\&. To be safe always allow
 +rpcclient
 +to prompt for a password and type it in directly\&.
 +.RE
 +.PP
 +\-S|\-\-signing on|off|required
 +.RS 4
 +Set the client signing state\&.
 +.RE
 +.PP
 +\-P|\-\-machine\-pass
 +.RS 4
 +Use stored machine account password\&.
 +.RE
 +.PP
 +\-e|\-\-encrypt
 +.RS 4
 +This command line parameter requires the remote server support the UNIX extensions or that the SMB3 protocol has been selected\&. Requests that the connection be encrypted\&. Negotiates SMB encryption using either SMB3 or POSIX extensions via GSSAPI\&. Uses the given credentials for the encryption negotiation (either kerberos or NTLMv1/v2 if given domain/username/password triple\&. Fails the connection if encryption cannot be negotiated\&.
 +.RE
 +.PP
 +\-\-pw\-nt\-hash
 +.RS 4
 +The supplied password is the NT hash\&.
 +.RE
 +.PP
 +\-n|\-\-netbiosname <primary NetBIOS name>
 +.RS 4
 +This option allows you to override the NetBIOS name that Samba uses for itself\&. This is identical to setting the
 +\m[blue]\fBnetbios name\fR\m[]
 +parameter in the
 +smb\&.conf
 +file\&. However, a command line setting will take precedence over settings in
 +smb\&.conf\&.
 +.RE
 +.PP
 +\-i|\-\-scope <scope>
 +.RS 4
 +This specifies a NetBIOS scope that
 +nmblookup
 +will use to communicate with when generating NetBIOS names\&. For details on the use of NetBIOS scopes, see rfc1001\&.txt and rfc1002\&.txt\&. NetBIOS scopes are
 +\fIvery\fR
 +rarely used, only set this parameter if you are the system administrator in charge of all the NetBIOS systems you communicate with\&.
 +.RE
 +.PP
 +\-W|\-\-workgroup=domain
 +.RS 4
 +Set the SMB domain of the username\&. This overrides the default domain which is the domain defined in smb\&.conf\&. If the domain specified is the same as the servers NetBIOS name, it causes the client to log on using the servers local SAM (as opposed to the Domain SAM)\&.
 +.RE
 +.PP
 +\-O|\-\-socket\-options socket options
 +.RS 4
 +TCP socket options to set on the client socket\&. See the socket options parameter in the
 +smb\&.conf
 +manual page for the list of valid options\&.
 +.RE
 +.PP
 +\-?|\-\-help
 +.RS 4
 +Print a summary of command line options\&.
 +.RE
 +.PP
 +\-\-usage
 +.RS 4
 +Display brief usage message\&.
 +.RE
 +.SH "COMMANDS"
 +.SS "LSARPC"
 +.PP
 +lsaquery
 +.RS 4
 +Query info policy
 +.RE
 +.PP
 +lookupsids
 +.RS 4
 +Resolve a list of SIDs to usernames\&.
 +.RE
 +.PP
 +lookupnames
 +.RS 4
 +Resolve a list of usernames to SIDs\&.
 +.RE
 +.PP
 +enumtrust
 +.RS 4
 +Enumerate trusted domains
 +.RE
 +.PP
 +enumprivs
 +.RS 4
 +Enumerate privileges
 +.RE
 +.PP
 +getdispname
 +.RS 4
 +Get the privilege name
 +.RE
 +.PP
 +lsaenumsid
 +.RS 4
 +Enumerate the LSA SIDS
 +.RE
 +.PP
 +lsaenumprivsaccount
 +.RS 4
 +Enumerate the privileges of an SID
 +.RE
 +.PP
 +lsaenumacctrights
 +.RS 4
 +Enumerate the rights of an SID
 +.RE
 +.PP
 +lsaenumacctwithright
 +.RS 4
 +Enumerate accounts with a right
 +.RE
 +.PP
 +lsaaddacctrights
 +.RS 4
 +Add rights to an account
 +.RE
 +.PP
 +lsaremoveacctrights
 +.RS 4
 +Remove rights from an account
 +.RE
 +.PP
 +lsalookupprivvalue
 +.RS 4
 +Get a privilege value given its name
 +.RE
 +.PP
 +lsaquerysecobj
 +.RS 4
 +Query LSA security object
 +.RE
 +.SS "LSARPC\-DS"
 +.PP
 +dsroledominfo
 +.RS 4
 +Get Primary Domain Information
 +.RE
 +.PP
 +.PP
 +\fIDFS\fR
 +.PP
 +dfsexist
 +.RS 4
 +Query DFS support
 +.RE
 +.PP
 +dfsadd
 +.RS 4
 +Add a DFS share
 +.RE
 +.PP
 +dfsremove
 +.RS 4
 +Remove a DFS share
 +.RE
 +.PP
 +dfsgetinfo
 +.RS 4
 +Query DFS share info
 +.RE
 +.PP
 +dfsenum
 +.RS 4
 +Enumerate dfs shares
 +.RE
 +.SS "REG"
 +.PP
 +shutdown
 +.RS 4
 +Remote Shutdown
 +.RE
 +.PP
 +abortshutdown
 +.RS 4
 +Abort Shutdown
 +.RE
 +.SS "SRVSVC"
 +.PP
 +srvinfo
 +.RS 4
 +Server query info
 +.RE
 +.PP
 +netshareenum
 +.RS 4
 +Enumerate shares
 +.RE
 +.PP
 +netshareenumall
 +.RS 4
 +Enumerate all shares
 +.RE
 +.PP
 +netsharegetinfo
 +.RS 4
 +Get Share Info
 +.RE
 +.PP
 +netsharesetinfo
 +.RS 4
 +Set Share Info
 +.RE
 +.PP
 +netsharesetdfsflags
 +.RS 4
 +Set DFS flags
 +.RE
 +.PP
 +netfileenum
 +.RS 4
 +Enumerate open files
 +.RE
 +.PP
 +netremotetod
 +.RS 4
 +Fetch remote time of day
 +.RE
 +.PP
 +netnamevalidate
 +.RS 4
 +Validate sharename
 +.RE
 +.PP
 +netfilegetsec
 +.RS 4
 +Get File security
 +.RE
 +.PP
 +netsessdel
 +.RS 4
 +Delete Session
 +.RE
 +.PP
 +netsessenum
 +.RS 4
 +Enumerate Sessions
 +.RE
 +.PP
 +netdiskenum
 +.RS 4
 +Enumerate Disks
 +.RE
 +.PP
 +netconnenum
 +.RS 4
 +Enumerate Connections
 +.RE
 +.PP
 +netshareadd
 +.RS 4
 +Add share
 +.RE
 +.PP
 +netsharedel
 +.RS 4
 +Delete share
 +.RE
 +.SS "SAMR"
 +.PP
 +queryuser
 +.RS 4
 +Query user info
 +.RE
 +.PP
 +querygroup
 +.RS 4
 +Query group info
 +.RE
 +.PP
 +queryusergroups
 +.RS 4
 +Query user groups
 +.RE
 +.PP
 +querygroupmem
 +.RS 4
 +Query group membership
 +.RE
 +.PP
 +queryaliasmem
 +.RS 4
 +Query alias membership
 +.RE
 +.PP
 +querydispinfo
 +.RS 4
 +Query display info
 +.RE
 +.PP
 +querydominfo
 +.RS 4
 +Query domain info
 +.RE
 +.PP
 +enumdomusers
 +.RS 4
 +Enumerate domain users
 +.RE
 +.PP
 +enumdomgroups
 +.RS 4
 +Enumerate domain groups
 +.RE
 +.PP
 +enumalsgroups
 +.RS 4
 +Enumerate alias groups
 +.RE
 +.PP
 +createdomuser
 +.RS 4
 +Create domain user
 +.RE
 +.PP
 +samlookupnames
 +.RS 4
 +Look up names
 +.RE
 +.PP
 +samlookuprids
 +.RS 4
 +Look up names
 +.RE
 +.PP
 +deletedomuser
 +.RS 4
 +Delete domain user
 +.RE
 +.PP
 +samquerysecobj
 +.RS 4
 +Query SAMR security object
 +.RE
 +.PP
 +getdompwinfo
 +.RS 4
 +Retrieve domain password info
 +.RE
 +.PP
 +lookupdomain
 +.RS 4
 +Look up domain
 +.RE
 +.SS "SPOOLSS"
 +.PP
 +adddriver <arch> <config> [<version>]
 +.RS 4
 +Execute an AddPrinterDriver() RPC to install the printer driver information on the server\&. Note that the driver files should already exist in the directory returned by
 +getdriverdir\&. Possible values for
 +\fIarch\fR
 +are the same as those for the
 +getdriverdir
 +command\&. The
 +\fIconfig\fR
 +parameter is defined as follows:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +Long Driver Name:\e
 +Driver File Name:\e
 +Data File Name:\e
 +Config File Name:\e
 +Help File Name:\e
 +Language Monitor Name:\e
 +Default Data Type:\e
 +Comma Separated list of Files
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.sp
 +Any empty fields should be enter as the string "NULL"\&.
 +.sp
 +Samba does not need to support the concept of Print Monitors since these only apply to local printers whose driver can make use of a bi\-directional link for communication\&. This field should be "NULL"\&. On a remote NT print server, the Print Monitor for a driver must already be installed prior to adding the driver or else the RPC will fail\&.
 +.sp
 +The
 +\fIversion\fR
 +parameter lets you specify the printer driver version number\&. If omitted, the default driver version for the specified architecture will be used\&. This option can be used to upload Windows 2000 (version 3) printer drivers\&.
 +.RE
 +.PP
 +addprinter <printername> <sharename> <drivername> <port>
 +.RS 4
 +Add a printer on the remote server\&. This printer will be automatically shared\&. Be aware that the printer driver must already be installed on the server (see
 +adddriver) and the
 +\fIport\fRmust be a valid port name (see
 +enumports\&.
 +.RE
 +.PP
 +deldriver <driver>
 +.RS 4
 +Delete the specified printer driver for all architectures\&. This does not delete the actual driver files from the server, only the entry from the server\*(Aqs list of drivers\&.
 +.RE
 +.PP
 +deldriverex <driver> [architecture] [version] [flags]
 +.RS 4
 +Delete the specified printer driver and optionally files associated with the driver\&. You can limit this action to a specific architecture and a specific version\&. If no architecture is given, all driver files of that driver will be deleted\&.
 +\fIflags\fR
 +correspond to numeric DPD_* values, i\&.e\&. a value of 3 requests (DPD_DELETE_UNUSED_FILES | DPD_DELETE_SPECIFIC_VERSION)\&.
 +.RE
 +.PP
 +enumdata
 +.RS 4
 +Enumerate all printer setting data stored on the server\&. On Windows NT clients, these values are stored in the registry, while Samba servers store them in the printers TDB\&. This command corresponds to the MS Platform SDK GetPrinterData() function (* This command is currently unimplemented)\&.
 +.RE
 +.PP
 +enumdataex
 +.RS 4
 +Enumerate printer data for a key
 +.RE
 +.PP
 +enumjobs <printer>
 +.RS 4
 +List the jobs and status of a given printer\&. This command corresponds to the MS Platform SDK EnumJobs() function
 +.RE
 +.PP
 +enumkey
 +.RS 4
 +Enumerate printer keys
 +.RE
 +.PP
 +enumports [level]
 +.RS 4
 +Executes an EnumPorts() call using the specified info level\&. Currently only info levels 1 and 2 are supported\&.
 +.RE
 +.PP
 +enumdrivers [level]
 +.RS 4
 +Execute an EnumPrinterDrivers() call\&. This lists the various installed printer drivers for all architectures\&. Refer to the MS Platform SDK documentation for more details of the various flags and calling options\&. Currently supported info levels are 1, 2, and 3\&.
 +.RE
 +.PP
 +enumprinters [level]
 +.RS 4
 +Execute an EnumPrinters() call\&. This lists the various installed and share printers\&. Refer to the MS Platform SDK documentation for more details of the various flags and calling options\&. Currently supported info levels are 1, 2 and 5\&.
 +.RE
 +.PP
 +getdata <printername> <valuename;>
 +.RS 4
 +Retrieve the data for a given printer setting\&. See the
 +enumdata
 +command for more information\&. This command corresponds to the GetPrinterData() MS Platform SDK function\&.
 +.RE
 +.PP
 +getdataex
 +.RS 4
 +Get printer driver data with keyname
 +.RE
 +.PP
 +getdriver <printername>
 +.RS 4
 +Retrieve the printer driver information (such as driver file, config file, dependent files, etc\&.\&.\&.) for the given printer\&. This command corresponds to the GetPrinterDriver() MS Platform SDK function\&. Currently info level 1, 2, and 3 are supported\&.
 +.RE
 +.PP
 +getdriverdir <arch>
 +.RS 4
 +Execute a GetPrinterDriverDirectory() RPC to retrieve the SMB share name and subdirectory for storing printer driver files for a given architecture\&. Possible values for
 +\fIarch\fR
 +are "Windows 4\&.0" (for Windows 95/98), "Windows NT x86", "Windows NT PowerPC", "Windows Alpha_AXP", and "Windows NT R4000"\&.
 +.RE
 +.PP
 +getprinter <printername>
 +.RS 4
 +Retrieve the current printer information\&. This command corresponds to the GetPrinter() MS Platform SDK function\&.
 +.RE
 +.PP
 +getprintprocdir
 +.RS 4
 +Get print processor directory
 +.RE
 +.PP
 +openprinter <printername>
 +.RS 4
 +Execute an OpenPrinterEx() and ClosePrinter() RPC against a given printer\&.
 +.RE
 +.PP
 +setdriver <printername> <drivername>
 +.RS 4
 +Execute a SetPrinter() command to update the printer driver associated with an installed printer\&. The printer driver must already be correctly installed on the print server\&.
 +.sp
 +See also the
 +enumprinters
 +and
 +enumdrivers
 +commands for obtaining a list of of installed printers and drivers\&.
 +.RE
 +.PP
 +addform
 +.RS 4
 +Add form
 +.RE
 +.PP
 +setform
 +.RS 4
 +Set form
 +.RE
 +.PP
 +getform
 +.RS 4
 +Get form
 +.RE
 +.PP
 +deleteform
 +.RS 4
 +Delete form
 +.RE
 +.PP
 +enumforms
 +.RS 4
 +Enumerate form
 +.RE
 +.PP
 +setprinter
 +.RS 4
 +Set printer comment
 +.RE
 +.PP
 +setprinterdata
 +.RS 4
 +Set REG_SZ printer data
 +.RE
 +.PP
 +setprintername <printername> <newprintername>
 +.RS 4
 +Set printer name
 +.RE
 +.PP
 +rffpcnex
 +.RS 4
 +Rffpcnex test
 +.RE
 +.SS "NETLOGON"
 +.PP
 +logonctrl2
 +.RS 4
 +Logon Control 2
 +.RE
 +.PP
 +logonctrl
 +.RS 4
 +Logon Control
 +.RE
 +.PP
 +samsync
 +.RS 4
 +Sam Synchronisation
 +.RE
 +.PP
 +samdeltas
 +.RS 4
 +Query Sam Deltas
 +.RE
 +.PP
 +samlogon
 +.RS 4
 +Sam Logon
 +.RE
 +.SS "FSRVP"
 +.PP
 +fss_is_path_sup <share>
 +.RS 4
 +Check whether a share supports shadow\-copy requests
 +.RE
 +.PP
 +fss_get_sup_version
 +.RS 4
 +Get supported FSRVP version from server
 +.RE
 +.PP
 +fss_create_expose <context> <[ro|rw]> <share1> [share2] \&.\&.\&. [shareN]
 +.RS 4
 +Request shadow\-copy creation and exposure as a new share
 +.RE
 +.PP
 +fss_delete <base_share> <shadow_copy_set_id> <shadow_copy_id>
 +.RS 4
 +Request shadow\-copy share deletion
 +.RE
 +.PP
 +fss_has_shadow_copy <base_share>
 +.RS 4
 +Check for an associated share shadow\-copy
 +.RE
 +.PP
 +fss_get_mapping <base_share> <shadow_copy_set_id> <shadow_copy_id>
 +.RS 4
 +Get shadow\-copy share mapping information
 +.RE
 +.PP
 +fss_recovery_complete <shadow_copy_set_id>
 +.RS 4
 +Flag read\-write shadow\-copy as recovery complete, allowing further shadow\-copy requests
 +.RE
 +.SS "GENERAL COMMANDS"
 +.PP
 +debuglevel
 +.RS 4
 +Set the current debug level used to log information\&.
 +.RE
 +.PP
 +help (?)
 +.RS 4
 +Print a listing of all known commands or extended help on a particular command\&.
 +.RE
 +.PP
 +quit (exit)
 +.RS 4
 +Exit
 +rpcclient\&.
 +.RE
 +.SH "BUGS"
 +.PP
 +rpcclient
 +is designed as a developer testing tool and may not be robust in certain areas (such as command line parsing)\&. It has been known to generate a core dump upon failures when invalid parameters where passed to the interpreter\&.
 +.PP
 +From Luke Leighton\*(Aqs original rpcclient man page:
 +.PP
 +\fIWARNING!\fR
 +The MSRPC over SMB code has been developed from examining Network traces\&. No documentation is available from the original creators (Microsoft) on how MSRPC over SMB works, or how the individual MSRPC services work\&. Microsoft\*(Aqs implementation of these services has been demonstrated (and reported) to be\&.\&.\&. a bit flaky in places\&.
 +.PP
 +The development of Samba\*(Aqs implementation is also a bit rough, and as more of the services are understood, it can even result in versions of
 +\fBsmbd\fR(8)
 +and
 +\fBrpcclient\fR(1)
 +that are incompatible for some commands or services\&. Additionally, the developers are sending reports to Microsoft, and problems found or reported to Microsoft are fixed in Service Packs, which may result in incompatibilities\&.
 +.SH "VERSION"
 +.PP
 +This man page is correct for version 3 of the Samba suite\&.
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
 +.PP
 +The original rpcclient man page was written by Matthew Geddes, Luke Kenneth Casson Leighton, and rewritten by Gerald Carter\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
diff --cc docs/manpages/samba-regedit.8
index 90a0507,0000000..76db229
mode 100644,000000..100644
--- a/docs/manpages/samba-regedit.8
+++ b/docs/manpages/samba-regedit.8
@@@ -1,221 -1,0 +1,221 @@@
 +'\" t
 +.\"     Title: samba-regedit
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: System Administration tools
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "SAMBA\-REGEDIT" "8" "12/01/2015" "Samba 4\&.3" "System Administration tools"
++.TH "SAMBA\-REGEDIT" "8" "12/10/2015" "Samba 4\&.3" "System Administration tools"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +samba-regedit \- ncurses based tool to manage the Samba registry
 +.SH "SYNOPSIS"
 +.HP \w'\ 'u
 +samba\-regedit [\-\-help] [\-\-usage] [\-d\ <debug\ level>] [\-s\ <configuration\ file>] [\-l\ <log\ directory>] [\-V] [\-\-option=<parameter>=<value>] [\-\-socket\-options=<SOCKETOPTIONS>] [\-\-netbiosname=<NETBIOSNAME>] [\-\-workgroup=<WORKGROUP>] [\-\-scope=<SCOPE>] [\-\-user=<USERNAME>] [\-N] [\-k] [\-\-authentication\-file=<FILE>] [\-\-signing=[on|off|required]] [\-P] [\-e] [\-C] [\-\-pw\-nt\-hash]
 +.SH "DESCRIPTION"
 +.PP
 +This tool is part of the
 +\fBsamba\fR(7)
 +suite\&.
 +.PP
 +samba\-regedit
 +is a ncurses based tool to manage the Samba registry\&. It can be used to show/edit registry keys/subkeys and their values\&.
 +.SH "OPTIONS"
 +.PP
 +\-?|\-\-help
 +.RS 4
 +Print a summary of command line options\&.
 +.RE
 +.PP
 +\-d|\-\-debuglevel=level
 +.RS 4
 +\fIlevel\fR
 +is an integer from 0 to 10\&. The default value if this parameter is not specified is 1\&.
 +.sp
 +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day\-to\-day running \- it generates a small amount of information about operations carried out\&.
 +.sp
 +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&.
 +.sp
 +Note that specifying this parameter here will override the
 +\m[blue]\fBlog level\fR\m[]
 +parameter in the
 +smb\&.conf
 +file\&.
 +.RE
 +.PP
 +\-\-usage
 +.RS 4
 +Display brief usage message\&.
 +.RE
 +.PP
 +\-V|\-\-version
 +.RS 4
 +Prints the program version number\&.
 +.RE
 +.PP
 +\-s|\-\-configfile=<configuration file>
 +.RS 4
 +The file specified contains the configuration details required by the server\&. The information in this file includes server\-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See
 +smb\&.conf
 +for more information\&. The default configuration file name is determined at compile time\&.
 +.RE
 +.PP
 +\-l|\-\-log\-basename=logdirectory
 +.RS 4
 +Base directory name for log/debug files\&. The extension
 +\fB"\&.progname"\fR
 +will be appended (e\&.g\&. log\&.smbclient, log\&.smbd, etc\&.\&.\&.)\&. The log file is never removed by the client\&.
 +.RE
 +.PP
 +\-\-option=<name>=<value>
 +.RS 4
 +Set the
 +\fBsmb.conf\fR(5)
 +option "<name>" to value "<value>" from the command line\&. This overrides compiled\-in defaults and options read from the configuration file\&.
 +.RE
 +.PP
 +\-n|\-\-netbiosname <primary NetBIOS name>
 +.RS 4
 +This option allows you to override the NetBIOS name that Samba uses for itself\&. This is identical to setting the
 +\m[blue]\fBnetbios name\fR\m[]
 +parameter in the
 +smb\&.conf
 +file\&. However, a command line setting will take precedence over settings in
 +smb\&.conf\&.
 +.RE
 +.PP
 +\-i|\-\-scope <scope>
 +.RS 4
 +This specifies a NetBIOS scope that
 +nmblookup
 +will use to communicate with when generating NetBIOS names\&. For details on the use of NetBIOS scopes, see rfc1001\&.txt and rfc1002\&.txt\&. NetBIOS scopes are
 +\fIvery\fR
 +rarely used, only set this parameter if you are the system administrator in charge of all the NetBIOS systems you communicate with\&.
 +.RE
 +.PP
 +\-W|\-\-workgroup=domain
 +.RS 4
 +Set the SMB domain of the username\&. This overrides the default domain which is the domain defined in smb\&.conf\&. If the domain specified is the same as the servers NetBIOS name, it causes the client to log on using the servers local SAM (as opposed to the Domain SAM)\&.
 +.RE
 +.PP
 +\-O|\-\-socket\-options socket options
 +.RS 4
 +TCP socket options to set on the client socket\&. See the socket options parameter in the
 +smb\&.conf
 +manual page for the list of valid options\&.
 +.RE
 +.PP
 +\-N|\-\-no\-pass
 +.RS 4
 +If specified, this parameter suppresses the normal password prompt from the client to the user\&. This is useful when accessing a service that does not require a password\&.
 +.sp
 +Unless a password is specified on the command line or this parameter is specified, the client will request a password\&.
 +.sp
 +If a password is specified on the command line and this option is also defined the password on the command line will be silently ingnored and no password will be used\&.
 +.RE
 +.PP
 +\-k|\-\-kerberos
 +.RS 4
 +Try to authenticate with kerberos\&. Only useful in an Active Directory environment\&.
 +.RE
 +.PP
 +\-C|\-\-use\-ccache
 +.RS 4
 +Try to use the credentials cached by winbind\&.
 +.RE
 +.PP
 +\-A|\-\-authentication\-file=filename
 +.RS 4
 +This option allows you to specify a file from which to read the username and password used in the connection\&. The format of the file is
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +username = <value>
 +password = <value>
 +domain   = <value>
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.sp
 +Make certain that the permissions on the file restrict access from unwanted users\&.
 +.RE
 +.PP
 +\-U|\-\-user=username[%password]
 +.RS 4
 +Sets the SMB username or username and password\&.
 +.sp
 +If %password is not specified, the user will be prompted\&. The client will first check the
 +\fBUSER\fR
 +environment variable, then the
 +\fBLOGNAME\fR
 +variable and if either exists, the string is uppercased\&. If these environmental variables are not found, the username
 +\fBGUEST\fR
 +is used\&.
 +.sp
 +A third option is to use a credentials file which contains the plaintext of the username and password\&. This option is mainly provided for scripts where the admin does not wish to pass the credentials on the command line or via environment variables\&. If this method is used, make certain that the permissions on the file restrict access from unwanted users\&. See the
 +\fI\-A\fR
 +for more details\&.
 +.sp
 +Be cautious about including passwords in scripts\&. Also, on many systems the command line of a running process may be seen via the
 +ps
 +command\&. To be safe always allow
 +rpcclient
 +to prompt for a password and type it in directly\&.
 +.RE
 +.PP
 +\-S|\-\-signing on|off|required
 +.RS 4
 +Set the client signing state\&.
 +.RE
 +.PP
 +\-P|\-\-machine\-pass
 +.RS 4
 +Use stored machine account password\&.
 +.RE
 +.PP
 +\-e|\-\-encrypt
 +.RS 4
 +This command line parameter requires the remote server support the UNIX extensions or that the SMB3 protocol has been selected\&. Requests that the connection be encrypted\&. Negotiates SMB encryption using either SMB3 or POSIX extensions via GSSAPI\&. Uses the given credentials for the encryption negotiation (either kerberos or NTLMv1/v2 if given domain/username/password triple\&. Fails the connection if encryption cannot be negotiated\&.
 +.RE
 +.PP
 +\-\-pw\-nt\-hash
 +.RS 4
 +The supplied password is the NT hash\&.
 +.RE
 +.SH "VERSION"
 +.PP
 +This man page is correct for version 4 of the Samba suite\&.
 +.SH "SEE ALSO"
 +.PP
 +\fBsmbd\fR(8),
 +\fBsamba\fR(7)
 +and
 +\fBnet\fR(8)\&.
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
 +.PP
 +The samba\-regedit man page was written by Karolin Seeger\&.
diff --cc docs/manpages/samba-tool.8
index a5d063b,0000000..2e3aafa
mode 100644,000000..100644
--- a/docs/manpages/samba-tool.8
+++ b/docs/manpages/samba-tool.8
@@@ -1,432 -1,0 +1,432 @@@
 +'\" t
 +.\"     Title: samba-tool
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: System Administration tools
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "SAMBA\-TOOL" "8" "12/01/2015" "Samba 4\&.3" "System Administration tools"
++.TH "SAMBA\-TOOL" "8" "12/10/2015" "Samba 4\&.3" "System Administration tools"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +samba-tool \- Main Samba administration tool\&.
 +.SH "SYNOPSIS"
 +.HP \w'\ 'u
 +samba\-tool [\-h] [\-W\ myworkgroup] [\-U\ user] [\-d\ debuglevel] [\-\-v]
 +.SH "DESCRIPTION"
 +.PP
 +This tool is part of the
 +\fBsamba\fR(7)
 +suite\&.
 +.SH "OPTIONS"
 +.PP
 +\-h|\-\-help
 +.RS 4
 +Show this help message and exit
 +.RE
 +.PP
 +\-\-realm=REALM
 +.RS 4
 +Set the realm name
 +.RE
 +.PP
 +\-\-simple\-bind\-dn=DN
 +.RS 4
 +DN to use for a simple bind
 +.RE
 +.PP
 +\-\-password=PASSWORD
 +.RS 4
 +Password
 +.RE
 +.PP
 +\-U USERNAME|\-\-username=USERNAME
 +.RS 4
 +Username
 +.RE
 +.PP
 +\-W WORKGROUP|\-\-workgroup=WORKGROUP
 +.RS 4
 +Workgroup
 +.RE
 +.PP
 +\-N|\-\-no\-pass
 +.RS 4
 +Don\*(Aqt ask for a password
 +.RE
 +.PP
 +\-k KERBEROS|\-\-kerberos=KERBEROS
 +.RS 4
 +Use Kerberos
 +.RE
 +.PP
 +\-\-ipaddress=IPADDRESS
 +.RS 4
 +IP address of the server
 +.RE
 +.PP
 +\-d|\-\-debuglevel=level
 +.RS 4
 +\fIlevel\fR
 +is an integer from 0 to 10\&. The default value if this parameter is not specified is 1\&.
 +.sp
 +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day\-to\-day running \- it generates a small amount of information about operations carried out\&.
 +.sp
 +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&.
 +.sp
 +Note that specifying this parameter here will override the
 +\m[blue]\fBlog level\fR\m[]
 +parameter in the
 +smb\&.conf
 +file\&.
 +.RE
 +.PP
 +\-V|\-\-version
 +.RS 4
 +Prints the program version number\&.
 +.RE
 +.PP
 +\-s|\-\-configfile=<configuration file>
 +.RS 4
 +The file specified contains the configuration details required by the server\&. The information in this file includes server\-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See
 +smb\&.conf
 +for more information\&. The default configuration file name is determined at compile time\&.
 +.RE
 +.PP
 +\-l|\-\-log\-basename=logdirectory
 +.RS 4
 +Base directory name for log/debug files\&. The extension
 +\fB"\&.progname"\fR
 +will be appended (e\&.g\&. log\&.smbclient, log\&.smbd, etc\&.\&.\&.)\&. The log file is never removed by the client\&.
 +.RE
 +.PP
 +\-\-option=<name>=<value>
 +.RS 4
 +Set the
 +\fBsmb.conf\fR(5)
 +option "<name>" to value "<value>" from the command line\&. This overrides compiled\-in defaults and options read from the configuration file\&.
 +.RE
 +.SH "COMMANDS"
 +.SS "dbcheck"
 +.PP
 +Check the local AD database for errors\&.
 +.SS "delegation"
 +.PP
 +Manage Delegations\&.
 +.SS "delegation add-service accountname principal [options]"
 +.PP
 +Add a service principal as msDS\-AllowedToDelegateTo\&.
 +.SS "delegation del-service accountname principal [options]"
 +.PP
 +Delete a service principal as msDS\-AllowedToDelegateTo\&.
 +.SS "delegation for-any-protocol accountname [(on|off)] [options]"
 +.PP
 +Set/unset UF_TRUSTED_TO_AUTHENTICATE_FOR_DELEGATION (S4U2Proxy) for an account\&.
 +.SS "delegation for-any-service accountname [(on|off)] [options]"
 +.PP
 +Set/unset UF_TRUSTED_FOR_DELEGATION for an account\&.
 +.SS "delegation show accountname [options]	"
 +.PP
 +Show the delegation setting of an account\&.
 +.SS "dns"
 +.PP
 +Manage Domain Name Service (DNS)\&.
 +.SS "dns add server zone name A|AAAA|PTR|CNAME|NS|MX|SRV|TXT data"
 +.PP
 +Add a DNS record\&.
 +.SS "dns delete server zone name A|AAAA|PTR|CNAME|NS|MX|SRV|TXT data"
 +.PP
 +Delete a DNS record\&.
 +.SS "dns query server zone name A|AAAA|PTR|CNAME|NS|MX|SRV|TXT|ALL [options] data"
 +.PP
 +Query a name\&.
 +.SS "dns roothints server [name] [options]"
 +.PP
 +Query root hints\&.
 +.SS "dns serverinfo server [options]"
 +.PP
 +Query server information\&.
 +.SS "dns update server zone name A|AAAA|PTR|CNAME|NS|MX|SRV|TXT olddata newdata"
 +.PP
 +Update a DNS record\&.
 +.SS "dns zonecreate server zone [options]"
 +.PP
 +Create a zone\&.
 +.SS "dns zonedelete server zone [options]"
 +.PP
 +Delete a zone\&.
 +.SS "dns zoneinfo server zone [options]"
 +.PP
 +Query zone information\&.
 +.SS "dns zonelist server [options]"
 +.PP
 +List zones\&.
 +.SS "domain"
 +.PP
 +Manage Domain\&.
 +.SS "domain classicupgrade [options] classic_smb_conf"
 +.PP
 +Upgrade from Samba classic (NT4\-like) database to Samba AD DC database\&.
 +.SS "domain dcpromo dnsdomain [DC|RODC] [options]"
 +.PP
 +Promote an existing domain member or NT4 PDC to an AD DC\&.
 +.SS "domain demote"
 +.PP
 +Demote ourselves from the role of domain controller\&.
 +.SS "domain exportkeytab keytab [options]"
 +.PP
 +Dumps Kerberos keys of the domain into a keytab\&.
 +.SS "domain info ip_address [options]"
 +.PP
 +Print basic info about a domain and the specified DC\&.
 +.SS "domain join dnsdomain [DC|RODC|MEMBER|SUBDOMAIN] [options]"
 +.PP
 +Join a domain as either member or backup domain controller\&.
 +.SS "domain level show|raise options [options]"
 +.PP
 +Show/raise domain and forest function levels\&.
 +.SS "domain passwordsettings show|set options [options]"
 +.PP
 +Show/set password settings\&.
 +.SS "domain provision"
 +.PP
 +Promote an existing domain member or NT4 PDC to an AD DC\&.
 +.SS "domain trust"
 +.PP
 +Domain and forest trust management\&.
 +.SS "domain trust create DOMAIN options [options]"
 +.PP
 +Create a domain or forest trust\&.
 +.SS "domain trust delete DOMAIN options [options]"
 +.PP
 +Delete a domain trust\&.
 +.SS "domain trust list options [options]"
 +.PP
 +List domain trusts\&.
 +.SS "domain trust namespaces [DOMAIN] options [options]"
 +.PP
 +Manage forest trust namespaces\&.
 +.SS "domain trust show DOMAIN options [options]"
 +.PP
 +Show trusted domain details\&.
 +.SS "domain trust validate DOMAIN options [options]"
 +.PP
 +Validate a domain trust\&.
 +.SS "drs"
 +.PP
 +Manage Directory Replication Services (DRS)\&.
 +.SS "drs bind"
 +.PP
 +Show DRS capabilities of a server\&.
 +.SS "drs kcc"
 +.PP
 +Trigger knowledge consistency center run\&.
 +.SS "drs options"
 +.PP
 +Query or change
 +\fIoptions\fR
 +for NTDS Settings object of a domain controller\&.
 +.SS "drs replicate destination_DC source_DC NC [options]"
 +.PP
 +Replicate a naming context between two DCs\&.
 +.SS "drs showrepl"
 +.PP
 +Show replication status\&.
 +.SS "dsacl"
 +.PP
 +Administer DS ACLs
 +.SS "dsacl set"
 +.PP
 +Modify access list on a directory object\&.
 +.SS "fsmo"
 +.PP
 +Manage Flexible Single Master Operations (FSMO)\&.
 +.SS "fsmo seize [options]"
 +.PP
 +Seize the role\&.
 +.SS "fsmo show"
 +.PP
 +Show the roles\&.
 +.SS "fsmo transfer [options]"
 +.PP
 +Transfer the role\&.
 +.SS "gpo"
 +.PP
 +Manage Group Policy Objects (GPO)\&.
 +.SS "gpo create displayname [options]"
 +.PP
 +Create an empty GPO\&.
 +.SS "gpo del gpo [options]"
 +.PP
 +Delete GPO\&.
 +.SS "gpo dellink container_dn gpo [options]"
 +.PP
 +Delete GPO link from a container\&.
 +.SS "gpo fetch gpo [options]"
 +.PP
 +Download a GPO\&.
 +.SS "gpo getinheritance container_dn [options]"
 +.PP
 +Get inheritance flag for a container\&.
 +.SS "gpo getlink container_dn [options]"
 +.PP
 +List GPO Links for a container\&.
 +.SS "gpo list username [options]"
 +.PP
 +List GPOs for an account\&.
 +.SS "gpo listall"
 +.PP
 +List all GPOs\&.
 +.SS "gpo listcontainers gpo [options]"
 +.PP
 +List all linked containers for a GPO\&.
 +.SS "gpo setinheritance container_dn block|inherit [options]"
 +.PP
 +Set inheritance flag on a container\&.
 +.SS "gpo setlink container_dn gpo [options]"
 +.PP
 +Add or Update a GPO link to a container\&.
 +.SS "gpo show gpo [options]"
 +.PP
 +Show information for a GPO\&.
 +.SS "group"
 +.PP
 +Manage groups\&.
 +.SS "group add groupname [options]"
 +.PP
 +Create a new AD group\&.
 +.SS "group addmembers groupname members [options]"
 +.PP
 +Add members to an AD group\&.
 +.SS "group delete groupname [options]"
 +.PP
 +Delete an AD group\&.
 +.SS "group list"
 +.PP
 +List all groups\&.
 +.SS "group listmembers groupname [options]"
 +.PP
 +List all members of the specified AD group\&.
 +.SS "group removemembers groupname members [options]"
 +.PP
 +Remove members from the specified AD group\&.
 +.SS "ldapcmp \fIURL1\fR \fIURL2\fR \fIdomain|configuration|schema|dnsdomain|dnsforest\fR [options]"
 +.PP
 +Compare two LDAP databases\&.
 +.SS "ntacl"
 +.PP
 +Manage NT ACLs\&.
 +.SS "ntacl get file [options]"
 +.PP
 +Get ACLs on a file\&.
 +.SS "ntacl set acl file [options]"
 +.PP
 +Set ACLs on a file\&.
 +.SS "ntacl sysvolcheck"
 +.PP
 +Check sysvol ACLs match defaults (including correct ACLs on GPOs)\&.
 +.SS "ntacl sysvolreset"
 +.PP
 +Reset sysvol ACLs to defaults (including correct ACLs on GPOs)\&.
 +.SS "rodc"
 +.PP
 +Manage Read\-Only Domain Controller (RODC)\&.
 +.SS "rodc preload SID|DN|accountname [options]"
 +.PP
 +Preload one account for an RODC\&.
 +.SS "sites"
 +.PP
 +Manage sites\&.
 +.SS "sites create site [options]"
 +.PP
 +Create a new site\&.
 +.SS "sites remove site [options]"
 +.PP
 +Delete an existing site\&.
 +.SS "spn"
 +.PP
 +Manage Service Principal Names (SPN)\&.
 +.SS "spn add name user [options]"
 +.PP
 +Create a new SPN\&.
 +.SS "spn delete name [user] [options]"
 +.PP
 +Delete an existing SPN\&.
 +.SS "spn list user [options]"
 +.PP
 +List SPNs of a given user\&.
 +.SS "testparm"
 +.PP
 +Check the syntax of the configuration file\&.
 +.SS "time"
 +.PP
 +Retrieve the time on a server\&.
 +.SS "user"
 +.PP
 +Manage users\&.
 +.SS "user add username [password]"
 +.PP
 +Create a new user\&. Please note that this subcommand is deprecated and available for compatibility reasons only\&. Please use
 +samba\-tool user create
 +instead\&.
 +.SS "user create username [password]"
 +.PP
 +Create a new user in the Active Directory Domain\&.
 +.SS "user delete username [options]"
 +.PP
 +Delete an existing user account\&.
 +.SS "user disable username"
 +.PP
 +Disable an user account\&.
 +.SS "user enable username"
 +.PP
 +Enable an user account\&.
 +.SS "user list"
 +.PP
 +List all users\&.
 +.SS "user password [options]"
 +.PP
 +Change password for an user account (the one provided in authentication)\&.
 +.SS "user setexpiry username [options]"
 +.PP
 +Set the expiration of an user account\&.
 +.SS "user setpassword username [options]"
 +.PP
 +Sets or resets the password of an user account\&.
 +.SS "vampire [options] \fIdomain\fR"
 +.PP
 +Join and synchronise a remote AD domain to the local server\&. Please note that
 +samba\-tool vampire
 +is deprecated, please use
 +samba\-tool domain join
 +instead\&.
 +.SS "help"
 +.PP
 +Gives usage information\&.
 +.SH "VERSION"
 +.PP
 +This man page is complete for version 4 of the Samba suite\&.
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
 +.PP
 +The samba\-tool manpage was written by Karolin Seeger\&.
diff --cc docs/manpages/samba.7
index b99b303,0000000..ad18244
mode 100644,000000..100644
--- a/docs/manpages/samba.7
+++ b/docs/manpages/samba.7
@@@ -1,261 -1,0 +1,261 @@@
 +'\" t
 +.\"     Title: samba
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: Miscellanea
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "SAMBA" "7" "12/01/2015" "Samba 4\&.3" "Miscellanea"
++.TH "SAMBA" "7" "12/10/2015" "Samba 4\&.3" "Miscellanea"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +samba \- A Windows AD and SMB/CIFS fileserver for UNIX
 +.SH "SYNOPSIS"
 +.HP \w'\ 'u
 +samba
 +.SH "DESCRIPTION"
 +.PP
 +The Samba software suite is a collection of programs that implements the Server Message Block (commonly abbreviated as SMB) protocol for UNIX systems and provides Active Directory services\&. This protocol is sometimes also referred to as the Common Internet File System (CIFS)\&. For a more thorough description, see
 +http://www\&.ubiqx\&.org/cifs/\&. Samba also implements the NetBIOS protocol in nmbd\&.
 +.PP
 +\fBsamba\fR(8)
 +.RS 4
 +The
 +samba
 +daemon provides the Active Directory services and file and print services to SMB clients\&. The configuration file for this daemon is described in
 +\fBsmb.conf\fR(5)\&.
 +.RE
 +.PP
 +\fBsmbd\fR(8)
 +.RS 4
 +The
 +smbd
 +daemon provides the file and print services to SMB clients, such as Windows 95/98, Windows NT, Windows for Workgroups or LanManager\&. The configuration file for this daemon is described in
 +\fBsmb.conf\fR(5)\&.
 +.RE
 +.PP
 +\fBnmbd\fR(8)
 +.RS 4
 +The
 +nmbd
 +daemon provides NetBIOS nameservice and browsing support\&. The configuration file for this daemon is described in
 +\fBsmb.conf\fR(5)\&.
 +.RE
 +.PP
 +\fBwinbindd\fR(8)
 +.RS 4
 +winbindd
 +is a daemon that is used for integrating authentication and the user database into unix\&.
 +.RE
 +.PP
 +\fBsmbclient\fR(1)
 +.RS 4
 +The
 +smbclient
 +program implements a simple ftp\-like client\&. This is useful for accessing SMB shares on other compatible servers (such as Windows NT), and can also be used to allow a UNIX box to print to a printer attached to any SMB server (such as a PC running Windows NT)\&.
 +.RE
 +.PP
 +\fBsamba-tool\fR(8)
 +.RS 4
 +The
 +samba\-tool
 +is the main Samba Administration tool regarding Active Directory services\&.
 +.RE
 +.PP
 +\fBtestparm\fR(1)
 +.RS 4
 +The
 +testparm
 +utility is a simple syntax checker for Samba\*(Aqs
 +\fBsmb.conf\fR(5)
 +configuration file\&.
 +.RE
 +.PP
 +\fBsmbstatus\fR(1)
 +.RS 4
 +The
 +smbstatus
 +tool provides access to information about the current connections to
 +smbd\&.
 +.RE
 +.PP
 +\fBnmblookup\fR(1)
 +.RS 4
 +The
 +nmblookup
 +tools allows NetBIOS name queries to be made from a UNIX host\&.
 +.RE
 +.PP
 +\fBsmbpasswd\fR(8)
 +.RS 4
 +The
 +smbpasswd
 +command is a tool for changing LanMan and Windows NT password hashes on Samba and Windows NT servers\&.
 +.RE
 +.PP
 +\fBsmbcacls\fR(1)
 +.RS 4
 +The
 +smbcacls
 +command is a tool to set ACL\*(Aqs on remote CIFS servers\&.
 +.RE
 +.PP
 +\fBsmbtree\fR(1)
 +.RS 4
 +The
 +smbtree
 +command is a text\-based network neighborhood tool\&.
 +.RE
 +.PP
 +\fBsmbtar\fR(1)
 +.RS 4
 +The
 +smbtar
 +can make backups of data on CIFS/SMB servers\&.
 +.RE
 +.PP
 +\fBsmbspool\fR(8)
 +.RS 4
 +smbspool
 +is a helper utility for printing on printers connected to CIFS servers\&.
 +.RE
 +.PP
 +\fBsmbcontrol\fR(1)
 +.RS 4
 +smbcontrol
 +is a utility that can change the behaviour of running
 +smbd,
 +nmbd
 +and
 +winbindd
 +daemons\&.
 +.RE
 +.PP
 +\fBrpcclient\fR(1)
 +.RS 4
 +rpcclient
 +is a utility that can be used to execute RPC commands on remote CIFS servers\&.
 +.RE
 +.PP
 +\fBpdbedit\fR(8)
 +.RS 4
 +The
 +pdbedit
 +command can be used to maintain the local user database on a samba server\&.
 +.RE
 +.PP
 +\fBfindsmb\fR(1)
 +.RS 4
 +The
 +findsmb
 +command can be used to find SMB servers on the local network\&.
 +.RE
 +.PP
 +\fBnet\fR(8)
 +.RS 4
 +The
 +net
 +command is supposed to work similar to the DOS/Windows NET\&.EXE command\&.
 +.RE
 +.PP
 +\fBwbinfo\fR(1)
 +.RS 4
 +wbinfo
 +is a utility that retrieves and stores information related to winbind\&.
 +.RE
 +.PP
 +\fBprofiles\fR(1)
 +.RS 4
 +profiles
 +is a command\-line utility that can be used to replace all occurrences of a certain SID with another SID\&.
 +.RE
 +.PP
 +\fBlog2pcap\fR(1)
 +.RS 4
 +log2pcap
 +is a utility for generating pcap trace files from Samba log files\&.
 +.RE
 +.PP
 +\fBvfstest\fR(1)
 +.RS 4
 +vfstest
 +is a utility that can be used to test vfs modules\&.
 +.RE
 +.PP
 +\fBntlm_auth\fR(1)
 +.RS 4
 +ntlm_auth
 +is a helper\-utility for external programs wanting to do NTLM\-authentication\&.
 +.RE
 +.PP
 +\fBsmbcquotas\fR(1)
 +.RS 4
 +smbcquotas
 +is a tool that can set remote QUOTA\*(Aqs on server with NTFS 5\&.
 +.RE
 +.SH "COMPONENTS"
 +.PP
 +The Samba suite is made up of several components\&. Each component is described in a separate manual page\&. It is strongly recommended that you read the documentation that comes with Samba and the manual pages of those components that you use\&. If the manual pages and documents aren\*(Aqt clear enough then please visit
 +http://devel\&.samba\&.org
 +for information on how to file a bug report or submit a patch\&.
 +.PP
 +If you require help, visit the Samba webpage at
 +http://www\&.samba\&.org/
 +and explore the many option available to you\&.
 +.SH "AVAILABILITY"
 +.PP
 +The Samba software suite is licensed under the GNU Public License(GPL)\&. A copy of that license should have come with the package in the file COPYING\&. You are encouraged to distribute copies of the Samba suite, but please obey the terms of this license\&.
 +.PP
 +The latest version of the Samba suite can be obtained via anonymous ftp from samba\&.org in the directory pub/samba/\&. It is also available on several mirror sites worldwide\&.
 +.PP
 +You may also find useful information about Samba on the newsgroup
 +comp\&.protocol\&.smb
 +and the Samba mailing list\&. Details on how to join the mailing list are given in the README file that comes with Samba\&.
 +.PP
 +If you have access to a WWW viewer (such as Mozilla or Konqueror) then you will also find lots of useful information, including back issues of the Samba mailing list, at
 +http://lists\&.samba\&.org\&.
 +.SH "VERSION"
 +.PP
 +This man page is correct for version 4 of the Samba suite\&.
 +.SH "CONTRIBUTIONS"
 +.PP
 +If you wish to contribute to the Samba project, then I suggest you join the Samba mailing list at
 +http://lists\&.samba\&.org\&.
 +.PP
 +If you have patches to submit, visit
 +http://devel\&.samba\&.org/
 +for information on how to do it properly\&. We prefer patches in
 +git format\-patch
 +format\&.
 +.SH "CONTRIBUTORS"
 +.PP
 +Contributors to the project are now too numerous to mention here but all deserve the thanks of all Samba users\&. To see a full list, look at the
 +change\-log
 +in the source package for the pre\-CVS changes and at
 +http://git\&.samba\&.org/
 +for the contributors to Samba post\-GIT\&. GIT is the Open Source source code control system used by the Samba Team to develop Samba\&. The project would have been unmanageable without it\&.
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
 +.PP
 +The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at
 +ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
diff --cc docs/manpages/samba.8
index 872c28b,0000000..31120f4
mode 100644,000000..100644
--- a/docs/manpages/samba.8
+++ b/docs/manpages/samba.8
@@@ -1,215 -1,0 +1,215 @@@
 +'\" t
 +.\"     Title: samba
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: System Administration tools
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "SAMBA" "8" "12/01/2015" "Samba 4\&.3" "System Administration tools"
++.TH "SAMBA" "8" "12/10/2015" "Samba 4\&.3" "System Administration tools"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +samba \- Server to provide AD and SMB/CIFS services to clients
 +.SH "SYNOPSIS"
 +.HP \w'\ 'u
 +samba [\-D] [\-i] [\-M\ <model>] [\-\-maximum\-runtime=<seconds>] [\-b] [\-\-help] [\-\-usage] [\-d\ <debug\ level>] [\-\-debug\-stderr] [\-s\ <configuration\ file>] [\-\-option=<smb_conf_param>=<value>] [\-l\ <log\ directory>] [\-\-leak\-report] [\-\-leak\-report\-full] [\-V]
 +.SH "DESCRIPTION"
 +.PP
 +This program is part of the
 +\fBsamba\fR(7)
 +suite\&.
 +.PP
 +samba
 +is the server daemon that provides Active Directory, filesharing and printing services to clients\&. The server provides filespace and directory services to clients using the SMB (or CIFS) protocol and other related protocols such as DCE/RPC, LDAP and Kerberos\&.
 +.PP
 +Clients supported include MSCLIENT 3\&.0 for DOS, Windows for Workgroups, Windows 95/98/ME, Windows NT, Windows 2000/XP/2003, OS/2, DAVE for Macintosh, and cifsfs for Linux\&.
 +.PP
 +An extensive description of the services that the server can provide is given in the man page for the configuration file controlling the attributes of those services (see
 +\fBsmb.conf\fR(5)\&. This man page will not describe the services, but will concentrate on the administrative aspects of running the server\&.
 +.PP
 +Please note that there are significant security implications to running this server, and the
 +\fBsmb.conf\fR(5)
 +manual page should be regarded as mandatory reading before proceeding with installation\&.
 +.SH "OPTIONS"
 +.PP
 +\-D|\-\-daemon
 +.RS 4
 +If specified, this parameter causes the server to operate as a daemon\&. That is, it detaches itself and runs in the background, fielding requests on the appropriate ports\&. Operating the server as a daemon is the recommended way of running
 +samba
 +for servers that provide more than casual use file and print services\&. This switch is assumed if
 +samba
 +is executed on the command line of a shell\&.
 +.RE
 +.PP
 +\-i|\-\-interactive
 +.RS 4
 +If this parameter is specified it causes the server to run "interactively", not as a daemon, even if the server is executed on the command line of a shell\&. Setting this parameter negates the implicit daemon mode when run from the command line\&.
 +samba
 +also logs to standard output, as if the
 +\-S
 +parameter had been given\&.
 +.RE
 +.PP
 +\-M model
 +.RS 4
 +This parameter can be used to specify the "process model" samba should use\&. This determines how concurrent clients are handled\&. Available process models include
 +\fIsingle\fR
 +(everything in a single process),
 +\fIstandard\fR
 +(similar behaviour to that of Samba 3),
 +\fIthread\fR
 +(single process, different threads\&.
 +.RE
 +.PP
 +\-\-maximum\-runtime=seconds
 +.RS 4
 +Set maximum runtime of the server process till autotermination in seconds\&.
 +.RE
 +.PP
 +\-b|\-\-show\-build
 +.RS 4
 +Print information about how Samba was built\&.
 +.RE
 +.PP
 +\-\-usage
 +.RS 4
 +Display brief usage message\&.
 +.RE
 +.PP
 +\-\-debug\-stderr
 +.RS 4
 +Send debug output to STDERR\&.
 +.RE
 +.PP
 +\-\-leak\-report
 +.RS 4
 +Enable talloc leak reporting on exit\&.
 +.RE
 +.PP
 +\-\-leak\-report\-full
 +.RS 4
 +Enable full talloc leak reporting on exit\&.
 +.RE
 +.PP
 +\-d|\-\-debuglevel=level
 +.RS 4
 +\fIlevel\fR
 +is an integer from 0 to 10\&. The default value if this parameter is not specified is 0\&.
 +.sp
 +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day\-to\-day running \- it generates a small amount of information about operations carried out\&.
 +.sp
 +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&.
 +.sp
 +Note that specifying this parameter here will override the
 +\m[blue]\fBlog level\fR\m[]
 +parameter in the
 +smb\&.conf
 +file\&.
 +.RE
 +.PP
 +\-V|\-\-version
 +.RS 4
 +Prints the program version number\&.
 +.RE
 +.PP
 +\-s|\-\-configfile=<configuration file>
 +.RS 4
 +The file specified contains the configuration details required by the server\&. The information in this file includes server\-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See
 +smb\&.conf
 +for more information\&. The default configuration file name is determined at compile time\&.
 +.RE
 +.PP
 +\-l|\-\-log\-basename=logdirectory
 +.RS 4
 +Base directory name for log/debug files\&. The extension
 +\fB"\&.progname"\fR
 +will be appended (e\&.g\&. log\&.smbclient, log\&.smbd, etc\&.\&.\&.)\&. The log file is never removed by the client\&.
 +.RE
 +.PP
 +\-\-option=<name>=<value>
 +.RS 4
 +Set the
 +\fBsmb.conf\fR(5)
 +option "<name>" to value "<value>" from the command line\&. This overrides compiled\-in defaults and options read from the configuration file\&.
 +.RE
 +.PP
 +\-?|\-\-help
 +.RS 4
 +Print a summary of command line options\&.
 +.RE
 +.PP
 +\-\-usage
 +.RS 4
 +Display brief usage message\&.
 +.RE
 +.SH "FILES"
 +.PP
 +/etc/rc
 +.RS 4
 +or whatever initialization script your system uses\&.
 +.sp
 +If running the server as a daemon at startup, this file will need to contain an appropriate startup sequence for the server\&.
 +.RE
 +.PP
 +/etc/services
 +.RS 4
 +If running the server via the meta\-daemon
 +inetd, this file must contain a mapping of service name (e\&.g\&., netbios\-ssn) to service port (e\&.g\&., 139) and protocol type (e\&.g\&., tcp)\&.
 +.RE
 +.PP
 +/usr/local/samba/lib/smb\&.conf
 +.RS 4
 +This is the default location of the
 +\fBsmb.conf\fR(5)
 +server configuration file\&. Other common places that systems install this file are
 +/usr/samba/lib/smb\&.conf
 +and
 +/etc/samba/smb\&.conf\&.
 +.sp
 +This file describes all the services the server is to make available to clients\&. See
 +\fBsmb.conf\fR(5)
 +for more information\&.
 +.RE
 +.SH "DIAGNOSTICS"
 +.PP
 +Most diagnostics issued by the server are logged in a specified log file\&. The log file name is specified at compile time, but may be overridden on the command line\&.
 +.PP
 +The number and nature of diagnostics available depends on the debug level used by the server\&. If you have problems, set the debug level to 3 and peruse the log files\&.
 +.PP
 +Most messages are reasonably self\-explanatory\&. Unfortunately, at the time this man page was created, there are too many diagnostics available in the source code to warrant describing each and every diagnostic\&. At this stage your best bet is still to grep the source code and inspect the conditions that gave rise to the diagnostics you are seeing\&.
 +.SH "VERSION"
 +.PP
 +This man page is correct for version 4 of the Samba suite\&.
 +.SH "SEE ALSO"
 +.PP
 +\fBhosts_access\fR(5)\fBsmb.conf\fR(5),
 +\fBsmbclient\fR(8),
 +\fBsamba-tool\fR(8),
 +\fBsmbd\fR(8),
 +\fBnmbd\fR(8),
 +\fBwinbindd\fR(1), and the Internet RFC\*(Aqs
 +rfc1001\&.txt,
 +rfc1002\&.txt\&. In addition the CIFS (formerly SMB) specification is available as a link from the Web page
 +http://samba\&.org/cifs/\&.
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
diff --cc docs/manpages/sharesec.1
index c38d794,0000000..9761e1c
mode 100644,000000..100644
--- a/docs/manpages/sharesec.1
+++ b/docs/manpages/sharesec.1
@@@ -1,341 -1,0 +1,341 @@@
 +'\" t
 +.\"     Title: sharesec
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: User Commands
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "SHARESEC" "1" "12/01/2015" "Samba 4\&.3" "User Commands"
++.TH "SHARESEC" "1" "12/10/2015" "Samba 4\&.3" "User Commands"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +sharesec \- Set or get share ACLs
 +.SH "SYNOPSIS"
 +.HP \w'\ 'u
 +sharesec {sharename} [\-r,\ \-\-remove=ACL] [\-m,\ \-\-modify=ACL] [\-a,\ \-\-add=ACL] [\-R,\ \-\-replace=ACLs] [\-D,\ \-\-delete] [\-v,\ \-\-view] [\-\-view\-all] [\-M,\ \-\-machine\-sid] [\-F,\ \-\-force] [\-d,\ \-\-debuglevel=DEBUGLEVEL] [\-s,\ \-\-configfile=CONFIGFILE] [\-l,\ \-\-log\-basename=LOGFILEBASE] [\-\-version] [\-?,\ \-\-help] [\-\-usage] [\-S,\ \-\-setsddl=STRING] [\-V,\ \-\-viewsddl]
 +.SH "DESCRIPTION"
 +.PP
 +This tool is part of the
 +\fBsamba\fR(7)
 +suite\&.
 +.PP
 +The
 +sharesec
 +program manipulates share permissions on SMB file shares\&.
 +.SH "OPTIONS"
 +.PP
 +The following options are available to the
 +sharesec
 +program\&. The format of ACLs is described in the section ACL FORMAT
 +.PP
 +\-a|\-\-add=ACL
 +.RS 4
 +Add the ACEs specified to the ACL list\&.
 +.RE
 +.PP
 +\-D|\-\-delete
 +.RS 4
 +Delete the entire security descriptor\&.
 +.RE
 +.PP
 +\-F|\-\-force
 +.RS 4
 +Force storing the ACL\&.
 +.RE
 +.PP
 +\-m|\-\-modify=ACL
 +.RS 4
 +Modify existing ACEs\&.
 +.RE
 +.PP
 +\-M|\-\-machine\-sid
 +.RS 4
 +Initialize the machine SID\&.
 +.RE
 +.PP
 +\-r|\-\-remove=ACL
 +.RS 4
 +Remove ACEs\&.
 +.RE
 +.PP
 +\-R|\-\-replace=ACLS
 +.RS 4
 +Overwrite an existing share permission ACL\&.
 +.RE
 +.PP
 +\-v|\-\-view
 +.RS 4
 +List a share acl
 +.RE
 +.PP
 +\-\-view\-all
 +.RS 4
 +List all share acls
 +.RE
 +.PP
 +\-S|\-\-setsddl=STRING
 +.RS 4
 +Set security descriptor by providing ACL in SDDL format\&.
 +.RE
 +.PP
 +\-V|\-\-viewsddl
 +.RS 4
 +List a share acl in SDDL format\&.
 +.RE
 +.PP
 +\-?|\-\-help
 +.RS 4
 +Print a summary of command line options\&.
 +.RE
 +.PP
 +\-d|\-\-debuglevel=level
 +.RS 4
 +\fIlevel\fR
 +is an integer from 0 to 10\&. The default value if this parameter is not specified is 0\&.
 +.sp
 +The higher this value, the more detail will be logged to the log files about the activities of the server\&. At level 0, only critical errors and serious warnings will be logged\&. Level 1 is a reasonable level for day\-to\-day running \- it generates a small amount of information about operations carried out\&.
 +.sp
 +Levels above 1 will generate considerable amounts of log data, and should only be used when investigating a problem\&. Levels above 3 are designed for use only by developers and generate HUGE amounts of log data, most of which is extremely cryptic\&.
 +.sp
 +Note that specifying this parameter here will override the
 +\m[blue]\fBlog level\fR\m[]
 +parameter in the
 +smb\&.conf
 +file\&.
 +.RE
 +.PP
 +\-V|\-\-version
 +.RS 4
 +Prints the program version number\&.
 +.RE
 +.PP
 +\-s|\-\-configfile=<configuration file>
 +.RS 4
 +The file specified contains the configuration details required by the server\&. The information in this file includes server\-specific information such as what printcap file to use, as well as descriptions of all the services that the server is to provide\&. See
 +smb\&.conf
 +for more information\&. The default configuration file name is determined at compile time\&.
 +.RE
 +.PP
 +\-l|\-\-log\-basename=logdirectory
 +.RS 4
 +Base directory name for log/debug files\&. The extension
 +\fB"\&.progname"\fR
 +will be appended (e\&.g\&. log\&.smbclient, log\&.smbd, etc\&.\&.\&.)\&. The log file is never removed by the client\&.
 +.RE
 +.PP
 +\-\-option=<name>=<value>
 +.RS 4
 +Set the
 +\fBsmb.conf\fR(5)
 +option "<name>" to value "<value>" from the command line\&. This overrides compiled\-in defaults and options read from the configuration file\&.
 +.RE
 +.SH "ACL FORMAT"
 +.PP
 +The format of an ACL is one or more ACL entries separated by either commas or newlines\&. An ACL entry is one of the following:
 +.PP
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	REVISION:<revision number>
 +	OWNER:<sid or name>
 +	GROUP:<sid or name>
 +	ACL:<sid or name>:<type>/<flags>/<mask>
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +The revision of the ACL specifies the internal Windows NT ACL revision for the security descriptor\&. If not specified it defaults to 1\&. Using values other than 1 may cause strange behaviour\&.
 +.PP
 +The owner and group specify the owner and group SIDs for the object\&. Share ACLs do not specify an owner or a group, so these fields are empty\&.
 +.PP
 +ACLs specify permissions granted to the SID\&. This SID can be specified in S\-1\-x\-y\-z format or as a name in which case it is resolved against the server on which the file or directory resides\&. The type, flags and mask values determine the type of access granted to the SID\&.
 +.PP
 +The type can be either ALLOWED or DENIED to allow/deny access to the SID\&. The flags values are generally zero for share ACLs\&.
 +.PP
 +The mask is a value which expresses the access right granted to the SID\&. It can be given as a decimal or hexadecimal value, or by using one of the following text strings which map to the NT file permissions of the same name\&.
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIR\fR
 +\- Allow read access
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIW\fR
 +\- Allow write access
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIX\fR
 +\- Execute permission on the object
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fID\fR
 +\- Delete the object
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIP\fR
 +\- Change permissions
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIO\fR
 +\- Take ownership
 +.RE
 +.sp
 +.RE
 +.PP
 +The following combined permissions can be specified:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIREAD\fR
 +\- Equivalent to \*(AqRX\*(Aq permissions
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fICHANGE\fR
 +\- Equivalent to \*(AqRXWD\*(Aq permissions
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIFULL\fR
 +\- Equivalent to \*(AqRWXDPO\*(Aq permissions
 +.RE
 +.SH "EXIT STATUS"
 +.PP
 +The
 +sharesec
 +program sets the exit status depending on the success or otherwise of the operations performed\&. The exit status may be one of the following values\&.
 +.PP
 +If the operation succeeded, sharesec returns and exit status of 0\&. If
 +sharesec
 +couldn\*(Aqt connect to the specified server, or there was an error getting or setting the ACLs, an exit status of 1 is returned\&. If there was an error parsing any command line arguments, an exit status of 2 is returned\&.
 +.SH "EXAMPLES"
 +.PP
 +Add full access for SID
 +\fIS\-1\-5\-21\-1866488690\-1365729215\-3963860297\-17724\fR
 +on
 +\fIshare\fR:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	host:~ # sharesec share \-a S\-1\-5\-21\-1866488690\-1365729215\-3963860297\-17724:ALLOWED/0/FULL
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +List all ACEs for
 +\fIshare\fR:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	host:~ # sharesec share \-v
 +	REVISION:1
 +	CONTROL:SR|DP
 +	OWNER:
 +	GROUP:
 +	ACL:S\-1\-1\-0:ALLOWED/0x0/FULL
 +	ACL:S\-1\-5\-21\-1866488690\-1365729215\-3963860297\-17724:ALLOWED/0x0/FULL
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.SH "VERSION"
 +.PP
 +This man page is correct for version 3 of the Samba suite\&.
 +.SH "AUTHOR"
 +.PP
 +The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
diff --cc docs/manpages/smb.conf.5
index e35b68d,0000000..02ea1b6
mode 100644,000000..100644
--- a/docs/manpages/smb.conf.5
+++ b/docs/manpages/smb.conf.5
@@@ -1,12420 -1,0 +1,12420 @@@
 +'\" t
 +.\"     Title: smb.conf
 +.\"    Author: [see the "AUTHOR" section]
 +.\" Generator: DocBook XSL Stylesheets v1.78.1 <http://docbook.sf.net/>
- .\"      Date: 12/01/2015
++.\"      Date: 12/10/2015
 +.\"    Manual: File Formats and Conventions
 +.\"    Source: Samba 4.3
 +.\"  Language: English
 +.\"
- .TH "SMB\&.CONF" "5" "12/01/2015" "Samba 4\&.3" "File Formats and Conventions"
++.TH "SMB\&.CONF" "5" "12/10/2015" "Samba 4\&.3" "File Formats and Conventions"
 +.\" -----------------------------------------------------------------
 +.\" * Define some portability stuff
 +.\" -----------------------------------------------------------------
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.\" http://bugs.debian.org/507673
 +.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
 +.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 +.ie \n(.g .ds Aq \(aq
 +.el       .ds Aq '
 +.\" -----------------------------------------------------------------
 +.\" * set default formatting
 +.\" -----------------------------------------------------------------
 +.\" disable hyphenation
 +.nh
 +.\" disable justification (adjust text to left margin only)
 +.ad l
 +.\" -----------------------------------------------------------------
 +.\" * MAIN CONTENT STARTS HERE *
 +.\" -----------------------------------------------------------------
 +.SH "NAME"
 +smb.conf \- The configuration file for the Samba suite
 +.SH "SYNOPSIS"
 +.PP
 +The
 +smb\&.conf
 +file is a configuration file for the Samba suite\&.
 +smb\&.conf
 +contains runtime configuration information for the Samba programs\&. The complete description of the file format and possible parameters held within are here for reference purposes\&.
 +.SH "FILE FORMAT"
 +.PP
 +The file consists of sections and parameters\&. A section begins with the name of the section in square brackets and continues until the next section begins\&. Sections contain parameters of the form:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +\fIname\fR = \fIvalue \fR
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +The file is line\-based \- that is, each newline\-terminated line represents either a comment, a section name or a parameter\&.
 +.PP
 +Section and parameter names are not case sensitive\&.
 +.PP
 +Only the first equals sign in a parameter is significant\&. Whitespace before or after the first equals sign is discarded\&. Leading, trailing and internal whitespace in section and parameter names is irrelevant\&. Leading and trailing whitespace in a parameter value is discarded\&. Internal whitespace within a parameter value is retained verbatim\&.
 +.PP
 +Any line beginning with a semicolon (\(lq;\(rq) or a hash (\(lq#\(rq) character is ignored, as are lines containing only whitespace\&.
 +.PP
 +Any line ending in a
 +\(lq\e\(rq
 +is continued on the next line in the customary UNIX fashion\&.
 +.PP
 +The values following the equals sign in parameters are all either a string (no quotes needed) or a boolean, which may be given as yes/no, 1/0 or true/false\&. Case is not significant in boolean values, but is preserved in string values\&. Some items such as create masks are numeric\&.
 +.SH "SECTION DESCRIPTIONS"
 +.PP
 +Each section in the configuration file (except for the [global] section) describes a shared resource (known as a
 +\(lqshare\(rq)\&. The section name is the name of the shared resource and the parameters within the section define the shares attributes\&.
 +.PP
 +There are three special sections, [global], [homes] and [printers], which are described under
 +\fIspecial sections\fR\&. The following notes apply to ordinary section descriptions\&.
 +.PP
 +A share consists of a directory to which access is being given plus a description of the access rights which are granted to the user of the service\&. Some housekeeping options are also specifiable\&.
 +.PP
 +Sections are either file share services (used by the client as an extension of their native file systems) or printable services (used by the client to access print services on the host running the server)\&.
 +.PP
 +Sections may be designated
 +\fIguest\fR
 +services, in which case no password is required to access them\&. A specified UNIX
 +\fIguest account\fR
 +is used to define access privileges in this case\&.
 +.PP
 +Sections other than guest services will require a password to access them\&. The client provides the username\&. As older clients only provide passwords and not usernames, you may specify a list of usernames to check against the password using the
 +user =
 +option in the share definition\&. For modern clients such as Windows 95/98/ME/NT/2000, this should not be necessary\&.
 +.PP
 +The access rights granted by the server are masked by the access rights granted to the specified or guest UNIX user by the host system\&. The server does not grant more access than the host system grants\&.
 +.PP
 +The following sample section defines a file space share\&. The user has write access to the path
 +/home/bar\&. The share is accessed via the share name
 +foo:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	\fI[foo]\fR
 +	\m[blue]\fBpath = /home/bar\fR\m[]
 +	\m[blue]\fBread only = no\fR\m[]
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +The following sample section defines a printable share\&. The share is read\-only, but printable\&. That is, the only write access permitted is via calls to open, write to and close a spool file\&. The
 +\fIguest ok\fR
 +parameter means access will be permitted as the default guest user (specified elsewhere):
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	\fI[aprinter]\fR
 +	\m[blue]\fBpath = /usr/spool/public\fR\m[]
 +	\m[blue]\fBread only = yes\fR\m[]
 +	\m[blue]\fBprintable = yes\fR\m[]
 +	\m[blue]\fBguest ok = yes\fR\m[]
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.sp
 +.SH "SPECIAL SECTIONS"
 +.SS "The [global] section"
 +.PP
 +Parameters in this section apply to the server as a whole, or are defaults for sections that do not specifically define certain items\&. See the notes under PARAMETERS for more information\&.
 +.SS "The [homes] section"
 +.PP
 +If a section called [homes] is included in the configuration file, services connecting clients to their home directories can be created on the fly by the server\&.
 +.PP
 +When the connection request is made, the existing sections are scanned\&. If a match is found, it is used\&. If no match is found, the requested section name is treated as a username and looked up in the local password file\&. If the name exists and the correct password has been given, a share is created by cloning the [homes] section\&.
 +.PP
 +Some modifications are then made to the newly created share:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +The share name is changed from homes to the located username\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +If no path was given, the path is set to the user\*(Aqs home directory\&.
 +.RE
 +.sp
 +.RE
 +.PP
 +If you decide to use a
 +\fIpath =\fR
 +line in your [homes] section, it may be useful to use the %S macro\&. For example:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +\fBpath = /data/pchome/%S\fR
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.sp
 +is useful if you have different home directories for your PCs than for UNIX access\&.
 +.PP
 +This is a fast and simple way to give a large number of clients access to their home directories with a minimum of fuss\&.
 +.PP
 +A similar process occurs if the requested section name is
 +\(lqhomes\(rq, except that the share name is not changed to that of the requesting user\&. This method of using the [homes] section works well if different users share a client PC\&.
 +.PP
 +The [homes] section can specify all the parameters a normal service section can specify, though some make more sense than others\&. The following is a typical and suitable [homes] section:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +\fI[homes]\fR
 +\m[blue]\fBread only = no\fR\m[]
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +An important point is that if guest access is specified in the [homes] section, all home directories will be visible to all clients
 +\fIwithout a password\fR\&. In the very unlikely event that this is actually desirable, it is wise to also specify
 +\fIread only access\fR\&.
 +.PP
 +The
 +\fIbrowseable\fR
 +flag for auto home directories will be inherited from the global browseable flag, not the [homes] browseable flag\&. This is useful as it means setting
 +\fIbrowseable = no\fR
 +in the [homes] section will hide the [homes] share but make any auto home directories visible\&.
 +.SS "The [printers] section"
 +.PP
 +This section works like [homes], but for printers\&.
 +.PP
 +If a [printers] section occurs in the configuration file, users are able to connect to any printer specified in the local host\*(Aqs printcap file\&.
 +.PP
 +When a connection request is made, the existing sections are scanned\&. If a match is found, it is used\&. If no match is found, but a [homes] section exists, it is used as described above\&. Otherwise, the requested section name is treated as a printer name and the appropriate printcap file is scanned to see if the requested section name is a valid printer share name\&. If a match is found, a new printer share is created by cloning the [printers] section\&.
 +.PP
 +A few modifications are then made to the newly created share:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +The share name is set to the located printer name
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +If no printer name was given, the printer name is set to the located printer name
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +If the share does not permit guest access and no username was given, the username is set to the located printer name\&.
 +.RE
 +.sp
 +.RE
 +.PP
 +The [printers] service MUST be printable \- if you specify otherwise, the server will refuse to load the configuration file\&.
 +.PP
 +Typically the path specified is that of a world\-writeable spool directory with the sticky bit set on it\&. A typical [printers] entry looks like this:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +\fI[printers]\fR
 +\m[blue]\fBpath = /usr/spool/public\fR\m[]
 +\m[blue]\fBguest ok = yes\fR\m[]
 +\m[blue]\fBprintable = yes\fR\m[]
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +All aliases given for a printer in the printcap file are legitimate printer names as far as the server is concerned\&. If your printing subsystem doesn\*(Aqt work like that, you will have to set up a pseudo\-printcap\&. This is a file consisting of one or more lines like this:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +alias|alias|alias|alias\&.\&.\&.    
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +Each alias should be an acceptable printer name for your printing subsystem\&. In the [global] section, specify the new file as your printcap\&. The server will only recognize names found in your pseudo\-printcap, which of course can contain whatever aliases you like\&. The same technique could be used simply to limit access to a subset of your local printers\&.
 +.PP
 +An alias, by the way, is defined as any component of the first entry of a printcap record\&. Records are separated by newlines, components (if there are more than one) are separated by vertical bar symbols (|)\&.
 +.if n \{\
 +.sp
 +.\}
 +.RS 4
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBNote\fR
 +.ps -1
 +.br
 +.PP
 +On SYSV systems which use lpstat to determine what printers are defined on the system you may be able to use
 +printcap name = lpstat
 +to automatically obtain a list of printers\&. See the
 +printcap name
 +option for more details\&.
 +.sp .5v
 +.RE
 +.SH "USERSHARES"
 +.PP
 +Starting with Samba version 3\&.0\&.23 the capability for non\-root users to add, modify, and delete their own share definitions has been added\&. This capability is called
 +\fIusershares\fR
 +and is controlled by a set of parameters in the [global] section of the smb\&.conf\&. The relevant parameters are :
 +.PP
 +usershare allow guests
 +.RS 4
 +Controls if usershares can permit guest access\&.
 +.RE
 +.PP
 +usershare max shares
 +.RS 4
 +Maximum number of user defined shares allowed\&.
 +.RE
 +.PP
 +usershare owner only
 +.RS 4
 +If set only directories owned by the sharing user can be shared\&.
 +.RE
 +.PP
 +usershare path
 +.RS 4
 +Points to the directory containing the user defined share definitions\&. The filesystem permissions on this directory control who can create user defined shares\&.
 +.RE
 +.PP
 +usershare prefix allow list
 +.RS 4
 +Comma\-separated list of absolute pathnames restricting what directories can be shared\&. Only directories below the pathnames in this list are permitted\&.
 +.RE
 +.PP
 +usershare prefix deny list
 +.RS 4
 +Comma\-separated list of absolute pathnames restricting what directories can be shared\&. Directories below the pathnames in this list are prohibited\&.
 +.RE
 +.PP
 +usershare template share
 +.RS 4
 +Names a pre\-existing share used as a template for creating new usershares\&. All other share parameters not specified in the user defined share definition are copied from this named share\&.
 +.RE
 +.PP
 +To allow members of the UNIX group
 +foo
 +to create user defined shares, create the directory to contain the share definitions as follows:
 +.PP
 +Become root:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +mkdir /usr/local/samba/lib/usershares
 +chgrp foo /usr/local/samba/lib/usershares
 +chmod 1770 /usr/local/samba/lib/usershares
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.PP
 +Then add the parameters
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	\m[blue]\fBusershare path = /usr/local/samba/lib/usershares\fR\m[]
 +	\m[blue]\fBusershare max shares = 10\fR\m[] # (or the desired number of shares)
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.sp
 +to the global section of your
 +smb\&.conf\&. Members of the group foo may then manipulate the user defined shares using the following commands\&.
 +.PP
 +net usershare add sharename path [comment] [acl] [guest_ok=[y|n]]
 +.RS 4
 +To create or modify (overwrite) a user defined share\&.
 +.RE
 +.PP
 +net usershare delete sharename
 +.RS 4
 +To delete a user defined share\&.
 +.RE
 +.PP
 +net usershare list wildcard\-sharename
 +.RS 4
 +To list user defined shares\&.
 +.RE
 +.PP
 +net usershare info wildcard\-sharename
 +.RS 4
 +To print information about user defined shares\&.
 +.RE
 +.SH "PARAMETERS"
 +.PP
 +Parameters define the specific attributes of sections\&.
 +.PP
 +Some parameters are specific to the [global] section (e\&.g\&.,
 +\fIsecurity\fR)\&. Some parameters are usable in all sections (e\&.g\&.,
 +\fIcreate mask\fR)\&. All others are permissible only in normal sections\&. For the purposes of the following descriptions the [homes] and [printers] sections will be considered normal\&. The letter
 +\fIG\fR
 +in parentheses indicates that a parameter is specific to the [global] section\&. The letter
 +\fIS\fR
 +indicates that a parameter can be specified in a service specific section\&. All
 +\fIS\fR
 +parameters can also be specified in the [global] section \- in which case they will define the default behavior for all services\&.
 +.PP
 +Parameters are arranged here in alphabetical order \- this may not create best bedfellows, but at least you can find them! Where there are synonyms, the preferred synonym is described, others refer to the preferred synonym\&.
 +.SH "VARIABLE SUBSTITUTIONS"
 +.PP
 +Many of the strings that are settable in the config file can take substitutions\&. For example the option
 +\(lqpath = /tmp/%u\(rq
 +is interpreted as
 +\(lqpath = /tmp/john\(rq
 +if the user connected with the username john\&.
 +.PP
 +These substitutions are mostly noted in the descriptions below, but there are some general substitutions which apply whenever they might be relevant\&. These are:
 +.PP
 +%U
 +.RS 4
 +session username (the username that the client wanted, not necessarily the same as the one they got)\&.
 +.RE
 +.PP
 +%G
 +.RS 4
 +primary group name of %U\&.
 +.RE
 +.PP
 +%h
 +.RS 4
 +the Internet hostname that Samba is running on\&.
 +.RE
 +.PP
 +%m
 +.RS 4
 +the NetBIOS name of the client machine (very useful)\&.
 +.sp
 +This parameter is not available when Samba listens on port 445, as clients no longer send this information\&. If you use this macro in an include statement on a domain that has a Samba domain controller be sure to set in the [global] section
 +\fIsmb ports = 139\fR\&. This will cause Samba to not listen on port 445 and will permit include functionality to function as it did with Samba 2\&.x\&.
 +.RE
 +.PP
 +%L
 +.RS 4
 +the NetBIOS name of the server\&. This allows you to change your config based on what the client calls you\&. Your server can have a
 +\(lqdual personality\(rq\&.
 +.RE
 +.PP
 +%M
 +.RS 4
 +the Internet name of the client machine\&.
 +.RE
 +.PP
 +%R
 +.RS 4
 +the selected protocol level after protocol negotiation\&. It can be one of CORE, COREPLUS, LANMAN1, LANMAN2, NT1, SMB2_02, SMB2_10, SMB2_22, SMB2_24, SMB3_00, SMB3_02, SMB3_10, SMB3_11 or SMB2_FF\&.
 +.RE
 +.PP
 +%d
 +.RS 4
 +the process id of the current server process\&.
 +.RE
 +.PP
 +%a
 +.RS 4
 +The architecture of the remote machine\&. It currently recognizes Samba (\fBSamba\fR), the Linux CIFS file system (\fBCIFSFS\fR), OS/2, (\fBOS2\fR), Mac OS X (\fBOSX\fR), Windows for Workgroups (\fBWfWg\fR), Windows 9x/ME (\fBWin95\fR), Windows NT (\fBWinNT\fR), Windows 2000 (\fBWin2K\fR), Windows XP (\fBWinXP\fR), Windows XP 64\-bit(\fBWinXP64\fR), Windows 2003 including 2003R2 (\fBWin2K3\fR), and Windows Vista (\fBVista\fR)\&. Anything else will be known as
 +\fBUNKNOWN\fR\&.
 +.RE
 +.PP
 +%I
 +.RS 4
 +the IP address of the client machine\&.
 +.sp
 +Before 4\&.0\&.0 it could contain IPv4 mapped IPv6 addresses, now it only contains IPv4 or IPv6 addresses\&.
 +.RE
 +.PP
 +%i
 +.RS 4
 +the local IP address to which a client connected\&.
 +.sp
 +Before 4\&.0\&.0 it could contain IPv4 mapped IPv6 addresses, now it only contains IPv4 or IPv6 addresses\&.
 +.RE
 +.PP
 +%T
 +.RS 4
 +the current date and time\&.
 +.RE
 +.PP
 +%D
 +.RS 4
 +name of the domain or workgroup of the current user\&.
 +.RE
 +.PP
 +%w
 +.RS 4
 +the winbind separator\&.
 +.RE
 +.PP
 +%$(\fIenvvar\fR)
 +.RS 4
 +the value of the environment variable
 +\fIenvar\fR\&.
 +.RE
 +.PP
 +The following substitutes apply only to some configuration options (only those that are used when a connection has been established):
 +.PP
 +%S
 +.RS 4
 +the name of the current service, if any\&.
 +.RE
 +.PP
 +%P
 +.RS 4
 +the root directory of the current service, if any\&.
 +.RE
 +.PP
 +%u
 +.RS 4
 +username of the current service, if any\&.
 +.RE
 +.PP
 +%g
 +.RS 4
 +primary group name of %u\&.
 +.RE
 +.PP
 +%H
 +.RS 4
 +the home directory of the user given by %u\&.
 +.RE
 +.PP
 +%N
 +.RS 4
 +the name of your NIS home directory server\&. This is obtained from your NIS auto\&.map entry\&. If you have not compiled Samba with the
 +\fI\-\-with\-automount\fR
 +option, this value will be the same as %L\&.
 +.RE
 +.PP
 +%p
 +.RS 4
 +the path of the service\*(Aqs home directory, obtained from your NIS auto\&.map entry\&. The NIS auto\&.map entry is split up as
 +%N:%p\&.
 +.RE
 +.PP
 +There are some quite creative things that can be done with these substitutions and other
 +smb\&.conf
 +options\&.
 +.SH "NAME MANGLING"
 +.PP
 +Samba supports
 +name mangling
 +so that DOS and Windows clients can use files that don\*(Aqt conform to the 8\&.3 format\&. It can also be set to adjust the case of 8\&.3 format filenames\&.
 +.PP
 +There are several options that control the way mangling is performed, and they are grouped here rather than listed separately\&. For the defaults look at the output of the testparm program\&.
 +.PP
 +These options can be set separately for each service\&.
 +.PP
 +The options are:
 +.PP
 +case sensitive = yes/no/auto
 +.RS 4
 +controls whether filenames are case sensitive\&. If they aren\*(Aqt, Samba must do a filename search and match on passed names\&. The default setting of auto allows clients that support case sensitive filenames (Linux CIFSVFS and smbclient 3\&.0\&.5 and above currently) to tell the Samba server on a per\-packet basis that they wish to access the file system in a case\-sensitive manner (to support UNIX case sensitive semantics)\&. No Windows or DOS system supports case\-sensitive filenam [...]
 +\fIauto\fR\&.
 +.RE
 +.PP
 +default case = upper/lower
 +.RS 4
 +controls what the default case is for new filenames (ie\&. files that don\*(Aqt currently exist in the filesystem)\&. Default
 +\fIlower\fR\&. IMPORTANT NOTE: As part of the optimizations for directories containing large numbers of files, the following special case applies\&. If the options
 +\m[blue]\fBcase sensitive = yes\fR\m[],
 +\m[blue]\fBpreserve case = No\fR\m[], and
 +\m[blue]\fBshort preserve case = No\fR\m[]
 +are set, then the case of
 +\fIall\fR
 +incoming client filenames, not just new filenames, will be modified\&. See additional notes below\&.
 +.RE
 +.PP
 +preserve case = yes/no
 +.RS 4
 +controls whether new files (ie\&. files that don\*(Aqt currently exist in the filesystem) are created with the case that the client passes, or if they are forced to be the
 +default
 +case\&. Default
 +\fIyes\fR\&.
 +.RE
 +.PP
 +short preserve case = yes/no
 +.RS 4
 +controls if new files (ie\&. files that don\*(Aqt currently exist in the filesystem) which conform to 8\&.3 syntax, that is all in upper case and of suitable length, are created upper case, or if they are forced to be the
 +default
 +case\&. This option can be used with
 +preserve case = yes
 +to permit long filenames to retain their case, while short names are lowercased\&. Default
 +\fIyes\fR\&.
 +.RE
 +.PP
 +By default, Samba 3\&.0 has the same semantics as a Windows NT server, in that it is case insensitive but case preserving\&. As a special case for directories with large numbers of files, if the case options are set as follows, "case sensitive = yes", "case preserve = no", "short preserve case = no" then the "default case" option will be applied and will modify all filenames sent from the client when accessing this share\&.
 +.SH "REGISTRY-BASED CONFIGURATION"
 +.PP
 +Starting with Samba version 3\&.2\&.0, the capability to store Samba configuration in the registry is available\&. The configuration is stored in the registry key
 +\fIHKLM\eSoftware\eSamba\esmbconf\fR\&. There are two levels of registry configuration:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04' 1.\h'+01'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP "  1." 4.2
 +.\}
 +Share definitions stored in registry are used\&. This is triggered by setting the global parameter
 +\fIregistry shares\fR
 +to
 +\(lqyes\(rq
 +in
 +\fIsmb\&.conf\fR\&.
 +.sp
 +The registry shares are loaded not at startup but on demand at runtime by
 +\fIsmbd\fR\&. Shares defined in
 +\fIsmb\&.conf\fR
 +take priority over shares of the same name defined in registry\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04' 2.\h'+01'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP "  2." 4.2
 +.\}
 +Global
 +\fIsmb\&.conf\fR
 +options stored in registry are used\&. This can be activated in two different ways:
 +.sp
 +Firstly, a registry only configuration is triggered by setting
 +\m[blue]\fBconfig backend = registry\fR\m[]
 +in the [global] section of
 +\fIsmb\&.conf\fR\&. This resets everything that has been read from config files to this point and reads the content of the global configuration section from the registry\&. This is the recommended method of using registry based configuration\&.
 +.sp
 +Secondly, a mixed configuration can be activated by a special new meaning of the parameter
 +\m[blue]\fBinclude = registry\fR\m[]
 +in the [global] section of
 +\fIsmb\&.conf\fR\&. This reads the global options from registry with the same priorities as for an include of a text file\&. This may be especially useful in cases where an initial configuration is needed to access the registry\&.
 +.sp
 +Activation of global registry options automatically activates registry shares\&. So in the registry only case, shares are loaded on demand only\&.
 +.RE
 +.sp
 +.RE
 +.PP
 +Note: To make registry\-based configurations foolproof at least to a certain extent, the use of
 +\fIlock directory\fR
 +and
 +\fIconfig backend\fR
 +inside the registry configuration has been disabled: Especially by changing the
 +\fIlock directory\fR
 +inside the registry configuration, one would create a broken setup where the daemons do not see the configuration they loaded once it is active\&.
 +.PP
 +The registry configuration can be accessed with tools like
 +\fIregedit\fR
 +or
 +\fInet (rpc) registry\fR
 +in the key
 +\fIHKLM\eSoftware\eSamba\esmbconf\fR\&. More conveniently, the
 +\fIconf\fR
 +subcommand of the
 +\fBnet\fR(8)
 +utility offers a dedicated interface to read and write the registry based configuration locally, i\&.e\&. directly accessing the database file, circumventing the server\&.
 +.SH "EXPLANATION OF EACH PARAMETER"
 +
 +
 +abort shutdown script (G)
 +.\" abort shutdown script
 +.PP
 +.RS 4
 +This a full path name to a script called by
 +\fBsmbd\fR(8)
 +that should stop a shutdown procedure issued by the
 +\m[blue]\fBshutdown script\fR\m[]\&.
 +.sp
 +If the connected user possesses the
 +\fBSeRemoteShutdownPrivilege\fR, right, this command will be run as root\&.
 +.sp
 +Default:
 +\fI\fIabort shutdown script\fR\fR\fI = \fR\fI""\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIabort shutdown script\fR\fR\fI = \fR\fI/sbin/shutdown \-c\fR\fI \fR
 +.RE
 +
 +access based share enum (S)
 +.\" access based share enum
 +.PP
 +.RS 4
 +If this parameter is
 +\fByes\fR
 +for a service, then the share hosted by the service will only be visible to users who have read or write access to the share during share enumeration (for example net view \e\esambaserver)\&. The share ACLs which allow or deny the access to the share can be modified using for example the
 +sharesec
 +command or using the appropriate Windows tools\&. This has parallels to access based enumeration, the main difference being that only share permissions are evaluated, and security descriptors on files contained on the share are not used in computing enumeration access rights\&.
 +.sp
 +Default:
 +\fI\fIaccess based share enum\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +acl allow execute always (S)
 +.\" acl allow execute always
 +.PP
 +.RS 4
 +This boolean parameter controls the behaviour of
 +\fBsmbd\fR(8)
 +when receiving a protocol request of "open for execution" from a Windows client\&. With Samba 3\&.6 and older, the execution right in the ACL was not checked, so a client could execute a file even if it did not have execute rights on the file\&. In Samba 4\&.0, this has been fixed, so that by default, i\&.e\&. when this parameter is set to "False", "open for execution" is now denied when execution permissions are not present\&.
 +.sp
 +If this parameter is set to "True", Samba does not check execute permissions on "open for execution", thus re\-establishing the behaviour of Samba 3\&.6\&. This can be useful to smoothen upgrades from older Samba versions to 4\&.0 and newer\&. This setting is not meant to be used as a permanent setting, but as a temporary relief: It is recommended to fix the permissions in the ACLs and reset this parameter to the default after a certain transition period\&.
 +.sp
 +Default:
 +\fI\fIacl allow execute always\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +acl check permissions (S)
 +.\" acl check permissions
 +.PP
 +.RS 4
 +Please note this parameter is now deprecated in Samba 3\&.6\&.2 and will be removed in a future version of Samba\&.
 +.sp
 +This boolean parameter controls what
 +\fBsmbd\fR(8)
 +does on receiving a protocol request of "open for delete" from a Windows client\&. If a Windows client doesn\*(Aqt have permissions to delete a file then they expect this to be denied at open time\&. POSIX systems normally only detect restrictions on delete by actually attempting to delete the file or directory\&. As Windows clients can (and do) "back out" a delete request by unsetting the "delete on close" bit Samba cannot delete the file immediately on "open for delete" request as we  [...]
 +.sp
 +If this parameter is set to "false" Samba doesn\*(Aqt check permissions on "open for delete" and allows the open\&. If the user doesn\*(Aqt have permission to delete the file this will only be discovered at close time, which is too late for the Windows user tools to display an error message to the user\&. The symptom of this is files that appear to have been deleted "magically" re\-appearing on a Windows explorer refresh\&. This is an extremely advanced protocol option which should not  [...]
 +.sp
 +Default:
 +\fI\fIacl check permissions\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +acl group control (S)
 +.\" acl group control
 +.PP
 +.RS 4
 +In a POSIX filesystem, only the owner of a file or directory and the superuser can modify the permissions and ACLs on a file\&. If this parameter is set, then Samba overrides this restriction, and also allows the
 +\fIprimary group owner\fR
 +of a file or directory to modify the permissions and ACLs on that file\&.
 +.sp
 +On a Windows server, groups may be the owner of a file or directory \- thus allowing anyone in that group to modify the permissions on it\&. This allows the delegation of security controls on a point in the filesystem to the group owner of a directory and anything below it also owned by that group\&. This means there are multiple people with permissions to modify ACLs on a file or directory, easing manageability\&.
 +.sp
 +This parameter allows Samba to also permit delegation of the control over a point in the exported directory hierarchy in much the same way as Windows\&. This allows all members of a UNIX group to control the permissions on a file or directory they have group ownership on\&.
 +.sp
 +This parameter is best used with the
 +\m[blue]\fBinherit owner\fR\m[]
 +option and also on a share containing directories with the UNIX
 +\fIsetgid bit\fR
 +set on them, which causes new files and directories created within it to inherit the group ownership from the containing directory\&.
 +.sp
 +This parameter was deprecated in Samba 3\&.0\&.23, but re\-activated in Samba 3\&.0\&.31 and above, as it now only controls permission changes if the user is in the owning primary group\&. It is now no longer equivalent to the
 +\fIdos filemode\fR
 +option\&.
 +.sp
 +Default:
 +\fI\fIacl group control\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +acl map full control (S)
 +.\" acl map full control
 +.PP
 +.RS 4
 +This boolean parameter controls whether
 +\fBsmbd\fR(8)
 +maps a POSIX ACE entry of "rwx" (read/write/execute), the maximum allowed POSIX permission set, into a Windows ACL of "FULL CONTROL"\&. If this parameter is set to true any POSIX ACE entry of "rwx" will be returned in a Windows ACL as "FULL CONTROL", is this parameter is set to false any POSIX ACE entry of "rwx" will be returned as the specific Windows ACL bits representing read, write and execute\&.
 +.sp
 +Default:
 +\fI\fIacl map full control\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +add group script (G)
 +.\" add group script
 +.PP
 +.RS 4
 +This is the full pathname to a script that will be run
 +\fIAS ROOT\fR
 +by
 +\fBsmbd\fR(8)
 +when a new group is requested\&. It will expand any
 +\fI%g\fR
 +to the group name passed\&. This script is only useful for installations using the Windows NT domain administration tools\&. The script is free to create a group with an arbitrary name to circumvent unix group name restrictions\&. In that case the script must print the numeric gid of the created group on stdout\&.
 +.sp
 +Default:
 +\fI\fIadd group script\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIadd group script\fR\fR\fI = \fR\fI/usr/sbin/groupadd %g\fR\fI \fR
 +.RE
 +
 +add machine script (G)
 +.\" add machine script
 +.PP
 +.RS 4
 +This is the full pathname to a script that will be run by
 +\fBsmbd\fR(8)
 +when a machine is added to Samba\*(Aqs domain and a Unix account matching the machine\*(Aqs name appended with a "$" does not already exist\&.
 +.sp
 +This option is very similar to the
 +\m[blue]\fBadd user script\fR\m[], and likewise uses the %u substitution for the account name\&. Do not use the %m substitution\&.
 +.sp
 +Default:
 +\fI\fIadd machine script\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIadd machine script\fR\fR\fI = \fR\fI/usr/sbin/adduser \-n \-g machines \-c Machine \-d /var/lib/nobody \-s /bin/false %u\fR\fI \fR
 +.RE
 +
 +addport command (G)
 +.\" addport command
 +.PP
 +.RS 4
 +Samba 3\&.0\&.23 introduced support for adding printer ports remotely using the Windows "Add Standard TCP/IP Port Wizard"\&. This option defines an external program to be executed when smbd receives a request to add a new Port to the system\&. The script is passed two parameters:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIport name\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIdevice URI\fR
 +.RE
 +.sp
 +.RE
 +The deviceURI is in the format of socket://<hostname>[:<portnumber>] or lpd://<hostname>/<queuename>\&.
 +.sp
 +Default:
 +\fI\fIaddport command\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIaddport command\fR\fR\fI = \fR\fI/etc/samba/scripts/addport\&.sh\fR\fI \fR
 +.RE
 +
 +addprinter command (G)
 +.\" addprinter command
 +.PP
 +.RS 4
 +With the introduction of MS\-RPC based printing support for Windows NT/2000 clients in Samba 2\&.2, The MS Add Printer Wizard (APW) icon is now also available in the "Printers\&.\&.\&." folder displayed a share listing\&. The APW allows for printers to be add remotely to a Samba or Windows NT/2000 print server\&.
 +.sp
 +For a Samba host this means that the printer must be physically added to the underlying printing system\&. The
 +\fIaddprinter command\fR
 +defines a script to be run which will perform the necessary operations for adding the printer to the print system and to add the appropriate service definition to the
 +smb\&.conf
 +file in order that it can be shared by
 +\fBsmbd\fR(8)\&.
 +.sp
 +The
 +\fIaddprinter command\fR
 +is automatically invoked with the following parameter (in order):
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIprinter name\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIshare name\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIport name\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIdriver name\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIlocation\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIWindows 9x driver location\fR
 +.RE
 +.sp
 +.RE
 +All parameters are filled in from the PRINTER_INFO_2 structure sent by the Windows NT/2000 client with one exception\&. The "Windows 9x driver location" parameter is included for backwards compatibility only\&. The remaining fields in the structure are generated from answers to the APW questions\&.
 +.sp
 +Once the
 +\fIaddprinter command\fR
 +has been executed,
 +smbd
 +will reparse the
 +smb\&.conf
 +to determine if the share defined by the APW exists\&. If the sharename is still invalid, then
 +smbd
 +will return an ACCESS_DENIED error to the client\&.
 +.sp
 +The
 +\fIaddprinter command\fR
 +program can output a single line of text, which Samba will set as the port the new printer is connected to\&. If this line isn\*(Aqt output, Samba won\*(Aqt reload its printer shares\&.
 +.sp
 +Default:
 +\fI\fIaddprinter command\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIaddprinter command\fR\fR\fI = \fR\fI/usr/bin/addprinter\fR\fI \fR
 +.RE
 +
 +add share command (G)
 +.\" add share command
 +.PP
 +.RS 4
 +Samba 2\&.2\&.0 introduced the ability to dynamically add and delete shares via the Windows NT 4\&.0 Server Manager\&. The
 +\fIadd share command\fR
 +is used to define an external program or script which will add a new service definition to
 +smb\&.conf\&.
 +.sp
 +In order to successfully execute the
 +\fIadd share command\fR,
 +smbd
 +requires that the administrator connects using a root account (i\&.e\&. uid == 0) or has the
 +SeDiskOperatorPrivilege\&. Scripts defined in the
 +\fIadd share command\fR
 +parameter are executed as root\&.
 +.sp
 +When executed,
 +smbd
 +will automatically invoke the
 +\fIadd share command\fR
 +with five parameters\&.
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIconfigFile\fR
 +\- the location of the global
 +smb\&.conf
 +file\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIshareName\fR
 +\- the name of the new share\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIpathName\fR
 +\- path to an **existing** directory on disk\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIcomment\fR
 +\- comment string to associate with the new share\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fImax connections\fR
 +Number of maximum simultaneous connections to this share\&.
 +.RE
 +.sp
 +.RE
 +This parameter is only used to add file shares\&. To add printer shares, see the
 +\m[blue]\fBaddprinter command\fR\m[]\&.
 +.sp
 +Default:
 +\fI\fIadd share command\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIadd share command\fR\fR\fI = \fR\fI/usr/local/bin/addshare\fR\fI \fR
 +.RE
 +
 +add user script (G)
 +.\" add user script
 +.PP
 +.RS 4
 +This is the full pathname to a script that will be run
 +\fIAS ROOT\fR
 +by
 +\fBsmbd\fR(8)
 +under special circumstances described below\&.
 +.sp
 +Normally, a Samba server requires that UNIX users are created for all users accessing files on this server\&. For sites that use Windows NT account databases as their primary user database creating these users and keeping the user list in sync with the Windows NT PDC is an onerous task\&. This option allows smbd to create the required UNIX users
 +\fION DEMAND\fR
 +when a user accesses the Samba server\&.
 +.sp
 +When the Windows user attempts to access the Samba server, at login (session setup in the SMB protocol) time,
 +\fBsmbd\fR(8)
 +contacts the
 +\m[blue]\fBpassword server\fR\m[]
 +and attempts to authenticate the given user with the given password\&. If the authentication succeeds then
 +smbd
 +attempts to find a UNIX user in the UNIX password database to map the Windows user into\&. If this lookup fails, and
 +\m[blue]\fBadd user script\fR\m[]
 +is set then
 +smbd
 +will call the specified script
 +\fIAS ROOT\fR, expanding any
 +\fI%u\fR
 +argument to be the user name to create\&.
 +.sp
 +If this script successfully creates the user then
 +smbd
 +will continue on as though the UNIX user already existed\&. In this way, UNIX users are dynamically created to match existing Windows NT accounts\&.
 +.sp
 +See also
 +\m[blue]\fBsecurity\fR\m[],
 +\m[blue]\fBpassword server\fR\m[],
 +\m[blue]\fBdelete user script\fR\m[]\&.
 +.sp
 +Default:
 +\fI\fIadd user script\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIadd user script\fR\fR\fI = \fR\fI/usr/local/samba/bin/add_user %u\fR\fI \fR
 +.RE
 +
 +add user to group script (G)
 +.\" add user to group script
 +.PP
 +.RS 4
 +Full path to the script that will be called when a user is added to a group using the Windows NT domain administration tools\&. It will be run by
 +\fBsmbd\fR(8)\fIAS ROOT\fR\&. Any
 +\fI%g\fR
 +will be replaced with the group name and any
 +\fI%u\fR
 +will be replaced with the user name\&.
 +.sp
 +Note that the
 +adduser
 +command used in the example below does not support the used syntax on all systems\&.
 +.sp
 +Default:
 +\fI\fIadd user to group script\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIadd user to group script\fR\fR\fI = \fR\fI/usr/sbin/adduser %u %g\fR\fI \fR
 +.RE
 +
 +administrative share (S)
 +.\" administrative share
 +.PP
 +.RS 4
 +If this parameter is set to
 +\fByes\fR
 +for a share, then the share will be an administrative share\&. The Administrative Shares are the default network shares created by all Windows NT\-based operating systems\&. These are shares like C$, D$ or ADMIN$\&. The type of these shares is STYPE_DISKTREE_HIDDEN\&.
 +.sp
 +See the section below on
 +\m[blue]\fBsecurity\fR\m[]
 +for more information about this option\&.
 +.sp
 +Default:
 +\fI\fIadministrative share\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +admin users (S)
 +.\" admin users
 +.PP
 +.RS 4
 +This is a list of users who will be granted administrative privileges on the share\&. This means that they will do all file operations as the super\-user (root)\&.
 +.sp
 +You should use this option very carefully, as any user in this list will be able to do anything they like on the share, irrespective of file permissions\&.
 +.sp
 +Default:
 +\fI\fIadmin users\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIadmin users\fR\fR\fI = \fR\fIjason\fR\fI \fR
 +.RE
 +
 +afs share (S)
 +.\" afs share
 +.PP
 +.RS 4
 +This parameter controls whether special AFS features are enabled for this share\&. If enabled, it assumes that the directory exported via the
 +\fIpath\fR
 +parameter is a local AFS import\&. The special AFS features include the attempt to hand\-craft an AFS token if you enabled \-\-with\-fake\-kaserver in configure\&.
 +.sp
 +Default:
 +\fI\fIafs share\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +afs token lifetime (G)
 +.\" afs token lifetime
 +.PP
 +.RS 4
 +This parameter controls the lifetime of tokens that the AFS fake\-kaserver claims\&. In reality these never expire but this lifetime controls when the afs client will forget the token\&.
 +.sp
 +Set this parameter to 0 to get
 +\fBNEVERDATE\fR\&.
 +.sp
 +Default:
 +\fI\fIafs token lifetime\fR\fR\fI = \fR\fI604800\fR\fI \fR
 +.RE
 +
 +afs username map (G)
 +.\" afs username map
 +.PP
 +.RS 4
 +If you are using the fake kaserver AFS feature, you might want to hand\-craft the usernames you are creating tokens for\&. For example this is necessary if you have users from several domain in your AFS Protection Database\&. One possible scheme to code users as DOMAIN+User as it is done by winbind with the + as a separator\&.
 +.sp
 +The mapped user name must contain the cell name to log into, so without setting this parameter there will be no token\&.
 +.sp
 +Default:
 +\fI\fIafs username map\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIafs username map\fR\fR\fI = \fR\fI%u at afs\&.samba\&.org\fR\fI \fR
 +.RE
 +
 +aio read size (S)
 +.\" aio read size
 +.PP
 +.RS 4
 +If Samba has been built with asynchronous I/O support and this integer parameter is set to non\-zero value, Samba will read from file asynchronously when size of request is bigger than this value\&. Note that it happens only for non\-chained and non\-chaining reads and when not using write cache\&.
 +.sp
 +Current implementation of asynchronous I/O in Samba 3\&.0 does support only up to 10 outstanding asynchronous requests, read and write combined\&.
 +.sp
 +Related command:
 +\m[blue]\fBwrite cache size\fR\m[]
 +.sp
 +Related command:
 +\m[blue]\fBaio write size\fR\m[]
 +.sp
 +Default:
 +\fI\fIaio read size\fR\fR\fI = \fR\fI0\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIaio read size\fR\fR\fI = \fR\fI16384 # Use asynchronous I/O for reads bigger than 16KB request size\fR\fI \fR
 +.RE
 +
 +aio write behind (S)
 +.\" aio write behind
 +.PP
 +.RS 4
 +If Samba has been built with asynchronous I/O support, Samba will not wait until write requests are finished before returning the result to the client for files listed in this parameter\&. Instead, Samba will immediately return that the write request has been finished successfully, no matter if the operation will succeed or not\&. This might speed up clients without aio support, but is really dangerous, because data could be lost and files could be damaged\&.
 +.sp
 +The syntax is identical to the
 +\m[blue]\fBveto files\fR\m[]
 +parameter\&.
 +.sp
 +Default:
 +\fI\fIaio write behind\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIaio write behind\fR\fR\fI = \fR\fI/*\&.tmp/\fR\fI \fR
 +.RE
 +
 +aio write size (S)
 +.\" aio write size
 +.PP
 +.RS 4
 +If Samba has been built with asynchronous I/O support and this integer parameter is set to non\-zero value, Samba will write to file asynchronously when size of request is bigger than this value\&. Note that it happens only for non\-chained and non\-chaining reads and when not using write cache\&.
 +.sp
 +Current implementation of asynchronous I/O in Samba 3\&.0 does support only up to 10 outstanding asynchronous requests, read and write combined\&.
 +.sp
 +Related command:
 +\m[blue]\fBwrite cache size\fR\m[]
 +.sp
 +Related command:
 +\m[blue]\fBaio read size\fR\m[]
 +.sp
 +Default:
 +\fI\fIaio write size\fR\fR\fI = \fR\fI0\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIaio write size\fR\fR\fI = \fR\fI16384 # Use asynchronous I/O for writes bigger than 16KB request size\fR\fI \fR
 +.RE
 +
 +algorithmic rid base (G)
 +.\" algorithmic rid base
 +.PP
 +.RS 4
 +This determines how Samba will use its algorithmic mapping from uids/gid to the RIDs needed to construct NT Security Identifiers\&.
 +.sp
 +Setting this option to a larger value could be useful to sites transitioning from WinNT and Win2k, as existing user and group rids would otherwise clash with system users etc\&.
 +.sp
 +All UIDs and GIDs must be able to be resolved into SIDs for the correct operation of ACLs on the server\&. As such the algorithmic mapping can\*(Aqt be \*(Aqturned off\*(Aq, but pushing it \*(Aqout of the way\*(Aq should resolve the issues\&. Users and groups can then be assigned \*(Aqlow\*(Aq RIDs in arbitrary\-rid supporting backends\&.
 +.sp
 +Default:
 +\fI\fIalgorithmic rid base\fR\fR\fI = \fR\fI1000\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIalgorithmic rid base\fR\fR\fI = \fR\fI100000\fR\fI \fR
 +.RE
 +
 +allocation roundup size (S)
 +.\" allocation roundup size
 +.PP
 +.RS 4
 +This parameter allows an administrator to tune the allocation size reported to Windows clients\&. The default size of 1Mb generally results in improved Windows client performance\&. However, rounding the allocation size may cause difficulties for some applications, e\&.g\&. MS Visual Studio\&. If the MS Visual Studio compiler starts to crash with an internal error, set this parameter to zero for this share\&.
 +.sp
 +The integer parameter specifies the roundup size in bytes\&.
 +.sp
 +Default:
 +\fI\fIallocation roundup size\fR\fR\fI = \fR\fI1048576\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIallocation roundup size\fR\fR\fI = \fR\fI0 # (to disable roundups)\fR\fI \fR
 +.RE
 +
 +allow dns updates (G)
 +.\" allow dns updates
 +.PP
 +.RS 4
 +This option determines what kind of updates to the DNS are allowed\&.
 +.sp
 +DNS updates can either be disallowed completely by setting it to
 +\fBdisabled\fR, enabled over secure connections only by setting it to
 +\fBsecure only\fR
 +or allowed in all cases by setting it to
 +\fBnonsecure\fR\&.
 +.sp
 +Default:
 +\fI\fIallow dns updates\fR\fR\fI = \fR\fIsecure only\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIallow dns updates\fR\fR\fI = \fR\fIdisabled\fR\fI \fR
 +.RE
 +
 +allow insecure wide links (G)
 +.\" allow insecure wide links
 +.PP
 +.RS 4
 +In normal operation the option
 +\m[blue]\fBwide links\fR\m[]
 +which allows the server to follow symlinks outside of a share path is automatically disabled when
 +\m[blue]\fBunix extensions\fR\m[]
 +are enabled on a Samba server\&. This is done for security purposes to prevent UNIX clients creating symlinks to areas of the server file system that the administrator does not wish to export\&.
 +.sp
 +Setting
 +\m[blue]\fBallow insecure wide links\fR\m[]
 +to true disables the link between these two parameters, removing this protection and allowing a site to configure the server to follow symlinks (by setting
 +\m[blue]\fBwide links\fR\m[]
 +to "true") even when
 +\m[blue]\fBunix extensions\fR\m[]
 +is turned on\&.
 +.sp
 +If is not recommended to enable this option unless you fully understand the implications of allowing the server to follow symbolic links created by UNIX clients\&. For most normal Samba configurations this would be considered a security hole and setting this parameter is not recommended\&.
 +.sp
 +This option was added at the request of sites who had deliberately set Samba up in this way and needed to continue supporting this functionality without having to patch the Samba code\&.
 +.sp
 +Default:
 +\fI\fIallow insecure wide links\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +allow nt4 crypto (G)
 +.\" allow nt4 crypto
 +.PP
 +.RS 4
 +This option controls whether the netlogon server (currently only in \*(Aqactive directory domain controller\*(Aq mode), will reject clients which does not support NETLOGON_NEG_STRONG_KEYS nor NETLOGON_NEG_SUPPORTS_AES\&.
 +.sp
 +This option was added with Samba 4\&.2\&.0\&. It may lock out clients which worked fine with Samba versions up to 4\&.1\&.x\&. as the effective default was "yes" there, while it is "no" now\&.
 +.sp
 +If you have clients without RequireStrongKey = 1 in the registry, you may need to set "allow nt4 crypto = yes", until you have fixed all clients\&.
 +.sp
 +"allow nt4 crypto = yes" allows weak crypto to be negotiated, maybe via downgrade attacks\&.
 +.sp
 +This option yields precedence to the \*(Aqreject md5 clients\*(Aq option\&.
 +.sp
 +Default:
 +\fI\fIallow nt4 crypto\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +allow trusted domains (G)
 +.\" allow trusted domains
 +.PP
 +.RS 4
 +This option only takes effect when the
 +\m[blue]\fBsecurity\fR\m[]
 +option is set to
 +\fBserver\fR,
 +\fBdomain\fR
 +or
 +\fBads\fR\&. If it is set to no, then attempts to connect to a resource from a domain or workgroup other than the one which smbd is running in will fail, even if that domain is trusted by the remote server doing the authentication\&.
 +.sp
 +This is useful if you only want your Samba server to serve resources to users in the domain it is a member of\&. As an example, suppose that there are two domains DOMA and DOMB\&. DOMB is trusted by DOMA, which contains the Samba server\&. Under normal circumstances, a user with an account in DOMB can then access the resources of a UNIX account with the same account name on the Samba server even if they do not have an account in DOMA\&. This can make implementing a security boundary dif [...]
 +.sp
 +Default:
 +\fI\fIallow trusted domains\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +async smb echo handler (G)
 +.\" async smb echo handler
 +.PP
 +.RS 4
 +This parameter specifies whether Samba should fork the async smb echo handler\&. It can be beneficial if your file system can block syscalls for a very long time\&. In some circumstances, it prolongs the timeout that Windows uses to determine whether a connection is dead\&.
 +.sp
 +Default:
 +\fI\fIasync smb echo handler\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +auth methods (G)
 +.\" auth methods
 +.PP
 +.RS 4
 +This option allows the administrator to chose what authentication methods
 +smbd
 +will use when authenticating a user\&. This option defaults to sensible values based on
 +\m[blue]\fBsecurity\fR\m[]\&. This should be considered a developer option and used only in rare circumstances\&. In the majority (if not all) of production servers, the default setting should be adequate\&.
 +.sp
 +Each entry in the list attempts to authenticate the user in turn, until the user authenticates\&. In practice only one method will ever actually be able to complete the authentication\&.
 +.sp
 +Possible options include
 +\fBguest\fR
 +(anonymous access),
 +\fBsam\fR
 +(lookups in local list of accounts based on netbios name or domain name),
 +\fBwinbind\fR
 +(relay authentication requests for remote users through winbindd),
 +\fBntdomain\fR
 +(pre\-winbindd method of authentication for remote domain users; deprecated in favour of winbind method),
 +\fBtrustdomain\fR
 +(authenticate trusted users by contacting the remote DC directly from smbd; deprecated in favour of winbind method)\&.
 +.sp
 +Default:
 +\fI\fIauth methods\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIauth methods\fR\fR\fI = \fR\fIguest sam winbind\fR\fI \fR
 +.RE
 +
 +available (S)
 +.\" available
 +.PP
 +.RS 4
 +This parameter lets you "turn off" a service\&. If
 +\fIavailable = no\fR, then
 +\fIALL\fR
 +attempts to connect to the service will fail\&. Such failures are logged\&.
 +.sp
 +Default:
 +\fI\fIavailable\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +bind interfaces only (G)
 +.\" bind interfaces only
 +.PP
 +.RS 4
 +This global parameter allows the Samba admin to limit what interfaces on a machine will serve SMB requests\&. It affects file service
 +\fBsmbd\fR(8)
 +and name service
 +\fBnmbd\fR(8)
 +in a slightly different ways\&.
 +.sp
 +For name service it causes
 +nmbd
 +to bind to ports 137 and 138 on the interfaces listed in the
 +\m[blue]\fBinterfaces\fR\m[]
 +parameter\&.
 +nmbd
 +also binds to the "all addresses" interface (0\&.0\&.0\&.0) on ports 137 and 138 for the purposes of reading broadcast messages\&. If this option is not set then
 +nmbd
 +will service name requests on all of these sockets\&. If
 +\m[blue]\fBbind interfaces only\fR\m[]
 +is set then
 +nmbd
 +will check the source address of any packets coming in on the broadcast sockets and discard any that don\*(Aqt match the broadcast addresses of the interfaces in the
 +\m[blue]\fBinterfaces\fR\m[]
 +parameter list\&. As unicast packets are received on the other sockets it allows
 +nmbd
 +to refuse to serve names to machines that send packets that arrive through any interfaces not listed in the
 +\m[blue]\fBinterfaces\fR\m[]
 +list\&. IP Source address spoofing does defeat this simple check, however, so it must not be used seriously as a security feature for
 +nmbd\&.
 +.sp
 +For file service it causes
 +\fBsmbd\fR(8)
 +to bind only to the interface list given in the
 +\m[blue]\fBinterfaces\fR\m[]
 +parameter\&. This restricts the networks that
 +smbd
 +will serve, to packets coming in on those interfaces\&. Note that you should not use this parameter for machines that are serving PPP or other intermittent or non\-broadcast network interfaces as it will not cope with non\-permanent interfaces\&.
 +.sp
 +If
 +\m[blue]\fBbind interfaces only\fR\m[]
 +is set and the network address
 +\fI127\&.0\&.0\&.1\fR
 +is not added to the
 +\m[blue]\fBinterfaces\fR\m[]
 +parameter list
 +\fBsmbpasswd\fR(8)
 +may not work as expected due to the reasons covered below\&.
 +.sp
 +To change a users SMB password, the
 +smbpasswd
 +by default connects to the
 +\fIlocalhost \- 127\&.0\&.0\&.1\fR
 +address as an SMB client to issue the password change request\&. If
 +\m[blue]\fBbind interfaces only\fR\m[]
 +is set then unless the network address
 +\fI127\&.0\&.0\&.1\fR
 +is added to the
 +\m[blue]\fBinterfaces\fR\m[]
 +parameter list then
 +smbpasswd
 +will fail to connect in it\*(Aqs default mode\&.
 +smbpasswd
 +can be forced to use the primary IP interface of the local host by using its
 +\fBsmbpasswd\fR(8)\fI\-r \fR\fI\fIremote machine\fR\fR
 +parameter, with
 +\fIremote machine\fR
 +set to the IP name of the primary interface of the local host\&.
 +.sp
 +Default:
 +\fI\fIbind interfaces only\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +blocking locks (S)
 +.\" blocking locks
 +.PP
 +.RS 4
 +This parameter controls the behavior of
 +\fBsmbd\fR(8)
 +when given a request by a client to obtain a byte range lock on a region of an open file, and the request has a time limit associated with it\&.
 +.sp
 +If this parameter is set and the lock range requested cannot be immediately satisfied, samba will internally queue the lock request, and periodically attempt to obtain the lock until the timeout period expires\&.
 +.sp
 +If this parameter is set to
 +\fBno\fR, then samba will behave as previous versions of Samba would and will fail the lock request immediately if the lock range cannot be obtained\&.
 +.sp
 +Default:
 +\fI\fIblocking locks\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +block size (S)
 +.\" block size
 +.PP
 +.RS 4
 +This parameter controls the behavior of
 +\fBsmbd\fR(8)
 +when reporting disk free sizes\&. By default, this reports a disk block size of 1024 bytes\&.
 +.sp
 +Changing this parameter may have some effect on the efficiency of client writes, this is not yet confirmed\&. This parameter was added to allow advanced administrators to change it (usually to a higher value) and test the effect it has on client write performance without re\-compiling the code\&. As this is an experimental option it may be removed in a future release\&.
 +.sp
 +Changing this option does not change the disk free reporting size, just the block size unit reported to the client\&.
 +.sp
 +Default:
 +\fI\fIblock size\fR\fR\fI = \fR\fI1024\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIblock size\fR\fR\fI = \fR\fI4096\fR\fI \fR
 +.RE
 +
 +browsable
 +.\" browsable
 +.PP
 +.RS 4
 +This parameter is a synonym for
 +browseable\&.
 +.RE
 +
 +browseable (S)
 +.\" browseable
 +.PP
 +.RS 4
 +This controls whether this share is seen in the list of available shares in a net view and in the browse list\&.
 +.sp
 +Default:
 +\fI\fIbrowseable\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +browse list (G)
 +.\" browse list
 +.PP
 +.RS 4
 +This controls whether
 +\fBsmbd\fR(8)
 +will serve a browse list to a client doing a
 +NetServerEnum
 +call\&. Normally set to
 +\fByes\fR\&. You should never need to change this\&.
 +.sp
 +Default:
 +\fI\fIbrowse list\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +cache directory (G)
 +.\" cache directory
 +.PP
 +.RS 4
 +Usually, most of the TDB files are stored in the
 +\fIlock directory\fR\&. Since Samba 3\&.4\&.0, it is possible to differentiate between TDB files with persistent data and TDB files with non\-persistent data using the
 +\fIstate directory\fR
 +and the
 +\fIcache directory\fR
 +options\&.
 +.sp
 +This option specifies the directory where TDB files containing non\-persistent data will be stored\&.
 +.sp
 +Default:
 +\fI\fIcache directory\fR\fR\fI = \fR\fI${prefix}/var/cache\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIcache directory\fR\fR\fI = \fR\fI/var/run/samba/locks/cache\fR\fI \fR
 +.RE
 +
 +casesignames
 +.\" casesignames
 +.PP
 +.RS 4
 +This parameter is a synonym for
 +case sensitive\&.
 +.RE
 +
 +case sensitive (S)
 +.\" case sensitive
 +.PP
 +.RS 4
 +See the discussion in the section
 +\m[blue]\fBname mangling\fR\m[]\&.
 +.sp
 +Default:
 +\fI\fIcase sensitive\fR\fR\fI = \fR\fIauto\fR\fI \fR
 +.RE
 +
 +change notify (G)
 +.\" change notify
 +.PP
 +.RS 4
 +This parameter specifies whether Samba should reply to a client\*(Aqs file change notify requests\&.
 +.sp
 +You should never need to change this parameter
 +.sp
 +Default:
 +\fI\fIchange notify\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +change share command (G)
 +.\" change share command
 +.PP
 +.RS 4
 +Samba 2\&.2\&.0 introduced the ability to dynamically add and delete shares via the Windows NT 4\&.0 Server Manager\&. The
 +\fIchange share command\fR
 +is used to define an external program or script which will modify an existing service definition in
 +smb\&.conf\&.
 +.sp
 +In order to successfully execute the
 +\fIchange share command\fR,
 +smbd
 +requires that the administrator connects using a root account (i\&.e\&. uid == 0) or has the
 +SeDiskOperatorPrivilege\&. Scripts defined in the
 +\fIchange share command\fR
 +parameter are executed as root\&.
 +.sp
 +When executed,
 +smbd
 +will automatically invoke the
 +\fIchange share command\fR
 +with six parameters\&.
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIconfigFile\fR
 +\- the location of the global
 +smb\&.conf
 +file\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIshareName\fR
 +\- the name of the new share\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIpathName\fR
 +\- path to an **existing** directory on disk\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIcomment\fR
 +\- comment string to associate with the new share\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fImax connections\fR
 +Number of maximum simultaneous connections to this share\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fICSC policy\fR
 +\- client side caching policy in string form\&. Valid values are: manual, documents, programs, disable\&.
 +.RE
 +.sp
 +.RE
 +This parameter is only used to modify existing file share definitions\&. To modify printer shares, use the "Printers\&.\&.\&." folder as seen when browsing the Samba host\&.
 +.sp
 +Default:
 +\fI\fIchange share command\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIchange share command\fR\fR\fI = \fR\fI/usr/local/bin/changeshare\fR\fI \fR
 +.RE
 +
 +check password script (G)
 +.\" check password script
 +.PP
 +.RS 4
 +The name of a program that can be used to check password complexity\&. The password is sent to the program\*(Aqs standard input\&.
 +.sp
 +The program must return 0 on a good password, or any other value if the password is bad\&. In case the password is considered weak (the program does not return 0) the user will be notified and the password change will fail\&.
 +.sp
 +Note: In the example directory is a sample program called
 +crackcheck
 +that uses cracklib to check the password quality\&.
 +.sp
 +Default:
 +\fI\fIcheck password script\fR\fR\fI = \fR\fI # Disabled\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIcheck password script\fR\fR\fI = \fR\fI/usr/local/sbin/crackcheck\fR\fI \fR
 +.RE
 +
 +cldap port (G)
 +.\" cldap port
 +.PP
 +.RS 4
 +This option controls the port used by the CLDAP protocol\&.
 +.sp
 +Default:
 +\fI\fIcldap port\fR\fR\fI = \fR\fI389\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIcldap port\fR\fR\fI = \fR\fI3389\fR\fI \fR
 +.RE
 +
 +client lanman auth (G)
 +.\" client lanman auth
 +.PP
 +.RS 4
 +This parameter determines whether or not
 +\fBsmbclient\fR(8)
 +and other samba client tools will attempt to authenticate itself to servers using the weaker LANMAN password hash\&. If disabled, only server which support NT password hashes (e\&.g\&. Windows NT/2000, Samba, etc\&.\&.\&. but not Windows 95/98) will be able to be connected from the Samba client\&.
 +.sp
 +The LANMAN encrypted response is easily broken, due to its case\-insensitive nature, and the choice of algorithm\&. Clients without Windows 95/98 servers are advised to disable this option\&.
 +.sp
 +Disabling this option will also disable the
 +client plaintext auth
 +option\&.
 +.sp
 +Likewise, if the
 +client ntlmv2 auth
 +parameter is enabled, then only NTLMv2 logins will be attempted\&.
 +.sp
 +Default:
 +\fI\fIclient lanman auth\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +client ldap sasl wrapping (G)
 +.\" client ldap sasl wrapping
 +.PP
 +.RS 4
 +The
 +\m[blue]\fBclient ldap sasl wrapping\fR\m[]
 +defines whether ldap traffic will be signed or signed and encrypted (sealed)\&. Possible values are
 +\fIplain\fR,
 +\fIsign\fR
 +and
 +\fIseal\fR\&.
 +.sp
 +The values
 +\fIsign\fR
 +and
 +\fIseal\fR
 +are only available if Samba has been compiled against a modern OpenLDAP version (2\&.3\&.x or higher)\&.
 +.sp
 +This option is needed in the case of Domain Controllers enforcing the usage of signed LDAP connections (e\&.g\&. Windows 2000 SP3 or higher)\&. LDAP sign and seal can be controlled with the registry key "HKLM\eSystem\eCurrentControlSet\eServices\eNTDS\eParameters\eLDAPServerIntegrity" on the Windows server side\&.
 +.sp
 +Depending on the used KRB5 library (MIT and older Heimdal versions) it is possible that the message "integrity only" is not supported\&. In this case,
 +\fIsign\fR
 +is just an alias for
 +\fIseal\fR\&.
 +.sp
 +The default value is
 +\fIsign\fR\&. That implies synchronizing the time with the KDC in the case of using
 +\fIKerberos\fR\&.
 +.sp
 +Default:
 +\fI\fIclient ldap sasl wrapping\fR\fR\fI = \fR\fIsign\fR\fI \fR
 +.RE
 +
 +client max protocol (G)
 +.\" client max protocol
 +.PP
 +.RS 4
 +The value of the parameter (a string) is the highest protocol level that will be supported by the client\&.
 +.sp
 +Possible values are :
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fBCORE\fR: Earliest version\&. No concept of user names\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fBCOREPLUS\fR: Slight improvements on CORE for efficiency\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fBLANMAN1\fR: First
 +\fImodern\fR
 +version of the protocol\&. Long filename support\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fBLANMAN2\fR: Updates to Lanman1 protocol\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fBNT1\fR: Current up to date version of the protocol\&. Used by Windows NT\&. Known as CIFS\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fBSMB2\fR: Re\-implementation of the SMB protocol\&. Used by Windows Vista and later versions of Windows\&. SMB2 has sub protocols available\&.
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fBSMB2_02\fR: The earliest SMB2 version\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fBSMB2_10\fR: Windows 7 SMB2 version\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fBSMB2_22\fR: Early Windows 8 SMB2 version\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fBSMB2_24\fR: Windows 8 beta SMB2 version\&.
 +.RE
 +.sp
 +.RE
 +By default SMB2 selects the SMB2_10 variant\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fBSMB3\fR: The same as SMB2\&. Used by Windows 8\&. SMB3 has sub protocols available\&.
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fBSMB3_00\fR: Windows 8 SMB3 version\&. (mostly the same as SMB2_24)
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fBSMB3_02\fR: Windows 8\&.1 SMB3 version\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fBSMB3_10\fR: early Windows 10 technical preview SMB3 version\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fBSMB3_11\fR: Windows 10 technical preview SMB3 version (maybe final)\&.
 +.RE
 +.sp
 +.RE
 +By default SMB3 selects the SMB3_11 variant\&.
 +.RE
 +.sp
 +.RE
 +Normally this option should not be set as the automatic negotiation phase in the SMB protocol takes care of choosing the appropriate protocol\&.
 +.sp
 +The value
 +\fBdefault\fR
 +refers to the default protocol in each part of the code, currently
 +\fBNT1\fR
 +in the client tools and
 +\fBSMB3_02\fR
 +in winbindd\&.
 +.sp
 +Default:
 +\fI\fIclient max protocol\fR\fR\fI = \fR\fIdefault\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIclient max protocol\fR\fR\fI = \fR\fILANMAN1\fR\fI \fR
 +.RE
 +
 +client min protocol (G)
 +.\" client min protocol
 +.PP
 +.RS 4
 +This setting controls the minimum protocol version that the client will attempt to use\&.
 +.sp
 +Normally this option should not be set as the automatic negotiation phase in the SMB protocol takes care of choosing the appropriate protocol\&.
 +.sp
 +See
 +Related command: \m[blue]\fBclient max protocol\fR\m[]
 +for a full list of available protocols\&.
 +.sp
 +Default:
 +\fI\fIclient min protocol\fR\fR\fI = \fR\fICORE\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIclient min protocol\fR\fR\fI = \fR\fINT1\fR\fI \fR
 +.RE
 +
 +client NTLMv2 auth (G)
 +.\" client NTLMv2 auth
 +.PP
 +.RS 4
 +This parameter determines whether or not
 +\fBsmbclient\fR(8)
 +will attempt to authenticate itself to servers using the NTLMv2 encrypted password response\&.
 +.sp
 +If enabled, only an NTLMv2 and LMv2 response (both much more secure than earlier versions) will be sent\&. Older servers (including NT4 < SP4, Win9x and Samba 2\&.2) are not compatible with NTLMv2 when not in an NTLMv2 supporting domain
 +.sp
 +Similarly, if enabled, NTLMv1,
 +client lanman auth
 +and
 +client plaintext auth
 +authentication will be disabled\&. This also disables share\-level authentication\&.
 +.sp
 +If disabled, an NTLM response (and possibly a LANMAN response) will be sent by the client, depending on the value of
 +client lanman auth\&.
 +.sp
 +Note that Windows Vista and later versions already use NTLMv2 by default, and some sites (particularly those following \*(Aqbest practice\*(Aq security polices) only allow NTLMv2 responses, and not the weaker LM or NTLM\&.
 +.sp
 +Default:
 +\fI\fIclient NTLMv2 auth\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +client plaintext auth (G)
 +.\" client plaintext auth
 +.PP
 +.RS 4
 +Specifies whether a client should send a plaintext password if the server does not support encrypted passwords\&.
 +.sp
 +Default:
 +\fI\fIclient plaintext auth\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +client schannel (G)
 +.\" client schannel
 +.PP
 +.RS 4
 +This controls whether the client offers or even demands the use of the netlogon schannel\&.
 +\m[blue]\fBclient schannel = no\fR\m[]
 +does not offer the schannel,
 +\m[blue]\fBclient schannel = auto\fR\m[]
 +offers the schannel but does not enforce it, and
 +\m[blue]\fBclient schannel = yes\fR\m[]
 +denies access if the server is not able to speak netlogon schannel\&.
 +.sp
 +Note that for active directory domains this is hardcoded to
 +\m[blue]\fBclient schannel = yes\fR\m[]\&.
 +.sp
 +This option yields precedence to the
 +\m[blue]\fBrequire strong key\fR\m[]
 +option\&.
 +.sp
 +Default:
 +\fI\fIclient schannel\fR\fR\fI = \fR\fIauto\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIclient schannel\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +client signing (G)
 +.\" client signing
 +.PP
 +.RS 4
 +This controls whether the client is allowed or required to use SMB signing\&. Possible values are
 +\fIauto\fR,
 +\fImandatory\fR
 +and
 +\fIdisabled\fR\&.
 +.sp
 +When set to auto or default, SMB signing is offered, but not enforced, except in winbindd, where it is enforced to Active Directory Domain Controllers\&.
 +.sp
 +When set to mandatory, SMB signing is required and if set to disabled, SMB signing is not offered either\&.
 +.sp
 +Default:
 +\fI\fIclient signing\fR\fR\fI = \fR\fIdefault\fR\fI \fR
 +.RE
 +
 +client use spnego principal (G)
 +.\" client use spnego principal
 +.PP
 +.RS 4
 +This parameter determines whether or not
 +\fBsmbclient\fR(8)
 +and other samba components acting as a client will attempt to use the server\-supplied principal sometimes given in the SPNEGO exchange\&.
 +.sp
 +If enabled, Samba can attempt to use Kerberos to contact servers known only by IP address\&. Kerberos relies on names, so ordinarily cannot function in this situation\&.
 +.sp
 +This is a VERY BAD IDEA for security reasons, and so this parameter SHOULD NOT BE USED\&. It will be removed in a future version of Samba\&.
 +.sp
 +If disabled, Samba will use the name used to look up the server when asking the KDC for a ticket\&. This avoids situations where a server may impersonate another, soliciting authentication as one principal while being known on the network as another\&.
 +.sp
 +Note that Windows XP SP2 and later versions already follow this behaviour, and Windows Vista and later servers no longer supply this \*(Aqrfc4178 hint\*(Aq principal on the server side\&.
 +.sp
 +This parameter is deprecated in Samba 4\&.2\&.1 and will be removed (along with the functionality) in a later release of Samba\&.
 +.sp
 +Default:
 +\fI\fIclient use spnego principal\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +client use spnego (G)
 +.\" client use spnego
 +.PP
 +.RS 4
 +This variable controls whether Samba clients will try to use Simple and Protected NEGOciation (as specified by rfc2478) with supporting servers (including WindowsXP, Windows2000 and Samba 3\&.0) to agree upon an authentication mechanism\&. This enables Kerberos authentication in particular\&.
 +.sp
 +Default:
 +\fI\fIclient use spnego\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +cluster addresses (G)
 +.\" cluster addresses
 +.PP
 +.RS 4
 +With this parameter you can add additional addresses nmbd will register with a WINS server\&. These addresses are not necessarily present on all nodes simultaneously, but they will be registered with the WINS server so that clients can contact any of the nodes\&.
 +.sp
 +Default:
 +\fI\fIcluster addresses\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIcluster addresses\fR\fR\fI = \fR\fI10\&.0\&.0\&.1 10\&.0\&.0\&.2 10\&.0\&.0\&.3\fR\fI \fR
 +.RE
 +
 +clustering (G)
 +.\" clustering
 +.PP
 +.RS 4
 +This parameter specifies whether Samba should contact ctdb for accessing its tdb files and use ctdb as a backend for its messaging backend\&.
 +.sp
 +Set this parameter to
 +yes
 +only if you have a cluster setup with ctdb running\&.
 +.sp
 +Default:
 +\fI\fIclustering\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +comment (S)
 +.\" comment
 +.PP
 +.RS 4
 +This is a text field that is seen next to a share when a client does a queries the server, either via the network neighborhood or via
 +net view
 +to list what shares are available\&.
 +.sp
 +If you want to set the string that is displayed next to the machine name then see the
 +\m[blue]\fBserver string\fR\m[]
 +parameter\&.
 +.sp
 +Default:
 +\fI\fIcomment\fR\fR\fI = \fR\fI # No comment\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIcomment\fR\fR\fI = \fR\fIFred\*(Aqs Files\fR\fI \fR
 +.RE
 +
 +config backend (G)
 +.\" config backend
 +.PP
 +.RS 4
 +This controls the backend for storing the configuration\&. Possible values are
 +\fIfile\fR
 +(the default) and
 +\fIregistry\fR\&. When
 +\m[blue]\fBconfig backend = registry\fR\m[]
 +is encountered while loading
 +\fIsmb\&.conf\fR, the configuration read so far is dropped and the global options are read from registry instead\&. So this triggers a registry only configuration\&. Share definitions are not read immediately but instead
 +\fIregistry shares\fR
 +is set to
 +\fIyes\fR\&.
 +.sp
 +Note: This option can not be set inside the registry configuration itself\&.
 +.sp
 +Default:
 +\fI\fIconfig backend\fR\fR\fI = \fR\fIfile\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIconfig backend\fR\fR\fI = \fR\fIregistry\fR\fI \fR
 +.RE
 +
 +config file (G)
 +.\" config file
 +.PP
 +.RS 4
 +This allows you to override the config file to use, instead of the default (usually
 +smb\&.conf)\&. There is a chicken and egg problem here as this option is set in the config file!
 +.sp
 +For this reason, if the name of the config file has changed when the parameters are loaded then it will reload them from the new config file\&.
 +.sp
 +This option takes the usual substitutions, which can be very useful\&.
 +.sp
 +If the config file doesn\*(Aqt exist then it won\*(Aqt be loaded (allowing you to special case the config files of just a few clients)\&.
 +.sp
 +\fINo default\fR
 +.sp
 +Example:
 +\fI\fIconfig file\fR\fR\fI = \fR\fI/usr/local/samba/lib/smb\&.conf\&.%m\fR\fI \fR
 +.RE
 +
 +copy (S)
 +.\" copy
 +.PP
 +.RS 4
 +This parameter allows you to "clone" service entries\&. The specified service is simply duplicated under the current service\*(Aqs name\&. Any parameters specified in the current section will override those in the section being copied\&.
 +.sp
 +This feature lets you set up a \*(Aqtemplate\*(Aq service and create similar services easily\&. Note that the service being copied must occur earlier in the configuration file than the service doing the copying\&.
 +.sp
 +Default:
 +\fI\fIcopy\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIcopy\fR\fR\fI = \fR\fIotherservice\fR\fI \fR
 +.RE
 +
 +create krb5 conf (G)
 +.\" create krb5 conf
 +.PP
 +.RS 4
 +Setting this parameter to
 +no
 +prevents winbind from creating custom krb5\&.conf files\&. Winbind normally does this because the krb5 libraries are not AD\-site\-aware and thus would pick any domain controller out of potentially very many\&. Winbind is site\-aware and makes the krb5 libraries use a local DC by creating its own krb5\&.conf files\&.
 +.sp
 +Preventing winbind from doing this might become necessary if you have to add special options into your system\-krb5\&.conf that winbind does not see\&.
 +.sp
 +Default:
 +\fI\fIcreate krb5 conf\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +create mode
 +.\" create mode
 +.PP
 +.RS 4
 +This parameter is a synonym for
 +create mask\&.
 +.RE
 +
 +create mask (S)
 +.\" create mask
 +.PP
 +.RS 4
 +When a file is created, the necessary permissions are calculated according to the mapping from DOS modes to UNIX permissions, and the resulting UNIX mode is then bit\-wise \*(AqAND\*(Aqed with this parameter\&. This parameter may be thought of as a bit\-wise MASK for the UNIX modes of a file\&. Any bit
 +\fInot\fR
 +set here will be removed from the modes set on a file when it is created\&.
 +.sp
 +The default value of this parameter removes the
 +group
 +and
 +other
 +write and execute bits from the UNIX modes\&.
 +.sp
 +Following this Samba will bit\-wise \*(AqOR\*(Aq the UNIX mode created from this parameter with the value of the
 +\m[blue]\fBforce create mode\fR\m[]
 +parameter which is set to 000 by default\&.
 +.sp
 +This parameter does not affect directory masks\&. See the parameter
 +\m[blue]\fBdirectory mask\fR\m[]
 +for details\&.
 +.sp
 +Default:
 +\fI\fIcreate mask\fR\fR\fI = \fR\fI0744\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIcreate mask\fR\fR\fI = \fR\fI0775\fR\fI \fR
 +.RE
 +
 +csc policy (S)
 +.\" csc policy
 +.PP
 +.RS 4
 +This stands for
 +\fIclient\-side caching policy\fR, and specifies how clients capable of offline caching will cache the files in the share\&. The valid values are: manual, documents, programs, disable\&.
 +.sp
 +These values correspond to those used on Windows servers\&.
 +.sp
 +For example, shares containing roaming profiles can have offline caching disabled using
 +\m[blue]\fBcsc policy = disable\fR\m[]\&.
 +.sp
 +Default:
 +\fI\fIcsc policy\fR\fR\fI = \fR\fImanual\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIcsc policy\fR\fR\fI = \fR\fIprograms\fR\fI \fR
 +.RE
 +
 +ctdbd socket (G)
 +.\" ctdbd socket
 +.PP
 +.RS 4
 +If you set
 +clustering=yes, you need to tell Samba where ctdbd listens on its unix domain socket\&. The default path as of ctdb 1\&.0 is /tmp/ctdb\&.socket which you have to explicitly set for Samba in smb\&.conf\&.
 +.sp
 +Default:
 +\fI\fIctdbd socket\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIctdbd socket\fR\fR\fI = \fR\fI/tmp/ctdb\&.socket\fR\fI \fR
 +.RE
 +
 +ctdb locktime warn threshold (G)
 +.\" ctdb locktime warn threshold
 +.PP
 +.RS 4
 +In a cluster environment using Samba and ctdb it is critical that locks on central ctdb\-hosted databases like locking\&.tdb are not held for long\&. With the current Samba architecture it happens that Samba takes a lock and while holding that lock makes file system calls into the shared cluster file system\&. This option makes Samba warn if it detects that it has held locks for the specified number of milliseconds\&. If this happens,
 +\fIsmbd\fR
 +will emit a debug level 0 message into its logs and potentially into syslog\&. The most likely reason for such a log message is that an operation of the cluster file system Samba exports is taking longer than expected\&. The messages are meant as a debugging aid for potential cluster problems\&.
 +.sp
 +The default value of 0 disables this logging\&.
 +.sp
 +Default:
 +\fI\fIctdb locktime warn threshold\fR\fR\fI = \fR\fI0\fR\fI \fR
 +.RE
 +
 +ctdb timeout (G)
 +.\" ctdb timeout
 +.PP
 +.RS 4
 +This parameter specifies a timeout in milliseconds for the connection between Samba and ctdb\&. It is only valid if you have compiled Samba with clustering and if you have set
 +\fIclustering=yes\fR\&.
 +.sp
 +When something in the cluster blocks, it can happen that we wait indefinitely long for ctdb, just adding to the blocking condition\&. In a well\-running cluster this should never happen, but there are too many components in a cluster that might have hickups\&. Choosing the right balance for this value is very tricky, because on a busy cluster long service times to transfer something across the cluster might be valid\&. Setting it too short will degrade the service your cluster presents, [...]
 +.sp
 +Be aware that if you set this parameter, this needs to be in the file smb\&.conf, it is not really helpful to put this into a registry configuration (typical on a cluster), because to access the registry contact to ctdb is required\&.
 +.sp
 +Setting
 +\fIctdb timeout\fR
 +to n makes any process waiting longer than n milliseconds for a reply by the cluster panic\&. Setting it to 0 (the default) makes Samba block forever, which is the highly recommended default\&.
 +.sp
 +Default:
 +\fI\fIctdb timeout\fR\fR\fI = \fR\fI0\fR\fI \fR
 +.RE
 +
 +cups connection timeout (G)
 +.\" cups connection timeout
 +.PP
 +.RS 4
 +This parameter is only applicable if
 +\m[blue]\fBprinting\fR\m[]
 +is set to
 +\fBcups\fR\&.
 +.sp
 +If set, this option specifies the number of seconds that smbd will wait whilst trying to contact to the CUPS server\&. The connection will fail if it takes longer than this number of seconds\&.
 +.sp
 +Default:
 +\fI\fIcups connection timeout\fR\fR\fI = \fR\fI30\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIcups connection timeout\fR\fR\fI = \fR\fI60\fR\fI \fR
 +.RE
 +
 +cups encrypt (G)
 +.\" cups encrypt
 +.PP
 +.RS 4
 +This parameter is only applicable if
 +\m[blue]\fBprinting\fR\m[]
 +is set to
 +\fBcups\fR
 +and if you use CUPS newer than 1\&.0\&.x\&.It is used to define whether or not Samba should use encryption when talking to the CUPS server\&. Possible values are
 +\fIauto\fR,
 +\fIyes\fR
 +and
 +\fIno\fR
 +.sp
 +When set to auto we will try to do a TLS handshake on each CUPS connection setup\&. If that fails, we will fall back to unencrypted operation\&.
 +.sp
 +Default:
 +\fI\fIcups encrypt\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +cups options (S)
 +.\" cups options
 +.PP
 +.RS 4
 +This parameter is only applicable if
 +\m[blue]\fBprinting\fR\m[]
 +is set to
 +\fBcups\fR\&. Its value is a free form string of options passed directly to the cups library\&.
 +.sp
 +You can pass any generic print option known to CUPS (as listed in the CUPS "Software Users\*(Aq Manual")\&. You can also pass any printer specific option (as listed in "lpoptions \-d printername \-l") valid for the target queue\&. Multiple parameters should be space\-delimited name/value pairs according to the PAPI text option ABNF specification\&. Collection values ("name={a=\&.\&.\&. b=\&.\&.\&. c=\&.\&.\&.}") are stored with the curley brackets intact\&.
 +.sp
 +You should set this parameter to
 +\fBraw\fR
 +if your CUPS server
 +error_log
 +file contains messages such as "Unsupported format \*(Aqapplication/octet\-stream\*(Aq" when printing from a Windows client through Samba\&. It is no longer necessary to enable system wide raw printing in
 +/etc/cups/mime\&.{convs,types}\&.
 +.sp
 +Default:
 +\fI\fIcups options\fR\fR\fI = \fR\fI""\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIcups options\fR\fR\fI = \fR\fI"raw media=a4"\fR\fI \fR
 +.RE
 +
 +cups server (G)
 +.\" cups server
 +.PP
 +.RS 4
 +This parameter is only applicable if
 +\m[blue]\fBprinting\fR\m[]
 +is set to
 +\fBcups\fR\&.
 +.sp
 +If set, this option overrides the ServerName option in the CUPS
 +client\&.conf\&. This is necessary if you have virtual samba servers that connect to different CUPS daemons\&.
 +.sp
 +Optionally, a port can be specified by separating the server name and port number with a colon\&. If no port was specified, the default port for IPP (631) will be used\&.
 +.sp
 +Default:
 +\fI\fIcups server\fR\fR\fI = \fR\fI""\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIcups server\fR\fR\fI = \fR\fImycupsserver\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIcups server\fR\fR\fI = \fR\fImycupsserver:1631\fR\fI \fR
 +.RE
 +
 +dcerpc endpoint servers (G)
 +.\" dcerpc endpoint servers
 +.PP
 +.RS 4
 +Specifies which DCE/RPC endpoint servers should be run\&.
 +.sp
 +Default:
 +\fI\fIdcerpc endpoint servers\fR\fR\fI = \fR\fIepmapper, wkssvc, rpcecho, samr, netlogon, lsarpc, spoolss, drsuapi, dssetup, unixinfo, browser, eventlog6, backupkey, dnsserver\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIdcerpc endpoint servers\fR\fR\fI = \fR\fIrpcecho\fR\fI \fR
 +.RE
 +
 +deadtime (G)
 +.\" deadtime
 +.PP
 +.RS 4
 +The value of the parameter (a decimal integer) represents the number of minutes of inactivity before a connection is considered dead, and it is disconnected\&. The deadtime only takes effect if the number of open files is zero\&.
 +.sp
 +This is useful to stop a server\*(Aqs resources being exhausted by a large number of inactive connections\&.
 +.sp
 +Most clients have an auto\-reconnect feature when a connection is broken so in most cases this parameter should be transparent to users\&.
 +.sp
 +Using this parameter with a timeout of a few minutes is recommended for most systems\&.
 +.sp
 +A deadtime of zero indicates that no auto\-disconnection should be performed\&.
 +.sp
 +Default:
 +\fI\fIdeadtime\fR\fR\fI = \fR\fI0\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIdeadtime\fR\fR\fI = \fR\fI15\fR\fI \fR
 +.RE
 +
 +debug class (G)
 +.\" debug class
 +.PP
 +.RS 4
 +With this boolean parameter enabled, the debug class (DBGC_CLASS) will be displayed in the debug header\&.
 +.sp
 +For more information about currently available debug classes, see section about
 +\m[blue]\fBlog level\fR\m[]\&.
 +.sp
 +Default:
 +\fI\fIdebug class\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +debug hires timestamp (G)
 +.\" debug hires timestamp
 +.PP
 +.RS 4
 +Sometimes the timestamps in the log messages are needed with a resolution of higher that seconds, this boolean parameter adds microsecond resolution to the timestamp message header when turned on\&.
 +.sp
 +Note that the parameter
 +\m[blue]\fBdebug timestamp\fR\m[]
 +must be on for this to have an effect\&.
 +.sp
 +Default:
 +\fI\fIdebug hires timestamp\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +debug pid (G)
 +.\" debug pid
 +.PP
 +.RS 4
 +When using only one log file for more then one forked
 +\fBsmbd\fR(8)\-process there may be hard to follow which process outputs which message\&. This boolean parameter is adds the process\-id to the timestamp message headers in the logfile when turned on\&.
 +.sp
 +Note that the parameter
 +\m[blue]\fBdebug timestamp\fR\m[]
 +must be on for this to have an effect\&.
 +.sp
 +Default:
 +\fI\fIdebug pid\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +debug prefix timestamp (G)
 +.\" debug prefix timestamp
 +.PP
 +.RS 4
 +With this option enabled, the timestamp message header is prefixed to the debug message without the filename and function information that is included with the
 +\m[blue]\fBdebug timestamp\fR\m[]
 +parameter\&. This gives timestamps to the messages without adding an additional line\&.
 +.sp
 +Note that this parameter overrides the
 +\m[blue]\fBdebug timestamp\fR\m[]
 +parameter\&.
 +.sp
 +Default:
 +\fI\fIdebug prefix timestamp\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +timestamp logs
 +.\" timestamp logs
 +.PP
 +.RS 4
 +This parameter is a synonym for
 +debug timestamp\&.
 +.RE
 +
 +debug timestamp (G)
 +.\" debug timestamp
 +.PP
 +.RS 4
 +Samba debug log messages are timestamped by default\&. If you are running at a high
 +\m[blue]\fBdebug level\fR\m[]
 +these timestamps can be distracting\&. This boolean parameter allows timestamping to be turned off\&.
 +.sp
 +Default:
 +\fI\fIdebug timestamp\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +debug uid (G)
 +.\" debug uid
 +.PP
 +.RS 4
 +Samba is sometimes run as root and sometime run as the connected user, this boolean parameter inserts the current euid, egid, uid and gid to the timestamp message headers in the log file if turned on\&.
 +.sp
 +Note that the parameter
 +\m[blue]\fBdebug timestamp\fR\m[]
 +must be on for this to have an effect\&.
 +.sp
 +Default:
 +\fI\fIdebug uid\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +dedicated keytab file (G)
 +.\" dedicated keytab file
 +.PP
 +.RS 4
 +Specifies the path to the kerberos keytab file when
 +\m[blue]\fBkerberos method\fR\m[]
 +is set to "dedicated keytab"\&.
 +.sp
 +Default:
 +\fI\fIdedicated keytab file\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIdedicated keytab file\fR\fR\fI = \fR\fI/usr/local/etc/krb5\&.keytab\fR\fI \fR
 +.RE
 +
 +default case (S)
 +.\" default case
 +.PP
 +.RS 4
 +See the section on
 +\m[blue]\fBname mangling\fR\m[]\&. Also note the
 +\m[blue]\fBshort preserve case\fR\m[]
 +parameter\&.
 +.sp
 +Default:
 +\fI\fIdefault case\fR\fR\fI = \fR\fIlower\fR\fI \fR
 +.RE
 +
 +default devmode (S)
 +.\" default devmode
 +.PP
 +.RS 4
 +This parameter is only applicable to
 +\m[blue]\fBprintable\fR\m[]
 +services\&. When smbd is serving Printer Drivers to Windows NT/2k/XP clients, each printer on the Samba server has a Device Mode which defines things such as paper size and orientation and duplex settings\&. The device mode can only correctly be generated by the printer driver itself (which can only be executed on a Win32 platform)\&. Because smbd is unable to execute the driver code to generate the device mode, the default behavior is to set this field to NULL\&.
 +.sp
 +Most problems with serving printer drivers to Windows NT/2k/XP clients can be traced to a problem with the generated device mode\&. Certain drivers will do things such as crashing the client\*(Aqs Explorer\&.exe with a NULL devmode\&. However, other printer drivers can cause the client\*(Aqs spooler service (spoolsv\&.exe) to die if the devmode was not created by the driver itself (i\&.e\&. smbd generates a default devmode)\&.
 +.sp
 +This parameter should be used with care and tested with the printer driver in question\&. It is better to leave the device mode to NULL and let the Windows client set the correct values\&. Because drivers do not do this all the time, setting
 +default devmode = yes
 +will instruct smbd to generate a default one\&.
 +.sp
 +For more information on Windows NT/2k printing and Device Modes, see the
 +MSDN documentation\&.
 +.sp
 +Default:
 +\fI\fIdefault devmode\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +default
 +.\" default
 +.PP
 +.RS 4
 +This parameter is a synonym for
 +default service\&.
 +.RE
 +
 +default service (G)
 +.\" default service
 +.PP
 +.RS 4
 +This parameter specifies the name of a service which will be connected to if the service actually requested cannot be found\&. Note that the square brackets are
 +\fINOT\fR
 +given in the parameter value (see example below)\&.
 +.sp
 +There is no default value for this parameter\&. If this parameter is not given, attempting to connect to a nonexistent service results in an error\&.
 +.sp
 +Typically the default service would be a
 +\m[blue]\fBguest ok\fR\m[],
 +\m[blue]\fBread\-only\fR\m[]
 +service\&.
 +.sp
 +Also note that the apparent service name will be changed to equal that of the requested service, this is very useful as it allows you to use macros like
 +\fI%S\fR
 +to make a wildcard service\&.
 +.sp
 +Note also that any "_" characters in the name of the service used in the default service will get mapped to a "/"\&. This allows for interesting things\&.
 +.sp
 +Default:
 +\fI\fIdefault service\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIdefault service\fR\fR\fI = \fR\fIpub\fR\fI \fR
 +.RE
 +
 +defer sharing violations (G)
 +.\" defer sharing violations
 +.PP
 +.RS 4
 +Windows allows specifying how a file will be shared with other processes when it is opened\&. Sharing violations occur when a file is opened by a different process using options that violate the share settings specified by other processes\&. This parameter causes smbd to act as a Windows server does, and defer returning a "sharing violation" error message for up to one second, allowing the client to close the file causing the violation in the meantime\&.
 +.sp
 +UNIX by default does not have this behaviour\&.
 +.sp
 +There should be no reason to turn off this parameter, as it is designed to enable Samba to more correctly emulate Windows\&.
 +.sp
 +Default:
 +\fI\fIdefer sharing violations\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +delete group script (G)
 +.\" delete group script
 +.PP
 +.RS 4
 +This is the full pathname to a script that will be run
 +\fIAS ROOT\fR\fBsmbd\fR(8)
 +when a group is requested to be deleted\&. It will expand any
 +\fI%g\fR
 +to the group name passed\&. This script is only useful for installations using the Windows NT domain administration tools\&.
 +.sp
 +Default:
 +\fI\fIdelete group script\fR\fR\fI = \fR\fI\fR\fI \fR
 +.RE
 +
 +deleteprinter command (G)
 +.\" deleteprinter command
 +.PP
 +.RS 4
 +With the introduction of MS\-RPC based printer support for Windows NT/2000 clients in Samba 2\&.2, it is now possible to delete a printer at run time by issuing the DeletePrinter() RPC call\&.
 +.sp
 +For a Samba host this means that the printer must be physically deleted from the underlying printing system\&. The
 +\m[blue]\fBdeleteprinter command\fR\m[]
 +defines a script to be run which will perform the necessary operations for removing the printer from the print system and from
 +smb\&.conf\&.
 +.sp
 +The
 +\m[blue]\fBdeleteprinter command\fR\m[]
 +is automatically called with only one parameter:
 +\m[blue]\fBprinter name\fR\m[]\&.
 +.sp
 +Once the
 +\m[blue]\fBdeleteprinter command\fR\m[]
 +has been executed,
 +smbd
 +will reparse the
 +smb\&.conf
 +to check that the associated printer no longer exists\&. If the sharename is still valid, then
 +smbd
 +will return an ACCESS_DENIED error to the client\&.
 +.sp
 +Default:
 +\fI\fIdeleteprinter command\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIdeleteprinter command\fR\fR\fI = \fR\fI/usr/bin/removeprinter\fR\fI \fR
 +.RE
 +
 +delete readonly (S)
 +.\" delete readonly
 +.PP
 +.RS 4
 +This parameter allows readonly files to be deleted\&. This is not normal DOS semantics, but is allowed by UNIX\&.
 +.sp
 +This option may be useful for running applications such as rcs, where UNIX file ownership prevents changing file permissions, and DOS semantics prevent deletion of a read only file\&.
 +.sp
 +Default:
 +\fI\fIdelete readonly\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +delete share command (G)
 +.\" delete share command
 +.PP
 +.RS 4
 +Samba 2\&.2\&.0 introduced the ability to dynamically add and delete shares via the Windows NT 4\&.0 Server Manager\&. The
 +\fIdelete share command\fR
 +is used to define an external program or script which will remove an existing service definition from
 +smb\&.conf\&.
 +.sp
 +In order to successfully execute the
 +\fIdelete share command\fR,
 +smbd
 +requires that the administrator connects using a root account (i\&.e\&. uid == 0) or has the
 +SeDiskOperatorPrivilege\&. Scripts defined in the
 +\fIdelete share command\fR
 +parameter are executed as root\&.
 +.sp
 +When executed,
 +smbd
 +will automatically invoke the
 +\fIdelete share command\fR
 +with two parameters\&.
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIconfigFile\fR
 +\- the location of the global
 +smb\&.conf
 +file\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIshareName\fR
 +\- the name of the existing service\&.
 +.RE
 +.sp
 +.RE
 +This parameter is only used to remove file shares\&. To delete printer shares, see the
 +\m[blue]\fBdeleteprinter command\fR\m[]\&.
 +.sp
 +Default:
 +\fI\fIdelete share command\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIdelete share command\fR\fR\fI = \fR\fI/usr/local/bin/delshare\fR\fI \fR
 +.RE
 +
 +delete user from group script (G)
 +.\" delete user from group script
 +.PP
 +.RS 4
 +Full path to the script that will be called when a user is removed from a group using the Windows NT domain administration tools\&. It will be run by
 +\fBsmbd\fR(8)\fIAS ROOT\fR\&. Any
 +\fI%g\fR
 +will be replaced with the group name and any
 +\fI%u\fR
 +will be replaced with the user name\&.
 +.sp
 +Default:
 +\fI\fIdelete user from group script\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIdelete user from group script\fR\fR\fI = \fR\fI/usr/sbin/deluser %u %g\fR\fI \fR
 +.RE
 +
 +delete user script (G)
 +.\" delete user script
 +.PP
 +.RS 4
 +This is the full pathname to a script that will be run by
 +\fBsmbd\fR(8)
 +when managing users with remote RPC (NT) tools\&.
 +.sp
 +This script is called when a remote client removes a user from the server, normally using \*(AqUser Manager for Domains\*(Aq or
 +rpcclient\&.
 +.sp
 +This script should delete the given UNIX username\&.
 +.sp
 +Default:
 +\fI\fIdelete user script\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIdelete user script\fR\fR\fI = \fR\fI/usr/local/samba/bin/del_user %u\fR\fI \fR
 +.RE
 +
 +delete veto files (S)
 +.\" delete veto files
 +.PP
 +.RS 4
 +This option is used when Samba is attempting to delete a directory that contains one or more vetoed directories (see the
 +\m[blue]\fBveto files\fR\m[]
 +option)\&. If this option is set to
 +\fBno\fR
 +(the default) then if a vetoed directory contains any non\-vetoed files or directories then the directory delete will fail\&. This is usually what you want\&.
 +.sp
 +If this option is set to
 +\fByes\fR, then Samba will attempt to recursively delete any files and directories within the vetoed directory\&. This can be useful for integration with file serving systems such as NetAtalk which create meta\-files within directories you might normally veto DOS/Windows users from seeing (e\&.g\&.
 +\&.AppleDouble)
 +.sp
 +Setting
 +\m[blue]\fBdelete veto files = yes\fR\m[]
 +allows these directories to be transparently deleted when the parent directory is deleted (so long as the user has permissions to do so)\&.
 +.sp
 +Default:
 +\fI\fIdelete veto files\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +dfree cache time (S)
 +.\" dfree cache time
 +.PP
 +.RS 4
 +The
 +\fIdfree cache time\fR
 +should only be used on systems where a problem occurs with the internal disk space calculations\&. This has been known to happen with Ultrix, but may occur with other operating systems\&. The symptom that was seen was an error of "Abort Retry Ignore" at the end of each directory listing\&.
 +.sp
 +This is a new parameter introduced in Samba version 3\&.0\&.21\&. It specifies in seconds the time that smbd will cache the output of a disk free query\&. If set to zero (the default) no caching is done\&. This allows a heavily loaded server to prevent rapid spawning of
 +\m[blue]\fBdfree command\fR\m[]
 +scripts increasing the load\&.
 +.sp
 +By default this parameter is zero, meaning no caching will be done\&.
 +.sp
 +\fINo default\fR
 +.sp
 +Example:
 +\fI\fIdfree cache time\fR\fR\fI = \fR\fI60\fR\fI \fR
 +.RE
 +
 +dfree command (S)
 +.\" dfree command
 +.PP
 +.RS 4
 +The
 +\fIdfree command\fR
 +setting should only be used on systems where a problem occurs with the internal disk space calculations\&. This has been known to happen with Ultrix, but may occur with other operating systems\&. The symptom that was seen was an error of "Abort Retry Ignore" at the end of each directory listing\&.
 +.sp
 +This setting allows the replacement of the internal routines to calculate the total disk space and amount available with an external routine\&. The example below gives a possible script that might fulfill this function\&.
 +.sp
 +In Samba version 3\&.0\&.21 this parameter has been changed to be a per\-share parameter, and in addition the parameter
 +\m[blue]\fBdfree cache time\fR\m[]
 +was added to allow the output of this script to be cached for systems under heavy load\&.
 +.sp
 +The external program will be passed a single parameter indicating a directory in the filesystem being queried\&. This will typically consist of the string
 +\&./\&. The script should return two integers in ASCII\&. The first should be the total disk space in blocks, and the second should be the number of available blocks\&. An optional third return value can give the block size in bytes\&. The default blocksize is 1024 bytes\&.
 +.sp
 +Note: Your script should
 +\fINOT\fR
 +be setuid or setgid and should be owned by (and writeable only by) root!
 +.sp
 +Where the script dfree (which must be made executable) could be:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 + 
 +#!/bin/sh
 +df $1 | tail \-1 | awk \*(Aq{print $(NF\-4),$(NF\-2)}\*(Aq
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.sp
 +or perhaps (on Sys V based systems):
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 + 
 +#!/bin/sh
 +/usr/bin/df \-k $1 | tail \-1 | awk \*(Aq{print $3" "$5}\*(Aq
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.sp
 +Note that you may have to replace the command names with full path names on some systems\&.
 +.sp
 +By default internal routines for determining the disk capacity and remaining space will be used\&.
 +.sp
 +\fINo default\fR
 +.sp
 +Example:
 +\fI\fIdfree command\fR\fR\fI = \fR\fI/usr/local/samba/bin/dfree\fR\fI \fR
 +.RE
 +
 +dgram port (G)
 +.\" dgram port
 +.PP
 +.RS 4
 +Specifies which ports the server should listen on for NetBIOS datagram traffic\&.
 +.sp
 +Default:
 +\fI\fIdgram port\fR\fR\fI = \fR\fI138\fR\fI \fR
 +.RE
 +
 +directory mode
 +.\" directory mode
 +.PP
 +.RS 4
 +This parameter is a synonym for
 +directory mask\&.
 +.RE
 +
 +directory mask (S)
 +.\" directory mask
 +.PP
 +.RS 4
 +This parameter is the octal modes which are used when converting DOS modes to UNIX modes when creating UNIX directories\&.
 +.sp
 +When a directory is created, the necessary permissions are calculated according to the mapping from DOS modes to UNIX permissions, and the resulting UNIX mode is then bit\-wise \*(AqAND\*(Aqed with this parameter\&. This parameter may be thought of as a bit\-wise MASK for the UNIX modes of a directory\&. Any bit
 +\fInot\fR
 +set here will be removed from the modes set on a directory when it is created\&.
 +.sp
 +The default value of this parameter removes the \*(Aqgroup\*(Aq and \*(Aqother\*(Aq write bits from the UNIX mode, allowing only the user who owns the directory to modify it\&.
 +.sp
 +Following this Samba will bit\-wise \*(AqOR\*(Aq the UNIX mode created from this parameter with the value of the
 +\m[blue]\fBforce directory mode\fR\m[]
 +parameter\&. This parameter is set to 000 by default (i\&.e\&. no extra mode bits are added)\&.
 +.sp
 +Default:
 +\fI\fIdirectory mask\fR\fR\fI = \fR\fI0755\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIdirectory mask\fR\fR\fI = \fR\fI0775\fR\fI \fR
 +.RE
 +
 +directory name cache size (S)
 +.\" directory name cache size
 +.PP
 +.RS 4
 +This parameter specifies the size of the directory name cache\&. It will be needed to turn this off for *BSD systems\&.
 +.sp
 +Default:
 +\fI\fIdirectory name cache size\fR\fR\fI = \fR\fI100\fR\fI \fR
 +.RE
 +
 +directory security mask (S)
 +.\" directory security mask
 +.PP
 +.RS 4
 +This parameter has been removed for Samba 4\&.0\&.0\&.
 +.sp
 +\fINo default\fR
 +.RE
 +
 +disable netbios (G)
 +.\" disable netbios
 +.PP
 +.RS 4
 +Enabling this parameter will disable netbios support in Samba\&. Netbios is the only available form of browsing in all windows versions except for 2000 and XP\&.
 +.if n \{\
 +.sp
 +.\}
 +.RS 4
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBNote\fR
 +.ps -1
 +.br
 +Clients that only support netbios won\*(Aqt be able to see your samba server when netbios support is disabled\&.
 +.sp .5v
 +.RE
 +Default:
 +\fI\fIdisable netbios\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +disable spoolss (G)
 +.\" disable spoolss
 +.PP
 +.RS 4
 +Enabling this parameter will disable Samba\*(Aqs support for the SPOOLSS set of MS\-RPC\*(Aqs and will yield identical behavior as Samba 2\&.0\&.x\&. Windows NT/2000 clients will downgrade to using Lanman style printing commands\&. Windows 9x/ME will be unaffected by the parameter\&. However, this will also disable the ability to upload printer drivers to a Samba server via the Windows NT Add Printer Wizard or by using the NT printer properties dialog window\&. It will also disable the  [...]
 +\fIBe very careful about enabling this parameter\&.\fR
 +.sp
 +Default:
 +\fI\fIdisable spoolss\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +dmapi support (S)
 +.\" dmapi support
 +.PP
 +.RS 4
 +This parameter specifies whether Samba should use DMAPI to determine whether a file is offline or not\&. This would typically be used in conjunction with a hierarchical storage system that automatically migrates files to tape\&.
 +.sp
 +Note that Samba infers the status of a file by examining the events that a DMAPI application has registered interest in\&. This heuristic is satisfactory for a number of hierarchical storage systems, but there may be system for which it will fail\&. In this case, Samba may erroneously report files to be offline\&.
 +.sp
 +This parameter is only available if a supported DMAPI implementation was found at compilation time\&. It will only be used if DMAPI is found to enabled on the system at run time\&.
 +.sp
 +Default:
 +\fI\fIdmapi support\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +dns forwarder (G)
 +.\" dns forwarder
 +.PP
 +.RS 4
 +This option specifies the DNS server that DNS requests will be forwarded to if they can not be handled by Samba itself\&.
 +.sp
 +The DNS forwarder is only used if the internal DNS server in Samba is used\&.
 +.sp
 +Default:
 +\fI\fIdns forwarder\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIdns forwarder\fR\fR\fI = \fR\fI192\&.168\&.0\&.1\fR\fI \fR
 +.RE
 +
 +dns proxy (G)
 +.\" dns proxy
 +.PP
 +.RS 4
 +Specifies that
 +\fBnmbd\fR(8)
 +when acting as a WINS server and finding that a NetBIOS name has not been registered, should treat the NetBIOS name word\-for\-word as a DNS name and do a lookup with the DNS server for that name on behalf of the name\-querying client\&.
 +.sp
 +Note that the maximum length for a NetBIOS name is 15 characters, so the DNS name (or DNS alias) can likewise only be 15 characters, maximum\&.
 +.sp
 +nmbd
 +spawns a second copy of itself to do the DNS name lookup requests, as doing a name lookup is a blocking action\&.
 +.sp
 +Default:
 +\fI\fIdns proxy\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +dns update command (G)
 +.\" dns update command
 +.PP
 +.RS 4
 +This option sets the command that is called when there are DNS updates\&. It should update the local machines DNS names using TSIG\-GSS\&.
 +.sp
 +Default:
 +\fI\fIdns update command\fR\fR\fI = \fR\fI${prefix}/sbin/samba_dnsupdate\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIdns update command\fR\fR\fI = \fR\fI/usr/local/sbin/dnsupdate\fR\fI \fR
 +.RE
 +
 +domain logons (G)
 +.\" domain logons
 +.PP
 +.RS 4
 +If set to
 +\fByes\fR, the Samba server will provide the netlogon service for Windows 9X network logons for the
 +\m[blue]\fBworkgroup\fR\m[]
 +it is in\&. This will also cause the Samba server to act as a domain controller for NT4 style domain services\&. For more details on setting up this feature see the Domain Control chapter of the Samba HOWTO Collection\&.
 +.sp
 +Default:
 +\fI\fIdomain logons\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +domain master (G)
 +.\" domain master
 +.PP
 +.RS 4
 +Tell
 +\fBsmbd\fR(8)
 +to enable WAN\-wide browse list collation\&. Setting this option causes
 +nmbd
 +to claim a special domain specific NetBIOS name that identifies it as a domain master browser for its given
 +\m[blue]\fBworkgroup\fR\m[]\&. Local master browsers in the same
 +\m[blue]\fBworkgroup\fR\m[]
 +on broadcast\-isolated subnets will give this
 +nmbd
 +their local browse lists, and then ask
 +\fBsmbd\fR(8)
 +for a complete copy of the browse list for the whole wide area network\&. Browser clients will then contact their local master browser, and will receive the domain\-wide browse list, instead of just the list for their broadcast\-isolated subnet\&.
 +.sp
 +Note that Windows NT Primary Domain Controllers expect to be able to claim this
 +\m[blue]\fBworkgroup\fR\m[]
 +specific special NetBIOS name that identifies them as domain master browsers for that
 +\m[blue]\fBworkgroup\fR\m[]
 +by default (i\&.e\&. there is no way to prevent a Windows NT PDC from attempting to do this)\&. This means that if this parameter is set and
 +nmbd
 +claims the special name for a
 +\m[blue]\fBworkgroup\fR\m[]
 +before a Windows NT PDC is able to do so then cross subnet browsing will behave strangely and may fail\&.
 +.sp
 +If
 +\m[blue]\fBdomain logons = yes\fR\m[], then the default behavior is to enable the
 +\m[blue]\fBdomain master\fR\m[]
 +parameter\&. If
 +\m[blue]\fBdomain logons\fR\m[]
 +is not enabled (the default setting), then neither will
 +\m[blue]\fBdomain master\fR\m[]
 +be enabled by default\&.
 +.sp
 +When
 +\m[blue]\fBdomain logons = Yes\fR\m[]
 +the default setting for this parameter is Yes, with the result that Samba will be a PDC\&. If
 +\m[blue]\fBdomain master = No\fR\m[], Samba will function as a BDC\&. In general, this parameter should be set to \*(AqNo\*(Aq only on a BDC\&.
 +.sp
 +Default:
 +\fI\fIdomain master\fR\fR\fI = \fR\fIauto\fR\fI \fR
 +.RE
 +
 +dont descend (S)
 +.\" dont descend
 +.PP
 +.RS 4
 +There are certain directories on some systems (e\&.g\&., the
 +/proc
 +tree under Linux) that are either not of interest to clients or are infinitely deep (recursive)\&. This parameter allows you to specify a comma\-delimited list of directories that the server should always show as empty\&.
 +.sp
 +Note that Samba can be very fussy about the exact format of the "dont descend" entries\&. For example you may need
 +\&./proc
 +instead of just
 +/proc\&. Experimentation is the best policy :\-)
 +.sp
 +Default:
 +\fI\fIdont descend\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIdont descend\fR\fR\fI = \fR\fI/proc,/dev\fR\fI \fR
 +.RE
 +
 +dos charset (G)
 +.\" dos charset
 +.PP
 +.RS 4
 +DOS SMB clients assume the server has the same charset as they do\&. This option specifies which charset Samba should talk to DOS clients\&.
 +.sp
 +The default depends on which charsets you have installed\&. Samba tries to use charset 850 but falls back to ASCII in case it is not available\&. Run
 +\fBtestparm\fR(1)
 +to check the default on your system\&.
 +.sp
 +\fINo default\fR
 +.RE
 +
 +dos filemode (S)
 +.\" dos filemode
 +.PP
 +.RS 4
 +The default behavior in Samba is to provide UNIX\-like behavior where only the owner of a file/directory is able to change the permissions on it\&. However, this behavior is often confusing to DOS/Windows users\&. Enabling this parameter allows a user who has write access to the file (by whatever means, including an ACL permission) to modify the permissions (including ACL) on it\&. Note that a user belonging to the group owning the file will not be allowed to change permissions if the g [...]
 +.sp
 +Default:
 +\fI\fIdos filemode\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +dos filetime resolution (S)
 +.\" dos filetime resolution
 +.PP
 +.RS 4
 +Under the DOS and Windows FAT filesystem, the finest granularity on time resolution is two seconds\&. Setting this parameter for a share causes Samba to round the reported time down to the nearest two second boundary when a query call that requires one second resolution is made to
 +\fBsmbd\fR(8)\&.
 +.sp
 +This option is mainly used as a compatibility option for Visual C++ when used against Samba shares\&. If oplocks are enabled on a share, Visual C++ uses two different time reading calls to check if a file has changed since it was last read\&. One of these calls uses a one\-second granularity, the other uses a two second granularity\&. As the two second call rounds any odd second down, then if the file has a timestamp of an odd number of seconds then the two timestamps will not match and [...]
 +.sp
 +Default:
 +\fI\fIdos filetime resolution\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +dos filetimes (S)
 +.\" dos filetimes
 +.PP
 +.RS 4
 +Under DOS and Windows, if a user can write to a file they can change the timestamp on it\&. Under POSIX semantics, only the owner of the file or root may change the timestamp\&. By default, Samba emulates the DOS semantics and allows to change the timestamp on a file if the user
 +smbd
 +is acting on behalf has write permissions\&. Due to changes in Microsoft Office 2000 and beyond, the default for this parameter has been changed from "no" to "yes" in Samba 3\&.0\&.14 and above\&. Microsoft Excel will display dialog box warnings about the file being changed by another user if this parameter is not set to "yes" and files are being shared between users\&.
 +.sp
 +Default:
 +\fI\fIdos filetimes\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +durable handles (S)
 +.\" durable handles
 +.PP
 +.RS 4
 +This boolean parameter controls whether Samba can grant SMB2 durable file handles on a share\&.
 +.sp
 +Note that durable handles are only enabled if
 +\m[blue]\fBkernel oplocks = no\fR\m[],
 +\m[blue]\fBkernel share modes = no\fR\m[], and
 +\m[blue]\fBposix locking = no\fR\m[], i\&.e\&. if the share is configured for CIFS/SMB2 only access, not supporting interoperability features with local UNIX processes or NFS operations\&.
 +.sp
 +Also note that, for the time being, durability is not granted for a handle that has the delete on close flag set\&.
 +.sp
 +Default:
 +\fI\fIdurable handles\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +ea support (S)
 +.\" ea support
 +.PP
 +.RS 4
 +This boolean parameter controls whether
 +\fBsmbd\fR(8)
 +will allow clients to attempt to store OS/2 style Extended attributes on a share\&. In order to enable this parameter the underlying filesystem exported by the share must support extended attributes (such as provided on XFS and EXT3 on Linux, with the correct kernel patches)\&. On Linux the filesystem must have been mounted with the mount option user_xattr in order for extended attributes to work, also extended attributes must be compiled into the Linux kernel\&.
 +.sp
 +Default:
 +\fI\fIea support\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +enable asu support (G)
 +.\" enable asu support
 +.PP
 +.RS 4
 +Hosts running the "Advanced Server for Unix (ASU)" product require some special accomodations such as creating a builtin [ADMIN$] share that only supports IPC connections\&. The has been the default behavior in smbd for many years\&. However, certain Microsoft applications such as the Print Migrator tool require that the remote server support an [ADMIN$] file share\&. Disabling this parameter allows for creating an [ADMIN$] file share in smb\&.conf\&.
 +.sp
 +Default:
 +\fI\fIenable asu support\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +enable core files (G)
 +.\" enable core files
 +.PP
 +.RS 4
 +This parameter specifies whether core dumps should be written on internal exits\&. Normally set to
 +\fByes\fR\&. You should never need to change this\&.
 +.sp
 +Default:
 +\fI\fIenable core files\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIenable core files\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +enable privileges (G)
 +.\" enable privileges
 +.PP
 +.RS 4
 +This deprecated parameter controls whether or not smbd will honor privileges assigned to specific SIDs via either
 +net rpc rights
 +or one of the Windows user and group manager tools\&. This parameter is enabled by default\&. It can be disabled to prevent members of the Domain Admins group from being able to assign privileges to users or groups which can then result in certain smbd operations running as root that would normally run under the context of the connected user\&.
 +.sp
 +An example of how privileges can be used is to assign the right to join clients to a Samba controlled domain without providing root access to the server via smbd\&.
 +.sp
 +Please read the extended description provided in the Samba HOWTO documentation\&.
 +.sp
 +Default:
 +\fI\fIenable privileges\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +enable spoolss (G)
 +.\" enable spoolss
 +.PP
 +.RS 4
 +Inverted synonym for
 +\m[blue]\fBdisable spoolss\fR\m[]\&.
 +.sp
 +Default:
 +\fI\fIenable spoolss\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +encrypt passwords (G)
 +.\" encrypt passwords
 +.PP
 +.RS 4
 +This boolean controls whether encrypted passwords will be negotiated with the client\&. Note that Windows NT 4\&.0 SP3 and above and also Windows 98 will by default expect encrypted passwords unless a registry entry is changed\&. To use encrypted passwords in Samba see the chapter "User Database" in the Samba HOWTO Collection\&.
 +.sp
 +MS Windows clients that expect Microsoft encrypted passwords and that do not have plain text password support enabled will be able to connect only to a Samba server that has encrypted password support enabled and for which the user accounts have a valid encrypted password\&. Refer to the smbpasswd command man page for information regarding the creation of encrypted passwords for user accounts\&.
 +.sp
 +The use of plain text passwords is NOT advised as support for this feature is no longer maintained in Microsoft Windows products\&. If you want to use plain text passwords you must set this parameter to no\&.
 +.sp
 +In order for encrypted passwords to work correctly
 +\fBsmbd\fR(8)
 +must either have access to a local
 +\fBsmbpasswd\fR(5)
 +file (see the
 +\fBsmbpasswd\fR(8)
 +program for information on how to set up and maintain this file), or set the
 +\m[blue]\fBsecurity = [domain|ads]\fR\m[]
 +parameter which causes
 +smbd
 +to authenticate against another server\&.
 +.sp
 +Default:
 +\fI\fIencrypt passwords\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +enhanced browsing (G)
 +.\" enhanced browsing
 +.PP
 +.RS 4
 +This option enables a couple of enhancements to cross\-subnet browse propagation that have been added in Samba but which are not standard in Microsoft implementations\&.
 +.sp
 +The first enhancement to browse propagation consists of a regular wildcard query to a Samba WINS server for all Domain Master Browsers, followed by a browse synchronization with each of the returned DMBs\&. The second enhancement consists of a regular randomised browse synchronization with all currently known DMBs\&.
 +.sp
 +You may wish to disable this option if you have a problem with empty workgroups not disappearing from browse lists\&. Due to the restrictions of the browse protocols, these enhancements can cause a empty workgroup to stay around forever which can be annoying\&.
 +.sp
 +In general you should leave this option enabled as it makes cross\-subnet browse propagation much more reliable\&.
 +.sp
 +Default:
 +\fI\fIenhanced browsing\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +enumports command (G)
 +.\" enumports command
 +.PP
 +.RS 4
 +The concept of a "port" is fairly foreign to UNIX hosts\&. Under Windows NT/2000 print servers, a port is associated with a port monitor and generally takes the form of a local port (i\&.e\&. LPT1:, COM1:, FILE:) or a remote port (i\&.e\&. LPD Port Monitor, etc\&.\&.\&.)\&. By default, Samba has only one port defined\-\-\fB"Samba Printer Port"\fR\&. Under Windows NT/2000, all printers must have a valid port name\&. If you wish to have a list of ports displayed (smbd
 +does not use a port name for anything) other than the default
 +\fB"Samba Printer Port"\fR, you can define
 +\fIenumports command\fR
 +to point to a program which should generate a list of ports, one per line, to standard output\&. This listing will then be used in response to the level 1 and 2 EnumPorts() RPC\&.
 +.sp
 +Default:
 +\fI\fIenumports command\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIenumports command\fR\fR\fI = \fR\fI/usr/bin/listports\fR\fI \fR
 +.RE
 +
 +eventlog list (G)
 +.\" eventlog list
 +.PP
 +.RS 4
 +This option defines a list of log names that Samba will report to the Microsoft EventViewer utility\&. The listed eventlogs will be associated with tdb file on disk in the
 +$(statedir)/eventlog\&.
 +.sp
 +The administrator must use an external process to parse the normal Unix logs such as
 +/var/log/messages
 +and write then entries to the eventlog tdb files\&. Refer to the eventlogadm(8) utility for how to write eventlog entries\&.
 +.sp
 +Default:
 +\fI\fIeventlog list\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIeventlog list\fR\fR\fI = \fR\fISecurity Application Syslog Apache\fR\fI \fR
 +.RE
 +
 +fake directory create times (S)
 +.\" fake directory create times
 +.PP
 +.RS 4
 +NTFS and Windows VFAT file systems keep a create time for all files and directories\&. This is not the same as the ctime \- status change time \- that Unix keeps, so Samba by default reports the earliest of the various times Unix does keep\&. Setting this parameter for a share causes Samba to always report midnight 1\-1\-1980 as the create time for directories\&.
 +.sp
 +This option is mainly used as a compatibility option for Visual C++ when used against Samba shares\&. Visual C++ generated makefiles have the object directory as a dependency for each object file, and a make rule to create the directory\&. Also, when NMAKE compares timestamps it uses the creation time when examining a directory\&. Thus the object directory will be created if it does not exist, but once it does exist it will always have an earlier timestamp than the object files it contains\&.
 +.sp
 +However, Unix time semantics mean that the create time reported by Samba will be updated whenever a file is created or deleted in the directory\&. NMAKE finds all object files in the object directory\&. The timestamp of the last one built is then compared to the timestamp of the object directory\&. If the directory\*(Aqs timestamp if newer, then all object files will be rebuilt\&. Enabling this option ensures directories always predate their contents and an NMAKE build will proceed as e [...]
 +.sp
 +Default:
 +\fI\fIfake directory create times\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +fake oplocks (S)
 +.\" fake oplocks
 +.PP
 +.RS 4
 +Oplocks are the way that SMB clients get permission from a server to locally cache file operations\&. If a server grants an oplock (opportunistic lock) then the client is free to assume that it is the only one accessing the file and it will aggressively cache file data\&. With some oplock types the client may even cache file open/close operations\&. This can give enormous performance benefits\&.
 +.sp
 +When you set
 +fake oplocks = yes,
 +\fBsmbd\fR(8)
 +will always grant oplock requests no matter how many clients are using the file\&.
 +.sp
 +It is generally much better to use the real
 +\m[blue]\fBoplocks\fR\m[]
 +support rather than this parameter\&.
 +.sp
 +If you enable this option on all read\-only shares or shares that you know will only be accessed from one client at a time such as physically read\-only media like CDROMs, you will see a big performance improvement on many operations\&. If you enable this option on shares where multiple clients may be accessing the files read\-write at the same time you can get data corruption\&. Use this option carefully!
 +.sp
 +Default:
 +\fI\fIfake oplocks\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +follow symlinks (S)
 +.\" follow symlinks
 +.PP
 +.RS 4
 +This parameter allows the Samba administrator to stop
 +\fBsmbd\fR(8)
 +from following symbolic links in a particular share\&. Setting this parameter to
 +\fBno\fR
 +prevents any file or directory that is a symbolic link from being followed (the user will get an error)\&. This option is very useful to stop users from adding a symbolic link to
 +/etc/passwd
 +in their home directory for instance\&. However it will slow filename lookups down slightly\&.
 +.sp
 +This option is enabled (i\&.e\&.
 +smbd
 +will follow symbolic links) by default\&.
 +.sp
 +Default:
 +\fI\fIfollow symlinks\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +force create mode (S)
 +.\" force create mode
 +.PP
 +.RS 4
 +This parameter specifies a set of UNIX mode bit permissions that will
 +\fIalways\fR
 +be set on a file created by Samba\&. This is done by bitwise \*(AqOR\*(Aqing these bits onto the mode bits of a file that is being created\&. The default for this parameter is (in octal) 000\&. The modes in this parameter are bitwise \*(AqOR\*(Aqed onto the file mode after the mask set in the
 +\fIcreate mask\fR
 +parameter is applied\&.
 +.sp
 +The example below would force all newly created files to have read and execute permissions set for \*(Aqgroup\*(Aq and \*(Aqother\*(Aq as well as the read/write/execute bits set for the \*(Aquser\*(Aq\&.
 +.sp
 +Default:
 +\fI\fIforce create mode\fR\fR\fI = \fR\fI0000\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIforce create mode\fR\fR\fI = \fR\fI0755\fR\fI \fR
 +.RE
 +
 +force directory mode (S)
 +.\" force directory mode
 +.PP
 +.RS 4
 +This parameter specifies a set of UNIX mode bit permissions that will
 +\fIalways\fR
 +be set on a directory created by Samba\&. This is done by bitwise \*(AqOR\*(Aqing these bits onto the mode bits of a directory that is being created\&. The default for this parameter is (in octal) 0000 which will not add any extra permission bits to a created directory\&. This operation is done after the mode mask in the parameter
 +\fIdirectory mask\fR
 +is applied\&.
 +.sp
 +The example below would force all created directories to have read and execute permissions set for \*(Aqgroup\*(Aq and \*(Aqother\*(Aq as well as the read/write/execute bits set for the \*(Aquser\*(Aq\&.
 +.sp
 +Default:
 +\fI\fIforce directory mode\fR\fR\fI = \fR\fI0000\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIforce directory mode\fR\fR\fI = \fR\fI0755\fR\fI \fR
 +.RE
 +
 +force directory security mode (S)
 +.\" force directory security mode
 +.PP
 +.RS 4
 +This parameter has been removed for Samba 4\&.0\&.0\&.
 +.sp
 +\fINo default\fR
 +.RE
 +
 +group
 +.\" group
 +.PP
 +.RS 4
 +This parameter is a synonym for
 +force group\&.
 +.RE
 +
 +force group (S)
 +.\" force group
 +.PP
 +.RS 4
 +This specifies a UNIX group name that will be assigned as the default primary group for all users connecting to this service\&. This is useful for sharing files by ensuring that all access to files on service will use the named group for their permissions checking\&. Thus, by assigning permissions for this group to the files and directories within this service the Samba administrator can restrict or allow sharing of these files\&.
 +.sp
 +In Samba 2\&.0\&.5 and above this parameter has extended functionality in the following way\&. If the group name listed here has a \*(Aq+\*(Aq character prepended to it then the current user accessing the share only has the primary group default assigned to this group if they are already assigned as a member of that group\&. This allows an administrator to decide that only users who are already in a particular group will create files with group ownership set to that group\&. This gives  [...]
 +force group = +sys
 +means that only users who are already in group sys will have their default primary group assigned to sys when accessing this Samba share\&. All other users will retain their ordinary primary group\&.
 +.sp
 +If the
 +\m[blue]\fBforce user\fR\m[]
 +parameter is also set the group specified in
 +\fIforce group\fR
 +will override the primary group set in
 +\fIforce user\fR\&.
 +.sp
 +Default:
 +\fI\fIforce group\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIforce group\fR\fR\fI = \fR\fIagroup\fR\fI \fR
 +.RE
 +
 +force printername (S)
 +.\" force printername
 +.PP
 +.RS 4
 +When printing from Windows NT (or later), each printer in
 +smb\&.conf
 +has two associated names which can be used by the client\&. The first is the sharename (or shortname) defined in smb\&.conf\&. This is the only printername available for use by Windows 9x clients\&. The second name associated with a printer can be seen when browsing to the "Printers" (or "Printers and Faxes") folder on the Samba server\&. This is referred to simply as the printername (not to be confused with the
 +\fIprinter name\fR
 +option)\&.
 +.sp
 +When assigning a new driver to a printer on a remote Windows compatible print server such as Samba, the Windows client will rename the printer to match the driver name just uploaded\&. This can result in confusion for users when multiple printers are bound to the same driver\&. To prevent Samba from allowing the printer\*(Aqs printername to differ from the sharename defined in smb\&.conf, set
 +\fIforce printername = yes\fR\&.
 +.sp
 +Be aware that enabling this parameter may affect migrating printers from a Windows server to Samba since Windows has no way to force the sharename and printername to match\&.
 +.sp
 +It is recommended that this parameter\*(Aqs value not be changed once the printer is in use by clients as this could cause a user not be able to delete printer connections from their local Printers folder\&.
 +.sp
 +Default:
 +\fI\fIforce printername\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +force security mode (S)
 +.\" force security mode
 +.PP
 +.RS 4
 +This parameter has been removed for Samba 4\&.0\&.0\&.
 +.sp
 +\fINo default\fR
 +.RE
 +
 +force unknown acl user (S)
 +.\" force unknown acl user
 +.PP
 +.RS 4
 +If this parameter is set, a Windows NT ACL that contains an unknown SID (security descriptor, or representation of a user or group id) as the owner or group owner of the file will be silently mapped into the current UNIX uid or gid of the currently connected user\&.
 +.sp
 +This is designed to allow Windows NT clients to copy files and folders containing ACLs that were created locally on the client machine and contain users local to that machine only (no domain users) to be copied to a Samba server (usually with XCOPY /O) and have the unknown userid and groupid of the file owner map to the current connected user\&. This can only be fixed correctly when winbindd allows arbitrary mapping from any Windows NT SID to a UNIX uid or gid\&.
 +.sp
 +Try using this parameter when XCOPY /O gives an ACCESS_DENIED error\&.
 +.sp
 +Default:
 +\fI\fIforce unknown acl user\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +force user (S)
 +.\" force user
 +.PP
 +.RS 4
 +This specifies a UNIX user name that will be assigned as the default user for all users connecting to this service\&. This is useful for sharing files\&. You should also use it carefully as using it incorrectly can cause security problems\&.
 +.sp
 +This user name only gets used once a connection is established\&. Thus clients still need to connect as a valid user and supply a valid password\&. Once connected, all file operations will be performed as the "forced user", no matter what username the client connected as\&. This can be very useful\&.
 +.sp
 +In Samba 2\&.0\&.5 and above this parameter also causes the primary group of the forced user to be used as the primary group for all file activity\&. Prior to 2\&.0\&.5 the primary group was left as the primary group of the connecting user (this was a bug)\&.
 +.sp
 +Default:
 +\fI\fIforce user\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIforce user\fR\fR\fI = \fR\fIauser\fR\fI \fR
 +.RE
 +
 +fss: prune stale (G)
 +.\" fss: prune stale
 +.PP
 +.RS 4
 +When enabled, Samba\*(Aqs File Server Remove VSS Protocol (FSRVP) server checks all FSRVP initiated snapshots on startup, and removes any corresponding state (including share definitions) for nonexistent snapshot paths\&.
 +.sp
 +Default:
 +\fI\fIfss: prune stale\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIfss: prune stale\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +fss: sequence timeout (G)
 +.\" fss: sequence timeout
 +.PP
 +.RS 4
 +The File Server Remove VSS Protocol (FSRVP) server includes a message sequence timer to ensure cleanup on unexpected client disconnect\&. This parameter overrides the default timeout between FSRVP operations\&. FSRVP timeouts can be completely disabled via a value of 0\&.
 +.sp
 +Default:
 +\fI\fIfss: sequence timeout\fR\fR\fI = \fR\fI180 or 1800, depending on operation\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIfss: sequence timeout\fR\fR\fI = \fR\fI0\fR\fI \fR
 +.RE
 +
 +fstype (S)
 +.\" fstype
 +.PP
 +.RS 4
 +This parameter allows the administrator to configure the string that specifies the type of filesystem a share is using that is reported by
 +\fBsmbd\fR(8)
 +when a client queries the filesystem type for a share\&. The default type is
 +\fBNTFS\fR
 +for compatibility with Windows NT but this can be changed to other strings such as
 +\fBSamba\fR
 +or
 +\fBFAT\fR
 +if required\&.
 +.sp
 +Default:
 +\fI\fIfstype\fR\fR\fI = \fR\fINTFS\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIfstype\fR\fR\fI = \fR\fISamba\fR\fI \fR
 +.RE
 +
 +get quota command (G)
 +.\" get quota command
 +.PP
 +.RS 4
 +The
 +get quota command
 +should only be used whenever there is no operating system API available from the OS that samba can use\&.
 +.sp
 +This option is only available Samba was compiled with quotas support\&.
 +.sp
 +This parameter should specify the path to a script that queries the quota information for the specified user/group for the partition that the specified directory is on\&.
 +.sp
 +Such a script is being given 3 arguments:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +directory
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +type of query
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +uid of user or gid of group
 +.RE
 +.sp
 +.RE
 +The directory is actually mostly just "\&." \- It needs to be treated relatively to the current working directory that the script can also query\&.
 +.sp
 +The type of query can be one of:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +1 \- user quotas
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +2 \- user default quotas (uid = \-1)
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +3 \- group quotas
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +4 \- group default quotas (gid = \-1)
 +.RE
 +.sp
 +.RE
 +This script should print one line as output with spaces between the columns\&. The printed columns should be:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +1 \- quota flags (0 = no quotas, 1 = quotas enabled, 2 = quotas enabled and enforced)
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +2 \- number of currently used blocks
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +3 \- the softlimit number of blocks
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +4 \- the hardlimit number of blocks
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +5 \- currently used number of inodes
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +6 \- the softlimit number of inodes
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +7 \- the hardlimit number of inodes
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +8 (optional) \- the number of bytes in a block(default is 1024)
 +.RE
 +.sp
 +.RE
 +Default:
 +\fI\fIget quota command\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIget quota command\fR\fR\fI = \fR\fI/usr/local/sbin/query_quota\fR\fI \fR
 +.RE
 +
 +getwd cache (G)
 +.\" getwd cache
 +.PP
 +.RS 4
 +This is a tuning option\&. When this is enabled a caching algorithm will be used to reduce the time taken for getwd() calls\&. This can have a significant impact on performance, especially when the
 +\m[blue]\fBwide smbconfoptions\fR\m[]
 +parameter is set to
 +\fBno\fR\&.
 +.sp
 +Default:
 +\fI\fIgetwd cache\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +guest account (G)
 +.\" guest account
 +.PP
 +.RS 4
 +This is a username which will be used for access to services which are specified as
 +\m[blue]\fBguest ok\fR\m[]
 +(see below)\&. Whatever privileges this user has will be available to any client connecting to the guest service\&. This user must exist in the password file, but does not require a valid login\&. The user account "ftp" is often a good choice for this parameter\&.
 +.sp
 +On some systems the default guest account "nobody" may not be able to print\&. Use another account in this case\&. You should test this by trying to log in as your guest user (perhaps by using the
 +su \-
 +command) and trying to print using the system print command such as
 +lpr(1)
 +or
 +lp(1)\&.
 +.sp
 +This parameter does not accept % macros, because many parts of the system require this value to be constant for correct operation\&.
 +.sp
 +Default:
 +\fI\fIguest account\fR\fR\fI = \fR\fInobody # default can be changed at compile\-time\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIguest account\fR\fR\fI = \fR\fIftp\fR\fI \fR
 +.RE
 +
 +public
 +.\" public
 +.PP
 +.RS 4
 +This parameter is a synonym for
 +guest ok\&.
 +.RE
 +
 +guest ok (S)
 +.\" guest ok
 +.PP
 +.RS 4
 +If this parameter is
 +\fByes\fR
 +for a service, then no password is required to connect to the service\&. Privileges will be those of the
 +\m[blue]\fBguest account\fR\m[]\&.
 +.sp
 +This parameter nullifies the benefits of setting
 +\m[blue]\fBrestrict anonymous = 2\fR\m[]
 +.sp
 +See the section below on
 +\m[blue]\fBsecurity\fR\m[]
 +for more information about this option\&.
 +.sp
 +Default:
 +\fI\fIguest ok\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +only guest
 +.\" only guest
 +.PP
 +.RS 4
 +This parameter is a synonym for
 +guest only\&.
 +.RE
 +
 +guest only (S)
 +.\" guest only
 +.PP
 +.RS 4
 +If this parameter is
 +\fByes\fR
 +for a service, then only guest connections to the service are permitted\&. This parameter will have no effect if
 +\m[blue]\fBguest ok\fR\m[]
 +is not set for the service\&.
 +.sp
 +See the section below on
 +\m[blue]\fBsecurity\fR\m[]
 +for more information about this option\&.
 +.sp
 +Default:
 +\fI\fIguest only\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +hide dot files (S)
 +.\" hide dot files
 +.PP
 +.RS 4
 +This is a boolean parameter that controls whether files starting with a dot appear as hidden files\&.
 +.sp
 +Default:
 +\fI\fIhide dot files\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +hide files (S)
 +.\" hide files
 +.PP
 +.RS 4
 +This is a list of files or directories that are not visible but are accessible\&. The DOS \*(Aqhidden\*(Aq attribute is applied to any files or directories that match\&.
 +.sp
 +Each entry in the list must be separated by a \*(Aq/\*(Aq, which allows spaces to be included in the entry\&. \*(Aq*\*(Aq and \*(Aq?\*(Aq can be used to specify multiple files or directories as in DOS wildcards\&.
 +.sp
 +Each entry must be a Unix path, not a DOS path and must not include the Unix directory separator \*(Aq/\*(Aq\&.
 +.sp
 +Note that the case sensitivity option is applicable in hiding files\&.
 +.sp
 +Setting this parameter will affect the performance of Samba, as it will be forced to check all files and directories for a match as they are scanned\&.
 +.sp
 +The example shown above is based on files that the Macintosh SMB client (DAVE) available from
 +Thursby
 +creates for internal use, and also still hides all files beginning with a dot\&.
 +.sp
 +An example of us of this parameter is:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +hide files = /\&.*/DesktopFolderDB/TrashFor%m/resource\&.frk/
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.sp
 +Default:
 +\fI\fIhide files\fR\fR\fI = \fR\fI # no file are hidden\fR\fI \fR
 +.RE
 +
 +hide special files (S)
 +.\" hide special files
 +.PP
 +.RS 4
 +This parameter prevents clients from seeing special files such as sockets, devices and fifo\*(Aqs in directory listings\&.
 +.sp
 +Default:
 +\fI\fIhide special files\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +hide unreadable (S)
 +.\" hide unreadable
 +.PP
 +.RS 4
 +This parameter prevents clients from seeing the existance of files that cannot be read\&. Defaults to off\&.
 +.sp
 +Please note that enabling this can slow down listing large directories significantly\&. Samba has to evaluate the ACLs of all directory members, which can be a lot of effort\&.
 +.sp
 +Default:
 +\fI\fIhide unreadable\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +hide unwriteable files (S)
 +.\" hide unwriteable files
 +.PP
 +.RS 4
 +This parameter prevents clients from seeing the existance of files that cannot be written to\&. Defaults to off\&. Note that unwriteable directories are shown as usual\&.
 +.sp
 +Please note that enabling this can slow down listing large directories significantly\&. Samba has to evaluate the ACLs of all directory members, which can be a lot of effort\&.
 +.sp
 +Default:
 +\fI\fIhide unwriteable files\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +homedir map (G)
 +.\" homedir map
 +.PP
 +.RS 4
 +If
 +\m[blue]\fBnis homedir\fR\m[]
 +is
 +\fByes\fR, and
 +\fBsmbd\fR(8)
 +is also acting as a Win95/98
 +\fIlogon server\fR
 +then this parameter specifies the NIS (or YP) map from which the server for the user\*(Aqs home directory should be extracted\&. At present, only the Sun auto\&.home map format is understood\&. The form of the map is:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +username server:/some/file/system
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.sp
 +and the program will extract the servername from before the first \*(Aq:\*(Aq\&. There should probably be a better parsing system that copes with different map formats and also Amd (another automounter) maps\&.
 +.if n \{\
 +.sp
 +.\}
 +.RS 4
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBNote\fR
 +.ps -1
 +.br
 +A working NIS client is required on the system for this option to work\&.
 +.sp .5v
 +.RE
 +Default:
 +\fI\fIhomedir map\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIhomedir map\fR\fR\fI = \fR\fIamd\&.homedir\fR\fI \fR
 +.RE
 +
 +host msdfs (G)
 +.\" host msdfs
 +.PP
 +.RS 4
 +If set to
 +\fByes\fR, Samba will act as a Dfs server, and allow Dfs\-aware clients to browse Dfs trees hosted on the server\&.
 +.sp
 +See also the
 +\m[blue]\fBmsdfs root\fR\m[]
 +share level parameter\&. For more information on setting up a Dfs tree on Samba, refer to the MSFDS chapter in the book Samba3\-HOWTO\&.
 +.sp
 +Default:
 +\fI\fIhost msdfs\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +hostname lookups (G)
 +.\" hostname lookups
 +.PP
 +.RS 4
 +Specifies whether samba should use (expensive) hostname lookups or use the ip addresses instead\&. An example place where hostname lookups are currently used is when checking the
 +hosts deny
 +and
 +hosts allow\&.
 +.sp
 +Default:
 +\fI\fIhostname lookups\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIhostname lookups\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +allow hosts
 +.\" allow hosts
 +.PP
 +.RS 4
 +This parameter is a synonym for
 +hosts allow\&.
 +.RE
 +
 +hosts allow (S)
 +.\" hosts allow
 +.PP
 +.RS 4
 +A synonym for this parameter is
 +\m[blue]\fBallow hosts\fR\m[]\&.
 +.sp
 +This parameter is a comma, space, or tab delimited set of hosts which are permitted to access a service\&.
 +.sp
 +If specified in the [global] section then it will apply to all services, regardless of whether the individual service has a different setting\&.
 +.sp
 +You can specify the hosts by name or IP number\&. For example, you could restrict access to only the hosts on a Class C subnet with something like
 +allow hosts = 150\&.203\&.5\&.\&. The full syntax of the list is described in the man page
 +hosts_access(5)\&. Note that this man page may not be present on your system, so a brief description will be given here also\&.
 +.sp
 +Note that the localhost address 127\&.0\&.0\&.1 will always be allowed access unless specifically denied by a
 +\m[blue]\fBhosts deny\fR\m[]
 +option\&.
 +.sp
 +You can also specify hosts by network/netmask pairs and by netgroup names if your system supports netgroups\&. The
 +\fIEXCEPT\fR
 +keyword can also be used to limit a wildcard list\&. The following examples may provide some help:
 +.sp
 +Example 1: allow all IPs in 150\&.203\&.*\&.*; except one
 +.sp
 +hosts allow = 150\&.203\&. EXCEPT 150\&.203\&.6\&.66
 +.sp
 +Example 2: allow hosts that match the given network/netmask
 +.sp
 +hosts allow = 150\&.203\&.15\&.0/255\&.255\&.255\&.0
 +.sp
 +Example 3: allow a couple of hosts
 +.sp
 +hosts allow = lapland, arvidsjaur
 +.sp
 +Example 4: allow only hosts in NIS netgroup "foonet", but deny access from one particular host
 +.sp
 +hosts allow = @foonet
 +.sp
 +hosts deny = pirate
 +.if n \{\
 +.sp
 +.\}
 +.RS 4
 +.it 1 an-trap
 +.nr an-no-space-flag 1
 +.nr an-break-flag 1
 +.br
 +.ps +1
 +\fBNote\fR
 +.ps -1
 +.br
 +Note that access still requires suitable user\-level passwords\&.
 +.sp .5v
 +.RE
 +See
 +\fBtestparm\fR(1)
 +for a way of testing your host access to see if it does what you expect\&.
 +.sp
 +Default:
 +\fI\fIhosts allow\fR\fR\fI = \fR\fI # none (i\&.e\&., all hosts permitted access)\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIhosts allow\fR\fR\fI = \fR\fI150\&.203\&.5\&. myhost\&.mynet\&.edu\&.au\fR\fI \fR
 +.RE
 +
 +deny hosts
 +.\" deny hosts
 +.PP
 +.RS 4
 +This parameter is a synonym for
 +hosts deny\&.
 +.RE
 +
 +hosts deny (S)
 +.\" hosts deny
 +.PP
 +.RS 4
 +The opposite of
 +\fIhosts allow\fR
 +\- hosts listed here are
 +\fINOT\fR
 +permitted access to services unless the specific services have their own lists to override this one\&. Where the lists conflict, the
 +\fIallow\fR
 +list takes precedence\&.
 +.sp
 +In the event that it is necessary to deny all by default, use the keyword ALL (or the netmask
 +0\&.0\&.0\&.0/0) and then explicitly specify to the
 +\m[blue]\fBhosts allow = hosts allow\fR\m[]
 +parameter those hosts that should be permitted access\&.
 +.sp
 +Default:
 +\fI\fIhosts deny\fR\fR\fI = \fR\fI # none (i\&.e\&., no hosts specifically excluded)\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIhosts deny\fR\fR\fI = \fR\fI150\&.203\&.4\&. badhost\&.mynet\&.edu\&.au\fR\fI \fR
 +.RE
 +
 +idmap backend (G)
 +.\" idmap backend
 +.PP
 +.RS 4
 +The idmap backend provides a plugin interface for Winbind to use varying backends to store SID/uid/gid mapping tables\&.
 +.sp
 +This option specifies the default backend that is used when no special configuration set, but it is now deprecated in favour of the new spelling
 +\m[blue]\fBidmap config * : backend\fR\m[]\&.
 +.sp
 +Default:
 +\fI\fIidmap backend\fR\fR\fI = \fR\fItdb\fR\fI \fR
 +.RE
 +
 +idmap cache time (G)
 +.\" idmap cache time
 +.PP
 +.RS 4
 +This parameter specifies the number of seconds that Winbind\*(Aqs idmap interface will cache positive SID/uid/gid query results\&. By default, Samba will cache these results for one week\&.
 +.sp
 +Default:
 +\fI\fIidmap cache time\fR\fR\fI = \fR\fI604800\fR\fI \fR
 +.RE
 +
 +idmap config:OPTION (G)
 +.\" idmap config:OPTION
 +.PP
 +.RS 4
 +ID mapping in Samba is the mapping between Windows SIDs and Unix user and group IDs\&. This is performed by Winbindd with a configurable plugin interface\&. Samba\*(Aqs ID mapping is configured by options starting with the
 +\m[blue]\fBidmap config\fR\m[]
 +prefix\&. An idmap option consists of the
 +\m[blue]\fBidmap config\fR\m[]
 +prefix, followed by a domain name or the asterisk character (*), a colon, and the name of an idmap setting for the chosen domain\&.
 +.sp
 +The idmap configuration is hence divided into groups, one group for each domain to be configured, and one group with the asterisk instead of a proper domain name, which specifies the default configuration that is used to catch all domains that do not have an explicit idmap configuration of their own\&.
 +.sp
 +There are three general options available:
 +.PP
 +backend = backend_name
 +.RS 4
 +This specifies the name of the idmap plugin to use as the SID/uid/gid backend for this domain\&. The standard backends are tdb (\fBidmap_tdb\fR(8)), tdb2 (\fBidmap_tdb2\fR(8)), ldap (\fBidmap_ldap\fR(8)), , rid (\fBidmap_rid\fR(8)), , hash (\fBidmap_hash\fR(8)), , autorid (\fBidmap_autorid\fR(8)), , ad (\fBidmap_ad\fR(8)), , and nss\&. (\fBidmap_nss\fR(8)), The corresponding manual pages contain the details, but here is a summary\&.
 +.sp
 +The first three of these create mappings of their own using internal unixid counters and store the mappings in a database\&. These are suitable for use in the default idmap configuration\&. The rid and hash backends use a pure algorithmic calculation to determine the unixid for a SID\&. The autorid module is a mixture of the tdb and rid backend\&. It creates ranges for each domain encountered and then uses the rid algorithm for each of these automatically configured domains individually [...]
 +.RE
 +.PP
 +range = low \- high
 +.RS 4
 +Defines the available matching uid and gid range for which the backend is authoritative\&. For allocating backends, this also defines the start and the end of the range for allocating new unique IDs\&.
 +.sp
 +winbind uses this parameter to find the backend that is authoritative for a unix ID to SID mapping, so it must be set for each individually configured domain and for the default configuration\&. The configured ranges must be mutually disjoint\&.
 +.RE
 +.PP
 +read only = yes|no
 +.RS 4
 +This option can be used to turn the writing backends tdb, tdb2, and ldap into read only mode\&. This can be useful e\&.g\&. in cases where a pre\-filled database exists that should not be extended automatically\&.
 +.RE
 +.sp
 +The following example illustrates how to configure the
 +\fBidmap_ad\fR(8)
 +backend for the CORP domain and the
 +\fBidmap_tdb\fR(8)
 +backend for all other domains\&. This configuration assumes that the admin of CORP assigns unix ids below 1000000 via the SFU extensions, and winbind is supposed to use the next million entries for its own mappings from trusted domains and for local groups for example\&.
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	idmap config * : backend = tdb
 +	idmap config * : range = 1000000\-1999999
 +
 +	idmap config CORP : backend  = ad
 +	idmap config CORP : range = 1000\-999999
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.sp
 +\fINo default\fR
 +.RE
 +
 +winbind gid
 +.\" winbind gid
 +.PP
 +.RS 4
 +This parameter is a synonym for
 +idmap gid\&.
 +.RE
 +
 +idmap gid (G)
 +.\" idmap gid
 +.PP
 +.RS 4
 +The idmap gid parameter specifies the range of group ids for the default idmap configuration\&. It is now deprecated in favour of
 +\m[blue]\fBidmap config * : range\fR\m[]\&.
 +.sp
 +See the
 +\m[blue]\fBidmap config\fR\m[]
 +option\&.
 +.sp
 +Default:
 +\fI\fIidmap gid\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIidmap gid\fR\fR\fI = \fR\fI10000\-20000\fR\fI \fR
 +.RE
 +
 +idmap negative cache time (G)
 +.\" idmap negative cache time
 +.PP
 +.RS 4
 +This parameter specifies the number of seconds that Winbind\*(Aqs idmap interface will cache negative SID/uid/gid query results\&.
 +.sp
 +Default:
 +\fI\fIidmap negative cache time\fR\fR\fI = \fR\fI120\fR\fI \fR
 +.RE
 +
 +winbind uid
 +.\" winbind uid
 +.PP
 +.RS 4
 +This parameter is a synonym for
 +idmap uid\&.
 +.RE
 +
 +idmap uid (G)
 +.\" idmap uid
 +.PP
 +.RS 4
 +The idmap uid parameter specifies the range of user ids for the default idmap configuration\&. It is now deprecated in favour of
 +\m[blue]\fBidmap config * : range\fR\m[]\&.
 +.sp
 +See the
 +\m[blue]\fBidmap config\fR\m[]
 +option\&.
 +.sp
 +Default:
 +\fI\fIidmap uid\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIidmap uid\fR\fR\fI = \fR\fI10000\-20000\fR\fI \fR
 +.RE
 +
 +include (G)
 +.\" include
 +.PP
 +.RS 4
 +This allows you to include one config file inside another\&. The file is included literally, as though typed in place\&.
 +.sp
 +It takes the standard substitutions, except
 +\fI%u\fR,
 +\fI%P\fR
 +and
 +\fI%S\fR\&.
 +.sp
 +The parameter
 +\fIinclude = registry\fR
 +has a special meaning: It does
 +\fInot\fR
 +include a file named
 +\fIregistry\fR
 +from the current working directory, but instead reads the global configuration options from the registry\&. See the section on registry\-based configuration for details\&. Note that this option automatically activates registry shares\&.
 +.sp
 +Default:
 +\fI\fIinclude\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIinclude\fR\fR\fI = \fR\fI/usr/local/samba/lib/admin_smb\&.conf\fR\fI \fR
 +.RE
 +
 +inherit acls (S)
 +.\" inherit acls
 +.PP
 +.RS 4
 +This parameter can be used to ensure that if default acls exist on parent directories, they are always honored when creating a new file or subdirectory in these parent directories\&. The default behavior is to use the unix mode specified when creating the directory\&. Enabling this option sets the unix mode to 0777, thus guaranteeing that default directory acls are propagated\&. Note that using the VFS modules acl_xattr or acl_tdb which store native Windows as meta\-data will automatica [...]
 +.sp
 +Default:
 +\fI\fIinherit acls\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +inherit owner (S)
 +.\" inherit owner
 +.PP
 +.RS 4
 +The ownership of new files and directories is normally governed by effective uid of the connected user\&. This option allows the Samba administrator to specify that the ownership for new files and directories should be controlled by the ownership of the parent directory\&.
 +.sp
 +Common scenarios where this behavior is useful is in implementing drop\-boxes, where users can create and edit files but not delete them and ensuring that newly created files in a user\*(Aqs roaming profile directory are actually owned by the user\&.
 +.sp
 +Default:
 +\fI\fIinherit owner\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +inherit permissions (S)
 +.\" inherit permissions
 +.PP
 +.RS 4
 +The permissions on new files and directories are normally governed by
 +\m[blue]\fBcreate mask\fR\m[],
 +\m[blue]\fBdirectory mask\fR\m[],
 +\m[blue]\fBforce create mode\fR\m[]
 +and
 +\m[blue]\fBforce directory mode\fR\m[]
 +but the boolean inherit permissions parameter overrides this\&.
 +.sp
 +New directories inherit the mode of the parent directory, including bits such as setgid\&.
 +.sp
 +New files inherit their read/write bits from the parent directory\&. Their execute bits continue to be determined by
 +\m[blue]\fBmap archive\fR\m[],
 +\m[blue]\fBmap hidden\fR\m[]
 +and
 +\m[blue]\fBmap system\fR\m[]
 +as usual\&.
 +.sp
 +Note that the setuid bit is
 +\fInever\fR
 +set via inheritance (the code explicitly prohibits this)\&.
 +.sp
 +This can be particularly useful on large systems with many users, perhaps several thousand, to allow a single [homes] share to be used flexibly by each user\&.
 +.sp
 +Default:
 +\fI\fIinherit permissions\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +init logon delay (G)
 +.\" init logon delay
 +.PP
 +.RS 4
 +This parameter specifies a delay in milliseconds for the hosts configured for delayed initial samlogon with
 +\m[blue]\fBinit logon delayed hosts\fR\m[]\&.
 +.sp
 +Default:
 +\fI\fIinit logon delay\fR\fR\fI = \fR\fI100\fR\fI \fR
 +.RE
 +
 +init logon delayed hosts (G)
 +.\" init logon delayed hosts
 +.PP
 +.RS 4
 +This parameter takes a list of host names, addresses or networks for which the initial samlogon reply should be delayed (so other DCs get preferred by XP workstations if there are any)\&.
 +.sp
 +The length of the delay can be specified with the
 +\m[blue]\fBinit logon delay\fR\m[]
 +parameter\&.
 +.sp
 +Default:
 +\fI\fIinit logon delayed hosts\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIinit logon delayed hosts\fR\fR\fI = \fR\fI150\&.203\&.5\&. myhost\&.mynet\&.de\fR\fI \fR
 +.RE
 +
 +interfaces (G)
 +.\" interfaces
 +.PP
 +.RS 4
 +This option allows you to override the default network interfaces list that Samba will use for browsing, name registration and other NetBIOS over TCP/IP (NBT) traffic\&. By default Samba will query the kernel for the list of all active interfaces and use any interfaces except 127\&.0\&.0\&.1 that are broadcast capable\&.
 +.sp
 +The option takes a list of interface strings\&. Each string can be in any of the following forms:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +a network interface name (such as eth0)\&. This may include shell\-like wildcards so eth* will match any interface starting with the substring "eth"
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +an IP address\&. In this case the netmask is determined from the list of interfaces obtained from the kernel
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +an IP/mask pair\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +a broadcast/mask pair\&.
 +.RE
 +.sp
 +.RE
 +The "mask" parameters can either be a bit length (such as 24 for a C class network) or a full netmask in dotted decimal form\&.
 +.sp
 +The "IP" parameters above can either be a full dotted decimal IP address or a hostname which will be looked up via the OS\*(Aqs normal hostname resolution mechanisms\&.
 +.sp
 +By default Samba enables all active interfaces that are broadcast capable except the loopback adaptor (IP address 127\&.0\&.0\&.1)\&.
 +.sp
 +The example below configures three network interfaces corresponding to the eth0 device and IP addresses 192\&.168\&.2\&.10 and 192\&.168\&.3\&.10\&. The netmasks of the latter two interfaces would be set to 255\&.255\&.255\&.0\&.
 +.sp
 +Default:
 +\fI\fIinterfaces\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIinterfaces\fR\fR\fI = \fR\fIeth0 192\&.168\&.2\&.10/24 192\&.168\&.3\&.10/255\&.255\&.255\&.0\fR\fI \fR
 +.RE
 +
 +invalid users (S)
 +.\" invalid users
 +.PP
 +.RS 4
 +This is a list of users that should not be allowed to login to this service\&. This is really a
 +\fIparanoid\fR
 +check to absolutely ensure an improper setting does not breach your security\&.
 +.sp
 +A name starting with a \*(Aq@\*(Aq is interpreted as an NIS netgroup first (if your system supports NIS), and then as a UNIX group if the name was not found in the NIS netgroup database\&.
 +.sp
 +A name starting with \*(Aq+\*(Aq is interpreted only by looking in the UNIX group database via the NSS getgrnam() interface\&. A name starting with \*(Aq&\*(Aq is interpreted only by looking in the NIS netgroup database (this requires NIS to be working on your system)\&. The characters \*(Aq+\*(Aq and \*(Aq&\*(Aq may be used at the start of the name in either order so the value
 +\fI+&group\fR
 +means check the UNIX group database, followed by the NIS netgroup database, and the value
 +\fI&+group\fR
 +means check the NIS netgroup database, followed by the UNIX group database (the same as the \*(Aq@\*(Aq prefix)\&.
 +.sp
 +The current servicename is substituted for
 +\fI%S\fR\&. This is useful in the [homes] section\&.
 +.sp
 +Default:
 +\fI\fIinvalid users\fR\fR\fI = \fR\fI # no invalid users\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIinvalid users\fR\fR\fI = \fR\fIroot fred admin @wheel\fR\fI \fR
 +.RE
 +
 +iprint server (G)
 +.\" iprint server
 +.PP
 +.RS 4
 +This parameter is only applicable if
 +\m[blue]\fBprinting\fR\m[]
 +is set to
 +\fBiprint\fR\&.
 +.sp
 +If set, this option overrides the ServerName option in the CUPS
 +client\&.conf\&. This is necessary if you have virtual samba servers that connect to different CUPS daemons\&.
 +.sp
 +Default:
 +\fI\fIiprint server\fR\fR\fI = \fR\fI""\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIiprint server\fR\fR\fI = \fR\fIMYCUPSSERVER\fR\fI \fR
 +.RE
 +
 +keepalive (G)
 +.\" keepalive
 +.PP
 +.RS 4
 +The value of the parameter (an integer) represents the number of seconds between
 +\fIkeepalive\fR
 +packets\&. If this parameter is zero, no keepalive packets will be sent\&. Keepalive packets, if sent, allow the server to tell whether a client is still present and responding\&.
 +.sp
 +Keepalives should, in general, not be needed if the socket has the SO_KEEPALIVE attribute set on it by default\&. (see
 +\m[blue]\fBsocket options\fR\m[])\&. Basically you should only use this option if you strike difficulties\&.
 +.sp
 +Please note this option only applies to SMB1 client connections, and has no effect on SMB2 clients\&.
 +.sp
 +Default:
 +\fI\fIkeepalive\fR\fR\fI = \fR\fI300\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIkeepalive\fR\fR\fI = \fR\fI600\fR\fI \fR
 +.RE
 +
 +kerberos method (G)
 +.\" kerberos method
 +.PP
 +.RS 4
 +Controls how kerberos tickets are verified\&.
 +.sp
 +Valid options are:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +secrets only \- use only the secrets\&.tdb for ticket verification (default)
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +system keytab \- use only the system keytab for ticket verification
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +dedicated keytab \- use a dedicated keytab for ticket verification
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +secrets and keytab \- use the secrets\&.tdb first, then the system keytab
 +.RE
 +.sp
 +.RE
 +The major difference between "system keytab" and "dedicated keytab" is that the latter method relies on kerberos to find the correct keytab entry instead of filtering based on expected principals\&.
 +.sp
 +When the kerberos method is in "dedicated keytab" mode,
 +\m[blue]\fBdedicated keytab file\fR\m[]
 +must be set to specify the location of the keytab file\&.
 +.sp
 +Default:
 +\fI\fIkerberos method\fR\fR\fI = \fR\fIdefault\fR\fI \fR
 +.RE
 +
 +kernel change notify (G)
 +.\" kernel change notify
 +.PP
 +.RS 4
 +This parameter specifies whether Samba should ask the kernel for change notifications in directories so that SMB clients can refresh whenever the data on the server changes\&.
 +.sp
 +This parameter is only used when your kernel supports change notification to user programs using the inotify interface\&.
 +.sp
 +Default:
 +\fI\fIkernel change notify\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +kernel oplocks (S)
 +.\" kernel oplocks
 +.PP
 +.RS 4
 +For UNIXes that support kernel based
 +\m[blue]\fBoplocks\fR\m[]
 +(currently only IRIX and the Linux 2\&.4 kernel), this parameter allows the use of them to be turned on or off\&. However, this disables Level II oplocks for clients as the Linux and IRIX kernels do not support them properly\&.
 +.sp
 +Kernel oplocks support allows Samba
 +\fIoplocks \fR
 +to be broken whenever a local UNIX process or NFS operation accesses a file that
 +\fBsmbd\fR(8)
 +has oplocked\&. This allows complete data consistency between SMB/CIFS, NFS and local file access (and is a
 +\fIvery\fR
 +cool feature :\-)\&.
 +.sp
 +If you do not need this interaction, you should disable the parameter on Linux and IRIX to get Level II oplocks and the associated performance benefit\&.
 +.sp
 +This parameter defaults to
 +\fBno\fR
 +and is translated to a no\-op on systems that do not have the necessary kernel support\&.
 +.sp
 +Default:
 +\fI\fIkernel oplocks\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +kernel share modes (S)
 +.\" kernel share modes
 +.PP
 +.RS 4
 +This parameter controls whether SMB share modes are translated into UNIX flocks\&.
 +.sp
 +Kernel share modes provide a minimal level of interoperability with local UNIX processes and NFS operations by preventing access with flocks corresponding to the SMB share modes\&. Generally, it is very desirable to leave this enabled\&.
 +.sp
 +Note that in order to use SMB2 durable file handles on a share, you have to turn kernel share modes off\&.
 +.sp
 +This parameter defaults to
 +\fByes\fR
 +and is translated to a no\-op on systems that do not have the necessary kernel flock support\&.
 +.sp
 +Default:
 +\fI\fIkernel share modes\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +kpasswd port (G)
 +.\" kpasswd port
 +.PP
 +.RS 4
 +Specifies which ports the Kerberos server should listen on for password changes\&.
 +.sp
 +Default:
 +\fI\fIkpasswd port\fR\fR\fI = \fR\fI464\fR\fI \fR
 +.RE
 +
 +krb5 port (G)
 +.\" krb5 port
 +.PP
 +.RS 4
 +Specifies which port the KDC should listen on for Kerberos traffic\&.
 +.sp
 +Default:
 +\fI\fIkrb5 port\fR\fR\fI = \fR\fI88\fR\fI \fR
 +.RE
 +
 +lanman auth (G)
 +.\" lanman auth
 +.PP
 +.RS 4
 +This parameter determines whether or not
 +\fBsmbd\fR(8)
 +will attempt to authenticate users or permit password changes using the LANMAN password hash\&. If disabled, only clients which support NT password hashes (e\&.g\&. Windows NT/2000 clients, smbclient, but not Windows 95/98 or the MS DOS network client) will be able to connect to the Samba host\&.
 +.sp
 +The LANMAN encrypted response is easily broken, due to its case\-insensitive nature, and the choice of algorithm\&. Servers without Windows 95/98/ME or MS DOS clients are advised to disable this option\&.
 +.sp
 +When this parameter is set to
 +no
 +this will also result in sambaLMPassword in Samba\*(Aqs passdb being blanked after the next password change\&. As a result of that lanman clients won\*(Aqt be able to authenticate, even if lanman auth is reenabled later on\&.
 +.sp
 +Unlike the
 +encrypt passwords
 +option, this parameter cannot alter client behaviour, and the LANMAN response will still be sent over the network\&. See the
 +client lanman auth
 +to disable this for Samba\*(Aqs clients (such as smbclient)
 +.sp
 +If this option, and
 +ntlm auth
 +are both disabled, then only NTLMv2 logins will be permited\&. Not all clients support NTLMv2, and most will require special configuration to use it\&.
 +.sp
 +Default:
 +\fI\fIlanman auth\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +large readwrite (G)
 +.\" large readwrite
 +.PP
 +.RS 4
 +This parameter determines whether or not
 +\fBsmbd\fR(8)
 +supports the new 64k streaming read and write variant SMB requests introduced with Windows 2000\&. Note that due to Windows 2000 client redirector bugs this requires Samba to be running on a 64\-bit capable operating system such as IRIX, Solaris or a Linux 2\&.4 kernel\&. Can improve performance by 10% with Windows 2000 clients\&. Defaults to on\&. Not as tested as some other Samba code paths\&.
 +.sp
 +Default:
 +\fI\fIlarge readwrite\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +ldap admin dn (G)
 +.\" ldap admin dn
 +.PP
 +.RS 4
 +The
 +\m[blue]\fBldap admin dn\fR\m[]
 +defines the Distinguished Name (DN) name used by Samba to contact the ldap server when retreiving user account information\&. The
 +\m[blue]\fBldap admin dn\fR\m[]
 +is used in conjunction with the admin dn password stored in the
 +private/secrets\&.tdb
 +file\&. See the
 +\fBsmbpasswd\fR(8)
 +man page for more information on how to accomplish this\&.
 +.sp
 +The
 +\m[blue]\fBldap admin dn\fR\m[]
 +requires a fully specified DN\&. The
 +\m[blue]\fBldap suffix\fR\m[]
 +is not appended to the
 +\m[blue]\fBldap admin dn\fR\m[]\&.
 +.sp
 +\fINo default\fR
 +.RE
 +
 +ldap connection timeout (G)
 +.\" ldap connection timeout
 +.PP
 +.RS 4
 +This parameter tells the LDAP library calls which timeout in seconds they should honor during initial connection establishments to LDAP servers\&. It is very useful in failover scenarios in particular\&. If one or more LDAP servers are not reachable at all, we do not have to wait until TCP timeouts are over\&. This feature must be supported by your LDAP library\&.
 +.sp
 +This parameter is different from
 +\m[blue]\fBldap timeout\fR\m[]
 +which affects operations on LDAP servers using an existing connection and not establishing an initial connection\&.
 +.sp
 +Default:
 +\fI\fIldap connection timeout\fR\fR\fI = \fR\fI2\fR\fI \fR
 +.RE
 +
 +ldap debug level (G)
 +.\" ldap debug level
 +.PP
 +.RS 4
 +This parameter controls the debug level of the LDAP library calls\&. In the case of OpenLDAP, it is the same bit\-field as understood by the server and documented in the
 +\fBslapd.conf\fR(5)
 +manpage\&. A typical useful value will be
 +\fI1\fR
 +for tracing function calls\&.
 +.sp
 +The debug output from the LDAP libraries appears with the prefix [LDAP] in Samba\*(Aqs logging output\&. The level at which LDAP logging is printed is controlled by the parameter
 +\fIldap debug threshold\fR\&.
 +.sp
 +Default:
 +\fI\fIldap debug level\fR\fR\fI = \fR\fI0\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIldap debug level\fR\fR\fI = \fR\fI1\fR\fI \fR
 +.RE
 +
 +ldap debug threshold (G)
 +.\" ldap debug threshold
 +.PP
 +.RS 4
 +This parameter controls the Samba debug level at which the ldap library debug output is printed in the Samba logs\&. See the description of
 +\fIldap debug level\fR
 +for details\&.
 +.sp
 +Default:
 +\fI\fIldap debug threshold\fR\fR\fI = \fR\fI10\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIldap debug threshold\fR\fR\fI = \fR\fI5\fR\fI \fR
 +.RE
 +
 +ldap delete dn (G)
 +.\" ldap delete dn
 +.PP
 +.RS 4
 +This parameter specifies whether a delete operation in the ldapsam deletes the complete entry or only the attributes specific to Samba\&.
 +.sp
 +Default:
 +\fI\fIldap delete dn\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +ldap deref (G)
 +.\" ldap deref
 +.PP
 +.RS 4
 +This option controls whether Samba should tell the LDAP library to use a certain alias dereferencing method\&. The default is
 +\fIauto\fR, which means that the default setting of the ldap client library will be kept\&. Other possible values are
 +\fInever\fR,
 +\fIfinding\fR,
 +\fIsearching\fR
 +and
 +\fIalways\fR\&. Grab your LDAP manual for more information\&.
 +.sp
 +Default:
 +\fI\fIldap deref\fR\fR\fI = \fR\fIauto\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIldap deref\fR\fR\fI = \fR\fIsearching\fR\fI \fR
 +.RE
 +
 +ldap follow referral (G)
 +.\" ldap follow referral
 +.PP
 +.RS 4
 +This option controls whether to follow LDAP referrals or not when searching for entries in the LDAP database\&. Possible values are
 +\fIon\fR
 +to enable following referrals,
 +\fIoff\fR
 +to disable this, and
 +\fIauto\fR, to use the libldap default settings\&. libldap\*(Aqs choice of following referrals or not is set in /etc/openldap/ldap\&.conf with the REFERRALS parameter as documented in ldap\&.conf(5)\&.
 +.sp
 +Default:
 +\fI\fIldap follow referral\fR\fR\fI = \fR\fIauto\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIldap follow referral\fR\fR\fI = \fR\fIoff\fR\fI \fR
 +.RE
 +
 +ldap group suffix (G)
 +.\" ldap group suffix
 +.PP
 +.RS 4
 +This parameter specifies the suffix that is used for groups when these are added to the LDAP directory\&. If this parameter is unset, the value of
 +\m[blue]\fBldap suffix\fR\m[]
 +will be used instead\&. The suffix string is pre\-pended to the
 +\m[blue]\fBldap suffix\fR\m[]
 +string so use a partial DN\&.
 +.sp
 +Default:
 +\fI\fIldap group suffix\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIldap group suffix\fR\fR\fI = \fR\fIou=Groups\fR\fI \fR
 +.RE
 +
 +ldap idmap suffix (G)
 +.\" ldap idmap suffix
 +.PP
 +.RS 4
 +This parameters specifies the suffix that is used when storing idmap mappings\&. If this parameter is unset, the value of
 +\m[blue]\fBldap suffix\fR\m[]
 +will be used instead\&. The suffix string is pre\-pended to the
 +\m[blue]\fBldap suffix\fR\m[]
 +string so use a partial DN\&.
 +.sp
 +Default:
 +\fI\fIldap idmap suffix\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIldap idmap suffix\fR\fR\fI = \fR\fIou=Idmap\fR\fI \fR
 +.RE
 +
 +ldap machine suffix (G)
 +.\" ldap machine suffix
 +.PP
 +.RS 4
 +It specifies where machines should be added to the ldap tree\&. If this parameter is unset, the value of
 +\m[blue]\fBldap suffix\fR\m[]
 +will be used instead\&. The suffix string is pre\-pended to the
 +\m[blue]\fBldap suffix\fR\m[]
 +string so use a partial DN\&.
 +.sp
 +Default:
 +\fI\fIldap machine suffix\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIldap machine suffix\fR\fR\fI = \fR\fIou=Computers\fR\fI \fR
 +.RE
 +
 +ldap page size (G)
 +.\" ldap page size
 +.PP
 +.RS 4
 +This parameter specifies the number of entries per page\&.
 +.sp
 +If the LDAP server supports paged results, clients can request subsets of search results (pages) instead of the entire list\&. This parameter specifies the size of these pages\&.
 +.sp
 +Default:
 +\fI\fIldap page size\fR\fR\fI = \fR\fI1024\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIldap page size\fR\fR\fI = \fR\fI512\fR\fI \fR
 +.RE
 +
 +ldap password sync
 +.\" ldap password sync
 +.PP
 +.RS 4
 +This parameter is a synonym for
 +ldap passwd sync\&.
 +.RE
 +
 +ldap passwd sync (G)
 +.\" ldap passwd sync
 +.PP
 +.RS 4
 +This option is used to define whether or not Samba should sync the LDAP password with the NT and LM hashes for normal accounts (NOT for workstation, server or domain trusts) on a password change via SAMBA\&.
 +.sp
 +The
 +\m[blue]\fBldap passwd sync\fR\m[]
 +can be set to one of three values:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIYes\fR
 += Try to update the LDAP, NT and LM passwords and update the pwdLastSet time\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fINo\fR
 += Update NT and LM passwords and update the pwdLastSet time\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIOnly\fR
 += Only update the LDAP password and let the LDAP server do the rest\&.
 +.RE
 +.sp
 +.RE
 +Default:
 +\fI\fIldap passwd sync\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +ldap replication sleep (G)
 +.\" ldap replication sleep
 +.PP
 +.RS 4
 +When Samba is asked to write to a read\-only LDAP replica, we are redirected to talk to the read\-write master server\&. This server then replicates our changes back to the \*(Aqlocal\*(Aq server, however the replication might take some seconds, especially over slow links\&. Certain client activities, particularly domain joins, can become confused by the \*(Aqsuccess\*(Aq that does not immediately change the LDAP back\-end\*(Aqs data\&.
 +.sp
 +This option simply causes Samba to wait a short time, to allow the LDAP server to catch up\&. If you have a particularly high\-latency network, you may wish to time the LDAP replication with a network sniffer, and increase this value accordingly\&. Be aware that no checking is performed that the data has actually replicated\&.
 +.sp
 +The value is specified in milliseconds, the maximum value is 5000 (5 seconds)\&.
 +.sp
 +Default:
 +\fI\fIldap replication sleep\fR\fR\fI = \fR\fI1000\fR\fI \fR
 +.RE
 +
 +ldapsam:editposix (G)
 +.\" ldapsam:editposix
 +.PP
 +.RS 4
 +Editposix is an option that leverages ldapsam:trusted to make it simpler to manage a domain controller eliminating the need to set up custom scripts to add and manage the posix users and groups\&. This option will instead directly manipulate the ldap tree to create, remove and modify user and group entries\&. This option also requires a running winbindd as it is used to allocate new uids/gids on user/group creation\&. The allocation range must be therefore configured\&.
 +.sp
 +To use this option, a basic ldap tree must be provided and the ldap suffix parameters must be properly configured\&. On virgin servers the default users and groups (Administrator, Guest, Domain Users, Domain Admins, Domain Guests) can be precreated with the command
 +net sam provision\&. To run this command the ldap server must be running, Winbindd must be running and the smb\&.conf ldap options must be properly configured\&. The typical ldap setup used with the
 +\m[blue]\fBldapsam:trusted = yes\fR\m[]
 +option is usually sufficient to use
 +\m[blue]\fBldapsam:editposix = yes\fR\m[]
 +as well\&.
 +.sp
 +An example configuration can be the following:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	encrypt passwords = true
 +	passdb backend = ldapsam
 +
 +	ldapsam:trusted=yes
 +	ldapsam:editposix=yes
 +
 +	ldap admin dn = cn=admin,dc=samba,dc=org
 +	ldap delete dn = yes
 +	ldap group suffix = ou=groups
 +	ldap idmap suffix = ou=idmap
 +	ldap machine suffix = ou=computers
 +	ldap user suffix = ou=users
 +	ldap suffix = dc=samba,dc=org
 +
 +	idmap backend = ldap:"ldap://localhost"
 +
 +	idmap uid = 5000\-50000
 +	idmap gid = 5000\-50000
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.sp
 +This configuration assumes a directory layout like described in the following ldif:
 +.sp
 +.if n \{\
 +.RS 4
 +.\}
 +.nf
 +	dn: dc=samba,dc=org
 +	objectClass: top
 +	objectClass: dcObject
 +	objectClass: organization
 +	o: samba\&.org
 +	dc: samba
 +
 +	dn: cn=admin,dc=samba,dc=org
 +	objectClass: simpleSecurityObject
 +	objectClass: organizationalRole
 +	cn: admin
 +	description: LDAP administrator
 +	userPassword: secret
 +
 +	dn: ou=users,dc=samba,dc=org
 +	objectClass: top
 +	objectClass: organizationalUnit
 +	ou: users
 +
 +	dn: ou=groups,dc=samba,dc=org
 +	objectClass: top
 +	objectClass: organizationalUnit
 +	ou: groups
 +
 +	dn: ou=idmap,dc=samba,dc=org
 +	objectClass: top
 +	objectClass: organizationalUnit
 +	ou: idmap
 +
 +	dn: ou=computers,dc=samba,dc=org
 +	objectClass: top
 +	objectClass: organizationalUnit
 +	ou: computers
 +	
 +.fi
 +.if n \{\
 +.RE
 +.\}
 +.sp
 +Default:
 +\fI\fIldapsam:editposix\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +ldapsam:trusted (G)
 +.\" ldapsam:trusted
 +.PP
 +.RS 4
 +By default, Samba as a Domain Controller with an LDAP backend needs to use the Unix\-style NSS subsystem to access user and group information\&. Due to the way Unix stores user information in /etc/passwd and /etc/group this inevitably leads to inefficiencies\&. One important question a user needs to know is the list of groups he is member of\&. The plain UNIX model involves a complete enumeration of the file /etc/group and its NSS counterparts in LDAP\&. UNIX has optimized functions to  [...]
 +.sp
 +To make Samba scale well in large environments, the
 +\m[blue]\fBldapsam:trusted = yes\fR\m[]
 +option assumes that the complete user and group database that is relevant to Samba is stored in LDAP with the standard posixAccount/posixGroup attributes\&. It further assumes that the Samba auxiliary object classes are stored together with the POSIX data in the same LDAP object\&. If these assumptions are met,
 +\m[blue]\fBldapsam:trusted = yes\fR\m[]
 +can be activated and Samba can bypass the NSS system to query user group memberships\&. Optimized LDAP queries can greatly speed up domain logon and administration tasks\&. Depending on the size of the LDAP database a factor of 100 or more for common queries is easily achieved\&.
 +.sp
 +Default:
 +\fI\fIldapsam:trusted\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +ldap ssl (G)
 +.\" ldap ssl
 +.PP
 +.RS 4
 +This option is used to define whether or not Samba should use SSL when connecting to the ldap server This is
 +\fINOT\fR
 +related to Samba\*(Aqs previous SSL support which was enabled by specifying the
 +\-\-with\-ssl
 +option to the
 +configure
 +script\&.
 +.sp
 +LDAP connections should be secured where possible\&. This may be done setting
 +\fIeither\fR
 +this parameter to
 +\fIStart_tls\fR\fIor\fR
 +by specifying
 +\fIldaps://\fR
 +in the URL argument of
 +\m[blue]\fBpassdb backend\fR\m[]\&.
 +.sp
 +The
 +\m[blue]\fBldap ssl\fR\m[]
 +can be set to one of two values:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIOff\fR
 += Never use SSL when querying the directory\&.
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIstart tls\fR
 += Use the LDAPv3 StartTLS extended operation (RFC2830) for communicating with the directory server\&.
 +.RE
 +.sp
 +.RE
 +Please note that this parameter does only affect
 +\fIrpc\fR
 +methods\&. To enable the LDAPv3 StartTLS extended operation (RFC2830) for
 +\fIads\fR, set
 +\m[blue]\fBldap ssl = yes\fR\m[]\fIand\fR\m[blue]\fBldap ssl ads = yes\fR\m[]\&. See
 +smb\&.conf(5)
 +for more information on
 +\m[blue]\fBldap ssl ads\fR\m[]\&.
 +.sp
 +Default:
 +\fI\fIldap ssl\fR\fR\fI = \fR\fIstart tls\fR\fI \fR
 +.RE
 +
 +ldap ssl ads (G)
 +.\" ldap ssl ads
 +.PP
 +.RS 4
 +This option is used to define whether or not Samba should use SSL when connecting to the ldap server using
 +\fIads\fR
 +methods\&. Rpc methods are not affected by this parameter\&. Please note, that this parameter won\*(Aqt have any effect if
 +\m[blue]\fBldap ssl\fR\m[]
 +is set to
 +\fIno\fR\&.
 +.sp
 +See
 +smb\&.conf(5)
 +for more information on
 +\m[blue]\fBldap ssl\fR\m[]\&.
 +.sp
 +Default:
 +\fI\fIldap ssl ads\fR\fR\fI = \fR\fIno\fR\fI \fR
 +.RE
 +
 +ldap suffix (G)
 +.\" ldap suffix
 +.PP
 +.RS 4
 +Specifies the base for all ldap suffixes and for storing the sambaDomain object\&.
 +.sp
 +The ldap suffix will be appended to the values specified for the
 +\m[blue]\fBldap user suffix\fR\m[],
 +\m[blue]\fBldap group suffix\fR\m[],
 +\m[blue]\fBldap machine suffix\fR\m[], and the
 +\m[blue]\fBldap idmap suffix\fR\m[]\&. Each of these should be given only a DN relative to the
 +\m[blue]\fBldap suffix\fR\m[]\&.
 +.sp
 +Default:
 +\fI\fIldap suffix\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIldap suffix\fR\fR\fI = \fR\fIdc=samba,dc=org\fR\fI \fR
 +.RE
 +
 +ldap timeout (G)
 +.\" ldap timeout
 +.PP
 +.RS 4
 +This parameter defines the number of seconds that Samba should use as timeout for LDAP operations\&.
 +.sp
 +Default:
 +\fI\fIldap timeout\fR\fR\fI = \fR\fI15\fR\fI \fR
 +.RE
 +
 +ldap user suffix (G)
 +.\" ldap user suffix
 +.PP
 +.RS 4
 +This parameter specifies where users are added to the tree\&. If this parameter is unset, the value of
 +\m[blue]\fBldap suffix\fR\m[]
 +will be used instead\&. The suffix string is pre\-pended to the
 +\m[blue]\fBldap suffix\fR\m[]
 +string so use a partial DN\&.
 +.sp
 +Default:
 +\fI\fIldap user suffix\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIldap user suffix\fR\fR\fI = \fR\fIou=people\fR\fI \fR
 +.RE
 +
 +level2 oplocks (S)
 +.\" level2 oplocks
 +.PP
 +.RS 4
 +This parameter controls whether Samba supports level2 (read\-only) oplocks on a share\&.
 +.sp
 +Level2, or read\-only oplocks allow Windows NT clients that have an oplock on a file to downgrade from a read\-write oplock to a read\-only oplock once a second client opens the file (instead of releasing all oplocks on a second open, as in traditional, exclusive oplocks)\&. This allows all openers of the file that support level2 oplocks to cache the file for read\-ahead only (ie\&. they may not cache writes or lock requests) and increases performance for many accesses of files that are [...]
 +.sp
 +Once one of the clients which have a read\-only oplock writes to the file all clients are notified (no reply is needed or waited for) and told to break their oplocks to "none" and delete any read\-ahead caches\&.
 +.sp
 +It is recommended that this parameter be turned on to speed access to shared executables\&.
 +.sp
 +For more discussions on level2 oplocks see the CIFS spec\&.
 +.sp
 +Currently, if
 +\m[blue]\fBkernel oplocks\fR\m[]
 +are supported then level2 oplocks are not granted (even if this parameter is set to
 +\fByes\fR)\&. Note also, the
 +\m[blue]\fBoplocks\fR\m[]
 +parameter must be set to
 +\fByes\fR
 +on this share in order for this parameter to have any effect\&.
 +.sp
 +Default:
 +\fI\fIlevel2 oplocks\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +lm announce (G)
 +.\" lm announce
 +.PP
 +.RS 4
 +This parameter determines if
 +\fBnmbd\fR(8)
 +will produce Lanman announce broadcasts that are needed by OS/2 clients in order for them to see the Samba server in their browse list\&. This parameter can have three values,
 +\fByes\fR,
 +\fBno\fR, or
 +\fBauto\fR\&. The default is
 +\fBauto\fR\&. If set to
 +\fBno\fR
 +Samba will never produce these broadcasts\&. If set to
 +\fByes\fR
 +Samba will produce Lanman announce broadcasts at a frequency set by the parameter
 +\m[blue]\fBlm interval\fR\m[]\&. If set to
 +\fBauto\fR
 +Samba will not send Lanman announce broadcasts by default but will listen for them\&. If it hears such a broadcast on the wire it will then start sending them at a frequency set by the parameter
 +\m[blue]\fBlm interval\fR\m[]\&.
 +.sp
 +Default:
 +\fI\fIlm announce\fR\fR\fI = \fR\fIauto\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIlm announce\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +lm interval (G)
 +.\" lm interval
 +.PP
 +.RS 4
 +If Samba is set to produce Lanman announce broadcasts needed by OS/2 clients (see the
 +\m[blue]\fBlm announce\fR\m[]
 +parameter) then this parameter defines the frequency in seconds with which they will be made\&. If this is set to zero then no Lanman announcements will be made despite the setting of the
 +\m[blue]\fBlm announce\fR\m[]
 +parameter\&.
 +.sp
 +Default:
 +\fI\fIlm interval\fR\fR\fI = \fR\fI60\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIlm interval\fR\fR\fI = \fR\fI120\fR\fI \fR
 +.RE
 +
 +load printers (G)
 +.\" load printers
 +.PP
 +.RS 4
 +A boolean variable that controls whether all printers in the printcap will be loaded for browsing by default\&. See the
 +\m[blue]\fBprinters\fR\m[]
 +section for more details\&.
 +.sp
 +Default:
 +\fI\fIload printers\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +local master (G)
 +.\" local master
 +.PP
 +.RS 4
 +This option allows
 +\fBnmbd\fR(8)
 +to try and become a local master browser on a subnet\&. If set to
 +\fBno\fR
 +then
 +nmbd
 +will not attempt to become a local master browser on a subnet and will also lose in all browsing elections\&. By default this value is set to
 +\fByes\fR\&. Setting this value to
 +\fByes\fR
 +doesn\*(Aqt mean that Samba will
 +\fIbecome\fR
 +the local master browser on a subnet, just that
 +nmbd
 +will
 +\fIparticipate\fR
 +in elections for local master browser\&.
 +.sp
 +Setting this value to
 +\fBno\fR
 +will cause
 +nmbd\fInever\fR
 +to become a local master browser\&.
 +.sp
 +Default:
 +\fI\fIlocal master\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +lock dir
 +.\" lock dir
 +.PP
 +.RS 4
 +This parameter is a synonym for
 +lock directory\&.
 +.RE
 +
 +lock directory (G)
 +.\" lock directory
 +.PP
 +.RS 4
 +This option specifies the directory where lock files will be placed\&. The lock files are used to implement the
 +\m[blue]\fBmax connections\fR\m[]
 +option\&.
 +.sp
 +Note: This option can not be set inside registry configurations\&.
 +.sp
 +Default:
 +\fI\fIlock directory\fR\fR\fI = \fR\fI${prefix}/var/lock\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIlock directory\fR\fR\fI = \fR\fI/var/run/samba/locks\fR\fI \fR
 +.RE
 +
 +locking (S)
 +.\" locking
 +.PP
 +.RS 4
 +This controls whether or not locking will be performed by the server in response to lock requests from the client\&.
 +.sp
 +If
 +locking = no, all lock and unlock requests will appear to succeed and all lock queries will report that the file in question is available for locking\&.
 +.sp
 +If
 +locking = yes, real locking will be performed by the server\&.
 +.sp
 +This option
 +\fImay\fR
 +be useful for read\-only filesystems which
 +\fImay\fR
 +not need locking (such as CDROM drives), although setting this parameter of
 +\fBno\fR
 +is not really recommended even in this case\&.
 +.sp
 +Be careful about disabling locking either globally or in a specific service, as lack of locking may result in data corruption\&. You should never need to set this parameter\&.
 +.sp
 +Default:
 +\fI\fIlocking\fR\fR\fI = \fR\fIyes\fR\fI \fR
 +.RE
 +
 +lock spin time (G)
 +.\" lock spin time
 +.PP
 +.RS 4
 +The time in milliseconds that smbd should keep waiting to see if a failed lock request can be granted\&. This parameter has changed in default value from Samba 3\&.0\&.23 from 10 to 200\&. The associated
 +\m[blue]\fBlock spin count\fR\m[]
 +parameter is no longer used in Samba 3\&.0\&.24\&. You should not need to change the value of this parameter\&.
 +.sp
 +Default:
 +\fI\fIlock spin time\fR\fR\fI = \fR\fI200\fR\fI \fR
 +.RE
 +
 +log file (G)
 +.\" log file
 +.PP
 +.RS 4
 +This option allows you to override the name of the Samba log file (also known as the debug file)\&.
 +.sp
 +This option takes the standard substitutions, allowing you to have separate log files for each user or machine\&.
 +.sp
 +\fINo default\fR
 +.sp
 +Example:
 +\fI\fIlog file\fR\fR\fI = \fR\fI/usr/local/samba/var/log\&.%m\fR\fI \fR
 +.RE
 +
 +logging (G)
 +.\" logging
 +.PP
 +.RS 4
 +This parameter configures logging backends\&. Multiple backends can be specified at the same time, with different log levels for each backend\&. The parameter is a list of backends, where each backend is specified as backend[:option][@loglevel]\&.
 +.sp
 +The \*(Aqoption\*(Aq parameter can be used to pass backend\-specific options\&.
 +.sp
 +The log level for a backend is optional, if it is not set for a backend, all messages are sent to this backend\&. The parameter
 +\m[blue]\fBlog level\fR\m[]
 +determines overall log levels, while the log levels specified here define what is sent to the individual backends\&.
 +.sp
 +When
 +\m[blue]\fBlogging\fR\m[]
 +is set, it overrides the
 +\m[blue]\fBsyslog\fR\m[]
 +and
 +\m[blue]\fBsyslog only\fR\m[]
 +parameters\&.
 +.sp
 +Some backends are only available when Samba has been compiled with the additional libraries\&. The overall list of logging backends:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIsyslog\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIfile\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIsystemd\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIlttng\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIgpfs\fR
 +.RE
 +.sp
 +.RE
 +Default:
 +\fI\fIlogging\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIlogging\fR\fR\fI = \fR\fIsyslog at 1 file\fR\fI \fR
 +.RE
 +
 +debuglevel
 +.\" debuglevel
 +.PP
 +.RS 4
 +This parameter is a synonym for
 +log level\&.
 +.RE
 +
 +log level (G)
 +.\" log level
 +.PP
 +.RS 4
 +The value of the parameter (a astring) allows the debug level (logging level) to be specified in the
 +smb\&.conf
 +file\&.
 +.sp
 +This parameter has been extended since the 2\&.2\&.x series, now it allows to specify the debug level for multiple debug classes\&. This is to give greater flexibility in the configuration of the system\&. The following debug classes are currently implemented:
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIall\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fItdb\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIprintdrivers\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIlanman\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIsmb\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIrpc_parse\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIrpc_srv\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIrpc_cli\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIpassdb\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIsam\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIauth\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIwinbind\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIvfs\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIidmap\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIquota\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIacls\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIlocking\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fImsdfs\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIdmapi\fR
 +.RE
 +.sp
 +.RS 4
 +.ie n \{\
 +\h'-04'\(bu\h'+03'\c
 +.\}
 +.el \{\
 +.sp -1
 +.IP \(bu 2.3
 +.\}
 +\fIregistry\fR
 +.RE
 +.sp
 +.RE
 +Default:
 +\fI\fIlog level\fR\fR\fI = \fR\fI0\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIlog level\fR\fR\fI = \fR\fI3 passdb:5 auth:10 winbind:2\fR\fI \fR
 +.RE
 +
 +log nt token command (G)
 +.\" log nt token command
 +.PP
 +.RS 4
 +This option can be set to a command that will be called when new nt tokens are created\&.
 +.sp
 +This is only useful for development purposes\&.
 +.sp
 +Default:
 +\fI\fIlog nt token command\fR\fR\fI = \fR\fI\fR\fI \fR
 +.RE
 +
 +logon drive (G)
 +.\" logon drive
 +.PP
 +.RS 4
 +This parameter specifies the local path to which the home directory will be connected (see
 +\m[blue]\fBlogon home\fR\m[]) and is only used by NT Workstations\&.
 +.sp
 +Note that this option is only useful if Samba is set up as a logon server\&.
 +.sp
 +Default:
 +\fI\fIlogon drive\fR\fR\fI = \fR\fI\fR\fI \fR
 +.sp
 +Example:
 +\fI\fIlogon drive\fR\fR\fI = \fR\fIh:\fR\fI \fR
 +.RE
 +
 +logon home (G)
 +.\" logon home
 +.PP
 +