Changeset 134 for branches/samba-3.0/docs/manpages

branches/samba-3.0/docs/manpages/eventlogadm.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "EVENTLOGADM" 8 "" "" ""
+.\"     Title: eventlogadm
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "EVENTLOGADM" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 eventlogadm - push records into the Samba event log store
 .SH "SYNOPSIS"
 .HP 1
 eventlogadm [\fB-d\fR] [\fB-h\fR] \fB-o\fR addsource \fIEVENTLOG\fR \fISOURCENAME\fR \fIMSGFILE\fR
+eventlogadm [\fB\-d\fR] [\fB\-h\fR] \fB\-o\fR\ addsource\ \fIEVENTLOG\fR\ \fISOURCENAME\fR\ \fIMSGFILE\fR
 .HP 1
 eventlogadm [\fB-d\fR] [\fB-h\fR] \fB-o\fR write \fIEVENTLOG\fR
+eventlogadm [\fB\-d\fR] [\fB\-h\fR] \fB\-o\fR\ write\ \fIEVENTLOG\fR
 .SH "DESCRIPTION"
 .PP
 This tool is part of the
 \fBsamba\fR(1)
 suite.
+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.
+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-d\fR
 .RS 3n
+\fB\-d\fR
+.RS 4
 The
 -d
+\-d
 option causes
 eventlogadm
 to emit debugging information.
 .RE
 .PP
 \fB-o\fR addsource \fIEVENTLOG\fR \fISOURCENAME\fR \fIMSGFILE\fR
 .RS 3n
+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 3n
+\-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 theSamba event log store named by EVENTLOG.
 .RE
 .PP
 \fB-h\fR
 .RS 3n
 Print usage information.
+\-o write
+reads event log records from standard input and writes them to theSamba event log store named by EVENTLOG\.
+.RE
+.PP
+\fB\-h\fR
+.RS 4
+Print usage information\.
 .RE
 .SH "EVENTLOG RECORD FORMAT"
 …
 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.
+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:
+.TP 3n
+\(bu
+.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
+\- This field should be 0, since
 eventlogadm
+will calculate this value.
+.TP 3n
+\(bu
+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.
+.TP 3n
+\(bu
+\- 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.
+.TP 3n
+\(bu
+\- 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.
+.TP 3n
+\(bu
+\- 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.
+.TP 3n
+\(bu
+\- 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.
+.TP 3n
+\(bu
+\- 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".
+.TP 3n
+\(bu
+\- 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.
+.TP 3n
+\(bu
+\- 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.
+.TP 3n
+\(bu
+\- 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.
+.TP 3n
+\(bu
+\- 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.
+.TP 3n
+\(bu
+\- 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.
+.TP 3n
+\(bu
+\- 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
+- he name of the machine on which the eventlog was generated. This is typically the host name.
+.TP 3n
+\(bu
+\- he 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.
+.TP 3n
+\(bu
+\- 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.
+\- This field should be left unset\.
 .SH "EXAMPLES"
 .PP
 An example of the record format accepted by
 eventlogadm:
+.sp
+.RS 4
 .nf
         LEN: 0
         RS1: 1699505740
 …
         TMG: 1128631322
         TMW: 1128631322
         EID: 1000
+        EID: 1000
         ETP: INFO
         ECT: 0
+        ECT: 0
         RS2: 0
         CRN: 0
 …
         SRC: cron
         SRN: dmlinux
         STR: (root) CMD ( rm -f /var/spool/cron/lastrun/cron.hourly)
         DAT:
+        STR: (root) CMD ( rm \-f /var/spool/cron/lastrun/cron\.hourly)
+        DAT:
 .fi
+.RE
 .PP
 Set up an eventlog source, specifying a message file DLL:
+.sp
+.RS 4
 .nf
+        eventlogadm -o addsource Application MyApplication | \\
+                %SystemRoot%/system32/MyApplication.dll
+        eventlogadm \-o addsource Application MyApplication | \e\e
+                %SystemRoot%/system32/MyApplication\.dll
 .fi
+.RE
 .PP
 Filter messages from the system log into an event log:
+.sp
+.RS 4
 .nf
+        tail -f /var/log/messages | \\
+                my_program_to_parse_into_eventlog_records | \\
+        tail \-f /var/log/messages | \e\e
+                my_program_to_parse_into_eventlog_records | \e\e
                 eventlogadm SystemLogEvents
 .fi
+.RE
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0.25 of the Samba suite.
+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.
+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\.

branches/samba-3.0/docs/manpages/findsmb.1

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "FINDSMB" 1 "" "" ""
+.\"     Title: findsmb
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: User Commands
+.\"    Source: Samba 3.0
+.\"
+.TH "FINDSMB" "1" "05/21/2008" "Samba 3\.0" "User Commands"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 findsmb - list info about machines that respond to SMB name queries on a subnet
 .SH "SYNOPSIS"
 .HP 1
 findsmb [subnet broadcast address]
+findsmb [subnet\ broadcast\ address]
 .SH "DESCRIPTION"
 .PP
 This perl script is part of the
 \fBsamba\fR(7)
 suite.
+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
+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.
+to obtain this information\.
 .SH "OPTIONS"
 .PP
 -r
 .RS 3n
+\-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,
+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.
+\fB\-B\fR
+option\.
 .RE
 .PP
 subnet broadcast address
 .RS 3n
+.RS 4
 Without this option,
 findsmb
 will probe the subnet of the machine where
 \fBfindsmb\fR(1)
 is run. This value is passed to
+is run\. This value is passed to
 \fBnmblookup\fR(1)
 as part of the
 \fB-B\fR
 option.
+\fB\-B\fR
+option\.
 .RE
 .SH "EXAMPLES"
 …
 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.
+for any name: IP address, NetBIOS name, Workgroup name, operating system, and SMB server version\.
 .PP
 There will be a '+' in front of the workgroup name for machines that are local master browsers for that workgroup. There will be an '*' 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.
+There will be a \'+\' in front of the workgroup name for machines that are local master browsers for that workgroup\. There will be an \'*\' 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
+\fB\-r\fR
 option must be run on a system without
 \fBnmbd\fR(8)
 running. If
+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
+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.
+running\.
 .PP
 For example, running
 findsmb
 without
 \fB-r\fR
+\fB\-r\fR
 option set would yield output similar to the following
+.sp
+.RS 4
 .nf
 IP ADDR         NETBIOS NAME   WORKGROUP/OS/VERSION
+---------------------------------------------------------------------
+.168.35.10   MINESET-TEST1  [DMVENGR]
+.168.35.55   LINUXBOX      *[MYGROUP] [Unix] [Samba 2.0.6]
+.168.35.56   HERBNT2        [HERB-NT]
+.168.35.63   GANDALF        [MVENGR] [Unix] [Samba 2.0.5a for IRIX]
+.168.35.65   SAUNA          [WORKGROUP] [Unix] [Samba 1.9.18p10]
+.168.35.71   FROGSTAR       [ENGR] [Unix] [Samba 2.0.0 for IRIX]
+.168.35.78   HERBDHCP1     +[HERB]
+.168.35.88   SCNT2         +[MVENGR] [Windows NT 4.0] [NT LAN Manager 4.0]
+.168.35.93   FROGSTAR-PC    [MVENGR] [Windows 5.0] [Windows 2000 LAN Manager]
+.168.35.97   HERBNT1       *[HERB-NT] [Windows NT 4.0] [NT LAN Manager 4.0]
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+\.168\.35\.10   MINESET\-TEST1  [DMVENGR]
+\.168\.35\.55   LINUXBOX      *[MYGROUP] [Unix] [Samba 2\.0\.6]
+\.168\.35\.56   HERBNT2        [HERB\-NT]
+\.168\.35\.63   GANDALF        [MVENGR] [Unix] [Samba 2\.0\.5a for IRIX]
+\.168\.35\.65   SAUNA          [WORKGROUP] [Unix] [Samba 1\.9\.18p10]
+\.168\.35\.71   FROGSTAR       [ENGR] [Unix] [Samba 2\.0\.0 for IRIX]
+\.168\.35\.78   HERBDHCP1     +[HERB]
+\.168\.35\.88   SCNT2         +[MVENGR] [Windows NT 4\.0] [NT LAN Manager 4\.0]
+\.168\.35\.93   FROGSTAR\-PC    [MVENGR] [Windows 5\.0] [Windows 2000 LAN Manager]
+\.168\.35\.97   HERBNT1       *[HERB\-NT] [Windows NT 4\.0] [NT LAN Manager 4\.0]
 .fi
+.RE
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 of the Samba suite\.
 .SH "SEE ALSO"
 .PP
 …
 .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.
+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.
+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\.

branches/samba-3.0/docs/manpages/libsmbclient.7

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "LIBSMBCLIENT" 7 "" "" ""
+.\"     Title: libsmbclient
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: 7
+.\"    Source: Samba 3.0
+.\"
+.TH "LIBSMBCLIENT" "7" "05/21/2008" "Samba 3\.0" "7"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 libsmbclient - An extension library for browsers and that can be used as a generic browsing API.
 …
 Browser URL:.PP
 smb://[[[domain:]user[:password@]]server[/share[/path[/file]]]] [?options]
 .SH "DESCRIPTION"
 .PP
 This tool is part of the
 \fBsamba\fR(7)
 suite.
+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's can be manipulated, and so on. Of course, its functionality includes all the capabilities commonly called browsing.
+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\'s 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.
+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
 …
 .PP
 smb://
 .RS 3n
 Shows all workgroups or domains that are visible in the network. The behavior matches that of the Microsoft Windows Explorer.
+.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 querried. If there are a large number of workgroups on the network, the time spent querying will be significant. For small networks (just a few workgroups), it is suggested to set this value to 0, instructing libsmbclient to query all local master browsers. In an environment that has many workgroups a more reasonable setting may be around 3.
+(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 querried\. If there are a large number of workgroups on the network, the time spent querying will be significant\. For small networks (just a few workgroups), it is suggested to set this value to 0, instructing libsmbclient to query all local master browsers\. In an environment that has many workgroups a more reasonable setting may be around 3\.
 .RE
 .PP
 smb://name/
 .RS 3n
 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.
+.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
 \fI.smb\fR
 in the $HOME directory that is specified in the users shell environment. It then searches for a file called
 \fIsmb.conf\fR
 which, if present, will fully over-ride the system
 \fI/etc/samba/smb.conf\fR
 file. If instead libsmbclient finds a file called
 \fI~/.smb/smb.conf.append\fR, it will read the system
 \fI/etc/samba/smb.conf\fR
+\fI\.smb\fR
+in the $HOME directory that is specified in the users shell environment\. It then searches for a file called
+\fIsmb\.conf\fR
+which, if present, will fully over\-ride the system
+\fI/etc/samba/smb\.conf\fR
+file\. If instead libsmbclient finds a file called
+\fI~/\.smb/smb\.conf\.append\fR, it will read the system
+\fI/etc/samba/smb\.conf\fR
 and then append the contents of the
 \fI~/.smb/smb.conf.append\fR
 to it.
+\fI~/\.smb/smb\.conf\.append\fR
+to it\.
 .PP
 …
 parameter and will use its value when if the
 user
 parameter was not included in the URL.
+parameter was not included in the URL\.
 .SH "PROGRAMMERS GUIDE"
 .PP
 Watch this space for future updates.
+Watch this space for future updates\.
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 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.
+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.
+The libsmbclient manpage page was written by John H Terpstra\.

branches/samba-3.0/docs/manpages/lmhosts.5

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "LMHOSTS" 5 "" "" ""
+.\"     Title: lmhosts
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: File Formats and Conventions
+.\"    Source: Samba 3.0
+.\"
+.TH "LMHOSTS" "5" "05/21/2008" "Samba 3\.0" "File Formats and Conventions"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 lmhosts - The Samba NetBIOS hosts file
 …
 is the
 \fBsamba\fR(7)
 NetBIOS name to IP address mapping file.
+NetBIOS name to IP address mapping file\.
 .SH "DESCRIPTION"
 .PP
 This file is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 \fIlmhosts\fR
 is the
 \fBSamba \fR
 NetBIOS name to IP address mapping file. It is very similar to the
+\fISamba \fR
+NetBIOS name to IP address mapping file\. It is very similar to the
 \fI/etc/hosts\fR
 file format, except that the hostname component must correspond to the NetBIOS naming format.
+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 '#' is ignored. Each line in the lmhosts file contains the following information:
+.TP 3n
+\(bu
+IP Address - in dotted decimal format.
+.TP 3n
+\(bu
+NetBIOS Name - This name format is a maximum fifteen character host name, with an optional trailing '#' character followed by the NetBIOS name type as two hexadecimal digits.
+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 \'#\' is ignored\. Each line in the lmhosts file contains the following information:
 .sp
+If the trailing '#' 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.
+.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 \'#\' character followed by the NetBIOS name type as two hexadecimal digits\.
+.sp
+If the trailing \'#\' 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\.
+.sp
+.RE
 .PP
 An example follows:
 .sp
+.RS 4
 .nf
+#
 # Sample Samba lmhosts file.
+# Sample Samba lmhosts file\.
+#
+.9.200.1     TESTPC
+.9.200.20    NTSERVER#20
+.9.200.21    SAMBASERVER
+\.9\.200\.1  TESTPC
+\.9\.200\.20 NTSERVER#20
+\.9\.200\.21 SAMBASERVER
 .fi
+.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.
+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.
+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
 …
 file is in the same directory as the
 \fBsmb.conf\fR(5)
 file.
+file\.
 .SH "FILES"
 .PP
 lmhosts is loaded from the configuration directory. This is usually
+lmhosts is loaded from the configuration directory\. This is usually
 \fI/etc/samba\fR
 or
 \fI/usr/local/samba/lib\fR.
+\fI/usr/local/samba/lib\fR\.
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 of the Samba suite\.
 .SH "SEE ALSO"
 .PP
 …
 .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.
+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.
+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\.

branches/samba-3.0/docs/manpages/log2pcap.1

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "LOG2PCAP" 1 "" "" ""
+.\"     Title: log2pcap
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: User Commands
+.\"    Source: Samba 3.0
+.\"
+.TH "LOG2PCAP" "1" "05/21/2008" "Samba 3\.0" "User Commands"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 log2pcap - Extract network traces from Samba log files
 .SH "SYNOPSIS"
 .HP 1
 log2pcap [-h] [-q] [logfile] [pcap_file]
+log2pcap [\-h] [\-q] [logfile] [pcap_file]
 .SH "DESCRIPTION"
 .PP
 This tool is part of the
 \fBsamba\fR(7)
 suite.
+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.
+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
 …
 to get the first 512 data bytes of the packet and
 \fB50\fR
 to get the whole packet.
+to get the whole packet\.
 .SH "OPTIONS"
 .PP
 -h
 .RS 3n
+\-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.
+utility\.
 .RE
 .PP
 -q
 .RS 3n
 Be quiet. No warning messages about missing or incomplete data will be given.
+\-q
+.RS 4
+Be quiet\. No warning messages about missing or incomplete data will be given\.
 .RE
 .PP
 logfile
 .RS 3n
 Samba log file. log2pcap will try to read the log from stdin if the log file is not specified.
+.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 3n
 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.
+.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
 -h|--help
 .RS 3n
 Print a summary of command line options.
+\-h|\-\-help
+.RS 4
+Print a summary of command line options\.
 .RE
 .SH "EXAMPLES"
 …
 Extract all network traffic from all samba log files:
 .PP
+.sp
+.RS 4
 .nf
+                        $ log2pcap < /var/log/* > trace.pcap
+                        $ log2pcap < /var/log/* > trace\.pcap
 .fi
+.RE
 .PP
 Convert to pcap using text2pcap:
 .PP
+.sp
+.RS 4
 .nf
+        $ log2pcap -h samba.log | text2pcap -T 139,139 - trace.pcap
+        $ log2pcap \-h samba\.log | text2pcap \-T 139,139 \- trace\.pcap
 .fi
+.RE
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 of the Samba suite\.
 .SH "BUGS"
 .PP
 Only SMB data is extracted from the samba logs, no LDAP, NetBIOS lookup or other data.
+Only SMB data is extracted from the samba logs, no LDAP, NetBIOS lookup or other data\.
 .PP
 The generated TCP and IP headers don't contain a valid checksum.
+The generated TCP and IP headers don\'t contain a valid checksum\.
 .SH "SEE ALSO"
 .PP
 …
 .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.
+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.
+This manpage was written by Jelmer Vernooij\.

branches/samba-3.0/docs/manpages/mount.cifs.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "MOUNT.CIFS" 8 "" "" ""
+.\"     Title: mount.cifs
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "MOUNT\.CIFS" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 mount.cifs - mount using the Common Internet File System (CIFS)
 .SH "SYNOPSIS"
 .HP 1
 mount.cifs {service} {mount-point} [-o options]
+mount\.cifs {service} {mount\-point} [\-o\ options]
 .SH "DESCRIPTION"
 .PP
 This tool is part of the
 \fBsamba\fR(7)
 suite.
 .PP
 mount.cifs mounts a Linux CIFS filesystem. It is usually invoked indirectly by the
+suite\.
+.PP
+mount\.cifs mounts a Linux CIFS filesystem\. It is usually invoked indirectly by the
 \fBmount\fR(8)
 command when using the "-t cifs" option. This command only works in Linux, and the kernel must support the cifs filesystem. The CIFS protocol is the successor to the SMB protocol and is supported by most Windows servers and many other commercial servers and Network Attached Storage appliances as well as by the popular Open Source server Samba.
 .PP
 The mount.cifs utility attaches the UNC name (exported network resource) to the local directory
 \fBmount-point\fR. It is possible to set the mode for mount.cifs to setuid root to allow non-root users to mount shares to directories for which they have write permission.
+command when using the "\-t cifs" option\. This command only works in Linux, and the kernel must support the cifs filesystem\. The CIFS protocol is the successor to the SMB protocol and is supported by most Windows servers and many other commercial servers and Network Attached Storage appliances as well as by the popular Open Source server Samba\.
+.PP
+The mount\.cifs utility attaches the UNC name (exported network resource) to the local directory
+\fImount\-point\fR\. It is possible to set the mode for mount\.cifs to setuid root to allow non\-root users to mount shares to directories for which they have write permission\.
 .PP
 Options to
 \fBmount.cifs\fR
 are specified as a comma-separated list of key=value pairs. It is possible to send options other than those listed here, assuming that the cifs filesystem kernel module (cifs.ko) supports them. Unrecognized cifs mount options passed to the cifs vfs kernel code will be logged to the kernel log.
 .PP
 \fBmount.cifs\fR
 causes the cifs vfs to launch a thread named cifsd. After mounting it keeps running until the mounted resource is unmounted (usually via the umount utility).
+\fImount\.cifs\fR
+are specified as a comma\-separated list of key=value pairs\. It is possible to send options other than those listed here, assuming that the cifs filesystem kernel module (cifs\.ko) supports them\. Unrecognized cifs mount options passed to the cifs vfs kernel code will be logged to the kernel log\.
+.PP
+\fImount\.cifs\fR
+causes the cifs vfs to launch a thread named cifsd\. After mounting it keeps running until the mounted resource is unmounted (usually via the umount utility)\.
 .SH "OPTIONS"
 .PP
 user=\fIarg\fR
 .RS 3n
 specifies the username to connect as. If this is not given, then the environment variable
 \fBUSER\fR
 is used. This option can also take the form "user%password" or "workgroup/user" or "workgroup/user%password" to allow the password and workgroup to be specified as part of the username.
+.RS 4
+specifies the username to connect as\. If this is not given, then the environment variable
+\fIUSER\fR
+is used\. This option can also take the form "user%password" or "workgroup/user" or "workgroup/user%password" to allow the password and workgroup to be specified as part of the username\.
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBNote\fR
+Note
 The cifs vfs accepts the parameter
 \fIuser=\fR, or for users familiar with smbfs it accepts the longer form of the parameter
 \fIusername=\fR. Similarly the longer smbfs style parameter names may be accepted as synonyms for the shorter cifs parameters
+\fIusername=\fR\. Similarly the longer smbfs style parameter names may be accepted as synonyms for the shorter cifs parameters
 \fIpass=\fR,\fIdom=\fR
 and
 \fIcred=\fR.
+\fIcred=\fR\.
 .RE
 .PP
 password=\fIarg\fR
 .RS 3n
 specifies the CIFS password. If this option is not given then the environment variable
 \fBPASSWD\fR
 is used. If the password is not specified directly or indirectly via an argument to mount
 \fBmount.cifs\fR
 will prompt for a password, unless the guest option is specified.
 .sp
 Note that a password which contains the delimiter character (i.e. a comma ',') will fail to be parsed correctly on the command line. However, the same password defined in the PASSWD environment variable or via a credentials file (see below) or entered at the password prompt will be read correctly.
+.RS 4
+specifies the CIFS password\. If this option is not given then the environment variable
+\fIPASSWD\fR
+is used\. If the password is not specified directly or indirectly via an argument to mount,
+\fImount\.cifs\fR
+will prompt for a password, unless the guest option is specified\.
+.sp
+Note that a password which contains the delimiter character (i\.e\. a comma \',\') will fail to be parsed correctly on the command line\. However, the same password defined in the PASSWD environment variable or via a credentials file (see below) or entered at the password prompt will be read correctly\.
 .RE
 .PP
 credentials=\fIfilename\fR
+.RS 3n
+specifies a file that contains a username and/or password. The format of the file is:
+.RS 4
+specifies a file that contains a username and/or password\. The format of the file is:
+.sp
+.RS 4
 .nf
                 username=\fIvalue\fR
                 password=\fIvalue\fR
 .fi
+.RE
 This is preferred over having passwords in plaintext in a shared file, such as
 \fI/etc/fstab\fR. Be sure to protect any credentials file properly.
+\fI/etc/fstab\fR\. Be sure to protect any credentials file properly\.
 .RE
 .PP
 uid=\fIarg\fR
 .RS 3n
 sets the uid that will own all files on the mounted filesystem. It may be specified as either a username or a numeric uid. This parameter is ignored when the target server supports the CIFS Unix extensions.
+.RS 4
+sets the uid that will own all files on the mounted filesystem\. It may be specified as either a username or a numeric uid\. For mounts to servers which do support the CIFS Unix extensions, such as a properly configured Samba server, the server provides the uid, gid and mode so this parameter should not be specified unless the server and client uid and gid numbering differ\. If the server and client are in the same domain (e\.g\. running winbind or nss_ldap) and the server supports the Unix Extensions then the uid and gid can be retrieved from the server (and uid and gid would not have to be specifed on the mount\. For servers which do not support the CIFS Unix extensions, the default uid (and gid) returned on lookup of existing files will be the uid (gid) of the person who executed the mount (root, except when mount\.cifs is configured setuid for user mounts) unless the "uid=" (gid) mount option is specified\. For the uid (gid) of newly created files and directories, ie files created since the last mount of the server share, the expected uid (gid) is cached as long as the inode remains in memory on the client\. Also note that permission checks (authorization checks) on accesses to a file occur at the server, but there are cases in which an administrator may want to restrict at the client as well\. For those servers which do not report a uid/gid owner (such as Windows), permissions can also be checked at the client, and a crude form of client side permission checking can be enabled by specifying file_mode and dir_mode on the client\. Note that the mount\.cifs helper must be at version 1\.10 or higher to support specifying the uid (or gid) in non\-numeric form\.
 .RE
 .PP
 gid=\fIarg\fR
 .RS 3n
 sets the gid that will own all files on the mounted filesystem. It may be specified as either a groupname or a numeric gid. This parameter is ignored when the target server supports the CIFS Unix extensions.
+.RS 4
+sets the gid that will own all files on the mounted filesystem\. It may be specified as either a groupname or a numeric gid\. For other considerations see the description of uid above\.
 .RE
 .PP
 port=\fIarg\fR
+.RS 3n
+sets the port number on the server to attempt to contact to negotiate CIFS support. If the CIFS server is not listening on this port or if it is not specified, the default ports will be tried i.e. port 445 is tried and if no response then port 139 is tried.
+.RS 4
+sets the port number on the server to attempt to contact to negotiate CIFS support\. If the CIFS server is not listening on this port or if it is not specified, the default ports will be tried i\.e\. port 445 is tried and if no response then port 139 is tried\.
+.RE
+.PP
+servern=\fIarg\fR
+.RS 4
+Specify the server netbios name (RFC1001 name) to use when attempting to setup a session to the server\. Although rarely needed for mounting to newer servers, this option is needed for mounting to some older servers (such as OS/2 or Windows 98 and Windows ME) since when connecting over port 139 they, unlike most newer servers, do not support a default server name\. A server name can be up to 15 characters long and is usually uppercased\.
 .RE
 .PP
 netbiosname=\fIarg\fR
 .RS 3n
 When mounting to servers via port 139, specifies the RFC1001 source name to use to represent the client netbios machine name when doing the RFC1001 netbios session initialize.
+.RS 4
+When mounting to servers via port 139, specifies the RFC1001 source name to use to represent the client netbios machine name when doing the RFC1001 netbios session initialize\.
 .RE
 .PP
 file_mode=\fIarg\fR
 .RS 3n
 If the server does not support the CIFS Unix extensions this overrides the default file mode.
+.RS 4
+If the server does not support the CIFS Unix extensions this overrides the default file mode\.
 .RE
 .PP
 dir_mode=\fIarg\fR
 .RS 3n
 If the server does not support the CIFS Unix extensions this overrides the default mode for directories.
+.RS 4
+If the server does not support the CIFS Unix extensions this overrides the default mode for directories\.
 .RE
 .PP
 ip=\fIarg\fR
 .RS 3n
 sets the destination host or IP address.
+.RS 4
+sets the destination IP address\. This option is set automatically if the server name portion of the requested UNC name can be resolved so rarely needs to be specified by the user\.
 .RE
 .PP
 domain=\fIarg\fR
 .RS 3n
+.RS 4
 sets the domain (workgroup) of the user
 .RE
 .PP
 guest
 .RS 3n
 don't prompt for a password
+.RS 4
+don\'t prompt for a password
 .RE
 .PP
 iocharset
 .RS 3n
 Charset used to convert local path names to and from Unicode. Unicode is used by default for network path names if the server supports it. If iocharset is not specified then the nls_default specified during the local client kernel build will be used. If server does not support Unicode, this parameter is unused.
+.RS 4
+Charset used to convert local path names to and from Unicode\. Unicode is used by default for network path names if the server supports it\. If iocharset is not specified then the nls_default specified during the local client kernel build will be used\. If server does not support Unicode, this parameter is unused\.
 .RE
 .PP
 ro
 .RS 3n
 mount read-only
+.RS 4
+mount read\-only
 .RE
 .PP
 rw
 .RS 3n
 mount read-write
+.RS 4
+mount read\-write
 .RE
 .PP
 setuids
 .RS 3n
 If the CIFS Unix extensions are negotiated with the server the client will attempt to set the effective uid and gid of the local process on newly created files, directories, and devices (create, mkdir, mknod). If the CIFS Unix Extensions are not negotiated, for newly created files and directories instead of using the default uid and gid specified on the the mount, cache the new file's uid and gid locally which means that the uid for the file can change when the inode is reloaded (or the user remounts the share).
+.RS 4
+If the CIFS Unix extensions are negotiated with the server the client will attempt to set the effective uid and gid of the local process on newly created files, directories, and devices (create, mkdir, mknod)\. If the CIFS Unix Extensions are not negotiated, for newly created files and directories instead of using the default uid and gid specified on the the mount, cache the new file\'s uid and gid locally which means that the uid for the file can change when the inode is reloaded (or the user remounts the share)\.
 .RE
 .PP
 nosetuids
 .RS 3n
 The client will not attempt to set the uid and gid on on newly created files, directories, and devices (create, mkdir, mknod) which will result in the server setting the uid and gid to the default (usually the server uid of the user who mounted the share). Letting the server (rather than the client) set the uid and gid is the default.If the CIFS Unix Extensions are not negotiated then the uid and gid for new files will appear to be the uid (gid) of the mounter or the uid (gid) parameter specified on the mount.
+.RS 4
+The client will not attempt to set the uid and gid on on newly created files, directories, and devices (create, mkdir, mknod) which will result in the server setting the uid and gid to the default (usually the server uid of the user who mounted the share)\. Letting the server (rather than the client) set the uid and gid is the default\.If the CIFS Unix Extensions are not negotiated then the uid and gid for new files will appear to be the uid (gid) of the mounter or the uid (gid) parameter specified on the mount\.
 .RE
 .PP
 perm
 .RS 3n
 Client does permission checks (vfs_permission check of uid and gid of the file against the mode and desired operation), Note that this is in addition to the normal ACL check on the target machine done by the server software. Client permission checking is enabled by default.
+.RS 4
+Client does permission checks (vfs_permission check of uid and gid of the file against the mode and desired operation), Note that this is in addition to the normal ACL check on the target machine done by the server software\. Client permission checking is enabled by default\.
 .RE
 .PP
 noperm
 .RS 3n
 Client does not do permission checks. This can expose files on this mount to access by other users on the local client system. It is typically only needed when the server supports the CIFS Unix Extensions but the UIDs/GIDs on the client and server system do not match closely enough to allow access by the user doing the mount. Note that this does not affect the normal ACL check on the target machine done by the server software (of the server ACL against the user name provided at mount time).
+.RS 4
+Client does not do permission checks\. This can expose files on this mount to access by other users on the local client system\. It is typically only needed when the server supports the CIFS Unix Extensions but the UIDs/GIDs on the client and server system do not match closely enough to allow access by the user doing the mount\. Note that this does not affect the normal ACL check on the target machine done by the server software (of the server ACL against the user name provided at mount time)\.
 .RE
 .PP
 directio
 .RS 3n
 Do not do inode data caching on files opened on this mount. This precludes mmaping files on this mount. In some cases with fast networks and little or no caching benefits on the client (e.g. when the application is doing large sequential reads bigger than page size without rereading the same data) this can provide better performance than the default behavior which caches reads (readahead) and writes (writebehind) through the local Linux client pagecache if oplock (caching token) is granted and held. Note that direct allows write operations larger than page size to be sent to the server. On some kernels this requires the cifs.ko module to be built with the CIFS_EXPERIMENTAL configure option.
+.RS 4
+Do not do inode data caching on files opened on this mount\. This precludes mmaping files on this mount\. In some cases with fast networks and little or no caching benefits on the client (e\.g\. when the application is doing large sequential reads bigger than page size without rereading the same data) this can provide better performance than the default behavior which caches reads (readahead) and writes (writebehind) through the local Linux client pagecache if oplock (caching token) is granted and held\. Note that direct allows write operations larger than page size to be sent to the server\. On some kernels this requires the cifs\.ko module to be built with the CIFS_EXPERIMENTAL configure option\.
 .RE
 .PP
 mapchars
 .RS 3n
 Translate six of the seven reserved characters (not backslash, but including the colon, question mark, pipe, asterik, greater than and less than characters) to the remap range (above 0xF000), which also allows the CIFS client to recognize files created with such characters by Windows's POSIX emulation. This can also be useful when mounting to most versions of Samba (which also forbids creating and opening files whose names contain any of these seven characters). This has no effect if the server does not support Unicode on the wire.
+.RS 4
+Translate six of the seven reserved characters (not backslash, but including the colon, question mark, pipe, asterik, greater than and less than characters) to the remap range (above 0xF000), which also allows the CIFS client to recognize files created with such characters by Windows\'s POSIX emulation\. This can also be useful when mounting to most versions of Samba (which also forbids creating and opening files whose names contain any of these seven characters)\. This has no effect if the server does not support Unicode on the wire\.
 .RE
 .PP
 nomapchars
 .RS 3n
+.RS 4
 Do not translate any of these seven characters (default)
 .RE
 .PP
 intr
 .RS 3n
+.RS 4
 currently unimplemented
 .RE
 .PP
 nointr
 .RS 3n
+.RS 4
 (default) currently unimplemented
 .RE
 .PP
 hard
 .RS 3n
 The program accessing a file on the cifs mounted file system will hang when the server crashes.
+.RS 4
+The program accessing a file on the cifs mounted file system will hang when the server crashes\.
 .RE
 .PP
 soft
 .RS 3n
 (default) The program accessing a file on the cifs mounted file system will not hang when the server crashes and will return errors to the user application.
+.RS 4
+(default) The program accessing a file on the cifs mounted file system will not hang when the server crashes and will return errors to the user application\.
 .RE
 .PP
 noacl
 .RS 3n
 Do not allow POSIX ACL operations even if server would support them.
 .sp
 The CIFS client can get and set POSIX ACLs (getfacl, setfacl) to Samba servers version 3.10 and later. Setting POSIX ACLs requires enabling both XATTR and then POSIX support in the CIFS configuration options when building the cifs module. POSIX ACL support can be disabled on a per mount basic by specifying "noacl" on mount.
+.RS 4
+Do not allow POSIX ACL operations even if server would support them\.
+.sp
+The CIFS client can get and set POSIX ACLs (getfacl, setfacl) to Samba servers version 3\.10 and later\. Setting POSIX ACLs requires enabling both XATTR and then POSIX support in the CIFS configuration options when building the cifs module\. POSIX ACL support can be disabled on a per mount basic by specifying "noacl" on mount\.
 .RE
 .PP
 nocase
 .RS 3n
 Request case insensitive path name matching (case sensitive is the default if the server suports it).
+.RS 4
+Request case insensitive path name matching (case sensitive is the default if the server suports it)\.
 .RE
 .PP
 sec=
+.RS 3n
+Security mode. Allowed values are:
+.RS 3n
+.TP 3n
+\(bu
+.RS 4
+Security mode\. Allowed values are:
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 none attempt to connection as a null user (no name)
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 krb5 Use Kerberos version 5 authentication
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 krb5i Use Kerberos authentication and packet signing
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 ntlm Use NTLM password hashing (default)
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 ntlmi Use NTLM password hashing with signing (if /proc/fs/cifs/PacketSigningEnabled on or if server requires signing also can be the default)
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 ntlmv2 Use NTLMv2 password hashing
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 ntlmv2i Use NTLMv2 password hashing with packet signing
 .RE
 .IP "" 3n
 [NB This [sec parameter] is under development and expected to be available in cifs kernel module 1.40 and later]
+.sp
+.RE
+[NB This [sec parameter] is under development and expected to be available in cifs kernel module 1\.40 and later]
 .RE
 .PP
 nobrl
 .RS 3n
 Do not send byte range lock requests to the server. This is necessary for certain applications that break with cifs style mandatory byte range locks (and most cifs servers do not yet support requesting advisory byte range locks).
+.RS 4
+Do not send byte range lock requests to the server\. This is necessary for certain applications that break with cifs style mandatory byte range locks (and most cifs servers do not yet support requesting advisory byte range locks)\.
 .RE
 .PP
 sfu
 .RS 3n
 When the CIFS Unix Extensions are not negotiated, attempt to create device files and fifos in a format compatible with Services for Unix (SFU). In addition retrieve bits 10-12 of the mode via the SETFILEBITS extended attribute (as SFU does). In the future the bottom 9 bits of the mode mode also will be emulated using queries of the security descriptor (ACL). [NB: requires version 1.39 or later of the CIFS VFS. To recognize symlinks and be able to create symlinks in an SFU interoperable form requires version 1.40 or later of the CIFS VFS kernel module.
+.RS 4
+When the CIFS Unix Extensions are not negotiated, attempt to create device files and fifos in a format compatible with Services for Unix (SFU)\. In addition retrieve bits 10\-12 of the mode via the SETFILEBITS extended attribute (as SFU does)\. In the future the bottom 9 bits of the mode mode also will be emulated using queries of the security descriptor (ACL)\. [NB: requires version 1\.39 or later of the CIFS VFS\. To recognize symlinks and be able to create symlinks in an SFU interoperable form requires version 1\.40 or later of the CIFS VFS kernel module\.
 .RE
 .PP
 serverino
 .RS 3n
 Use inode numbers (unique persistent file identifiers) returned by the server instead of automatically generating temporary inode numbers on the client. Although server inode numbers make it easier to spot hardlinked files (as they will have the same inode numbers) and inode numbers may be persistent (which is userful for some sofware), the server does not guarantee that the inode numbers are unique if multiple server side mounts are exported under a single share (since inode numbers on the servers might not be unique if multiple filesystems are mounted under the same shared higher level directory). Note that not all servers support returning server inode numbers, although those that support the CIFS Unix Extensions, and Windows 2000 and later servers typically do support this (although not necessarily on every local server filesystem). Parameter has no effect if the server lacks support for returning inode numbers or equivalent.
+.RS 4
+Use inode numbers (unique persistent file identifiers) returned by the server instead of automatically generating temporary inode numbers on the client\. Although server inode numbers make it easier to spot hardlinked files (as they will have the same inode numbers) and inode numbers may be persistent (which is userful for some sofware), the server does not guarantee that the inode numbers are unique if multiple server side mounts are exported under a single share (since inode numbers on the servers might not be unique if multiple filesystems are mounted under the same shared higher level directory)\. Note that not all servers support returning server inode numbers, although those that support the CIFS Unix Extensions, and Windows 2000 and later servers typically do support this (although not necessarily on every local server filesystem)\. Parameter has no effect if the server lacks support for returning inode numbers or equivalent\.
 .RE
 .PP
 noserverino
 .RS 3n
 client generates inode numbers (rather than using the actual one from the server) by default.
+.RS 4
+client generates inode numbers (rather than using the actual one from the server) by default\.
 .RE
 .PP
 nouser_xattr
 .RS 3n
 (default) Do not allow getfattr/setfattr to get/set xattrs, even if server would support it otherwise.
+.RS 4
+(default) Do not allow getfattr/setfattr to get/set xattrs, even if server would support it otherwise\.
 .RE
 .PP
 rsize=\fIarg\fR
 .RS 3n
 default network read size
+.RS 4
+default network read size (usually 16K)\. The client currently can not use rsize larger than CIFSMaxBufSize\. CIFSMaxBufSize defaults to 16K and may be changed (from 8K to the maximum kmalloc size allowed by your kernel) at module install time for cifs\.ko\. Setting CIFSMaxBufSize to a very large value will cause cifs to use more memory and may reduce performance in some cases\. To use rsize greater than 127K (the original cifs protocol maximum) also requires that the server support a new Unix Capability flag (for very large read) which some newer servers (e\.g\. Samba 3\.0\.26 or later) do\. rsize can be set from a minimum of 2048 to a maximum of 130048 (127K or CIFSMaxBufSize, whichever is smaller)
 .RE
 .PP
 wsize=\fIarg\fR
+.RS 3n
+default network write size
+.RE
+.PP
+--verbose
+.RS 3n
+Print additional debugging information for the mount. Note that this parameter must be specified before the -o. For example:
+.sp
+mount -t cifs //server/share /mnt --verbose -o user=username
+.RE
+.RS 4
+default network write size (default 57344) maximum wsize currently allowed by CIFS is 57344 (fourteen 4096 byte pages)
+.RE
+.PP
+\-\-verbose
+.RS 4
+Print additional debugging information for the mount\. Note that this parameter must be specified before the \-o\. For example:
+.sp
+mount \-t cifs //server/share /mnt \-\-verbose \-o user=username
+.RE
+.SH "SERVICE FORMATTING AND DELIMITERS"
+.PP
+It\'s generally preferred to use forward slashes (/) as a delimiter in service names\. They are considered to be the "universal delimiter" since they are generally not allowed to be embedded within path components on Windows machines and the client can convert them to blackslashes (\e) unconditionally\. Conversely, backslash characters are allowed by POSIX to be part of a path component, and can\'t be automatically converted in the same way\.
+.PP
+mount\.cifs will attempt to convert backslashes to forward slashes where it\'s able to do so, but it cannot do so in any path component following the sharename\.
 .SH "ENVIRONMENT VARIABLES"
 .PP
 The variable
 \fBUSER\fR
 may contain the username of the person to be used to authenticate to the server. The variable can be used to set both username and password by using the format username%password.
+\fIUSER\fR
+may contain the username of the person to be used to authenticate to the server\. The variable can be used to set both username and password by using the format username%password\.
 .PP
 The variable
 \fBPASSWD\fR
 may contain the password of the person using the client.
+\fIPASSWD\fR
+may contain the password of the person using the client\.
 .PP
 The variable
 \fBPASSWD_FILE\fR
 may contain the pathname of a file to read the password from. A single line of input is read and used as the password.
+\fIPASSWD_FILE\fR
+may contain the pathname of a file to read the password from\. A single line of input is read and used as the password\.
 .SH "NOTES"
 .PP
 This command may be used only by root, unless installed setuid, in which case the noeexec and nosuid mount flags are enabled.
+This command may be used only by root, unless installed setuid, in which case the noeexec and nosuid mount flags are enabled\.
 .SH "CONFIGURATION"
 .PP
 The primary mechanism for making configuration changes and for reading debug information for the cifs vfs is via the Linux /proc filesystem. In the directory
+The primary mechanism for making configuration changes and for reading debug information for the cifs vfs is via the Linux /proc filesystem\. In the directory
 \fI/proc/fs/cifs\fR
 are various configuration files and pseudo files which can display debug information. There are additional startup options such as maximum buffer size and number of buffers which only may be set when the kernel cifs vfs (cifs.ko module) is loaded. These can be seen by running the modinfo utility against the file cifs.ko which will list the options that may be passed to cifs during module installation (device driver load). For more information see the kernel file
 \fIfs/cifs/README\fR.
+are various configuration files and pseudo files which can display debug information\. There are additional startup options such as maximum buffer size and number of buffers which only may be set when the kernel cifs vfs (cifs\.ko module) is loaded\. These can be seen by running the modinfo utility against the file cifs\.ko which will list the options that may be passed to cifs during module installation (device driver load)\. For more information see the kernel file
+\fIfs/cifs/README\fR\.
 .SH "BUGS"
 .PP
 Mounting using the CIFS URL specification is currently not supported.
 .PP
 The credentials file does not handle usernames or passwords with leading space.
 .PP
 Note that the typical response to a bug report is a suggestion to try the latest version first. So please try doing that first, and always include which versions you use of relevant software when reporting bugs (minimum: mount.cifs (try mount.cifs -V), kernel (see /proc/version) and server type you are trying to contact.
+Mounting using the CIFS URL specification is currently not supported\.
+.PP
+The credentials file does not handle usernames or passwords with leading space\.
+.PP
+Note that the typical response to a bug report is a suggestion to try the latest version first\. So please try doing that first, and always include which versions you use of relevant software when reporting bugs (minimum: mount\.cifs (try mount\.cifs \-V), kernel (see /proc/version) and server type you are trying to contact\.
 .SH "VERSION"
 .PP
 This man page is correct for version 1.39 of the cifs vfs filesystem (roughly Linux kernel 2.6.15).
+This man page is correct for version 1\.52 of the cifs vfs filesystem (roughly Linux kernel 2\.6\.24)\.
 .SH "SEE ALSO"
 .PP
 Documentation/filesystems/cifs.txt and fs/cifs/README in the linux kernel source tree may contain additional options and information.
+Documentation/filesystems/cifs\.txt and fs/cifs/README in the linux kernel source tree may contain additional options and information\.
 .PP
 \fBumount.cifs\fR(8)
 …
 Steve French
 .PP
 The syntax and manpage were loosely based on that of smbmount. It was converted to Docbook/XML by Jelmer Vernooij.
+The syntax and manpage were loosely based on that of smbmount\. It was converted to Docbook/XML by Jelmer Vernooij\.
 .PP
 The maintainer of the Linux cifs vfs and the userspace tool
 \fBmount.cifs\fR
+\fImount\.cifs\fR
 is
 Steve French. The
+Steve French\. The
 Linux CIFS Mailing list
+is the preferred place to ask questions regarding these programs.
+is the preferred place to ask questions regarding these programs\.

branches/samba-3.0/docs/manpages/net.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "NET" 8 "" "" ""
+.\"     Title: net
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "NET" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 net - Tool for administration of Samba and remote CIFS servers.
 .SH "SYNOPSIS"
 .HP 1
 net {<ads|rap|rpc>} [-h] [-w workgroup] [-W myworkgroup] [-U user] [-I ip-address] [-p port] [-n myname] [-s conffile] [-S server] [-l] [-P] [-d debuglevel] [-V]
+net {<ads|rap|rpc>} [\-h] [\-w\ workgroup] [\-W\ myworkgroup] [\-U\ user] [\-I\ ip\-address] [\-p\ port] [\-n\ myname] [\-s\ conffile] [\-S\ server] [\-l] [\-P] [\-d\ debuglevel] [\-V]
 .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.
+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
 -h|--help
 .RS 3n
 Print a summary of command line options.
 .RE
 .PP
 -w target-workgroup
 .RS 3n
 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 workgroup
 .RS 3n
+\-h|\-\-help
+.RS 4
+Print a summary of command line options\.
+.RE
+.PP
+\-w 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 workgroup
+.RS 4
 Sets client workgroup or domain
 .RE
 .PP
 -U user
 .RS 3n
+\-U user
+.RS 4
 User name to use
 .RE
 .PP
 -I ip-address
 .RS 3n
 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
 .RS 3n
 Port on the target server to connect to (usually 139 or 445). Defaults to trying 445 first, then 139.
 .RE
 .PP
 -n <primary NetBIOS name>
 .RS 3n
 This option allows you to override the NetBIOS name that Samba uses for itself. This is identical to setting the
+\-I 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
+.RS 4
+Port on the target server to connect to (usually 139 or 445)\. Defaults to trying 445 first, then 139\.
+.RE
+.PP
+\-n <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
+\fInetbios name\fR
 parameter in the
 \fIsmb.conf\fR
 file. However, a command line setting will take precedence over settings in
 \fIsmb.conf\fR.
 .RE
 .PP
 -s <configuration file>
 .RS 3n
 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
 \fIsmb.conf\fR
 for more information. The default configuration file name is determined at compile time.
 .RE
 .PP
 -S server
 .RS 3n
 Name of target server. You should specify either this option or a target workgroup or a target IP address.
 .RE
 .PP
 -l
 .RS 3n
 When listing data, give more information on each item.
 .RE
 .PP
 -P
 .RS 3n
 Make queries to the external server using the machine account of the local server.
 .RE
 .PP
 -d|--debuglevel=level
 .RS 3n
+\fIsmb\.conf\fR
+file\. However, a command line setting will take precedence over settings in
+\fIsmb\.conf\fR\.
+.RE
+.PP
+\-s <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
+\fIsmb\.conf\fR
+for more information\. The default configuration file name is determined at compile time\.
+.RE
+.PP
+\-S 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
+.RS 4
+When listing data, give more information on each item\.
+.RE
+.PP
+\-P
+.RS 4
+Make queries to the external server using the machine account of the local 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 zero.
 .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.
+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
+\fIlog level\fR
 parameter in the
 \fIsmb.conf\fR
 file.
+\fIsmb\.conf\fR
+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 password. Do NOT use this without care and attention as it will overwrite a legitimate machine password without warning. YOU HAVE BEEN WARNED.
+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 password\. Do NOT use this without care and attention as it will overwrite a legitimate machine password without warning\. YOU HAVE BEEN WARNED\.
 .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.
+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.
+command displays the time on the remote server\.
 .SS "TIME SYSTEM"
 .PP
 Displays the time on the remote server in a format ready for
+/bin/date
+/bin/date\.
 .SS "TIME SET"
 .PP
 Tries to set the date and time of the local server to that on the remote server using
+/bin/date.
+/bin/date\.
 .SS "TIME ZONE"
 .PP
 Displays the timezone in hours from GMT on the remote computer.
 .SS "[RPC|ADS] JOIN [TYPE] [-U username[%password]] [createupn=UPN] [createcomputer=OU] [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@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 '/'. Please note that '\' 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.
+Displays the timezone in hours from GMT on the remote computer\.
+.SS "[RPC|ADS] JOIN [TYPE] [\-U username[%password]] [createupn=UPN] [createcomputer=OU] [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@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 \'/\'\. Please note that \'\e\' 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\.
 .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.
+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 a the specified user.
+List the domain groups of the specified user\.
 .SS "[RPC|ADS] USER RENAME oldname newname"
 .PP
+Rename specified user.
+Rename specified user\.
 .SS "[RPC|ADS] USER ADD name [password] [-F user flags] [-C comment]"
 .PP
 Add specified user.
+Add specified user\.
 .SS "[RPC|ADS] GROUP"
 .SS "[RPC|ADS] GROUP [misc options] [targets]"
 .PP
+List user groups.
+List user groups\.
 .SS "[RPC|ADS] GROUP DELETE name [misc. options]"
 .PP
+Delete specified group.
+Delete specified group\.
 .SS "[RPC|ADS] GROUP ADD name [-C comment]"
 .PP
 Create specified group.
+Create specified group\.
 .SS "[RAP|RPC] SHARE"
 .SS "[RAP|RPC] SHARE [misc. options] [targets]"
 .PP
+Enumerates all exported resources (network shares) on target server.
+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 sharenam"
+.PP
+Delete specified share.
+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.
+List all open files on remote server\.
 .SS "[RPC|RAP] FILE CLOSE fileid"
 .PP
 Close file with specified
 \fIfileid\fR
+on remote server.
+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"
+\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 LIST 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\.
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBNote\fR
+.PP
+Currently NOT implemented.
+.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 LIST 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.
+Note
+.PP
+Currently NOT implemented\.
+.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\.
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBNote\fR
+.PP
+Currently NOT implemented.
+.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.
+Note
+.PP
+Currently NOT implemented\.
+.SS "RAP SERVICE"
+.SS "RAP SERVICE START NAME [arguments...]"
+.PP
+Start the specified service on the remote server\. Not implemented yet\.
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBNote\fR
+.PP
+Currently NOT implemented.
+.SS "RAP SERVICE"
+Note
+.PP
+Currently NOT implemented\.
 .SS "RAP SERVICE START NAME [arguments...]"
 .PP
 Start the specified service on the remote server. Not implemented yet.
+.SS "RAP SERVICE STOP"
+.PP
+Stop the specified service on the remote server\.
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBNote\fR
+.PP
+Currently NOT implemented.
+.SS "RAP SERVICE STOP"
+.PP
+Stop the specified service on the remote server.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+.PP
+Currently NOT implemented.
+Note
+.PP
+Currently NOT implemented\.
 .SS "RAP PASSWORD \fIUSER\fR \fIOLDPASS\fR \fINEWPASS\fR"
 .PP
 …
 \fIOLDPASS\fR
 to
 \fINEWPASS\fR.
+\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"
+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.
+\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.
+\fIREALM\fR\. Defaults to local realm\.
 .SS "LOOKUP DC [DOMAIN]"
 .PP
+Give IP's of Domain Controllers for specified
+\fI DOMAIN\fR. Defaults to local domain.
+Give IP\'s 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.
+or workgroup\. Defaults to local domain\.
 .SS "CACHE"
 .PP
 Samba uses a general caching interface called 'gencache'. It can be controlled using 'NET CACHE'.
+Samba uses a general caching interface called \'gencache\'\. It can be controlled using \'NET CACHE\'\.
 .PP
 All the timeout parameters support the suffixes:
+.IP "" 3n
+s - Seconds
+.IP "" 3n
+m - Minutes
+.IP "" 3n
+h - Hours
+.IP "" 3n
+d - Days
+.IP "" 3n
+w - Weeks
+.IP "" 4
+s \- Seconds
+.IP "" 4
+m \- Minutes
+.IP "" 4
+h \- Hours
+.IP "" 4
+d \- Days
+.IP "" 4
+w \- Weeks
 .SS "CACHE ADD key data time-out"
 .PP
+Add specified key+data to the cache with the given timeout.
+Add specified key+data to the cache with the given timeout\.
 .SS "CACHE DEL key"
 .PP
+Delete key from the cache.
+Delete key from the cache\.
 .SS "CACHE SET key data time-out"
 .PP
+Update data of existing cache entry.
+Update data of existing cache entry\.
 .SS "CACHE SEARCH PATTERN"
 .PP
+Search for the specified pattern in the cache data.
+Search for the specified pattern in the cache data\.
 .SS "CACHE LIST"
 .PP
+List all current items in the cache.
+List all current items in the cache\.
 .SS "CACHE FLUSH"
 .PP
 Remove all the current items from the cache.
+Remove all the current items from the cache\.
 .SS "GETLOCALSID [DOMAIN]"
 .PP
+Print the SID of the specified domain, or if the parameter is omitted, the SID of the domain the local server is in.
+.SS "SETLOCALSID S-1-5-21-x-y-z"
+.PP
+Sets domain sid for the local server to the specified SID.
+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. Parameters take the for "parameter=value". Common options include:
+.TP 3n
+\(bu
+unixgroup - Name of the UNIX group
+.TP 3n
+\(bu
+ntgroup - Name of the Windows NT group (must be resolvable to a SID
+.TP 3n
+\(bu
+rid - Unsigned 32-bit integer
+.TP 3n
+\(bu
+sid - Full SID in the form of "S-1-..."
+.TP 3n
+\(bu
+type - Type of the group; either 'domain', 'local', or 'builtin'
+.TP 3n
+\(bu
+comment - Freeform text description of the group
+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 \'domain\', \'local\', or \'builtin\'
+.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
+.sp
+.RE
 .SS "GROUPMAP ADD"
 .PP
 Add a new group mapping entry:
+.sp
+.sp
+.RS 4
 .nf
+net groupmap add {rid=int|sid=string} unixgroup=string \
+      [type={domain|local}] [ntgroup=string] [comment=string]
+net groupmap add {rid=int|sid=string} unixgroup=string \e
+        [type={domain|local}] [ntgroup=string] [comment=string]
 .fi
+.RE
+.sp
 .SS "GROUPMAP DELETE"
 .PP
 Delete a group mapping entry. If more then one group name matches, the first entry found is deleted.
+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 en existing group entry\.
+.PP
+.SS "GROUPMAP MODIFY"
+.PP
+Update en existing group entry
+.PP
+.sp
+.sp
+.RS 4
 .nf
+net groupmap modify {ntgroup=string|sid=SID} [unixgroup=string] \
+net groupmap modify {ntgroup=string|sid=SID} [unixgroup=string] \e
        [comment=string] [type={domain|local}]
 .fi
+.RE
+.sp
 .SS "GROUPMAP LIST"
 .PP
 List existing group mapping entries
+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 'passdb backend').
+Prints out the highest RID currently in use on the local server (by the active \'passdb backend\')\.
 .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.
+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.
+Check whether participation in a domain is still valid\.
 .SS "[RPC|ADS] CHANGETRUSTPW"
 .PP
 Force change of domain trust password.
+Force change of domain trust password\.
 .SS "RPC TRUSTDOM"
 .SS "RPC TRUSTDOM ADD DOMAIN"
 .PP
 Add a interdomain trust account for
+\fIDOMAIN\fR
+to the remote server.
+.SS "RPC TRUSTDOM DEL DOMAIM"
+\fIDOMAIN\fR\. This is in fact a Samba account named
+\fIDOMAIN$\fR
+with the account flag
+\fB\'I\'\fR
+(interdomain trust account)\. 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
+from the remote server.
+.sp
+.it 1 an-trap
+.nr an-no-space-flag 1
+.nr an-break-flag 1
+.br
+\fBNote\fR
+.PP
+Currently NOT implemented.
+\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 trusting domain. Interdomain account must already be created on the remote PDC.
+Establish a trust relationship to a trusting domain\. Interdomain account must already be created on the remote PDC\.
 .SS "RPC TRUSTDOM REVOKE DOMAIN"
 .PP
 Abandon relationship to trusted domain
 .SS "RPC TRUSTDOM LIST"
 .PP
+List all current interdomain trust relationships.
+List all current interdomain trust relationships\.
 .SS "RPC RIGHTS"
 .PP
 This subcommand is used to view and manage Samba's rights assignments (also referred to as privileges). There are three options current available:
+This subcommand is used to view and manage Samba\'s rights assignments (also referred to as privileges)\. There are three options currently available:
 \fIlist\fR,
 \fIgrant\fR, and
 \fIrevoke\fR. More details on Samba's privilege model and its use can be found in the Samba-HOWTO-Collection.
+\fIrevoke\fR\. More details on Samba\'s 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 3n
+Reboot after shutdown.
+.RE
+.PP
+-f
+.RS 3n
+Force shutting down all applications.
+.RE
+.PP
+-t timeout
+.RS 3n
+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 3n
+Display the specified message on the screen to announce the shutdown.
+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.
+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.
+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\.
 .SS "RPC GETSID"
 .PP
 Fetch domain SID and store it in the local
 \fIsecrets.tdb\fR.
+\fIsecrets\.tdb\fR\.
 .SS "ADS LEAVE"
 .PP
 Make the remote host leave the domain it is part of.
+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.
+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
 …
 \fIPRINTER\fR
 on
+\fISERVER\fR. The printer name defaults to "*", the server name defaults to the local host.
+\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.
+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.
+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 '(objectCategory=group)' sAMAccountName\fR
+\fBnet ads search \'(objectCategory=group)\' 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.
+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 'CN=administrator,CN=Users,DC=my,DC=domain' SAMAccountName\fR
+\fBnet ads dn \'CN=administrator,CN=Users,DC=my,DC=domain\' SAMAccountName\fR
 .SS "ADS WORKGROUP"
 .PP
 Print out workgroup name for specified kerberos realm.
+Print out workgroup name for specified kerberos realm\.
 .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 ompatible Access. This command requires a running Winbindd with idmap allocation properly configured. The group gid will be allocated out of the winbindd range.
+(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.
+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).
+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.
+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.
+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.
+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.
+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.
+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.
+List the specified set of accounts by name\. If verbose is specified, the rid and description is also provided for each account\.
 .SS "SAM SHOW <NAME>"
 .PP
 Show the full DOMAIN\\NAME the SID and the type for the corrisponding account.
+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.
+Set the home directory for a user account\.
 .SS "SAM SET PROFILEPATH <NAME> <PATH>"
 .PP
 Set the profile path for a user account.
+Set the profile path for a user account\.
 .SS "SAM SET COMMENT <NAME> <COMMENT>"
 .PP
 Set the comment for a user or group account.
+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.
+Set the full name for a user account\.
 .SS "SAM SET LOGONSCRIPT <NAME> <SCRIPT>"
 .PP
 Set the logon script for a user account.
+Set the logon script for a user account\.
 .SS "SAM SET HOMEDRIVE <NAME> <DRIVE>"
 .PP
 Set the home drive for a user account.
+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.
+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.
+Set the "disabled" flag for a user account\.
 .SS "SAM SET PWNOTREQ <NAME>"
 .PP
 Set the "password not required" flag for a user account.
+Set the "password not required" flag for a user account\.
 .SS "SAM SET AUTOLOCK <NAME>"
 .PP
 Set the "autolock" flag for a user account.
+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 PWMUSTCHANGENOW <NAME> [yes|no]"
 .PP
 Set or unset the "password must change" flag fro a user account.
+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 avilable account policies.
+List the available account policies\.
 .SS "SAM POLICY SHOW <account policy>"
 .PP
 Show the account policy value.
+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.
+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 <output file>"
 .PP
 Dumps the mappings in the specified output file.
+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.
+Restore the mappings from the specified file or stdin\.
 .SS "IDMAP SECRET <DOMAIN>|ALLOC <secret>"
 .PP
 Store a secret for the sepcified 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.
+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 "USERSHARE"
 .PP
 Starting with version 3.0.23, a Samba server now supports the ability for non-root users to add user define 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 means that a file in that directory can be renamed or deleted only by the owner of the file). Finally, tell smbd how many usershares you will allow by adding to the [global] section of smb.conf a line such as : usershare max shares = 100. To allow 100 usershare definitions. Now, members of the UNIX group "serverops" can create user defined shares on demand using the commands below.
+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 means that a file in that directory can be renamed or deleted only by the owner of the file)\. Finally, tell smbd how many usershares you will allow by adding to the [global] section of smb\.conf a line such as : usershare max shares = 100\. To allow 100 usershare definitions\. Now, members of the UNIX group "serverops" can create user defined shares on demand using the commands below\.
 .PP
 The usershare commands are:
+.IP "" 3n
+net usershare add sharename path [comment] [acl] [guest_ok=[y|n]] - to add or change a user defined share.
+.IP "" 3n
+net usershare delete sharename - to delete a user defined share.
+.IP "" 3n
+net usershare info [-l|--long] [wildcard sharename] - to print info about a user defined share.
+.IP "" 3n
+net usershare list [-l|--long] [wildcard sharename] - to list user defined shares.
+.IP "" 4
+net usershare add sharename path [comment] [acl] [guest_ok=[y|n]] \- to add or change a user defined share\.
+.IP "" 4
+net usershare delete sharename \- to delete a user defined share\.
+.IP "" 4
+net usershare info [\-l|\-\-long] [wildcard sharename] \- to print info about a user defined share\.
+.IP "" 4
+net usershare list [\-l|\-\-long] [wildcard sharename] \- to list user defined shares\.
 .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 user from accessing this share. "R" stands for "read only", ie. only allow read access to this share (no creation of new files or directories or writing to files).
 .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.
+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 user from accessing this share\. "R" stands for "read only", ie\. only allow read access to this share (no creation of new files or directories or writing to files)\.
+.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\.
 …
 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
+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.
+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.
+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 ('*' matches one or more characters, '?' matches only one character). If the '-l' or '--long' 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.
+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 (\'*\' matches one or more characters, \'?\' matches only one character)\. If the \'\-l\' or \'\-\-long\' 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 ('*' matches one or more characters, '?' matches only one character). If the '-l' or '--long' option is also given, it includes the names of user defined shares created by other users.
+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 (\'*\' matches one or more characters, \'?\' matches only one character)\. If the \'\-l\' or \'\-\-long\' option is also given, it includes the names of user defined shares created by other users\.
 .SS "HELP [COMMAND]"
 .PP
 Gives usage information for the specified command.
+Gives usage information for the specified command\.
 .SH "VERSION"
 .PP
 This man page is complete for version 3.0 of the Samba suite.
+This man page is complete for version 3\.0 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.
+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\.

branches/samba-3.0/docs/manpages/nmbd.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "NMBD" 8 "" "" ""
+.\"     Title: nmbd
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "NMBD" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 nmbd - NetBIOS name server to provide NetBIOS over IP naming services to clients
 .SH "SYNOPSIS"
 .HP 1
 nmbd [-D] [-F] [-S] [-a] [-i] [-o] [-h] [-V] [-d <debug level>] [-H <lmhosts file>] [-l <log directory>] [-p <port number>] [-s <configuration file>]
+nmbd [\-D] [\-F] [\-S] [\-a] [\-i] [\-o] [\-h] [\-V] [\-d\ <debug\ level>] [\-H\ <lmhosts\ file>] [\-l\ <log\ directory>] [\-p\ <port\ number>] [\-s\ <configuration\ file>]
 .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.
+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
+netbios name in
+\fIsmb.conf\fR. Thus
+nmbd
+will reply to broadcast queries for its own name(s). Additional names for
+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
+\fInetbios name\fR
+in
+\fIsmb\.conf\fR\. 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.
+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.
+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
 .RS 3n
+\-D
+.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
+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
 .RS 3n
+meta\-daemon, although this is not recommended\.
+.RE
+.PP
+\-F
+.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
+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
 …
 and
 svscan
 from Daniel J. Bernstein's
+from Daniel J\. Bernstein\'s
 daemontools
 package, or the AIX process monitor.
 .RE
 .PP
 -S
 .RS 3n
+package, or the AIX process monitor\.
+.RE
+.PP
+\-S
+.RS 4
 If specified, this parameter causes
 nmbd
 to log to standard output rather than a file.
 .RE
 .PP
 -i
 .RS 3n
 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.
+to log to standard output rather than a file\.
+.RE
+.PP
+\-i
+.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
+-h|--help
+.RS 3n
+Print a summary of command line options.
+.RE
+.PP
+-H <filename>
+.RS 3n
+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
+name resolve order described in
+\fBsmb.conf\fR(5)
+to resolve any NetBIOS name queries needed by the server. Note that the contents of this file are
+\fBNOT\fR
+\fB\-S\fR
+parameter had been given\.
+.RE
+.PP
+\-h|\-\-help
+.RS 4
+Print a summary of command line options\.
+.RE
+.PP
+\-H <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
+\fIname resolve order\fR
+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
 \fBONLY\fR.
 .sp
 The default path to this file is compiled into Samba as part of the build process. Common defaults are
+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
 \fI/usr/local/samba/lib/lmhosts\fR,
 \fI/usr/samba/lib/lmhosts\fR
 or
 \fI/etc/samba/lmhosts\fR. See the
+\fI/etc/samba/lmhosts\fR\. See the
 \fBlmhosts\fR(5)
+man page for details on the contents of this file.
+.RE
+.PP
+-V
+.RS 3n
+Prints the program version number.
+.RE
+.PP
+-s <configuration file>
+.RS 3n
+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
+\fIsmb.conf\fR
+for more information. The default configuration file name is determined at compile time.
+.RE
+.PP
+-d|--debuglevel=level
+.RS 3n
+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 zero.
 .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.
+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
+\fIlog level\fR
 parameter in the
+\fIsmb.conf\fR
+file.
+.RE
+.PP
+-l|--logfile=logdirectory
+.RS 3n
+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
+-p <UDP port number>
+.RS 3n
+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't use this option unless you are an expert, in which case you won't need help!
+\fIsmb\.conf\fR
+file\.
+.RE
+.PP
+\-V
+.RS 4
+Prints the program version number\.
+.RE
+.PP
+\-s <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
+\fIsmb\.conf\fR
+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
+\-p <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\'t use this option unless you are an expert, in which case you won\'t need help!
 .RE
 .SH "FILES"
 .PP
 \fI/etc/inetd.conf\fR
 .RS 3n
+\fI/etc/inetd\.conf\fR
+.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.
+meta\-daemon, this file must contain suitable startup information for the meta\-daemon\.
 .RE
 .PP
 \fI/etc/rc\fR
 .RS 3n
 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.
+.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
 \fI/etc/services\fR
 .RS 3n
 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
 \fI/usr/local/samba/lib/smb.conf\fR
 .RS 3n
+.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
+\fI/usr/local/samba/lib/smb\.conf\fR
+.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
 \fI/usr/samba/lib/smb.conf\fR
+server configuration file\. Other common places that systems install this file are
+\fI/usr/samba/lib/smb\.conf\fR
 and
 \fI/etc/samba/smb.conf\fR.
+\fI/etc/samba/smb\.conf\fR\.
 .sp
 When run as a WINS server (see the
+wins support parameter in the
+\fIwins support\fR
+parameter in the
 \fBsmb.conf\fR(5)
 man page),
 nmbd
 will store the WINS database in the file
 \fIwins.dat\fR
+\fIwins\.dat\fR
 in the
 \fIvar/locks\fR
 directory configured under wherever Samba was configured to install itself.
+directory configured under wherever Samba was configured to install itself\.
 .sp
 If
 nmbd
 is acting as a
 \fB browse master\fR
+\fI browse master\fR
 (see the
+local master parameter in the
+\fIlocal master\fR
+parameter in the
 \fBsmb.conf\fR(5)
 man page,
 nmbd
 will store the browsing database in the file
 \fIbrowse.dat \fR
+\fIbrowse\.dat \fR
 in the
 \fIvar/locks\fR
 directory configured under wherever Samba was configured to install itself.
+directory configured under wherever Samba was configured to install itself\.
 .RE
 .SH "SIGNALS"
 …
 To shut down an
 nmbd
 process it is recommended that SIGKILL (-9)
 \fBNOT\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.
+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
 \fInamelist.debug \fR
+\fInamelist\.debug \fR
 in the
 \fI/usr/local/samba/var/locks\fR
 directory (or the
 \fIvar/locks\fR
 directory configured under wherever Samba was configured to install itself). This will also cause
+directory configured under wherever Samba was configured to install itself)\. This will also cause
 nmbd
 to dump out its server database in the
 \fIlog.nmb\fR
 file.
+\fIlog\.nmb\fR
+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.
+(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.0 of the Samba suite.
+This man page is correct for version 3\.0 of the Samba suite\.
 .SH "SEE ALSO"
 .PP
 …
 \fBsmbclient\fR(1),
 \fBtestparm\fR(1),
 \fBtestprns\fR(1), and the Internet RFC's
 \fIrfc1001.txt\fR,
 \fIrfc1002.txt\fR. In addition the CIFS (formerly SMB) specification is available as a link from the Web page
 http://samba.org/cifs/.
+\fBtestprns\fR(1), and the Internet RFC\'s
+\fIrfc1001\.txt\fR,
+\fIrfc1002\.txt\fR\. 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.
+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\.

branches/samba-3.0/docs/manpages/nmblookup.1

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "NMBLOOKUP" 1 "" "" ""
+.\"     Title: nmblookup
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: User Commands
+.\"    Source: Samba 3.0
+.\"
+.TH "NMBLOOKUP" "1" "05/21/2008" "Samba 3\.0" "User Commands"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 nmblookup - NetBIOS over TCP/IP client used to lookup NetBIOS names
 .SH "SYNOPSIS"
 .HP 1
 nmblookup [-M] [-R] [-S] [-r] [-A] [-h] [-B <broadcast address>] [-U <unicast address>] [-d <debug level>] [-s <smb config file>] [-i <NetBIOS scope>] [-T] [-f] {name}
+nmblookup [\-M] [\-R] [\-S] [\-r] [\-A] [\-h] [\-B\ <broadcast\ address>] [\-U\ <unicast\ address>] [\-d\ <debug\ level>] [\-s\ <smb\ config\ file>] [\-i\ <NetBIOS\ scope>] [\-T] [\-f] {name}
 .SH "DESCRIPTION"
 .PP
 This tool is part of the
 \fBsamba\fR(7)
 suite.
+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.
+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
 .RS 3n
+\-M
+.RS 4
 Searches for a master browser by looking up the NetBIOS name
 \fIname\fR
 with a type of
 \fB0x1d\fR. If
+\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't parsed as an argument, e.g. use :
 \fBnmblookup -M -- -\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\'t parsed as an argument, e\.g\. use :
+\fBnmblookup \-M \-\- \-\fR\.
 .RE
 .PP
 -R
 .RS 3n
 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.
+\-R
+.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
 .RS 3n
 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.
+\-S
+.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
 .RS 3n
 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
+\-r
+.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.
+daemon is running on this machine it also binds to this port\.
 .RE
 .PP
 -A
 .RS 3n
+\-A
+.RS 4
 Interpret
 \fIname\fR
 as an IP Address and do a node status query on this address.
+as an IP Address and do a node status query on this address\.
 .RE
 .PP
 -n <primary NetBIOS name>
 .RS 3n
 This option allows you to override the NetBIOS name that Samba uses for itself. This is identical to setting the
+\-n <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
+\fInetbios name\fR
 parameter in the
 \fIsmb.conf\fR
 file. However, a command line setting will take precedence over settings in
 \fIsmb.conf\fR.
+\fIsmb\.conf\fR
+file\. However, a command line setting will take precedence over settings in
+\fIsmb\.conf\fR\.
 .RE
 .PP
 -i <scope>
 .RS 3n
+\-i <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
 \fBvery\fR
 rarely used, only set this parameter if you are the system administrator in charge of all the NetBIOS systems you communicate with.
+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 3n
 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).
+\-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
 .RS 3n
 TCP socket options to set on the client socket. See the socket options parameter in the
 \fIsmb.conf\fR
 manual page for the list of valid options.
+\-O socket options
+.RS 4
+TCP socket options to set on the client socket\. See the socket options parameter in the
+\fIsmb\.conf\fR
+manual page for the list of valid options\.
 .RE
 .PP
 -h|--help
 .RS 3n
 Print a summary of command line options.
+\-h|\-\-help
+.RS 4
+Print a summary of command line options\.
 .RE
 .PP
 -B <broadcast address>
 .RS 3n
 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
+\-B <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.
+file\.
 .RE
 .PP
 -U <unicast address>
 .RS 3n
+\-U <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.
+\fIunicast address\fR\. This option (along with the
+\fI\-R\fR
+option) is needed to query a WINS server\.
 .RE
 .PP
+-V
+.RS 3n
+Prints the program version number.
+\-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
+\fIlog level\fR
+parameter in the
+\fIsmb\.conf\fR
+file\.
 .RE
 .PP
+-s <configuration file>
+.RS 3n
+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
+\fIsmb.conf\fR
+for more information. The default configuration file name is determined at compile time.
+\-V
+.RS 4
+Prints the program version number\.
 .RE
 .PP
+-d|--debuglevel=level
+.RS 3n
+\fIlevel\fR
+is an integer from 0 to 10. The default value if this parameter is not specified is zero.
+.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
+parameter in the
+\fIsmb.conf\fR
+file.
+\-s <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
+\fIsmb\.conf\fR
+for more information\. The default configuration file name is determined at compile time\.
 .RE
 .PP
 -l|--logfile=logdirectory
 .RS 3n
 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.
+\-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
 -T
 .RS 3n
+\-T
+.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
 \fBIP address .... NetBIOS name\fR
+\fIIP address \.\.\.\. NetBIOS name\fR
 .sp
 pair that is the normal output.
+pair that is the normal output\.
 .RE
 .PP
 -f
 .RS 3n
 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.
+\-f
+.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 3n
 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 '#<type>' to the name. This name may also be '*', which will return all registered names within a broadcast area.
+.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 \'#<type>\' to the name\. This name may also be \'*\', which will return all registered names within a broadcast area\.
 .RE
 .SH "EXAMPLES"
 …
 can be used to query a WINS server (in the same way
 nslookup
 is used to query DNS servers). To query a WINS server,
+is used to query DNS servers)\. To query a WINS server,
 nmblookup
 must be called like this:
 .PP
 nmblookup -U server -R 'name'
+nmblookup \-U server \-R \'name\'
 .PP
 For example, running :
 .PP
 nmblookup -U samba.org -R 'IRIX#1B'
+nmblookup \-U samba\.org \-R \'IRIX#1B\'
 .PP
 would query the WINS server samba.org for the domain master browser (1B name type) for the IRIX workgroup.
+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.0 of the Samba suite.
+This man page is correct for version 3\.0 of the Samba suite\.
 .SH "SEE ALSO"
 .PP
 \fBnmbd\fR(8),
 \fBsamba\fR(7), and
 \fBsmb.conf\fR(5).
+\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.
+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.
+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\.

branches/samba-3.0/docs/manpages/ntlm_auth.1

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "NTLM_AUTH" 1 "" "" ""
+.\"     Title: ntlm_auth
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: User Commands
+.\"    Source: Samba 3.0
+.\"
+.TH "NTLM_AUTH" "1" "05/21/2008" "Samba 3\.0" "User Commands"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 ntlm_auth - tool to allow external access to Winbind's NTLM authentication function
 .SH "SYNOPSIS"
 .HP 1
 ntlm_auth [-d debuglevel] [-l logdir] [-s <smb config file>]
+ntlm_auth [\-d\ debuglevel] [\-l\ logdir] [\-s\ <smb\ config\ file>]
 .SH "DESCRIPTION"
 .PP
 This tool is part of the
 \fBsamba\fR(7)
 suite.
+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 indended to be used by other programs (currently
+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 indended to be used by other programs (currently
 Squid
 and
 …
 The
 \fBwinbindd\fR(8)
 daemon must be operational for many of these commands to function.
+daemon must be operational for many of these commands to function\.
 .PP
 Some of these commands also require access to the directory
 \fIwinbindd_privileged\fR
 in
 \fI$LOCKDIR\fR. This should be done either by running this command as root or providing group access to the
 \fIwinbindd_privileged\fR
 directory. For security reasons, this directory should not be world-accessable.
+\fI$LOCKDIR\fR\. This should be done either by running this command as root or providing group access to the
+\fIwinbindd_privileged\fR
+directory\. For security reasons, this directory should not be world\-accessable\.
 .SH "OPTIONS"
 .PP
+--helper-protocol=PROTO
+.RS 3n
+Operate as a stdio-based helper. Valid helper protocols are:
+.RS 3n
+.PP
+squid-2.4-basic
+.RS 3n
+Server-side helper for use with Squid 2.4's basic (plaintext) authentication.
+.RE
+.PP
+squid-2.5-basic
+.RS 3n
+Server-side helper for use with Squid 2.5's basic (plaintext) authentication.
+.RE
+.PP
+squid-2.5-ntlmssp
+.RS 3n
+Server-side helper for use with Squid 2.5's NTLMSSP authentication.
+\-\-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\'s basic (plaintext) authentication\.
+.RE
+.PP
+squid\-2\.5\-basic
+.RS 4
+Server\-side helper for use with Squid 2\.5\'s basic (plaintext) authentication\.
+.RE
+.PP
+squid\-2\.5\-ntlmssp
+.RS 4
+Server\-side helper for use with Squid 2\.5\'s NTLMSSP authentication\.
 .sp
 Requires access to the directory
 \fIwinbindd_privileged\fR
 in
 \fI$LOCKDIR\fR. 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
+\fI$LOCKDIR\fR\. 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 3n
 Client-side helper for use with arbitary external programs that may wish to use Samba's NTLMSSP authentication knowlege.
 .sp
 This helper is a client, and as such may be run by any user. The protocol used is effectivly the reverse of the previous protocol. A
+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\'s 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 3n
 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.
+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
 \fIwinbindd_privileged\fR
 in
 \fI$LOCKDIR\fR.
 .RE
 .PP
 gss-spnego-client
 .RS 3n
 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 3n
 Server-side helper protocol, intended for use by a RADIUS server or the 'winbind' plugin for pppd, for the provision of MSCHAP and MSCHAPv2 authentication.
 .sp
 This protocol consists of lines in for form:
+\fI$LOCKDIR\fR\.
+.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 \'winbind\' plugin for pppd, for the provision of MSCHAP and MSCHAPv2 authentication\.
+.sp
+This protocol consists of lines in the form:
 Parameter: value
 and
 Paramter:: 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).
+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
 Curently implemented parameters from the external program to the helper are:
-.RS 3n
 .PP
 Username
+.RS 3n
+The username, expected to be in Samba's
+unix charset.
+.sp
+\fBExample 1. \fRUsername: bob
+.sp
+\fBExample 2. \fRUsername:: Ym9i
+.RS 4
+The username, expected to be in Samba\'s
+\fIunix charset\fR\.
+.PP \fBExample\ 1.\ \fR Username: bob
+.PP \fBExample\ 2.\ \fR Username:: Ym9i
 .RE
 .PP
 Username
+.RS 3n
+The user's domain, expected to be in Samba's
+unix charset.
+.sp
+\fBExample 3. \fRDomain: WORKGROUP
+.sp
+\fBExample 4. \fRDomain:: V09SS0dST1VQ
+.RE
+.PP
+Full-Username
+.RS 3n
+The fully qualified username, expected to be in Samba's
+.RS 4
+The user\'s domain, expected to be in Samba\'s
+\fIunix charset\fR\.
+.PP \fBExample\ 3.\ \fR Domain: WORKGROUP
+.PP \fBExample\ 4.\ \fR Domain:: V09SS0dST1VQ
+.RE
+.PP
+Full\-Username
+.RS 4
+The fully qualified username, expected to be in Samba\'s
+\fIunix charset\fR
 and qualified with the
+winbind separator.
+.sp
+\fBExample 5. \fRFull-Username: WORKGROUP\bob
+.sp
+\fBExample 6. \fRFull-Username:: V09SS0dST1VQYm9i
+.RE
+.PP
+LANMAN-Challenge
+.RS 3n
+\fIwinbind separator\fR\.
+.PP \fBExample\ 5.\ \fR Full\-Username: WORKGROUP\ebob
+.PP \fBExample\ 6.\ \fR Full\-Username:: V09SS0dST1VQYm9i
+.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.
+.sp
+\fBExample 7. \fRLANMAN-Challege: 0102030405060708
+.RE
+.PP
+LANMAN-Response
+.RS 3n
+value, generated randomly by the server, or (in cases such as MSCHAPv2) generated in some way by both the server and the client\.
+.PP \fBExample\ 7.\ \fR LANMAN\-Challege: 0102030405060708
+.RE
+.PP
+LANMAN\-Response
+.RS 4
 The 24 byte
 LANMAN Response
+value, calculated from the user's password and the supplied
+LANMAN Challenge. Typically, this is provided over the network by a client wishing to authenticate.
+.sp
+\fBExample 8. \fRLANMAN-Response: 0102030405060708090A0B0C0D0E0F101112131415161718
+.RE
+.PP
+NT-Response
+.RS 3n
+value, calculated from the user\'s password and the supplied
+LANMAN Challenge\. Typically, this is provided over the network by a client wishing to authenticate\.
+.PP \fBExample\ 8.\ \fR LANMAN\-Response: 0102030405060708090A0B0C0D0E0F101112131415161718
+.RE
+.PP
+NT\-Response
+.RS 4
 The >= 24 byte
 NT Response
+calculated from the user's password and the supplied
+LANMAN Challenge. Typically, this is provided over the network by a client wishing to authenticate.
+.sp
+\fBExample 9. \fRNT-Response: 0102030405060708090A0B0C0D0E0F101112131415161718
+calculated from the user\'s password and the supplied
+LANMAN Challenge\. Typically, this is provided over the network by a client wishing to authenticate\.
+.PP \fBExample\ 9.\ \fR NT\-Response: 0102030405060708090A0B0C0D0E0F101112131415161718
 .RE
 .PP
 Password
+.RS 3n
+The user's 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.
+.sp
+\fBExample 10. \fRPassword: samba2
+.sp
+\fBExample 11. \fRPassword:: c2FtYmEy
+.RE
+.PP
+Request-User-Session-Key
+.RS 3n
+Apon sucessful authenticaiton, return the user session key associated with the login.
+.sp
+\fBExample 12. \fRRequest-User-Session-Key: Yes
+.RE
+.PP
+Request-LanMan-Session-Key
+.RS 3n
+Apon sucessful authenticaiton, return the LANMAN session key associated with the login.
+.sp
+\fBExample 13. \fRRequest-LanMan-Session-Key: Yes
+.RS 4
+The user\'s 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 \fBExample\ 10.\ \fR Password: samba2
+.PP \fBExample\ 11.\ \fR Password:: c2FtYmEy
+.RE
+.PP
+Request\-User\-Session\-Key
+.RS 4
+Apon sucessful authenticaiton, return the user session key associated with the login\.
+.PP \fBExample\ 12.\ \fR Request\-User\-Session\-Key: Yes
+.RE
+.PP
+Request\-LanMan\-Session\-Key
+.RS 4
+Apon sucessful authenticaiton, return the LANMAN session key associated with the login\.
+.PP \fBExample\ 13.\ \fR Request\-LanMan\-Session\-Key: Yes
 .RE
 .sp
 …
 .nr an-break-flag 1
 .br
+\fBWarning\fR
+Warning
 Implementors 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.
+.RE
+.RE
+.RE
+.RE
+.PP
+--username=USERNAME
+.RS 3n
+                a newline\.  They may also need to decode strings from
+                the helper, which likewise may have been base64 encoded\.
+.RE
+.RE
+.PP
+\-\-username=USERNAME
+.RS 4
 Specify username of user to authenticate
 .RE
 .PP
 --domain=DOMAIN
 .RS 3n
+\-\-domain=DOMAIN
+.RS 4
 Specify domain of user to authenticate
 .RE
 .PP
 --workstation=WORKSTATION
 .RS 3n
+\-\-workstation=WORKSTATION
+.RS 4
 Specify the workstation the user authenticated from
 .RE
 .PP
 --challenge=STRING
 .RS 3n
+\-\-challenge=STRING
+.RS 4
 NTLM challenge (in HEXADECIMAL)
 .RE
 .PP
 --lm-response=RESPONSE
 .RS 3n
+\-\-lm\-response=RESPONSE
+.RS 4
 LM Response to the challenge (in HEXADECIMAL)
 .RE
 .PP
 --nt-response=RESPONSE
 .RS 3n
+\-\-nt\-response=RESPONSE
+.RS 4
 NT or NTLMv2 Response to the challenge (in HEXADECIMAL)
 .RE
 .PP
 --password=PASSWORD
 .RS 3n
 User's plaintext password
 .sp
 If not specified on the command line, this is prompted for when required.
 .sp
 For the NTLMSSP based server roles, this paramter specifies the expected password, allowing testing without winbindd operational.
 .RE
 .PP
 --request-lm-key
 .RS 3n
+\-\-password=PASSWORD
+.RS 4
+User\'s 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
 Retreive LM session key
 .RE
 .PP
 --request-nt-key
 .RS 3n
+\-\-request\-nt\-key
+.RS 4
 Request NT key
 .RE
 .PP
+--diagnostics
+.RS 3n
+Perform Diagnostics on the authentication chain. Uses the password from
+--password
+or prompts for one.
+.RE
+.PP
+--require-membership-of={SID|Name}
+.RS 3n
+Require that a user be a member of specified group (either name or SID) for authentication to succeed.
+.RE
+.PP
+-V
+.RS 3n
+Prints the program version number.
+.RE
+.PP
+-s <configuration file>
+.RS 3n
+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
+\fIsmb.conf\fR
+for more information. The default configuration file name is determined at compile time.
+.RE
+.PP
+-d|--debuglevel=level
+.RS 3n
+\-\-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
+\-d|\-\-debuglevel=level
+.RS 4
 \fIlevel\fR
 is an integer from 0 to 10. The default value if this parameter is not specified is zero.
 .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.
+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
+\fIlog level\fR
 parameter in the
+\fIsmb.conf\fR
+file.
+.RE
+.PP
+-l|--logfile=logdirectory
+.RS 3n
+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
+-h|--help
+.RS 3n
+Print a summary of command line options.
+\fIsmb\.conf\fR
+file\.
+.RE
+.PP
+\-V
+.RS 4
+Prints the program version number\.
+.RE
+.PP
+\-s <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
+\fIsmb\.conf\fR
+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
+\-h|\-\-help
+.RS 4
+Print a summary of command line options\.
 .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
+\fIsquid.conf\fR
+file.
+.sp
+To setup ntlm_auth for use by squid 2\.5, with both basic and NTLMSSP authentication, the following should be placed in the
+\fIsquid\.conf\fR
+file\.
+.sp
+.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 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 realm Squid proxy\-caching web server
 auth_param basic credentialsttl 2 hours
 .fi
+.RE
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBNote\fR
+Note
 .PP
 This example assumes that ntlm_auth has been installed into your path, and that the group permissions on
 \fIwinbindd_privileged\fR
+are as described above.
+.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
+\fIsquid.conf\fR
+file.
+.sp
+are as described above\.
+.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
+\fIsquid\.conf\fR
+file\.
+.sp
+.RS 4
 .nf
+auth_param ntlm program ntlm_auth --helper-protocol=squid-2.5-ntlmssp --require-membership-of='WORKGROUP\Domain Users'
+auth_param basic program ntlm_auth --helper-protocol=squid-2.5-basic --require-membership-of='WORKGROUP\Domain Users'
+auth_param ntlm program ntlm_auth \-\-helper\-protocol=squid\-2\.5\-ntlmssp \-\-require\-membership\-of=\'WORKGROUP\eDomain Users\'
+auth_param basic program ntlm_auth \-\-helper\-protocol=squid\-2\.5\-basic \-\-require\-membership\-of=\'WORKGROUP\eDomain Users\'
 .fi
+.RE
 .SH "TROUBLESHOOTING"
 .PP
 If you're experiencing problems with authenticating Internet Explorer running under MS Windows 9X or Millenium Edition against ntlm_auth's NTLMSSP authentication helper (--helper-protocol=squid-2.5-ntlmssp), then please read
 the Microsoft Knowledge Base article #239869 and follow instructions described there.
+If you\'re experiencing problems with authenticating Internet Explorer running under MS Windows 9X or Millenium Edition against ntlm_auth\'s 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.0 of the Samba suite.
+This man page is correct for version 3\.0 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.
+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\.

branches/samba-3.0/docs/manpages/pam_winbind.7

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "PAM_WINBIND" 7 "" "" ""
+.\"     Title: pam_winbind
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: 7
+.\"    Source: Samba 3.0
+.\"
+.TH "PAM_WINBIND" "7" "05/21/2008" "Samba 3\.0" "7"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 pam_winbind - PAM module for Winbind
 …
 This tool is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 pam_winbind is a PAM module that can authenticate users against the local domain by talking to the Winbind daemon.
+pam_winbind is a PAM module that can authenticate users against the local domain by talking to the Winbind daemon\.
 .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
 \fI/etc/security/pam_winbind.conf\fR. Options from the PAM configuration file take precedence to those from the configuration file.
+\fI/etc/security/pam_winbind\.conf\fR\. Options from the PAM configuration file take precedence to those from the configuration file\.
 .PP
 debug
 .RS 3n
 Gives debugging output to syslog.
+.RS 4
+Gives debugging output to syslog\.
 .RE
 .PP
 debug_state
 .RS 3n
 Gives detailed PAM state debugging output to syslog.
+.RS 4
+Gives detailed PAM state debugging output to syslog\.
 .RE
 .PP
 require_membership_of=[SID or NAME]
 .RS 3n
 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, a alias-SID or even a user-SID. It is also possible to give a NAME instead of the SID. That name must have the form:
 \fIMYDOMAIN\\mygroup\fR
+.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\\myuser\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.
+\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\.
 .RE
 .PP
 try_first_pass
+.RS 3n
+.RS 4
 .RE
 .PP
 use_first_pass
 .RS 3n
 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.
+.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
 use_authtok
 .RS 3n
 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.
+.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 3n
 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.
+.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 3n
+.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.
+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 3n
+.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.
+is enabled\. To use this feature from the PAM module this option must be set\.
 .RE
 .PP
 silent
 .RS 3n
 Do not emit any messages.
+.RS 4
+Do not emit any messages\.
 .RE
 .SH "SEE ALSO"
 .PP
 …
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of Samba.
+This man page is correct for version 3\.0 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.
+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.
+This manpage was written by Jelmer Vernooij and Guenther Deschner\.

branches/samba-3.0/docs/manpages/pdbedit.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "PDBEDIT" 8 "" "" ""
+.\"     Title: pdbedit
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "PDBEDIT" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 pdbedit - manage the SAM database (Database of Samba Users)
 .SH "SYNOPSIS"
 .HP 1
 pdbedit [-L] [-v] [-w] [-u username] [-f fullname] [-h homedir] [-D drive] [-S script] [-p profile] [-a] [-t, --password-from-stdin] [-m] [-r] [-x] [-i passdb-backend] [-e passdb-backend] [-b passdb-backend] [-g] [-d debuglevel] [-s configfile] [-P account-policy] [-C value] [-c account-control] [-y]
+pdbedit [\-L] [\-v] [\-w] [\-u\ username] [\-f\ fullname] [\-h\ homedir] [\-D\ drive] [\-S\ script] [\-p\ profile] [\-a] [\-t,\ \-\-password\-from\-stdin] [\-m] [\-r] [\-x] [\-i\ passdb\-backend] [\-e\ passdb\-backend] [\-b\ passdb\-backend] [\-g] [\-d\ debuglevel] [\-s\ configfile] [\-P\ account\-policy] [\-C\ value] [\-c\ account\-control] [\-y]
 .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, modifing a user account, listing user accounts, importing users accounts.
+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, modifing a user account, listing user accounts, importing users accounts\.
 .SH "OPTIONS"
 .PP
+-L
+.RS 3n
+This option lists all the user accounts present in the users database. This option prints a list of user/uid pairs separated by the ':' character.
+.sp
+Example:
+pdbedit -L
+.sp
+.sp
+.nf
+\-L
+.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 \':\' character\.
+.sp
+Example:
+pdbedit \-L
+.sp
+.sp
+.RS 4
+.nf
 sorce:500:Simo Sorce
 samba:45:Test User
+.fi
+.RE
+.PP
+-v
+.RS 3n
+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
+.sp
+.nf
+---------------
+.fi
+.RE
+.RE
+.PP
+\-v
+.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
+.sp
+.RS 4
+.nf
+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
 username:       sorce
 user ID/Group:  500/500
 user RID/GRID:  2000/2001
 Full Name:      Simo Sorce
 Home Directory: \\BERSERKER\sorce
+Home Directory: \e\eBERSERKER\esorce
 HomeDir Drive:  H:
 Logon Script:   \\BERSERKER\netlogon\sorce.bat
 Profile Path:   \\BERSERKER\profile
 ---------------
+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: \\BERSERKER\samba
+Home Directory: \e\eBERSERKER\esamba
 HomeDir Drive:
 Logon Script:
+Profile Path:   \\BERSERKER\profile
+.fi
+.RE
+.PP
+-w
+.RS 3n
+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
+Profile Path:   \e\eBERSERKER\eprofile
+.fi
+.RE
+.RE
+.PP
+\-w
+.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
 \fIsmbpasswd\fR
 file format. (see the
+file format\. (see the
 \fBsmbpasswd\fR(5)
 for details)
 .sp
 Example:
 pdbedit -L -w
 .nf
+pdbedit \-L \-w
+.sp
+.RS 4
+.nf
 sorce:500:508818B733CE64BEAAD3B435B51404EE:
           D2A2418EFC466A8A0F6B1DBB5C3DB80C:
           [UX         ]:LCT-00000000:
+          [UX         ]:LCT\-00000000:
 samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:
           BC281CE3F53B6A5146629CD4751D3490:
+          [UX         ]:LCT-3BFA1E8D:
+          [UX         ]:LCT\-3BFA1E8D:
+.fi
+.RE
+.RE
+.PP
+\-u 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
+.RS 4
+This option can be used while adding or modifing a user account\. It will specify the user\'s full name\.
+.sp
+Example:
+\-f "Simo Sorce"
+.RE
+.PP
+\-h homedir
+.RS 4
+This option can be used while adding or modifing a user account\. It will specify the user\'s home directory network path\.
+.sp
+Example:
+\-h "\e\e\e\eBERSERKER\e\esorce"
+.RE
+.PP
+\-D drive
+.RS 4
+This option can be used while adding or modifing 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
+.RS 4
+This option can be used while adding or modifing a user account\. It will specify the user\'s logon script path\.
+.sp
+Example:
+\-S "\e\e\e\eBERSERKER\e\enetlogon\e\esorce\.bat"
+.RE
+.PP
+\-p profile
+.RS 4
+This option can be used while adding or modifing a user account\. It will specify the user\'s profile directory\.
+.sp
+Example:
+\-p "\e\e\e\eBERSERKER\e\enetlogon"
+.RE
+.PP
+\-G SID|rid
+.RS 4
+This option can be used while adding or modifying a user account\. It will specify the users\' new primary group SID (Security Identifier) or rid\.
+.sp
+Example:
+\-G S\-1\-5\-21\-2447931902\-1787058256\-3961074038\-1201
+.RE
+.PP
+\-U SID|rid
+.RS 4
+This option can be used while adding or modifying a user account\. It will specify the users\' new SID (Security Identifier) or rid\.
+.sp
+Example:
+\-U S\-1\-5\-21\-2447931902\-1787058256\-3961074038\-5004
+.RE
+.PP
+\-c account\-control
+.RS 4
+This option can be used while adding or modifying a user account\. It will specify the users\' account control property\. Possible flags are listed below\.
+.sp
+.fi
+.RE
+.PP
+-u username
+.RS 3n
+This option specifies the username to be used for the operation requested (listing, adding, removing). It is
+\fBrequired\fR
+in add, remove and modify operations and
+\fBoptional\fR
+in list operations.
+.RE
+.PP
+-f fullname
+.RS 3n
+This option can be used while adding or modifing a user account. It will specify the user's full name.
+.sp
+Example:
+-f "Simo Sorce"
+.RE
+.PP
+-h homedir
+.RS 3n
+This option can be used while adding or modifing a user account. It will specify the user's home directory network path.
+.sp
+Example:
+-h "\\\\\\\\BERSERKER\\\\sorce"
+.RE
+.PP
+-D drive
+.RS 3n
+This option can be used while adding or modifing 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
+.RS 3n
+This option can be used while adding or modifing a user account. It will specify the user's logon script path.
+.sp
+Example:
+-S "\\\\\\\\BERSERKER\\\\netlogon\\\\sorce.bat"
+.RE
+.PP
+-p profile
+.RS 3n
+This option can be used while adding or modifing a user account. It will specify the user's profile directory.
+.sp
+Example:
+-p "\\\\\\\\BERSERKER\\\\netlogon"
+.RE
+.PP
+-G SID|rid
+.RS 3n
+This option can be used while adding or modifying a user account. It will specify the users' new primary group SID (Security Identifier) or rid.
+.sp
+Example:
+-G S-1-5-21-2447931902-1787058256-3961074038-1201
+.RE
+.PP
+-U SID|rid
+.RS 3n
+This option can be used while adding or modifying a user account. It will specify the users' new SID (Security Identifier) or rid.
+.sp
+Example:
+-U S-1-5-21-2447931902-1787058256-3961074038-5004
+.RE
+.PP
+-c account-control
+.RS 3n
+This option can be used while adding or modifying a user account. It will specify the users' account control property. Possible flags are listed below.
+.sp
+.RS 3n
+.TP 3n
+\(bu
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 N: No password required
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 D: Account disabled
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 H: Home directory required
+.TP 3n
+\(bu
+.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
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 U: Regular user account
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 M: MNS logon user account
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 W: Workstation Trust Account
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 S: Server Trust Account
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 L: Automatic Locking
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 X: Password does not expire
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 I: Domain Trust Account
+.RE
+.IP "" 3n
+.sp
+Example:
+-c "[X ]"
+.RE
+.PP
+-a
+.RS 3n
+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
+.sp
+.RE
+.sp
+Example:
+\-c "[X ]"
+.RE
+.PP
+\-a
+.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
+.RS 4
 .nf
 new password:
 retype new password
 .fi
+.fi
+.RE
+.sp
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBNote\fR
+Note
 pdbedit does not call the unix password syncronisation script if
+unix password sync has been set. It only updates the data in the Samba user database.
+\fIunix password sync\fR
+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's
 \fB-a\fR
 option.
 .RE
 .PP
 -t, --password-from-stdin
 .RS 3n
+smbpasswd\'s
+\fB\-a\fR
+option\.
+.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
 .RS 3n
 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
 .RS 3n
+program does)\. The password has to be submitted twice and terminated by a newline each\.
+.RE
+.PP
+\-r
+.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
+.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
 .RS 3n
 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 passdb-backend
 .RS 3n
 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 passdb-backend
 .RS 3n
 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
 .RS 3n
+\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
+.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 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 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
+.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 passdb-backend
 .RS 3n
 Use a different default passdb backend.
 .sp
 Example:
 pdbedit -b xml:/root/pdb-backup.xml -l
 .RE
 .PP
 -P account-policy
 .RS 3n
+\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 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
+.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
+.sp
+.nf
+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
+.sp
+.RS 4
+.nf
 account policy value for bad lockout attempt is 0
+.fi
+.RE
+.PP
+-C account-policy-value
+.RS 3n
+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
+.sp
+.nf
+.fi
+.RE
+.RE
+.PP
+\-C 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
+.sp
+.RS 4
+.nf
 account policy value for bad lockout attempt was 0
 account policy value for bad lockout attempt is now 3
+.fi
+.RE
+.PP
+-y
+.RS 3n
+.fi
+.RE
+.RE
+.PP
+\-y
+.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
+-h|--help
+.RS 3n
+Print a summary of command line options.
+.RE
+.PP
+-V
+.RS 3n
+Prints the program version number.
+.RE
+.PP
+-s <configuration file>
+.RS 3n
+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
+\fIsmb.conf\fR
+for more information. The default configuration file name is determined at compile time.
+.RE
+.PP
+-d|--debuglevel=level
+.RS 3n
+\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
+\-h|\-\-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 zero.
 .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.
+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
+\fIlog level\fR
 parameter in the
+\fIsmb.conf\fR
+file.
+.RE
+.PP
+-l|--logfile=logdirectory
+.RS 3n
+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.
+\fIsmb\.conf\fR
+file\.
+.RE
+.PP
+\-V
+.RS 4
+Prints the program version number\.
+.RE
+.PP
+\-s <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
+\fIsmb\.conf\fR
+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
 .SH "NOTES"
 .PP
 This command may be used only by root.
+This command may be used only by root\.
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 of the Samba suite\.
 .SH "SEE ALSO"
 .PP
 …
 .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.
+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\.

branches/samba-3.0/docs/manpages/profiles.1

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "PROFILES" 1 "" "" ""
+.\"     Title: profiles
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: User Commands
+.\"    Source: Samba 3.0
+.\"
+.TH "PROFILES" "1" "05/21/2008" "Samba 3\.0" "User Commands"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 profiles - A utility to report and change SIDs in registry files
 .SH "SYNOPSIS"
 .HP 1
 profiles [-v] [-c SID] [-n SID] {file}
+profiles [\-v] [\-c\ SID] [\-n\ SID] {file}
 .SH "DESCRIPTION"
 .PP
 This tool is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 profiles
 is a utility that reports and changes SIDs in windows registry files. It currently only supports NT.
+is a utility that reports and changes SIDs in windows registry files\. It currently only supports NT\.
 .SH "OPTIONS"
 .PP
 file
 .RS 3n
 Registry file to view or edit.
+.RS 4
+Registry file to view or edit\.
 .RE
 .PP
 -v,--verbose
 .RS 3n
 Increases verbosity of messages.
+\-v,\-\-verbose
+.RS 4
+Increases verbosity of messages\.
 .RE
 .PP
 -c SID1 -n SID2
 .RS 3n
+\-c SID1 \-n SID2
+.RS 4
 Change all occurences of SID1 in
 \fIfile\fR
 by SID2.
+by SID2\.
 .RE
 .PP
 -h|--help
 .RS 3n
 Print a summary of command line options.
+\-h|\-\-help
+.RS 4
+Print a summary of command line options\.
 .RE
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 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.
+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.
+The profiles man page was written by Jelmer Vernooij\.

branches/samba-3.0/docs/manpages/rpcclient.1

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "RPCCLIENT" 1 "" "" ""
+.\"     Title: rpcclient
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: User Commands
+.\"    Source: Samba 3.0
+.\"
+.TH "RPCCLIENT" "1" "05/21/2008" "Samba 3\.0" "User Commands"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 rpcclient - tool for executing client side MS-RPC functions
 .SH "SYNOPSIS"
 .HP 1
 rpcclient [-A authfile] [-c <command string>] [-d debuglevel] [-h] [-l logdir] [-N] [-s <smb config file>] [-U username[%password]] [-W workgroup] [-N] [-I destinationIP] {server}
+rpcclient [\-A\ authfile] [\-c\ <command\ string>] [\-d\ debuglevel] [\-h] [\-l\ logdir] [\-N] [\-s\ <smb\ config\ file>] [\-U\ username[%password]] [\-W\ workgroup] [\-N] [\-I\ destinationIP] {server}
 .SH "DESCRIPTION"
 .PP
 This tool is part of the
 \fBsamba\fR(7)
 suite.
+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.
+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 3n
+NetBIOS name of Server to which to connect. The server can be any SMB/CIFS server. The name is resolved using the
+name resolve order line from
+\fBsmb.conf\fR(5).
+.RE
+.PP
+-c|--command='command string'
+.RS 3n
+.RS 4
+NetBIOS name of Server to which to connect\. The server can be any SMB/CIFS server\. The name is resolved using the
+\fIname resolve order\fR
+line from
+\fBsmb.conf\fR(5)\.
+.RE
+.PP
+\-c|\-\-command=\'command string\'
+.RS 4
 execute semicolon separated commands (listed below))
 .RE
 .PP
 -I IP-address
 .RS 3n
+\-I 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.
+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
+-V
+.RS 3n
+Prints the program version number.
+.RE
+.PP
+-s <configuration file>
+.RS 3n
+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
+\fIsmb.conf\fR
+for more information. The default configuration file name is determined at compile time.
+.RE
+.PP
+-d|--debuglevel=level
+.RS 3n
+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
+\-d|\-\-debuglevel=level
+.RS 4
 \fIlevel\fR
 is an integer from 0 to 10. The default value if this parameter is not specified is zero.
 .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.
+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
+\fIlog level\fR
 parameter in the
+\fIsmb.conf\fR
+file.
+.RE
+.PP
+-l|--logfile=logdirectory
+.RS 3n
+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
+-N
+.RS 3n
+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
+.RS 3n
+Try to authenticate with kerberos. Only useful in an Active Directory environment.
+.RE
+.PP
+-A|--authentication-file=filename
+.RS 3n
+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
+.sp
+\fIsmb\.conf\fR
+file\.
+.RE
+.PP
+\-V
+.RS 4
+Prints the program version number\.
+.RE
+.PP
+\-s <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
+\fIsmb\.conf\fR
+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
+\-N
+.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
+.RS 4
+Try to authenticate with kerberos\. Only useful in an Active Directory environment\.
+.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
+.sp
+.RS 4
 .nf
 username = <value>
 password = <value>
 domain   = <value>
 .fi
 .sp
 Make certain that the permissions on the file restrict access from unwanted users.
 .RE
 .PP
 -U|--user=username[%password]
 .RS 3n
 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
+.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
+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
+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
+command\. To be safe always allow
 rpcclient
 to prompt for a password and type it in directly.
 .RE
 .PP
 -n <primary NetBIOS name>
 .RS 3n
 This option allows you to override the NetBIOS name that Samba uses for itself. This is identical to setting the
+to prompt for a password and type it in directly\.
+.RE
+.PP
+\-n <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
+\fInetbios name\fR
 parameter in the
 \fIsmb.conf\fR
 file. However, a command line setting will take precedence over settings in
 \fIsmb.conf\fR.
 .RE
 .PP
 -i <scope>
 .RS 3n
+\fIsmb\.conf\fR
+file\. However, a command line setting will take precedence over settings in
+\fIsmb\.conf\fR\.
+.RE
+.PP
+\-i <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
 \fBvery\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 3n
 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
 .RS 3n
 TCP socket options to set on the client socket. See the socket options parameter in the
 \fIsmb.conf\fR
 manual page for the list of valid options.
 .RE
 .PP
 -h|--help
 .RS 3n
 Print a summary of command line options.
+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
+.RS 4
+TCP socket options to set on the client socket\. See the socket options parameter in the
+\fIsmb\.conf\fR
+manual page for the list of valid options\.
+.RE
+.PP
+\-h|\-\-help
+.RS 4
+Print a summary of command line options\.
 .RE
 .SH "COMMANDS"
 …
 .PP
 lsaquery
 .RS 3n
+.RS 4
 Query info policy
 .RE
 .PP
 lookupsids
 .RS 3n
 Resolve a list of SIDs to usernames.
+.RS 4
+Resolve a list of SIDs to usernames\.
 .RE
 .PP
 lookupnames
 .RS 3n
 Resolve a list of usernames to SIDs.
+.RS 4
+Resolve a list of usernames to SIDs\.
 .RE
 .PP
 enumtrusts
 .RS 3n
+.RS 4
 Enumerate trusted domains
 .RE
 .PP
 enumprivs
 .RS 3n
+.RS 4
 Enumerate privileges
 .RE
 .PP
 getdispname
 .RS 3n
+.RS 4
 Get the privilege name
 .RE
 .PP
 lsaenumsid
 .RS 3n
+.RS 4
 Enumerate the LSA SIDS
 .RE
 .PP
 lsaenumprivsaccount
 .RS 3n
+.RS 4
 Enumerate the privileges of an SID
 .RE
 .PP
 lsaenumacctrights
 .RS 3n
+.RS 4
 Enumerate the rights of an SID
 .RE
 .PP
 lsaenumacctwithright
 .RS 3n
+.RS 4
 Enumerate accounts with a right
 .RE
 .PP
 lsaaddacctrights
 .RS 3n
+.RS 4
 Add rights to an account
 .RE
 .PP
 lsaremoveacctrights
 .RS 3n
+.RS 4
 Remove rights from an account
 .RE
 .PP
 lsalookupprivvalue
 .RS 3n
+.RS 4
 Get a privilege value given its name
 .RE
 .PP
 lsaquerysecobj
 .RS 3n
+.RS 4
 Query LSA security object
 .RE
 .SS "LSARPC-DS"
+.SS "LSARPC\-DS"
 .PP
 dsroledominfo
 .RS 3n
+.RS 4
 Get Primary Domain Information
 .RE
 .PP
+.PP
+\fBDFS\fR
+.PP
+\fIDFS\fR
 .PP
 dfsexist
 .RS 3n
+.RS 4
 Query DFS support
 .RE
 .PP
 dfsadd
 .RS 3n
+.RS 4
 Add a DFS share
 .RE
 .PP
 dfsremove
 .RS 3n
+.RS 4
 Remove a DFS share
 .RE
 .PP
 dfsgetinfo
 .RS 3n
+.RS 4
 Query DFS share info
 .RE
 .PP
 dfsenum
 .RS 3n
+.RS 4
 Enumerate dfs shares
 .RE
 …
 .PP
 shutdown
 .RS 3n
+.RS 4
 Remote Shutdown
 .RE
 .PP
 abortshutdown
 .RS 3n
+.RS 4
 Abort Shutdown
 .RE
 …
 .PP
 srvinfo
 .RS 3n
+.RS 4
 Server query info
 .RE
 .PP
 netshareenum
 .RS 3n
+.RS 4
 Enumerate shares
 .RE
 .PP
 netfileenum
 .RS 3n
+.RS 4
 Enumerate open files
 .RE
 .PP
 netremotetod
 .RS 3n
+.RS 4
 Fetch remote time of day
 .RE
 …
 .PP
 queryuser
 .RS 3n
+.RS 4
 Query user info
 .RE
 .PP
 querygroup
 .RS 3n
+.RS 4
 Query group info
 .RE
 .PP
 queryusergroups
 .RS 3n
+.RS 4
 Query user groups
 .RE
 .PP
 querygroupmem
 .RS 3n
+.RS 4
 Query group membership
 .RE
 .PP
 queryaliasmem
 .RS 3n
+.RS 4
 Query alias membership
 .RE
 .PP
 querydispinfo
 .RS 3n
+.RS 4
 Query display info
 .RE
 .PP
 querydominfo
 .RS 3n
+.RS 4
 Query domain info
 .RE
 .PP
 enumdomusers
 .RS 3n
+.RS 4
 Enumerate domain users
 .RE
 .PP
 enumdomgroups
 .RS 3n
+.RS 4
 Enumerate domain groups
 .RE
 .PP
 enumalsgroups
 .RS 3n
+.RS 4
 Enumerate alias groups
 .RE
 .PP
 createdomuser
 .RS 3n
+.RS 4
 Create domain user
 .RE
 .PP
 samlookupnames
 .RS 3n
+.RS 4
 Look up names
 .RE
 .PP
 samlookuprids
 .RS 3n
+.RS 4
 Look up names
 .RE
 .PP
 deletedomuser
 .RS 3n
+.RS 4
 Delete domain user
 .RE
 .PP
 samquerysecobj
 .RS 3n
+.RS 4
 Query SAMR security object
 .RE
 .PP
 getdompwinfo
 .RS 3n
+.RS 4
 Retrieve domain password info
 .RE
 .PP
 lookupdomain
 .RS 3n
+.RS 4
 Look up domain
 .RE
 …
 .PP
 adddriver <arch> <config> [<version>]
 .RS 3n
 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
+.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
+command\. The
 \fIconfig\fR
 parameter is defined as follows:
 .sp
+.sp
+.sp
+.RS 4
 .nf
+Long Printer Name:\
+Driver File Name:\
+Data File Name:\
+Config File Name:\
+Help File Name:\
+Language Monitor Name:\
+Default Data Type:\
+Long Printer 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
 .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.
+.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.
+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 3n
 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
+.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.
+enumports\.
 .RE
 .PP
 deldriver
 .RS 3n
 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's list of drivers.
+.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\'s list of drivers\.
 .RE
 .PP
 deldriverex <driver> [architecture] [version]
 .RS 3n
 Delete the specified printer driver including driver files. You can limit this action to a specific architecture and a specific version. If no architecure is given, all driver files of that driver will be deleted.
+.RS 4
+Delete the specified printer driver including driver files\. You can limit this action to a specific architecture and a specific version\. If no architecure is given, all driver files of that driver will be deleted\.
 .RE
 .PP
 enumdata
 .RS 3n
 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).
+.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 3n
+.RS 4
 Enumerate printer data for a key
 .RE
 .PP
 enumjobs <printer>
 .RS 3n
 List the jobs and status of a given printer. This command corresponds to the MS Platform SDK EnumJobs() function
+.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 3n
+.RS 4
 Enumerate printer keys
 .RE
 .PP
 enumports [level]
 .RS 3n
 Executes an EnumPorts() call using the specified info level. Currently only info levels 1 and 2 are supported.
+.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 3n
 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.
+.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 3n
 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.
+.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 3n
 Retrieve the data for a given printer setting. See the
+.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.
+command for more information\. This command corresponds to the GetPrinterData() MS Platform SDK function\.
 .RE
 .PP
 getdataex
 .RS 3n
+.RS 4
 Get printer driver data with keyname
 .RE
 .PP
 getdriver <printername>
 .RS 3n
 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.
+.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 3n
 Execute a GetPrinterDriverDirectory() RPC to retrieve the SMB share name and subdirectory for storing printer driver files for a given architecture. Possible values for
+.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".
+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 3n
 Retrieve the current printer information. This command corresponds to the GetPrinter() MS Platform SDK function.
+.RS 4
+Retrieve the current printer information\. This command corresponds to the GetPrinter() MS Platform SDK function\.
 .RE
 .PP
 getprintprocdir
 .RS 3n
+.RS 4
 Get print processor directory
 .RE
 .PP
 openprinter <printername>
 .RS 3n
 Execute an OpenPrinterEx() and ClosePrinter() RPC against a given printer.
+.RS 4
+Execute an OpenPrinterEx() and ClosePrinter() RPC against a given printer\.
 .RE
 .PP
 setdriver <printername> <drivername>
 .RS 3n
 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.
+.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
 …
 and
 enumdrivers
 commands for obtaining a list of of installed printers and drivers.
+commands for obtaining a list of of installed printers and drivers\.
 .RE
 .PP
 addform
 .RS 3n
+.RS 4
 Add form
 .RE
 .PP
 setform
 .RS 3n
+.RS 4
 Set form
 .RE
 .PP
 getform
 .RS 3n
+.RS 4
 Get form
 .RE
 .PP
 deleteform
 .RS 3n
+.RS 4
 Delete form
 .RE
 .PP
 enumforms
 .RS 3n
+.RS 4
 Enumerate form
 .RE
 .PP
 setprinter
 .RS 3n
+.RS 4
 Set printer comment
 .RE
 .PP
 setprinterdata
 .RS 3n
+.RS 4
 Set REG_SZ printer data
 .RE
 .PP
 setprintername <printername> <newprintername>
 .RS 3n
+.RS 4
 Set printer name
 .RE
 .PP
 rffpcnex
 .RS 3n
+.RS 4
 Rffpcnex test
 .RE
 …
 .PP
 logonctrl2
 .RS 3n
+.RS 4
 Logon Control 2
 .RE
 .PP
 logonctrl
 .RS 3n
+.RS 4
 Logon Control
 .RE
 .PP
 samsync
 .RS 3n
+.RS 4
 Sam Synchronisation
 .RE
 .PP
 samdeltas
 .RS 3n
+.RS 4
 Query Sam Deltas
 .RE
 .PP
 samlogon
 .RS 3n
+.RS 4
 Sam Logon
 .RE
 …
 .PP
 debuglevel
 .RS 3n
 Set the current debug level used to log information.
+.RS 4
+Set the current debug level used to log information\.
 .RE
 .PP
 help (?)
 .RS 3n
 Print a listing of all known commands or extended help on a particular command.
+.RS 4
+Print a listing of all known commands or extended help on a particular command\.
 .RE
 .PP
 quit (exit)
 .RS 3n
+.RS 4
 Exit
 rpcclient.
+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's original rpcclient man page:
 .PP
 \fBWARNING!\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's implementation of these services has been demonstrated (and reported) to be... a bit flaky in places.
 .PP
 The development of Samba's implementation is also a bit rough, and as more of the services are understood, it can even result in versions of
+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\'s 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\'s implementation of these services has been demonstrated (and reported) to be\.\.\. a bit flaky in places\.
+.PP
+The development of Samba\'s 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.
+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.0 of the Samba suite.
+This man page is correct for version 3\.0 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.
+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\.

branches/samba-3.0/docs/manpages/samba.7

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "SAMBA" 7 "" "" ""
+.\"     Title: samba
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: Miscellanea
+.\"    Source: Samba 3.0
+.\"
+.TH "SAMBA" "7" "05/21/2008" "Samba 3\.0" "Miscellanea"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 samba - A Windows SMB/CIFS fileserver for UNIX
 …
 .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. 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.
+The Samba software suite is a collection of programs that implements the Server Message Block (commonly abbreviated as SMB) protocol for UNIX systems\. 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
 \fBsmbd\fR(8)
 .RS 3n
+.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
+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 3n
+.RS 4
 The
 nmbd
 daemon provides NetBIOS nameservice and browsing support. The configuration file for this daemon is described in
+daemon provides NetBIOS nameservice and browsing support\. The configuration file for this daemon is described in
 \fBsmb.conf\fR(5)
 .RE
 .PP
 \fBsmbclient\fR(1)
 .RS 3n
+.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).
+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
 \fBtestparm\fR(1)
 .RS 3n
+.RS 4
 The
 testparm
 utility is a simple syntax checker for Samba's
+utility is a simple syntax checker for Samba\'s
 \fBsmb.conf\fR(5)
 configuration file.
+configuration file\.
 .RE
 .PP
 \fBtestprns\fR(1)
 .RS 3n
+.RS 4
 The
 testprns
 utility supports testing printer names defined in your
 \fIprintcap\fR
 file used by Samba.
+file used by Samba\.
 .RE
 .PP
 \fBsmbstatus\fR(1)
 .RS 3n
+.RS 4
 The
 smbstatus
 tool provides access to information about the current connections to
 smbd.
+smbd\.
 .RE
 .PP
 \fBnmblookup\fR(1)
 .RS 3n
+.RS 4
 The
 nmblookup
 tools allows NetBIOS name queries to be made from a UNIX host.
+tools allows NetBIOS name queries to be made from a UNIX host\.
 .RE
 .PP
 \fBsmbpasswd\fR(8)
 .RS 3n
+.RS 4
 The
 smbpasswd
 command is a tool for changing LanMan and Windows NT password hashes on Samba and Windows NT servers.
+command is a tool for changing LanMan and Windows NT password hashes on Samba and Windows NT servers\.
 .RE
 .PP
 \fBsmbcacls\fR(1)
 .RS 3n
+.RS 4
 The
 smbcacls
 command is a tool to set ACL's on remote CIFS servers.
+command is a tool to set ACL\'s on remote CIFS servers\.
 .RE
 .PP
 \fBsmbsh\fR(1)
 .RS 3n
+.RS 4
 The
 smbsh
 command is a program that allows you to run a unix shell with with an overloaded VFS.
+command is a program that allows you to run a unix shell with with an overloaded VFS\.
 .RE
 .PP
 \fBsmbtree\fR(1)
 .RS 3n
+.RS 4
 The
 smbtree
 command is a text-based network neighborhood tool.
+command is a text\-based network neighborhood tool\.
 .RE
 .PP
 \fBsmbtar\fR(1)
 .RS 3n
+.RS 4
 The
 smbtar
 can make backups of data on CIFS/SMB servers.
+can make backups of data on CIFS/SMB servers\.
 .RE
 .PP
 \fBsmbspool\fR(8)
 .RS 3n
+.RS 4
 smbspool
 is a helper utility for printing on printers connected to CIFS servers.
+is a helper utility for printing on printers connected to CIFS servers\.
 .RE
 .PP
 \fBsmbcontrol\fR(1)
 .RS 3n
+.RS 4
 smbcontrol
 is a utility that can change the behaviour of running samba daemons.
+is a utility that can change the behaviour of running samba daemons\.
 .RE
 .PP
 \fBrpcclient\fR(1)
 .RS 3n
+.RS 4
 rpcclient
 is a utility that can be used to execute RPC commands on remote CIFS servers.
+is a utility that can be used to execute RPC commands on remote CIFS servers\.
 .RE
 .PP
 \fBpdbedit\fR(8)
 .RS 3n
+.RS 4
 The
 pdbedit
 command can be used to maintain the local user database on a samba server.
+command can be used to maintain the local user database on a samba server\.
 .RE
 .PP
 \fBfindsmb\fR(1)
 .RS 3n
+.RS 4
 The
 findsmb
 command can be used to find SMB servers on the local network.
+command can be used to find SMB servers on the local network\.
 .RE
 .PP
 \fBnet\fR(8)
 .RS 3n
+.RS 4
 The
 net
 command is supposed to work similar to the DOS/Windows NET.EXE command.
+command is supposed to work similar to the DOS/Windows NET\.EXE command\.
 .RE
 .PP
 \fBswat\fR(8)
 .RS 3n
+.RS 4
 swat
 is a web-based interface to configuring
 \fIsmb.conf\fR.
+is a web\-based interface to configuring
+\fIsmb\.conf\fR\.
 .RE
 .PP
 \fBwinbindd\fR(8)
 .RS 3n
+.RS 4
 winbindd
 is a daemon that is used for integrating authentication and the user database into unix.
+is a daemon that is used for integrating authentication and the user database into unix\.
 .RE
 .PP
 \fBwbinfo\fR(1)
 .RS 3n
+.RS 4
 wbinfo
 is a utility that retrieves and stores information related to winbind.
+is a utility that retrieves and stores information related to winbind\.
 .RE
 .PP
 \fBprofiles\fR(1)
 .RS 3n
+.RS 4
 profiles
 is a command-line utility that can be used to replace all occurences of a certain SID with another SID.
+is a command\-line utility that can be used to replace all occurences of a certain SID with another SID\.
 .RE
 .PP
 \fBlog2pcap\fR(1)
 .RS 3n
+.RS 4
 log2pcap
 is a utility for generating pcap trace files from Samba log files.
+is a utility for generating pcap trace files from Samba log files\.
 .RE
 .PP
 \fBvfstest\fR(1)
 .RS 3n
+.RS 4
 vfstest
 is a utility that can be used to test vfs modules.
+is a utility that can be used to test vfs modules\.
 .RE
 .PP
 \fBntlm_auth\fR(1)
 .RS 3n
+.RS 4
 ntlm_auth
 is a helper-utility for external programs wanting to do NTLM-authentication.
+is a helper\-utility for external programs wanting to do NTLM\-authentication\.
 .RE
 .PP
 \fBsmbmount\fR(8), \fBsmbumount\fR(8), \fBsmbmnt\fR(8)
 .RS 3n
+.RS 4
 smbmount,smbumount
 and
 smbmnt
 are commands that can be used to mount CIFS/SMB shares on Linux.
+are commands that can be used to mount CIFS/SMB shares on Linux\.
 .RE
 .PP
 \fBsmbcquotas\fR(1)
 .RS 3n
+.RS 4
 smbcquotas
 is a tool that can set remote QUOTA's on server with NTFS 5.
+is a tool that can set remote QUOTA\'s 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't clear enough then please visit
 http://devel.samba.org
 for information on how to file a bug report or submit a patch.
+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\'t 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.
+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.
+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.
+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.
+http://lists\.samba\.org\.
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 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.
+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
 diff -u
 format.
+http://devel\.samba\.org/
+for information on how to do it properly\. We prefer patches in
+diff \-u
+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
 \fIchange-log\fR
 in the source package for the pre-CVS changes and at
 http://cvs.samba.org/
 for the contributors to Samba post-CVS. CVS is the Open Source source code control system used by the Samba Team to develop Samba. The project would have been unmanageable without it.
+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
+\fIchange\-log\fR
+in the source package for the pre\-CVS changes and at
+http://cvs\.samba\.org/
+for the contributors to Samba post\-CVS\. CVS 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.
+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\.

branches/samba-3.0/docs/manpages/smb.conf.5

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "SMB.CONF" 5 "" "" ""
+.\"     Title: smb.conf
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: File Formats and Conventions
+.\"    Source: Samba 3.0
+.\"
+.TH "SMB\.CONF" "5" "05/21/2008" "Samba 3\.0" "File Formats and Conventions"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 smb.conf - The configuration file for the Samba suite
 …
 .PP
 The
 \fIsmb.conf\fR
 file is a configuration file for the Samba suite.
 \fIsmb.conf\fR
 contains runtime configuration information for the Samba programs. The
 \fIsmb.conf\fR
+\fIsmb\.conf\fR
+file is a configuration file for the Samba suite\.
+\fIsmb\.conf\fR
+contains runtime configuration information for the Samba programs\. The
+\fIsmb\.conf\fR
 file is designed to be configured and administered by the
 \fBswat\fR(8)
 program. The complete description of the file format and possible parameters held within are here for reference purposes.
+program\. 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
+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
+.RS 4
 .nf
 \fIname\fR = \fIvalue \fR
 .fi
 .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 (\fB;\fR) or a hash (\fB#\fR) character is ignored, as are lines containing only whitespace.
+.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
 \fB\\\fR
 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, 0/1 or true/false. Case is not significant in boolean values, but is preserved in string values. Some items such as create masks are numeric.
+\(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, 0/1 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
 \fBshare\fR). The section name is the name of the shared resource and the parameters within the section define the shares attributes.
+\(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
 \fBspecial 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).
+\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
 \fBguest\fR
 services, in which case no password is required to access them. A specified UNIX
 \fBguest 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
+\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
 \fI/home/bar\fR. The share is accessed via the share name
+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
+\fI/home/bar\fR\. The share is accessed via the share name
 foo:
+.sp
+.sp
+.RS 4
 .nf
         \fI[foo]\fR
+        path = /home/bar
+        read only = no
+        \fIpath = /home/bar\fR
+        \fIread only = no\fR
 .fi
 .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
 \fBguest ok\fR
+.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
+.sp
+.RS 4
 .nf
         \fI[aprinter]\fR
+        path = /usr/spool/public
+        read only = yes
+        printable = yes
+        guest ok = yes
+        \fIpath = /usr/spool/public\fR
+        \fIread only = yes\fR
+        \fIprintable = yes\fR
+        \fIguest ok = yes\fR
 .fi
+.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.
+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.
+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:
+.TP 3n
+\(bu
+The share name is changed from homes to the located username.
+.TP 3n
+\(bu
+If no path was given, the path is set to the user's home directory.
+.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\'s home directory\.
+.sp
+.RE
 .PP
 If you decide to use a
+\fBpath =\fR
+line in your [homes] section, it may be useful to use the %S macro. For example:
+.sp
+\fIpath =\fR
+line in your [homes] section, it may be useful to use the %S macro\. For example:
+.sp
+.RS 4
 .nf
 \fBpath = /data/pchome/%S\fR
 .fi
+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.
+.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
+\fBhomes\fR, 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
+\(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
+.RS 4
 .nf
 \fI[homes]\fR
+read only = no
+\fIread only = no\fR
 .fi
+.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
 \fBwithout a password\fR. In the very unlikely event that this is actually desirable, it is wise to also specify
 \fBread only access\fR.
+\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
 \fBbrowseable\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
 \fBbrowseable = no\fR
 in the [homes] section will hide the [homes] share but make any auto home directories visible.
+\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's 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.
+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\'s 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:
+.TP 3n
+\(bu
+.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
+.TP 3n
+\(bu
+.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
+.TP 3n
+\(bu
+If the share does not permit guest access and no username was given, the username is set to the located printer name.
+.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
+.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\.
+.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
+.RS 4
 .nf
 \fI[printers]\fR
+path = /usr/spool/public
+guest ok = yes
+printable = yes
+\fIpath = /usr/spool/public\fR
+\fIguest ok = yes\fR
+\fIprintable = yes\fR
 .fi
+.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't 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
+.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\'t 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
+.RS 4
 .nf
+alias|alias|alias|alias...
+alias|alias|alias|alias\.\.\.
 .fi
 .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 (|).
+.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 (|)\.
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBNote\fR
+Note
 .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
+to automatically obtain a list of printers\. See the
 printcap name
 option for more details.
+option for more details\.
 .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
 \fBusershares\fR
 and is controlled by a set of parameters in the [global] section of the smb.conf. The relevant parameters are :
+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 3n
 Controls if usershares can permit guest access.
+.RS 4
+Controls if usershares can permit guest access\.
 .RE
 .PP
 usershare max shares
 .RS 3n
 Maximum number of user defined shares allowed.
+.RS 4
+Maximum number of user defined shares allowed\.
 .RE
 .PP
 usershare owner only
 .RS 3n
 If set only directories owned by the sharing user can be shared.
+.RS 4
+If set only directories owned by the sharing user can be shared\.
 .RE
 .PP
 usershare path
 .RS 3n
 Points to the directory containing the user defined share definitions. The filesystem permissions on this directory control who can create user defined shares.
+.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 3n
 Comma-separated list of absolute pathnames restricting what directories can be shared. Only directories below the pathnames in this list are permitted.
+.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 3n
 Comma-separated list of absolute pathnames restricting what directories can be shared. Directories below the pathnames in this list are prohibited.
+.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 3n
 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.
+.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
 …
 .PP
 Become root:
+.sp
+.RS 4
 .nf
 mkdir /usr/local/samba/lib/usershares
 chgrp foo /usr/local/samba/lib/usershares
 chmod 1770 /usr/local/samba/lib/usershares
 .fi
+.RE
 .PP
 Then add the parameters
+.sp
+.sp
+.RS 4
 .nf
+        usershare path = /usr/local/samba/lib/usershares
+        usershare max shares = 10 # (or the desired number of shares)
+        \fIusershare path = /usr/local/samba/lib/usershares\fR
+        \fIusershare max shares = 10\fR # (or the desired number of shares)
 .fi
+.RE
+.sp
 to the global section of your
 \fIsmb.conf\fR. Members of the group foo may then manipulate the user defined shares using the following commands.
+\fIsmb\.conf\fR\. 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 3n
 To create or modify (overwrite) a user defined share.
+.RS 4
+To create or modify (overwrite) a user defined share\.
 .RE
 .PP
 net usershare delete sharename
 .RS 3n
 To delete a user defined share.
 .RE
 .PP
 net usershare list wildcard-sharename
 .RS 3n
 To list user defined shares.
 .RE
 .PP
 net usershare info wildcard-sharename
 .RS 3n
 To print information about user defined shares.
+.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.,
 \fBsecurity\fR). Some parameters are usable in all sections (e.g.,
 \fBcreate 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
 \fBG\fR
 in parentheses indicates that a parameter is specific to the [global] section. The letter
 \fBS\fR
 indicates that a parameter can be specified in a service specific section. All
 \fBS\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.
+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
 \fBpath = /tmp/%u\fR
+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
 \fBpath = /tmp/john\fR
 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:
+\(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 3n
 session username (the username that the client wanted, not necessarily the same as the one they got).
+.RS 4
+session username (the username that the client wanted, not necessarily the same as the one they got)\.
 .RE
 .PP
 %G
 .RS 3n
 primary group name of %U.
+.RS 4
+primary group name of %U\.
 .RE
 .PP
 %h
 .RS 3n
 the Internet hostname that Samba is running on.
+.RS 4
+the Internet hostname that Samba is running on\.
 .RE
 .PP
 %m
 .RS 3n
 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.
+.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 3n
 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
 \fBdual personality\fR.
+.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 3n
 the Internet name of the client machine.
+.RS 4
+the Internet name of the client machine\.
 .RE
 .PP
 %R
 .RS 3n
 the selected protocol level after protocol negotiation. It can be one of CORE, COREPLUS, LANMAN1, LANMAN2 or NT1.
+.RS 4
+the selected protocol level after protocol negotiation\. It can be one of CORE, COREPLUS, LANMAN1, LANMAN2 or NT1\.
 .RE
 .PP
 %d
 .RS 3n
 the process id of the current server process.
+.RS 4
+the process id of the current server process\.
 .RE
 .PP
 %a
 .RS 3n
 the architecture of the remote machine. It currently recognizes Samba (\fBSamba\fR), the Linux CIFS file system (\fBCIFSFS\fR), OS/2, (\fBOS2\fR), Windows for Workgroups (\fBWfWg\fR), Windows 9x/ME (\fBWin95\fR), Windows NT (\fBWinNT\fR), Windows 2000 (\fBWin2K\fR), Windows XP (\fBWinXP\fR), and Windows 2003 (\fBWin2K3\fR). Anything else will be known as
 \fBUNKNOWN\fR.
+.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), 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 3n
 the IP address of the client machine.
+.RS 4
+the IP address of the client machine\.
 .RE
 .PP
 %i
 .RS 3n
 the local IP address to which a client connected.
+.RS 4
+the local IP address to which a client connected\.
 .RE
 .PP
 %T
 .RS 3n
 the current date and time.
+.RS 4
+the current date and time\.
 .RE
 .PP
 %D
 .RS 3n
 name of the domain or workgroup of the current user.
+.RS 4
+name of the domain or workgroup of the current user\.
 .RE
 .PP
 %w
 .RS 3n
 the winbind separator.
+.RS 4
+the winbind separator\.
 .RE
 .PP
 %$(\fIenvvar\fR)
 .RS 3n
+.RS 4
 the value of the environment variable
 \fIenvar\fR.
+\fIenvar\fR\.
 .RE
 .PP
 …
 .PP
 %S
 .RS 3n
 the name of the current service, if any.
+.RS 4
+the name of the current service, if any\.
 .RE
 .PP
 %P
 .RS 3n
 the root directory of the current service, if any.
+.RS 4
+the root directory of the current service, if any\.
 .RE
 .PP
 %u
 .RS 3n
 username of the current service, if any.
+.RS 4
+username of the current service, if any\.
 .RE
 .PP
 %g
 .RS 3n
 primary group name of %u.
+.RS 4
+primary group name of %u\.
 .RE
 .PP
 %H
 .RS 3n
 the home directory of the user given by %u.
+.RS 4
+the home directory of the user given by %u\.
 .RE
 .PP
 %N
 .RS 3n
 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
 \fB--with-automount\fR
 option, this value will be the same as %L.
+.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 3n
 the path of the service's home directory, obtained from your NIS auto.map entry. The NIS auto.map entry is split up as
 %N:%p.
+.RS 4
+the path of the service\'s 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
 \fIsmb.conf\fR
 options.
+\fIsmb\.conf\fR
+options\.
 .SH "NAME MANGLING"
 .PP
 Samba supports
 name mangling
 so that DOS and Windows clients can use files that don't 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.
+so that DOS and Windows clients can use files that don\'t 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 3n
 controls whether filenames are case sensitive. If they aren't, 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 filename so setting this option to auto is that same as setting it to no for them. Default
 \fBauto\fR.
+.RS 4
+controls whether filenames are case sensitive\. If they aren\'t, 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 filename so setting this option to auto is that same as setting it to no for them\. Default
+\fIauto\fR\.
 .RE
 .PP
 default case = upper/lower
 .RS 3n
 controls what the default case is for new filenames (ie. files that don't currently exist in the filesystem). Default
 \fBlower\fR. IMPORTANT NOTE: This option will be used to modify the case of
 \fBall\fR
+.RS 4
+controls what the default case is for new filenames (ie\. files that don\'t currently exist in the filesystem)\. Default
+\fIlower\fR\. IMPORTANT NOTE: This option will be used to modify the case of
+\fIall\fR
 incoming client filenames, not just new filenames if the options
+case sensitive = yes,
+preserve case = No,
+short preserve case = No are set. This change is needed as part of the optimisations for directories containing large numbers of files.
+\fIcase sensitive = yes\fR,
+\fIpreserve case = No\fR,
+\fIshort preserve case = No\fR
+are set\. This change is needed as part of the optimisations for directories containing large numbers of files\.
 .RE
 .PP
 preserve case = yes/no
 .RS 3n
 controls whether new files (ie. files that don't currently exist in the filesystem) are created with the case that the client passes, or if they are forced to be the
+.RS 4
+controls whether new files (ie\. files that don\'t 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
 \fByes\fR.
+case\. Default
+\fIyes\fR\.
 .RE
 .PP
 short preserve case = yes/no
 .RS 3n
 controls if new files (ie. files that don't 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
+.RS 4
+controls if new files (ie\. files that don\'t 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
+case\. This option can be used with
 preserve case = yes
 to permit long filenames to retain their case, while short names are lowercased. Default
 \fByes\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.
+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 "NOTE ABOUT USERNAME/PASSWORD VALIDATION"
 .PP
 There are a number of ways in which a user can connect to a service. The server uses the following steps in determining if it will allow a connection to a specified service. If all the steps fail, the connection request is rejected. However, if one of the steps succeeds, the following steps are not checked.
+There are a number of ways in which a user can connect to a service\. The server uses the following steps in determining if it will allow a connection to a specified service\. If all the steps fail, the connection request is rejected\. However, if one of the steps succeeds, the following steps are not checked\.
 .PP
 If the service is marked
+\fBguest only = yes\fR
+and the server is running with share-level security (\fBsecurity = share\fR, steps 1 to 5 are skipped.
+.TP 3n
+.
+If the client has passed a username/password pair and that username/password pair is validated by the UNIX system's password programs, the connection is made as that username. This includes the
+\\\\server\\service%\fIusername\fR
+method of passing a username.
+.TP 3n
+.
+If the client has previously registered a username with the system and now supplies a correct password for that username, the connection is allowed.
+.TP 3n
+.
+The client's NetBIOS name and any previously used usernames are checked against the supplied password. If they match, the connection is allowed as the corresponding user.
+.TP 3n
+.
+If the client has previously validated a username/password pair with the server and the client has passed the validation token, that username is used.
+.TP 3n
+.
+If a
+\(lqguest only = yes\(rq
+and the server is running with share\-level security (\(lqsecurity = share\(rq, steps 1 to 5 are skipped\.
+.sp
+.RS 4
+\h'-04' 1.\h'+02'If the client has passed a username/password pair and that username/password pair is validated by the UNIX system\'s password programs, the connection is made as that username\. This includes the
+\e\eserver\eservice%\fIusername\fR
+method of passing a username\.
+.RE
+.sp
+.RS 4
+\h'-04' 2.\h'+02'If the client has previously registered a username with the system and now supplies a correct password for that username, the connection is allowed\.
+.RE
+.sp
+.RS 4
+\h'-04' 3.\h'+02'The client\'s NetBIOS name and any previously used usernames are checked against the supplied password\. If they match, the connection is allowed as the corresponding user\.
+.RE
+.sp
+.RS 4
+\h'-04' 4.\h'+02'If the client has previously validated a username/password pair with the server and the client has passed the validation token, that username is used\.
+.RE
+.sp
+.RS 4
+\h'-04' 5.\h'+02'If a
 user =
 field is given in the
 \fIsmb.conf\fR
 file for the service and the client has supplied a password, and that password matches (according to the UNIX system's password checking) with one of the usernames from the
+\fIsmb\.conf\fR
+file for the service and the client has supplied a password, and that password matches (according to the UNIX system\'s password checking) with one of the usernames from the
 user =
 field, the connection is made as the username in the
 user =
 line. If one of the usernames in the
+line\. If one of the usernames in the
 user =
 list begins with a
+@, that name expands to a list of names in the group of the same name.
+.TP 3n
+.
+If the service is a guest service, a connection is made as the username given in the
+@, that name expands to a list of names in the group of the same name\.
+.RE
+.sp
+.RS 4
+\h'-04' 6.\h'+02'If the service is a guest service, a connection is made as the username given in the
 guest account =
+for the service, irrespective of the supplied password.
+for the service, irrespective of the supplied password\.
+.RE
 .SH "EXPLANATION OF EACH PARAMETER"
+.PP
 abort shutdown script (G)
+.RS 3n
+.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
 shutdown script.
+\fIshutdown script\fR\.
 .sp
 If the connected user posseses the
 \fBSeRemoteShutdownPrivilege\fR, right, this command will be run as user.
 .sp
 Default:
 \fB\fIabort shutdown script\fR = "" \fR
 .sp
 Example:
 \fB\fIabort shutdown script\fR = /sbin/shutdown -c \fR
 .RE
+.PP
+\fBSeRemoteShutdownPrivilege\fR, right, this command will be run as user\.
+.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
 acl check permissions (S)
+.RS 3n
+.PP
+.RS 4
 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't 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 cannot restore such a deleted file. With this parameter set to true (the default) then smbd checks the file system permissions directly on "open for delete" and denies the request without actually deleting the file if the file system permissions would seem to deny it. This is not perfect, as it's possible a user could have deleted a file without Samba being able to check the permissions correctly, but it is close enough to Windows semantics for mostly correct behaviour. Samba will correctly check POSIX ACL semantics in this case.
 .sp
 If this parameter is set to "false" Samba doesn't check permissions on "open for delete" and allows the open. If the user doesn't 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 refersh. This is an extremely advanced protocol option which should not need to be changed. This parameter was introduced in its final form in 3.0.21, an earlier version with slightly different semantics was introduced in 3.0.20. That older version is not documented here.
 .sp
 Default:
 \fB\fIacl check permissions\fR = True \fR
 .RE
+.PP
+\fBsmbd\fR(8)does on receiving a protocol request of "open for delete" from a Windows client\. If a Windows client doesn\'t 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 cannot restore such a deleted file\. With this parameter set to true (the default) then smbd checks the file system permissions directly on "open for delete" and denies the request without actually deleting the file if the file system permissions would seem to deny it\. This is not perfect, as it\'s possible a user could have deleted a file without Samba being able to check the permissions correctly, but it is close enough to Windows semantics for mostly correct behaviour\. Samba will correctly check POSIX ACL semantics in this case\.
+.sp
+If this parameter is set to "false" Samba doesn\'t check permissions on "open for delete" and allows the open\. If the user doesn\'t 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 refersh\. This is an extremely advanced protocol option which should not need to be changed\. This parameter was introduced in its final form in 3\.0\.21, an earlier version with slightly different semantics was introduced in 3\.0\.20\. That older version is not documented here\.
+.sp
+Default:
+\fI\fIacl check permissions\fR\fR\fI = \fR\fITrue\fR\fI \fR
+.RE
 acl compatibility (S)
+.RS 3n
+This parameter specifies what OS ACL semantics should be compatible with. Possible values are
+\fBwinnt\fR
+.PP
+.RS 4
+This parameter specifies what OS ACL semantics should be compatible with\. Possible values are
+\fIwinnt\fR
 for Windows NT 4,
 \fBwin2k\fR
+\fIwin2k\fR
 for Windows 2000 and above and
 \fBauto\fR. If you specify
 \fBauto\fR, the value for this parameter will be based upon the version of the client. There should be no reason to change this parameter from the default.
 .sp
 Default:
 \fB\fIacl compatibility\fR = Auto \fR
 .sp
 Example:
 \fB\fIacl compatibility\fR = win2k \fR
 .RE
+.PP
+\fIauto\fR\. If you specify
+\fIauto\fR, the value for this parameter will be based upon the version of the client\. There should be no reason to change this parameter from the default\.
+.sp
+Default:
+\fI\fIacl compatibility\fR\fR\fI = \fR\fIAuto\fR\fI \fR
+.sp
+Example:
+\fI\fIacl compatibility\fR\fR\fI = \fR\fIwin2k\fR\fI \fR
+.RE
 acl group control (S)
+.RS 3n
+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
+\fBprimary 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 managability.
+.sp
+This parameter allows Samba to also permit delegation of the control over a point in the exported directory hierarchy in much the same was as Windows. This allows all members of a UNIX group to control the permissions on a file or directory they have group ownership on.
+.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 managability\.
+.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
+inherit owner option and also on on a share containing directories with the UNIX
+\fBsetgid bit\fR
+bit set on them, which causes new files and directories created within it to inherit the group ownership from the containing directory.
+.sp
+This is parameter has been marked deprecated in Samba 3.0.23. The same behavior is now implemented by the
+\fIinherit owner\fR
+option and also on 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 is parameter has been marked deprecated in Samba 3\.0\.23\. The same behavior is now implemented by the
 \fIdos filemode\fR
 option.
 .sp
 Default:
 \fB\fIacl group control\fR = no \fR
 .RE
+.PP
+option\.
+.sp
+Default:
+\fI\fIacl group control\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 acl map full control (S)
+.RS 3n
+.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:
 \fB\fIacl map full control\fR = True \fR
 .RE
+.PP
+\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\fITrue\fR\fI \fR
+.RE
 add group script (G)
+.RS 3n
+.PP
+.RS 4
 This is the full pathname to a script that will be run
 \fBAS ROOT\fR
+\fIAS ROOT\fR
 by
 \fBsmbd\fR(8)
 when a new group is requested. It will expand any
+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:
 \fB\fIadd group script\fR = \fR
 .sp
 Example:
 \fB\fIadd group script\fR = /usr/sbin/groupadd %g \fR
 .RE
+.PP
+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)
+.RS 3n
+.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's domain and a Unix account matching the machine's name appended with a "$" does not already exist.
+when a machine is added to Samba\'s domain and a Unix account matching the machine\'s name appended with a "$" does not already exist\.
 .sp
 This option is very similar to the
 add user script, and likewise uses the %u substitution for the account name. Do not use the %m substitution.
 .sp
 Default:
 \fB\fIadd machine script\fR = \fR
 .sp
 Example:
 \fB\fIadd machine script\fR = /usr/sbin/adduser -n -g machines -c Machine -d /var/lib/nobody -s /bin/false %u \fR
 .RE
+.PP
+\fIadd user script\fR, 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
 add port command (G)
+.RS 3n
+Samba 3.0.23 introduces 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. he script is passed two parameters:
+.RS 3n
+.TP 3n
+\(bu
+.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
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fIdevice URI\fR
 .RE
 .IP "" 3n
 The deviceURI is in the for of socket://<hostname>[:<portnumber>] or lpd://<hostname>/<queuename>.
 .sp
 Default:
 \fB\fIadd port command\fR = \fR
 .sp
 Example:
 \fB\fIadd port command\fR = /etc/samba/scripts/addport.sh \fR
 .RE
+.PP
+.sp
+.RE
+The deviceURI is in the for of socket://<hostname>[:<portnumber>] or lpd://<hostname>/<queuename>\.
+.sp
+Default:
+\fI\fIadd port command\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fIadd port command\fR\fR\fI = \fR\fI/etc/samba/scripts/addport\.sh\fR\fI \fR
+.RE
 add printer command (G)
+.RS 3n
+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
+.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
 \fIadd printer 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
 \fIsmb.conf\fR
+\fIsmb\.conf\fR
 file in order that it can be shared by
 \fBsmbd\fR(8).
+\fBsmbd\fR(8)\.
 .sp
 The
 \fIaddprinter command\fR
 is automatically invoked with the following parameter (in order):
+.RS 3n
+.TP 3n
+\(bu
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fIprinter name\fR
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fIshare name\fR
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fIport name\fR
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fIdriver name\fR
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fIlocation\fR
+.TP 3n
+\(bu
+.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
 .IP "" 3n
 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
+.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
 …
 smbd
 will reparse the
 \fI smb.conf\fR
 to determine if the share defined by the APW exists. If the sharename is still invalid, then
+\fI smb\.conf\fR
+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 "add printer command" 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't output, Samba won't reload its printer shares.
 .sp
 Default:
 \fB\fIadd printer command\fR = \fR
 .sp
 Example:
 \fB\fIadd printer command\fR = /usr/bin/addprinter \fR
 .RE
+.PP
+will return an ACCESS_DENIED error to the client\.
+.sp
+The "add printer command" 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\'t output, Samba won\'t reload its printer shares\.
+.sp
+Default:
+\fI\fIadd printer command\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fIadd printer command\fR\fR\fI = \fR\fI/usr/bin/addprinter\fR\fI \fR
+.RE
 add share command (G)
+.RS 3n
+Samba 2.2.0 introduced the ability to dynamically add and delete shares via the Windows NT 4.0 Server Manager. The
+.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
 \fIsmb.conf\fR. In order to successfully execute the
+\fIsmb\.conf\fR\. In order to successfully execute the
 \fIadd share command\fR,
 smbd
+requires that the administrator be connected using a root account (i.e. uid == 0).
+requires that the administrator be connected using a root account (i\.e\. uid == 0)\.
+.sp
+If the connected account has
+SeDiskOperatorPrivilege, scripts defined in
+\fIchange share\fR
+parameter are executed as root\.
 .sp
 When executed,
 …
 will automatically invoke the
 \fIadd share command\fR
+with five parameters.
+.RS 3n
+.TP 3n
+\(bu
+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
+\fIsmb.conf\fR
+file.
+.TP 3n
+\(bu
+\- the location of the global
+\fIsmb\.conf\fR
+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.
+.TP 3n
+\(bu
+\- 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.
+.TP 3n
+\(bu
+\- 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.
+.TP 3n
+\(bu
+\- 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
 .IP "" 3n
 This parameter is only used for add file shares. To add printer shares, see the
 addprinter command.
 .sp
 Default:
 \fB\fIadd share command\fR = \fR
 .sp
 Example:
 \fB\fIadd share command\fR = /usr/local/bin/addshare \fR
 .RE
+.PP
+Number of maximum simultaneous connections to this share\.
+.sp
+.RE
+This parameter is only used for add file shares\. To add printer shares, see the
+\fIaddprinter command\fR\.
+.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)
+.RS 3n
+.PP
+.RS 4
 This is the full pathname to a script that will be run
 \fBAS ROOT\fR
+\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
 \fBON DEMAND\fR
 when a user accesses the Samba server.
+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
 In order to use this option,
 \fBsmbd\fR(8)
 must
 \fBNOT\fR
+\fINOT\fR
 be set to
+security = share and
+add user script must be set to a full pathname for a script that will create a UNIX user given one argument of
+\fI%u\fR, which expands into the UNIX user name to create.
+\fIsecurity = share\fR
+and
+\fIadd user script\fR
+must be set to a full pathname for a script that will create a UNIX user given one argument of
+\fI%u\fR, which expands into the UNIX user name to create\.
 .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
+password server and attempts to authenticate the given user with the given password. If the authentication succeeds then
+\fIpassword server\fR
+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
+add user script is set then
+attempts to find a UNIX user in the UNIX password database to map the Windows user into\. If this lookup fails, and
+\fIadd user script\fR
+is set then
 smbd
 will call the specified script
 \fBAS ROOT\fR, expanding any
+\fIAS ROOT\fR, expanding any
 \fI%u\fR
 argument to be the user name to create.
+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.
+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
 security,
 password server,
 delete user script.
 .sp
 Default:
 \fB\fIadd user script\fR = \fR
 .sp
 Example:
 \fB\fIadd user script\fR = /usr/local/samba/bin/add_user %u \fR
 .RE
+.PP
+\fIsecurity\fR,
+\fIpassword server\fR,
+\fIdelete user script\fR\.
+.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)
+.RS 3n
+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
+.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)
 \fBAS ROOT\fR. Any
+\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.
+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:
 \fB\fIadd user to group script\fR = \fR
 .sp
 Example:
 \fB\fIadd user to group script\fR = /usr/sbin/adduser %u %g \fR
 .RE
+.PP
+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
 admin users (S)
+.RS 3n
+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.
+.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
 This parameter will not work with the
+security = share in Samba 3.0. This is by design.
+.sp
+Default:
+\fB\fIadmin users\fR = \fR
+.sp
+Example:
+\fB\fIadmin users\fR = jason \fR
+.RE
+.PP
+\fIsecurity = share\fR
+in Samba 3\.0\. This is by design\.
+.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)
+.RS 3n
+This parameter controls whether special AFS features are enabled for this share. If enabled, it assumes that the directory exported via the
+.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:
 \fB\fIafs share\fR = no \fR
 .RE
+.PP
+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 username map (G)
+.RS 3n
+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:
+\fB\fIafs username map\fR = \fR
+.sp
+Example:
+\fB\fIafs username map\fR = %u@afs.samba.org \fR
+.RE
+.PP
+.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@afs\.samba\.org\fR\fI \fR
+.RE
 aio read size (S)
+.RS 3n
+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
+  write cache size
+  aio write size
+Default:
+\fB\fIaio read size\fR = 0 \fR
+.sp
+Example:
+\fB\fIaio read size\fR = 16384 # Use asynchronous I/O for reads bigger than 16KB request size \fR
+.RE
+.PP
+.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:
+\fIwrite cache size\fR
+.sp
+Related command:
+\fIaio write size\fR
+.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 size (S)
+.RS 3n
+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
+  write cache size
+  aio read size
+Default:
+\fB\fIaio write size\fR = 0 \fR
+.sp
+Example:
+\fB\fIaio write size\fR = 16384 # Use asynchronous I/O for writes bigger than 16KB request size \fR
+.RE
+.PP
+.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:
+\fIwrite cache size\fR
+.sp
+Related command:
+\fIaio read size\fR
+.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)
+.RS 3n
+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 sytem 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't be 'turned off', but pushing it 'out of the way' should resolve the issues. Users and groups can then be assigned 'low' RIDs in arbitary-rid supporting backends.
+.sp
+Default:
+\fB\fIalgorithmic rid base\fR = 1000 \fR
+.sp
+Example:
+\fB\fIalgorithmic rid base\fR = 100000 \fR
+.RE
+.PP
+.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 sytem 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\'t be \'turned off\', but pushing it \'out of the way\' should resolve the issues\. Users and groups can then be assigned \'low\' 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)
+.RS 3n
+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:
+\fB\fIallocation roundup size\fR = 1048576 \fR
+.sp
+Example:
+\fB\fIallocation roundup size\fR = 0 # (to disable roundups) \fR
+.RE
+.PP
+.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 trusted domains (G)
+.RS 3n
+.PP
+.RS 4
 This option only takes effect when the
+security option is set to
+\fIsecurity\fR
+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 difficult.
 .sp
 Default:
 \fB\fIallow trusted domains\fR = yes \fR
 .RE
+.PP
+\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 difficult\.
+.sp
+Default:
+\fI\fIallow trusted domains\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 announce as (G)
+.RS 3n
+.PP
+.RS 4
 This specifies what type of server
 \fBnmbd\fR(8)
 will announce itself as, to a network neighborhood browse list. By default this is set to Windows NT. The valid options are : "NT Server" (which can also be written as "NT"), "NT Workstation", "Win95" or "WfW" meaning Windows NT Server, Windows NT Workstation, Windows 95 and Windows for Workgroups respectively. Do not change this parameter unless you have a specific need to stop Samba appearing as an NT server as this may prevent Samba servers from participating as browser servers correctly.
 .sp
 Default:
 \fB\fIannounce as\fR = NT Server \fR
 .sp
 Example:
 \fB\fIannounce as\fR = Win95 \fR
 .RE
+.PP
+will announce itself as, to a network neighborhood browse list\. By default this is set to Windows NT\. The valid options are : "NT Server" (which can also be written as "NT"), "NT Workstation", "Win95" or "WfW" meaning Windows NT Server, Windows NT Workstation, Windows 95 and Windows for Workgroups respectively\. Do not change this parameter unless you have a specific need to stop Samba appearing as an NT server as this may prevent Samba servers from participating as browser servers correctly\.
+.sp
+Default:
+\fI\fIannounce as\fR\fR\fI = \fR\fINT Server\fR\fI \fR
+.sp
+Example:
+\fI\fIannounce as\fR\fR\fI = \fR\fIWin95\fR\fI \fR
+.RE
 announce version (G)
+.RS 3n
+This specifies the major and minor version numbers that nmbd will use when announcing itself as a server. The default is 4.9. Do not change this parameter unless you have a specific need to set a Samba server to be a downlevel server.
+.sp
+Default:
+\fB\fIannounce version\fR = 4.9 \fR
+.sp
+Example:
+\fB\fIannounce version\fR = 2.0 \fR
+.RE
+.PP
+.PP
+.RS 4
+This specifies the major and minor version numbers that nmbd will use when announcing itself as a server\. The default is 4\.9\. Do not change this parameter unless you have a specific need to set a Samba server to be a downlevel server\.
+.sp
+Default:
+\fI\fIannounce version\fR\fR\fI = \fR\fI4\.9\fR\fI \fR
+.sp
+Example:
+\fI\fIannounce version\fR\fR\fI = \fR\fI2\.0\fR\fI \fR
+.RE
 auth methods (G)
+.RS 3n
+.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
 security. 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.
+will use when authenticating a user\. This option defaults to sensible values based on
+\fIsecurity\fR\. 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
 …
 (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),
+(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:
 \fB\fIauth methods\fR = \fR
 .sp
 Example:
 \fB\fIauth methods\fR = guest sam winbind \fR
 .RE
+.PP
+(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)
+.RS 3n
+This parameter lets you "turn off" a service. If
+.PP
+.RS 4
+This parameter lets you "turn off" a service\. If
 \fIavailable = no\fR, then
 \fBALL\fR
 attempts to connect to the service will fail. Such failures are logged.
 .sp
 Default:
 \fB\fIavailable\fR = yes \fR
 .RE
+.PP
+\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)
+.RS 3n
+This global parameter allows the Samba admin to limit what interfaces on a machine will serve SMB requests. It affects file service
+.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.
+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
+interfaces parameter.
+\fIinterfaces\fR
+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
+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
+bind interfaces only is set then
+will service name requests on all of these sockets\. If
+\fIbind interfaces only\fR
+is set then
 nmbd
+will check the source address of any packets coming in on the broadcast sockets and discard any that don't match the broadcast addresses of the interfaces in the
+interfaces parameter list. As unicast packets are received on the other sockets it allows
+will check the source address of any packets coming in on the broadcast sockets and discard any that don\'t match the broadcast addresses of the interfaces in the
+\fIinterfaces\fR
+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
+interfaces list. IP Source address spoofing does defeat this simple check, however, so it must not be used seriously as a security feature for
+nmbd.
+\fIinterfaces\fR
+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
+interfaces parameter. This restricts the networks that
+\fIinterfaces\fR
+parameter\. This restricts the networks that
 smbd
 will serve to packets coming in 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.
+will serve to packets coming in 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
+bind interfaces only is set then unless the network address
+\fB127.0.0.1\fR
+\fIbind interfaces only\fR
+is set then unless the network address
+\fI127\.0\.0\.1\fR
 is added to the
+interfaces parameter list
+\fIinterfaces\fR
+parameter list
 \fBsmbpasswd\fR(8)
 and
 \fBswat\fR(8)
 may not work as expected due to the reasons covered below.
+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
+\fBlocalhost - 127.0.0.1\fR
+address as an SMB client to issue the password change request. If
+bind interfaces only is set then unless the network address
+\fB127.0.0.1\fR
+\fIlocalhost \- 127\.0\.0\.1\fR
+address as an SMB client to issue the password change request\. If
+\fIbind interfaces only\fR
+is set then unless the network address
+\fI127\.0\.0\.1\fR
 is added to the
+interfaces parameter list then
+\fIinterfaces\fR
+parameter list then
 smbpasswd
 will fail to connect in it's default mode.
+will fail to connect in it\'s 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
+\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.
+set to the IP name of the primary interface of the local host\.
 .sp
 The
 …
 nmbd
 at the address
 \fB127.0.0.1\fR
 to determine if they are running. Not adding
 \fB127.0.0.1\fR
+\fI127\.0\.0\.1\fR
+to determine if they are running\. Not adding
+\fI127\.0\.0\.1\fR
 will cause
 smbd
 and
 nmbd
 to always show "not running" even if they really are. This can prevent
+to always show "not running" even if they really are\. This can prevent
 swat
 from starting/stopping/restarting
 smbd
 and
 nmbd.
 .sp
 Default:
 \fB\fIbind interfaces only\fR = no \fR
 .RE
+.PP
+nmbd\.
+.sp
+Default:
+\fI\fIbind interfaces only\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 blocking locks (S)
+.RS 3n
+.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.
+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:
 \fB\fIblocking locks\fR = yes \fR
 .RE
+.PP
+\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)
+.RS 3n
+.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:
 \fB\fIblock size\fR = 1024 \fR
 .sp
 Example:
 \fB\fIblock size\fR = 4096 \fR
 .RE
 .PP
+browsable
+.RS 3n
 This parameter is a synonym for browseable.
 .RE
+.PP
+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.PP
+.RS 4
+This parameter is a synonym for
+browseable\.
+.RE
 browseable (S)
+.RS 3n
+This controls whether this share is seen in the list of available shares in a net view and in the browse list.
+.sp
+Default:
+\fB\fIbrowseable\fR = yes \fR
+.RE
+.PP
+.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)
+.RS 3n
+.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:
 \fB\fIbrowse list\fR = yes \fR
 .RE
 .PP
+casesignames
+.RS 3n
 This parameter is a synonym for case sensitive.
 .RE
+.PP
+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
+casesignames.PP
+.RS 4
+This parameter is a synonym for
+case sensitive\.
+.RE
 case sensitive (S)
+.RS 3n
+.PP
+.RS 4
 See the discussion in the section
 name mangling.
 .sp
 Default:
 \fB\fIcase sensitive\fR = no \fR
 .RE
+.PP
+\fIname mangling\fR\.
+.sp
+Default:
+\fI\fIcase sensitive\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 change notify (S)
+.RS 3n
+This parameter specifies whether Samba should reply to a client's file change notify requests.
+.PP
+.RS 4
+This parameter specifies whether Samba should reply to a client\'s file change notify requests\.
 .sp
 You should never need to change this parameter
 .sp
 Default:
 \fB\fIchange notify\fR = no \fR
 .RE
+.PP
+\fI\fIchange notify\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 change share command (G)
+.RS 3n
+Samba 2.2.0 introduced the ability to dynamically add and delete shares via the Windows NT 4.0 Server Manager. The
+.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
 \fIsmb.conf\fR. In order to successfully execute the
+\fIsmb\.conf\fR\. In order to successfully execute the
 \fIchange share command\fR,
 smbd
+requires that the administrator be connected using a root account (i.e. uid == 0).
+requires that the administrator be connected using a root account (i\.e\. uid == 0)\.
+.sp
+If the connected account has
+SeDiskOperatorPrivilege, scripts defined in
+\fIchange share\fR
+parameter are executed as root\.
 .sp
 When executed,
 …
 will automatically invoke the
 \fIchange share command\fR
+with five parameters.
+.RS 3n
+.TP 3n
+\(bu
+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
+\fIsmb.conf\fR
+file.
+.TP 3n
+\(bu
+\- the location of the global
+\fIsmb\.conf\fR
+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.
+.TP 3n
+\(bu
+\- 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.
+.TP 3n
+\(bu
+\- 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.
+.TP 3n
+\(bu
+\- 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
 .IP "" 3n
 This parameter is only used modify existing file shares definitions. To modify printer shares, use the "Printers..." folder as seen when browsing the Samba host.
 .sp
 Default:
 \fB\fIchange share command\fR = \fR
 .sp
 Example:
 \fB\fIchange share command\fR = /usr/local/bin/addshare \fR
 .RE
+.PP
+Number of maximum simultaneous connections to this share\.
+.sp
+.RE
+This parameter is only used modify existing file shares 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/addshare\fR\fI \fR
+.RE
 check password script (G)
+.RS 3n
+The name of a program that can be used to check password complexity. The password is sent to the program's standrad input.
+.sp
+The program must return 0 on good password any other value otherwise. In case the password is considered weak (the program do not return 0) the user will be notified and the password change will fail.
+.sp
+Note: In the example directory there is a sample program called crackcheck that uses cracklib to checkpassword quality
+.sp
+.
+Default:
+\fB\fIcheck password script\fR = Disabled \fR
+.sp
+Example:
+\fB\fIcheck password script\fR = check password script = /usr/local/sbin/crackcheck \fR
+.RE
+.PP
+.PP
+.RS 4
+The name of a program that can be used to check password complexity\. The password is sent to the program\'s standrad input\.
+.sp
+The program must return 0 on good password any other value otherwise\. In case the password is considered weak (the program do not return 0) the user will be notified and the password change will fail\.
+.sp
+Note: In the example directory there is a sample program called crackcheck that uses cracklib to checkpassword quality\.
+.sp
+Default:
+\fI\fIcheck password script\fR\fR\fI = \fR\fIDisabled\fR\fI \fR
+.sp
+Example:
+\fI\fIcheck password script\fR\fR\fI = \fR\fIcheck password script = /usr/local/sbin/crackcheck\fR\fI \fR
+.RE
 client lanman auth (G)
+.RS 3n
+.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 it's case-insensitive nature, and the choice of algorithm. Clients without Windows 95/98 servers are advised to disable this option.
+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 it\'s 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
 …
 Likewise, if the
 client ntlmv2 auth
 parameter is enabled, then only NTLMv2 logins will be attempted.
 .sp
 Default:
 \fB\fIclient lanman auth\fR = yes \fR
 .RE
+.PP
+parameter is enabled, then only NTLMv2 logins will be attempted\.
+.sp
+Default:
+\fI\fIclient lanman auth\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 client ntlmv2 auth (G)
+.RS 3n
+.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. Many servers (including NT4 < SP4, Win9x and Samba 2.2) are not compatible with NTLMv2.
+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\. Many servers (including NT4 < SP4, Win9x and Samba 2\.2) are not compatible with NTLMv2\.
 .sp
 Similarly, if enabled, NTLMv1,
 …
 and
 client plaintext auth
 authentication will be disabled. This also disables share-level authentication.
+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 some sites (particularly those following 'best practice' security polices) only allow NTLMv2 responses, and not the weaker LM or NTLM.
 .sp
 Default:
 \fB\fIclient ntlmv2 auth\fR = no \fR
 .RE
+.PP
+client lanman auth\.
+.sp
+Note that some sites (particularly those following \'best practice\' security polices) only allow NTLMv2 responses, and not the weaker LM or NTLM\.
+.sp
+Default:
+\fI\fIclient ntlmv2 auth\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 client plaintext auth (G)
+.RS 3n
+Specifies whether a client should send a plaintext password if the server does not support encrypted passwords.
+.sp
+Default:
+\fB\fIclient plaintext auth\fR = yes \fR
+.RE
+.PP
+.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\fIyes\fR\fI \fR
+.RE
 client schannel (G)
+.RS 3n
+This controls whether the client offers or even demands the use of the netlogon schannel.
+client schannel = no does not offer the schannel,
+client schannel = auto offers the schannel but does not enforce it, and
+client schannel = yes denies access if the server is not able to speak netlogon schannel.
+.sp
+Default:
+\fB\fIclient schannel\fR = auto \fR
+.sp
+Example:
+\fB\fIclient schannel\fR = yes \fR
+.RE
+.PP
+.PP
+.RS 4
+This controls whether the client offers or even demands the use of the netlogon schannel\.
+\fIclient schannel = no\fR
+does not offer the schannel,
+\fIclient schannel = auto\fR
+offers the schannel but does not enforce it, and
+\fIclient schannel = yes\fR
+denies access if the server is not able to speak netlogon schannel\.
+.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)
+.RS 3n
+This controls whether the client offers or requires the server it talks to to use SMB signing. Possible values are
+\fBauto\fR,
+\fBmandatory\fR
+.PP
+.RS 4
+This controls whether the client offers or requires the server it talks to to use SMB signing\. Possible values are
+\fIauto\fR,
+\fImandatory\fR
 and
 \fBdisabled\fR.
 .sp
 When set to auto, SMB signing is offered, but not enforced. When set to mandatory, SMB signing is required and if set to disabled, SMB signing is not offered either.
 .sp
 Default:
 \fB\fIclient signing\fR = auto \fR
 .RE
+.PP
+\fIdisabled\fR\.
+.sp
+When set to auto, SMB signing is offered, but not enforced\. 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\fIauto\fR\fI \fR
+.RE
 client use spnego (G)
+.RS 3n
+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:
+\fB\fIclient use spnego\fR = yes \fR
+.RE
+.PP
+.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
 comment (S)
+.RS 3n
+.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.
+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
+server string parameter.
+.sp
+Default:
+\fB\fIcomment\fR = # No comment \fR
+.sp
+Example:
+\fB\fIcomment\fR = Fred's Files \fR
+.RE
+.PP
+\fIserver string\fR
+parameter\.
+.sp
+Default:
+\fI\fIcomment\fR\fR\fI = \fR\fI # No comment\fR\fI \fR
+.sp
+Example:
+\fI\fIcomment\fR\fR\fI = \fR\fIFred\'s Files\fR\fI \fR
+.RE
 config file (G)
+.RS 3n
+.PP
+.RS 4
 This allows you to override the config file to use, instead of the default (usually
 \fIsmb.conf\fR). 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't exist then it won't be loaded (allowing you to special case the config files of just a few clients).
 .sp
 \fBNo default\fR
 .sp
 Example:
 \fB\fIconfig file\fR = /usr/local/samba/lib/smb.conf.%m \fR
 .RE
+.PP
+\fIsmb\.conf\fR)\. 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\'t exist then it won\'t 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)
+.RS 3n
+This parameter allows you to "clone" service entries. The specified service is simply duplicated under the current service's name. Any parameters specified in the current section will override those in the section being copied.
+.sp
+This feature lets you set up a 'template' 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:
+\fB\fIcopy\fR = \fR
+.sp
+Example:
+\fB\fIcopy\fR = otherservice \fR
+.RE
+.PP
+create mode
+.RS 3n
+This parameter is a synonym for create mask.
+.RE
+.PP
+.PP
+.RS 4
+This parameter allows you to "clone" service entries\. The specified service is simply duplicated under the current service\'s name\. Any parameters specified in the current section will override those in the section being copied\.
+.sp
+This feature lets you set up a \'template\' 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 mode.PP
+.RS 4
+This parameter is a synonym for
+create mask\.
+.RE
 create mask (S)
+.RS 3n
+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 'AND'ed with this parameter. This parameter may be thought of as a bit-wise MASK for the UNIX modes of a file. Any bit
+\fBnot\fR
+set here will be removed from the modes set on a file when it is created.
+.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 \'AND\'ed 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
 …
 and
 other
+write and execute bits from the UNIX modes.
+.sp
+Following this Samba will bit-wise 'OR' the UNIX mode created from this parameter with the value of the
+force create mode parameter which is set to 000 by default.
+.sp
+This parameter does not affect directory masks. See the parameter
+directory mask for details.
+.sp
+Note that this parameter does not apply to permissions set by Windows NT/2000 ACL editors. If the administrator wishes to enforce a mask on access control lists also, they need to set the
+security mask.
+.sp
+Default:
+\fB\fIcreate mask\fR = 0744 \fR
+.sp
+Example:
+\fB\fIcreate mask\fR = 0775 \fR
+.RE
+.PP
+write and execute bits from the UNIX modes\.
+.sp
+Following this Samba will bit\-wise \'OR\' the UNIX mode created from this parameter with the value of the
+\fIforce create mode\fR
+parameter which is set to 000 by default\.
+.sp
+This parameter does not affect directory masks\. See the parameter
+\fIdirectory mask\fR
+for details\.
+.sp
+Note that this parameter does not apply to permissions set by Windows NT/2000 ACL editors\. If the administrator wishes to enforce a mask on access control lists also, they need to set the
+\fIsecurity mask\fR\.
+.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)
+.RS 3n
+.PP
+.RS 4
 This stands for
 \fBclient-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.
+\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
 csc policy = disable.
 .sp
 Default:
 \fB\fIcsc policy\fR = manual \fR
 .sp
 Example:
 \fB\fIcsc policy\fR = programs \fR
 .RE
+.PP
+\fIcsc policy = disable\fR\.
+.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
 cups options (S)
+.RS 3n
+.PP
+.RS 4
 This parameter is only applicable if
+printing 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' Manual"). You can also pass any printer specific option (as listed in "lpoptions -d printername -l") valid for the target queue.
+\fIprinting\fR
+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\' 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
 …
 if your CUPS server
 \fIerror_log\fR
 file contains messages such as "Unsupported format 'application/octet-stream'" when printing from a Windows client through Samba. It is no longer necessary to enable system wide raw printing in
 \fI/etc/cups/mime.{convs,types}\fR.
 .sp
 Default:
 \fB\fIcups options\fR = "" \fR
 .sp
 Example:
 \fB\fIcups options\fR = "raw,media=a4,job-sheets=secret,secret" \fR
 .RE
+.PP
+file contains messages such as "Unsupported format \'application/octet\-stream\'" when printing from a Windows client through Samba\. It is no longer necessary to enable system wide raw printing in
+\fI/etc/cups/mime\.{convs,types}\fR\.
+.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)
+.RS 3n
+.PP
+.RS 4
 This parameter is only applicable if
+printing is set to
+\fBcups\fR.
+\fIprinting\fR
+is set to
+\fBcups\fR\.
 .sp
 If set, this option overrides the ServerName option in the CUPS
 \fIclient.conf\fR. 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:
 \fB\fIcups server\fR = "" \fR
 .sp
 Example:
 \fB\fIcups server\fR = mycupsserver \fR
 .sp
 Example:
 \fB\fIcups server\fR = mycupsserver:1631 \fR
 .RE
+.PP
+\fIclient\.conf\fR\. 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
 deadtime (G)
+.RS 3n
+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's 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:
+\fB\fIdeadtime\fR = 0 \fR
+.sp
+Example:
+\fB\fIdeadtime\fR = 15 \fR
+.RE
+.PP
+.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\'s 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 hires timestamp (G)
+.RS 3n
+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.
+.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
+debug timestamp must be on for this to have an effect.
+.sp
+Default:
+\fB\fIdebug hires timestamp\fR = no \fR
+.RE
+.PP
+\fIdebug timestamp\fR
+must be on for this to have an effect\.
+.sp
+Default:
+\fI\fIdebug hires timestamp\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 debug pid (G)
+.RS 3n
+.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.
+\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
+debug timestamp must be on for this to have an effect.
+.sp
+Default:
+\fB\fIdebug pid\fR = no \fR
+.RE
+.PP
+\fIdebug timestamp\fR
+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)
+.RS 3n
+.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
+debug timestamp parameter. This gives timestamps to the messages without adding an additional line.
+\fIdebug timestamp\fR
+parameter\. This gives timestamps to the messages without adding an additional line\.
 .sp
 Note that this parameter overrides the
+debug timestamp parameter.
+.sp
+Default:
+\fB\fIdebug prefix timestamp\fR = no \fR
+.RE
+.PP
+timestamp logs
+.RS 3n
+This parameter is a synonym for debug timestamp.
+.RE
+.PP
+\fIdebug timestamp\fR
+parameter\.
+.sp
+Default:
+\fI\fIdebug prefix timestamp\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
+timestamp logs.PP
+.RS 4
+This parameter is a synonym for
+debug timestamp\.
+.RE
 debug timestamp (G)
+.RS 3n
+Samba debug log messages are timestamped by default. If you are running at a high
+debug level these timestamps can be distracting. This boolean parameter allows timestamping to be turned off.
+.sp
+Default:
+\fB\fIdebug timestamp\fR = yes \fR
+.RE
+.PP
+.PP
+.RS 4
+Samba debug log messages are timestamped by default\. If you are running at a high
+\fIdebug level\fR
+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)
+.RS 3n
+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.
+.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
+debug timestamp must be on for this to have an effect.
+.sp
+Default:
+\fB\fIdebug uid\fR = no \fR
+.RE
+.PP
+\fIdebug timestamp\fR
+must be on for this to have an effect\.
+.sp
+Default:
+\fI\fIdebug uid\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 default case (S)
+.RS 3n
+.PP
+.RS 4
 See the section on
+name mangling. Also note the
+short preserve case parameter.
+.sp
+Default:
+\fB\fIdefault case\fR = lower \fR
+.RE
+.PP
+\fIname mangling\fR\. Also note the
+\fIshort preserve case\fR
+parameter\.
+.sp
+Default:
+\fI\fIdefault case\fR\fR\fI = \fR\fIlower\fR\fI \fR
+.RE
 default devmode (S)
+.RS 3n
+.PP
+.RS 4
 This parameter is only applicable to
+printable 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's Explorer.exe with a NULL devmode. However, other printer drivers can cause the client's 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
+\fIprintable\fR
+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\'s Explorer\.exe with a NULL devmode\. However, other printer drivers can cause the client\'s 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.
+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:
 \fB\fIdefault devmode\fR = yes \fR
 .RE
 .PP
+default
+.RS 3n
 This parameter is a synonym for default service.
 .RE
+.PP
+MSDN documentation\.
+.sp
+Default:
+\fI\fIdefault devmode\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
+default.PP
+.RS 4
+This parameter is a synonym for
+default service\.
+.RE
 default service (G)
+.RS 3n
+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
+\fBNOT\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.
+.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
+guest ok,
+read-only service.
+\fIguest ok\fR,
+\fIread\-only\fR
+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:
 \fB\fIdefault service\fR = \fR
 .sp
 Example:
 \fB\fIdefault service\fR = pub \fR
 .RE
+.PP
+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)
+.RS 3n
+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:
+\fB\fIdefer sharing violations\fR = True \fR
+.RE
+.PP
+.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\fITrue\fR\fI \fR
+.RE
 delete group script (G)
+.RS 3n
+.PP
+.RS 4
 This is the full pathname to a script that will be run
 \fBAS ROOT\fR
+\fIAS ROOT\fR
 \fBsmbd\fR(8)
 when a group is requested to be deleted. It will expand any
+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:
 \fB\fIdelete group script\fR = \fR
 .RE
+.PP
+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)
+.RS 3n
+With the introduction of MS-RPC based printer support for Windows NT/2000 clients in Samba 2.2, it is now possible to delete 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 underlying printing system. The
+deleteprinter command defines a script to be run which will perform the necessary operations for removing the printer from the print system and from
+\fIsmb.conf\fR.
+.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 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 underlying printing system\. The
+\fIdeleteprinter command\fR
+defines a script to be run which will perform the necessary operations for removing the printer from the print system and from
+\fIsmb\.conf\fR\.
 .sp
 The
+deleteprinter command is automatically called with only one parameter:
+printer name.
+\fIdeleteprinter command\fR
+is automatically called with only one parameter:
+\fIprinter name\fR\.
 .sp
 Once the
+deleteprinter command has been executed,
+\fIdeleteprinter command\fR
+has been executed,
 smbd
 will reparse the
 \fI smb.conf\fR
 to associated printer no longer exists. If the sharename is still valid, then
+\fI smb\.conf\fR
+to associated printer no longer exists\. If the sharename is still valid, then
 smbd
 will return an ACCESS_DENIED error to the client.
 .sp
 Default:
 \fB\fIdeleteprinter command\fR = \fR
 .sp
 Example:
 \fB\fIdeleteprinter command\fR = /usr/bin/removeprinter \fR
 .RE
+.PP
+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)
+.RS 3n
+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:
+\fB\fIdelete readonly\fR = no \fR
+.RE
+.PP
+.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)
+.RS 3n
+Samba 2.2.0 introduced the ability to dynamically add and delete shares via the Windows NT 4.0 Server Manager. The
+.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
 \fIsmb.conf\fR. In order to successfully execute the
+\fIsmb\.conf\fR\. In order to successfully execute the
 \fIdelete share command\fR,
 smbd
+requires that the administrator be connected using a root account (i.e. uid == 0).
+requires that the administrator be connected using a root account (i\.e\. uid == 0)\.
+.sp
+If the connected account has
+SeDiskOperatorPrivilege, scripts defined in
+\fIchange share\fR
+parameter are executed as root\.
 .sp
 When executed,
 …
 will automatically invoke the
 \fIdelete share command\fR
+with two parameters.
+.RS 3n
+.TP 3n
+\(bu
+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
+\fIsmb.conf\fR
+file.
+.TP 3n
+\(bu
+\- the location of the global
+\fIsmb\.conf\fR
+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
 .IP "" 3n
 This parameter is only used to remove file shares. To delete printer shares, see the
 deleteprinter command.
 .sp
 Default:
 \fB\fIdelete share command\fR = \fR
 .sp
 Example:
 \fB\fIdelete share command\fR = /usr/local/bin/delshare \fR
 .RE
+.PP
+\- the name of the existing service\.
+.sp
+.RE
+This parameter is only used to remove file shares\. To delete printer shares, see the
+\fIdeleteprinter command\fR\.
+.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)
+.RS 3n
+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
+.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)
 \fBAS ROOT\fR. Any
+\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:
 \fB\fIdelete user from group script\fR = \fR
 .sp
 Example:
 \fB\fIdelete user from group script\fR = /usr/sbin/deluser %u %g \fR
 .RE
+.PP
+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)
+.RS 3n
+.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 'User Manager for Domains' or
 rpcclient.
 .sp
 This script should delete the given UNIX username.
 .sp
 Default:
 \fB\fIdelete user script\fR = \fR
 .sp
 Example:
 \fB\fIdelete user script\fR = /usr/local/samba/bin/del_user %u \fR
 .RE
+.PP
+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 \'User Manager for Domains\' 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)
+.RS 3n
+.PP
+.RS 4
 This option is used when Samba is attempting to delete a directory that contains one or more vetoed directories (see the
+veto files option). If this option is set to
+\fIveto files\fR
+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.
+(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.
 \fI.AppleDouble\fR)
+\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\.
+\fI\.AppleDouble\fR)
 .sp
 Setting
+delete veto files = yes 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:
+\fB\fIdelete veto files\fR = no \fR
+.RE
+.PP
+\fIdelete veto files = yes\fR
+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)
+.RS 3n
+.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
+dfree command scripts increasing the load.
+.sp
+By default this parameter is zero, meaning no caching will be done.
+.sp
+\fBNo default\fR
+.sp
+Example:
+\fB\fIdfree cache time\fR = dfree cache time = 60 \fR
+.RE
+.PP
+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
+\fIdfree command\fR
+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\fIdfree cache time = 60\fR\fI \fR
+.RE
 dfree command (S)
+.RS 3n
+.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
+dfree cache time 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
+\fI./\fR. 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.
+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
+\fIdfree cache time\fR
+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
+\fI\./\fR\. 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
 \fBNOT\fR
+\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
+.sp
+.RS 4
 .nf
 #!/bin/sh
+df $1 | tail -1 | awk '{print $2" "$4}'
+df $1 | tail \-1 | awk \'{print $(NF\-4),$(NF\-2)}\'
 .fi
+.RE
+.sp
 or perhaps (on Sys V based systems):
+.sp
+.sp
+.RS 4
 .nf
 #!/bin/sh
+/usr/bin/df -k $1 | tail -1 | awk '{print $3" "$5}'
+/usr/bin/df \-k $1 | tail \-1 | awk \'{print $3" "$5}\'
 .fi
+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
+\fBNo default\fR
+.sp
+Example:
+\fB\fIdfree command\fR = /usr/local/samba/bin/dfree \fR
+.RE
+.PP
+directory mode
+.RS 3n
+This parameter is a synonym for directory mask.
+.RE
+.PP
+.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
+directory mode.PP
+.RS 4
+This parameter is a synonym for
+directory mask\.
+.RE
 directory mask (S)
+.RS 3n
+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 'AND'ed with this parameter. This parameter may be thought of as a bit-wise MASK for the UNIX modes of a directory. Any bit
+\fBnot\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 'group' and 'other' write bits from the UNIX mode, allowing only the user who owns the directory to modify it.
+.sp
+Following this Samba will bit-wise 'OR' the UNIX mode created from this parameter with the value of the
+force directory mode parameter. This parameter is set to 000 by default (i.e. no extra mode bits are added).
+.sp
+Note that this parameter does not apply to permissions set by Windows NT/2000 ACL editors. If the administrator wishes to enforce a mask on access control lists also, they need to set the
+directory security mask.
+.sp
+Default:
+\fB\fIdirectory mask\fR = 0755 \fR
+.sp
+Example:
+\fB\fIdirectory mask\fR = 0775 \fR
+.RE
+.PP
+.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 \'AND\'ed 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 \'group\' and \'other\' write bits from the UNIX mode, allowing only the user who owns the directory to modify it\.
+.sp
+Following this Samba will bit\-wise \'OR\' the UNIX mode created from this parameter with the value of the
+\fIforce directory mode\fR
+parameter\. This parameter is set to 000 by default (i\.e\. no extra mode bits are added)\.
+.sp
+Note that this parameter does not apply to permissions set by Windows NT/2000 ACL editors\. If the administrator wishes to enforce a mask on access control lists also, they need to set the
+\fIdirectory security mask\fR\.
+.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 security mask (S)
+.RS 3n
+This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a directory using the native NT security dialog box.
+.sp
+This parameter is applied as a mask (AND'ed with) to the changed permission bits, thus preventing any bits not in this mask from being modified. Make sure not to mix up this parameter with
+force directory security mode, which works similar like this one but uses logical OR instead of AND. Essentially, zero bits in this mask may be treated as a set of bits the user is not allowed to change.
+.sp
+If not set explicitly this parameter is set to 0777 meaning a user is allowed to modify all the user/group/world permissions on a directory.
+.sp
+\fBNote\fR
+that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. Administrators of most normal systems will probably want to leave it as the default of
+\fB0777\fR.
+.sp
+Default:
+\fB\fIdirectory security mask\fR = 0777 \fR
+.sp
+Example:
+\fB\fIdirectory security mask\fR = 0700 \fR
+.RE
+.PP
+.PP
+.RS 4
+This parameter controls what UNIX permission bits will be set when a Windows NT client is manipulating the UNIX permission on a directory using the native NT security dialog box\.
+.sp
+This parameter is applied as a mask (AND\'ed with) to the incoming permission bits, thus resetting any bits not in this mask\. Make sure not to mix up this parameter with
+\fIforce directory security mode\fR, which works similar like this one but uses logical OR instead of AND\. Essentially, zero bits in this mask are a set of bits that will always be set to zero\.
+.sp
+Essentially, all bits set to zero in this mask will result in setting to zero the corresponding bits on the file permissions regardless of the previous status of this bits on the file\.
+.sp
+If not set explicitly this parameter is set to 0777 meaning a user is allowed to set all the user/group/world permissions on a directory\.
+.sp
+\fINote\fR
+that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems\. Administrators of most normal systems will probably want to leave it as the default of
+\fB0777\fR\.
+.sp
+Default:
+\fI\fIdirectory security mask\fR\fR\fI = \fR\fI0777\fR\fI \fR
+.sp
+Example:
+\fI\fIdirectory security mask\fR\fR\fI = \fR\fI0700\fR\fI \fR
+.RE
 disable netbios (G)
+.RS 3n
+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.
+.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\.
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBNote\fR
+Clients that only support netbios won't be able to see your samba server when netbios support is disabled.
+Default:
+\fB\fIdisable netbios\fR = no \fR
+.RE
+.PP
+Note
+Clients that only support netbios won\'t be able to see your samba server when netbios support is disabled\.
+Default:
+\fI\fIdisable netbios\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 disable spoolss (G)
+.RS 3n
+Enabling this parameter will disable Samba's support for the SPOOLSS set of MS-RPC's 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 capability of Windows NT/2000 clients to download print drivers from the Samba host upon demand.
+\fBBe very careful about enabling this parameter.\fR
+.sp
+Default:
+\fB\fIdisable spoolss\fR = no \fR
+.RE
+.PP
+.PP
+.RS 4
+Enabling this parameter will disable Samba\'s support for the SPOOLSS set of MS\-RPC\'s 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 capability of Windows NT/2000 clients to download print drivers from the Samba host upon demand\.
+\fIBe very careful about enabling this parameter\.\fR
+.sp
+Default:
+\fI\fIdisable spoolss\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 display charset (G)
+.RS 3n
+Specifies the charset that samba will use to print messages to stdout and stderr. The default value is "LOCALE", which means automatically set, depending on the current locale. The value should generally be the same as the value of the parameter
+unix charset.
+.sp
+Default:
+\fB\fIdisplay charset\fR = "LOCALE" or "ASCII" (depending on the system) \fR
+.sp
+Example:
+\fB\fIdisplay charset\fR = UTF8 \fR
+.RE
+.PP
+.PP
+.RS 4
+Specifies the charset that samba will use to print messages to stdout and stderr\. The default value is "LOCALE", which means automatically set, depending on the current locale\. The value should generally be the same as the value of the parameter
+\fIunix charset\fR\.
+.sp
+Default:
+\fI\fIdisplay charset\fR\fR\fI = \fR\fI"LOCALE" or "ASCII" (depending on the system)\fR\fI \fR
+.sp
+Example:
+\fI\fIdisplay charset\fR\fR\fI = \fR\fIUTF8\fR\fI \fR
+.RE
 dmapi support (S)
 .RS 3n
+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
 .sp
 Default:
 \fB\fIdmapi support\fR = no \fR
 .RE
+.PP
+.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
+.sp
+Default:
+\fI\fIdmapi support\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 dns proxy (G)
+.RS 3n
+.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.
+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:
 \fB\fIdns proxy\fR = yes \fR
 .RE
+.PP
+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
 domain logons (G)
+.RS 3n
+.PP
+.RS 4
 If set to
 \fByes\fR, the Samba server will provide the netlogon service for Windows 9X network logons for the
+workgroup 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:
+\fB\fIdomain logons\fR = no \fR
+.RE
+.PP
+\fIworkgroup\fR
+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)
+.RS 3n
+.PP
+.RS 4
 Tell
 \fBsmbd\fR(8)
 to enable WAN-wide browse list collation. Setting this option causes
+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
+workgroup. Local master browsers in the same
+workgroup on broadcast-isolated subnets will give this
+\fIworkgroup\fR\. Local master browsers in the same
+\fIworkgroup\fR
+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.
+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
+workgroup specific special NetBIOS name that identifies them as domain master browsers for that
+workgroup 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
+\fIworkgroup\fR
+specific special NetBIOS name that identifies them as domain master browsers for that
+\fIworkgroup\fR
+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
+workgroup before a Windows NT PDC is able to do so then cross subnet browsing will behave strangely and may fail.
+\fIworkgroup\fR
+before a Windows NT PDC is able to do so then cross subnet browsing will behave strangely and may fail\.
 .sp
 If
+domain logons = yes, then the default behavior is to enable the
+domain master parameter. If
+domain logons is not enabled (the default setting), then neither will
+domain master be enabled by default.
+\fIdomain logons = yes\fR, then the default behavior is to enable the
+\fIdomain master\fR
+parameter\. If
+\fIdomain logons\fR
+is not enabled (the default setting), then neither will
+\fIdomain master\fR
+be enabled by default\.
 .sp
 When
+domain logons = Yes the default setting for this parameter is Yes, with the result that Samba will be a PDC. If
+domain master = No, Samba will function as a BDC. In general, this parameter should be set to 'No' only on a BDC.
+.sp
+Default:
+\fB\fIdomain master\fR = auto \fR
+.RE
+.PP
+\fIdomain logons = Yes\fR
+the default setting for this parameter is Yes, with the result that Samba will be a PDC\. If
+\fIdomain master = No\fR, Samba will function as a BDC\. In general, this parameter should be set to \'No\' only on a BDC\.
+.sp
+Default:
+\fI\fIdomain master\fR\fR\fI = \fR\fIauto\fR\fI \fR
+.RE
 dont descend (S)
+.RS 3n
+There are certain directories on some systems (e.g., the
+.PP
+.RS 4
+There are certain directories on some systems (e\.g\., the
 \fI/proc\fR
 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
 \fI ./proc\fR
+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
+\fI \./proc\fR
 instead of just
 \fI/proc\fR. Experimentation is the best policy :-)
 .sp
 Default:
 \fB\fIdont descend\fR = \fR
 .sp
 Example:
 \fB\fIdont descend\fR = /proc,/dev \fR
 .RE
+.PP
+\fI/proc\fR\. 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)
+.RS 3n
+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
+.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
 \fBNo default\fR
 .RE
+.PP
+to check the default on your system\.
+.sp
+\fINo default\fR
+.RE
 dos filemode (S)
+.RS 3n
+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) 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 group is only granted read access. Ownership of the file/directory may also be changed.
+.sp
+Default:
+\fB\fIdos filemode\fR = no \fR
+.RE
+.PP
+.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) 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 group is only granted read access\. Ownership of the file/directory may also be changed\.
+.sp
+Default:
+\fI\fIdos filemode\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 dos filetime resolution (S)
+.RS 3n
+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 Visual C++ will keep reporting the file has changed. Setting this option causes the two timestamps to match, and Visual C++ is happy.
+.sp
+Default:
+\fB\fIdos filetime resolution\fR = no \fR
+.RE
+.PP
+.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 Visual C++ will keep reporting the file has changed\. Setting this option causes the two timestamps to match, and Visual C++ is happy\.
+.sp
+Default:
+\fI\fIdos filetime resolution\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 dos filetimes (S)
+.RS 3n
+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 runs with POSIX semantics and refuses to change the timestamp on a file if the user
+.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 runs with POSIX semantics and refuses to change the timestamp on a file if the user
 smbd
 is acting on behalf of is not the file owner. Setting this option to
+is acting on behalf of is not the file owner\. Setting this option to
 \fB yes\fR
 allows DOS semantics and
 \fBsmbd\fR(8)
 will change the file timestamp as DOS requires. 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:
 \fB\fIdos filetimes\fR = yes \fR
 .RE
+.PP
+will change the file timestamp as DOS requires\. 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
 ea support (S)
+.RS 3n
+.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:
 \fB\fIea support\fR = no \fR
 .RE
+.PP
+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)
+.RS 3n
+Hosts running the "Advanced Server for Unix (ASU)" product require some special accomodations such as creating a builting [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:
+\fB\fIenable asu support\fR = no \fR
+.RE
+.PP
+.PP
+.RS 4
+Hosts running the "Advanced Server for Unix (ASU)" product require some special accomodations such as creating a builting [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 privileges (G)
+.RS 3n
+.PP
+.RS 4
 This 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:
 \fB\fIenable privileges\fR = yes \fR
 .RE
+.PP
+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
 encrypt passwords (G)
+.RS 3n
+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.
+.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
 …
 \fBsmbpasswd\fR(8)
 program for information on how to set up and maintain this file), or set the
+security = [server|domain|ads] parameter which causes
+\fIsecurity = [server|domain|ads]\fR
+parameter which causes
 smbd
 to authenticate against another server.
 .sp
 Default:
 \fB\fIencrypt passwords\fR = yes \fR
 .RE
+.PP
+to authenticate against another server\.
+.sp
+Default:
+\fI\fIencrypt passwords\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 enhanced browsing (G)
+.RS 3n
+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:
+\fB\fIenhanced browsing\fR = yes \fR
+.RE
+.PP
+.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)
+.RS 3n
+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
+.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:
 \fB\fIenumports command\fR = \fR
 .sp
 Example:
 \fB\fIenumports command\fR = /usr/bin/listports \fR
 .RE
+.PP
+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)
+.RS 3n
+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
+\fI$(lockdir)/eventlog\fR.
+.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
+\fI$(lockdir)/eventlog\fR\.
 .sp
 The administrator must use an external process to parse the normal Unix logs such as
 \fI/var/log/messages\fR
 and write then entries to the eventlog tdb files. Refer to the eventlogadm(8) utility for how to write eventlog entries.
 .sp
 Default:
 \fB\fIeventlog list\fR = \fR
 .sp
 Example:
 \fB\fIeventlog list\fR = Security Application Syslog Apache \fR
 .RE
+.PP
+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)
+.RS 3n
+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 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's 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 expected.
+.sp
+Default:
+\fB\fIfake directory create times\fR = no \fR
+.RE
+.PP
+.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 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\'s 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 expected\.
+.sp
+Default:
+\fI\fIfake directory create times\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 fake oplocks (S)
+.RS 3n
+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.
+.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.
+will always grant oplock requests no matter how many clients are using the file\.
 .sp
 It is generally much better to use the real
+oplocks 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:
+\fB\fIfake oplocks\fR = no \fR
+.RE
+.PP
+\fIoplocks\fR
+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)
+.RS 3n
+.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
+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
+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
 \fI/etc/passwd\fR
 in their home directory for instance. However it will slow filename lookups down slightly.
 .sp
 This option is enabled (i.e.
+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:
 \fB\fIfollow symlinks\fR = yes \fR
 .RE
+.PP
+will follow symbolic links) by default\.
+.sp
+Default:
+\fI\fIfollow symlinks\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 force create mode (S)
+.RS 3n
+.PP
+.RS 4
 This parameter specifies a set of UNIX mode bit permissions that will
 \fBalways\fR
 be set on a file created by Samba. This is done by bitwise 'OR'ing these bits onto the mode bits of a file that is being created or having its permissions changed. The default for this parameter is (in octal) 000. The modes in this parameter are bitwise 'OR'ed onto the file mode after the mask set in the
+\fIalways\fR
+be set on a file created by Samba\. This is done by bitwise \'OR\'ing these bits onto the mode bits of a file that is being created or having its permissions changed\. The default for this parameter is (in octal) 000\. The modes in this parameter are bitwise \'OR\'ed onto the file mode after the mask set in the
 \fIcreate mask\fR
 parameter is applied.
 .sp
 The example below would force all created files to have read and execute permissions set for 'group' and 'other' as well as the read/write/execute bits set for the 'user'.
 .sp
 Default:
 \fB\fIforce create mode\fR = 000 \fR
 .sp
 Example:
 \fB\fIforce create mode\fR = 0755 \fR
 .RE
+.PP
+parameter is applied\.
+.sp
+The example below would force all created files to have read and execute permissions set for \'group\' and \'other\' as well as the read/write/execute bits set for the \'user\'\.
+.sp
+Default:
+\fI\fIforce create mode\fR\fR\fI = \fR\fI000\fR\fI \fR
+.sp
+Example:
+\fI\fIforce create mode\fR\fR\fI = \fR\fI0755\fR\fI \fR
+.RE
 force directory mode (S)
+.RS 3n
+.PP
+.RS 4
 This parameter specifies a set of UNIX mode bit permissions that will
 \fBalways\fR
 be set on a directory created by Samba. This is done by bitwise 'OR'ing 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
+\fIalways\fR
+be set on a directory created by Samba\. This is done by bitwise \'OR\'ing 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 'group' and 'other' as well as the read/write/execute bits set for the 'user'.
 .sp
 Default:
 \fB\fIforce directory mode\fR = 000 \fR
 .sp
 Example:
 \fB\fIforce directory mode\fR = 0755 \fR
 .RE
+.PP
+is applied\.
+.sp
+The example below would force all created directories to have read and execute permissions set for \'group\' and \'other\' as well as the read/write/execute bits set for the \'user\'\.
+.sp
+Default:
+\fI\fIforce directory mode\fR\fR\fI = \fR\fI000\fR\fI \fR
+.sp
+Example:
+\fI\fIforce directory mode\fR\fR\fI = \fR\fI0755\fR\fI \fR
+.RE
 force directory security mode (S)
+.RS 3n
+This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a directory using the native NT security dialog box.
+.sp
+This parameter is applied as a mask (OR'ed with) to the changed permission bits, thus forcing any bits in this mask that the user may have modified to be on. Make sure not to mix up this parameter with
+directory security mask, which works in a similar manner to this one, but uses a logical AND instead of an OR.
+.sp
+Essentially, this mask may be treated as a set of bits that, when modifying security on a directory, to will enable (1) any flags that are off (0) but which the mask has set to on (1).
+.sp
+If not set explicitly this parameter is 0000, which allows a user to modify all the user/group/world permissions on a directory without restrictions.
+.PP
+.RS 4
+This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a directory using the native NT security dialog box\.
+.sp
+This parameter is applied as a mask (OR\'ed with) to the changed permission bits, thus forcing any bits in this mask that the user may have modified to be on\. Make sure not to mix up this parameter with
+\fIdirectory security mask\fR, which works in a similar manner to this one, but uses a logical AND instead of an OR\.
+.sp
+Essentially, this mask may be treated as a set of bits that, when modifying security on a directory, to will enable (1) any flags that are off (0) but which the mask has set to on (1)\.
+.sp
+If not set explicitly this parameter is 0000, which allows a user to modify all the user/group/world permissions on a directory without restrictions\.
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBNote\fR
+Users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. Administrators of most normal systems will probably want to leave it set as 0000.
+Default:
+\fB\fIforce directory security mode\fR = 0 \fR
+.sp
+Example:
+\fB\fIforce directory security mode\fR = 700 \fR
+.RE
+.PP
+group
+.RS 3n
+This parameter is a synonym for force group.
+.RE
+.PP
+Note
+Users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems\. Administrators of most normal systems will probably want to leave it set as 0000\.
+Default:
+\fI\fIforce directory security mode\fR\fR\fI = \fR\fI0\fR\fI \fR
+.sp
+Example:
+\fI\fIforce directory security mode\fR\fR\fI = \fR\fI700\fR\fI \fR
+.RE
+group.PP
+.RS 4
+This parameter is a synonym for
+force group\.
+.RE
 force group (S)
+.RS 3n
+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 '+' 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 a finer granularity of ownership assignment. For example, the setting
+.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 \'+\' 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 a finer granularity of ownership assignment\. For example, the setting
 \fIforce group = +sys\fR
 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.
+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
+force user parameter is also set the group specified in
+\fIforce user\fR
+parameter is also set the group specified in
 \fIforce group\fR
 will override the primary group set in
 \fIforce user\fR.
 .sp
 Default:
 \fB\fIforce group\fR = \fR
 .sp
 Example:
 \fB\fIforce group\fR = agroup \fR
 .RE
+.PP
+\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)
+.RS 3n
+.PP
+.RS 4
 When printing from Windows NT (or later), each printer in
 \fIsmb.conf\fR
 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
+\fIsmb\.conf\fR
+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's 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's 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:
 \fB\fIforce printername\fR = no \fR
 .RE
+.PP
+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\'s 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\'s 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)
+.RS 3n
+This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a file using the native NT security dialog box.
+.sp
+This parameter is applied as a mask (OR'ed with) to the changed permission bits, thus forcing any bits in this mask that the user may have modified to be on. Make sure not to mix up this parameter with
+security mask, which works similar like this one but uses logical AND instead of OR.
+.sp
+Essentially, one bits in this mask may be treated as a set of bits that, when modifying security on a file, the user has always set to be on.
+.sp
+If not set explicitly this parameter is set to 0, and allows a user to modify all the user/group/world permissions on a file, with no restrictions.
+.sp
+\fB Note\fR
+that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. Administrators of most normal systems will probably want to leave this set to 0000.
+.sp
+Default:
+\fB\fIforce security mode\fR = 0 \fR
+.sp
+Example:
+\fB\fIforce security mode\fR = 700 \fR
+.RE
+.PP
+.PP
+.RS 4
+This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a file using the native NT security dialog box\.
+.sp
+This parameter is applied as a mask (OR\'ed with) to the changed permission bits, thus forcing any bits in this mask that the user may have modified to be on\. Make sure not to mix up this parameter with
+\fIsecurity mask\fR, which works similar like this one but uses logical AND instead of OR\.
+.sp
+Essentially, one bits in this mask may be treated as a set of bits that, when modifying security on a file, the user has always set to be on\.
+.sp
+If not set explicitly this parameter is set to 0, and allows a user to modify all the user/group/world permissions on a file, with no restrictions\.
+.sp
+\fI Note\fR
+that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems\. Administrators of most normal systems will probably want to leave this set to 0000\.
+.sp
+Default:
+\fI\fIforce security mode\fR\fR\fI = \fR\fI0\fR\fI \fR
+.sp
+Example:
+\fI\fIforce security mode\fR\fR\fI = \fR\fI700\fR\fI \fR
+.RE
 force unknown acl user (S)
+.RS 3n
+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:
+\fB\fIforce unknown acl user\fR = no \fR
+.RE
+.PP
+.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)
+.RS 3n
+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:
+\fB\fIforce user\fR = \fR
+.sp
+Example:
+\fB\fIforce user\fR = auser \fR
+.RE
+.PP
+.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
 fstype (S)
+.RS 3n
+.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
+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
 …
 or
 \fBFAT\fR
 if required.
 .sp
 Default:
 \fB\fIfstype\fR = NTFS \fR
 .sp
 Example:
 \fB\fIfstype\fR = Samba \fR
 .RE
+.PP
+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)
+.RS 3n
+.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.
+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 with
 ./configure --with-sys-quotas. Or on linux when
 ./configure --with-quotas
 was used and a working quota api was found in the system.
 .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.
+\./configure \-\-with\-sys\-quotas\. Or on linux when
+\./configure \-\-with\-quotas
+was used and a working quota api was found in the system\.
+.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 should take 3 arguments:
+.RS 3n
+.TP 3n
+\(bu
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 directory
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 type of query
+.TP 3n
+\(bu
+.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
 .IP "" 3n
+.sp
+.RE
 The type of query can be one of :
+.RS 3n
+.TP 3n
+\(bu
+- user quotas
+.TP 3n
+\(bu
+- user default quotas (uid = -1)
+.TP 3n
+\(bu
+- group quotas
+.TP 3n
+\(bu
+- group default quotas (gid = -1)
+.RE
+.IP "" 3n
+This script should print one line as output with spaces between the arguments. The arguments are:
+.RS 3n
+.TP 3n
+\(bu
+Arg 1 - quota flags (0 = no quotas, 1 = quotas enabled, 2 = quotas enabled and enforced)
+.TP 3n
+\(bu
+Arg 2 - number of currently used blocks
+.TP 3n
+\(bu
+Arg 3 - the softlimit number of blocks
+.TP 3n
+\(bu
+Arg 4 - the hardlimit number of blocks
+.TP 3n
+\(bu
+Arg 5 - currently used number of inodes
+.TP 3n
+\(bu
+Arg 6 - the softlimit number of inodes
+.TP 3n
+\(bu
+Arg 7 - the hardlimit number of inodes
+.TP 3n
+\(bu
+Arg 8(optional) - the number of bytes in a block(default is 1024)
+.RE
+.IP "" 3n
+Default:
+\fB\fIget quota command\fR = \fR
+.sp
+Example:
+\fB\fIget quota command\fR = /usr/local/sbin/query_quota \fR
+.RE
+.PP
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\- user quotas
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\- user default quotas (uid = \-1)
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\- group quotas
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\- group default quotas (gid = \-1)
+.sp
+.RE
+This script should print one line as output with spaces between the arguments\. The arguments are:
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+Arg 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
+.\}
+Arg 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
+.\}
+Arg 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
+.\}
+Arg 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
+.\}
+Arg 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
+.\}
+Arg 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
+.\}
+Arg 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
+.\}
+Arg 8(optional) \- the number of bytes in a block(default is 1024)
+.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)
+.RS 3n
+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
+wide smbconfoptions parameter is set to
+\fBno\fR.
+.sp
+Default:
+\fB\fIgetwd cache\fR = yes \fR
+.RE
+.PP
+.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
+\fIwide smbconfoptions\fR
+parameter is set to
+\fBno\fR\.
+.sp
+Default:
+\fI\fIgetwd cache\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 guest account (G)
+.RS 3n
+.PP
+.RS 4
 This is a username which will be used for access to services which are specified as
+guest ok (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 -
+\fIguest ok\fR
+(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:
 \fB\fIguest account\fR = nobody # default can be changed at compile-time \fR
 .sp
 Example:
 \fB\fIguest account\fR = ftp \fR
 .RE
 .PP
+public
+.RS 3n
 This parameter is a synonym for guest ok.
 .RE
+.PP
+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.PP
+.RS 4
+This parameter is a synonym for
+guest ok\.
+.RE
 guest ok (S)
+.RS 3n
+.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
 guest account.
+for a service, then no password is required to connect to the service\. Privileges will be those of the
+\fIguest account\fR\.
 .sp
 This paramater nullifies the benifits of setting
+restrict anonymous = 2
+\fIrestrict anonymous = 2\fR
 .sp
 See the section below on
+security for more information about this option.
+.sp
+Default:
+\fB\fIguest ok\fR = no \fR
+.RE
+.PP
+only guest
+.RS 3n
+This parameter is a synonym for guest only.
+.RE
+.PP
+\fIsecurity\fR
+for more information about this option\.
+.sp
+Default:
+\fI\fIguest ok\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
+only guest.PP
+.RS 4
+This parameter is a synonym for
+guest only\.
+.RE
 guest only (S)
+.RS 3n
+.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
+guest ok is not set for the service.
+for a service, then only guest connections to the service are permitted\. This parameter will have no effect if
+\fIguest ok\fR
+is not set for the service\.
 .sp
 See the section below on
+security for more information about this option.
+.sp
+Default:
+\fB\fIguest only\fR = no \fR
+.RE
+.PP
+\fIsecurity\fR
+for more information about this option\.
+.sp
+Default:
+\fI\fIguest only\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 hide dot files (S)
+.RS 3n
+This is a boolean parameter that controls whether files starting with a dot appear as hidden files.
+.sp
+Default:
+\fB\fIhide dot files\fR = yes \fR
+.RE
+.PP
+.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)
+.RS 3n
+This is a list of files or directories that are not visible but are accessible. The DOS 'hidden' attribute is applied to any files or directories that match.
+.sp
+Each entry in the list must be separated by a '/', which allows spaces to be included in the entry. '*' and '?' 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 '/'.
+.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.
+.PP
+.RS 4
+This is a list of files or directories that are not visible but are accessible\. The DOS \'hidden\' attribute is applied to any files or directories that match\.
+.sp
+Each entry in the list must be separated by a \'/\', which allows spaces to be included in the entry\. \'*\' and \'?\' 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 \'/\'\.
+.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.
+creates for internal use, and also still hides all files beginning with a dot\.
 .sp
 An example of us of this parameter is:
+.sp
+.sp
+.RS 4
 .nf
+hide files = /.*/DesktopFolderDB/TrashFor%m/resource.frk/
+hide files = /\.*/DesktopFolderDB/TrashFor%m/resource\.frk/
 .fi
+.sp
+Default:
+\fB\fIhide files\fR = # no file are hidden \fR
+.RE
+.PP
+.RE
+.sp
+.sp
+Default:
+\fI\fIhide files\fR\fR\fI = \fR\fI # no file are hidden\fR\fI \fR
+.RE
 hide special files (S)
+.RS 3n
+This parameter prevents clients from seeing special files such as sockets, devices and fifo's in directory listings.
+.sp
+Default:
+\fB\fIhide special files\fR = no \fR
+.RE
+.PP
+.PP
+.RS 4
+This parameter prevents clients from seeing special files such as sockets, devices and fifo\'s in directory listings\.
+.sp
+Default:
+\fI\fIhide special files\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 hide unreadable (S)
+.RS 3n
+This parameter prevents clients from seeing the existance of files that cannot be read. Defaults to off.
+.sp
+Default:
+\fB\fIhide unreadable\fR = no \fR
+.RE
+.PP
+.PP
+.RS 4
+This parameter prevents clients from seeing the existance of files that cannot be read\. Defaults to off\.
+.sp
+Default:
+\fI\fIhide unreadable\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 hide unwriteable files (S)
+.RS 3n
+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
+Default:
+\fB\fIhide unwriteable files\fR = no \fR
+.RE
+.PP
+.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
+Default:
+\fI\fIhide unwriteable files\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 homedir map (G)
+.RS 3n
+.PP
+.RS 4
 If
+nis homedir is
+\fInis homedir\fR
+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's home directory should be extracted. At present, only the Sun auto.home map format is understood. The form of the map is:
+.sp
+then this parameter specifies the NIS (or YP) map from which the server for the user\'s home directory should be extracted\. At present, only the Sun auto\.home map format is understood\. The form of the map is:
+.sp
+.RS 4
 .nf
 username server:/some/file/system
 .fi
+and the program will extract the servername from before the first ':'. There should probably be a better parsing system that copes with different map formats and also Amd (another automounter) maps.
+.RE
+.sp
+and the program will extract the servername from before the first \':\'\. There should probably be a better parsing system that copes with different map formats and also Amd (another automounter) maps\.
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBNote\fR
+A working NIS client is required on the system for this option to work.
+Default:
+\fB\fIhomedir map\fR = \fR
+.sp
+Example:
+\fB\fIhomedir map\fR = amd.homedir \fR
+.RE
+.PP
+Note
+A working NIS client is required on the system for this option to work\.
+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)
+.RS 3n
+.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.
+\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
+msdfs root 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:
+\fB\fIhost msdfs\fR = yes \fR
+.RE
+.PP
+\fImsdfs root\fR
+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)
+.RS 3n
+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
+.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:
 \fB\fIhostname lookups\fR = no \fR
 .sp
 Example:
 \fB\fIhostname lookups\fR = yes \fR
 .RE
 .PP
+allow hosts
+.RS 3n
 This parameter is a synonym for hosts allow.
 .RE
+.PP
+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.PP
+.RS 4
+This parameter is a synonym for
+hosts allow\.
+.RE
 hosts allow (S)
+.RS 3n
+.PP
+.RS 4
 A synonym for this parameter is
+allow hosts.
+.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
+\fIhosts_access(5)\fR. 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
+hosts deny option.
+.sp
+You can also specify hosts by network/netmask pairs and by netgroup names if your system supports netgroups. The
+\fBEXCEPT\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
+\fIallow hosts\fR\.
+.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
+\fIhosts_access(5)\fR\. 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
+\fIhosts deny\fR
+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
+hosts allow = 150\.203\.15\.0/255\.255\.255\.0
 .sp
 Example 3: allow a couple of hosts
 …
 .nr an-break-flag 1
 .br
+\fBNote\fR
+Note that access still requires suitable user-level passwords.
+Note
+Note that access still requires suitable user\-level passwords\.
 See
 \fBtestparm\fR(1)
 for a way of testing your host access to see if it does what you expect.
 .sp
 Default:
 \fB\fIhosts allow\fR = # none (i.e., all hosts permitted access) \fR
 .sp
 Example:
 \fB\fIhosts allow\fR = 150.203.5. myhost.mynet.edu.au \fR
 .RE
 .PP
+deny hosts
+.RS 3n
 This parameter is a synonym for hosts deny.
 .RE
+.PP
+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.PP
+.RS 4
+This parameter is a synonym for
+hosts deny\.
+.RE
 hosts deny (S)
+.RS 3n
+.PP
+.RS 4
 The opposite of
 \fIhosts allow\fR
 - hosts listed here are
 \fBNOT\fR
 permitted access to services unless the specific services have their own lists to override this one. Where the lists conflict, the
+\- 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.
+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) and then explicitly specify to the
+hosts allow = hosts allow parameter those hosts that should be permitted access.
+.sp
+Default:
+\fB\fIhosts deny\fR = # none (i.e., no hosts specifically excluded) \fR
+.sp
+Example:
+\fB\fIhosts deny\fR = 150.203.4. badhost.mynet.edu.au \fR
+.RE
+.PP
+\.0\.0\.0/0) and then explicitly specify to the
+\fIhosts allow = hosts allow\fR
+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 alloc backend (G)
+.RS 3n
+The idmap alloc backend provides a plugin interface for Winbind to use when allocating Unix uids/gids for Windows SIDs. This option is to be used in conjunction with the
+idmap domains parameter and refers to the name of the idmap module which will provide the id allocation functionality. Please refer to the man page for each idmap plugin to determine whether or not the module implements the allocation feature. The most common plugins are the tdb (\fBidmap_tdb\fR(8)) and ldap (\fBidmap_ldap\fR(8)) libraries.
+.PP
+.RS 4
+The idmap alloc backend provides a plugin interface for Winbind to use when allocating Unix uids/gids for Windows SIDs\. This option is to be used in conjunction with the
+\fIidmap domains\fR
+parameter and refers to the name of the idmap module which will provide the id allocation functionality\. Please refer to the man page for each idmap plugin to determine whether or not the module implements the allocation feature\. The most common plugins are the tdb (\fBidmap_tdb\fR(8)) and ldap (\fBidmap_ldap\fR(8)) libraries\.
 .sp
 Also refer to the
+idmap alloc config option.
+.sp
+\fBNo default\fR
+.sp
+Example:
+\fB\fIidmap alloc backend\fR = tdb \fR
+.RE
+.PP
+\fIidmap alloc config\fR
+option\.
+.sp
+\fINo default\fR
+.sp
+Example:
+\fI\fIidmap alloc backend\fR\fR\fI = \fR\fItdb\fR\fI \fR
+.RE
 idmap alloc config (G)
+.RS 3n
+.PP
+.RS 4
 The idmap alloc config prefix provides a means of managing settings for the backend defined by the
+idmap alloc backend parameter. Refer to the man page for each idmap plugin regarding specific configuration details.
+.sp
+\fBNo default\fR
+.RE
+.PP
+\fIidmap alloc backend\fR
+parameter\. Refer to the man page for each idmap plugin regarding specific configuration details\.
+.sp
+\fINo default\fR
+.RE
 idmap backend (G)
+.RS 3n
+The idmap backend provides a plugin interface for Winbind to use varying backends to store SID/uid/gid mapping tables. This option is mutually exclusive with the newer and more flexible
+idmap domains parameter. The main difference between the "idmap backend" and the "idmap domains" is that the former only allows on backend for all domains while the latter supports configuring backends on a per domain basis.
+.sp
+Examples of SID/uid/gid backends include tdb (\fBidmap_tdb\fR(8)), ldap (\fBidmap_ldap\fR(8)), rid (\fBidmap_rid\fR(8)), and ad (\fBidmap_tdb\fR(8)).
+.sp
+Default:
+\fB\fIidmap backend\fR = tdb \fR
+.RE
+.PP
+.PP
+.RS 4
+The idmap backend provides a plugin interface for Winbind to use varying backends to store SID/uid/gid mapping tables\. This option is mutually exclusive with the newer and more flexible
+\fIidmap domains\fR
+parameter\. The main difference between the "idmap backend" and the "idmap domains" is that the former only allows on backend for all domains while the latter supports configuring backends on a per domain basis\.
+.sp
+Examples of SID/uid/gid backends include tdb (\fBidmap_tdb\fR(8)), ldap (\fBidmap_ldap\fR(8)), rid (\fBidmap_rid\fR(8)), and ad (\fBidmap_tdb\fR(8))\.
+.sp
+Default:
+\fI\fIidmap backend\fR\fR\fI = \fR\fItdb\fR\fI \fR
+.RE
 idmap cache time (G)
+.RS 3n
+This parameter specifies the number of seconds that Winbind's idmap interface will cache positive SID/uid/gid query results.
+.sp
+Default:
+\fB\fIidmap cache time\fR = 900 \fR
+.RE
+.PP
+.PP
+.RS 4
+This parameter specifies the number of seconds that Winbind\'s idmap interface will cache positive SID/uid/gid query results\.
+.sp
+Default:
+\fI\fIidmap cache time\fR\fR\fI = \fR\fI900\fR\fI \fR
+.RE
 idmap config (G)
+.RS 3n
+.PP
+.RS 4
 The idmap config prefix provides a means of managing each domain defined by the
+idmap domains option using Samba's parameteric option support. The idmap config prefix should be followed by the name of the domain, a colon, and a setting specific to the chosen backend. There are three options available for all domains:
+.RS 3n
+\fIidmap domains\fR
+option using Samba\'s parameteric option support\. The idmap config prefix should be followed by the name of the domain, a colon, and a setting specific to the chosen backend\. There are three options available for all domains:
 .PP
 backend = backend_name
 .RS 3n
 Specifies the name of the idmap plugin to use as the SID/uid/gid backend for this domain.
+.RS 4
+Specifies the name of the idmap plugin to use as the SID/uid/gid backend for this domain\.
 .RE
 .PP
 default = [yes|no]
 .RS 3n
 The default domain/backend will be used for searching for users and groups not belonging to one of the explicitly listed domains (matched by comparing the account SID and the domain SID).
+.RS 4
+The default domain/backend will be used for searching for users and groups not belonging to one of the explicitly listed domains (matched by comparing the account SID and the domain SID)\.
 .RE
 .PP
 readonly = [yes|no]
 .RS 3n
+.RS 4
 Mark the domain as readonly which means that no attempts to allocate a uid or gid (by the
+idmap alloc backend) for any user or group in that domain will be attempted.
+.RE
+.RE
+.IP "" 3n
+\fIidmap alloc backend\fR) for any user or group in that domain will be attempted\.
+.RE
+.sp
 The following example illustrates how to configure the
 \fBidmap_ad\fR(8)
 for the CORP domain and the
 \fBidmap_tdb\fR(8)
+backend for all other domains. The TRUSTEDDOMAINS string is simply a key used to reference the "idmap config" settings and does not represent the actual name of a domain.
+backend for all other domains\. The TRUSTEDDOMAINS string is simply a key used to reference the "idmap config" settings and does not represent the actual name of a domain\.
+.sp
+.RS 4
 .nf
         idmap domains = CORP TRUSTEDDOMAINS
 …
         idmap config TRUSTEDDOMAINS:backend = tdb
         idmap config TRUSTEDDOMAINS:default = yes
         idmap config TRUSTEDDOMAINS:range   = 1000 - 9999
+        idmap config TRUSTEDDOMAINS:range   = 1000 \- 9999
 .fi
+\fBNo default\fR
+.RE
+.PP
+.RE
+\fINo default\fR
+.RE
 idmap domains (G)
+.RS 3n
+The idmap domains option defines a list of Windows domains which will each have a separately configured backend for managing Winbind's SID/uid/gid tables. This parameter is mutually exclusive with the older
+idmap backend option.
+.sp
+Values consist of the short domain name for Winbind's primary or collection of trusted domains. You may also use an arbitrary string to represent a catchall domain backend for any domain not explicitly listed.
+.PP
+.RS 4
+The idmap domains option defines a list of Windows domains which will each have a separately configured backend for managing Winbind\'s SID/uid/gid tables\. This parameter is mutually exclusive with the older
+\fIidmap backend\fR
+option\.
+.sp
+Values consist of the short domain name for Winbind\'s primary or collection of trusted domains\. You may also use an arbitrary string to represent a catchall domain backend for any domain not explicitly listed\.
 .sp
 Refer to the
+idmap config for details about managing the SID/uid/gid backend for each domain.
+.sp
+\fBNo default\fR
+.sp
+Example:
+\fB\fIidmap domains\fR = default AD CORP \fR
+.RE
+.PP
+winbind gid
+.RS 3n
+This parameter is a synonym for idmap gid.
+.RE
+.PP
+\fIidmap config\fR
+for details about managing the SID/uid/gid backend for each domain\.
+.sp
+\fINo default\fR
+.sp
+Example:
+\fI\fIidmap domains\fR\fR\fI = \fR\fIdefault AD CORP\fR\fI \fR
+.RE
+winbind gid.PP
+.RS 4
+This parameter is a synonym for
+idmap gid\.
+.RE
 idmap gid (G)
+.RS 3n
+The idmap gid parameter specifies the range of group ids that are allocated for the purpose of mapping UNX groups to NT group SIDs. This range of group ids should have no existing local or NIS groups within it as strange conflicts can occur otherwise.
+.PP
+.RS 4
+The idmap gid parameter specifies the range of group ids that are allocated for the purpose of mapping UNX groups to NT group SIDs\. This range of group ids should have no existing local or NIS groups within it as strange conflicts can occur otherwise\.
 .sp
 See also the
+idmap backend,
+idmap domains, and
+idmap config options.
+.sp
+Default:
+\fB\fIidmap gid\fR = \fR
+.sp
+Example:
+\fB\fIidmap gid\fR = 10000-20000 \fR
+.RE
+.PP
+\fIidmap backend\fR,
+\fIidmap domains\fR, and
+\fIidmap config\fR
+options\.
+.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)
+.RS 3n
+This parameter specifies the number of seconds that Winbind's idmap interface will cache negative SID/uid/gid query results.
+.sp
+Default:
+\fB\fIidmap negative cache time\fR = 120 \fR
+.RE
+.PP
+winbind uid
+.RS 3n
+This parameter is a synonym for idmap uid.
+.RE
+.PP
+.PP
+.RS 4
+This parameter specifies the number of seconds that Winbind\'s 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.PP
+.RS 4
+This parameter is a synonym for
+idmap uid\.
+.RE
 idmap uid (G)
+.RS 3n
+The idmap uid parameter specifies the range of user ids that are allocated for use in mapping UNIX users to NT user SIDs. This range of ids should have no existing local or NIS users within it as strange conflicts can occur otherwise.
+.PP
+.RS 4
+The idmap uid parameter specifies the range of user ids that are allocated for use in mapping UNIX users to NT user SIDs\. This range of ids should have no existing local or NIS users within it as strange conflicts can occur otherwise\.
 .sp
 See also the
+idmap backend,
+idmap domains, and
+idmap config options.
+.sp
+Default:
+\fB\fIidmap uid\fR = \fR
+.sp
+Example:
+\fB\fIidmap uid\fR = 10000-20000 \fR
+.RE
+.PP
+\fIidmap backend\fR,
+\fIidmap domains\fR, and
+\fIidmap config\fR
+options\.
+.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)
+.RS 3n
+This allows you to include one config file inside another. The file is included literally, as though typed in place.
+.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%P\fR
 and
 \fI%S\fR.
 .sp
 Default:
 \fB\fIinclude\fR = \fR
 .sp
 Example:
 \fB\fIinclude\fR = /usr/local/samba/lib/admin_smb.conf \fR
 .RE
+.PP
+\fI%S\fR\.
+.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)
+.RS 3n
+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.
+.sp
+Default:
+\fB\fIinherit acls\fR = no \fR
+.RE
+.PP
+.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\.
+.sp
+Default:
+\fI\fIinherit acls\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 inherit owner (S)
+.RS 3n
+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 to ensure that newly create files in a user's roaming profile directory are actually owner by the user.
+.sp
+Default:
+\fB\fIinherit owner\fR = no \fR
+.RE
+.PP
+.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 to ensure that newly create files in a user\'s roaming profile directory are actually owner by the user\.
+.sp
+Default:
+\fI\fIinherit owner\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 inherit permissions (S)
+.RS 3n
+.PP
+.RS 4
 The permissions on new files and directories are normally governed by
+create mask,
+directory mask,
+force create mode and
+force directory mode 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
+map archive,
+map hidden and
+map system as usual.
+\fIcreate mask\fR,
+\fIdirectory mask\fR,
+\fIforce create mode\fR
+and
+\fIforce directory mode\fR
+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
+\fImap archive\fR,
+\fImap hidden\fR
+and
+\fImap system\fR
+as usual\.
 .sp
 Note that the setuid bit is
 \fBnever\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:
 \fB\fIinherit permissions\fR = no \fR
 .RE
+.PP
+\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
 interfaces (G)
+.RS 3n
+This option allows you to override the default network interfaces list that Samba will use for browsing, name registration and other 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:
+.RS 3n
+.TP 3n
+\(bu
+a network interface name (such as eth0). This may include shell-like wildcards so eth* will match any interface starting with the substring "eth"
+.TP 3n
+\(bu
+an IP address. In this case the netmask is determined from the list of interfaces obtained from the kernel
+.TP 3n
+\(bu
+an IP/mask pair.
+.TP 3n
+\(bu
+a broadcast/mask pair.
+.RE
+.IP "" 3n
+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's 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:
+\fB\fIinterfaces\fR = \fR
+.sp
+Example:
+\fB\fIinterfaces\fR = eth0 192.168.2.10/24 192.168.3.10/255.255.255.0 \fR
+.RE
+.PP
+.PP
+.RS 4
+This option allows you to override the default network interfaces list that Samba will use for browsing, name registration and other 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\.
+.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\'s 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)
+.RS 3n
+This is a list of users that should not be allowed to login to this service. This is really a
+\fBparanoid\fR
+check to absolutely ensure an improper setting does not breach your security.
+.sp
+A name starting with a '@' 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 '+' is interpreted only by looking in the UNIX group database via the NSS getgrnam() interface. A name starting with '&' is interpreted only by looking in the NIS netgroup database (this requires NIS to be working on your system). The characters '+' and '&' may be used at the start of the name in either order so the value
+.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 \'@\' 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 \'+\' is interpreted only by looking in the UNIX group database via the NSS getgrnam() interface\. A name starting with \'&\' is interpreted only by looking in the NIS netgroup database (this requires NIS to be working on your system)\. The characters \'+\' and \'&\' 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 '@' prefix).
+means check the NIS netgroup database, followed by the UNIX group database (the same as the \'@\' prefix)\.
 .sp
 The current servicename is substituted for
 \fI%S\fR. This is useful in the [homes] section.
 .sp
 Default:
 \fB\fIinvalid users\fR = # no invalid users \fR
 .sp
 Example:
 \fB\fIinvalid users\fR = root fred admin @wheel \fR
 .RE
+.PP
+\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)
+.RS 3n
+.PP
+.RS 4
 This parameter is only applicable if
+printing is set to
+\fBiprint\fR.
+\fIprinting\fR
+is set to
+\fBiprint\fR\.
 .sp
 If set, this option overrides the ServerName option in the CUPS
 \fIclient.conf\fR. This is necessary if you have virtual samba servers that connect to different CUPS daemons.
 .sp
 Default:
 \fB\fIiprint server\fR = "" \fR
 .sp
 Example:
 \fB\fIiprint server\fR = MYCUPSSERVER \fR
 .RE
+.PP
+\fIclient\.conf\fR\. 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)
+.RS 3n
+.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
 socket options). Basically you should only use this option if you strike difficulties.
 .sp
 Default:
 \fB\fIkeepalive\fR = 300 \fR
 .sp
 Example:
 \fB\fIkeepalive\fR = 600 \fR
 .RE
+.PP
+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
+\fIsocket options\fR)\. Basically you should only use this option if you strike difficulties\.
+.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
 kernel change notify (S)
+.RS 3n
+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:
+\fB\fIkernel change notify\fR = yes \fR
+.RE
+.PP
+.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 (G)
+.RS 3n
+.PP
+.RS 4
 For UNIXes that support kernel based
+oplocks (currently only IRIX and the Linux 2.4 kernel), this parameter allows the use of them to be turned on or off.
+\fIoplocks\fR
+(currently only IRIX and the Linux 2\.4 kernel), this parameter allows the use of them to be turned on or off\.
 .sp
 Kernel oplocks support allows Samba
 …
 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
 \fBvery\fR
 cool feature :-).
+has oplocked\. This allows complete data consistency between SMB/CIFS, NFS and local file access (and is a
+\fIvery\fR
+cool feature :\-)\.
 .sp
 This parameter defaults to
 \fBon\fR, but is translated to a no-op on systems that no not have the necessary kernel support. You should never need to touch this parameter.
 .sp
 Default:
 \fB\fIkernel oplocks\fR = yes \fR
 .RE
+.PP
+\fBon\fR, but is translated to a no\-op on systems that no not have the necessary kernel support\. You should never need to touch this parameter\.
+.sp
+Default:
+\fI\fIkernel oplocks\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 lanman auth (G)
+.RS 3n
+.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 it's case-insensitive nature, and the choice of algorithm. Servers without Windows 95/98/ME or MS DOS clients are advised to disable this option.
+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 it\'s 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
 Unlike the
 encrypt passwords
 option, this parameter cannot alter client behaviour, and the LANMAN response will still be sent over the network. See the
+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's clients (such as smbclient)
+to disable this for Samba\'s 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:
 \fB\fIlanman auth\fR = yes \fR
 .RE
+.PP
+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\fIyes\fR\fI \fR
+.RE
 large readwrite (G)
+.RS 3n
+.PP
+.RS 4
 This parameter determines whether or not
 \fBsmbd\fR(8)
 supports the new 64k streaming read and write varient 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:
 \fB\fIlarge readwrite\fR = yes \fR
 .RE
+.PP
+supports the new 64k streaming read and write varient 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)
+.RS 3n
+.PP
+.RS 4
 The
+ldap admin dn defines the Distinguished Name (DN) name used by Samba to contact the ldap server when retreiving user account information. The
+ldap admin dn is used in conjunction with the admin dn password stored in the
+\fIprivate/secrets.tdb\fR
+file. See the
+\fIldap admin dn\fR
+defines the Distinguished Name (DN) name used by Samba to contact the ldap server when retreiving user account information\. The
+\fIldap admin dn\fR
+is used in conjunction with the admin dn password stored in the
+\fIprivate/secrets\.tdb\fR
+file\. See the
 \fBsmbpasswd\fR(8)
 man page for more information on how to accomplish this.
+man page for more information on how to accomplish this\.
 .sp
 The
+ldap admin dn requires a fully specified DN. The
+ldap suffix is not appended to the
+ldap admin dn.
+.sp
+\fBNo default\fR
+.RE
+.PP
+\fIldap admin dn\fR
+requires a fully specified DN\. The
+\fIldap suffix\fR
+is not appended to the
+\fIldap admin dn\fR\.
+.sp
+\fINo default\fR
+.RE
 ldap delete dn (G)
+.RS 3n
+This parameter specifies whether a delete operation in the ldapsam deletes the complete entry or only the attributes specific to Samba.
+.sp
+Default:
+\fB\fIldap delete dn\fR = no \fR
+.RE
+.PP
+.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 group suffix (G)
+.RS 3n
+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
+ldap suffix will be used instead. The suffix string is pre-pended to the
+ldap suffix string so use a partial DN.
+.sp
+Default:
+\fB\fIldap group suffix\fR = \fR
+.sp
+Example:
+\fB\fIldap group suffix\fR = ou=Groups \fR
+.RE
+.PP
+.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
+\fIldap suffix\fR
+will be used instead\. The suffix string is pre\-pended to the
+\fIldap suffix\fR
+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)
+.RS 3n
+This parameters specifies the suffix that is used when storing idmap mappings. If this parameter is unset, the value of
+ldap suffix will be used instead. The suffix string is pre-pended to the
+ldap suffix string so use a partial DN.
+.sp
+Default:
+\fB\fIldap idmap suffix\fR = \fR
+.sp
+Example:
+\fB\fIldap idmap suffix\fR = ou=Idmap \fR
+.RE
+.PP
+.PP
+.RS 4
+This parameters specifies the suffix that is used when storing idmap mappings\. If this parameter is unset, the value of
+\fIldap suffix\fR
+will be used instead\. The suffix string is pre\-pended to the
+\fIldap suffix\fR
+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)
+.RS 3n
+It specifies where machines should be added to the ldap tree. If this parameter is unset, the value of
+ldap suffix will be used instead. The suffix string is pre-pended to the
+ldap suffix string so use a partial DN.
+.sp
+Default:
+\fB\fIldap machine suffix\fR = \fR
+.sp
+Example:
+\fB\fIldap machine suffix\fR = ou=Computers \fR
+.RE
+.PP
+.PP
+.RS 4
+It specifies where machines should be added to the ldap tree\. If this parameter is unset, the value of
+\fIldap suffix\fR
+will be used instead\. The suffix string is pre\-pended to the
+\fIldap suffix\fR
+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 passwd sync (G)
+.RS 3n
+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.
+.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
+ldap passwd sync can be set to one of three values:
+.RS 3n
+.TP 3n
+\(bu
+\fIldap passwd sync\fR
+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.
+.TP 3n
+\(bu
+= 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.
+.TP 3n
+\(bu
+= 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
 .IP "" 3n
 Default:
 \fB\fIldap passwd sync\fR = no \fR
 .RE
+.PP
+= Only update the LDAP password and let the LDAP server do the rest\.
+.sp
+.RE
+Default:
+\fI\fIldap passwd sync\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 ldap replication sleep (G)
+.RS 3n
+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 'local' server, however the replication might take some seconds, especially over slow links. Certain client activities, particularly domain joins, can become confused by the 'success' that does not immediately change the LDAP back-end's 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:
+\fB\fIldap replication sleep\fR = 1000 \fR
+.RE
+.PP
+.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 \'local\' server, however the replication might take some seconds, especially over slow links\. Certain client activities, particularly domain joins, can become confused by the \'success\' that does not immediately change the LDAP back\-end\'s 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)
+.RS 3n
+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, Winindd must be running and the smb.conf ldap options must be properly configured. The typical ldap setup used with the
+ldapsam:trusted = yes option is usually sufficient to use
+ldapsam:editposix = yes as well.
+.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, Winindd must be running and the smb\.conf ldap options must be properly configured\. The typical ldap setup used with the
+\fIldapsam:trusted = yes\fR
+option is usually sufficient to use
+\fIldapsam:editposix = yes\fR
+as well\.
 .sp
 An example configuration can be the following:
+.sp
+.sp
+.RS 4
 .nf
         encrypt passwords = true
         passdb backend = ldapsam
 …
         idmap backend = ldap:"ldap://localhost"
         idmap uid = 5000-50000
         idmap gid = 5000-50000
+        idmap uid = 5000\-50000
+        idmap gid = 5000\-50000
 .fi
+.RE
+.sp
 This configuration assume the ldap server have been loaded with a base tree like described in the following ldif:
+.sp
+.sp
+.RS 4
 .nf
         dn: dc=samba,dc=org
         objectClass: top
         objectClass: dcObject
         objectClass: organization
         o: samba.org
+        o: samba\.org
         dc: samba
 …
 .fi
+.sp
+Default:
+\fB\fIldapsam:editposix\fR = no \fR
+.RE
+.PP
+.RE
+.sp
+.sp
+Default:
+\fI\fIldapsam:editposix\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 ldapsam:trusted (G)
+.RS 3n
+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 enumerate group membership. Sadly, other functions that are used to deal with user and group attributes lack such optimization.
+.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 enumerate group membership\. Sadly, other functions that are used to deal with user and group attributes lack such optimization\.
 .sp
 To make Samba scale well in large environments, the
+ldapsam:trusted = yes 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,
+ldapsam:trusted = yes 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:
+\fB\fIldapsam:trusted\fR = no \fR
+.RE
+.PP
+\fIldapsam:trusted = yes\fR
+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,
+\fIldapsam:trusted = yes\fR
+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)
+.RS 3n
+.PP
+.RS 4
 This option is used to define whether or not Samba should use SSL when connecting to the ldap server This is
 \fBNOT\fR
 related to Samba's previous SSL support which was enabled by specifying the
 --with-ssl
+\fINOT\fR
+related to Samba\'s previous SSL support which was enabled by specifying the
+\-\-with\-ssl
 option to the
 \fIconfigure\fR
 script.
+script\.
 .sp
 The
+ldap ssl can be set to one of three values:
+.RS 3n
+.TP 3n
+\(bu
+\fIldap ssl\fR
+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
+.\}
 \fIOff\fR
+= Never use SSL when querying the directory.
+.TP 3n
+\(bu
+= 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.
+.TP 3n
+\(bu
+= Use the LDAPv3 StartTLS extended operation (RFC2830) for communicating with the directory server\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fIOn\fR
 = Use SSL on the ldaps port when contacting the
 \fIldap server\fR. Only available when the backwards-compatiblity
 --with-ldapsam
 option is specified to configure. See
+passdb backend
+.
                 .RE
 .IP "" 3n
 Default:
 \fB\fIldap ssl\fR = start_tls \fR
 .RE
+.PP
+\fIldap server\fR\. Only available when the backwards\-compatiblity
+\-\-with\-ldapsam
+option is specified to configure\. See
+\fIpassdb backend\fR
+\.
+                .sp
+.RE
+Default:
+\fI\fIldap ssl\fR\fR\fI = \fR\fIstart_tls\fR\fI \fR
+.RE
 ldap suffix (G)
+.RS 3n
+Specifies the base for all ldap suffixes and for storing the sambaDomain object.
+.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
 ldap user suffix,
 ldap group suffix,
 ldap machine suffix, and the
 ldap idmap suffix. Each of these should be given only a DN relative to the
 ldap suffix.
 .sp
 Default:
 \fB\fIldap suffix\fR = \fR
 .sp
 Example:
 \fB\fIldap suffix\fR = dc=samba,dc=org \fR
 .RE
+.PP
+\fIldap user suffix\fR,
+\fIldap group suffix\fR,
+\fIldap machine suffix\fR, and the
+\fIldap idmap suffix\fR\. Each of these should be given only a DN relative to the
+\fIldap suffix\fR\.
+.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)
+.RS 3n
+When Samba connects to an ldap server that servermay be down or unreachable. To prevent Samba from hanging whilst waiting for the connection this parameter specifies in seconds how long Samba should wait before failing the connect. The default is to only wait fifteen seconds for the ldap server to respond to the connect request.
+.sp
+Default:
+\fB\fIldap timeout\fR = 15 \fR
+.RE
+.PP
+.PP
+.RS 4
+When Samba connects to an ldap server that servermay be down or unreachable\. To prevent Samba from hanging whilst waiting for the connection this parameter specifies in seconds how long Samba should wait before failing the connect\. The default is to only wait fifteen seconds for the ldap server to respond to the connect request\.
+.sp
+Default:
+\fI\fIldap timeout\fR\fR\fI = \fR\fI15\fR\fI \fR
+.RE
 ldap user suffix (G)
+.RS 3n
+This parameter specifies where users are added to the tree. If this parameter is unset, the value of
+ldap suffix will be used instead. The suffix string is pre-pended to the
+ldap suffix string so use a partial DN.
+.sp
+Default:
+\fB\fIldap user suffix\fR = \fR
+.sp
+Example:
+\fB\fIldap user suffix\fR = ou=people \fR
+.RE
+.PP
+.PP
+.RS 4
+This parameter specifies where users are added to the tree\. If this parameter is unset, the value of
+\fIldap suffix\fR
+will be used instead\. The suffix string is pre\-pended to the
+\fIldap suffix\fR
+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)
+.RS 3n
+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 not commonly written (such as application .EXE files).
+.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.
+.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 not commonly written (such as application \.EXE files)\.
+.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
+kernel oplocks are supported then level2 oplocks are not granted (even if this parameter is set to
+\fByes\fR). Note also, the
+oplocks parameter must be set to
+\fIkernel oplocks\fR
+are supported then level2 oplocks are not granted (even if this parameter is set to
+\fByes\fR)\. Note also, the
+\fIoplocks\fR
+parameter must be set to
 \fByes\fR
 on this share in order for this parameter to have any effect.
 .sp
 Default:
 \fB\fIlevel2 oplocks\fR = yes \fR
 .RE
+.PP
+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)
+.RS 3n
+.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,
+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
+\fBauto\fR\. The default is
+\fBauto\fR\. If set to
 \fBno\fR
 Samba will never produce these broadcasts. If set to
+Samba will never produce these broadcasts\. If set to
 \fByes\fR
 Samba will produce Lanman announce broadcasts at a frequency set by the parameter
 lm interval. If set to
+\fIlm interval\fR\. 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
 lm interval.
 .sp
 Default:
 \fB\fIlm announce\fR = auto \fR
 .sp
 Example:
 \fB\fIlm announce\fR = yes \fR
 .RE
+.PP
+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
+\fIlm interval\fR\.
+.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)
+.RS 3n
+.PP
+.RS 4
 If Samba is set to produce Lanman announce broadcasts needed by OS/2 clients (see the
+lm announce 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
+lm announce parameter.
+.sp
+Default:
+\fB\fIlm interval\fR = 60 \fR
+.sp
+Example:
+\fB\fIlm interval\fR = 120 \fR
+.RE
+.PP
+\fIlm announce\fR
+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
+\fIlm announce\fR
+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)
+.RS 3n
+A boolean variable that controls whether all printers in the printcap will be loaded for browsing by default. See the
+printers section for more details.
+.sp
+Default:
+\fB\fIload printers\fR = yes \fR
+.RE
+.PP
+.PP
+.RS 4
+A boolean variable that controls whether all printers in the printcap will be loaded for browsing by default\. See the
+\fIprinters\fR
+section for more details\.
+.sp
+Default:
+\fI\fIload printers\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 local master (G)
+.RS 3n
+.PP
+.RS 4
 This option allows
 \fBnmbd\fR(8)
 to try and become a local master browser on a subnet. If set to
+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
+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't mean that Samba will
 \fBbecome\fR
+doesn\'t mean that Samba will
+\fIbecome\fR
 the local master browser on a subnet, just that
 nmbd
 will
 \fBparticipate\fR
 in elections for local master browser.
+\fIparticipate\fR
+in elections for local master browser\.
 .sp
 Setting this value to
 …
 will cause
 nmbd
 \fBnever\fR
 to become a local master browser.
 .sp
 Default:
 \fB\fIlocal master\fR = yes \fR
 .RE
 .PP
+lock dir
+.RS 3n
 This parameter is a synonym for lock directory.
 .RE
+.PP
+\fInever\fR
+to become a local master browser\.
+.sp
+Default:
+\fI\fIlocal master\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
+lock dir.PP
+.RS 4
+This parameter is a synonym for
+lock directory\.
+.RE
 lock directory (G)
+.RS 3n
+This option specifies the directory where lock files will be placed. The lock files are used to implement the
+max connections option.
+.sp
+Default:
+\fB\fIlock directory\fR = ${prefix}/var/locks \fR
+.sp
+Example:
+\fB\fIlock directory\fR = /var/run/samba/locks \fR
+.RE
+.PP
+.PP
+.RS 4
+This option specifies the directory where lock files will be placed\. The lock files are used to implement the
+\fImax connections\fR
+option\.
+.sp
+Default:
+\fI\fIlock directory\fR\fR\fI = \fR\fI${prefix}/var/locks\fR\fI \fR
+.sp
+Example:
+\fI\fIlock directory\fR\fR\fI = \fR\fI/var/run/samba/locks\fR\fI \fR
+.RE
 locking (S)
+.RS 3n
+This controls whether or not locking will be performed by the server in response to lock requests from the client.
+.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.
+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.
+locking = yes, real locking will be performed by the server\.
 .sp
 This option
 \fBmay\fR
 be useful for read-only filesystems which
 \fBmay\fR
+\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
 \fBNo default\fR
 .RE
+.PP
+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
+\fINo default\fR
+.RE
 lock spin count (G)
+.RS 3n
+This parameter has been made inoperative in Samba 3.0.24. The functionality it contolled is now controlled by the parameter
+lock spin time.
+.sp
+Default:
+\fB\fIlock spin count\fR = 0 \fR
+.RE
+.PP
+.PP
+.RS 4
+This parameter has been made inoperative in Samba 3\.0\.24\. The functionality it contolled is now controlled by the parameter
+\fIlock spin time\fR\.
+.sp
+Default:
+\fI\fIlock spin count\fR\fR\fI = \fR\fI0\fR\fI \fR
+.RE
 lock spin time (G)
+.RS 3n
+The time in microseconds 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
+lock spin count parameter is no longer used in Samba 3.0.24. You should not need to change the value of this parameter.
+.sp
+Default:
+\fB\fIlock spin time\fR = 200 \fR
+.RE
+.PP
+.PP
+.RS 4
+The time in microseconds 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
+\fIlock spin count\fR
+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)
+.RS 3n
+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
+\fBNo default\fR
+.sp
+Example:
+\fB\fIlog file\fR = /usr/local/samba/var/log.%m \fR
+.RE
+.PP
+debuglevel
+.RS 3n
+This parameter is a synonym for log level.
+.RE
+.PP
+.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
+debuglevel.PP
+.RS 4
+This parameter is a synonym for
+log level\.
+.RE
 log level (G)
+.RS 3n
+.PP
+.RS 4
 The value of the parameter (a astring) allows the debug level (logging level) to be specified in the
+\fIsmb.conf\fR
+file. This parameter has been extended since the 2.2.x series, now it allow to specify the debug level for multiple debug classes. This is to give greater flexibility in the configuration of the system.
+.sp
+The default will be the log level specified on the command line or level zero if none was specified.
+.sp
+\fBNo default\fR
+.sp
+Example:
+\fB\fIlog level\fR = 3 passdb:5 auth:10 winbind:2 \fR
+.RE
+.PP
+\fIsmb\.conf\fR
+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
+.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
 logon drive (G)
+.RS 3n
+.PP
+.RS 4
 This parameter specifies the local path to which the home directory will be connected (see
 logon home) 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:
 \fB\fIlogon drive\fR = \fR
 .sp
 Example:
 \fB\fIlogon drive\fR = h: \fR
 .RE
+.PP
+\fIlogon home\fR) 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)
+.RS 3n
+This parameter specifies the home directory location when a Win95/98 or NT Workstation logs into a Samba PDC. It allows you to do
+.sp
+C:\>\fBNET USE H: /HOME\fR
+.sp
+from a command prompt, for example.
+.sp
+This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine.
+.sp
+This parameter can be used with Win9X workstations to ensure that roaming profiles are stored in a subdirectory of the user's home directory. This is done in the following way:
+.sp
+logon home = \\\\%N\\%U\\profile
+.sp
+This tells Samba to return the above string, with substitutions made when a client requests the info, generally in a NetUserGetInfo request. Win9X clients truncate the info to \\server\share when a user does
+.PP
+.RS 4
+This parameter specifies the home directory location when a Win95/98 or NT Workstation logs into a Samba PDC\. It allows you to do
+.sp
+C:\e>\fBNET USE H: /HOME\fR
+.sp
+from a command prompt, for example\.
+.sp
+This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine\.
+.sp
+This parameter can be used with Win9X workstations to ensure that roaming profiles are stored in a subdirectory of the user\'s home directory\. This is done in the following way:
+.sp
+logon home = \e\e%N\e%U\eprofile
+.sp
+This tells Samba to return the above string, with substitutions made when a client requests the info, generally in a NetUserGetInfo request\. Win9X clients truncate the info to \e\eserver\eshare when a user does
 net use /home
 but use the whole string when dealing with profiles.
+but use the whole string when dealing with profiles\.
 .sp
 Note that in prior versions of Samba, the
+logon path was returned rather than
+\fIlogon home\fR. This broke
+\fIlogon path\fR
+was returned rather than
+\fIlogon home\fR\. This broke
 net use /home
 but allowed profiles outside the home directory. The current implementation is correct, and can be used for profiles if you use the above trick.
+but allowed profiles outside the home directory\. The current implementation is correct, and can be used for profiles if you use the above trick\.
 .sp
 Disable this feature by setting
+logon home = "" - using the empty string.
+.sp
+This option is only useful if Samba is set up as a logon server.
+.sp
+Default:
+\fB\fIlogon home\fR = \\\\%N\\%U \fR
+.sp
+Example:
+\fB\fIlogon home\fR = \\\\remote_smb_server\\%U \fR
+.RE
+.PP
+\fIlogon home = ""\fR
+\- using the empty string\.
+.sp
+This option is only useful if Samba is set up as a logon server\.
+.sp
+Default:
+\fI\fIlogon home\fR\fR\fI = \fR\fI\e\e%N\e%U\fR\fI \fR
+.sp
+Example:
+\fI\fIlogon home\fR\fR\fI = \fR\fI\e\eremote_smb_server\e%U\fR\fI \fR
+.RE
 logon path (G)
+.RS 3n
+This parameter specifies the directory where roaming profiles (Desktop, NTuser.dat, etc) are stored. Contrary to previous versions of these manual pages, it has nothing to do with Win 9X roaming profiles. To find out how to handle roaming profiles for Win 9X system, see the
+logon home parameter.
+.sp
+This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine. It also specifies the directory from which the "Application Data",
+.PP
+.RS 4
+This parameter specifies the directory where roaming profiles (Desktop, NTuser\.dat, etc) are stored\. Contrary to previous versions of these manual pages, it has nothing to do with Win 9X roaming profiles\. To find out how to handle roaming profiles for Win 9X system, see the
+\fIlogon home\fR
+parameter\.
+.sp
+This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine\. It also specifies the directory from which the "Application Data",
 \fIdesktop\fR,
 \fIstart menu\fR,
 \fInetwork neighborhood\fR,
 \fIprograms\fR
 and other folders, and their contents, are loaded and displayed on your Windows NT client.
 .sp
 The share and the path must be readable by the user for the preferences and directories to be loaded onto the Windows NT client. The share must be writeable when the user logs in for the first time, in order that the Windows NT client can create the NTuser.dat and other directories. Thereafter, the directories and any of the contents can, if required, be made read-only. It is not advisable that the NTuser.dat file be made read-only - rename it to NTuser.man to achieve the desired effect (a
 \fBMAN\fRdatory profile).
 .sp
 Windows clients can sometimes maintain a connection to the [homes] share, even though there is no user logged in. Therefore, it is vital that the logon path does not include a reference to the homes share (i.e. setting this parameter to \\%N\homes\profile_path will cause problems).
 .sp
 This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine.
+and other folders, and their contents, are loaded and displayed on your Windows NT client\.
+.sp
+The share and the path must be readable by the user for the preferences and directories to be loaded onto the Windows NT client\. The share must be writeable when the user logs in for the first time, in order that the Windows NT client can create the NTuser\.dat and other directories\. Thereafter, the directories and any of the contents can, if required, be made read\-only\. It is not advisable that the NTuser\.dat file be made read\-only \- rename it to NTuser\.man to achieve the desired effect (a
+\fIMAN\fRdatory profile)\.
+.sp
+Windows clients can sometimes maintain a connection to the [homes] share, even though there is no user logged in\. Therefore, it is vital that the logon path does not include a reference to the homes share (i\.e\. setting this parameter to \e\e%N\ehomes\eprofile_path will cause problems)\.
+.sp
+This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine\.
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBWarning\fR
+Do not quote the value. Setting this as
+\fB\\%N\profile\%U\fR
+will break profile handling. Where the tdbsam or ldapsam passdb backend is used, at the time the user account is created the value configured for this parameter is written to the passdb backend and that value will over-ride the parameter value present in the smb.conf file. Any error present in the passdb backend account record must be editted using the appropriate tool (pdbedit on the command-line, or any other locally provided system tool).
+Note that this option is only useful if Samba is set up as a domain controller.
+.sp
+Disable the use of roaming profiles by setting the value of this parameter to the empty string. For example,
+logon path = "". Take note that even if the default setting in the smb.conf file is the empty string, any value specified in the user account settings in the passdb backend will over-ride the effect of setting this parameter to null. Disabling of all roaming profile use requires that the user account settings must also be blank.
+Warning
+Do not quote the value\. Setting this as
+\(lq\e\e%N\eprofile\e%U\(rq
+will break profile handling\. Where the tdbsam or ldapsam passdb backend is used, at the time the user account is created the value configured for this parameter is written to the passdb backend and that value will over\-ride the parameter value present in the smb\.conf file\. Any error present in the passdb backend account record must be editted using the appropriate tool (pdbedit on the command\-line, or any other locally provided system tool)\.
+Note that this option is only useful if Samba is set up as a domain controller\.
+.sp
+Disable the use of roaming profiles by setting the value of this parameter to the empty string\. For example,
+\fIlogon path = ""\fR\. Take note that even if the default setting in the smb\.conf file is the empty string, any value specified in the user account settings in the passdb backend will over\-ride the effect of setting this parameter to null\. Disabling of all roaming profile use requires that the user account settings must also be blank\.
 .sp
 An example of use is:
+.sp
+.sp
+.RS 4
 .nf
+logon path = \\PROFILESERVER\PROFILE\%U
+logon path = \e\ePROFILESERVER\ePROFILE\e%U
 .fi
+.sp
+Default:
+\fB\fIlogon path\fR = \\\\%N\\%U\\profile \fR
+.RE
+.PP
+.RE
+.sp
+.sp
+Default:
+\fI\fIlogon path\fR\fR\fI = \fR\fI\e\e%N\e%U\eprofile\fR\fI \fR
+.RE
 logon script (G)
+.RS 3n
+This parameter specifies the batch file (\fI.bat\fR) or NT command file (\fI.cmd\fR) to be downloaded and run on a machine when a user successfully logs in. The file must contain the DOS style CR/LF line endings. Using a DOS-style editor to create the file is recommended.
+.PP
+.RS 4
+This parameter specifies the batch file (\fI\.bat\fR) or NT command file (\fI\.cmd\fR) to be downloaded and run on a machine when a user successfully logs in\. The file must contain the DOS style CR/LF line endings\. Using a DOS\-style editor to create the file is recommended\.
 .sp
 The script must be a relative path to the
 \fI[netlogon]\fR
+service. If the [netlogon] service specifies a
+path of
+service\. If the [netlogon] service specifies a
+\fIpath\fR
+of
 \fI/usr/local/samba/netlogon\fR, and
+logon script = STARTUP.BAT, then the file that will be downloaded is:
+.sp
+\fIlogon script = STARTUP\.BAT\fR, then the file that will be downloaded is:
+.sp
+.RS 4
 .nf
+        /usr/local/samba/netlogon/STARTUP.BAT
+        /usr/local/samba/netlogon/STARTUP\.BAT
 .fi
+.sp
+The contents of the batch file are entirely your choice. A suggested command would be to add
+NET TIME \\\\SERVER /SET /YES, to force every machine to synchronize clocks with the same time server. Another use would be to add
+NET USE U: \\\\SERVER\\UTILS
+.RE
+.sp
+.sp
+The contents of the batch file are entirely your choice\. A suggested command would be to add
+NET TIME \e\eSERVER /SET /YES, to force every machine to synchronize clocks with the same time server\. Another use would be to add
+NET USE U: \e\eSERVER\eUTILS
 for commonly used utilities, or
+.sp
+.sp
+.RS 4
 .nf
+\fBNET USE Q: \\SERVER\ISO9001_QA\fR
+\fBNET USE Q: \e\eSERVER\eISO9001_QA\fR
 .fi
+for example.
+.sp
+Note that it is particularly important not to allow write access to the [netlogon] share, or to grant users write permission on the batch files in a secure environment, as this would allow the batch files to be arbitrarily modified and security to be breached.
+.sp
+This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine.
+.sp
+This option is only useful if Samba is set up as a logon server.
+.sp
+Default:
+\fB\fIlogon script\fR = \fR
+.sp
+Example:
+\fB\fIlogon script\fR = scripts\\%U.bat \fR
+.RE
+.PP
+.RE
+.sp
+for example\.
+.sp
+Note that it is particularly important not to allow write access to the [netlogon] share, or to grant users write permission on the batch files in a secure environment, as this would allow the batch files to be arbitrarily modified and security to be breached\.
+.sp
+This option takes the standard substitutions, allowing you to have separate logon scripts for each user or machine\.
+.sp
+This option is only useful if Samba is set up as a logon server\.
+.sp
+Default:
+\fI\fIlogon script\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fIlogon script\fR\fR\fI = \fR\fIscripts\e%U\.bat\fR\fI \fR
+.RE
 lppause command (S)
+.RS 3n
+This parameter specifies the command to be executed on the server host in order to stop printing or spooling a specific print job.
+.sp
+This command should be a program or script which takes a printer name and job number to pause the print job. One way of implementing this is by using job priorities, where jobs having a too low priority won't be sent to the printer.
+.PP
+.RS 4
+This parameter specifies the command to be executed on the server host in order to stop printing or spooling a specific print job\.
+.sp
+This command should be a program or script which takes a printer name and job number to pause the print job\. One way of implementing this is by using job priorities, where jobs having a too low priority won\'t be sent to the printer\.
 .sp
 If a
 \fI%p\fR
 is given then the printer name is put in its place. A
+is given then the printer name is put in its place\. A
 \fI%j\fR
 is replaced with the job number (an integer). On HPUX (see
+is replaced with the job number (an integer)\. On HPUX (see
 \fIprinting=hpux \fR), if the
 \fI-p%p\fR
 option is added to the lpq command, the job will show up with the correct status, i.e. if the job priority is lower than the set fence priority it will have the PAUSED status, whereas if the priority is equal or higher it will have the SPOOLED or PRINTING status.
 .sp
 Note that it is good practice to include the absolute path in the lppause command as the PATH may not be available to the server.
 .sp
 Default:
 \fB\fIlppause command\fR = # Currently no default value is given to this string, unless the value of the printing parameter is \\fBSYSV\\fR, in which case the default is : lp -i %p-%j -H hold or if the value of the \\fIprinting\\fR parameter is \\fBSOFTQ\\fR, then the default is: qstat -s -j%j -h. \fR
 .sp
 Example:
 \fB\fIlppause command\fR = /usr/bin/lpalt %p-%j -p0 \fR
 .RE
+.PP
+\fI\-p%p\fR
+option is added to the lpq command, the job will show up with the correct status, i\.e\. if the job priority is lower than the set fence priority it will have the PAUSED status, whereas if the priority is equal or higher it will have the SPOOLED or PRINTING status\.
+.sp
+Note that it is good practice to include the absolute path in the lppause command as the PATH may not be available to the server\.
+.sp
+Default:
+\fI\fIlppause command\fR\fR\fI = \fR\fI # Currently no default value is given to this string, unless the value of the \fIprinting\fR parameter is \fBSYSV\fR, in which case the default is : lp \-i %p\-%j \-H hold or if the value of the \fIprinting\fR parameter is \fBSOFTQ\fR, then the default is: qstat \-s \-j%j \-h\. \fR\fI \fR
+.sp
+Example:
+\fI\fIlppause command\fR\fR\fI = \fR\fI/usr/bin/lpalt %p\-%j \-p0\fR\fI \fR
+.RE
 lpq cache time (G)
+.RS 3n
+.PP
+.RS 4
 This controls how long lpq info will be cached for to prevent the
 lpq
 command being called too often. A separate cache is kept for each variation of the
+command being called too often\. A separate cache is kept for each variation of the
 lpq
 command used by the system, so if you use different
 lpq
 commands for different users then they won't share cache information.
+commands for different users then they won\'t share cache information\.
 .sp
 The cache files are stored in
 \fI/tmp/lpq.xxxx\fR
+\fI/tmp/lpq\.xxxx\fR
 where xxxx is a hash of the
 lpq
 command in use.
+command in use\.
 .sp
 The default is 30 seconds, meaning that the cached results of a previous identical
 lpq
 command will be used if the cached data is less than 30 seconds old. A large value may be advisable if your
+command will be used if the cached data is less than 30 seconds old\. A large value may be advisable if your
 lpq
 command is very slow.
 .sp
 A value of 0 will disable caching completely.
 .sp
 Default:
 \fB\fIlpq cache time\fR = 30 \fR
 .sp
 Example:
 \fB\fIlpq cache time\fR = 10 \fR
 .RE
+.PP
+command is very slow\.
+.sp
+A value of 0 will disable caching completely\.
+.sp
+Default:
+\fI\fIlpq cache time\fR\fR\fI = \fR\fI30\fR\fI \fR
+.sp
+Example:
+\fI\fIlpq cache time\fR\fR\fI = \fR\fI10\fR\fI \fR
+.RE
 lpq command (S)
+.RS 3n
+.PP
+.RS 4
 This parameter specifies the command to be executed on the server host in order to obtain
 lpq-style printer status information.
 .sp
 This command should be a program or script which takes a printer name as its only parameter and outputs printer status information.
 .sp
 Currently nine styles of printer status information are supported; BSD, AIX, LPRNG, PLP, SYSV, HPUX, QNX, CUPS, and SOFTQ. This covers most UNIX systems. You control which type is expected using the
+lpq\-style printer status information\.
+.sp
+This command should be a program or script which takes a printer name as its only parameter and outputs printer status information\.
+.sp
+Currently nine styles of printer status information are supported; BSD, AIX, LPRNG, PLP, SYSV, HPUX, QNX, CUPS, and SOFTQ\. This covers most UNIX systems\. You control which type is expected using the
 \fIprinting =\fR
 option.
 .sp
 Some clients (notably Windows for Workgroups) may not correctly send the connection number for the printer they are requesting status information about. To get around this, the server reports on the first printer service connected to by the client. This only happens if the connection number sent is invalid.
+option\.
+.sp
+Some clients (notably Windows for Workgroups) may not correctly send the connection number for the printer they are requesting status information about\. To get around this, the server reports on the first printer service connected to by the client\. This only happens if the connection number sent is invalid\.
 .sp
 If a
 \fI%p\fR
 is given then the printer name is put in its place. Otherwise it is placed at the end of the command.
+is given then the printer name is put in its place\. Otherwise it is placed at the end of the command\.
 .sp
 Note that it is good practice to include the absolute path in the
 …
 as the
 \fB$PATH \fR
 may not be available to the server. When compiled with the CUPS libraries, no
+may not be available to the server\. When compiled with the CUPS libraries, no
 \fIlpq command\fR
 is needed because smbd will make a library call to obtain the print queue listing.
 .sp
 Default:
 \fB\fIlpq command\fR = \fR
 .sp
 Example:
 \fB\fIlpq command\fR = /usr/bin/lpq -P%p \fR
 .RE
+.PP
+is needed because smbd will make a library call to obtain the print queue listing\.
+.sp
+Default:
+\fI\fIlpq command\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fIlpq command\fR\fR\fI = \fR\fI/usr/bin/lpq \-P%p\fR\fI \fR
+.RE
 lpresume command (S)
+.RS 3n
+This parameter specifies the command to be executed on the server host in order to restart or continue printing or spooling a specific print job.
+.sp
+This command should be a program or script which takes a printer name and job number to resume the print job. See also the
+lppause command parameter.
+.PP
+.RS 4
+This parameter specifies the command to be executed on the server host in order to restart or continue printing or spooling a specific print job\.
+.sp
+This command should be a program or script which takes a printer name and job number to resume the print job\. See also the
+\fIlppause command\fR
+parameter\.
 .sp
 If a
 \fI%p\fR
 is given then the printer name is put in its place. A
+is given then the printer name is put in its place\. A
 \fI%j\fR
 is replaced with the job number (an integer).
+is replaced with the job number (an integer)\.
 .sp
 Note that it is good practice to include the absolute path in the
 \fIlpresume command\fR
 as the PATH may not be available to the server.
+as the PATH may not be available to the server\.
 .sp
 See also the
+printing parameter.
+\fIprinting\fR
+parameter\.
 .sp
 Default: Currently no default value is given to this string, unless the value of the
 \fIprinting\fR
 parameter is
 \fBSYSV\fR, in which case the default is :
 .sp
 lp -i %p-%j -H resume
+\fBSYSV\fR, in which case the default is:
+.sp
+lp \-i %p\-%j \-H resume
 .sp
 or if the value of the
 …
 \fBSOFTQ\fR, then the default is:
 .sp
+qstat -s -j%j -r
+.sp
+Default:
+\fB\fIlpresume command\fR = lpresume command = /usr/bin/lpalt %p-%j -p2 \fR
+.RE
+.PP
+qstat \-s \-j%j \-r
+.sp
+\fINo default\fR
+.sp
+Example:
+\fI\fIlpresume command\fR\fR\fI = \fR\fI/usr/bin/lpalt %p\-%j \-p2\fR\fI \fR
+.RE
 lprm command (S)
+.RS 3n
+This parameter specifies the command to be executed on the server host in order to delete a print job.
+.sp
+This command should be a program or script which takes a printer name and job number, and deletes the print job.
+.PP
+.RS 4
+This parameter specifies the command to be executed on the server host in order to delete a print job\.
+.sp
+This command should be a program or script which takes a printer name and job number, and deletes the print job\.
 .sp
 If a
 \fI%p\fR
 is given then the printer name is put in its place. A
+is given then the printer name is put in its place\. A
 \fI%j\fR
 is replaced with the job number (an integer).
+is replaced with the job number (an integer)\.
 .sp
 Note that it is good practice to include the absolute path in the
 \fIlprm command\fR
 as the PATH may not be available to the server.
+as the PATH may not be available to the server\.
 .sp
 Examples of use are:
+.sp
+.sp
+.RS 4
 .nf
+lprm command = /usr/bin/lprm -P%p %j
+lprm command = /usr/bin/lprm \-P%p %j
 or
+lprm command = /usr/bin/cancel %p-%j
+lprm command = /usr/bin/cancel %p\-%j
 .fi
+.sp
+Default:
+\fB\fIlprm command\fR = determined by printing parameter \fR
+.RE
+.PP
+.RE
+.sp
+.sp
+Default:
+\fI\fIlprm command\fR\fR\fI = \fR\fI determined by printing parameter\fR\fI \fR
+.RE
 machine password timeout (G)
+.RS 3n
+.PP
+.RS 4
 If a Samba server is a member of a Windows NT Domain (see the
+security = domain parameter) then periodically a running smbd process will try and change the MACHINE ACCOUNT PASSWORD stored in the TDB called
+\fIprivate/secrets.tdb \fR. This parameter specifies how often this password will be changed, in seconds. The default is one week (expressed in seconds), the same as a Windows NT Domain member server.
+\fIsecurity = domain\fR
+parameter) then periodically a running smbd process will try and change the MACHINE ACCOUNT PASSWORD stored in the TDB called
+\fIprivate/secrets\.tdb \fR\. This parameter specifies how often this password will be changed, in seconds\. The default is one week (expressed in seconds), the same as a Windows NT Domain member server\.
 .sp
 See also
 \fBsmbpasswd\fR(8), and the
+security = domain parameter.
+.sp
+Default:
+\fB\fImachine password timeout\fR = 604800 \fR
+.RE
+.PP
+\fIsecurity = domain\fR
+parameter\.
+.sp
+Default:
+\fI\fImachine password timeout\fR\fR\fI = \fR\fI604800\fR\fI \fR
+.RE
 magic output (S)
+.RS 3n
+.PP
+.RS 4
 This parameter specifies the name of a file which will contain output created by a magic script (see the
+magic script parameter below).
+\fImagic script\fR
+parameter below)\.
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBWarning\fR
+Warning
 If two clients use the same
 \fImagic script \fR
+in the same directory the output file content is undefined.
+Default:
+\fB\fImagic output\fR = <magic script name>.out \fR
+.sp
+Example:
+\fB\fImagic output\fR = myfile.txt \fR
+.RE
+.PP
+in the same directory the output file content is undefined\.
+Default:
+\fI\fImagic output\fR\fR\fI = \fR\fI<magic script name>\.out\fR\fI \fR
+.sp
+Example:
+\fI\fImagic output\fR\fR\fI = \fR\fImyfile\.txt\fR\fI \fR
+.RE
 magic script (S)
+.RS 3n
+This parameter specifies the name of a file which, if opened, will be executed by the server when the file is closed. This allows a UNIX script to be sent to the Samba host and executed on behalf of the connected user.
+.sp
+Scripts executed in this way will be deleted upon completion assuming that the user has the appropriate level of privilege and the file permissions allow the deletion.
+.PP
+.RS 4
+This parameter specifies the name of a file which, if opened, will be executed by the server when the file is closed\. This allows a UNIX script to be sent to the Samba host and executed on behalf of the connected user\.
+.sp
+Scripts executed in this way will be deleted upon completion assuming that the user has the appropriate level of privilege and the file permissions allow the deletion\.
 .sp
 If the script generates output, output will be sent to the file specified by the
+magic output parameter (see above).
+.sp
+Note that some shells are unable to interpret scripts containing CR/LF instead of CR as the end-of-line marker. Magic scripts must be executable
+\fBas is\fR
+on the host, which for some hosts and some shells will require filtering at the DOS end.
+\fImagic output\fR
+parameter (see above)\.
+.sp
+Note that some shells are unable to interpret scripts containing CR/LF instead of CR as the end\-of\-line marker\. Magic scripts must be executable
+\fIas is\fR
+on the host, which for some hosts and some shells will require filtering at the DOS end\.
 .sp
 Magic scripts are
 \fBEXPERIMENTAL\fR
+\fIEXPERIMENTAL\fR
 and should
 \fBNOT\fR
 be relied upon.
 .sp
 Default:
 \fB\fImagic script\fR = \fR
 .sp
 Example:
 \fB\fImagic script\fR = user.csh \fR
 .RE
+.PP
+\fINOT\fR
+be relied upon\.
+.sp
+Default:
+\fI\fImagic script\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fImagic script\fR\fR\fI = \fR\fIuser\.csh\fR\fI \fR
+.RE
 mangled map (S)
+.RS 3n
+This is for those who want to directly map UNIX file names which cannot be represented on Windows/DOS. The mangling of names is not always what is needed. In particular you may have documents with file extensions that differ between DOS and UNIX. For example, under UNIX it is common to use
+\fI.html\fR
+.PP
+.RS 4
+This is for those who want to directly map UNIX file names which cannot be represented on Windows/DOS\. The mangling of names is not always what is needed\. In particular you may have documents with file extensions that differ between DOS and UNIX\. For example, under UNIX it is common to use
+\fI\.html\fR
 for HTML files, whereas under Windows/DOS
 \fI.htm\fR
 is more commonly used.
+\fI\.htm\fR
+is more commonly used\.
 .sp
 So to map
 …
 .sp
 mangled map = (*.html *.htm).
+\fImangled map = (*\.html *\.htm)\fR\.
 .sp
 One very useful case is to remove the annoying
 \fI;1\fR
 off the ends of filenames on some CDROMs (only visible under some UNIXes). To do this use a map of (*;1 *;).
 .sp
 Default:
 \fB\fImangled map\fR = # no mangled map \fR
 .sp
 Example:
 \fB\fImangled map\fR = (*;1 *;) \fR
 .RE
+.PP
+off the ends of filenames on some CDROMs (only visible under some UNIXes)\. To do this use a map of (*;1 *;)\.
+.sp
+Default:
+\fI\fImangled map\fR\fR\fI = \fR\fI # no mangled map\fR\fI \fR
+.sp
+Example:
+\fI\fImangled map\fR\fR\fI = \fR\fI(*;1 *;)\fR\fI \fR
+.RE
 mangled names (S)
+.RS 3n
+This controls whether non-DOS names under UNIX should be mapped to DOS-compatible names ("mangled") and made visible, or whether non-DOS names should simply be ignored.
+.PP
+.RS 4
+This controls whether non\-DOS names under UNIX should be mapped to DOS\-compatible names ("mangled") and made visible, or whether non\-DOS names should simply be ignored\.
 .sp
 See the section on
+name mangling for details on how to control the mangling process.
+\fIname mangling\fR
+for details on how to control the mangling process\.
 .sp
 If mangling is used then the mangling algorithm is as follows:
+.RS 3n
+.TP 3n
+\(bu
+The first (up to) five alphanumeric characters before the rightmost dot of the filename are preserved, forced to upper case, and appear as the first (up to) five characters of the mangled name.
+.TP 3n
+\(bu
+A tilde "~" is appended to the first part of the mangled name, followed by a two-character unique sequence, based on the original root name (i.e., the original filename minus its final extension). The final extension is included in the hash calculation only if it contains any upper case characters or is longer than three characters.
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+The first (up to) five alphanumeric characters before the rightmost dot of the filename are preserved, forced to upper case, and appear as the first (up to) five characters of the mangled name\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+A tilde "~" is appended to the first part of the mangled name, followed by a two\-character unique sequence, based on the original root name (i\.e\., the original filename minus its final extension)\. The final extension is included in the hash calculation only if it contains any upper case characters or is longer than three characters\.
 .sp
 Note that the character to use may be specified using the
+mangling char option, if you don't like '~'.
+.TP 3n
+\(bu
+Files whose UNIX name begins with a dot will be presented as DOS hidden files. The mangled name will be created as for other filenames, but with the leading dot removed and "___" as its extension regardless of actual original extension (that's three underscores).
+.RE
+.IP "" 3n
+The two-digit hash value consists of upper case alphanumeric characters.
+.sp
+This algorithm can cause name collisions only if files in a directory share the same first five alphanumeric characters. The probability of such a clash is 1/1300.
+.sp
+The name mangling (if enabled) allows a file to be copied between UNIX directories from Windows/DOS while retaining the long UNIX filename. UNIX files can be renamed to a new extension from Windows/DOS and will retain the same basename. Mangled names do not change between sessions.
+.sp
+Default:
+\fB\fImangled names\fR = yes \fR
+.RE
+.PP
+\fImangling char\fR
+option, if you don\'t like \'~\'\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+Files whose UNIX name begins with a dot will be presented as DOS hidden files\. The mangled name will be created as for other filenames, but with the leading dot removed and "___" as its extension regardless of actual original extension (that\'s three underscores)\.
+.sp
+.RE
+The two\-digit hash value consists of upper case alphanumeric characters\.
+.sp
+This algorithm can cause name collisions only if files in a directory share the same first five alphanumeric characters\. The probability of such a clash is 1/1300\.
+.sp
+The name mangling (if enabled) allows a file to be copied between UNIX directories from Windows/DOS while retaining the long UNIX filename\. UNIX files can be renamed to a new extension from Windows/DOS and will retain the same basename\. Mangled names do not change between sessions\.
+.sp
+Default:
+\fI\fImangled names\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 mangle prefix (G)
+.RS 3n
+controls the number of prefix characters from the original name used when generating the mangled names. A larger value will give a weaker hash and therefore more name collisions. The minimum value is 1 and the maximum value is 6.
+.sp
+mangle prefix is effective only when mangling method is hash2.
+.sp
+Default:
+\fB\fImangle prefix\fR = 1 \fR
+.sp
+Example:
+\fB\fImangle prefix\fR = 4 \fR
+.RE
+.PP
+.PP
+.RS 4
+controls the number of prefix characters from the original name used when generating the mangled names\. A larger value will give a weaker hash and therefore more name collisions\. The minimum value is 1 and the maximum value is 6\.
+.sp
+mangle prefix is effective only when mangling method is hash2\.
+.sp
+Default:
+\fI\fImangle prefix\fR\fR\fI = \fR\fI1\fR\fI \fR
+.sp
+Example:
+\fI\fImangle prefix\fR\fR\fI = \fR\fI4\fR\fI \fR
+.RE
 mangling char (S)
+.RS 3n
+.PP
+.RS 4
 This controls what character is used as the
 \fBmagic\fR
+\fImagic\fR
 character in
 name mangling. The default is a '~' but this may interfere with some software. Use this option to set it to whatever you prefer. This is effective only when mangling method is hash.
 .sp
 Default:
 \fB\fImangling char\fR = ~ \fR
 .sp
 Example:
 \fB\fImangling char\fR = ^ \fR
 .RE
+.PP
+\fIname mangling\fR\. The default is a \'~\' but this may interfere with some software\. Use this option to set it to whatever you prefer\. This is effective only when mangling method is hash\.
+.sp
+Default:
+\fI\fImangling char\fR\fR\fI = \fR\fI~\fR\fI \fR
+.sp
+Example:
+\fI\fImangling char\fR\fR\fI = \fR\fI^\fR\fI \fR
+.RE
 mangling method (G)
+.RS 3n
+controls the algorithm used for the generating the mangled names. Can take two different values, "hash" and "hash2". "hash" is the algorithm that was used used in Samba for many years and was the default in Samba 2.2.x "hash2" is now the default and is newer and considered a better algorithm (generates less collisions) in the names. Many Win32 applications store the mangled names and so changing to algorithms must not be done lightly as these applications may break unless reinstalled.
+.sp
+Default:
+\fB\fImangling method\fR = hash2 \fR
+.sp
+Example:
+\fB\fImangling method\fR = hash \fR
+.RE
+.PP
+.PP
+.RS 4
+controls the algorithm used for the generating the mangled names\. Can take two different values, "hash" and "hash2"\. "hash" is the algorithm that was used used in Samba for many years and was the default in Samba 2\.2\.x "hash2" is now the default and is newer and considered a better algorithm (generates less collisions) in the names\. Many Win32 applications store the mangled names and so changing to algorithms must not be done lightly as these applications may break unless reinstalled\.
+.sp
+Default:
+\fI\fImangling method\fR\fR\fI = \fR\fIhash2\fR\fI \fR
+.sp
+Example:
+\fI\fImangling method\fR\fR\fI = \fR\fIhash\fR\fI \fR
+.RE
 map acl inherit (S)
+.RS 3n
+.PP
+.RS 4
 This boolean parameter controls whether
 \fBsmbd\fR(8)
 will attempt to map the 'inherit' and 'protected' access control entry flags stored in Windows ACLs into an extended attribute called user.SAMBA_PAI. This parameter only takes effect if Samba is being run on a platform that supports extended attributes (Linux and IRIX so far) and allows the Windows 2000 ACL editor to correctly use inheritance with the Samba POSIX ACL mapping code.
 .sp
 Default:
 \fB\fImap acl inherit\fR = no \fR
 .RE
+.PP
+will attempt to map the \'inherit\' and \'protected\' access control entry flags stored in Windows ACLs into an extended attribute called user\.SAMBA_PAI\. This parameter only takes effect if Samba is being run on a platform that supports extended attributes (Linux and IRIX so far) and allows the Windows 2000 ACL editor to correctly use inheritance with the Samba POSIX ACL mapping code\.
+.sp
+Default:
+\fI\fImap acl inherit\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 map archive (S)
+.RS 3n
+This controls whether the DOS archive attribute should be mapped to the UNIX owner execute bit. The DOS archive bit is set when a file has been modified since its last backup. One motivation for this option is to keep Samba/your PC from making any file it touches from becoming executable under UNIX. This can be quite annoying for shared source code, documents, etc...
+.PP
+.RS 4
+This controls whether the DOS archive attribute should be mapped to the UNIX owner execute bit\. The DOS archive bit is set when a file has been modified since its last backup\. One motivation for this option is to keep Samba/your PC from making any file it touches from becoming executable under UNIX\. This can be quite annoying for shared source code, documents, etc\.\.\.
 .sp
 Note that this requires the
+create mask parameter to be set such that owner execute bit is not masked out (i.e. it must include 100). See the parameter
+create mask for details.
+.sp
+Default:
+\fB\fImap archive\fR = yes \fR
+.RE
+.PP
+\fIcreate mask\fR
+parameter to be set such that owner execute bit is not masked out (i\.e\. it must include 100)\. See the parameter
+\fIcreate mask\fR
+for details\.
+.sp
+Default:
+\fI\fImap archive\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 map hidden (S)
+.RS 3n
+This controls whether DOS style hidden files should be mapped to the UNIX world execute bit.
+.PP
+.RS 4
+This controls whether DOS style hidden files should be mapped to the UNIX world execute bit\.
 .sp
 Note that this requires the
+create mask to be set such that the world execute bit is not masked out (i.e. it must include 001). See the parameter
+create mask for details.
+.sp
+\fBNo default\fR
+.RE
+.PP
+\fIcreate mask\fR
+to be set such that the world execute bit is not masked out (i\.e\. it must include 001)\. See the parameter
+\fIcreate mask\fR
+for details\.
+.sp
+\fINo default\fR
+.RE
 map read only (S)
+.RS 3n
+This controls how the DOS read only attribute should be mapped from a UNIX filesystem.
+.PP
+.RS 4
+This controls how the DOS read only attribute should be mapped from a UNIX filesystem\.
 .sp
 This parameter can take three different values, which tell
 \fBsmbd\fR(8)
 how to display the read only attribute on files, where either
+store dos attributes is set to
+\fBNo\fR, or no extended attribute is present. If
+store dos attributes is set to
+\fIstore dos attributes\fR
+is set to
+\fBNo\fR, or no extended attribute is present\. If
+\fIstore dos attributes\fR
+is set to
 \fByes\fR
 then this parameter is
 \fBignored\fR. This is a new parameter introduced in Samba version 3.0.21.
+\fIignored\fR\. This is a new parameter introduced in Samba version 3\.0\.21\.
 .sp
 The three settings are :
+.RS 3n
+.TP 3n
+\(bu
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fBYes\fR
+- The read only DOS attribute is mapped to the inverse of the user or owner write bit in the unix permission mode set. If the owner write bit is not set, the read only attribute is reported as being set on the file.
+.TP 3n
+\(bu
+\- The read only DOS attribute is mapped to the inverse of the user or owner write bit in the unix permission mode set\. If the owner write bit is not set, the read only attribute is reported as being set on the file\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fBPermissions\fR
 - The read only DOS attribute is mapped to the effective permissions of the connecting user, as evaluated by
+\- The read only DOS attribute is mapped to the effective permissions of the connecting user, as evaluated by
 \fBsmbd\fR(8)
+by reading the unix permissions and POSIX ACL (if present). If the connecting user does not have permission to modify the file, the read only attribute is reported as being set on the file.
+.TP 3n
+\(bu
+by reading the unix permissions and POSIX ACL (if present)\. If the connecting user does not have permission to modify the file, the read only attribute is reported as being set on the file\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fBNo\fR
+- The read only DOS attribute is unaffected by permissions, and can only be set by the
+store dos attributes method. This may be useful for exporting mounted CDs.
+.RE
+.IP "" 3n
+Default:
+\fB\fImap read only\fR = yes \fR
+.RE
+.PP
+\- The read only DOS attribute is unaffected by permissions, and can only be set by the
+\fIstore dos attributes\fR
+method\. This may be useful for exporting mounted CDs\.
+.sp
+.RE
+Default:
+\fI\fImap read only\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 map system (S)
+.RS 3n
+This controls whether DOS style system files should be mapped to the UNIX group execute bit.
+.PP
+.RS 4
+This controls whether DOS style system files should be mapped to the UNIX group execute bit\.
 .sp
 Note that this requires the
+create mask to be set such that the group execute bit is not masked out (i.e. it must include 010). See the parameter
+create mask for details.
+.sp
+Default:
+\fB\fImap system\fR = no \fR
+.RE
+.PP
+\fIcreate mask\fR
+to be set such that the group execute bit is not masked out (i\.e\. it must include 010)\. See the parameter
+\fIcreate mask\fR
+for details\.
+.sp
+Default:
+\fI\fImap system\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 map to guest (G)
+.RS 3n
+.PP
+.RS 4
 This parameter is only useful in
+SECURITY = security modes other than
+\fISECURITY = security\fR
+modes other than
 \fIsecurity = share\fR
 and
 \fIsecurity = server\fR
 - i.e.
+\- i\.e\.
 \fBuser\fR, and
 \fBdomain\fR.
+\fBdomain\fR\.
 .sp
 This parameter can take four different values, which tell
 \fBsmbd\fR(8)
 what to do with user login requests that don't match a valid UNIX user in some way.
+what to do with user login requests that don\'t match a valid UNIX user in some way\.
 .sp
 The four settings are :
+.RS 3n
+.TP 3n
+\(bu
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fBNever\fR
+- Means user login requests with an invalid password are rejected. This is the default.
+.TP 3n
+\(bu
+\- Means user login requests with an invalid password are rejected\. This is the default\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fBBad User\fR
+- Means user logins with an invalid password are rejected, unless the username does not exist, in which case it is treated as a guest login and mapped into the
+guest account.
+.TP 3n
+\(bu
+\- Means user logins with an invalid password are rejected, unless the username does not exist, in which case it is treated as a guest login and mapped into the
+\fIguest account\fR\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fBBad Password\fR
 - Means user logins with an invalid password are treated as a guest login and mapped into the
 guest account. Note that this can cause problems as it means that any user incorrectly typing their password will be silently logged on as "guest" - and will not know the reason they cannot access files they think they should - there will have been no message given to them that they got their password wrong. Helpdesk services will
 \fBhate\fR
+\- Means user logins with an invalid password are treated as a guest login and mapped into the
+\fIguest account\fR\. Note that this can cause problems as it means that any user incorrectly typing their password will be silently logged on as "guest" \- and will not know the reason they cannot access files they think they should \- there will have been no message given to them that they got their password wrong\. Helpdesk services will
+\fIhate\fR
 you if you set the
 \fImap to guest\fR
+parameter this way :-).
+.TP 3n
+\(bu
+parameter this way :\-)\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fBBad Uid\fR
 - Is only applicable when Samba is configured in some type of domain mode security (security = {domain|ads}) and means that user logins which are successfully authenticated but which have no valid Unix user account (and smbd is unable to create one) should be mapped to the defined guest account. This was the default behavior of Samba 2.x releases. Note that if a member server is running winbindd, this option should never be required because the nss_winbind library will export the Windows domain users and groups to the underlying OS via the Name Service Switch interface.
 .RE
 .IP "" 3n
+\- Is only applicable when Samba is configured in some type of domain mode security (security = {domain|ads}) and means that user logins which are successfully authenticated but which have no valid Unix user account (and smbd is unable to create one) should be mapped to the defined guest account\. This was the default behavior of Samba 2\.x releases\. Note that if a member server is running winbindd, this option should never be required because the nss_winbind library will export the Windows domain users and groups to the underlying OS via the Name Service Switch interface\.
+.sp
+.RE
 Note that this parameter is needed to set up "Guest" share services when using
 \fIsecurity\fR
 modes other than share and server. This is because in these modes the name of the resource being requested is
 \fBnot\fR
 sent to the server until after the server has successfully authenticated the client so the server cannot make authentication decisions at the correct time (connection to the share) for "Guest" shares. This parameter is not useful with
+modes other than share and server\. This is because in these modes the name of the resource being requested is
+\fInot\fR
+sent to the server until after the server has successfully authenticated the client so the server cannot make authentication decisions at the correct time (connection to the share) for "Guest" shares\. This parameter is not useful with
 \fIsecurity = server\fR
 as in this security mode no information is returned about whether a user logon failed due to a bad username or bad password, the same error is returned from a modern server in both cases.
 .sp
 For people familiar with the older Samba releases, this parameter maps to the old compile-time setting of the
+as in this security mode no information is returned about whether a user logon failed due to a bad username or bad password, the same error is returned from a modern server in both cases\.
+.sp
+For people familiar with the older Samba releases, this parameter maps to the old compile\-time setting of the
 \fB GUEST_SESSSETUP\fR
 value in local.h.
 .sp
 Default:
 \fB\fImap to guest\fR = Never \fR
 .sp
 Example:
 \fB\fImap to guest\fR = Bad User \fR
 .RE
+.PP
+value in local\.h\.
+.sp
+Default:
+\fI\fImap to guest\fR\fR\fI = \fR\fINever\fR\fI \fR
+.sp
+Example:
+\fI\fImap to guest\fR\fR\fI = \fR\fIBad User\fR\fI \fR
+.RE
 max connections (S)
+.RS 3n
+This option allows the number of simultaneous connections to a service to be limited. If
+.PP
+.RS 4
+This option allows the number of simultaneous connections to a service to be limited\. If
 \fImax connections\fR
+is greater than 0 then connections will be refused if this number of connections to the service are already open. A value of zero mean an unlimited number of connections may be made.
+.sp
+Record lock files are used to implement this feature. The lock files will be stored in the directory specified by the
+lock directory option.
+.sp
+Default:
+\fB\fImax connections\fR = 0 \fR
+.sp
+Example:
+\fB\fImax connections\fR = 10 \fR
+.RE
+.PP
+is greater than 0 then connections will be refused if this number of connections to the service are already open\. A value of zero mean an unlimited number of connections may be made\.
+.sp
+Record lock files are used to implement this feature\. The lock files will be stored in the directory specified by the
+\fIlock directory\fR
+option\.
+.sp
+Default:
+\fI\fImax connections\fR\fR\fI = \fR\fI0\fR\fI \fR
+.sp
+Example:
+\fI\fImax connections\fR\fR\fI = \fR\fI10\fR\fI \fR
+.RE
 max disk size (G)
+.RS 3n
+This option allows you to put an upper limit on the apparent size of disks. If you set this option to 100 then all shares will appear to be not larger than 100 MB in size.
+.sp
+Note that this option does not limit the amount of data you can put on the disk. In the above case you could still store much more than 100 MB on the disk, but if a client ever asks for the amount of free disk space or the total disk size then the result will be bounded by the amount specified in
+\fImax disk size\fR.
+.sp
+This option is primarily useful to work around bugs in some pieces of software that can't handle very large disks, particularly disks over 1GB in size.
+.PP
+.RS 4
+This option allows you to put an upper limit on the apparent size of disks\. If you set this option to 100 then all shares will appear to be not larger than 100 MB in size\.
+.sp
+Note that this option does not limit the amount of data you can put on the disk\. In the above case you could still store much more than 100 MB on the disk, but if a client ever asks for the amount of free disk space or the total disk size then the result will be bounded by the amount specified in
+\fImax disk size\fR\.
+.sp
+This option is primarily useful to work around bugs in some pieces of software that can\'t handle very large disks, particularly disks over 1GB in size\.
 .sp
+A
 \fImax disk size\fR
 of 0 means no limit.
 .sp
 Default:
 \fB\fImax disk size\fR = 0 \fR
 .sp
 Example:
 \fB\fImax disk size\fR = 1000 \fR
 .RE
+.PP
+of 0 means no limit\.
+.sp
+Default:
+\fI\fImax disk size\fR\fR\fI = \fR\fI0\fR\fI \fR
+.sp
+Example:
+\fI\fImax disk size\fR\fR\fI = \fR\fI1000\fR\fI \fR
+.RE
 max log size (G)
+.RS 3n
+This option (an integer in kilobytes) specifies the max size the log file should grow to. Samba periodically checks the size and if it is exceeded it will rename the file, adding a
+\fI.old\fR
+extension.
+.sp
+A size of 0 means no limit.
+.sp
+Default:
+\fB\fImax log size\fR = 5000 \fR
+.sp
+Example:
+\fB\fImax log size\fR = 1000 \fR
+.RE
+.PP
+.PP
+.RS 4
+This option (an integer in kilobytes) specifies the max size the log file should grow to\. Samba periodically checks the size and if it is exceeded it will rename the file, adding a
+\fI\.old\fR
+extension\.
+.sp
+A size of 0 means no limit\.
+.sp
+Default:
+\fI\fImax log size\fR\fR\fI = \fR\fI5000\fR\fI \fR
+.sp
+Example:
+\fI\fImax log size\fR\fR\fI = \fR\fI1000\fR\fI \fR
+.RE
 max mux (G)
+.RS 3n
+This option controls the maximum number of outstanding simultaneous SMB operations that Samba tells the client it will allow. You should never need to set this parameter.
+.sp
+Default:
+\fB\fImax mux\fR = 50 \fR
+.RE
+.PP
+.PP
+.RS 4
+This option controls the maximum number of outstanding simultaneous SMB operations that Samba tells the client it will allow\. You should never need to set this parameter\.
+.sp
+Default:
+\fI\fImax mux\fR\fR\fI = \fR\fI50\fR\fI \fR
+.RE
 max open files (G)
+.RS 3n
+.PP
+.RS 4
 This parameter limits the maximum number of open files that one
 \fBsmbd\fR(8)
 file serving process may have open for a client at any one time. The default for this parameter is set very high (10,000) as Samba uses only one bit per unopened file.
 .sp
 The limit of the number of open files is usually set by the UNIX per-process file descriptor limit rather than this parameter so you should never need to touch this parameter.
 .sp
 Default:
 \fB\fImax open files\fR = 10000 \fR
 .RE
+.PP
+file serving process may have open for a client at any one time\. The default for this parameter is set very high (10,000) as Samba uses only one bit per unopened file\.
+.sp
+The limit of the number of open files is usually set by the UNIX per\-process file descriptor limit rather than this parameter so you should never need to touch this parameter\.
+.sp
+Default:
+\fI\fImax open files\fR\fR\fI = \fR\fI10000\fR\fI \fR
+.RE
 max print jobs (S)
+.RS 3n
+This parameter limits the maximum number of jobs allowable in a Samba printer queue at any given moment. If this number is exceeded,
+.PP
+.RS 4
+This parameter limits the maximum number of jobs allowable in a Samba printer queue at any given moment\. If this number is exceeded,
 \fBsmbd\fR(8)
 will remote "Out of Space" to the client.
 .sp
 Default:
 \fB\fImax print jobs\fR = 1000 \fR
 .sp
 Example:
 \fB\fImax print jobs\fR = 5000 \fR
 .RE
 .PP
+protocol
+.RS 3n
 This parameter is a synonym for max protocol.
 .RE
+.PP
+will remote "Out of Space" to the client\.
+.sp
+Default:
+\fI\fImax print jobs\fR\fR\fI = \fR\fI1000\fR\fI \fR
+.sp
+Example:
+\fI\fImax print jobs\fR\fR\fI = \fR\fI5000\fR\fI \fR
+.RE
+protocol.PP
+.RS 4
+This parameter is a synonym for
+max protocol\.
+.RE
 max protocol (G)
+.RS 3n
+The value of the parameter (a string) is the highest protocol level that will be supported by the server.
+.PP
+.RS 4
+The value of the parameter (a string) is the highest protocol level that will be supported by the server\.
 .sp
 Possible values are :
+.RS 3n
+.TP 3n
+\(bu
+\fBCORE\fR: Earliest version. No concept of user names.
+.TP 3n
+\(bu
+\fBCOREPLUS\fR: Slight improvements on CORE for efficiency.
+.TP 3n
+\(bu
+.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
+\fB modern\fR
+version of the protocol. Long filename support.
+.TP 3n
+\(bu
+\fBLANMAN2\fR: Updates to Lanman1 protocol.
+.TP 3n
+\(bu
+\fBNT1\fR: Current up to date version of the protocol. Used by Windows NT. Known as CIFS.
+.RE
+.IP "" 3n
+Normally this option should not be set as the automatic negotiation phase in the SMB protocol takes care of choosing the appropriate protocol.
+.sp
+Default:
+\fB\fImax protocol\fR = NT1 \fR
+.sp
+Example:
+\fB\fImax protocol\fR = LANMAN1 \fR
+.RE
+.PP
+\fI modern\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\.
+.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
+Default:
+\fI\fImax protocol\fR\fR\fI = \fR\fINT1\fR\fI \fR
+.sp
+Example:
+\fI\fImax protocol\fR\fR\fI = \fR\fILANMAN1\fR\fI \fR
+.RE
 max reported print jobs (S)
+.RS 3n
+This parameter limits the maximum number of jobs displayed in a port monitor for Samba printer queue at any given moment. If this number is exceeded, the excess jobs will not be shown. A value of zero means there is no limit on the number of print jobs reported.
+.sp
+Default:
+\fB\fImax reported print jobs\fR = 0 \fR
+.sp
+Example:
+\fB\fImax reported print jobs\fR = 1000 \fR
+.RE
+.PP
+.PP
+.RS 4
+This parameter limits the maximum number of jobs displayed in a port monitor for Samba printer queue at any given moment\. If this number is exceeded, the excess jobs will not be shown\. A value of zero means there is no limit on the number of print jobs reported\.
+.sp
+Default:
+\fI\fImax reported print jobs\fR\fR\fI = \fR\fI0\fR\fI \fR
+.sp
+Example:
+\fI\fImax reported print jobs\fR\fR\fI = \fR\fI1000\fR\fI \fR
+.RE
 max smbd processes (G)
+.RS 3n
+.PP
+.RS 4
 This parameter limits the maximum number of
 \fBsmbd\fR(8)
 processes concurrently running on a system and is intended as a stopgap to prevent degrading service to clients in the event that the server has insufficient resources to handle more than this number of connections. Remember that under normal operating conditions, each user will have an
+processes concurrently running on a system and is intended as a stopgap to prevent degrading service to clients in the event that the server has insufficient resources to handle more than this number of connections\. Remember that under normal operating conditions, each user will have an
 \fBsmbd\fR(8)
 associated with him or her to handle connections to all shares from a given host.
 .sp
 Default:
 \fB\fImax smbd processes\fR = 0 \fR
 .sp
 Example:
 \fB\fImax smbd processes\fR = 1000 \fR
 .RE
+.PP
+associated with him or her to handle connections to all shares from a given host\.
+.sp
+Default:
+\fI\fImax smbd processes\fR\fR\fI = \fR\fI0\fR\fI \fR
+.sp
+Example:
+\fI\fImax smbd processes\fR\fR\fI = \fR\fI1000\fR\fI \fR
+.RE
 max stat cache size (G)
+.RS 3n
+.PP
+.RS 4
 This parameter limits the size in memory of any
 \fIstat cache\fR
 being used to speed up case insensitive name mappings. This parameter is the number of kilobyte (1024) units the stat cache can use. A value of zero means unlimited which is not advised a&#1109; it can use a lot of memory. You should not need to change this parameter.
 .sp
 Default:
 \fB\fImax stat cache size\fR = 1024 \fR
 .sp
 Example:
 \fB\fImax stat cache size\fR = 100 \fR
 .RE
+.PP
+being used to speed up case insensitive name mappings\. It represents the number of kilobyte (1024) units the stat cache can use\. A value of zero, meaning unlimited, is not advisable due to increased memory useage\. You should not need to change this parameter\.
+.sp
+Default:
+\fI\fImax stat cache size\fR\fR\fI = \fR\fI256\fR\fI \fR
+.sp
+Example:
+\fI\fImax stat cache size\fR\fR\fI = \fR\fI100\fR\fI \fR
+.RE
 max ttl (G)
+.RS 3n
+.PP
+.RS 4
 This option tells
 \fBnmbd\fR(8)
 what the default 'time to live' of NetBIOS names should be (in seconds) when
+what the default \'time to live\' of NetBIOS names should be (in seconds) when
 nmbd
 is requesting a name using either a broadcast packet or from a WINS server. You should never need to change this parameter. The default is 3 days.
 .sp
 Default:
 \fB\fImax ttl\fR = 259200 \fR
 .RE
+.PP
+is requesting a name using either a broadcast packet or from a WINS server\. You should never need to change this parameter\. The default is 3 days\.
+.sp
+Default:
+\fI\fImax ttl\fR\fR\fI = \fR\fI259200\fR\fI \fR
+.RE
 max wins ttl (G)
+.RS 3n
+.PP
+.RS 4
 This option tells
 \fBsmbd\fR(8)
 when acting as a WINS server (wins support = yes) what the maximum 'time to live' of NetBIOS names that
+when acting as a WINS server (\fIwins support = yes\fR) what the maximum \'time to live\' of NetBIOS names that
 nmbd
 will grant will be (in seconds). You should never need to change this parameter. The default is 6 days (518400 seconds).
 .sp
 Default:
 \fB\fImax wins ttl\fR = 518400 \fR
 .RE
+.PP
+will grant will be (in seconds)\. You should never need to change this parameter\. The default is 6 days (518400 seconds)\.
+.sp
+Default:
+\fI\fImax wins ttl\fR\fR\fI = \fR\fI518400\fR\fI \fR
+.RE
 max xmit (G)
+.RS 3n
+This option controls the maximum packet size that will be negotiated by Samba. The default is 16644, which matches the behavior of Windows 2000. A value below 2048 is likely to cause problems. You should never need to change this parameter from its default value.
+.sp
+Default:
+\fB\fImax xmit\fR = 16644 \fR
+.sp
+Example:
+\fB\fImax xmit\fR = 8192 \fR
+.RE
+.PP
+.PP
+.RS 4
+This option controls the maximum packet size that will be negotiated by Samba\. The default is 16644, which matches the behavior of Windows 2000\. A value below 2048 is likely to cause problems\. You should never need to change this parameter from its default value\.
+.sp
+Default:
+\fI\fImax xmit\fR\fR\fI = \fR\fI16644\fR\fI \fR
+.sp
+Example:
+\fI\fImax xmit\fR\fR\fI = \fR\fI8192\fR\fI \fR
+.RE
 message command (G)
+.RS 3n
+This specifies what command to run when the server receives a WinPopup style message.
+.sp
+This would normally be a command that would deliver the message somehow. How this is to be done is up to your imagination.
+.PP
+.RS 4
+This specifies what command to run when the server receives a WinPopup style message\.
+.sp
+This would normally be a command that would deliver the message somehow\. How this is to be done is up to your imagination\.
 .sp
 An example is:
+.sp
+.sp
+.RS 4
 .nf
+message command = csh -c 'xedit %s;rm %s' &
+message command = csh \-c \'xedit %s;rm %s\' &
 .fi
+.RE
+.sp
 .sp
 This delivers the message using
 xedit, then removes it afterwards.
 \fBNOTE THAT IT IS VERY IMPORTANT THAT THIS COMMAND RETURN IMMEDIATELY\fR. That's why I have the '&' on the end. If it doesn't return immediately then your PCs may freeze when sending messages (they should recover after 30 seconds, hopefully).
 .sp
 All messages are delivered as the global guest user. The command takes the standard substitutions, although
+xedit, then removes it afterwards\.
+\fINOTE THAT IT IS VERY IMPORTANT THAT THIS COMMAND RETURN IMMEDIATELY\fR\. That\'s why I have the \'&\' on the end\. If it doesn\'t return immediately then your PCs may freeze when sending messages (they should recover after 30 seconds, hopefully)\.
+.sp
+All messages are delivered as the global guest user\. The command takes the standard substitutions, although
 \fI %u\fR
+won't work (\fI%U\fR
+may be better in this case).
+.sp
+Apart from the standard substitutions, some additional ones apply. In particular:
+.RS 3n
+.TP 3n
+\(bu
+won\'t work (\fI%U\fR
+may be better in this case)\.
+.sp
+Apart from the standard substitutions, some additional ones apply\. In particular:
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fI%s\fR
+= the filename containing the message.
+.TP 3n
+\(bu
+= the filename containing the message\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fI%t\fR
+= the destination that the message was sent to (probably the server name).
+.TP 3n
+\(bu
+= the destination that the message was sent to (probably the server name)\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fI%f\fR
+= who the message is from.
+.RE
+.IP "" 3n
+You could make this command send mail, or whatever else takes your fancy. Please let us know of any really interesting ideas you have.
+.sp
+Here's a way of sending the messages as mail to root:
+.sp
+= who the message is from\.
+.sp
+.RE
+You could make this command send mail, or whatever else takes your fancy\. Please let us know of any really interesting ideas you have\.
+.sp
+Here\'s a way of sending the messages as mail to root:
+.sp
+.RS 4
 .nf
+message command = /bin/mail -s 'message from %f on %m' root < %s; rm %s
+message command = /bin/mail \-s \'message from %f on %m\' root < %s; rm %s
 .fi
+.sp
+If you don't have a message command then the message won't be delivered and Samba will tell the sender there was an error. Unfortunately WfWg totally ignores the error code and carries on regardless, saying that the message was delivered.
+.RE
+.sp
+.sp
+If you don\'t have a message command then the message won\'t be delivered and Samba will tell the sender there was an error\. Unfortunately WfWg totally ignores the error code and carries on regardless, saying that the message was delivered\.
 .sp
 If you want to silently delete it then try:
+.sp
+.sp
+.RS 4
 .nf
 message command = rm %s
 .fi
+.sp
+Default:
+\fB\fImessage command\fR = \fR
+.sp
+Example:
+\fB\fImessage command\fR = csh -c 'xedit %s; rm %s' & \fR
+.RE
+.PP
+.RE
+.sp
+.sp
+Default:
+\fI\fImessage command\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fImessage command\fR\fR\fI = \fR\fIcsh \-c \'xedit %s; rm %s\' &\fR\fI \fR
+.RE
 min print space (S)
+.RS 3n
+This sets the minimum amount of free disk space that must be available before a user will be able to spool a print job. It is specified in kilobytes. The default is 0, which means a user can always spool a print job.
+.sp
+Default:
+\fB\fImin print space\fR = 0 \fR
+.sp
+Example:
+\fB\fImin print space\fR = 2000 \fR
+.RE
+.PP
+.PP
+.RS 4
+This sets the minimum amount of free disk space that must be available before a user will be able to spool a print job\. It is specified in kilobytes\. The default is 0, which means a user can always spool a print job\.
+.sp
+Default:
+\fI\fImin print space\fR\fR\fI = \fR\fI0\fR\fI \fR
+.sp
+Example:
+\fI\fImin print space\fR\fR\fI = \fR\fI2000\fR\fI \fR
+.RE
 min protocol (G)
+.RS 3n
+The value of the parameter (a string) is the lowest SMB protocol dialect than Samba will support. Please refer to the
+max protocol parameter for a list of valid protocol names and a brief description of each. You may also wish to refer to the C source code in
+\fIsource/smbd/negprot.c\fR
+for a listing of known protocol dialects supported by clients.
+.PP
+.RS 4
+The value of the parameter (a string) is the lowest SMB protocol dialect than Samba will support\. Please refer to the
+\fImax protocol\fR
+parameter for a list of valid protocol names and a brief description of each\. You may also wish to refer to the C source code in
+\fIsource/smbd/negprot\.c\fR
+for a listing of known protocol dialects supported by clients\.
 .sp
 If you are viewing this parameter as a security measure, you should also refer to the
+lanman auth parameter. Otherwise, you should never need to change this parameter.
+.sp
+Default:
+\fB\fImin protocol\fR = CORE \fR
+.sp
+Example:
+\fB\fImin protocol\fR = NT1 \fR
+.RE
+.PP
+\fIlanman auth\fR
+parameter\. Otherwise, you should never need to change this parameter\.
+.sp
+Default:
+\fI\fImin protocol\fR\fR\fI = \fR\fICORE\fR\fI \fR
+.sp
+Example:
+\fI\fImin protocol\fR\fR\fI = \fR\fINT1\fR\fI \fR
+.RE
 min wins ttl (G)
+.RS 3n
+.PP
+.RS 4
 This option tells
 \fBnmbd\fR(8)
 when acting as a WINS server (wins support = yes) what the minimum 'time to live' of NetBIOS names that
+when acting as a WINS server (\fIwins support = yes\fR) what the minimum \'time to live\' of NetBIOS names that
 nmbd
 will grant will be (in seconds). You should never need to change this parameter. The default is 6 hours (21600 seconds).
 .sp
 Default:
 \fB\fImin wins ttl\fR = 21600 \fR
 .RE
+.PP
+will grant will be (in seconds)\. You should never need to change this parameter\. The default is 6 hours (21600 seconds)\.
+.sp
+Default:
+\fI\fImin wins ttl\fR\fR\fI = \fR\fI21600\fR\fI \fR
+.RE
 msdfs proxy (S)
+.RS 3n
+This parameter indicates that the share is a stand-in for another CIFS share whose location is specified by the value of the parameter. When clients attempt to connect to this share, they are redirected to the proxied share using the SMB-Dfs protocol.
+.sp
+Only Dfs roots can act as proxy shares. Take a look at the
+msdfs root and
+host msdfs options to find out how to set up a Dfs root share.
+.sp
+\fBNo default\fR
+.sp
+Example:
+\fB\fImsdfs proxy\fR = \\\\otherserver\\someshare \fR
+.RE
+.PP
+.PP
+.RS 4
+This parameter indicates that the share is a stand\-in for another CIFS share whose location is specified by the value of the parameter\. When clients attempt to connect to this share, they are redirected to the proxied share using the SMB\-Dfs protocol\.
+.sp
+Only Dfs roots can act as proxy shares\. Take a look at the
+\fImsdfs root\fR
+and
+\fIhost msdfs\fR
+options to find out how to set up a Dfs root share\.
+.sp
+\fINo default\fR
+.sp
+Example:
+\fI\fImsdfs proxy\fR\fR\fI = \fR\fI\eotherserver\esomeshare\fR\fI \fR
+.RE
 msdfs root (S)
+.RS 3n
+.PP
+.RS 4
 If set to
 \fByes\fR, Samba treats the share as a Dfs root and allows clients to browse the distributed file system tree rooted at the share directory. Dfs links are specified in the share directory by symbolic links of the form
 \fImsdfs:serverA\\shareA,serverB\\shareB\fR
 and so on. For more information on setting up a Dfs tree on Samba, refer to the MSDFS chapter in the Samba3-HOWTO book.
 .sp
 Default:
 \fB\fImsdfs root\fR = no \fR
 .RE
+.PP
+\fByes\fR, Samba treats the share as a Dfs root and allows clients to browse the distributed file system tree rooted at the share directory\. Dfs links are specified in the share directory by symbolic links of the form
+\fImsdfs:serverA\e\eshareA,serverB\e\eshareB\fR
+and so on\. For more information on setting up a Dfs tree on Samba, refer to the MSDFS chapter in the Samba3\-HOWTO book\.
+.sp
+Default:
+\fI\fImsdfs root\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 name cache timeout (G)
+.RS 3n
+Specifies the number of seconds it takes before entries in samba's hostname resolve cache time out. If the timeout is set to 0. the caching is disabled.
+.sp
+Default:
+\fB\fIname cache timeout\fR = 660 \fR
+.sp
+Example:
+\fB\fIname cache timeout\fR = 0 \fR
+.RE
+.PP
+.PP
+.RS 4
+Specifies the number of seconds it takes before entries in samba\'s hostname resolve cache time out\. If the timeout is set to 0\. the caching is disabled\.
+.sp
+Default:
+\fI\fIname cache timeout\fR\fR\fI = \fR\fI660\fR\fI \fR
+.sp
+Example:
+\fI\fIname cache timeout\fR\fR\fI = \fR\fI0\fR\fI \fR
+.RE
 name resolve order (G)
+.RS 3n
+This option is used by the programs in the Samba suite to determine what naming services to use and in what order to resolve host names to IP addresses. Its main purpose to is to control how netbios name resolution is performed. The option takes a space separated string of name resolution options.
+.sp
+The options are: "lmhosts", "host", "wins" and "bcast". They cause names to be resolved as follows:
+.RS 3n
+.TP 3n
+\(bu
+.PP
+.RS 4
+This option is used by the programs in the Samba suite to determine what naming services to use and in what order to resolve host names to IP addresses\. Its main purpose to is to control how netbios name resolution is performed\. The option takes a space separated string of name resolution options\.
+.sp
+The options are: "lmhosts", "host", "wins" and "bcast"\. They cause names to be resolved as follows:
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fBlmhosts\fR
+: Lookup an IP address in the Samba lmhosts file. If the line in lmhosts has no name type attached to the NetBIOS name (see the manpage for lmhosts for details) then any name type matches for lookup.
+.TP 3n
+\(bu
+: Lookup an IP address in the Samba lmhosts file\. If the line in lmhosts has no name type attached to the NetBIOS name (see the manpage for lmhosts for details) then any name type matches for lookup\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fBhost\fR
 : Do a standard host name to IP address resolution, using the system
+\fI/etc/hosts \fR, NIS, or DNS lookups. This method of name resolution is operating system depended for instance on IRIX or Solaris this may be controlled by the
+\fI/etc/nsswitch.conf\fR
+file. Note that this method is used only if the NetBIOS name type being queried is the 0x20 (server) name type or 0x1c (domain controllers). The latter case is only useful for active directory domains and results in a DNS query for the SRV RR entry matching _ldap._tcp.domain.
+.TP 3n
+\(bu
+\fI/etc/hosts \fR, NIS, or DNS lookups\. This method of name resolution is operating system depended for instance on IRIX or Solaris this may be controlled by the
+\fI/etc/nsswitch\.conf\fR
+file\. Note that this method is used only if the NetBIOS name type being queried is the 0x20 (server) name type or 0x1c (domain controllers)\. The latter case is only useful for active directory domains and results in a DNS query for the SRV RR entry matching _ldap\._tcp\.domain\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fBwins\fR
 : Query a name with the IP address listed in the
+WINSSERVER parameter. If no WINS server has been specified this method will be ignored.
+.TP 3n
+\(bu
+\fIWINSSERVER\fR
+parameter\. If no WINS server has been specified this method will be ignored\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fBbcast\fR
 : Do a broadcast on each of the known local interfaces listed in the
+interfaces parameter. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet.
+.RE
+.IP "" 3n
+The example below will cause the local lmhosts file to be examined first, followed by a broadcast attempt, followed by a normal system hostname lookup.
+\fIinterfaces\fR
+parameter\. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet\.
+.sp
+.RE
+The example below will cause the local lmhosts file to be examined first, followed by a broadcast attempt, followed by a normal system hostname lookup\.
 .sp
 When Samba is functioning in ADS security mode (security = ads) it is advised to use following settings for
 …
 name resolve order = wins bcast
 .sp
 DC lookups will still be done via DNS, but fallbacks to netbios names will not inundate your DNS servers with needless querys for DOMAIN<0x1c> lookups.
 .sp
 Default:
 \fB\fIname resolve order\fR = lmhosts host wins bcast \fR
 .sp
 Example:
 \fB\fIname resolve order\fR = lmhosts bcast host \fR
 .RE
+.PP
+DC lookups will still be done via DNS, but fallbacks to netbios names will not inundate your DNS servers with needless querys for DOMAIN<0x1c> lookups\.
+.sp
+Default:
+\fI\fIname resolve order\fR\fR\fI = \fR\fIlmhosts host wins bcast\fR\fI \fR
+.sp
+Example:
+\fI\fIname resolve order\fR\fR\fI = \fR\fIlmhosts bcast host\fR\fI \fR
+.RE
 netbios aliases (G)
+.RS 3n
+This is a list of NetBIOS names that nmbd will advertise as additional names by which the Samba server is known. This allows one machine to appear in browse lists under multiple names. If a machine is acting as a browse server or logon server none of these names will be advertised as either browse server or logon servers, only the primary name of the machine will be advertised with these capabilities.
+.sp
+Default:
+\fB\fInetbios aliases\fR = # empty string (no additional names) \fR
+.sp
+Example:
+\fB\fInetbios aliases\fR = TEST TEST1 TEST2 \fR
+.RE
+.PP
+.PP
+.RS 4
+This is a list of NetBIOS names that nmbd will advertise as additional names by which the Samba server is known\. This allows one machine to appear in browse lists under multiple names\. If a machine is acting as a browse server or logon server none of these names will be advertised as either browse server or logon servers, only the primary name of the machine will be advertised with these capabilities\.
+.sp
+Default:
+\fI\fInetbios aliases\fR\fR\fI = \fR\fI # empty string (no additional names)\fR\fI \fR
+.sp
+Example:
+\fI\fInetbios aliases\fR\fR\fI = \fR\fITEST TEST1 TEST2\fR\fI \fR
+.RE
 netbios name (G)
+.RS 3n
+This sets the NetBIOS name by which a Samba server is known. By default it is the same as the first component of the host's DNS name. If a machine is a browse server or logon server this name (or the first component of the hosts DNS name) will be the name that these services are advertised under.
+.sp
+There is a bug in Samba-3 that breaks operation of browsing and access to shares if the netbios name is set to the literal name
+PIPE. To avoid this problem, do not name your Samba-3 server
+PIPE.
+.sp
+Default:
+\fB\fInetbios name\fR = # machine DNS name \fR
+.sp
+Example:
+\fB\fInetbios name\fR = MYNAME \fR
+.RE
+.PP
+.PP
+.RS 4
+This sets the NetBIOS name by which a Samba server is known\. By default it is the same as the first component of the host\'s DNS name\. If a machine is a browse server or logon server this name (or the first component of the hosts DNS name) will be the name that these services are advertised under\.
+.sp
+There is a bug in Samba\-3 that breaks operation of browsing and access to shares if the netbios name is set to the literal name
+PIPE\. To avoid this problem, do not name your Samba\-3 server
+PIPE\.
+.sp
+Default:
+\fI\fInetbios name\fR\fR\fI = \fR\fI # machine DNS name\fR\fI \fR
+.sp
+Example:
+\fI\fInetbios name\fR\fR\fI = \fR\fIMYNAME\fR\fI \fR
+.RE
 netbios scope (G)
+.RS 3n
+This sets the NetBIOS scope that Samba will operate under. This should not be set unless every machine on your LAN also sets this value.
+.sp
+Default:
+\fB\fInetbios scope\fR = \fR
+.RE
+.PP
+.PP
+.RS 4
+This sets the NetBIOS scope that Samba will operate under\. This should not be set unless every machine on your LAN also sets this value\.
+.sp
+Default:
+\fI\fInetbios scope\fR\fR\fI = \fR\fI\fR\fI \fR
+.RE
 nis homedir (G)
+.RS 3n
+Get the home share server from a NIS map. For UNIX systems that use an automounter, the user's home directory will often be mounted on a workstation on demand from a remote server.
+.sp
+When the Samba logon server is not the actual home directory server, but is mounting the home directories via NFS then two network hops would be required to access the users home directory if the logon server told the client to use itself as the SMB server for home directories (one over SMB and one over NFS). This can be very slow.
+.sp
+This option allows Samba to return the home share as being on a different server to the logon server and as long as a Samba daemon is running on the home directory server, it will be mounted on the Samba client directly from the directory server. When Samba is returning the home share to the client, it will consult the NIS map specified in
+homedir map and return the server listed there.
+.sp
+Note that for this option to work there must be a working NIS system and the Samba server with this option must also be a logon server.
+.sp
+Default:
+\fB\fInis homedir\fR = no \fR
+.RE
+.PP
+.PP
+.RS 4
+Get the home share server from a NIS map\. For UNIX systems that use an automounter, the user\'s home directory will often be mounted on a workstation on demand from a remote server\.
+.sp
+When the Samba logon server is not the actual home directory server, but is mounting the home directories via NFS then two network hops would be required to access the users home directory if the logon server told the client to use itself as the SMB server for home directories (one over SMB and one over NFS)\. This can be very slow\.
+.sp
+This option allows Samba to return the home share as being on a different server to the logon server and as long as a Samba daemon is running on the home directory server, it will be mounted on the Samba client directly from the directory server\. When Samba is returning the home share to the client, it will consult the NIS map specified in
+\fIhomedir map\fR
+and return the server listed there\.
+.sp
+Note that for this option to work there must be a working NIS system and the Samba server with this option must also be a logon server\.
+.sp
+Default:
+\fI\fInis homedir\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 nt acl support (S)
+.RS 3n
+.PP
+.RS 4
 This boolean parameter controls whether
 \fBsmbd\fR(8)
 will attempt to map UNIX permissions into Windows NT access control lists. The UNIX permissions considered are the the traditional UNIX owner and group permissions, as well as POSIX ACLs set on any files or directories. This parameter was formally a global parameter in releases prior to 2.2.2.
 .sp
 Default:
 \fB\fInt acl support\fR = yes \fR
 .RE
+.PP
+will attempt to map UNIX permissions into Windows NT access control lists\. The UNIX permissions considered are the the traditional UNIX owner and group permissions, as well as POSIX ACLs set on any files or directories\. This parameter was formally a global parameter in releases prior to 2\.2\.2\.
+.sp
+Default:
+\fI\fInt acl support\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 ntlm auth (G)
+.RS 3n
+.PP
+.RS 4
 This parameter determines whether or not
 \fBsmbd\fR(8)
 will attempt to authenticate users using the NTLM encrypted password response. If disabled, either the lanman password hash or an NTLMv2 response will need to be sent by the client.
+will attempt to authenticate users using the NTLM encrypted password response\. If disabled, either the lanman password hash or an NTLMv2 response will need to be sent by the client\.
 .sp
 If this option, and
 lanman auth
 are both disabled, then only NTLMv2 logins will be permited. Not all clients support NTLMv2, and most will require special configuration to us it.
 .sp
 Default:
 \fB\fIntlm auth\fR = yes \fR
 .RE
+.PP
+are both disabled, then only NTLMv2 logins will be permited\. Not all clients support NTLMv2, and most will require special configuration to us it\.
+.sp
+Default:
+\fI\fIntlm auth\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 nt pipe support (G)
+.RS 3n
+.PP
+.RS 4
 This boolean parameter controls whether
 \fBsmbd\fR(8)
 will allow Windows NT clients to connect to the NT SMB specific
 \fBIPC$\fR
 pipes. This is a developer debugging option and can be left alone.
 .sp
 Default:
 \fB\fInt pipe support\fR = yes \fR
 .RE
+.PP
+pipes\. This is a developer debugging option and can be left alone\.
+.sp
+Default:
+\fI\fInt pipe support\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 nt status support (G)
+.RS 3n
+.PP
+.RS 4
 This boolean parameter controls whether
 \fBsmbd\fR(8)
 will negotiate NT specific status support with Windows NT/2k/XP clients. This is a developer debugging option and should be left alone. If this option is set to
+will negotiate NT specific status support with Windows NT/2k/XP clients\. This is a developer debugging option and should be left alone\. If this option is set to
 \fBno\fR
 then Samba offers exactly the same DOS error codes that versions prior to Samba 2.2.3 reported.
 .sp
 You should not need to ever disable this parameter.
 .sp
 Default:
 \fB\fInt status support\fR = yes \fR
 .RE
+.PP
+then Samba offers exactly the same DOS error codes that versions prior to Samba 2\.2\.3 reported\.
+.sp
+You should not need to ever disable this parameter\.
+.sp
+Default:
+\fI\fInt status support\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 null passwords (G)
+.RS 3n
+Allow or disallow client access to accounts that have null passwords.
+.PP
+.RS 4
+Allow or disallow client access to accounts that have null passwords\.
 .sp
 See also
 \fBsmbpasswd\fR(5).
 .sp
 Default:
 \fB\fInull passwords\fR = no \fR
 .RE
+.PP
+\fBsmbpasswd\fR(5)\.
+.sp
+Default:
+\fI\fInull passwords\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 obey pam restrictions (G)
+.RS 3n
+When Samba 3.0 is configured to enable PAM support (i.e. --with-pam), this parameter will control whether or not Samba should obey PAM's account and session management directives. The default behavior is to use PAM for clear text authentication only and to ignore any account or session management. Note that Samba always ignores PAM for authentication in the case of
+encrypt passwords = yes. The reason is that PAM modules cannot support the challenge/response authentication mechanism needed in the presence of SMB password encryption.
+.sp
+Default:
+\fB\fIobey pam restrictions\fR = no \fR
+.RE
+.PP
+.PP
+.RS 4
+When Samba 3\.0 is configured to enable PAM support (i\.e\. \-\-with\-pam), this parameter will control whether or not Samba should obey PAM\'s account and session management directives\. The default behavior is to use PAM for clear text authentication only and to ignore any account or session management\. Note that Samba always ignores PAM for authentication in the case of
+\fIencrypt passwords = yes\fR\. The reason is that PAM modules cannot support the challenge/response authentication mechanism needed in the presence of SMB password encryption\.
+.sp
+Default:
+\fI\fIobey pam restrictions\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 only user (S)
+.RS 3n
+.PP
+.RS 4
 This is a boolean option that controls whether connections with usernames not in the
 \fIuser\fR
 list will be allowed. By default this option is disabled so that a client can supply a username to be used by the server. Enabling this parameter will force the server to only use the login names from the
+list will be allowed\. By default this option is disabled so that a client can supply a username to be used by the server\. Enabling this parameter will force the server to only use the login names from the
 \fIuser\fR
 list and is only really useful in
+security = share level security.
+.sp
+Note that this also means Samba won't try to deduce usernames from the service name. This can be annoying for the [homes] section. To get around this you could use
+\fIsecurity = share\fR
+level security\.
+.sp
+Note that this also means Samba won\'t try to deduce usernames from the service name\. This can be annoying for the [homes] section\. To get around this you could use
 user = %S
 which means your
 \fIuser\fR
 list will be just the service name, which for home directories is the name of the user.
 .sp
 Default:
 \fB\fIonly user\fR = no \fR
 .RE
+.PP
+list will be just the service name, which for home directories is the name of the user\.
+.sp
+Default:
+\fI\fIonly user\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 open files database hash size (G)
+.RS 3n
+This parameter was added in Samba 3.0.23. This is an internal tuning parameter that sets the hash size of the tdb used for the open file databases. The presence of this parameter allows tuning of the system for very large (thousands of concurrent users) Samba setups. The default setting of this parameter should be sufficient for most normal environments. It is advised not to change this parameter unless advised to by a Samba Team member.
+.sp
+Default:
+\fB\fIopen files database hash size\fR = 10007 \fR
+.sp
+Example:
+\fB\fIopen files database hash size\fR = 1338457 \fR
+.RE
+.PP
+.PP
+.RS 4
+This parameter was added in Samba 3\.0\.23\. This is an internal tuning parameter that sets the hash size of the tdb used for the open file databases\. The presence of this parameter allows tuning of the system for very large (thousands of concurrent users) Samba setups\. The default setting of this parameter should be sufficient for most normal environments\. It is advised not to change this parameter unless advised to by a Samba Team member\.
+.sp
+Default:
+\fI\fIopen files database hash size\fR\fR\fI = \fR\fI10007\fR\fI \fR
+.sp
+Example:
+\fI\fIopen files database hash size\fR\fR\fI = \fR\fI1338457\fR\fI \fR
+.RE
 oplock break wait time (G)
+.RS 3n
+This is a tuning parameter added due to bugs in both Windows 9x and WinNT. If Samba responds to a client too quickly when that client issues an SMB that can cause an oplock break request, then the network client can fail and not respond to the break request. This tuning parameter (which is set in milliseconds) is the amount of time Samba will wait before sending an oplock break request to such (broken) clients.
+.PP
+.RS 4
+This is a tuning parameter added due to bugs in both Windows 9x and WinNT\. If Samba responds to a client too quickly when that client issues an SMB that can cause an oplock break request, then the network client can fail and not respond to the break request\. This tuning parameter (which is set in milliseconds) is the amount of time Samba will wait before sending an oplock break request to such (broken) clients\.
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBWarning\fR
+DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE.
+Default:
+\fB\fIoplock break wait time\fR = 0 \fR
+.RE
+.PP
+Warning
+DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE\.
+Default:
+\fI\fIoplock break wait time\fR\fR\fI = \fR\fI0\fR\fI \fR
+.RE
 oplock contention limit (S)
+.RS 3n
+.PP
+.RS 4
 This is a
 \fBvery\fR
+\fIvery\fR
 advanced
 \fBsmbd\fR(8)
 tuning option to improve the efficiency of the granting of oplocks under multiple client contention for the same file.
+tuning option to improve the efficiency of the granting of oplocks under multiple client contention for the same file\.
 .sp
 In brief it specifies a number, which causes
 \fBsmbd\fR(8)not to grant an oplock even when requested if the approximate number of clients contending for an oplock on the same file goes over this limit. This causes
+\fBsmbd\fR(8)not to grant an oplock even when requested if the approximate number of clients contending for an oplock on the same file goes over this limit\. This causes
 smbd
 to behave in a similar way to Windows NT.
+to behave in a similar way to Windows NT\.
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBWarning\fR
+DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE.
+Default:
+\fB\fIoplock contention limit\fR = 2 \fR
+.RE
+.PP
+Warning
+DO NOT CHANGE THIS PARAMETER UNLESS YOU HAVE READ AND UNDERSTOOD THE SAMBA OPLOCK CODE\.
+Default:
+\fI\fIoplock contention limit\fR\fR\fI = \fR\fI2\fR\fI \fR
+.RE
 oplocks (S)
+.RS 3n
+.PP
+.RS 4
 This boolean option tells
 smbd
 whether to issue oplocks (opportunistic locks) to file open requests on this share. The oplock code can dramatically (approx. 30% or more) improve the speed of access to files on Samba servers. It allows the clients to aggressively cache files locally and you may want to disable this option for unreliable network environments (it is turned on by default in Windows NT Servers). For more information see the file
 \fISpeed.txt\fR
+whether to issue oplocks (opportunistic locks) to file open requests on this share\. The oplock code can dramatically (approx\. 30% or more) improve the speed of access to files on Samba servers\. It allows the clients to aggressively cache files locally and you may want to disable this option for unreliable network environments (it is turned on by default in Windows NT Servers)\. For more information see the file
+\fISpeed\.txt\fR
 in the Samba
 \fIdocs/\fR
+directory.
+.sp
+Oplocks may be selectively turned off on certain files with a share. See the
+veto oplock files parameter. On some systems oplocks are recognized by the underlying operating system. This allows data synchronization between all access to oplocked files, whether it be via Samba or NFS or a local UNIX process. See the
+kernel oplocks parameter for details.
+.sp
+Default:
+\fB\fIoplocks\fR = yes \fR
+.RE
+.PP
+directory\.
+.sp
+Oplocks may be selectively turned off on certain files with a share\. See the
+\fIveto oplock files\fR
+parameter\. On some systems oplocks are recognized by the underlying operating system\. This allows data synchronization between all access to oplocked files, whether it be via Samba or NFS or a local UNIX process\. See the
+\fIkernel oplocks\fR
+parameter for details\.
+.sp
+Default:
+\fI\fIoplocks\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 os2 driver map (G)
+.RS 3n
+The parameter is used to define the absolute path to a file containing a mapping of Windows NT printer driver names to OS/2 printer driver names. The format is:
+.sp
+<nt driver name> = <os2 driver name>.<device name>
+.PP
+.RS 4
+The parameter is used to define the absolute path to a file containing a mapping of Windows NT printer driver names to OS/2 printer driver names\. The format is:
+.sp
+<nt driver name> = <os2 driver name>\.<device name>
 .sp
 For example, a valid entry using the HP LaserJet 5 printer driver would appear as
 HP LaserJet 5L = LASERJET.HP LaserJet 5L.
 .sp
 The need for the file is due to the printer driver namespace problem described in the chapter on Classical Printing in the Samba3-HOWTO book. For more details on OS/2 clients, please refer to chapter on other clients in the Samba3-HOWTO book.
 .sp
 Default:
 \fB\fIos2 driver map\fR = \fR
 .RE
+.PP
+HP LaserJet 5L = LASERJET\.HP LaserJet 5L\.
+.sp
+The need for the file is due to the printer driver namespace problem described in the chapter on Classical Printing in the Samba3\-HOWTO book\. For more details on OS/2 clients, please refer to chapter on other clients in the Samba3\-HOWTO book\.
+.sp
+Default:
+\fI\fIos2 driver map\fR\fR\fI = \fR\fI\fR\fI \fR
+.RE
 os level (G)
+.RS 3n
+This integer value controls what level Samba advertises itself as for browse elections. The value of this parameter determines whether
+.PP
+.RS 4
+This integer value controls what level Samba advertises itself as for browse elections\. The value of this parameter determines whether
 \fBnmbd\fR(8)
 has a chance of becoming a local master browser for the
+workgroup in the local broadcast area.
+.sp
+\fB Note :\fRBy default, Samba will win a local master browsing election over all Microsoft operating systems except a Windows NT 4.0/2000 Domain Controller. This means that a misconfigured Samba host can effectively isolate a subnet for browsing purposes. This parameter is largely auto-configured in the Samba-3 release series and it is seldom necessary to manually over-ride the default setting. Please refer to chapter 9 of the Samba-3 HOWTO document for further information regarding the use of this parameter.
+.sp
+Default:
+\fB\fIos level\fR = 20 \fR
+.sp
+Example:
+\fB\fIos level\fR = 65 \fR
+.RE
+.PP
+\fIworkgroup\fR
+in the local broadcast area\.
+.sp
+\fI Note:\fR
+By default, Samba will win a local master browsing election over all Microsoft operating systems except a Windows NT 4\.0/2000 Domain Controller\. This means that a misconfigured Samba host can effectively isolate a subnet for browsing purposes\. This parameter is largely auto\-configured in the Samba\-3 release series and it is seldom necessary to manually override the default setting\. Please refer to chapter 9 of the Samba\-3 HOWTO document for further information regarding the use of this parameter\.
+\fINote:\fR
+The maximum value for this parameter is 255\. If you use higher values, counting will start at 0!
+.sp
+Default:
+\fI\fIos level\fR\fR\fI = \fR\fI20\fR\fI \fR
+.sp
+Example:
+\fI\fIos level\fR\fR\fI = \fR\fI65\fR\fI \fR
+.RE
 pam password change (G)
+.RS 3n
+With the addition of better PAM support in Samba 2.2, this parameter, it is possible to use PAM's password change control flag for Samba. If enabled, then PAM will be used for password changes when requested by an SMB client instead of the program listed in
+passwd program. It should be possible to enable this without changing your
+passwd chat parameter for most setups.
+.sp
+Default:
+\fB\fIpam password change\fR = no \fR
+.RE
+.PP
+.PP
+.RS 4
+With the addition of better PAM support in Samba 2\.2, this parameter, it is possible to use PAM\'s password change control flag for Samba\. If enabled, then PAM will be used for password changes when requested by an SMB client instead of the program listed in
+\fIpasswd program\fR\. It should be possible to enable this without changing your
+\fIpasswd chat\fR
+parameter for most setups\.
+.sp
+Default:
+\fI\fIpam password change\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 panic action (G)
+.RS 3n
+.PP
+.RS 4
 This is a Samba developer option that allows a system command to be called when either
 \fBsmbd\fR(8)
 or
 \fBsmbd\fR(8)
 crashes. This is usually used to draw attention to the fact that a problem occurred.
 .sp
 Default:
 \fB\fIpanic action\fR = \fR
 .sp
 Example:
 \fB\fIpanic action\fR = "/bin/sleep 90000" \fR
 .RE
+.PP
+\fBnmbd\fR(8)
+crashes\. This is usually used to draw attention to the fact that a problem occurred\.
+.sp
+Default:
+\fI\fIpanic action\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fIpanic action\fR\fR\fI = \fR\fI"/bin/sleep 90000"\fR\fI \fR
+.RE
 paranoid server security (G)
+.RS 3n
+Some version of NT 4.x allow non-guest users with a bad passowrd. When this option is enabled, samba will not use a broken NT 4.x server as password server, but instead complain to the logs and exit.
+.sp
+Disabling this option prevents Samba from making this check, which involves deliberatly attempting a bad logon to the remote server.
+.sp
+Default:
+\fB\fIparanoid server security\fR = yes \fR
+.RE
+.PP
+.PP
+.RS 4
+Some version of NT 4\.x allow non\-guest users with a bad passowrd\. When this option is enabled, samba will not use a broken NT 4\.x server as password server, but instead complain to the logs and exit\.
+.sp
+Disabling this option prevents Samba from making this check, which involves deliberatly attempting a bad logon to the remote server\.
+.sp
+Default:
+\fI\fIparanoid server security\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 passdb backend (G)
+.RS 3n
+This option allows the administrator to chose which backend will be used for storing user and possibly group information. This allows you to swap between dfferent storage mechanisms without recompile.
+.sp
+The parameter value is divided into two parts, the backend's name, and a 'location' string that has meaning only to that particular backed. These are separated by a : character.
+.PP
+.RS 4
+This option allows the administrator to chose which backend will be used for storing user and possibly group information\. This allows you to swap between different storage mechanisms without recompile\.
+.sp
+The parameter value is divided into two parts, the backend\'s name, and a \'location\' string that has meaning only to that particular backed\. These are separated by a : character\.
 .sp
 Available backends can include:
+.RS 3n
+.TP 3n
+\(bu
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 smbpasswd
+- The default smbpasswd backend. Takes a path to the smbpasswd file as an optional argument.
+.TP 3n
+\(bu
+\- The default smbpasswd backend\. Takes a path to the smbpasswd file as an optional argument\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 tdbsam
+- The TDB based password storage backend. Takes a path to the TDB as an optional argument (defaults to passdb.tdb in the
+private dir directory.
+.TP 3n
+\(bu
+\- The TDB based password storage backend\. Takes a path to the TDB as an optional argument (defaults to passdb\.tdb in the
+\fIprivate dir\fR
+directory\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 ldapsam
 - The LDAP based passdb backend. Takes an LDAP URL as an optional argument (defaults to
+\- The LDAP based passdb backend\. Takes an LDAP URL as an optional argument (defaults to
 ldap://localhost)
 .sp
 LDAP connections should be secured where possible. This may be done using either Start-TLS (see
 ldap ssl) or by specifying
+LDAP connections should be secured where possible\. This may be done using either Start\-TLS (see
+\fIldap ssl\fR) or by specifying
 \fIldaps://\fR
+in the URL argument.
+.sp
+Multiple servers may also be specified in double-quotes, if your LDAP libraries supports the LDAP URL notation. (OpenLDAP does).
+.RE
+.IP "" 3n
+in the URL argument\.
+.sp
+Multiple servers may also be specified in double\-quotes\. Whether multiple servers are supported or not and the exact syntax depends on the LDAP library you use\.
+.sp
+.RE
         Examples of use are:
+.sp
+.RS 4
 .nf
+passdb backend = tdbsam:/etc/samba/private/passdb.tdb
+or
+passdb backend = ldapsam:"ldap://ldap-1.example.com ldap://ldap-2.example.com"
+passdb backend = tdbsam:/etc/samba/private/passdb\.tdb
+or multi server LDAP URL with OpenLDAP library:
+passdb backend = ldapsam:"ldap://ldap\-1\.example\.com ldap://ldap\-2\.example\.com"
+or multi server LDAP URL with Netscape based LDAP library:
+passdb backend = ldapsam:"ldap://ldap\-1\.example\.com ldap\-2\.example\.com"
 .fi
+Default:
+\fB\fIpassdb backend\fR = smbpasswd \fR
+.RE
+.PP
+.RE
+Default:
+\fI\fIpassdb backend\fR\fR\fI = \fR\fIsmbpasswd\fR\fI \fR
+.RE
 passdb expand explicit (G)
+.RS 3n
+This parameter controls whether Samba substitutes %-macros in the passdb fields if they are explicitly set. We used to expand macros here, but this turned out to be a bug because the Windows client can expand a variable %G_osver% in which %G would have been substituted by the user's primary group.
+.sp
+Default:
+\fB\fIpassdb expand explicit\fR = no \fR
+.RE
+.PP
+passwd chat (G)
+.RS 3n
+This string controls the
+\fB"chat"\fR
+conversation that takes places between
+\fBsmbd\fR(8)
+and the local password changing program to change the user's password. The string describes a sequence of response-receive pairs that
+\fBsmbd\fR(8)
+uses to determine what to send to the
+passwd program and what to expect back. If the expected output is not received then the password is not changed.
+.sp
+This chat sequence is often quite site specific, depending on what local methods are used for password control (such as NIS etc).
+.sp
+Note that this parameter only is only used if the
+unix password sync parameter is set to
+\fByes\fR. This sequence is then called
+\fBAS ROOT\fR
+when the SMB password in the smbpasswd file is being changed, without access to the old password cleartext. This means that root must be able to reset the user's password without knowing the text of the previous password. In the presence of NIS/YP, this means that the
+passwd program must be executed on the NIS master.
+.sp
+The string can contain the macro
+\fI%n\fR
+which is substituted for the new password. The chat sequence can also contain the standard macros \n, \r, \t and \s to give line-feed, carriage-return, tab and space. The chat sequence string can also contain a '*' which matches any sequence of characters. Double quotes can be used to collect strings with spaces in them into a single string.
+.sp
+If the send string in any part of the chat sequence is a full stop ".", then no string is sent. Similarly, if the expect string is a full stop then no string is expected.
+.sp
+If the
+pam password change parameter is set to
+\fByes\fR, the chat pairs may be matched in any order, and success is determined by the PAM result, not any particular output. The \n macro is ignored for PAM conversions.
+.sp
+Default:
+\fB\fIpasswd chat\fR = *new*password* %n\\n*new*password* %n\\n *changed* \fR
+.sp
+Example:
+\fB\fIpasswd chat\fR = "*Enter OLD password*" %o\\n "*Enter NEW password*" %n\\n "*Reenter NEW password*" %n\\n "*Password changed*" \fR
+.RE
+.PP
+.PP
+.RS 4
+This parameter controls whether Samba substitutes %\-macros in the passdb fields if they are explicitly set\. We used to expand macros here, but this turned out to be a bug because the Windows client can expand a variable %G_osver% in which %G would have been substituted by the user\'s primary group\.
+.sp
+Default:
+\fI\fIpassdb expand explicit\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 passwd chat debug (G)
+.RS 3n
+.PP
+.RS 4
 This boolean specifies if the passwd chat script parameter is run in
 \fBdebug\fR
 mode. In this mode the strings passed to and received from the passwd chat are printed in the
+\fIdebug\fR
+mode\. In this mode the strings passed to and received from the passwd chat are printed in the
 \fBsmbd\fR(8)
 log with a
+debug level of 100. This is a dangerous option as it will allow plaintext passwords to be seen in the
+\fIdebug level\fR
+of 100\. This is a dangerous option as it will allow plaintext passwords to be seen in the
 smbd
 log. It is available to help Samba admins debug their
+log\. It is available to help Samba admins debug their
 \fIpasswd chat\fR
 scripts when calling the
 \fIpasswd program\fR
+and should be turned off after this has been done. This option has no effect if the
+pam password change paramter is set. This parameter is off by default.
+.sp
+Default:
+\fB\fIpasswd chat debug\fR = no \fR
+.RE
+.PP
+and should be turned off after this has been done\. This option has no effect if the
+\fIpam password change\fR
+parameter is set\. This parameter is off by default\.
+.sp
+Default:
+\fI\fIpasswd chat debug\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 passwd chat timeout (G)
+.RS 3n
+This integer specifies the number of seconds smbd will wait for an initial answer from a passwd chat script being run. Once the initial answer is received the subsequent answers must be received in one tenth of this time. The default it two seconds.
+.sp
+Default:
+\fB\fIpasswd chat timeout\fR = 2 \fR
+.RE
+.PP
+.PP
+.RS 4
+This integer specifies the number of seconds smbd will wait for an initial answer from a passwd chat script being run\. Once the initial answer is received the subsequent answers must be received in one tenth of this time\. The default it two seconds\.
+.sp
+Default:
+\fI\fIpasswd chat timeout\fR\fR\fI = \fR\fI2\fR\fI \fR
+.RE
+passwd chat (G)
+.PP
+.RS 4
+This string controls the
+\fI"chat"\fR
+conversation that takes places between
+\fBsmbd\fR(8)
+and the local password changing program to change the user\'s password\. The string describes a sequence of response\-receive pairs that
+\fBsmbd\fR(8)
+uses to determine what to send to the
+\fIpasswd program\fR
+and what to expect back\. If the expected output is not received then the password is not changed\.
+.sp
+This chat sequence is often quite site specific, depending on what local methods are used for password control (such as NIS etc)\.
+.sp
+Note that this parameter only is only used if the
+\fIunix password sync\fR
+parameter is set to
+\fByes\fR\. This sequence is then called
+\fIAS ROOT\fR
+when the SMB password in the smbpasswd file is being changed, without access to the old password cleartext\. This means that root must be able to reset the user\'s password without knowing the text of the previous password\. In the presence of NIS/YP, this means that the
+\fIpasswd program\fR
+must be executed on the NIS master\.
+.sp
+The string can contain the macro
+\fI%n\fR
+which is substituted for the new password\. The old passsword (\fI%o\fR) is only available when
+\fIencrypt passwords\fR
+has been disabled\. The chat sequence can also contain the standard macros \en, \er, \et and \es to give line\-feed, carriage\-return, tab and space\. The chat sequence string can also contain a \'*\' which matches any sequence of characters\. Double quotes can be used to collect strings with spaces in them into a single string\.
+.sp
+If the send string in any part of the chat sequence is a full stop "\.", then no string is sent\. Similarly, if the expect string is a full stop then no string is expected\.
+.sp
+If the
+\fIpam password change\fR
+parameter is set to
+\fByes\fR, the chat pairs may be matched in any order, and success is determined by the PAM result, not any particular output\. The \en macro is ignored for PAM conversions\.
+.sp
+Default:
+\fI\fIpasswd chat\fR\fR\fI = \fR\fI*new*password* %n\en*new*password* %n\en *changed*\fR\fI \fR
+.sp
+Example:
+\fI\fIpasswd chat\fR\fR\fI = \fR\fI"*Enter NEW password*" %n\en "*Reenter NEW password*" %n\en "*Password changed*"\fR\fI \fR
+.RE
 passwd program (G)
+.RS 3n
+The name of a program that can be used to set UNIX user passwords. Any occurrences of
+.PP
+.RS 4
+The name of a program that can be used to set UNIX user passwords\. Any occurrences of
 \fI%u\fR
 will be replaced with the user name. The user name is checked for existence before calling the password changing program.
+will be replaced with the user name\. The user name is checked for existence before calling the password changing program\.
 .sp
 Also note that many passwd programs insist in
 \fBreasonable \fR
 passwords, such as a minimum length, or the inclusion of mixed case chars and digits. This can pose a problem as some clients (such as Windows for Workgroups) uppercase the password before sending it.
 .sp
 \fBNote\fR
+\fIreasonable \fR
+passwords, such as a minimum length, or the inclusion of mixed case chars and digits\. This can pose a problem as some clients (such as Windows for Workgroups) uppercase the password before sending it\.
+.sp
+\fINote\fR
 that if the
 \fIunix password sync\fR
 …
 \fByes \fR
 then this program is called
 \fBAS ROOT\fR
 before the SMB password in the smbpasswd file is changed. If this UNIX password change fails, then
+\fIAS ROOT\fR
+before the SMB password in the smbpasswd file is changed\. If this UNIX password change fails, then
 smbd
 will fail to change the SMB password also (this is by design).
+will fail to change the SMB password also (this is by design)\.
 .sp
 If the
 \fIunix password sync\fR
 parameter is set this parameter
 \fBMUST USE ABSOLUTE PATHS\fR
+\fIMUST USE ABSOLUTE PATHS\fR
 for
 \fBALL\fR
 programs called, and must be examined for security implications. Note that by default
+\fIALL\fR
+programs called, and must be examined for security implications\. Note that by default
 \fIunix password sync\fR
 is set to
 \fBno\fR.
 .sp
 Default:
 \fB\fIpasswd program\fR = \fR
 .sp
 Example:
 \fB\fIpasswd program\fR = /bin/passwd %u \fR
 .RE
+.PP
+\fBno\fR\.
+.sp
+Default:
+\fI\fIpasswd program\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fIpasswd program\fR\fR\fI = \fR\fI/bin/passwd %u\fR\fI \fR
+.RE
 password level (G)
+.RS 3n
+Some client/server combinations have difficulty with mixed-case passwords. One offending client is Windows for Workgroups, which for some reason forces passwords to upper case when using the LANMAN1 protocol, but leaves them alone when using COREPLUS! Another problem child is the Windows 95/98 family of operating systems. These clients upper case clear text passwords even when NT LM 0.12 selected by the protocol negotiation request/response.
+.sp
+This parameter defines the maximum number of characters that may be upper case in passwords.
+.sp
+For example, say the password given was "FRED". If
+.PP
+.RS 4
+Some client/server combinations have difficulty with mixed\-case passwords\. One offending client is Windows for Workgroups, which for some reason forces passwords to upper case when using the LANMAN1 protocol, but leaves them alone when using COREPLUS! Another problem child is the Windows 95/98 family of operating systems\. These clients upper case clear text passwords even when NT LM 0\.12 selected by the protocol negotiation request/response\.
+.sp
+This parameter defines the maximum number of characters that may be upper case in passwords\.
+.sp
+For example, say the password given was "FRED"\. If
 \fI password level\fR
 is set to 1, the following combinations would be tried if "FRED" failed:
 …
 was set to 2, the following combinations would also be tried:
 .sp
 "FRed", "FrEd", "FreD", "fREd", "fReD", "frED", ..
 .sp
 And so on.
 .sp
 The higher value this parameter is set to the more likely it is that a mixed case password will be matched against a single case password. However, you should be aware that use of this parameter reduces security and increases the time taken to process a new connection.
 .sp
 A value of zero will cause only two attempts to be made - the password as is and the password in all-lower case.
 .sp
 This parameter is used only when using plain-text passwords. It is not at all used when encrypted passwords as in use (that is the default since samba-3.0.0). Use this only when
 encrypt passwords = No.
 .sp
 Default:
 \fB\fIpassword level\fR = 0 \fR
 .sp
 Example:
 \fB\fIpassword level\fR = 4 \fR
 .RE
+.PP
+"FRed", "FrEd", "FreD", "fREd", "fReD", "frED", \.\.
+.sp
+And so on\.
+.sp
+The higher value this parameter is set to the more likely it is that a mixed case password will be matched against a single case password\. However, you should be aware that use of this parameter reduces security and increases the time taken to process a new connection\.
+.sp
+A value of zero will cause only two attempts to be made \- the password as is and the password in all\-lower case\.
+.sp
+This parameter is used only when using plain\-text passwords\. It is not at all used when encrypted passwords as in use (that is the default since samba\-3\.0\.0)\. Use this only when
+\fIencrypt passwords = No\fR\.
+.sp
+Default:
+\fI\fIpassword level\fR\fR\fI = \fR\fI0\fR\fI \fR
+.sp
+Example:
+\fI\fIpassword level\fR\fR\fI = \fR\fI4\fR\fI \fR
+.RE
 password server (G)
+.RS 3n
+.PP
+.RS 4
 By specifying the name of another SMB server or Active Directory domain controller with this option, and using
 security = [ads|domain|server]
 it is possible to get Samba to to do all its username/password validation using a specific remote server.
 .sp
 This option sets the name or IP address of the password server to use. New syntax has been added to support defining the port to use when connecting to the server the case of an ADS realm. To define a port other than the default LDAP port of 389, add the port number using a colon after the name or IP address (e.g. 192.168.1.100:389). If you do not specify a port, Samba will use the standard LDAP port of tcp/389. Note that port numbers have no effect on password servers for Windows NT 4.0 domains or netbios connections.
+it is possible to get Samba to to do all its username/password validation using a specific remote server\.
+.sp
+This option sets the name or IP address of the password server to use\. New syntax has been added to support defining the port to use when connecting to the server the case of an ADS realm\. To define a port other than the default LDAP port of 389, add the port number using a colon after the name or IP address (e\.g\. 192\.168\.1\.100:389)\. If you do not specify a port, Samba will use the standard LDAP port of tcp/389\. Note that port numbers have no effect on password servers for Windows NT 4\.0 domains or netbios connections\.
 .sp
 If parameter is a name, it is looked up using the parameter
+name resolve order and so may resolved by any method and order described in that parameter.
+.sp
+The password server must be a machine capable of using the "LM1.2X002" or the "NT LM 0.12" protocol, and it must be in user level security mode.
+\fIname resolve order\fR
+and so may resolved by any method and order described in that parameter\.
+.sp
+The password server must be a machine capable of using the "LM1\.2X002" or the "NT LM 0\.12" protocol, and it must be in user level security mode\.
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBNote\fR
+Using a password server means your UNIX box (running Samba) is only as secure as your password server.
+\fBDO NOT CHOOSE A PASSWORD SERVER THAT YOU DON'T COMPLETELY TRUST\fR.
+Never point a Samba server at itself for password serving. This will cause a loop and could lock up your Samba server!
+Note
+Using a password server means your UNIX box (running Samba) is only as secure as your password server\.
+\fIDO NOT CHOOSE A PASSWORD SERVER THAT YOU DON\'T COMPLETELY TRUST\fR\.
+Never point a Samba server at itself for password serving\. This will cause a loop and could lock up your Samba server!
 .sp
 The name of the password server takes the standard substitutions, but probably the only useful one is
 \fI%m \fR, which means the Samba server will use the incoming client as the password server. If you use this then you better trust your clients, and you had better restrict them with hosts allow!
+\fI%m \fR, which means the Samba server will use the incoming client as the password server\. If you use this then you better trust your clients, and you had better restrict them with hosts allow!
 .sp
 If the
 …
 \fBdomain\fR
 or
 \fBads\fR, then the list of machines in this option must be a list of Primary or Backup Domain controllers for the Domain or the character '*', as the Samba server is effectively in that domain, and will use cryptographically authenticated RPC calls to authenticate the user logging on. The advantage of using
+\fBads\fR, then the list of machines in this option must be a list of Primary or Backup Domain controllers for the Domain or the character \'*\', as the Samba server is effectively in that domain, and will use cryptographically authenticated RPC calls to authenticate the user logging on\. The advantage of using
 security = domain
 is that if you list several hosts in the
 …
 option then
 smbd
 will try each in turn till it finds one that responds. This is useful in case your primary server goes down.
+will try each in turn till it finds one that responds\. This is useful in case your primary server goes down\.
 .sp
 If the
 \fIpassword server\fR
 option is set to the character '*', then Samba will attempt to auto-locate the Primary or Backup Domain controllers to authenticate against by doing a query for the name
+option is set to the character \'*\', then Samba will attempt to auto\-locate the Primary or Backup Domain controllers to authenticate against by doing a query for the name
 \fBWORKGROUP<1C>\fR
 and then contacting each server returned in the list of IP addresses from the name resolution source.
 .sp
 If the list of servers contains both names/IP's and the '*' character, the list is treated as a list of preferred domain controllers, but an auto lookup of all remaining DC's will be added to the list as well. Samba will not attempt to optimize this list by locating the closest DC.
+and then contacting each server returned in the list of IP addresses from the name resolution source\.
+.sp
+If the list of servers contains both names/IP\'s and the \'*\' character, the list is treated as a list of preferred domain controllers, but an auto lookup of all remaining DC\'s will be added to the list as well\. Samba will not attempt to optimize this list by locating the closest DC\.
 .sp
 If the
 …
 \fBserver\fR, then there are different restrictions that
 security = domain
+doesn't suffer from:
+.RS 3n
+.TP 3n
+\(bu
+doesn\'t suffer from:
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 You may list several password servers in the
 \fIpassword server\fR
 …
 smbd
 makes a connection to a password server, and then the password server fails, no more users will be able to be authenticated from this
 smbd. This is a restriction of the SMB/CIFS protocol when in
+smbd\. This is a restriction of the SMB/CIFS protocol when in
 security = server
+mode and cannot be fixed in Samba.
+.TP 3n
+\(bu
+mode and cannot be fixed in Samba\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 If you are using a Windows NT server as your password server then you will have to ensure that your users are able to login from the Samba server, as when in
 security = server
 mode the network logon will appear to come from there rather than from the users workstation.
 .RE
 .IP "" 3n
 Default:
 \fB\fIpassword server\fR = \fR
 .sp
 Example:
 \fB\fIpassword server\fR = NT-PDC, NT-BDC1, NT-BDC2, * \fR
 .sp
 Example:
 \fB\fIpassword server\fR = windc.mydomain.com:389 192.168.1.101 * \fR
 .sp
 Example:
 \fB\fIpassword server\fR = * \fR
 .RE
 .PP
+directory
+.RS 3n
 This parameter is a synonym for path.
 .RE
+.PP
+mode the network logon will appear to come from there rather than from the users workstation\.
+.sp
+.RE
+Default:
+\fI\fIpassword server\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fIpassword server\fR\fR\fI = \fR\fINT\-PDC, NT\-BDC1, NT\-BDC2, *\fR\fI \fR
+.sp
+Example:
+\fI\fIpassword server\fR\fR\fI = \fR\fIwindc\.mydomain\.com:389 192\.168\.1\.101 *\fR\fI \fR
+.sp
+Example:
+\fI\fIpassword server\fR\fR\fI = \fR\fI*\fR\fI \fR
+.RE
+directory.PP
+.RS 4
+This parameter is a synonym for
+path\.
+.RE
 path (S)
+.RS 3n
+This parameter specifies a directory to which the user of the service is to be given access. In the case of printable services, this is where print data will spool prior to being submitted to the host for printing.
+.sp
+For a printable service offering guest access, the service should be readonly and the path should be world-writeable and have the sticky bit set. This is not mandatory of course, but you probably won't get the results you expect if you do otherwise.
+.PP
+.RS 4
+This parameter specifies a directory to which the user of the service is to be given access\. In the case of printable services, this is where print data will spool prior to being submitted to the host for printing\.
+.sp
+For a printable service offering guest access, the service should be readonly and the path should be world\-writeable and have the sticky bit set\. This is not mandatory of course, but you probably won\'t get the results you expect if you do otherwise\.
 .sp
 Any occurrences of
 \fI%u\fR
 in the path will be replaced with the UNIX username that the client is using on this connection. Any occurrences of
+in the path will be replaced with the UNIX username that the client is using on this connection\. Any occurrences of
 \fI%m\fR
 will be replaced by the NetBIOS name of the machine they are connecting from. These replacements are very useful for setting up pseudo home directories for users.
+will be replaced by the NetBIOS name of the machine they are connecting from\. These replacements are very useful for setting up pseudo home directories for users\.
 .sp
 Note that this path will be based on
+root dir if one was specified.
+.sp
+Default:
+\fB\fIpath\fR = \fR
+.sp
+Example:
+\fB\fIpath\fR = /home/fred \fR
+.RE
+.PP
+\fIroot dir\fR
+if one was specified\.
+.sp
+Default:
+\fI\fIpath\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fIpath\fR\fR\fI = \fR\fI/home/fred\fR\fI \fR
+.RE
 pid directory (G)
+.RS 3n
+This option specifies the directory where pid files will be placed.
+.sp
+Default:
+\fB\fIpid directory\fR = ${prefix}/var/locks \fR
+.sp
+Example:
+\fB\fIpid directory\fR = pid directory = /var/run/ \fR
+.RE
+.PP
+.PP
+.RS 4
+This option specifies the directory where pid files will be placed\.
+.sp
+Default:
+\fI\fIpid directory\fR\fR\fI = \fR\fI${prefix}/var/locks\fR\fI \fR
+.sp
+Example:
+\fI\fIpid directory\fR\fR\fI = \fR\fIpid directory = /var/run/\fR\fI \fR
+.RE
 posix locking (S)
+.RS 3n
+.PP
+.RS 4
 The
 \fBsmbd\fR(8)
 daemon maintains an database of file locks obtained by SMB clients. The default behavior is to map this internal database to POSIX locks. This means that file locks obtained by SMB clients are consistent with those seen by POSIX compliant applications accessing the files via a non-SMB method (e.g. NFS or local file access). You should never need to disable this parameter.
 .sp
 Default:
 \fB\fIposix locking\fR = yes \fR
 .RE
+.PP
+daemon maintains an database of file locks obtained by SMB clients\. The default behavior is to map this internal database to POSIX locks\. This means that file locks obtained by SMB clients are consistent with those seen by POSIX compliant applications accessing the files via a non\-SMB method (e\.g\. NFS or local file access)\. You should never need to disable this parameter\.
+.sp
+Default:
+\fI\fIposix locking\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 postexec (S)
+.RS 3n
+This option specifies a command to be run whenever the service is disconnected. It takes the usual substitutions. The command may be run as the root on some systems.
+.PP
+.RS 4
+This option specifies a command to be run whenever the service is disconnected\. It takes the usual substitutions\. The command may be run as the root on some systems\.
 .sp
 An interesting example may be to unmount server resources:
 …
 .sp
 Default:
+\fB\fIpostexec\fR = \fR
+.sp
+Example:
+\fB\fIpostexec\fR = echo \\"%u disconnected from %S from %m (%I)\\" >> /tmp/log \fR
+.RE
+.PP
+exec
+.RS 3n
+This parameter is a synonym for preexec.
+.RE
+.PP
+\fI\fIpostexec\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fIpostexec\fR\fR\fI = \fR\fIecho \e"%u disconnected from %S from %m (%I)\e" >> /tmp/log\fR\fI \fR
+.RE
+preexec close (S)
+.PP
+.RS 4
+This boolean option controls whether a non\-zero return code from
+\fIpreexec\fR
+should close the service being connected to\.
+.sp
+Default:
+\fI\fIpreexec close\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
+exec.PP
+.RS 4
+This parameter is a synonym for
+preexec\.
+.RE
 preexec (S)
+.RS 3n
+This option specifies a command to be run whenever the service is connected to. It takes the usual substitutions.
+.sp
+An interesting example is to send the users a welcome message every time they log in. Maybe a message of the day? Here is an example:
+.sp
+preexec = csh -c 'echo \\"Welcome to %S!\\" | /usr/local/samba/bin/smbclient -M %m -I %I' &
+.sp
+Of course, this could get annoying after a while :-)
+.PP
+.RS 4
+This option specifies a command to be run whenever the service is connected to\. It takes the usual substitutions\.
+.sp
+An interesting example is to send the users a welcome message every time they log in\. Maybe a message of the day? Here is an example:
+.sp
+preexec = csh \-c \'echo \e"Welcome to %S!\e" | /usr/local/samba/bin/smbclient \-M %m \-I %I\' &
+.sp
+Of course, this could get annoying after a while :\-)
 .sp
 See also
+preexec close and
+postexec.
+.sp
+Default:
+\fB\fIpreexec\fR = \fR
+.sp
+Example:
+\fB\fIpreexec\fR = echo \\"%u connected to %S from %m (%I)\\" >> /tmp/log \fR
+.RE
+.PP
+preexec close (S)
+.RS 3n
+This boolean option controls whether a non-zero return code from
+preexec should close the service being connected to.
+.sp
+Default:
+\fB\fIpreexec close\fR = no \fR
+.RE
+.PP
+prefered master
+.RS 3n
+This parameter is a synonym for preferred master.
+.RE
+.PP
+\fIpreexec close\fR
+and
+\fIpostexec\fR\.
+.sp
+Default:
+\fI\fIpreexec\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fIpreexec\fR\fR\fI = \fR\fIecho \e"%u connected to %S from %m (%I)\e" >> /tmp/log\fR\fI \fR
+.RE
+prefered master.PP
+.RS 4
+This parameter is a synonym for
+preferred master\.
+.RE
 preferred master (G)
+.RS 3n
+.PP
+.RS 4
 This boolean parameter controls if
 \fBnmbd\fR(8)
 is a preferred master browser for its workgroup.
+is a preferred master browser for its workgroup\.
 .sp
 If this is set to
 \fByes\fR, on startup,
 nmbd
 will force an election, and it will have a slight advantage in winning the election. It is recommended that this parameter is used in conjunction with
 domain master = yes, so that
+will force an election, and it will have a slight advantage in winning the election\. It is recommended that this parameter is used in conjunction with
+\fIdomain master = yes\fR, so that
 nmbd
+can guarantee becoming a domain master.
+.sp
+Use this option with caution, because if there are several hosts (whether Samba servers, Windows 95 or NT) that are preferred master browsers on the same subnet, they will each periodically and continuously attempt to become the local master browser. This will result in unnecessary broadcast traffic and reduced browsing capabilities.
+.sp
+Default:
+\fB\fIpreferred master\fR = auto \fR
+.RE
+.PP
+auto services
+.RS 3n
+This parameter is a synonym for preload.
+.RE
+.PP
+can guarantee becoming a domain master\.
+.sp
+Use this option with caution, because if there are several hosts (whether Samba servers, Windows 95 or NT) that are preferred master browsers on the same subnet, they will each periodically and continuously attempt to become the local master browser\. This will result in unnecessary broadcast traffic and reduced browsing capabilities\.
+.sp
+Default:
+\fI\fIpreferred master\fR\fR\fI = \fR\fIauto\fR\fI \fR
+.RE
+preload modules (G)
+.PP
+.RS 4
+This is a list of paths to modules that should be loaded into smbd before a client connects\. This improves the speed of smbd when reacting to new connections somewhat\.
+.sp
+Default:
+\fI\fIpreload modules\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fIpreload modules\fR\fR\fI = \fR\fI/usr/lib/samba/passdb/mysql\.so\fR\fI \fR
+.RE
+auto services.PP
+.RS 4
+This parameter is a synonym for
+preload\.
+.RE
 preload (G)
+.RS 3n
+This is a list of services that you want to be automatically added to the browse lists. This is most useful for homes and printers services that would otherwise not be visible.
+.PP
+.RS 4
+This is a list of services that you want to be automatically added to the browse lists\. This is most useful for homes and printers services that would otherwise not be visible\.
 .sp
 Note that if you just want all printers in your printcap file loaded then the
+load printers option is easier.
+.sp
+Default:
+\fB\fIpreload\fR = \fR
+.sp
+Example:
+\fB\fIpreload\fR = fred lp colorlp \fR
+.RE
+.PP
+preload modules (G)
+.RS 3n
+This is a list of paths to modules that should be loaded into smbd before a client connects. This improves the speed of smbd when reacting to new connections somewhat.
+.sp
+Default:
+\fB\fIpreload modules\fR = \fR
+.sp
+Example:
+\fB\fIpreload modules\fR = /usr/lib/samba/passdb/mysql.so \fR
+.RE
+.PP
+\fIload printers\fR
+option is easier\.
+.sp
+Default:
+\fI\fIpreload\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fIpreload\fR\fR\fI = \fR\fIfred lp colorlp\fR\fI \fR
+.RE
 preserve case (S)
+.RS 3n
+.PP
+.RS 4
 This controls if new filenames are created with the case that the client passes, or if they are forced to be the
 default case.
+\fIdefault case\fR\.
 .sp
 See the section on
 NAME MANGLING
 for a fuller discussion.
 .sp
 Default:
 \fB\fIpreserve case\fR = yes \fR
 .RE
 .PP
+print ok
+.RS 3n
 This parameter is a synonym for printable.
 .RE
+.PP
+for a fuller discussion\.
+.sp
+Default:
+\fI\fIpreserve case\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
+print ok.PP
+.RS 4
+This parameter is a synonym for
+printable\.
+.RE
 printable (S)
+.RS 3n
+.PP
+.RS 4
 If this parameter is
+\fByes\fR, then clients may open, write to and submit spool files on the directory specified for the service.
+.sp
+Note that a printable service will ALWAYS allow writing to the service path (user privileges permitting) via the spooling of print data. The
+read only parameter controls only non-printing access to the resource.
+.sp
+Default:
+\fB\fIprintable\fR = no \fR
+.RE
+.PP
+\fByes\fR, then clients may open, write to and submit spool files on the directory specified for the service\.
+.sp
+Note that a printable service will ALWAYS allow writing to the service path (user privileges permitting) via the spooling of print data\. The
+\fIread only\fR
+parameter controls only non\-printing access to the resource\.
+.sp
+Default:
+\fI\fIprintable\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 printcap cache time (G)
+.RS 3n
+This option specifies the number of seconds before the printing subsystem is again asked for the known printers. If the value is greater than 60 the initial waiting time is set to 60 seconds to allow an earlier first rescan of the printing subsystem.
+.sp
+Setting this parameter to 0 disables any rescanning for new or removed printers after the initial startup.
+.sp
+Default:
+\fB\fIprintcap cache time\fR = 750 \fR
+.sp
+Example:
+\fB\fIprintcap cache time\fR = 600 \fR
+.RE
+.PP
+printcap
+.RS 3n
+This parameter is a synonym for printcap name.
+.RE
+.PP
+.PP
+.RS 4
+This option specifies the number of seconds before the printing subsystem is again asked for the known printers\. If the value is greater than 60 the initial waiting time is set to 60 seconds to allow an earlier first rescan of the printing subsystem\.
+.sp
+Setting this parameter to 0 disables any rescanning for new or removed printers after the initial startup\.
+.sp
+Default:
+\fI\fIprintcap cache time\fR\fR\fI = \fR\fI750\fR\fI \fR
+.sp
+Example:
+\fI\fIprintcap cache time\fR\fR\fI = \fR\fI600\fR\fI \fR
+.RE
+printcap.PP
+.RS 4
+This parameter is a synonym for
+printcap name\.
+.RE
 printcap name (S)
+.RS 3n
+This parameter may be used to override the compiled-in default printcap name used by the server (usually
+\fI /etc/printcap\fR). See the discussion of the
+.PP
+.RS 4
+This parameter may be used to override the compiled\-in default printcap name used by the server (usually
+\fI /etc/printcap\fR)\. See the discussion of the
 [printers]
 section above for reasons why you might want to do this.
+section above for reasons why you might want to do this\.
 .sp
 To use the CUPS printing interface set
+printcap name = cups. This should be supplemented by an addtional setting
+printing = cups in the [global] section.
+printcap name = cups\. This should be supplemented by an addtional setting
+\fIprinting = cups\fR
+in the [global] section\.
 printcap name = cups
 will use the "dummy" printcap created by CUPS, as specified in your CUPS configuration file.
+will use the "dummy" printcap created by CUPS, as specified in your CUPS configuration file\.
 .sp
 On System V systems that use
 …
 to list available printers you can use
 printcap name = lpstat
 to automatically obtain lists of available printers. This is the default for systems that define SYSV at configure time in Samba (this includes most System V based systems). If
+to automatically obtain lists of available printers\. This is the default for systems that define SYSV at configure time in Samba (this includes most System V based systems)\. If
 \fI printcap name\fR
 is set to
 lpstat
 on these systems then Samba will launch
 lpstat -v
 and attempt to parse the output to obtain a printer list.
+lpstat \-v
+and attempt to parse the output to obtain a printer list\.
 .sp
 A minimal printcap file would look something like this:
+.sp
+.sp
+.RS 4
 .nf
 print1|My Printer 1
 print2|My Printer 2
 …
 print4|My Printer 4
 print5|My Printer 5
 .fi
+where the '|' separates aliases of a printer. The fact that the second alias has a space in it gives a hint to Samba that it's a comment.
+.RE
+.sp
+where the \'|\' separates aliases of a printer\. The fact that the second alias has a space in it gives a hint to Samba that it\'s a comment\.
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBNote\fR
+Note
 Under AIX the default printcap name is
 \fI/etc/qconfig\fR. Samba will assume the file is in AIX
+\fI/etc/qconfig\fR\. Samba will assume the file is in AIX
 \fIqconfig\fR
 format if the string
 \fIqconfig\fR
+appears in the printcap filename.
+Default:
+\fB\fIprintcap name\fR = /etc/printcap \fR
+.sp
+Example:
+\fB\fIprintcap name\fR = /etc/myprintcap \fR
+.RE
+.PP
+appears in the printcap filename\.
+Default:
+\fI\fIprintcap name\fR\fR\fI = \fR\fI/etc/printcap\fR\fI \fR
+.sp
+Example:
+\fI\fIprintcap name\fR\fR\fI = \fR\fI/etc/myprintcap\fR\fI \fR
+.RE
 print command (S)
+.RS 3n
+.PP
+.RS 4
 After a print job has finished spooling to a service, this command will be used via a
 system()
 call to process the spool file. Typically the command specified will submit the spool file to the host's printing subsystem, but there is no requirement that this be the case. The server will not remove the spool file, so whatever command you specify should remove the spool file when it has been processed, otherwise you will need to manually remove old spool files.
 .sp
 The print command is simply a text string. It will be used verbatim after macro substitutions have been made:
 .sp
 %s, %f - the path to the spool file name
 .sp
 %p - the appropriate printer name
 .sp
 %J - the job name as transmitted by the client.
 .sp
 %c - The number of printed pages of the spooled job (if known).
 .sp
 %z - the size of the spooled print job (in bytes)
+call to process the spool file\. Typically the command specified will submit the spool file to the host\'s printing subsystem, but there is no requirement that this be the case\. The server will not remove the spool file, so whatever command you specify should remove the spool file when it has been processed, otherwise you will need to manually remove old spool files\.
+.sp
+The print command is simply a text string\. It will be used verbatim after macro substitutions have been made:
+.sp
+%s, %f \- the path to the spool file name
+.sp
+%p \- the appropriate printer name
+.sp
+%J \- the job name as transmitted by the client\.
+.sp
+%c \- The number of printed pages of the spooled job (if known)\.
+.sp
+%z \- the size of the spooled print job (in bytes)
 .sp
 The print command
 \fBMUST\fR
+\fIMUST\fR
 contain at least one occurrence of
 \fI%s\fR
 or
 \fI%f \fR
 - the
+\- the
 \fI%p\fR
 is optional. At the time a job is submitted, if no printer name is supplied the
+is optional\. At the time a job is submitted, if no printer name is supplied the
 \fI%p \fR
 will be silently removed from the printer command.
 .sp
 If specified in the [global] section, the print command given will be used for any printable service that does not have its own print command specified.
 .sp
 If there is neither a specified print command for a printable service nor a global print command, spool files will be created but not processed and (most importantly) not removed.
+will be silently removed from the printer command\.
+.sp
+If specified in the [global] section, the print command given will be used for any printable service that does not have its own print command specified\.
+.sp
+If there is neither a specified print command for a printable service nor a global print command, spool files will be created but not processed and (most importantly) not removed\.
 .sp
 Note that printing may fail on some UNIXes from the
 \fBnobody\fR
+account. If this happens then create an alternative guest account that can print and set the
+guest account in the [global] section.
+.sp
+You can form quite complex print commands by realizing that they are just passed to a shell. For example the following will log a print job, print the file, then remove it. Note that ';' is the usual separator for command in shell scripts.
+.sp
+print command = echo Printing %s >> /tmp/print.log; lpr -P %p %s; rm %s
+.sp
+You may have to vary this command considerably depending on how you normally print files on your system. The default for the parameter varies depending on the setting of the
+printing parameter.
+account\. If this happens then create an alternative guest account that can print and set the
+\fIguest account\fR
+in the [global] section\.
+.sp
+You can form quite complex print commands by realizing that they are just passed to a shell\. For example the following will log a print job, print the file, then remove it\. Note that \';\' is the usual separator for command in shell scripts\.
+.sp
+print command = echo Printing %s >> /tmp/print\.log; lpr \-P %p %s; rm %s
+.sp
+You may have to vary this command considerably depending on how you normally print files on your system\. The default for the parameter varies depending on the setting of the
+\fIprinting\fR
+parameter\.
 .sp
 Default: For
 printing = BSD, AIX, QNX, LPRNG or PLP :
 .sp
 print command = lpr -r -P%p %s
+print command = lpr \-r \-P%p %s
 .sp
 For
 printing = SYSV or HPUX :
 .sp
 print command = lp -c -d%p %s; rm %s
+print command = lp \-c \-d%p %s; rm %s
 .sp
 For
 printing = SOFTQ :
 .sp
 print command = lp -d%p -s %s; rm %s
+print command = lp \-d%p \-s %s; rm %s
 .sp
 For printing = CUPS : If SAMBA is compiled against libcups, then
+printcap = cups uses the CUPS API to submit jobs, etc. Otherwise it maps to the System V commands with the -oraw option for printing, i.e. it uses
+lp -c -d%p -oraw; rm %s. With
+printing = cups, and if SAMBA is compiled against libcups, any manually set print command will be ignored.
+.sp
+\fBNo default\fR
+.sp
+Example:
+\fB\fIprint command\fR = /usr/local/samba/bin/myprintscript %p %s \fR
+.RE
+.PP
+\fIprintcap = cups\fR
+uses the CUPS API to submit jobs, etc\. Otherwise it maps to the System V commands with the \-oraw option for printing, i\.e\. it uses
+lp \-c \-d%p \-oraw; rm %s\. With
+printing = cups, and if SAMBA is compiled against libcups, any manually set print command will be ignored\.
+.sp
+\fINo default\fR
+.sp
+Example:
+\fI\fIprint command\fR\fR\fI = \fR\fI/usr/local/samba/bin/myprintscript %p %s\fR\fI \fR
+.RE
 printer admin (S)
+.RS 3n
+This lists users who can do anything to printers via the remote administration interfaces offered by MS-RPC (usually using a NT workstation). This parameter can be set per-share or globally. Note: The root user always has admin rights. Use caution with use in the global stanza as this can cause side effects.
+.sp
+This parameter has been marked deprecated in favor of using the SePrintOperatorPrivilege and individual print security descriptors. It will be removed in a future release.
+.sp
+Default:
+\fB\fIprinter admin\fR = \fR
+.sp
+Example:
+\fB\fIprinter admin\fR = admin, @staff \fR
+.RE
+.PP
+printer
+.RS 3n
+This parameter is a synonym for printer name.
+.RE
+.PP
+.PP
+.RS 4
+This lists users who can do anything to printers via the remote administration interfaces offered by MS\-RPC (usually using a NT workstation)\. This parameter can be set per\-share or globally\. Note: The root user always has admin rights\. Use caution with use in the global stanza as this can cause side effects\.
+.sp
+This parameter has been marked deprecated in favor of using the SePrintOperatorPrivilege and individual print security descriptors\. It will be removed in a future release\.
+.sp
+Default:
+\fI\fIprinter admin\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fIprinter admin\fR\fR\fI = \fR\fIadmin, @staff\fR\fI \fR
+.RE
+printer.PP
+.RS 4
+This parameter is a synonym for
+printer name\.
+.RE
 printer name (S)
+.RS 3n
+This parameter specifies the name of the printer to which print jobs spooled through a printable service will be sent.
+.sp
+If specified in the [global] section, the printer name given will be used for any printable service that does not have its own printer name specified.
+.PP
+.RS 4
+This parameter specifies the name of the printer to which print jobs spooled through a printable service will be sent\.
+.sp
+If specified in the [global] section, the printer name given will be used for any printable service that does not have its own printer name specified\.
 .sp
 The default value of the
+printer name may be
+\fIprinter name\fR
+may be
 lp
 on many systems.
 .sp
 Default:
 \fB\fIprinter name\fR = none \fR
 .sp
 Example:
 \fB\fIprinter name\fR = laserwriter \fR
 .RE
+.PP
+on many systems\.
+.sp
+Default:
+\fI\fIprinter name\fR\fR\fI = \fR\fInone\fR\fI \fR
+.sp
+Example:
+\fI\fIprinter name\fR\fR\fI = \fR\fIlaserwriter\fR\fI \fR
+.RE
 printing (S)
+.RS 3n
+This parameters controls how printer status information is interpreted on your system. It also affects the default values for the
+.PP
+.RS 4
+This parameters controls how printer status information is interpreted on your system\. It also affects the default values for the
 \fIprint command\fR,
 \fIlpq command\fR,
 …
 \fIlpresume command\fR, and
 \fIlprm command\fR
 if specified in the [global] section.
 .sp
 Currently nine printing styles are supported. They are
+if specified in the [global] section\.
+.sp
+Currently nine printing styles are supported\. They are
 \fBBSD\fR,
 \fBAIX\fR,
 …
 \fBQNX\fR,
 \fBSOFTQ\fR, and
 \fBCUPS\fR.
+\fBCUPS\fR\.
 .sp
 To see what the defaults are for the other print commands when using the various options use the
 \fBtestparm\fR(1)
 program.
 .sp
 This option can be set on a per printer basis. Please be aware however, that you must place any of the various printing commands (e.g. print command, lpq command, etc...) after defining the value for the
+program\.
+.sp
+This option can be set on a per printer basis\. Please be aware however, that you must place any of the various printing commands (e\.g\. print command, lpq command, etc\.\.\.) after defining the value for the
 \fIprinting\fR
 option since it will reset the printing commands to default values.
+option since it will reset the printing commands to default values\.
 .sp
 See also the discussion in the
 [printers]
 section.
 .sp
 \fBNo default\fR
 .RE
+.PP
+section\.
+.sp
+\fINo default\fR
+.RE
 printjob username (S)
+.RS 3n
+This parameter specifies which user information will be passed to the printing system. Usually, the username is sent, but in some cases, e.g. the domain prefix is useful, too.
+.sp
+Default:
+\fB\fIprintjob username\fR = %U \fR
+.sp
+Example:
+\fB\fIprintjob username\fR = %D\\%U \fR
+.RE
+.PP
+.PP
+.RS 4
+This parameter specifies which user information will be passed to the printing system\. Usually, the username is sent, but in some cases, e\.g\. the domain prefix is useful, too\.
+.sp
+Default:
+\fI\fIprintjob username\fR\fR\fI = \fR\fI%U\fR\fI \fR
+.sp
+Example:
+\fI\fIprintjob username\fR\fR\fI = \fR\fI%D\e%U\fR\fI \fR
+.RE
 private dir (G)
+.RS 3n
+.PP
+.RS 4
 This parameters defines the directory smbd will use for storing such files as
 \fIsmbpasswd\fR
 and
 \fIsecrets.tdb\fR.
 .sp
 Default:
 \fB\fIprivate dir\fR = ${prefix}/private \fR
 .RE
+.PP
+\fIsecrets\.tdb\fR\.
+.sp
+Default:
+\fI\fIprivate dir\fR\fR\fI = \fR\fI${prefix}/private\fR\fI \fR
+.RE
 profile acls (S)
+.RS 3n
+This boolean parameter was added to fix the problems that people have been having with storing user profiles on Samba shares from Windows 2000 or Windows XP clients. New versions of Windows 2000 or Windows XP service packs do security ACL checking on the owner and ability to write of the profile directory stored on a local workstation when copied from a Samba share.
+.sp
+When not in domain mode with winbindd then the security info copied onto the local workstation has no meaning to the logged in user (SID) on that workstation so the profile storing fails. Adding this parameter onto a share used for profile storage changes two things about the returned Windows ACL. Firstly it changes the owner and group owner of all reported files and directories to be BUILTIN\\Administrators, BUILTIN\\Users respectively (SIDs S-1-5-32-544, S-1-5-32-545). Secondly it adds an ACE entry of "Full Control" to the SID BUILTIN\\Users to every returned ACL. This will allow any Windows 2000 or XP workstation user to access the profile.
+.sp
+Note that if you have multiple users logging on to a workstation then in order to prevent them from being able to access each others profiles you must remove the "Bypass traverse checking" advanced user right. This will prevent access to other users profile directories as the top level profile directory (named after the user) is created by the workstation profile code and has an ACL restricting entry to the directory tree to the owning user.
+.sp
+Default:
+\fB\fIprofile acls\fR = no \fR
+.RE
+.PP
+.PP
+.RS 4
+This boolean parameter was added to fix the problems that people have been having with storing user profiles on Samba shares from Windows 2000 or Windows XP clients\. New versions of Windows 2000 or Windows XP service packs do security ACL checking on the owner and ability to write of the profile directory stored on a local workstation when copied from a Samba share\.
+.sp
+When not in domain mode with winbindd then the security info copied onto the local workstation has no meaning to the logged in user (SID) on that workstation so the profile storing fails\. Adding this parameter onto a share used for profile storage changes two things about the returned Windows ACL\. Firstly it changes the owner and group owner of all reported files and directories to be BUILTIN\e\eAdministrators, BUILTIN\e\eUsers respectively (SIDs S\-1\-5\-32\-544, S\-1\-5\-32\-545)\. Secondly it adds an ACE entry of "Full Control" to the SID BUILTIN\e\eUsers to every returned ACL\. This will allow any Windows 2000 or XP workstation user to access the profile\.
+.sp
+Note that if you have multiple users logging on to a workstation then in order to prevent them from being able to access each others profiles you must remove the "Bypass traverse checking" advanced user right\. This will prevent access to other users profile directories as the top level profile directory (named after the user) is created by the workstation profile code and has an ACL restricting entry to the directory tree to the owning user\.
+.sp
+Default:
+\fI\fIprofile acls\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 queuepause command (S)
+.RS 3n
+This parameter specifies the command to be executed on the server host in order to pause the printer queue.
+.sp
+This command should be a program or script which takes a printer name as its only parameter and stops the printer queue, such that no longer jobs are submitted to the printer.
+.sp
+This command is not supported by Windows for Workgroups, but can be issued from the Printers window under Windows 95 and NT.
+.PP
+.RS 4
+This parameter specifies the command to be executed on the server host in order to pause the printer queue\.
+.sp
+This command should be a program or script which takes a printer name as its only parameter and stops the printer queue, such that no longer jobs are submitted to the printer\.
+.sp
+This command is not supported by Windows for Workgroups, but can be issued from the Printers window under Windows 95 and NT\.
 .sp
 If a
 \fI%p\fR
 is given then the printer name is put in its place. Otherwise it is placed at the end of the command.
 .sp
 Note that it is good practice to include the absolute path in the command as the PATH may not be available to the server.
 .sp
 \fBNo default\fR
 .sp
 Example:
 \fB\fIqueuepause command\fR = disable %p \fR
 .RE
+.PP
+is given then the printer name is put in its place\. Otherwise it is placed at the end of the command\.
+.sp
+Note that it is good practice to include the absolute path in the command as the PATH may not be available to the server\.
+.sp
+\fINo default\fR
+.sp
+Example:
+\fI\fIqueuepause command\fR\fR\fI = \fR\fIdisable %p\fR\fI \fR
+.RE
 queueresume command (S)
+.RS 3n
+This parameter specifies the command to be executed on the server host in order to resume the printer queue. It is the command to undo the behavior that is caused by the previous parameter (queuepause command).
+.sp
+This command should be a program or script which takes a printer name as its only parameter and resumes the printer queue, such that queued jobs are resubmitted to the printer.
+.sp
+This command is not supported by Windows for Workgroups, but can be issued from the Printers window under Windows 95 and NT.
+.PP
+.RS 4
+This parameter specifies the command to be executed on the server host in order to resume the printer queue\. It is the command to undo the behavior that is caused by the previous parameter (\fIqueuepause command\fR)\.
+.sp
+This command should be a program or script which takes a printer name as its only parameter and resumes the printer queue, such that queued jobs are resubmitted to the printer\.
+.sp
+This command is not supported by Windows for Workgroups, but can be issued from the Printers window under Windows 95 and NT\.
 .sp
 If a
 \fI%p\fR
 is given then the printer name is put in its place. Otherwise it is placed at the end of the command.
 .sp
 Note that it is good practice to include the absolute path in the command as the PATH may not be available to the server.
 .sp
 Default:
 \fB\fIqueueresume command\fR = \fR
 .sp
 Example:
 \fB\fIqueueresume command\fR = enable %p \fR
 .RE
+.PP
+is given then the printer name is put in its place\. Otherwise it is placed at the end of the command\.
+.sp
+Note that it is good practice to include the absolute path in the command as the PATH may not be available to the server\.
+.sp
+Default:
+\fI\fIqueueresume command\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fIqueueresume command\fR\fR\fI = \fR\fIenable %p\fR\fI \fR
+.RE
 read bmpx (G)
+.RS 3n
+.PP
+.RS 4
 This boolean parameter controls whether
 \fBsmbd\fR(8)
 will support the "Read Block Multiplex" SMB. This is now rarely used and defaults to
 \fBno\fR. You should never need to set this parameter.
 .sp
 Default:
 \fB\fIread bmpx\fR = no \fR
 .RE
+.PP
+will support the "Read Block Multiplex" SMB\. This is now rarely used and defaults to
+\fBno\fR\. You should never need to set this parameter\.
+.sp
+Default:
+\fI\fIread bmpx\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 read list (S)
+.RS 3n
+This is a list of users that are given read-only access to a service. If the connecting user is in this list then they will not be given write access, no matter what the
+read only option is set to. The list can include group names using the syntax described in the
+invalid users parameter.
+.PP
+.RS 4
+This is a list of users that are given read\-only access to a service\. If the connecting user is in this list then they will not be given write access, no matter what the
+\fIread only\fR
+option is set to\. The list can include group names using the syntax described in the
+\fIinvalid users\fR
+parameter\.
 .sp
 This parameter will not work with the
+security = share in Samba 3.0. This is by design.
+.sp
+Default:
+\fB\fIread list\fR = \fR
+.sp
+Example:
+\fB\fIread list\fR = mary, @students \fR
+.RE
+.PP
+\fIsecurity = share\fR
+in Samba 3\.0\. This is by design\.
+.sp
+Default:
+\fI\fIread list\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fIread list\fR\fR\fI = \fR\fImary, @students\fR\fI \fR
+.RE
 read only (S)
+.RS 3n
+.PP
+.RS 4
 An inverted synonym is
 writeable.
+\fIwriteable\fR\.
 .sp
 If this parameter is
 \fByes\fR, then users of a service may not create or modify files in the service's directory.
+\fByes\fR, then users of a service may not create or modify files in the service\'s directory\.
 .sp
 Note that a printable service (printable = yes) will
 \fBALWAYS\fR
 allow writing to the directory (user privileges permitting), but only via spooling operations.
 .sp
 Default:
 \fB\fIread only\fR = yes \fR
 .RE
+.PP
+\fIALWAYS\fR
+allow writing to the directory (user privileges permitting), but only via spooling operations\.
+.sp
+Default:
+\fI\fIread only\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 read raw (G)
+.RS 3n
+This parameter controls whether or not the server will support the raw read SMB requests when transferring data to clients.
+.sp
+If enabled, raw reads allow reads of 65535 bytes in one packet. This typically provides a major performance benefit.
+.sp
+However, some clients either negotiate the allowable block size incorrectly or are incapable of supporting larger block sizes, and for these clients you may need to disable raw reads.
+.sp
+In general this parameter should be viewed as a system tuning tool and left severely alone.
+.sp
+Default:
+\fB\fIread raw\fR = yes \fR
+.RE
+.PP
+.PP
+.RS 4
+This parameter controls whether or not the server will support the raw read SMB requests when transferring data to clients\.
+.sp
+If enabled, raw reads allow reads of 65535 bytes in one packet\. This typically provides a major performance benefit\.
+.sp
+However, some clients either negotiate the allowable block size incorrectly or are incapable of supporting larger block sizes, and for these clients you may need to disable raw reads\.
+.sp
+In general this parameter should be viewed as a system tuning tool and left severely alone\.
+.sp
+Default:
+\fI\fIread raw\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 realm (G)
+.RS 3n
+This option specifies the kerberos realm to use. The realm is used as the ADS equivalent of the NT4
+domain. It is usually set to the DNS name of the kerberos server.
+.sp
+Default:
+\fB\fIrealm\fR = \fR
+.sp
+Example:
+\fB\fIrealm\fR = mysambabox.mycompany.com \fR
+.RE
+.PP
+.PP
+.RS 4
+This option specifies the kerberos realm to use\. The realm is used as the ADS equivalent of the NT4
+domain\. It is usually set to the DNS name of the kerberos server\.
+.sp
+Default:
+\fI\fIrealm\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fIrealm\fR\fR\fI = \fR\fImysambabox\.mycompany\.com\fR\fI \fR
+.RE
 remote announce (G)
+.RS 3n
+.PP
+.RS 4
 This option allows you to setup
 \fBnmbd\fR(8)to periodically announce itself to arbitrary IP addresses with an arbitrary workgroup name.
 .sp
 This is useful if you want your Samba server to appear in a remote workgroup for which the normal browse propagation rules don't work. The remote workgroup can be anywhere that you can send IP packets to.
+\fBnmbd\fR(8)to periodically announce itself to arbitrary IP addresses with an arbitrary workgroup name\.
+.sp
+This is useful if you want your Samba server to appear in a remote workgroup for which the normal browse propagation rules don\'t work\. The remote workgroup can be anywhere that you can send IP packets to\.
 .sp
 For example:
+.sp
+.sp
+.RS 4
 .nf
+remote announce = 192.168.2.255/SERVERS 192.168.4.255/STAFF
+remote announce = 192\.168\.2\.255/SERVERS 192\.168\.4\.255/STAFF
 .fi
+.RE
+.sp
 the above line would cause
 nmbd
+to announce itself to the two given IP addresses using the given workgroup names. If you leave out the workgroup name then the one given in the
+workgroup parameter is used instead.
+.sp
+The IP addresses you choose would normally be the broadcast addresses of the remote networks, but can also be the IP addresses of known browse masters if your network config is that stable.
+.sp
+See the chapter on Network Browsing in the Samba-HOWTO book.
+.sp
+Default:
+\fB\fIremote announce\fR = \fR
+.RE
+.PP
+to announce itself to the two given IP addresses using the given workgroup names\. If you leave out the workgroup name then the one given in the
+\fIworkgroup\fR
+parameter is used instead\.
+.sp
+The IP addresses you choose would normally be the broadcast addresses of the remote networks, but can also be the IP addresses of known browse masters if your network config is that stable\.
+.sp
+See the chapter on Network Browsing in the Samba\-HOWTO book\.
+.sp
+Default:
+\fI\fIremote announce\fR\fR\fI = \fR\fI\fR\fI \fR
+.RE
 remote browse sync (G)
+.RS 3n
+.PP
+.RS 4
 This option allows you to setup
 \fBnmbd\fR(8)
 to periodically request synchronization of browse lists with the master browser of a Samba server that is on a remote segment. This option will allow you to gain browse lists for multiple workgroups across routed networks. This is done in a manner that does not work with any non-Samba servers.
 .sp
 This is useful if you want your Samba server and all local clients to appear in a remote workgroup for which the normal browse propagation rules don't work. The remote workgroup can be anywhere that you can send IP packets to.
+to periodically request synchronization of browse lists with the master browser of a Samba server that is on a remote segment\. This option will allow you to gain browse lists for multiple workgroups across routed networks\. This is done in a manner that does not work with any non\-Samba servers\.
+.sp
+This is useful if you want your Samba server and all local clients to appear in a remote workgroup for which the normal browse propagation rules don\'t work\. The remote workgroup can be anywhere that you can send IP packets to\.
 .sp
 For example:
+.sp
+.sp
+.RS 4
 .nf
+\fIremote browse sync = 192.168.2.255 192.168.4.255\fR
+\fIremote browse sync = 192\.168\.2\.255 192\.168\.4\.255\fR
 .fi
+.RE
+.sp
 the above line would cause
 nmbd
 to request the master browser on the specified subnets or addresses to synchronize their browse lists with the local server.
 .sp
 The IP addresses you choose would normally be the broadcast addresses of the remote networks, but can also be the IP addresses of known browse masters if your network config is that stable. If a machine IP address is given Samba makes NO attempt to validate that the remote machine is available, is listening, nor that it is in fact the browse master on its segment.
+to request the master browser on the specified subnets or addresses to synchronize their browse lists with the local server\.
+.sp
+The IP addresses you choose would normally be the broadcast addresses of the remote networks, but can also be the IP addresses of known browse masters if your network config is that stable\. If a machine IP address is given Samba makes NO attempt to validate that the remote machine is available, is listening, nor that it is in fact the browse master on its segment\.
 .sp
 The
+remote browse sync may be used on networks where there is no WINS server, and may be used on disjoint networks where each network has its own WINS server.
+.sp
+Default:
+\fB\fIremote browse sync\fR = \fR
+.RE
+.PP
+\fIremote browse sync\fR
+may be used on networks where there is no WINS server, and may be used on disjoint networks where each network has its own WINS server\.
+.sp
+Default:
+\fI\fIremote browse sync\fR\fR\fI = \fR\fI\fR\fI \fR
+.RE
 rename user script (G)
+.RS 3n
+.PP
+.RS 4
 This is the full pathname to a script that will be run as root by
 \fBsmbd\fR(8)
 under special circumstances described below.
 .sp
 When a user with admin authority or SeAddUserPrivilege rights renames a user (e.g.: from the NT4 User Manager for Domains), this script will be run to rename the POSIX user. Two variables,
+under special circumstances described below\.
+.sp
+When a user with admin authority or SeAddUserPrivilege rights renames a user (e\.g\.: from the NT4 User Manager for Domains), this script will be run to rename the POSIX user\. Two variables,
 %uold
 and
 %unew, will be substituted with the old and new usernames, respectively. The script should return 0 upon successful completion, and nonzero otherwise.
+%unew, will be substituted with the old and new usernames, respectively\. The script should return 0 upon successful completion, and nonzero otherwise\.
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBNote\fR
+The script has all responsibility to rename all the necessary data that is accessible in this posix method. This can mean different requirements for different backends. The tdbsam and smbpasswd backends will take care of the contents of their respective files, so the script is responsible only for changing the POSIX username, and other data that may required for your circumstances, such as home directory. Please also consider whether or not you need to rename the actual home directories themselves. The ldapsam backend will not make any changes, because of the potential issues with renaming the LDAP naming attribute. In this case the script is responsible for changing the attribute that samba uses (uid) for locating users, as well as any data that needs to change for other applications using the same directory.
+Default:
+\fB\fIrename user script\fR = no \fR
+.RE
+.PP
+Note
+The script has all responsibility to rename all the necessary data that is accessible in this posix method\. This can mean different requirements for different backends\. The tdbsam and smbpasswd backends will take care of the contents of their respective files, so the script is responsible only for changing the POSIX username, and other data that may required for your circumstances, such as home directory\. Please also consider whether or not you need to rename the actual home directories themselves\. The ldapsam backend will not make any changes, because of the potential issues with renaming the LDAP naming attribute\. In this case the script is responsible for changing the attribute that samba uses (uid) for locating users, as well as any data that needs to change for other applications using the same directory\.
+Default:
+\fI\fIrename user script\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 reset on zero vc (G)
+.RS 3n
+This boolean option controls whether an incoming session setup should kill other connections coming from the same IP. This matches the default Windows 2003 behaviour. Setting this parameter to yes becomes necessary when you have a flaky network and windows decides to reconnect while the old connection still has files with share modes open. These files become inaccessible over the new connection. The client sends a zero VC on the new connection, and Windows 2003 kills all other connections coming from the same IP. This way the locked files are accessible again. Please be aware that enabling this option will kill connections behind a masquerading router.
+.sp
+Default:
+\fB\fIreset on zero vc\fR = no \fR
+.RE
+.PP
+.PP
+.RS 4
+This boolean option controls whether an incoming session setup should kill other connections coming from the same IP\. This matches the default Windows 2003 behaviour\. Setting this parameter to yes becomes necessary when you have a flaky network and windows decides to reconnect while the old connection still has files with share modes open\. These files become inaccessible over the new connection\. The client sends a zero VC on the new connection, and Windows 2003 kills all other connections coming from the same IP\. This way the locked files are accessible again\. Please be aware that enabling this option will kill connections behind a masquerading router\.
+.sp
+Default:
+\fI\fIreset on zero vc\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 restrict anonymous (G)
 .RS 3n
+The setting of this parameter determines whether user and group list information is returned for an anonymous connection. and mirrors the effects of the
 .sp
+.PP
+.RS 4
+The setting of this parameter determines whether user and group list information is returned for an anonymous connection\. and mirrors the effects of the
+.sp
+.RS 4
 .nf
+HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\
+           Control\LSA\RestrictAnonymous
+HKEY_LOCAL_MACHINE\eSYSTEM\eCurrentControlSet\e
+           Control\eLSA\eRestrictAnonymous
 .fi
+registry key in Windows 2000 and Windows NT. When set to 0, user and group list information is returned to anyone who asks. When set to 1, only an authenticated user can retrive user and group list information. For the value 2, supported by Windows 2000/XP and Samba, no anonymous connections are allowed at all. This can break third party and Microsoft applications which expect to be allowed to perform operations anonymously.
+.sp
+The security advantage of using restrict anonymous = 1 is dubious, as user and group list information can be obtained using other means.
+.RE
+.sp
+registry key in Windows 2000 and Windows NT\. When set to 0, user and group list information is returned to anyone who asks\. When set to 1, only an authenticated user can retrive user and group list information\. For the value 2, supported by Windows 2000/XP and Samba, no anonymous connections are allowed at all\. This can break third party and Microsoft applications which expect to be allowed to perform operations anonymously\.
+.sp
+The security advantage of using restrict anonymous = 1 is dubious, as user and group list information can be obtained using other means\.
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBNote\fR
+Note
 The security advantage of using restrict anonymous = 2 is removed by setting
+guest ok = yes on any share.
+Default:
+\fB\fIrestrict anonymous\fR = 0 \fR
+.RE
+.PP
+root
+.RS 3n
+This parameter is a synonym for root directory.
+.RE
+.PP
+root dir
+.RS 3n
+This parameter is a synonym for root directory.
+.RE
+.PP
+\fIguest ok = yes\fR
+on any share\.
+Default:
+\fI\fIrestrict anonymous\fR\fR\fI = \fR\fI0\fR\fI \fR
+.RE
+root.PP
+.RS 4
+This parameter is a synonym for
+root directory\.
+.RE
+root dir.PP
+.RS 4
+This parameter is a synonym for
+root directory\.
+.RE
 root directory (G)
+.RS 3n
+.PP
+.RS 4
 The server will
 chroot()
+(i.e. Change its root directory) to this directory on startup. This is not strictly necessary for secure operation. Even without it the server will deny access to files not in one of the service entries. It may also check for, and deny access to, soft links to other parts of the filesystem, or attempts to use ".." in file names to access other directories (depending on the setting of the
+wide smbconfoptions parameter).
+(i\.e\. Change its root directory) to this directory on startup\. This is not strictly necessary for secure operation\. Even without it the server will deny access to files not in one of the service entries\. It may also check for, and deny access to, soft links to other parts of the filesystem, or attempts to use "\.\." in file names to access other directories (depending on the setting of the
+\fIwide smbconfoptions\fR
+parameter)\.
 .sp
 Adding a
 \fIroot directory\fR
 entry other than "/" adds an extra level of security, but at a price. It absolutely ensures that no access is given to files not in the sub-tree specified in the
+entry other than "/" adds an extra level of security, but at a price\. It absolutely ensures that no access is given to files not in the sub\-tree specified in the
 \fIroot directory\fR
 option,
 \fBincluding\fR
 some files needed for complete operation of the server. To maintain full operability of the server you will need to mirror some system files into the
+\fIincluding\fR
+some files needed for complete operation of the server\. To maintain full operability of the server you will need to mirror some system files into the
 \fIroot directory\fR
 tree. In particular you will need to mirror
+tree\. In particular you will need to mirror
 \fI/etc/passwd\fR
 (or a subset of it), and any binaries or configuration files needed for printing (if required). The set of files that must be mirrored is operating system dependent.
 .sp
 Default:
 \fB\fIroot directory\fR = / \fR
 .sp
 Example:
 \fB\fIroot directory\fR = /homes/smb \fR
 .RE
+.PP
+(or a subset of it), and any binaries or configuration files needed for printing (if required)\. The set of files that must be mirrored is operating system dependent\.
+.sp
+Default:
+\fI\fIroot directory\fR\fR\fI = \fR\fI/\fR\fI \fR
+.sp
+Example:
+\fI\fIroot directory\fR\fR\fI = \fR\fI/homes/smb\fR\fI \fR
+.RE
 root postexec (S)
+.RS 3n
+.PP
+.RS 4
 This is the same as the
 \fIpostexec\fR
+parameter except that the command is run as root. This is useful for unmounting filesystems (such as CDROMs) after a connection is closed.
+.sp
+Default:
+\fB\fIroot postexec\fR = \fR
+.RE
+.PP
+parameter except that the command is run as root\. This is useful for unmounting filesystems (such as CDROMs) after a connection is closed\.
+.sp
+Default:
+\fI\fIroot postexec\fR\fR\fI = \fR\fI\fR\fI \fR
+.RE
+root preexec close (S)
+.PP
+.RS 4
+This is the same as the
+\fIpreexec close \fR
+parameter except that the command is run as root\.
+.sp
+Default:
+\fI\fIroot preexec close\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 root preexec (S)
+.RS 3n
+.PP
+.RS 4
 This is the same as the
 \fIpreexec\fR
+parameter except that the command is run as root. This is useful for mounting filesystems (such as CDROMs) when a connection is opened.
+.sp
+Default:
+\fB\fIroot preexec\fR = \fR
+.RE
+.PP
+root preexec close (S)
+.RS 3n
+This is the same as the
+\fIpreexec close \fR
+parameter except that the command is run as root.
+.sp
+Default:
+\fB\fIroot preexec close\fR = no \fR
+.RE
+.PP
+parameter except that the command is run as root\. This is useful for mounting filesystems (such as CDROMs) when a connection is opened\.
+.sp
+Default:
+\fI\fIroot preexec\fR\fR\fI = \fR\fI\fR\fI \fR
+.RE
+security mask (S)
+.PP
+.RS 4
+This parameter controls what UNIX permission bits will be set when a Windows NT client is manipulating the UNIX permission on a file using the native NT security dialog box\.
+.sp
+This parameter is applied as a mask (AND\'ed with) to the incoming permission bits, thus resetting any bits not in this mask\. Make sure not to mix up this parameter with
+\fIforce security mode\fR, which works in a manner similar to this one but uses a logical OR instead of an AND\.
+.sp
+Essentially, all bits set to zero in this mask will result in setting to zero the corresponding bits on the file permissions regardless of the previous status of this bits on the file\.
+.sp
+If not set explicitly this parameter is 0777, allowing a user to set all the user/group/world permissions on a file\.
+.sp
+\fI Note\fR
+that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems\. Administrators of most normal systems will probably want to leave it set to
+\fB0777\fR\.
+.sp
+Default:
+\fI\fIsecurity mask\fR\fR\fI = \fR\fI0777\fR\fI \fR
+.sp
+Example:
+\fI\fIsecurity mask\fR\fR\fI = \fR\fI0770\fR\fI \fR
+.RE
 security (G)
+.RS 3n
+.PP
+.RS 4
 This option affects how clients respond to Samba and is one of the most important settings in the
 \fI smb.conf\fR
 file.
+\fI smb\.conf\fR
+file\.
 .sp
 The option sets the "security mode bit" in replies to protocol negotiations with
 \fBsmbd\fR(8)
 to turn share level security on or off. Clients decide based on this bit whether (and how) to transfer user and password information to the server.
+to turn share level security on or off\. Clients decide based on this bit whether (and how) to transfer user and password information to the server\.
 .sp
 The default is
 security = user, as this is the most common setting needed when talking to Windows 98 and Windows NT.
+security = user, as this is the most common setting needed when talking to Windows 98 and Windows NT\.
 .sp
 The alternatives are
 …
 security = server
 or
 security = domain.
 .sp
 In versions of Samba prior to 2.0.0, the default was
+security = domain\.
+.sp
+In versions of Samba prior to 2\.0\.0, the default was
 security = share
 mainly because that was the only option at one stage.
 .sp
 There is a bug in WfWg that has relevance to this setting. When in user or server level security a WfWg client will totally ignore the username and password you type in the "connect drive" dialog box. This makes it very difficult (if not impossible) to connect to a Samba service as anyone except the user that you are logged into WfWg as.
+mainly because that was the only option at one stage\.
+.sp
+There is a bug in WfWg that has relevance to this setting\. When in user or server level security a WfWg client will totally ignore the username and password you type in the "connect drive" dialog box\. This makes it very difficult (if not impossible) to connect to a Samba service as anyone except the user that you are logged into WfWg as\.
 .sp
 If your PCs use usernames that are the same as their usernames on the UNIX machine then you will want to use
 security = user. If you mostly use usernames that don't exist on the UNIX box then use
 security = share.
+security = user\. If you mostly use usernames that don\'t exist on the UNIX box then use
+security = share\.
 .sp
 You should also use
 security = share
 if you want to mainly setup shares without a password (guest shares). This is commonly used for a shared printer server. It is more difficult to setup guest shares with
+if you want to mainly setup shares without a password (guest shares)\. This is commonly used for a shared printer server\. It is more difficult to setup guest shares with
 security = user, see the
 map to guestparameter for details.
+\fImap to guest\fRparameter for details\.
 .sp
 It is possible to use
 smbd
 in a
 \fB hybrid mode\fR
+\fI hybrid mode\fR
 where it is offers both user and share level security under different
 NetBIOS aliases.
 .sp
 The different settings will now be explained.
 .sp
 \fBSECURITY = SHARE\fR
+\fINetBIOS aliases\fR\.
+.sp
+The different settings will now be explained\.
+.sp
+\fISECURITY = SHARE\fR
 .sp
 When clients connect to a share level security server they need not log onto the server with a valid username and password before attempting to connect to a shared resource (although modern clients such as Windows 95/98 and Windows NT will send a logon request with a username but no password when talking to a
 security = share
 server). Instead, the clients send authentication information (passwords) on a per-share basis, at the time they attempt to connect to that share.
+server)\. Instead, the clients send authentication information (passwords) on a per\-share basis, at the time they attempt to connect to that share\.
 .sp
 Note that
 smbd
 \fBALWAYS\fR
+\fIALWAYS\fR
 uses a valid UNIX user to act on behalf of the client, even in
 security = share
 level security.
+level security\.
 .sp
 As clients are not required to send a username to the server in share level security,
 smbd
 uses several techniques to determine the correct UNIX user to use on behalf of the client.
+uses several techniques to determine the correct UNIX user to use on behalf of the client\.
 .sp
 A list of possible UNIX usernames to match with the given client password is constructed using the following methods :
+.RS 3n
+.TP 3n
+\(bu
+If the
+guest only parameter is set, then all the other stages are missed and only the
+guest account username is checked.
+.TP 3n
+\(bu
+Is a username is sent with the share connection request, then this username (after mapping - see
+username map), is added as a potential username.
+.TP 3n
+\(bu
+If the client did a previous
+\fBlogon \fR
+request (the SessionSetup SMB call) then the username sent in this SMB will be added as a potential username.
+.TP 3n
+\(bu
+The name of the service the client requested is added as a potential username.
+.TP 3n
+\(bu
+The NetBIOS name of the client is added to the list as a potential username.
+.TP 3n
+\(bu
+Any users on the
+user list are added as potential usernames.
+.RE
+.IP "" 3n
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 If the
 \fIguest only\fR
+parameter is not set, then this list is then tried with the supplied password. The first user for whom the password matches will be used as the UNIX user.
+parameter is set, then all the other stages are missed and only the
+\fIguest account\fR
+username is checked\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+Is a username is sent with the share connection request, then this username (after mapping \- see
+\fIusername map\fR), is added as a potential username\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+If the client did a previous
+\fIlogon \fR
+request (the SessionSetup SMB call) then the username sent in this SMB will be added as a potential username\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+The name of the service the client requested is added as a potential username\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+The NetBIOS name of the client is added to the list as a potential username\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+Any users on the
+\fIuser\fR
+list are added as potential usernames\.
+.sp
+.RE
+If the
+\fIguest only\fR
+parameter is not set, then this list is then tried with the supplied password\. The first user for whom the password matches will be used as the UNIX user\.
 .sp
 If the
 \fIguest only\fR
 parameter is set, or no username can be determined then if the share is marked as available to the
 \fIguest account\fR, then this guest user will be used, otherwise access is denied.
+\fIguest account\fR, then this guest user will be used, otherwise access is denied\.
 .sp
 Note that it can be
 \fBvery\fR
 confusing in share-level security as to which UNIX username will eventually be used in granting access.
+\fIvery\fR
+confusing in share\-level security as to which UNIX username will eventually be used in granting access\.
 .sp
 See also the section
+NOTE ABOUT USERNAME/PASSWORD VALIDATION.
+.sp
+\fBSECURITY = USER\fR
+.sp
+This is the default security setting in Samba 3.0. With user-level security a client must first "log-on" with a valid username and password (which can be mapped using the
+username map parameter). Encrypted passwords (see the
+encrypted passwords parameter) can also be used in this security mode. Parameters such as
+user and
+guest only if set are then applied and may change the UNIX user to use on this connection, but only after the user has been successfully authenticated.
+.sp
+\fBNote\fR
+NOTE ABOUT USERNAME/PASSWORD VALIDATION\.
+.sp
+\fISECURITY = USER\fR
+.sp
+This is the default security setting in Samba 3\.0\. With user\-level security a client must first "log\-on" with a valid username and password (which can be mapped using the
+\fIusername map\fR
+parameter)\. Encrypted passwords (see the
+\fIencrypted passwords\fR
+parameter) can also be used in this security mode\. Parameters such as
+\fIuser\fR
+and
+\fIguest only\fR
+if set are then applied and may change the UNIX user to use on this connection, but only after the user has been successfully authenticated\.
+.sp
+\fINote\fR
 that the name of the resource being requested is
+\fBnot\fR
+sent to the server until after the server has successfully authenticated the client. This is why guest shares don't work in user level security without allowing the server to automatically map unknown users into the
+guest account. See the
+map to guest parameter for details on doing this.
+\fInot\fR
+sent to the server until after the server has successfully authenticated the client\. This is why guest shares don\'t work in user level security without allowing the server to automatically map unknown users into the
+\fIguest account\fR\. See the
+\fImap to guest\fR
+parameter for details on doing this\.
 .sp
 See also the section
 NOTE ABOUT USERNAME/PASSWORD VALIDATION.
 .sp
 \fBSECURITY = DOMAIN\fR
+NOTE ABOUT USERNAME/PASSWORD VALIDATION\.
+.sp
+\fISECURITY = DOMAIN\fR
 .sp
 This mode will only work correctly if
 \fBnet\fR(8)
+has been used to add this machine into a Windows NT Domain. It expects the
+encrypted passwords parameter to be set to
+\fByes\fR. In this mode Samba will try to validate the username/password by passing it to a Windows NT Primary or Backup Domain Controller, in exactly the same way that a Windows NT Server would do.
+.sp
+\fBNote\fR
+that a valid UNIX user must still exist as well as the account on the Domain Controller to allow Samba to have a valid UNIX account to map file access to.
+.sp
+\fBNote\fR
+that from the client's point of view
+has been used to add this machine into a Windows NT Domain\. It expects the
+\fIencrypted passwords\fR
+parameter to be set to
+\fByes\fR\. In this mode Samba will try to validate the username/password by passing it to a Windows NT Primary or Backup Domain Controller, in exactly the same way that a Windows NT Server would do\.
+.sp
+\fINote\fR
+that a valid UNIX user must still exist as well as the account on the Domain Controller to allow Samba to have a valid UNIX account to map file access to\.
+.sp
+\fINote\fR
+that from the client\'s point of view
 security = domain
 is the same as
 security = user. It only affects how the server deals with the authentication, it does not in any way affect what the client sees.
 .sp
 \fBNote\fR
+security = user\. It only affects how the server deals with the authentication, it does not in any way affect what the client sees\.
+.sp
+\fINote\fR
 that the name of the resource being requested is
+\fBnot\fR
+sent to the server until after the server has successfully authenticated the client. This is why guest shares don't work in user level security without allowing the server to automatically map unknown users into the
+guest account. See the
+map to guest parameter for details on doing this.
+\fInot\fR
+sent to the server until after the server has successfully authenticated the client\. This is why guest shares don\'t work in user level security without allowing the server to automatically map unknown users into the
+\fIguest account\fR\. See the
+\fImap to guest\fR
+parameter for details on doing this\.
 .sp
 See also the section
 NOTE ABOUT USERNAME/PASSWORD VALIDATION.
+NOTE ABOUT USERNAME/PASSWORD VALIDATION\.
 .sp
 See also the
+password server parameter and the
+encrypted passwords parameter.
+.sp
+\fBSECURITY = SERVER\fR
+.sp
+In this mode Samba will try to validate the username/password by passing it to another SMB server, such as an NT box. If this fails it will revert to
+security = user. It expects the
+encrypted passwords parameter to be set to
+\fByes\fR, unless the remote server does not support them. However note that if encrypted passwords have been negotiated then Samba cannot revert back to checking the UNIX password file, it must have a valid
+\fIpassword server\fR
+parameter and the
+\fIencrypted passwords\fR
+parameter\.
+.sp
+\fISECURITY = SERVER\fR
+.sp
+In this mode Samba will try to validate the username/password by passing it to another SMB server, such as an NT box\. If this fails it will revert to
+security = user\. It expects the
+\fIencrypted passwords\fR
+parameter to be set to
+\fByes\fR, unless the remote server does not support them\. However note that if encrypted passwords have been negotiated then Samba cannot revert back to checking the UNIX password file, it must have a valid
 \fIsmbpasswd\fR
 file to check users against. See the chapter about the User Database in the Samba HOWTO Collection for details on how to set this up.
+file to check users against\. See the chapter about the User Database in the Samba HOWTO Collection for details on how to set this up\.
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBNote\fR
 This mode of operation has significant pitfalls since it is more vulnerable to man-in-the-middle attacks and server impersonation. In particular, this mode of operation can cause significant resource consuption on the PDC, as it must maintain an active connection for the duration of the user's session. Furthermore, if this connection is lost, there is no way to reestablish it, and futher authentications to the Samba server may fail (from a single client, till it disconnects).
+Note
+This mode of operation has significant pitfalls since it is more vulnerable to man\-in\-the\-middle attacks and server impersonation\. In particular, this mode of operation can cause significant resource consuption on the PDC, as it must maintain an active connection for the duration of the user\'s session\. Furthermore, if this connection is lost, there is no way to reestablish it, and futher authentications to the Samba server may fail (from a single client, till it disconnects)\.
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBNote\fR
 From the client's point of view
+Note
+From the client\'s point of view
 security = server
 is the same as
+security = user. It only affects how the server deals with the authentication, it does not in any way affect what the client sees.
+\fBNote\fR
+security = user\. It only affects how the server deals with the authentication, it does not in any way affect what the client sees\.
+\fINote\fR
 that the name of the resource being requested is
+\fBnot\fR
+sent to the server until after the server has successfully authenticated the client. This is why guest shares don't work in user level security without allowing the server to automatically map unknown users into the
+guest account. See the
+map to guest parameter for details on doing this.
+\fInot\fR
+sent to the server until after the server has successfully authenticated the client\. This is why guest shares don\'t work in user level security without allowing the server to automatically map unknown users into the
+\fIguest account\fR\. See the
+\fImap to guest\fR
+parameter for details on doing this\.
 .sp
 See also the section
 NOTE ABOUT USERNAME/PASSWORD VALIDATION.
+NOTE ABOUT USERNAME/PASSWORD VALIDATION\.
 .sp
 See also the
+password server parameter and the
+encrypted passwords parameter.
+.sp
+\fBSECURITY = ADS\fR
+.sp
+In this mode, Samba will act as a domain member in an ADS realm. To operate in this mode, the machine running Samba will need to have Kerberos installed and configured and Samba will need to be joined to the ADS realm using the net utility.
+.sp
+Note that this mode does NOT make Samba operate as a Active Directory Domain Controller.
+.sp
+Read the chapter about Domain Membership in the HOWTO for details.
+.sp
+Default:
+\fB\fIsecurity\fR = USER \fR
+.sp
+Example:
+\fB\fIsecurity\fR = DOMAIN \fR
+.RE
+.PP
+security mask (S)
+.RS 3n
+This parameter controls what UNIX permission bits can be modified when a Windows NT client is manipulating the UNIX permission on a file using the native NT security dialog box.
+.sp
+This parameter is applied as a mask (AND'ed with) to the changed permission bits, thus preventing any bits not in this mask from being modified. Make sure not to mix up this parameter with
+force security mode, which works in a manner similar to this one but uses a logical OR instead of an AND.
+.sp
+Essentially, zero bits in this mask may be treated as a set of bits the user is not allowed to change.
+.sp
+If not set explicitly this parameter is 0777, allowing a user to modify all the user/group/world permissions on a file.
+.sp
+\fB Note\fR
+that users who can access the Samba server through other means can easily bypass this restriction, so it is primarily useful for standalone "appliance" systems. Administrators of most normal systems will probably want to leave it set to
+\fB0777\fR.
+.sp
+Default:
+\fB\fIsecurity mask\fR = 0777 \fR
+.sp
+Example:
+\fB\fIsecurity mask\fR = 0770 \fR
+.RE
+.PP
+\fIpassword server\fR
+parameter and the
+\fIencrypted passwords\fR
+parameter\.
+.sp
+\fISECURITY = ADS\fR
+.sp
+In this mode, Samba will act as a domain member in an ADS realm\. To operate in this mode, the machine running Samba will need to have Kerberos installed and configured and Samba will need to be joined to the ADS realm using the net utility\.
+.sp
+Note that this mode does NOT make Samba operate as a Active Directory Domain Controller\.
+.sp
+Read the chapter about Domain Membership in the HOWTO for details\.
+.sp
+Default:
+\fI\fIsecurity\fR\fR\fI = \fR\fIUSER\fR\fI \fR
+.sp
+Example:
+\fI\fIsecurity\fR\fR\fI = \fR\fIDOMAIN\fR\fI \fR
+.RE
 server schannel (G)
+.RS 3n
+This controls whether the server offers or even demands the use of the netlogon schannel.
+server schannel = no does not offer the schannel,
+server schannel = auto offers the schannel but does not enforce it, and
+server schannel = yes denies access if the client is not able to speak netlogon schannel. This is only the case for Windows NT4 before SP4.
+.PP
+.RS 4
+This controls whether the server offers or even demands the use of the netlogon schannel\.
+\fIserver schannel = no\fR
+does not offer the schannel,
+\fIserver schannel = auto\fR
+offers the schannel but does not enforce it, and
+\fIserver schannel = yes\fR
+denies access if the client is not able to speak netlogon schannel\. This is only the case for Windows NT4 before SP4\.
 .sp
 Please note that with this set to
 no
 you will have to apply the WindowsXP
 \fIWinXP_SignOrSeal.reg\fR
 registry patch found in the docs/registry subdirectory of the Samba distribution tarball.
 .sp
 Default:
 \fB\fIserver schannel\fR = auto \fR
 .sp
 Example:
 \fB\fIserver schannel\fR = yes \fR
 .RE
+.PP
+\fIWinXP_SignOrSeal\.reg\fR
+registry patch found in the docs/registry subdirectory of the Samba distribution tarball\.
+.sp
+Default:
+\fI\fIserver schannel\fR\fR\fI = \fR\fIauto\fR\fI \fR
+.sp
+Example:
+\fI\fIserver schannel\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 server signing (G)
+.RS 3n
+This controls whether the server offers or requires the client it talks to to use SMB signing. Possible values are
+\fBauto\fR,
+\fBmandatory\fR
+.PP
+.RS 4
+This controls whether the server offers or requires the client it talks to to use SMB signing\. Possible values are
+\fIauto\fR,
+\fImandatory\fR
 and
 \fBdisabled\fR.
 .sp
 When set to auto, SMB signing is offered, but not enforced. When set to mandatory, SMB signing is required and if set to disabled, SMB signing is not offered either.
 .sp
 Default:
 \fB\fIserver signing\fR = Disabled \fR
 .RE
+.PP
+\fIdisabled\fR\.
+.sp
+When set to auto, SMB signing is offered, but not enforced\. When set to mandatory, SMB signing is required and if set to disabled, SMB signing is not offered either\.
+.sp
+Default:
+\fI\fIserver signing\fR\fR\fI = \fR\fIDisabled\fR\fI \fR
+.RE
 server string (G)
+.RS 3n
+.PP
+.RS 4
 This controls what string will show up in the printer comment box in print manager and next to the IPC connection in
 net view. It can be any string that you wish to show to your users.
 .sp
 It also sets what will appear in browse lists next to the machine name.
+net view\. It can be any string that you wish to show to your users\.
+.sp
+It also sets what will appear in browse lists next to the machine name\.
 .sp
+A
 \fI%v\fR
 will be replaced with the Samba version number.
+will be replaced with the Samba version number\.
 .sp
+A
 \fI%h\fR
 will be replaced with the hostname.
 .sp
 Default:
 \fB\fIserver string\fR = Samba %v \fR
 .sp
 Example:
 \fB\fIserver string\fR = University of GNUs Samba Server \fR
 .RE
+.PP
+will be replaced with the hostname\.
+.sp
+Default:
+\fI\fIserver string\fR\fR\fI = \fR\fISamba %v\fR\fI \fR
+.sp
+Example:
+\fI\fIserver string\fR\fR\fI = \fR\fIUniversity of GNUs Samba Server\fR\fI \fR
+.RE
 set directory (S)
+.RS 3n
+.PP
+.RS 4
 If
 set directory = no, then users of the service may not use the setdir command to change directory.
+set directory = no, then users of the service may not use the setdir command to change directory\.
 .sp
 The
 setdir
 command is only implemented in the Digital Pathworks client. See the Pathworks documentation for details.
 .sp
 Default:
 \fB\fIset directory\fR = no \fR
 .RE
+.PP
+command is only implemented in the Digital Pathworks client\. See the Pathworks documentation for details\.
+.sp
+Default:
+\fI\fIset directory\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 set primary group script (G)
+.RS 3n
+Thanks to the Posix subsystem in NT a Windows User has a primary group in addition to the auxiliary groups. This script sets the primary group in the unix userdatase when an administrator sets the primary group from the windows user manager or when fetching a SAM with
+net rpc vampire.
+.PP
+.RS 4
+Thanks to the Posix subsystem in NT a Windows User has a primary group in addition to the auxiliary groups\. This script sets the primary group in the unix userdatase when an administrator sets the primary group from the windows user manager or when fetching a SAM with
+net rpc vampire\.
 \fI%u\fR
 will be replaced with the user whose primary group is to be set.
+will be replaced with the user whose primary group is to be set\.
 \fI%g\fR
 will be replaced with the group to set.
 .sp
 Default:
 \fB\fIset primary group script\fR = \fR
 .sp
 Example:
 \fB\fIset primary group script\fR = /usr/sbin/usermod -g '%g' '%u' \fR
 .RE
+.PP
+will be replaced with the group to set\.
+.sp
+Default:
+\fI\fIset primary group script\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fIset primary group script\fR\fR\fI = \fR\fI/usr/sbin/usermod \-g \'%g\' \'%u\'\fR\fI \fR
+.RE
 set quota command (G)
+.RS 3n
+.PP
+.RS 4
 The
 set quota command
 should only be used whenever there is no operating system API available from the OS that samba can use.
+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 if Samba was configured with the argument
 --with-sys-quotas
+\-\-with\-sys\-quotas
 or on linux when
 ./configure --with-quotas
 was used and a working quota api was found in the system. Most packages are configured with these options already.
 .sp
 This parameter should specify the path to a script that can set quota for the specified arguments.
+\./configure \-\-with\-quotas
+was used and a working quota api was found in the system\. Most packages are configured with these options already\.
+.sp
+This parameter should specify the path to a script that can set quota for the specified arguments\.
 .sp
 The specified script should take the following arguments:
+.RS 3n
+.TP 3n
+\(bu
+- quota type
+.RS 3n
+.TP 3n
+\(bu
+- user quotas
+.TP 3n
+\(bu
+- user default quotas (uid = -1)
+.TP 3n
+\(bu
+- group quotas
+.TP 3n
+\(bu
+- group default quotas (gid = -1)
+.RE
+.IP "" 3n
+.TP 3n
+\(bu
+- id (uid for user, gid for group, -1 if N/A)
+.TP 3n
+\(bu
+- quota state (0 = disable, 1 = enable, 2 = enable and enforce)
+.TP 3n
+\(bu
+- block softlimit
+.TP 3n
+\(bu
+- block hardlimit
+.TP 3n
+\(bu
+- inode softlimit
+.TP 3n
+\(bu
+- inode hardlimit
+.TP 3n
+\(bu
+(optional) - block size, defaults to 1024
+.RE
+.IP "" 3n
+The script should output at least one line of data on success. And nothing on failure.
+.sp
+Default:
+\fB\fIset quota command\fR = \fR
+.sp
+Example:
+\fB\fIset quota command\fR = /usr/local/sbin/set_quota \fR
+.RE
+.PP
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\- quota type
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\- user quotas
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\- user default quotas (uid = \-1)
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\- group quotas
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\- group default quotas (gid = \-1)
+.sp
+.RE
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\- id (uid for user, gid for group, \-1 if N/A)
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\- quota state (0 = disable, 1 = enable, 2 = enable and enforce)
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\- block softlimit
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\- block hardlimit
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\- inode softlimit
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\- inode hardlimit
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+(optional) \- block size, defaults to 1024
+.sp
+.RE
+The script should output at least one line of data on success\. And nothing on failure\.
+.sp
+Default:
+\fI\fIset quota command\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fIset quota command\fR\fR\fI = \fR\fI/usr/local/sbin/set_quota\fR\fI \fR
+.RE
 share modes (S)
+.RS 3n
+.PP
+.RS 4
 This enables or disables the honoring of the
 \fIshare modes\fR
 during a file open. These modes are used by clients to gain exclusive read or write access to a file.
 .sp
 These open modes are not directly supported by UNIX, so they are simulated using shared memory, or lock files if your UNIX doesn't support shared memory (almost all do).
+during a file open\. These modes are used by clients to gain exclusive read or write access to a file\.
+.sp
+These open modes are not directly supported by UNIX, so they are simulated using shared memory, or lock files if your UNIX doesn\'t support shared memory (almost all do)\.
 .sp
 The share modes that are enabled by this option are
 …
 \fBDENY_NONE\fR
 and
 \fBDENY_FCB\fR.
 .sp
 This option gives full share compatibility and enabled by default.
+\fBDENY_FCB\fR\.
+.sp
+This option gives full share compatibility and enabled by default\.
 .sp
 You should
 \fBNEVER\fR
 turn this parameter off as many Windows applications will break if you do so.
 .sp
 Default:
 \fB\fIshare modes\fR = yes \fR
 .RE
+.PP
+\fINEVER\fR
+turn this parameter off as many Windows applications will break if you do so\.
+.sp
+Default:
+\fI\fIshare modes\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 short preserve case (S)
+.RS 3n
+This boolean parameter controls if new files 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 use with
+preserve case = yes to permit long filenames to retain their case, while short names are lowered.
+.PP
+.RS 4
+This boolean parameter controls if new files 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
+\fIdefault case\fR\. This option can be use with
+\fIpreserve case = yes\fR
+to permit long filenames to retain their case, while short names are lowered\.
 .sp
 See the section on
 NAME MANGLING.
 .sp
 Default:
 \fB\fIshort preserve case\fR = yes \fR
 .RE
+.PP
+NAME MANGLING\.
+.sp
+Default:
+\fI\fIshort preserve case\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 show add printer wizard (G)
+.RS 3n
+With the introduction of MS-RPC based printing support for Windows NT/2000 client in Samba 2.2, a "Printers..." folder will appear on Samba hosts in the share listing. Normally this folder will contain an icon for the MS Add Printer Wizard (APW). However, it is possible to disable this feature regardless of the level of privilege of the connected user.
+.sp
+Under normal circumstances, the Windows NT/2000 client will open a handle on the printer server with OpenPrinterEx() asking for Administrator privileges. If the user does not have administrative access on the print server (i.e is not root or a member of the
+.PP
+.RS 4
+With the introduction of MS\-RPC based printing support for Windows NT/2000 client in Samba 2\.2, a "Printers\.\.\." folder will appear on Samba hosts in the share listing\. Normally this folder will contain an icon for the MS Add Printer Wizard (APW)\. However, it is possible to disable this feature regardless of the level of privilege of the connected user\.
+.sp
+Under normal circumstances, the Windows NT/2000 client will open a handle on the printer server with OpenPrinterEx() asking for Administrator privileges\. If the user does not have administrative access on the print server (i\.e is not root or a member of the
 \fIprinter admin\fR
 group), the OpenPrinterEx() call fails and the client makes another open call with a request for a lower privilege level. This should succeed, however the APW icon will not be displayed.
+group), the OpenPrinterEx() call fails and the client makes another open call with a request for a lower privilege level\. This should succeed, however the APW icon will not be displayed\.
 .sp
 Disabling the
 \fIshow add printer wizard\fR
 parameter will always cause the OpenPrinterEx() on the server to fail. Thus the APW icon will never be displayed.
+parameter will always cause the OpenPrinterEx() on the server to fail\. Thus the APW icon will never be displayed\.
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBNote\fR
+This does not prevent the same user from having administrative privilege on an individual printer.
+Default:
+\fB\fIshow add printer wizard\fR = yes \fR
+.RE
+.PP
+Note
+This does not prevent the same user from having administrative privilege on an individual printer\.
+Default:
+\fI\fIshow add printer wizard\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 shutdown script (G)
+.RS 3n
+.PP
+.RS 4
 This a full path name to a script called by
 \fBsmbd\fR(8)
 that should start a shutdown procedure.
+that should start a shutdown procedure\.
 .sp
 If the connected user posseses the
 \fBSeRemoteShutdownPrivilege\fR, right, this command will be run as user.
+\fBSeRemoteShutdownPrivilege\fR, right, this command will be run as user\.
 .sp
 The %z %t %r %f variables are expanded as follows:
+.RS 3n
+.TP 3n
+\(bu
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fI%z\fR
+will be substituted with the shutdown message sent to the server.
+.TP 3n
+\(bu
+will be substituted with the shutdown message sent to the server\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fI%t\fR
+will be substituted with the number of seconds to wait before effectively starting the shutdown procedure.
+.TP 3n
+\(bu
+will be substituted with the number of seconds to wait before effectively starting the shutdown procedure\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fI%r\fR
 will be substituted with the switch
+\fB-r\fR. It means reboot after shutdown for NT.
+.TP 3n
+\(bu
+\fI\-r\fR\. It means reboot after shutdown for NT\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fI%f\fR
 will be substituted with the switch
 \fB-f\fR. It means force the shutdown even if applications do not respond for NT.
 .RE
 .IP "" 3n
+\fI\-f\fR\. It means force the shutdown even if applications do not respond for NT\.
+.sp
+.RE
 Shutdown script example:
+.sp
+.sp
+.RS 4
 .nf
 #!/bin/bash
 …
 /sbin/shutdown $3 $4 +$time $1 &
 .fi
+Shutdown does not return so we need to launch it in background.
+.sp
+Default:
+\fB\fIshutdown script\fR = \fR
+.sp
+Example:
+\fB\fIshutdown script\fR = /usr/local/samba/sbin/shutdown %m %t %r %f \fR
+.RE
+.PP
+.RE
+.sp
+Shutdown does not return so we need to launch it in background\.
+.sp
+Default:
+\fI\fIshutdown script\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fIshutdown script\fR\fR\fI = \fR\fI/usr/local/samba/sbin/shutdown %m %t %r %f\fR\fI \fR
+.RE
 smb passwd file (G)
+.RS 3n
+This option sets the path to the encrypted smbpasswd file. By default the path to the smbpasswd file is compiled into Samba.
+.PP
+.RS 4
+This option sets the path to the encrypted smbpasswd file\. By default the path to the smbpasswd file is compiled into Samba\.
 .sp
 An example of use is:
+.sp
+.sp
+.RS 4
 .nf
 smb passwd file = /etc/samba/smbpasswd
 .fi
+.sp
+Default:
+\fB\fIsmb passwd file\fR = ${prefix}/private/smbpasswd \fR
+.RE
+.PP
+.RE
+.sp
+.sp
+Default:
+\fI\fIsmb passwd file\fR\fR\fI = \fR\fI${prefix}/private/smbpasswd\fR\fI \fR
+.RE
 smb ports (G)
+.RS 3n
+Specifies which ports the server should listen on for SMB traffic.
+.sp
+Default:
+\fB\fIsmb ports\fR = 445 139 \fR
+.RE
+.PP
+.PP
+.RS 4
+Specifies which ports the server should listen on for SMB traffic\.
+.sp
+Default:
+\fI\fIsmb ports\fR\fR\fI = \fR\fI445 139\fR\fI \fR
+.RE
 socket address (G)
+.RS 3n
+This option allows you to control what address Samba will listen for connections on. This is used to support multiple virtual interfaces on the one server, each with a different configuration.
+.sp
+By default Samba will accept connections on any address.
+.sp
+Default:
+\fB\fIsocket address\fR = \fR
+.sp
+Example:
+\fB\fIsocket address\fR = 192.168.2.20 \fR
+.RE
+.PP
+.PP
+.RS 4
+This option allows you to control what address Samba will listen for connections on\. This is used to support multiple virtual interfaces on the one server, each with a different configuration\.
+.sp
+By default Samba will accept connections on any address\.
+.sp
+Default:
+\fI\fIsocket address\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fIsocket address\fR\fR\fI = \fR\fI192\.168\.2\.20\fR\fI \fR
+.RE
 socket options (G)
+.RS 3n
+This option allows you to set socket options to be used when talking with the client.
+.sp
+Socket options are controls on the networking layer of the operating systems which allow the connection to be tuned.
+.sp
+This option will typically be used to tune your Samba server for optimal performance for your local network. There is no way that Samba can know what the optimal parameters are for your net, so you must experiment and choose them yourself. We strongly suggest you read the appropriate documentation for your operating system first (perhaps
+.PP
+.RS 4
+This option allows you to set socket options to be used when talking with the client\.
+.sp
+Socket options are controls on the networking layer of the operating systems which allow the connection to be tuned\.
+.sp
+This option will typically be used to tune your Samba server for optimal performance for your local network\. There is no way that Samba can know what the optimal parameters are for your net, so you must experiment and choose them yourself\. We strongly suggest you read the appropriate documentation for your operating system first (perhaps
 man setsockopt
 will help).
 .sp
 You may find that on some systems Samba will say "Unknown socket option" when you supply an option. This means you either incorrectly typed it or you need to add an include file to includes.h for your OS. If the latter is the case please send the patch to
 samba-technical@samba.org.
 .sp
 Any of the supported socket options may be combined in any way you like, as long as your OS allows it.
+will help)\.
+.sp
+You may find that on some systems Samba will say "Unknown socket option" when you supply an option\. This means you either incorrectly typed it or you need to add an include file to includes\.h for your OS\. If the latter is the case please send the patch to
+samba\-technical@samba\.org\.
+.sp
+Any of the supported socket options may be combined in any way you like, as long as your OS allows it\.
 .sp
 This is the list of socket options currently settable using this option:
+.RS 3n
+.TP 3n
+\(bu
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 SO_KEEPALIVE
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 SO_REUSEADDR
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 SO_BROADCAST
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 TCP_NODELAY
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 IPTOS_LOWDELAY
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 IPTOS_THROUGHPUT
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 SO_SNDBUF *
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 SO_RCVBUF *
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 SO_SNDLOWAT *
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 SO_RCVLOWAT *
 .RE
 .IP "" 3n
+.sp
+.RE
 Those marked with a
 \fB'*'\fR
 take an integer argument. The others can optionally take a 1 or 0 argument to enable or disable the option, by default they will be enabled if you don't specify 1 or 0.
+\fI\'*\'\fR
+take an integer argument\. The others can optionally take a 1 or 0 argument to enable or disable the option, by default they will be enabled if you don\'t specify 1 or 0\.
 .sp
 To specify an argument use the syntax SOME_OPTION = VALUE for example
 SO_SNDBUF = 8192. Note that you must not have any spaces before or after the = sign.
+SO_SNDBUF = 8192\. Note that you must not have any spaces before or after the = sign\.
 .sp
 If you are on a local network then a sensible option might be:
 …
 socket options = IPTOS_LOWDELAY TCP_NODELAY
 .sp
 If you are on a wide area network then perhaps try setting IPTOS_THROUGHPUT.
 .sp
 Note that several of the options may cause your Samba server to fail completely. Use these options with caution!
 .sp
 Default:
 \fB\fIsocket options\fR = TCP_NODELAY \fR
 .sp
 Example:
 \fB\fIsocket options\fR = IPTOS_LOWDELAY \fR
 .RE
+.PP
+If you are on a wide area network then perhaps try setting IPTOS_THROUGHPUT\.
+.sp
+Note that several of the options may cause your Samba server to fail completely\. Use these options with caution!
+.sp
+Default:
+\fI\fIsocket options\fR\fR\fI = \fR\fITCP_NODELAY\fR\fI \fR
+.sp
+Example:
+\fI\fIsocket options\fR\fR\fI = \fR\fIIPTOS_LOWDELAY\fR\fI \fR
+.RE
 stat cache (G)
+.RS 3n
+.PP
+.RS 4
 This parameter determines if
 \fBsmbd\fR(8)
 will use a cache in order to speed up case insensitive name mappings. You should never need to change this parameter.
 .sp
 Default:
 \fB\fIstat cache\fR = yes \fR
 .RE
+.PP
+will use a cache in order to speed up case insensitive name mappings\. You should never need to change this parameter\.
+.sp
+Default:
+\fI\fIstat cache\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 store dos attributes (S)
+.RS 3n
+If this parameter is set Samba attempts to first read DOS attributes (SYSTEM, HIDDEN, ARCHIVE or READ-ONLY) from a filesystem extended attribute, before mapping DOS attributes to UNIX permission bits (such as occurs with
+map hidden and
+map readonly). When set, DOS attributes will be stored onto an extended attribute in the UNIX filesystem, associated with the file or directory. For no other mapping to occur as a fall-back, the parameters
+map hidden,
+map system,
+map archive and
+map readonly must be set to off. This parameter writes the DOS attributes as a string into the extended attribute named "user.DOSATTRIB". This extended attribute is explicitly hidden from smbd clients requesting an EA list. 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:
+\fB\fIstore dos attributes\fR = no \fR
+.RE
+.PP
+.PP
+.RS 4
+If this parameter is set Samba attempts to first read DOS attributes (SYSTEM, HIDDEN, ARCHIVE or READ\-ONLY) from a filesystem extended attribute, before mapping DOS attributes to UNIX permission bits (such as occurs with
+\fImap hidden\fR
+and
+\fImap readonly\fR)\. When set, DOS attributes will be stored onto an extended attribute in the UNIX filesystem, associated with the file or directory\. For no other mapping to occur as a fall\-back, the parameters
+\fImap hidden\fR,
+\fImap system\fR,
+\fImap archive\fR
+and
+\fImap readonly\fR
+must be set to off\. This parameter writes the DOS attributes as a string into the extended attribute named "user\.DOSATTRIB"\. This extended attribute is explicitly hidden from smbd clients requesting an EA list\. 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\fIstore dos attributes\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 strict allocate (S)
+.RS 3n
+This is a boolean that controls the handling of disk space allocation in the server. When this is set to
+.PP
+.RS 4
+This is a boolean that controls the handling of disk space allocation in the server\. When this is set to
 \fByes\fR
 the server will change from UNIX behaviour of not committing real disk storage blocks when a file is extended to the Windows behaviour of actually forcing the disk system to allocate real storage blocks when a file is created or extended to be a given size. In UNIX terminology this means that Samba will stop creating sparse files. This can be slow on some systems.
+the server will change from UNIX behaviour of not committing real disk storage blocks when a file is extended to the Windows behaviour of actually forcing the disk system to allocate real storage blocks when a file is created or extended to be a given size\. In UNIX terminology this means that Samba will stop creating sparse files\. This can be slow on some systems\.
 .sp
 When strict allocate is
 \fBno\fR
 the server does sparse disk block allocation when a file is extended.
+the server does sparse disk block allocation when a file is extended\.
 .sp
 Setting this to
 \fByes\fR
 can help Samba return out of quota messages on systems that are restricting the disk quota of users.
 .sp
 Default:
 \fB\fIstrict allocate\fR = no \fR
 .RE
+.PP
+can help Samba return out of quota messages on systems that are restricting the disk quota of users\.
+.sp
+Default:
+\fI\fIstrict allocate\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 strict locking (S)
+.RS 3n
+This is an enumerated type that controls the handling of file locking in the server. When this is set to
+\fByes\fR, the server will check every read and write access for file locks, and deny access if locks exist. This can be slow on some systems.
+.sp
+When strict locking is set to Auto (the default), the server performs file lock checks only on non-oplocked files. As most Windows redirectors perform file locking checks locally on oplocked files this is a good trade off for inproved performance.
+.sp
+When strict locking is disabled, the server performs file lock checks only when the client explicitly asks for them.
+.sp
+Well-behaved clients always ask for lock checks when it is important. So in the vast majority of cases,
+.PP
+.RS 4
+This is an enumerated type that controls the handling of file locking in the server\. When this is set to
+\fByes\fR, the server will check every read and write access for file locks, and deny access if locks exist\. This can be slow on some systems\.
+.sp
+When strict locking is set to Auto (the default), the server performs file lock checks only on non\-oplocked files\. As most Windows redirectors perform file locking checks locally on oplocked files this is a good trade off for inproved performance\.
+.sp
+When strict locking is disabled, the server performs file lock checks only when the client explicitly asks for them\.
+.sp
+Well\-behaved clients always ask for lock checks when it is important\. So in the vast majority of cases,
 strict locking = Auto
 or
 strict locking = no
 is acceptable.
 .sp
 Default:
 \fB\fIstrict locking\fR = Auto \fR
 .RE
+.PP
+is acceptable\.
+.sp
+Default:
+\fI\fIstrict locking\fR\fR\fI = \fR\fIAuto\fR\fI \fR
+.RE
 strict sync (S)
+.RS 3n
+Many Windows applications (including the Windows 98 explorer shell) seem to confuse flushing buffer contents to disk with doing a sync to disk. Under UNIX, a sync call forces the process to be suspended until the kernel has ensured that all outstanding data in kernel disk buffers has been safely stored onto stable storage. This is very slow and should only be done rarely. Setting this parameter to
+.PP
+.RS 4
+Many Windows applications (including the Windows 98 explorer shell) seem to confuse flushing buffer contents to disk with doing a sync to disk\. Under UNIX, a sync call forces the process to be suspended until the kernel has ensured that all outstanding data in kernel disk buffers has been safely stored onto stable storage\. This is very slow and should only be done rarely\. Setting this parameter to
 \fBno\fR
 (the default) means that
 \fBsmbd\fR(8)
 ignores the Windows applications requests for a sync call. There is only a possibility of losing data if the operating system itself that Samba is running on crashes, so there is little danger in this default setting. In addition, this fixes many performance problems that people have reported with the new Windows98 explorer shell file copies.
 .sp
 Default:
 \fB\fIstrict sync\fR = no \fR
 .RE
+.PP
+ignores the Windows applications requests for a sync call\. There is only a possibility of losing data if the operating system itself that Samba is running on crashes, so there is little danger in this default setting\. In addition, this fixes many performance problems that people have reported with the new Windows98 explorer shell file copies\.
+.sp
+Default:
+\fI\fIstrict sync\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 svcctl list (G)
+.RS 3n
+This option defines a list of init scripts that smbd will use for starting and stopping Unix services via the Win32 ServiceControl API. This allows Windows administrators to utilize the MS Management Console plug-ins to manage a Unix server running Samba.
+.PP
+.RS 4
+This option defines a list of init scripts that smbd will use for starting and stopping Unix services via the Win32 ServiceControl API\. This allows Windows administrators to utilize the MS Management Console plug\-ins to manage a Unix server running Samba\.
 .sp
 The administrator must create a directory name
 \fIsvcctl\fR
 in Samba's $(libdir) and create symbolic links to the init scripts in
 \fI/etc/init.d/\fR. The name of the links must match the names given as part of the
 \fIsvcctl list\fR.
 .sp
 Default:
 \fB\fIsvcctl list\fR = \fR
 .sp
 Example:
 \fB\fIsvcctl list\fR = cups postfix portmap httpd \fR
 .RE
+.PP
+in Samba\'s $(libdir) and create symbolic links to the init scripts in
+\fI/etc/init\.d/\fR\. The name of the links must match the names given as part of the
+\fIsvcctl list\fR\.
+.sp
+Default:
+\fI\fIsvcctl list\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fIsvcctl list\fR\fR\fI = \fR\fIcups postfix portmap httpd\fR\fI \fR
+.RE
 sync always (S)
+.RS 3n
+This is a boolean parameter that controls whether writes will always be written to stable storage before the write call returns. If this is
+.PP
+.RS 4
+This is a boolean parameter that controls whether writes will always be written to stable storage before the write call returns\. If this is
 \fBno\fR
 then the server will be guided by the client's request in each write call (clients can set a bit indicating that a particular write should be synchronous). If this is
+then the server will be guided by the client\'s request in each write call (clients can set a bit indicating that a particular write should be synchronous)\. If this is
 \fByes\fR
 then every write will be followed by a
 fsync()
 call to ensure the data is written to disk. Note that the
+call to ensure the data is written to disk\. Note that the
 \fIstrict sync\fR
 parameter must be set to
 \fByes\fR
+in order for this parameter to have any affect.
+.sp
+Default:
+\fB\fIsync always\fR = no \fR
+.RE
+.PP
+in order for this parameter to have any affect\.
+.sp
+Default:
+\fI\fIsync always\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
+syslog only (G)
+.PP
+.RS 4
+If this parameter is set then Samba debug messages are logged into the system syslog only, and not to the debug log files\. There still will be some logging to log\.[sn]mbd even if
+\fIsyslog only\fR
+is enabled\.
+.sp
+Default:
+\fI\fIsyslog only\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 syslog (G)
+.RS 3n
+This parameter maps how Samba debug messages are logged onto the system syslog logging levels. Samba debug level zero maps onto syslog
+.PP
+.RS 4
+This parameter maps how Samba debug messages are logged onto the system syslog logging levels\. Samba debug level zero maps onto syslog
 \fBLOG_ERR\fR, debug level one maps onto
 \fBLOG_WARNING\fR, debug level two maps onto
+\fBLOG_NOTICE\fR, debug level three maps onto LOG_INFO. All higher levels are mapped to
+\fBLOG_DEBUG\fR.
+.sp
+This parameter sets the threshold for sending messages to syslog. Only messages with debug level less than this value will be sent to syslog.
+.sp
+Default:
+\fB\fIsyslog\fR = 1 \fR
+.RE
+.PP
+syslog only (G)
+.RS 3n
+If this parameter is set then Samba debug messages are logged into the system syslog only, and not to the debug log files.
+.sp
+Default:
+\fB\fIsyslog only\fR = no \fR
+.RE
+.PP
+\fBLOG_NOTICE\fR, debug level three maps onto LOG_INFO\. All higher levels are mapped to
+\fBLOG_DEBUG\fR\.
+.sp
+This parameter sets the threshold for sending messages to syslog\. Only messages with debug level less than this value will be sent to syslog\. There still will be some logging to log\.[sn]mbd even if
+\fIsyslog only\fR
+is enabled\.
+.sp
+Default:
+\fI\fIsyslog\fR\fR\fI = \fR\fI1\fR\fI \fR
+.RE
 template homedir (G)
+.RS 3n
+.PP
+.RS 4
 When filling out the user information for a Windows NT user, the
 \fBwinbindd\fR(8)
 daemon uses this parameter to fill in the home directory for that user. If the string
+daemon uses this parameter to fill in the home directory for that user\. If the string
 \fI%D\fR
 is present it is substituted with the user's Windows NT domain name. If the string
+is present it is substituted with the user\'s Windows NT domain name\. If the string
 \fI%U\fR
 is present it is substituted with the user's Windows NT user name.
 .sp
 Default:
 \fB\fItemplate homedir\fR = /home/%D/%U \fR
 .RE
+.PP
+is present it is substituted with the user\'s Windows NT user name\.
+.sp
+Default:
+\fI\fItemplate homedir\fR\fR\fI = \fR\fI/home/%D/%U\fR\fI \fR
+.RE
 template shell (G)
+.RS 3n
+.PP
+.RS 4
 When filling out the user information for a Windows NT user, the
 \fBwinbindd\fR(8)
 daemon uses this parameter to fill in the login shell for that user.
 .sp
 \fBNo default\fR
 .RE
+.PP
+daemon uses this parameter to fill in the login shell for that user\.
+.sp
+\fINo default\fR
+.RE
 time offset (G)
+.RS 3n
+This parameter is a setting in minutes to add to the normal GMT to local time conversion. This is useful if you are serving a lot of PCs that have incorrect daylight saving time handling.
+.sp
+Default:
+\fB\fItime offset\fR = 0 \fR
+.sp
+Example:
+\fB\fItime offset\fR = 60 \fR
+.RE
+.PP
+.PP
+.RS 4
+This parameter is a setting in minutes to add to the normal GMT to local time conversion\. This is useful if you are serving a lot of PCs that have incorrect daylight saving time handling\.
+.sp
+Default:
+\fI\fItime offset\fR\fR\fI = \fR\fI0\fR\fI \fR
+.sp
+Example:
+\fI\fItime offset\fR\fR\fI = \fR\fI60\fR\fI \fR
+.RE
 time server (G)
+.RS 3n
+.PP
+.RS 4
 This parameter determines if
 \fBnmbd\fR(8)
 advertises itself as a time server to Windows clients.
 .sp
 Default:
 \fB\fItime server\fR = no \fR
 .RE
+.PP
+advertises itself as a time server to Windows clients\.
+.sp
+Default:
+\fI\fItime server\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 unix charset (G)
+.RS 3n
+Specifies the charset the unix machine Samba runs on uses. Samba needs to know this in order to be able to convert text to the charsets other SMB clients use.
+.sp
+This is also the charset Samba will use when specifying arguments to scripts that it invokes.
+.sp
+Default:
+\fB\fIunix charset\fR = UTF8 \fR
+.sp
+Example:
+\fB\fIunix charset\fR = ASCII \fR
+.RE
+.PP
+.PP
+.RS 4
+Specifies the charset the unix machine Samba runs on uses\. Samba needs to know this in order to be able to convert text to the charsets other SMB clients use\.
+.sp
+This is also the charset Samba will use when specifying arguments to scripts that it invokes\.
+.sp
+Default:
+\fI\fIunix charset\fR\fR\fI = \fR\fIUTF8\fR\fI \fR
+.sp
+Example:
+\fI\fIunix charset\fR\fR\fI = \fR\fIASCII\fR\fI \fR
+.RE
 unix extensions (G)
+.RS 3n
+This boolean parameter controls whether Samba implments the CIFS UNIX extensions, as defined by HP. These extensions enable Samba to better serve UNIX CIFS clients by supporting features such as symbolic links, hard links, etc... These extensions require a similarly enabled client, and are of no current use to Windows clients.
+.sp
+Default:
+\fB\fIunix extensions\fR = yes \fR
+.RE
+.PP
+.PP
+.RS 4
+This boolean parameter controls whether Samba implments the CIFS UNIX extensions, as defined by HP\. These extensions enable Samba to better serve UNIX CIFS clients by supporting features such as symbolic links, hard links, etc\.\.\. These extensions require a similarly enabled client, and are of no current use to Windows clients\.
+.sp
+Default:
+\fI\fIunix extensions\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 unix password sync (G)
+.RS 3n
+This boolean parameter controls whether Samba attempts to synchronize the UNIX password with the SMB password when the encrypted SMB password in the smbpasswd file is changed. If this is set to
+.PP
+.RS 4
+This boolean parameter controls whether Samba attempts to synchronize the UNIX password with the SMB password when the encrypted SMB password in the smbpasswd file is changed\. If this is set to
 \fByes\fR
 the program specified in the
 \fIpasswd program\fRparameter is called
 \fBAS ROOT\fR
 - to allow the new UNIX password to be set without access to the old UNIX password (as the SMB password change code has no access to the old password cleartext, only the new).
 .sp
 Default:
 \fB\fIunix password sync\fR = no \fR
 .RE
+.PP
+\fIAS ROOT\fR
+\- to allow the new UNIX password to be set without access to the old UNIX password (as the SMB password change code has no access to the old password cleartext, only the new)\.
+.sp
+Default:
+\fI\fIunix password sync\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 update encrypted (G)
+.RS 3n
+This boolean parameter allows a user logging on with a plaintext password to have their encrypted (hashed) password in the smbpasswd file to be updated automatically as they log on. This option allows a site to migrate from plaintext password authentication (users authenticate with plaintext password over the wire, and are checked against a UNIX account atabase) to encrypted password authentication (the SMB challenge/response authentication mechanism) without forcing all users to re-enter their passwords via smbpasswd at the time the change is made. This is a convenience option to allow the change over to encrypted passwords to be made over a longer period. Once all users have encrypted representations of their passwords in the smbpasswd file this parameter should be set to
+\fBno\fR.
+.PP
+.RS 4
+This boolean parameter allows a user logging on with a plaintext password to have their encrypted (hashed) password in the smbpasswd file to be updated automatically as they log on\. This option allows a site to migrate from plaintext password authentication (users authenticate with plaintext password over the wire, and are checked against a UNIX account atabase) to encrypted password authentication (the SMB challenge/response authentication mechanism) without forcing all users to re\-enter their passwords via smbpasswd at the time the change is made\. This is a convenience option to allow the change over to encrypted passwords to be made over a longer period\. Once all users have encrypted representations of their passwords in the smbpasswd file this parameter should be set to
+\fBno\fR\.
 .sp
 In order for this parameter to be operative the
+encrypt passwords parameter must be set to
+\fBno\fR. The default value of
+encrypt passwords = Yes. Note: This must be set to
+\fIencrypt passwords\fR
+parameter must be set to
+\fBno\fR\. The default value of
+\fIencrypt passwords = Yes\fR\. Note: This must be set to
 \fBno\fR
 for this
+update encrypted to work.
+\fIupdate encrypted\fR
+to work\.
 .sp
 Note that even when this parameter is set a user authenticating to
 smbd
 must still enter a valid password in order to connect correctly, and to update their hashed (smbpasswd) passwords.
 .sp
 Default:
 \fB\fIupdate encrypted\fR = no \fR
 .RE
+.PP
+must still enter a valid password in order to connect correctly, and to update their hashed (smbpasswd) passwords\.
+.sp
+Default:
+\fI\fIupdate encrypted\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 use client driver (S)
+.RS 3n
+This parameter applies only to Windows NT/2000 clients. It has no effect on Windows 95/98/ME clients. When serving a printer to Windows NT/2000 clients without first installing a valid printer driver on the Samba host, the client will be required to install a local printer driver. From this point on, the client will treat the print as a local printer and not a network printer connection. This is much the same behavior that will occur when
+disable spoolss = yes.
+.sp
+The differentiating factor is that under normal circumstances, the NT/2000 client will attempt to open the network printer using MS-RPC. The problem is that because the client considers the printer to be local, it will attempt to issue the OpenPrinterEx() call requesting access rights associated with the logged on user. If the user possesses local administator rights but not root privilege on the Samba host (often the case), the OpenPrinterEx() call will fail. The result is that the client will now display an "Access Denied; Unable to connect" message in the printer queue window (even though jobs may successfully be printed).
+.sp
+If this parameter is enabled for a printer, then any attempt to open the printer with the PRINTER_ACCESS_ADMINISTER right is mapped to PRINTER_ACCESS_USE instead. Thus allowing the OpenPrinterEx() call to succeed.
+\fBThis parameter MUST not be able enabled on a print share which has valid print driver installed on the Samba server.\fR
+.sp
+Default:
+\fB\fIuse client driver\fR = no \fR
+.RE
+.PP
+.PP
+.RS 4
+This parameter applies only to Windows NT/2000 clients\. It has no effect on Windows 95/98/ME clients\. When serving a printer to Windows NT/2000 clients without first installing a valid printer driver on the Samba host, the client will be required to install a local printer driver\. From this point on, the client will treat the print as a local printer and not a network printer connection\. This is much the same behavior that will occur when
+disable spoolss = yes\.
+.sp
+The differentiating factor is that under normal circumstances, the NT/2000 client will attempt to open the network printer using MS\-RPC\. The problem is that because the client considers the printer to be local, it will attempt to issue the OpenPrinterEx() call requesting access rights associated with the logged on user\. If the user possesses local administator rights but not root privilege on the Samba host (often the case), the OpenPrinterEx() call will fail\. The result is that the client will now display an "Access Denied; Unable to connect" message in the printer queue window (even though jobs may successfully be printed)\.
+.sp
+If this parameter is enabled for a printer, then any attempt to open the printer with the PRINTER_ACCESS_ADMINISTER right is mapped to PRINTER_ACCESS_USE instead\. Thus allowing the OpenPrinterEx() call to succeed\.
+\fIThis parameter MUST not be able enabled on a print share which has valid print driver installed on the Samba server\.\fR
+.sp
+Default:
+\fI\fIuse client driver\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 use kerberos keytab (G)
+.RS 3n
+.PP
+.RS 4
 Specifies whether Samba should attempt to maintain service principals in the systems keytab file for
 \fBhost/FQDN\fR
 and
 \fBcifs/FQDN\fR.
+\fBcifs/FQDN\fR\.
 .sp
 When you are using the heimdal Kerberos libraries, you must also specify the following in
+\fI/etc/krb5.conf\fR:
+.sp
+\fI/etc/krb5\.conf\fR:
+.sp
+.RS 4
 .nf
 [libdefaults]
+default_keytab_name = FILE:/etc/krb5.keytab
+default_keytab_name = FILE:/etc/krb5\.keytab
 .fi
+.sp
+Default:
+\fB\fIuse kerberos keytab\fR = False \fR
+.RE
+.PP
+.RE
+.sp
+.sp
+Default:
+\fI\fIuse kerberos keytab\fR\fR\fI = \fR\fIFalse\fR\fI \fR
+.RE
 use mmap (G)
+.RS 3n
+This global parameter determines if the tdb internals of Samba can depend on mmap working correctly on the running system. Samba requires a coherent mmap/read-write system memory cache. Currently only HPUX does not have such a coherent cache, and so this parameter is set to
+.PP
+.RS 4
+This global parameter determines if the tdb internals of Samba can depend on mmap working correctly on the running system\. Samba requires a coherent mmap/read\-write system memory cache\. Currently only HPUX does not have such a coherent cache, and so this parameter is set to
 \fBno\fR
+by default on HPUX. On all other systems this parameter should be left alone. This parameter is provided to help the Samba developers track down problems with the tdb internal code.
+.sp
+Default:
+\fB\fIuse mmap\fR = yes \fR
+.RE
+.PP
+user
+.RS 3n
+This parameter is a synonym for username.
+.RE
+.PP
+users
+.RS 3n
+This parameter is a synonym for username.
+.RE
+.PP
+username (S)
+.RS 3n
+Multiple users may be specified in a comma-delimited list, in which case the supplied password will be tested against each username in turn (left to right).
+.sp
+The
+\fIusername\fR
+line is needed only when the PC is unable to supply its own username. This is the case for the COREPLUS protocol or where your users have different WfWg usernames to UNIX usernames. In both these cases you may also be better using the \\server\share%user syntax instead.
+.sp
+The
+\fIusername\fR
+line is not a great solution in many cases as it means Samba will try to validate the supplied password against each of the usernames in the
+\fIusername\fR
+line in turn. This is slow and a bad idea for lots of users in case of duplicate passwords. You may get timeouts or security breaches using this parameter unwisely.
+.sp
+Samba relies on the underlying UNIX security. This parameter does not restrict who can login, it just offers hints to the Samba server as to what usernames might correspond to the supplied password. Users can login as whoever they please and they will be able to do no more damage than if they started a telnet session. The daemon runs as the user that they log in as, so they cannot do anything that user cannot do.
+.sp
+To restrict a service to a particular set of users you can use the
+valid users parameter.
+.sp
+If any of the usernames begin with a '@' then the name will be looked up first in the NIS netgroups list (if Samba is compiled with netgroup support), followed by a lookup in the UNIX groups database and will expand to a list of all users in the group of that name.
+.sp
+If any of the usernames begin with a '+' then the name will be looked up only in the UNIX groups database and will expand to a list of all users in the group of that name.
+.sp
+If any of the usernames begin with a '&' then the name will be looked up only in the NIS netgroups database (if Samba is compiled with netgroup support) and will expand to a list of all users in the netgroup group of that name.
+.sp
+Note that searching though a groups database can take quite some time, and some clients may time out during the search.
+.sp
+See the section
+NOTE ABOUT USERNAME/PASSWORD VALIDATION
+for more information on how this parameter determines access to the services.
+.sp
+Default:
+\fB\fIusername\fR = # The guest account if a guest service, else <empty string>. \fR
+.sp
+Example:
+\fB\fIusername\fR = fred, mary, jack, jane, @users, @pcgroup \fR
+.RE
+.PP
+by default on HPUX\. On all other systems this parameter should be left alone\. This parameter is provided to help the Samba developers track down problems with the tdb internal code\.
+.sp
+Default:
+\fI\fIuse mmap\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 username level (G)
+.RS 3n
+This option helps Samba to try and 'guess' at the real UNIX username, as many DOS clients send an all-uppercase username. By default Samba tries all lowercase, followed by the username with the first letter capitalized, and fails if the username is not found on the UNIX machine.
+.sp
+If this parameter is set to non-zero the behavior changes. This parameter is a number that specifies the number of uppercase combinations to try while trying to determine the UNIX user name. The higher the number the more combinations will be tried, but the slower the discovery of usernames will be. Use this parameter when you have strange usernames on your UNIX machine, such as
+\fBAstrangeUser \fR.
+.sp
+This parameter is needed only on UNIX systems that have case sensitive usernames.
+.sp
+Default:
+\fB\fIusername level\fR = 0 \fR
+.sp
+Example:
+\fB\fIusername level\fR = 5 \fR
+.RE
+.PP
+.PP
+.RS 4
+This option helps Samba to try and \'guess\' at the real UNIX username, as many DOS clients send an all\-uppercase username\. By default Samba tries all lowercase, followed by the username with the first letter capitalized, and fails if the username is not found on the UNIX machine\.
+.sp
+If this parameter is set to non\-zero the behavior changes\. This parameter is a number that specifies the number of uppercase combinations to try while trying to determine the UNIX user name\. The higher the number the more combinations will be tried, but the slower the discovery of usernames will be\. Use this parameter when you have strange usernames on your UNIX machine, such as
+\fBAstrangeUser \fR\.
+.sp
+This parameter is needed only on UNIX systems that have case sensitive usernames\.
+.sp
+Default:
+\fI\fIusername level\fR\fR\fI = \fR\fI0\fR\fI \fR
+.sp
+Example:
+\fI\fIusername level\fR\fR\fI = \fR\fI5\fR\fI \fR
+.RE
+username map script (G)
+.PP
+.RS 4
+This script is a mutually exclusive alternative to the
+\fIusername map\fR
+parameter\. This parameter specifies and external program or script that must accept a single command line option (the username transmitted in the authentication request) and return a line line on standard output (the name to which the account should mapped)\. In this way, it is possible to store username map tables in an LDAP or NIS directory services\.
+.sp
+Default:
+\fI\fIusername map script\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fIusername map script\fR\fR\fI = \fR\fI/etc/samba/scripts/mapusers\.sh\fR\fI \fR
+.RE
 username map (G)
+.RS 3n
+This option allows you to specify a file containing a mapping of usernames from the clients to the server. This can be used for several purposes. The most common is to map usernames that users use on DOS or Windows machines to those that the UNIX box uses. The other is to map multiple users to a single username so that they can more easily share files.
+.sp
+Please note that for user or share mode security, the username map is applied prior to validating the user credentials. Domain member servers (domain or ads) apply the username map after the user has been successfully authenticated by the domain controller and require fully qualified enties in the map table (e.g. biddle = DOMAIN\foo).
+.sp
+The map file is parsed line by line. Each line should contain a single UNIX username on the left then a '=' followed by a list of usernames on the right. The list of usernames on the right may contain names of the form @group in which case they will match any UNIX username in that group. The special client name '*' is a wildcard and matches any name. Each line of the map file may be up to 1023 characters long.
+.sp
+The file is processed on each line by taking the supplied username and comparing it with each username on the right hand side of the '=' signs. If the supplied name matches any of the names on the right hand side then it is replaced with the name on the left. Processing then continues with the next line.
+.sp
+If any line begins with a '#' or a ';' then it is ignored.
+.sp
+If any line begins with an '!' then the processing will stop after that line if a mapping was done by the line. Otherwise mapping continues with every line being processed. Using '!' is most useful when you have a wildcard mapping line later in the file.
+.PP
+.RS 4
+This option allows you to specify a file containing a mapping of usernames from the clients to the server\. This can be used for several purposes\. The most common is to map usernames that users use on DOS or Windows machines to those that the UNIX box uses\. The other is to map multiple users to a single username so that they can more easily share files\.
+.sp
+Please note that for user or share mode security, the username map is applied prior to validating the user credentials\. Domain member servers (domain or ads) apply the username map after the user has been successfully authenticated by the domain controller and require fully qualified enties in the map table (e\.g\. biddle =
+DOMAIN\efoo)\.
+.sp
+The map file is parsed line by line\. Each line should contain a single UNIX username on the left then a \'=\' followed by a list of usernames on the right\. The list of usernames on the right may contain names of the form @group in which case they will match any UNIX username in that group\. The special client name \'*\' is a wildcard and matches any name\. Each line of the map file may be up to 1023 characters long\.
+.sp
+The file is processed on each line by taking the supplied username and comparing it with each username on the right hand side of the \'=\' signs\. If the supplied name matches any of the names on the right hand side then it is replaced with the name on the left\. Processing then continues with the next line\.
+.sp
+If any line begins with a \'#\' or a \';\' then it is ignored\.
+.sp
+If any line begins with an \'!\' then the processing will stop after that line if a mapping was done by the line\. Otherwise mapping continues with every line being processed\. Using \'!\' is most useful when you have a wildcard mapping line later in the file\.
 .sp
 For example to map from the name
 …
 \fB root\fR
 you would use:
+.sp
+.sp
+.RS 4
 .nf
 root = admin administrator
 .fi
+.RE
+.sp
 Or to map anyone in the UNIX group
 \fBsystem\fR
 …
 \fBsys\fR
 you would use:
+.sp
+.sp
+.RS 4
 .nf
 sys = @system
 .fi
+.sp
+You can have as many mappings as you like in a username map file.
+.RE
+.sp
+.sp
+You can have as many mappings as you like in a username map file\.
 .sp
 If your system supports the NIS NETGROUP option then the netgroup database is checked before the
 \fI/etc/group \fR
+database for matching groups.
+.sp
+You can map Windows usernames that have spaces in them by using double quotes around the name. For example:
+.sp
+database for matching groups\.
+.sp
+You can map Windows usernames that have spaces in them by using double quotes around the name\. For example:
+.sp
+.RS 4
 .nf
 tridge = "Andrew Tridgell"
 .fi
+would map the windows username "Andrew Tridgell" to the unix username "tridge".
+.sp
+The following example would map mary and fred to the unix user sys, and map the rest to guest. Note the use of the '!' to tell Samba to stop processing if it gets a match on that line:
+.sp
+.RE
+.sp
+would map the windows username "Andrew Tridgell" to the unix username "tridge"\.
+.sp
+The following example would map mary and fred to the unix user sys, and map the rest to guest\. Note the use of the \'!\' to tell Samba to stop processing if it gets a match on that line:
+.sp
+.RS 4
 .nf
 !sys = mary fred
 guest = *
 .fi
+.sp
+Note that the remapping is applied to all occurrences of usernames. Thus if you connect to \\server\fred and
+.RE
+.sp
+.sp
+Note that the remapping is applied to all occurrences of usernames\. Thus if you connect to \e\eserver\efred and
 \fBfred\fR
 is remapped to
 \fBmary\fR
 then you will actually be connecting to \\server\mary and will need to supply a password suitable for
+then you will actually be connecting to \e\eserver\emary and will need to supply a password suitable for
 \fBmary\fR
 not
+\fBfred\fR. The only exception to this is the username passed to the
+password server (if you have one). The password server will receive whatever username the client supplies without modification.
+.sp
+Also note that no reverse mapping is done. The main effect this has is with printing. Users who have been mapped may have trouble deleting print jobs as PrintManager under WfWg will think they don't own the print job.
+.sp
+Samba versions prior to 3.0.8 would only support reading the fully qualified username (e.g.: DOMAIN\user) from the username map when performing a kerberos login from a client. However, when looking up a map entry for a user authenticated by NTLM[SSP], only the login name would be used for matches. This resulted in inconsistent behavior sometimes even on the same server.
+.sp
+The following functionality is obeyed in version 3.0.8 and later:
+.sp
+When performing local authentication, the username map is applied to the login name before attempting to authenticate the connection.
+.sp
+When relying upon a external domain controller for validating authentication requests, smbd will apply the username map to the fully qualified username (i.e. DOMAIN\user) only after the user has been successfully authenticated.
+\fBfred\fR\. The only exception to this is the username passed to the
+\fIpassword server\fR
+(if you have one)\. The password server will receive whatever username the client supplies without modification\.
+.sp
+Also note that no reverse mapping is done\. The main effect this has is with printing\. Users who have been mapped may have trouble deleting print jobs as PrintManager under WfWg will think they don\'t own the print job\.
+.sp
+Samba versions prior to 3\.0\.8 would only support reading the fully qualified username (e\.g\.:
+DOMAIN\euser) from the username map when performing a kerberos login from a client\. However, when looking up a map entry for a user authenticated by NTLM[SSP], only the login name would be used for matches\. This resulted in inconsistent behavior sometimes even on the same server\.
+.sp
+The following functionality is obeyed in version 3\.0\.8 and later:
+.sp
+When performing local authentication, the username map is applied to the login name before attempting to authenticate the connection\.
+.sp
+When relying upon a external domain controller for validating authentication requests, smbd will apply the username map to the fully qualified username (i\.e\.
+DOMAIN\euser) only after the user has been successfully authenticated\.
 .sp
 An example of use is:
+.sp
+.sp
+.RS 4
 .nf
+username map = /usr/local/samba/lib/users.map
+username map = /usr/local/samba/lib/users\.map
 .fi
+.sp
+Default:
+\fB\fIusername map\fR = # no username map \fR
+.RE
+.PP
+username map script (G)
+.RS 3n
+This script is a mutually exclusive alternative to the
+username map parameter. This parameter specifies and external program or script that must accept a single command line option (the username transmitted in the authentication request) and return a line line on standard output (the name to which the account should mapped). In this way, it is possible to store username map tables in an LDAP or NIS directory services.
+.sp
+Default:
+\fB\fIusername map script\fR = \fR
+.sp
+Example:
+\fB\fIusername map script\fR = /etc/samba/scripts/mapusers.sh \fR
+.RE
+.PP
+.RE
+.sp
+.sp
+Default:
+\fI\fIusername map\fR\fR\fI = \fR\fI # no username map\fR\fI \fR
+.RE
+user.PP
+.RS 4
+This parameter is a synonym for
+username\.
+.RE
+users.PP
+.RS 4
+This parameter is a synonym for
+username\.
+.RE
+username (S)
+.PP
+.RS 4
+Multiple users may be specified in a comma\-delimited list, in which case the supplied password will be tested against each username in turn (left to right)\.
+.sp
+The
+\fIusername\fR
+line is needed only when the PC is unable to supply its own username\. This is the case for the COREPLUS protocol or where your users have different WfWg usernames to UNIX usernames\. In both these cases you may also be better using the \e\eserver\eshare%user syntax instead\.
+.sp
+The
+\fIusername\fR
+line is not a great solution in many cases as it means Samba will try to validate the supplied password against each of the usernames in the
+\fIusername\fR
+line in turn\. This is slow and a bad idea for lots of users in case of duplicate passwords\. You may get timeouts or security breaches using this parameter unwisely\.
+.sp
+Samba relies on the underlying UNIX security\. This parameter does not restrict who can login, it just offers hints to the Samba server as to what usernames might correspond to the supplied password\. Users can login as whoever they please and they will be able to do no more damage than if they started a telnet session\. The daemon runs as the user that they log in as, so they cannot do anything that user cannot do\.
+.sp
+To restrict a service to a particular set of users you can use the
+\fIvalid users\fR
+parameter\.
+.sp
+If any of the usernames begin with a \'@\' then the name will be looked up first in the NIS netgroups list (if Samba is compiled with netgroup support), followed by a lookup in the UNIX groups database and will expand to a list of all users in the group of that name\.
+.sp
+If any of the usernames begin with a \'+\' then the name will be looked up only in the UNIX groups database and will expand to a list of all users in the group of that name\.
+.sp
+If any of the usernames begin with a \'&\' then the name will be looked up only in the NIS netgroups database (if Samba is compiled with netgroup support) and will expand to a list of all users in the netgroup group of that name\.
+.sp
+Note that searching though a groups database can take quite some time, and some clients may time out during the search\.
+.sp
+See the section
+NOTE ABOUT USERNAME/PASSWORD VALIDATION
+for more information on how this parameter determines access to the services\.
+.sp
+Default:
+\fI\fIusername\fR\fR\fI = \fR\fI # The guest account if a guest service, else <empty string>\.\fR\fI \fR
+.sp
+Example:
+\fI\fIusername\fR\fR\fI = \fR\fIfred, mary, jack, jane, @users, @pcgroup\fR\fI \fR
+.RE
 usershare allow guests (G)
+.RS 3n
+This parameter controls whether user defined shares are allowed to be accessed by non-authenticated users or not. It is the equivalent of allowing people who can create a share the option of setting
+.PP
+.RS 4
+This parameter controls whether user defined shares are allowed to be accessed by non\-authenticated users or not\. It is the equivalent of allowing people who can create a share the option of setting
 \fIguest ok = yes\fR
 in a share definition. Due to the security sensitive nature of this the default is set to off.
 .sp
 Default:
 \fB\fIusershare allow guests\fR = no \fR
 .RE
+.PP
+in a share definition\. Due to the security sensitive nature of this the default is set to off\.
+.sp
+Default:
+\fI\fIusershare allow guests\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 usershare max shares (G)
+.RS 3n
+This parameter specifies the number of user defined shares that are allowed to be created by users belonging to the group owning the usershare directory. If set to zero (the default) user defined shares are ignored.
+.sp
+Default:
+\fB\fIusershare max shares\fR = 0 \fR
+.RE
+.PP
+.PP
+.RS 4
+This parameter specifies the number of user defined shares that are allowed to be created by users belonging to the group owning the usershare directory\. If set to zero (the default) user defined shares are ignored\.
+.sp
+Default:
+\fI\fIusershare max shares\fR\fR\fI = \fR\fI0\fR\fI \fR
+.RE
 usershare owner only (G)
+.RS 3n
+This parameter controls whether the pathname exported by a user defined shares must be owned by the user creating the user defined share or not. If set to True (the default) then smbd checks that the directory path being shared is owned by the user who owns the usershare file defining this share and refuses to create the share if not. If set to False then no such check is performed and any directory path may be exported regardless of who owns it.
+.sp
+Default:
+\fB\fIusershare owner only\fR = True \fR
+.RE
+.PP
+.PP
+.RS 4
+This parameter controls whether the pathname exported by a user defined shares must be owned by the user creating the user defined share or not\. If set to True (the default) then smbd checks that the directory path being shared is owned by the user who owns the usershare file defining this share and refuses to create the share if not\. If set to False then no such check is performed and any directory path may be exported regardless of who owns it\.
+.sp
+Default:
+\fI\fIusershare owner only\fR\fR\fI = \fR\fITrue\fR\fI \fR
+.RE
 usershare path (G)
 .RS 3n
+This parameter specifies the absolute path of the directory on the filesystem used to store the user defined share definition files. This directory must be owned by root, and have no access for other, and be writable only by the group owner. In addition the "sticky" bit must also be set, restricting rename and delete to owners of a file (in the same way the /tmp directory is usually configured). Members of the group owner of this directory are the users allowed to create usershares. If this parameter is undefined then no user defined shares are allowed.
+.sp
+For example, a valid usershare directory might be /usr/local/samba/lib/usershares, set up as follows.
+.sp
 .sp
+.PP
+.RS 4
+This parameter specifies the absolute path of the directory on the filesystem used to store the user defined share definition files\. This directory must be owned by root, and have no access for other, and be writable only by the group owner\. In addition the "sticky" bit must also be set, restricting rename and delete to owners of a file (in the same way the /tmp directory is usually configured)\. Members of the group owner of this directory are the users allowed to create usershares\. If this parameter is undefined then no user defined shares are allowed\.
+.sp
+For example, a valid usershare directory might be /usr/local/samba/lib/usershares, set up as follows\.
+.sp
+.sp
+.RS 4
 .nf
+        ls -ld /usr/local/samba/lib/usershares/
+        drwxrwx--T  2 root power_users 4096 2006-05-05 12:27 /usr/local/samba/lib/usershares/
+        ls \-ld /usr/local/samba/lib/usershares/
+        drwxrwx\-\-T  2 root power_users 4096 2006\-05\-05 12:27 /usr/local/samba/lib/usershares/
 .fi
+.sp
+In this case, only members of the group "power_users" can create user defined shares.
+.sp
+Default:
+\fB\fIusershare path\fR = NULL \fR
+.RE
+.PP
+.RE
+.sp
+.sp
+In this case, only members of the group "power_users" can create user defined shares\.
+.sp
+Default:
+\fI\fIusershare path\fR\fR\fI = \fR\fINULL\fR\fI \fR
+.RE
 usershare prefix allow list (G)
+.RS 3n
+This parameter specifies a list of absolute pathnames the root of which are allowed to be exported by user defined share definitions. If the pathname exported doesn't start with one of the strings in this list the user defined share will not be allowed. This allows the Samba administrator to restrict the directories on the system that can be exported by user defined shares.
+.sp
+If there is a "usershare prefix deny list" and also a "usershare prefix allow list" the deny list is processed first, followed by the allow list, thus leading to the most restrictive interpretation.
+.sp
+Default:
+\fB\fIusershare prefix allow list\fR = NULL \fR
+.sp
+Example:
+\fB\fIusershare prefix allow list\fR = /home /data /space \fR
+.RE
+.PP
+.PP
+.RS 4
+This parameter specifies a list of absolute pathnames the root of which are allowed to be exported by user defined share definitions\. If the pathname exported doesn\'t start with one of the strings in this list the user defined share will not be allowed\. This allows the Samba administrator to restrict the directories on the system that can be exported by user defined shares\.
+.sp
+If there is a "usershare prefix deny list" and also a "usershare prefix allow list" the deny list is processed first, followed by the allow list, thus leading to the most restrictive interpretation\.
+.sp
+Default:
+\fI\fIusershare prefix allow list\fR\fR\fI = \fR\fINULL\fR\fI \fR
+.sp
+Example:
+\fI\fIusershare prefix allow list\fR\fR\fI = \fR\fI/home /data /space\fR\fI \fR
+.RE
 usershare prefix deny list (G)
+.RS 3n
+This parameter specifies a list of absolute pathnames the root of which are NOT allowed to be exported by user defined share definitions. If the pathname exported starts with one of the strings in this list the user defined share will not be allowed. Any pathname not starting with one of these strings will be allowed to be exported as a usershare. This allows the Samba administrator to restrict the directories on the system that can be exported by user defined shares.
+.sp
+If there is a "usershare prefix deny list" and also a "usershare prefix allow list" the deny list is processed first, followed by the allow list, thus leading to the most restrictive interpretation.
+.sp
+Default:
+\fB\fIusershare prefix deny list\fR = NULL \fR
+.sp
+Example:
+\fB\fIusershare prefix deny list\fR = /etc /dev /private \fR
+.RE
+.PP
+.PP
+.RS 4
+This parameter specifies a list of absolute pathnames the root of which are NOT allowed to be exported by user defined share definitions\. If the pathname exported starts with one of the strings in this list the user defined share will not be allowed\. Any pathname not starting with one of these strings will be allowed to be exported as a usershare\. This allows the Samba administrator to restrict the directories on the system that can be exported by user defined shares\.
+.sp
+If there is a "usershare prefix deny list" and also a "usershare prefix allow list" the deny list is processed first, followed by the allow list, thus leading to the most restrictive interpretation\.
+.sp
+Default:
+\fI\fIusershare prefix deny list\fR\fR\fI = \fR\fINULL\fR\fI \fR
+.sp
+Example:
+\fI\fIusershare prefix deny list\fR\fR\fI = \fR\fI/etc /dev /private\fR\fI \fR
+.RE
 usershare template share (G)
+.RS 3n
+User defined shares only have limited possible parameters such as path, guest ok etc. This parameter allows usershares to "cloned" from an existing share. If "usershare template share" is set to the name of an existing share, then all usershares created have their defaults set from the parameters set on this share.
+.sp
+The target share may be set to be invalid for real file sharing by setting the parameter "-valid = False" on the template share definition. This causes it not to be seen as a real exported share but to be able to be used as a template for usershares.
+.sp
+Default:
+\fB\fIusershare template share\fR = NULL \fR
+.sp
+Example:
+\fB\fIusershare template share\fR = template_share \fR
+.RE
+.PP
+.PP
+.RS 4
+User defined shares only have limited possible parameters such as path, guest ok etc\. This parameter allows usershares to "cloned" from an existing share\. If "usershare template share" is set to the name of an existing share, then all usershares created have their defaults set from the parameters set on this share\.
+.sp
+The target share may be set to be invalid for real file sharing by setting the parameter "\-valid = False" on the template share definition\. This causes it not to be seen as a real exported share but to be able to be used as a template for usershares\.
+.sp
+Default:
+\fI\fIusershare template share\fR\fR\fI = \fR\fINULL\fR\fI \fR
+.sp
+Example:
+\fI\fIusershare template share\fR\fR\fI = \fR\fItemplate_share\fR\fI \fR
+.RE
 use sendfile (S)
+.RS 3n
+.PP
+.RS 4
 If this parameter is
 \fByes\fR, and the
 \fBsendfile()\fR
 system call is supported by the underlying operating system, then some SMB read calls (mainly ReadAndX and ReadRaw) will use the more efficient sendfile system call for files that are exclusively oplocked. This may make more efficient use of the system CPU's and cause Samba to be faster. Samba automatically turns this off for clients that use protocol levels lower than NT LM 0.12 and when it detects a client is Windows 9x (using sendfile from Linux will cause these clients to fail).
 .sp
 Default:
 \fB\fIuse sendfile\fR = false \fR
 .RE
+.PP
+system call is supported by the underlying operating system, then some SMB read calls (mainly ReadAndX and ReadRaw) will use the more efficient sendfile system call for files that are exclusively oplocked\. This may make more efficient use of the system CPU\'s and cause Samba to be faster\. Samba automatically turns this off for clients that use protocol levels lower than NT LM 0\.12 and when it detects a client is Windows 9x (using sendfile from Linux will cause these clients to fail)\.
+.sp
+Default:
+\fI\fIuse sendfile\fR\fR\fI = \fR\fIfalse\fR\fI \fR
+.RE
 use spnego (G)
+.RS 3n
+This variable controls controls whether samba will try to use Simple and Protected NEGOciation (as specified by rfc2478) with WindowsXP and Windows2000 clients to agree upon an authentication mechanism.
+.sp
+Unless further issues are discovered with our SPNEGO implementation, there is no reason this should ever be disabled.
+.sp
+Default:
+\fB\fIuse spnego\fR = yes \fR
+.RE
+.PP
+.PP
+.RS 4
+This variable controls controls whether samba will try to use Simple and Protected NEGOciation (as specified by rfc2478) with WindowsXP and Windows2000 clients to agree upon an authentication mechanism\.
+.sp
+Unless further issues are discovered with our SPNEGO implementation, there is no reason this should ever be disabled\.
+.sp
+Default:
+\fI\fIuse spnego\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
+utmp directory (G)
+.PP
+.RS 4
+This parameter is only available if Samba has been configured and compiled with the option
+\-\-with\-utmp\. It specifies a directory pathname that is used to store the utmp or utmpx files (depending on the UNIX system) that record user connections to a Samba server\. By default this is not set, meaning the system will use whatever utmp file the native system is set to use (usually
+\fI/var/run/utmp\fR
+on Linux)\.
+.sp
+Default:
+\fI\fIutmp directory\fR\fR\fI = \fR\fI # Determined automatically\fR\fI \fR
+.sp
+Example:
+\fI\fIutmp directory\fR\fR\fI = \fR\fI/var/run/utmp\fR\fI \fR
+.RE
 utmp (G)
+.RS 3n
+.PP
+.RS 4
 This boolean parameter is only available if Samba has been configured and compiled with the option
 --with-utmp. If set to
+\-\-with\-utmp\. If set to
 \fByes\fR
+then Samba will attempt to add utmp or utmpx records (depending on the UNIX system) whenever a connection is made to a Samba server. Sites may use this to record the user connecting to a Samba share.
+.sp
+Due to the requirements of the utmp record, we are required to create a unique identifier for the incoming user. Enabling this option creates an n^2 algorithm to find this number. This may impede performance on large installations.
+.sp
+Default:
+\fB\fIutmp\fR = no \fR
+.RE
+.PP
+utmp directory (G)
+.RS 3n
+This parameter is only available if Samba has been configured and compiled with the option
+--with-utmp. It specifies a directory pathname that is used to store the utmp or utmpx files (depending on the UNIX system) that record user connections to a Samba server. By default this is not set, meaning the system will use whatever utmp file the native system is set to use (usually
+\fI/var/run/utmp\fR
+on Linux).
+.sp
+Default:
+\fB\fIutmp directory\fR = # Determined automatically \fR
+.sp
+Example:
+\fB\fIutmp directory\fR = /var/run/utmp \fR
+.RE
+.PP
+-valid (S)
+.RS 3n
+This parameter indicates whether a share is valid and thus can be used. When this parameter is set to false, the share will be in no way visible nor accessible.
+.sp
+This option should not be used by regular users but might be of help to developers. Samba uses this option internally to mark shares as deleted.
+.sp
+Default:
+\fB\fI-valid\fR = yes \fR
+.RE
+.PP
+then Samba will attempt to add utmp or utmpx records (depending on the UNIX system) whenever a connection is made to a Samba server\. Sites may use this to record the user connecting to a Samba share\.
+.sp
+Due to the requirements of the utmp record, we are required to create a unique identifier for the incoming user\. Enabling this option creates an n^2 algorithm to find this number\. This may impede performance on large installations\.
+.sp
+Default:
+\fI\fIutmp\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 valid users (S)
+.RS 3n
+This is a list of users that should be allowed to login to this service. Names starting with '@', '+' and '&' are interpreted using the same rules as described in the
+.PP
+.RS 4
+This is a list of users that should be allowed to login to this service\. Names starting with \'@\', \'+\' and \'&\' are interpreted using the same rules as described in the
 \fIinvalid users\fR
 parameter.
 .sp
 If this is empty (the default) then any user can login. If a username is in both this list and the
+parameter\.
+.sp
+If this is empty (the default) then any user can login\. If a username is in both this list and the
 \fIinvalid users\fR
 list then access is denied for that user.
+list then access is denied for that user\.
 .sp
 The current servicename is substituted for
+\fI%S\fR. This is useful in the [homes] section.
+.sp
+Default:
+\fB\fIvalid users\fR = # No valid users list (anyone can login) \fR
+.sp
+Example:
+\fB\fIvalid users\fR = greg, @pcusers \fR
+.RE
+.PP
+\fI%S\fR\. This is useful in the [homes] section\.
+.sp
+Default:
+\fI\fIvalid users\fR\fR\fI = \fR\fI # No valid users list (anyone can login) \fR\fI \fR
+.sp
+Example:
+\fI\fIvalid users\fR\fR\fI = \fR\fIgreg, @pcusers\fR\fI \fR
+.RE
+\-valid (S)
+.PP
+.RS 4
+This parameter indicates whether a share is valid and thus can be used\. When this parameter is set to false, the share will be in no way visible nor accessible\.
+.sp
+This option should not be used by regular users but might be of help to developers\. Samba uses this option internally to mark shares as deleted\.
+.sp
+Default:
+\fI\fI\-valid\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 veto files (S)
+.RS 3n
+This is a list of files and directories that are neither visible nor accessible. Each entry in the list must be separated by a '/', which allows spaces to be included in the entry. '*' and '?' can be used to specify multiple files or directories as in DOS wildcards.
+.PP
+.RS 4
+This is a list of files and directories that are neither visible nor accessible\. Each entry in the list must be separated by a \'/\', which allows spaces to be included in the entry\. \'*\' and \'?\' 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
 \fBnot\fR
 include the unix directory separator '/'.
+\fInot\fR
+include the unix directory separator \'/\'\.
 .sp
 Note that the
+case sensitive option is applicable in vetoing files.
+.sp
+One feature of the veto files parameter that it is important to be aware of is Samba's behaviour when trying to delete a directory. If a directory that is to be deleted contains nothing but veto files this deletion will
+\fBfail\fR
+\fIcase sensitive\fR
+option is applicable in vetoing files\.
+.sp
+One feature of the veto files parameter that it is important to be aware of is Samba\'s behaviour when trying to delete a directory\. If a directory that is to be deleted contains nothing but veto files this deletion will
+\fIfail\fR
 unless you also set the
+delete veto files parameter to
+\fIyes\fR.
+.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.
+\fIdelete veto files\fR
+parameter to
+\fIyes\fR\.
+.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
 Examples of use include:
+.sp
+.sp
+.RS 4
 .nf
 ; Veto any files containing the word Security,
 ; any ending in .tmp, and any directory containing the
 ; word root.
 veto files = /*Security*/*.tmp/*root*/
+; any ending in \.tmp, and any directory containing the
+; word root\.
+veto files = /*Security*/*\.tmp/*root*/
 ; Veto the Apple specific files that a NetAtalk server
+; creates.
+veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/
+; creates\.
+veto files = /\.AppleDouble/\.bin/\.AppleDesktop/Network Trash Folder/
 .fi
+.sp
+Default:
+\fB\fIveto files\fR = No files or directories are vetoed. \fR
+.RE
+.PP
+.RE
+.sp
+.sp
+Default:
+\fI\fIveto files\fR\fR\fI = \fR\fINo files or directories are vetoed\.\fR\fI \fR
+.RE
 veto oplock files (S)
+.RS 3n
+.PP
+.RS 4
 This parameter is only valid when the
+oplocks parameter is turned on for a share. It allows the Samba administrator to selectively turn off the granting of oplocks on selected files that match a wildcarded list, similar to the wildcarded list used in the
+veto files parameter.
+.sp
+You might want to do this on files that you know will be heavily contended for by clients. A good example of this is in the NetBench SMB benchmark program, which causes heavy client contention for files ending in
+\fI.SEM\fR. To cause Samba not to grant oplocks on these files you would use the line (either in the [global] section or in the section for the particular NetBench share.
+\fIoplocks\fR
+parameter is turned on for a share\. It allows the Samba administrator to selectively turn off the granting of oplocks on selected files that match a wildcarded list, similar to the wildcarded list used in the
+\fIveto files\fR
+parameter\.
+.sp
+You might want to do this on files that you know will be heavily contended for by clients\. A good example of this is in the NetBench SMB benchmark program, which causes heavy client contention for files ending in
+\fI\.SEM\fR\. To cause Samba not to grant oplocks on these files you would use the line (either in the [global] section or in the section for the particular NetBench share\.
 .sp
 An example of use is:
+.sp
+.sp
+.RS 4
 .nf
+veto oplock files = /.*SEM/
+veto oplock files = /\.*SEM/
 .fi
+.sp
+Default:
+\fB\fIveto oplock files\fR = # No files are vetoed for oplock grants \fR
+.RE
+.PP
+vfs object
+.RS 3n
+This parameter is a synonym for vfs objects.
+.RE
+.PP
+.RE
+.sp
+.sp
+Default:
+\fI\fIveto oplock files\fR\fR\fI = \fR\fI # No files are vetoed for oplock grants\fR\fI \fR
+.RE
+vfs object.PP
+.RS 4
+This parameter is a synonym for
+vfs objects\.
+.RE
 vfs objects (S)
+.RS 3n
+This parameter specifies the backend names which are used for Samba VFS I/O operations. By default, normal disk I/O operations are used but these can be overloaded with one or more VFS objects.
+.sp
+Default:
+\fB\fIvfs objects\fR = \fR
+.sp
+Example:
+\fB\fIvfs objects\fR = extd_audit recycle \fR
+.RE
+.PP
+.PP
+.RS 4
+This parameter specifies the backend names which are used for Samba VFS I/O operations\. By default, normal disk I/O operations are used but these can be overloaded with one or more VFS objects\.
+.sp
+Default:
+\fI\fIvfs objects\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fIvfs objects\fR\fR\fI = \fR\fIextd_audit recycle\fR\fI \fR
+.RE
 volume (S)
+.RS 3n
+This allows you to override the volume label returned for a share. Useful for CDROMs with installation programs that insist on a particular volume label.
+.sp
+Default:
+\fB\fIvolume\fR = # the name of the share \fR
+.RE
+.PP
+.PP
+.RS 4
+This allows you to override the volume label returned for a share\. Useful for CDROMs with installation programs that insist on a particular volume label\.
+.sp
+Default:
+\fI\fIvolume\fR\fR\fI = \fR\fI # the name of the share\fR\fI \fR
+.RE
 wide links (S)
+.RS 3n
+This parameter controls whether or not links in the UNIX file system may be followed by the server. Links that point to areas within the directory tree exported by the server are always allowed; this parameter controls access only to areas that are outside the directory tree being exported.
+.sp
+Note that setting this parameter can have a negative effect on your server performance due to the extra system calls that Samba has to do in order to perform the link checks.
+.sp
+Default:
+\fB\fIwide links\fR = yes \fR
+.RE
+.PP
+.PP
+.RS 4
+This parameter controls whether or not links in the UNIX file system may be followed by the server\. Links that point to areas within the directory tree exported by the server are always allowed; this parameter controls access only to areas that are outside the directory tree being exported\.
+.sp
+Note that setting this parameter can have a negative effect on your server performance due to the extra system calls that Samba has to do in order to perform the link checks\.
+.sp
+Default:
+\fI\fIwide links\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 winbind cache time (G)
+.RS 3n
+.PP
+.RS 4
 This parameter specifies the number of seconds the
 \fBwinbindd\fR(8)
 daemon will cache user and group information before querying a Windows NT server again.
+daemon will cache user and group information before querying a Windows NT server again\.
 .sp
 This does not apply to authentication requests, these are always evaluated in real time unless the
+winbind offline logon option has been enabled.
+.sp
+Default:
+\fB\fIwinbind cache time\fR = 300 \fR
+.RE
+.PP
+\fIwinbind offline logon\fR
+option has been enabled\.
+.sp
+Default:
+\fI\fIwinbind cache time\fR\fR\fI = \fR\fI300\fR\fI \fR
+.RE
 winbind enum groups (G)
+.RS 3n
+.PP
+.RS 4
 On large installations using
 \fBwinbindd\fR(8)
 …
 and
 endgrent()
 group of system calls. If the
+group of system calls\. If the
 \fIwinbind enum groups\fR
 parameter is
 \fBno\fR, calls to the
 getgrent()
 system call will not return any data.
+system call will not return any data\.
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBWarning\fR
+Turning off group enumeration may cause some programs to behave oddly.
+Default:
+\fB\fIwinbind enum groups\fR = no \fR
+.RE
+.PP
+Warning
+Turning off group enumeration may cause some programs to behave oddly\.
+Default:
+\fI\fIwinbind enum groups\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 winbind enum users (G)
+.RS 3n
+.PP
+.RS 4
 On large installations using
 \fBwinbindd\fR(8)
 …
 and
 endpwent()
 group of system calls. If the
+group of system calls\. If the
 \fIwinbind enum users\fR
 parameter is
 \fBno\fR, calls to the
 getpwent
 system call will not return any data.
+system call will not return any data\.
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBWarning\fR
+Turning off user enumeration may cause some programs to behave oddly. For example, the finger program relies on having access to the full user list when searching for matching usernames.
+Default:
+\fB\fIwinbind enum users\fR = no \fR
+.RE
+.PP
+winbind expand groups (G)
+.RS 3n
+This option controls the maximum depth that winbindd will traverse when flattening nested group memberships of Windows domain groups. This is different from the
+winbind nested groups option which implements the Windows NT4 model of local group nesting. The "winbind expand groups" parameter specifically applies to the membership of domain groups.
+.sp
+Be aware that a high value for this parameter can result in system slowdown as the main parent winbindd daemon must perform the group unrolling and will be unable to answer incoming NSS or authentication requests during this time.
+.sp
+Default:
+\fB\fIwinbind expand groups\fR = 1 \fR
+.RE
+.PP
+Warning
+Turning off user enumeration may cause some programs to behave oddly\. For example, the finger program relies on having access to the full user list when searching for matching usernames\.
+Default:
+\fI\fIwinbind enum users\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 winbind nested groups (G)
+.RS 3n
+If set to yes, this parameter activates the support for nested groups. Nested groups are also called local groups or aliases. They work like their counterparts in Windows: Nested groups are defined locally on any machine (they are shared between DC's through their SAM) and can contain users and global groups from any trusted SAM. To be able to use nested groups, you need to run nss_winbind.
+.sp
+Default:
+\fB\fIwinbind nested groups\fR = yes \fR
+.RE
+.PP
+.PP
+.RS 4
+If set to yes, this parameter activates the support for nested groups\. Nested groups are also called local groups or aliases\. They work like their counterparts in Windows: Nested groups are defined locally on any machine (they are shared between DC\'s through their SAM) and can contain users and global groups from any trusted SAM\. To be able to use nested groups, you need to run nss_winbind\.
+.sp
+Default:
+\fI\fIwinbind nested groups\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 winbind normalize names (G)
+.RS 3n
+This parameter controls whether winbindd will replace whitespace in user and group names with an underscore (_) character. For example, whether the name "Space Kadet" should be replaced with the string "space_kadet". Frequently Unix shell scripts will have difficulty with usernames contains whitespace due to the default field separator in the shell. Do not enable this option if the underscore character is used in account names within your domain
+.sp
+Default:
+\fB\fIwinbind normalize names\fR = no \fR
+.sp
+Example:
+\fB\fIwinbind normalize names\fR = yes \fR
+.RE
+.PP
+.PP
+.RS 4
+This parameter controls whether winbindd will replace whitespace in user and group names with an underscore (_) character\. For example, whether the name "Space Kadet" should be replaced with the string "space_kadet"\. Frequently Unix shell scripts will have difficulty with usernames contains whitespace due to the default field separator in the shell\. Do not enable this option if the underscore character is used in account names within your domain
+.sp
+Default:
+\fI\fIwinbind normalize names\fR\fR\fI = \fR\fIno\fR\fI \fR
+.sp
+Example:
+\fI\fIwinbind normalize names\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 winbind nss info (G)
+.RS 3n
+This parameter is designed to control how Winbind retrieves Name Service Information to construct a user's home directory and login shell. Currently the following settings are available:
+.RS 3n
+.TP 3n
+\(bu
+.PP
+.RS 4
+This parameter is designed to control how Winbind retrieves Name Service Information to construct a user\'s home directory and login shell\. Currently the following settings are available:
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fItemplate\fR
 - The default, using the parameters of
+\- The default, using the parameters of
 \fItemplate shell\fR
 and
 \fItemplate homedir\fR)
+.TP 3n
+\(bu
+\fIsfu\fR
+- When Samba is running in security = ads and your Active Directory Domain Controller does support the Microsoft "Services for Unix" (SFU) LDAP schema, winbind can retrieve the login shell and the home directory attributes directly from your Directory Server. Note that retrieving UID and GID from your ADS-Server requires to use
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\fI<sfu | rfc2307 >\fR
+\- When Samba is running in security = ads and your Active Directory Domain Controller does support the Microsoft "Services for Unix" (SFU) LDAP schema, winbind can retrieve the login shell and the home directory attributes directly from your Directory Server\. Note that retrieving UID and GID from your ADS\-Server requires to use
 \fIidmap backend\fR
+= idmap_ad as well.
+.RE
+.IP "" 3n
+.sp
+Default:
+\fB\fIwinbind nss info\fR = template \fR
+.sp
+Example:
+\fB\fIwinbind nss info\fR = template sfu \fR
+.RE
+.PP
+= ad or
+\fIidmap config DOMAIN:backend\fR
+= ad as well\.
+.sp
+.RE
+.sp
+Default:
+\fI\fIwinbind nss info\fR\fR\fI = \fR\fItemplate\fR\fI \fR
+.sp
+Example:
+\fI\fIwinbind nss info\fR\fR\fI = \fR\fItemplate sfu\fR\fI \fR
+.RE
 winbind offline logon (G)
+.RS 3n
+.PP
+.RS 4
 This parameter is designed to control whether Winbind should allow to login with the
 \fIpam_winbind\fR
 module using Cached Credentials. If enabled, winbindd will store user credentials from successful logins encrypted in a local cache.
 .sp
 Default:
 \fB\fIwinbind offline logon\fR = false \fR
 .sp
 Example:
 \fB\fIwinbind offline logon\fR = true \fR
 .RE
+.PP
+module using Cached Credentials\. If enabled, winbindd will store user credentials from successful logins encrypted in a local cache\.
+.sp
+Default:
+\fI\fIwinbind offline logon\fR\fR\fI = \fR\fIfalse\fR\fI \fR
+.sp
+Example:
+\fI\fIwinbind offline logon\fR\fR\fI = \fR\fItrue\fR\fI \fR
+.RE
 winbind refresh tickets (G)
+.RS 3n
+.PP
+.RS 4
 This parameter is designed to control whether Winbind should refresh Kerberos Tickets retrieved using the
 \fIpam_winbind\fR
+module.
+.sp
+Default:
+\fB\fIwinbind refresh tickets\fR = false \fR
+.sp
+Example:
+\fB\fIwinbind refresh tickets\fR = true \fR
+.RE
+.PP
+winbind rpc only (G)
+.RS 3n
+Setting this parameter to
+yes
+forces winbindd to use RPC instead of LDAP to retrieve information from Domain Controllers.
+.sp
+Default:
+\fB\fIwinbind rpc only\fR = no \fR
+.RE
+.PP
+module\.
+.sp
+Default:
+\fI\fIwinbind refresh tickets\fR\fR\fI = \fR\fIfalse\fR\fI \fR
+.sp
+Example:
+\fI\fIwinbind refresh tickets\fR\fR\fI = \fR\fItrue\fR\fI \fR
+.RE
 winbind separator (G)
+.RS 3n
+.PP
+.RS 4
 This parameter allows an admin to define the character used when listing a username of the form of
 \fIDOMAIN \fR\\fIuser\fR. This parameter is only applicable when using the
 \fIpam_winbind.so\fR
+\fIDOMAIN \fR\e\fIuser\fR\. This parameter is only applicable when using the
+\fIpam_winbind\.so\fR
 and
 \fInss_winbind.so\fR
 modules for UNIX services.
 .sp
 Please note that setting this parameter to + causes problems with group membership at least on glibc systems, as the character + is used as a special character for NIS in /etc/group.
 .sp
 Default:
 \fB\fIwinbind separator\fR = '\\' \fR
 .sp
 Example:
 \fB\fIwinbind separator\fR = + \fR
 .RE
+.PP
+\fInss_winbind\.so\fR
+modules for UNIX services\.
+.sp
+Please note that setting this parameter to + causes problems with group membership at least on glibc systems, as the character + is used as a special character for NIS in /etc/group\.
+.sp
+Default:
+\fI\fIwinbind separator\fR\fR\fI = \fR\fI\'\e\'\fR\fI \fR
+.sp
+Example:
+\fI\fIwinbind separator\fR\fR\fI = \fR\fI+\fR\fI \fR
+.RE
 winbind trusted domains only (G)
+.RS 3n
+This parameter is designed to allow Samba servers that are members of a Samba controlled domain to use UNIX accounts distributed via NIS, rsync, or LDAP as the uid's for winbindd users in the hosts primary domain. Therefore, the user
+DOMAIN\\user1
+would be mapped to the account user1 in /etc/passwd instead of allocating a new uid for him or her.
+.sp
+This parameter is now deprecated in favor of the newer idmap_nss backend. Refer to the
+idmap domains smb.conf option and the
+.PP
+.RS 4
+This parameter is designed to allow Samba servers that are members of a Samba controlled domain to use UNIX accounts distributed via NIS, rsync, or LDAP as the uid\'s for winbindd users in the hosts primary domain\. Therefore, the user
+DOMAIN\euser1
+would be mapped to the account user1 in /etc/passwd instead of allocating a new uid for him or her\.
+.sp
+This parameter is now deprecated in favor of the newer idmap_nss backend\. Refer to the
+\fIidmap domains\fR
+smb\.conf option and the
 \fBidmap_nss\fR(8)
 man page for more information.
 .sp
 Default:
 \fB\fIwinbind trusted domains only\fR = no \fR
 .RE
+.PP
+man page for more information\.
+.sp
+Default:
+\fI\fIwinbind trusted domains only\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 winbind use default domain (G)
+.RS 3n
+.PP
+.RS 4
 This parameter specifies whether the
 \fBwinbindd\fR(8)
 daemon should operate on users without domain component in their username. Users without a domain component are treated as is part of the winbindd server's own domain. While this does not benifit Windows users, it makes SSH, FTP and e-mail function in a way much closer to the way they would in a native unix system.
 .sp
 Default:
 \fB\fIwinbind use default domain\fR = no \fR
 .sp
 Example:
 \fB\fIwinbind use default domain\fR = yes \fR
 .RE
+.PP
+daemon should operate on users without domain component in their username\. Users without a domain component are treated as is part of the winbindd server\'s own domain\. While this does not benifit Windows users, it makes SSH, FTP and e\-mail function in a way much closer to the way they would in a native unix system\.
+.sp
+Default:
+\fI\fIwinbind use default domain\fR\fR\fI = \fR\fIno\fR\fI \fR
+.sp
+Example:
+\fI\fIwinbind use default domain\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 wins hook (G)
+.RS 3n
+When Samba is running as a WINS server this allows you to call an external program for all changes to the WINS database. The primary use for this option is to allow the dynamic update of external name resolution databases such as dynamic DNS.
+.PP
+.RS 4
+When Samba is running as a WINS server this allows you to call an external program for all changes to the WINS database\. The primary use for this option is to allow the dynamic update of external name resolution databases such as dynamic DNS\.
 .sp
 The wins hook parameter specifies the name of a script or executable that will be called as follows:
 .sp
 wins_hook operation name nametype ttl IP_list
+.RS 3n
+.TP 3n
+\(bu
+The first argument is the operation and is one of "add", "delete", or "refresh". In most cases the operation can be ignored as the rest of the parameters provide sufficient information. Note that "refresh" may sometimes be called when the name has not previously been added, in that case it should be treated as an add.
+.TP 3n
+\(bu
+The second argument is the NetBIOS name. If the name is not a legal name then the wins hook is not called. Legal names contain only letters, digits, hyphens, underscores and periods.
+.TP 3n
+\(bu
+The third argument is the NetBIOS name type as a 2 digit hexadecimal number.
+.TP 3n
+\(bu
+The fourth argument is the TTL (time to live) for the name in seconds.
+.TP 3n
+\(bu
+The fifth and subsequent arguments are the IP addresses currently registered for that name. If this list is empty then the name should be deleted.
+.RE
+.IP "" 3n
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+The first argument is the operation and is one of "add", "delete", or "refresh"\. In most cases the operation can be ignored as the rest of the parameters provide sufficient information\. Note that "refresh" may sometimes be called when the name has not previously been added, in that case it should be treated as an add\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+The second argument is the NetBIOS name\. If the name is not a legal name then the wins hook is not called\. Legal names contain only letters, digits, hyphens, underscores and periods\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+The third argument is the NetBIOS name type as a 2 digit hexadecimal number\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+The fourth argument is the TTL (time to live) for the name in seconds\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+The fifth and subsequent arguments are the IP addresses currently registered for that name\. If this list is empty then the name should be deleted\.
+.sp
+.RE
 An example script that calls the BIND dynamic DNS update program
 nsupdate
 is provided in the examples directory of the Samba source code.
 .sp
 \fBNo default\fR
 .RE
+.PP
+is provided in the examples directory of the Samba source code\.
+.sp
+\fINo default\fR
+.RE
 wins proxy (G)
+.RS 3n
+.PP
+.RS 4
 This is a boolean that controls if
 \fBnmbd\fR(8)
 will respond to broadcast name queries on behalf of other hosts. You may need to set this to
+will respond to broadcast name queries on behalf of other hosts\. You may need to set this to
 \fByes\fR
 for some older clients.
 .sp
 Default:
 \fB\fIwins proxy\fR = no \fR
 .RE
+.PP
+for some older clients\.
+.sp
+Default:
+\fI\fIwins proxy\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 wins server (G)
+.RS 3n
+.PP
+.RS 4
 This specifies the IP address (or DNS name: IP address for preference) of the WINS server that
 \fBnmbd\fR(8)
 should register with. If you have a WINS server on your network then you should set this to the WINS server's IP.
 .sp
 You should point this at your WINS server if you have a multi-subnetted network.
 .sp
 If you want to work in multiple namespaces, you can give every wins server a 'tag'. For each tag, only one (working) server will be queried for a name. The tag should be separated from the ip address by a colon.
+should register with\. If you have a WINS server on your network then you should set this to the WINS server\'s IP\.
+.sp
+You should point this at your WINS server if you have a multi\-subnetted network\.
+.sp
+If you want to work in multiple namespaces, you can give every wins server a \'tag\'\. For each tag, only one (working) server will be queried for a name\. The tag should be separated from the ip address by a colon\.
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBNote\fR
+You need to set up Samba to point to a WINS server if you have multiple subnets and wish cross-subnet browsing to work correctly.
+See the chapter in the Samba3-HOWTO on Network Browsing.
+.sp
+Default:
+\fB\fIwins server\fR = \fR
+.sp
+Example:
+\fB\fIwins server\fR = mary:192.9.200.1 fred:192.168.3.199 mary:192.168.2.61 # For this example when querying a certain name, 192.19.200.1 will be asked first and if that doesn't respond 192.168.2.61. If either of those doesn't know the name 192.168.3.199 will be queried. \fR
+.sp
+Example:
+\fB\fIwins server\fR = 192.9.200.1 192.168.2.61 \fR
+.RE
+.PP
+Note
+You need to set up Samba to point to a WINS server if you have multiple subnets and wish cross\-subnet browsing to work correctly\.
+See the chapter in the Samba3\-HOWTO on Network Browsing\.
+.sp
+Default:
+\fI\fIwins server\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fIwins server\fR\fR\fI = \fR\fImary:192\.9\.200\.1 fred:192\.168\.3\.199 mary:192\.168\.2\.61 # For this example when querying a certain name, 192\.19\.200\.1 will be asked first and if that doesn\'t respond 192\.168\.2\.61\. If either of those doesn\'t know the name 192\.168\.3\.199 will be queried\.\fR\fI \fR
+.sp
+Example:
+\fI\fIwins server\fR\fR\fI = \fR\fI192\.9\.200\.1 192\.168\.2\.61\fR\fI \fR
+.RE
 wins support (G)
+.RS 3n
+.PP
+.RS 4
 This boolean controls if the
 \fBnmbd\fR(8)
 process in Samba will act as a WINS server. You should not set this to
+process in Samba will act as a WINS server\. You should not set this to
 \fByes\fR
 unless you have a multi-subnetted network and you wish a particular
+unless you have a multi\-subnetted network and you wish a particular
 nmbd
 to be your WINS server. Note that you should
 \fBNEVER\fR
+to be your WINS server\. Note that you should
+\fINEVER\fR
 set this to
 \fByes\fR
 on more than one machine in your network.
 .sp
 Default:
 \fB\fIwins support\fR = no \fR
 .RE
+.PP
+on more than one machine in your network\.
+.sp
+Default:
+\fI\fIwins support\fR\fR\fI = \fR\fIno\fR\fI \fR
+.RE
 workgroup (G)
+.RS 3n
+This controls what workgroup your server will appear to be in when queried by clients. Note that this parameter also controls the Domain name used with the
+security = domain setting.
+.sp
+Default:
+\fB\fIworkgroup\fR = WORKGROUP \fR
+.sp
+Example:
+\fB\fIworkgroup\fR = MYGROUP \fR
+.RE
+.PP
+writable
+.RS 3n
+This parameter is a synonym for writeable.
+.RE
+.PP
+.PP
+.RS 4
+This controls what workgroup your server will appear to be in when queried by clients\. Note that this parameter also controls the Domain name used with the
+\fIsecurity = domain\fR
+setting\.
+.sp
+Default:
+\fI\fIworkgroup\fR\fR\fI = \fR\fIWORKGROUP\fR\fI \fR
+.sp
+Example:
+\fI\fIworkgroup\fR\fR\fI = \fR\fIMYGROUP\fR\fI \fR
+.RE
+writable.PP
+.RS 4
+This parameter is a synonym for
+writeable\.
+.RE
 writeable (S)
+.RS 3n
+.PP
+.RS 4
 Inverted synonym for
 read only.
 .sp
 \fBNo default\fR
 .RE
+.PP
+\fIread only\fR\.
+.sp
+\fINo default\fR
+.RE
 write cache size (S)
+.RS 3n
+If this integer parameter is set to non-zero value, Samba will create an in-memory cache for each oplocked file (it does
+\fBnot\fR
+do this for non-oplocked files). All writes that the client does not request to be flushed directly to disk will be stored in this cache if possible. The cache is flushed onto disk when a write comes in whose offset would not fit into the cache or when the file is closed by the client. Reads for the file are also served from this cache if the data is stored within it.
+.sp
+This cache allows Samba to batch client writes into a more efficient write size for RAID disks (i.e. writes may be tuned to be the RAID stripe size) and can improve performance on systems where the disk subsystem is a bottleneck but there is free memory for userspace programs.
+.sp
+The integer parameter specifies the size of this cache (per oplocked file) in bytes.
+.sp
+Default:
+\fB\fIwrite cache size\fR = 0 \fR
+.sp
+Example:
+\fB\fIwrite cache size\fR = 262144 # for a 256k cache size per file \fR
+.RE
+.PP
+.PP
+.RS 4
+If this integer parameter is set to non\-zero value, Samba will create an in\-memory cache for each oplocked file (it does
+\fInot\fR
+do this for non\-oplocked files)\. All writes that the client does not request to be flushed directly to disk will be stored in this cache if possible\. The cache is flushed onto disk when a write comes in whose offset would not fit into the cache or when the file is closed by the client\. Reads for the file are also served from this cache if the data is stored within it\.
+.sp
+This cache allows Samba to batch client writes into a more efficient write size for RAID disks (i\.e\. writes may be tuned to be the RAID stripe size) and can improve performance on systems where the disk subsystem is a bottleneck but there is free memory for userspace programs\.
+.sp
+The integer parameter specifies the size of this cache (per oplocked file) in bytes\.
+.sp
+Default:
+\fI\fIwrite cache size\fR\fR\fI = \fR\fI0\fR\fI \fR
+.sp
+Example:
+\fI\fIwrite cache size\fR\fR\fI = \fR\fI262144 # for a 256k cache size per file\fR\fI \fR
+.RE
 write list (S)
+.RS 3n
+This is a list of users that are given read-write access to a service. If the connecting user is in this list then they will be given write access, no matter what the
+read only option is set to. The list can include group names using the @group syntax.
+.sp
+Note that if a user is in both the read list and the write list then they will be given write access.
+.PP
+.RS 4
+This is a list of users that are given read\-write access to a service\. If the connecting user is in this list then they will be given write access, no matter what the
+\fIread only\fR
+option is set to\. The list can include group names using the @group syntax\.
+.sp
+Note that if a user is in both the read list and the write list then they will be given write access\.
 .sp
 By design, this parameter will not work with the
+security = share in Samba 3.0.
+.sp
+Default:
+\fB\fIwrite list\fR = \fR
+.sp
+Example:
+\fB\fIwrite list\fR = admin, root, @staff \fR
+.RE
+.PP
+\fIsecurity = share\fR
+in Samba 3\.0\.
+.sp
+Default:
+\fI\fIwrite list\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fIwrite list\fR\fR\fI = \fR\fIadmin, root, @staff\fR\fI \fR
+.RE
 write raw (G)
+.RS 3n
+This parameter controls whether or not the server will support raw write SMB's when transferring data from clients. You should never need to change this parameter.
+.sp
+Default:
+\fB\fIwrite raw\fR = yes \fR
+.RE
+.PP
+.PP
+.RS 4
+This parameter controls whether or not the server will support raw write SMB\'s when transferring data from clients\. You should never need to change this parameter\.
+.sp
+Default:
+\fI\fIwrite raw\fR\fR\fI = \fR\fIyes\fR\fI \fR
+.RE
 wtmp directory (G)
+.RS 3n
+.PP
+.RS 4
 This parameter is only available if Samba has been configured and compiled with the option
 --with-utmp. It specifies a directory pathname that is used to store the wtmp or wtmpx files (depending on the UNIX system) that record user connections to a Samba server. The difference with the utmp directory is the fact that user info is kept after a user has logged out.
+\-\-with\-utmp\. It specifies a directory pathname that is used to store the wtmp or wtmpx files (depending on the UNIX system) that record user connections to a Samba server\. The difference with the utmp directory is the fact that user info is kept after a user has logged out\.
 .sp
 By default this is not set, meaning the system will use whatever utmp file the native system is set to use (usually
 \fI/var/run/wtmp\fR
 on Linux).
 .sp
 Default:
 \fB\fIwtmp directory\fR = \fR
 .sp
 Example:
 \fB\fIwtmp directory\fR = /var/log/wtmp \fR
+on Linux)\.
+.sp
+Default:
+\fI\fIwtmp directory\fR\fR\fI = \fR\fI\fR\fI \fR
+.sp
+Example:
+\fI\fIwtmp directory\fR\fR\fI = \fR\fI/var/log/wtmp\fR\fI \fR
 .RE
 .SH "WARNINGS"
 .PP
 Although the configuration file permits service names to contain spaces, your client software may not. Spaces will be ignored in comparisons anyway, so it shouldn't be a problem - but be aware of the possibility.
 .PP
 On a similar note, many clients - especially DOS clients - limit service names to eight characters.
+Although the configuration file permits service names to contain spaces, your client software may not\. Spaces will be ignored in comparisons anyway, so it shouldn\'t be a problem \- but be aware of the possibility\.
+.PP
+On a similar note, many clients \- especially DOS clients \- limit service names to eight characters\.
 \fBsmbd\fR(8)
 has no such limitation, but attempts to connect from such clients will fail if they truncate the service names. For this reason you should probably keep your service names down to eight characters in length.
+has no such limitation, but attempts to connect from such clients will fail if they truncate the service names\. For this reason you should probably keep your service names down to eight characters in length\.
 .PP
 Use of the
 …
 and
 [printers]
 special sections make life for an administrator easy, but the various combinations of default attributes can be tricky. Take extreme care when designing these sections. In particular, ensure that the permissions on spool directories are correct.
+special sections make life for an administrator easy, but the various combinations of default attributes can be tricky\. Take extreme care when designing these sections\. In particular, ensure that the permissions on spool directories are correct\.
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 of the Samba suite\.
 .SH "SEE ALSO"
 .PP
 …
 \fBnmblookup\fR(1),
 \fBtestparm\fR(1),
 \fBtestprns\fR(1).
+\fBtestprns\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.
+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\.

branches/samba-3.0/docs/manpages/smbcacls.1

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "SMBCACLS" 1 "" "" ""
+.\"     Title: smbcacls
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: User Commands
+.\"    Source: Samba 3.0
+.\"
+.TH "SMBCACLS" "1" "05/21/2008" "Samba 3\.0" "User Commands"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 smbcacls - Set or get ACLs on an NT file or directory names
 .SH "SYNOPSIS"
 .HP 1
 smbcacls {//server/share} {filename} [-D acls] [-M acls] [-a acls] [-S acls] [-C name] [-G name] [--numeric] [-t] [-U username] [-h] [-d]
+smbcacls {//server/share} {filename} [\-D\ acls] [\-M\ acls] [\-a\ acls] [\-S\ acls] [\-C\ name] [\-G\ name] [\-\-numeric] [\-t] [\-U\ username] [\-h] [\-d]
 .SH "DESCRIPTION"
 .PP
 This tool is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 The
 smbcacls
 program manipulates NT Access Control Lists (ACLs) on SMB file shares.
+program manipulates NT Access Control Lists (ACLs) on SMB file shares\.
 .SH "OPTIONS"
 .PP
 The following options are available to the
 smbcacls
 program. The format of ACLs is described in the section ACL FORMAT
 .PP
 -a acls
 .RS 3n
 Add the ACLs specified to the ACL list. Existing access control entries are unchanged.
 .RE
 .PP
 -M acls
 .RS 3n
 Modify the mask value (permissions) for the ACLs specified on the command line. An error will be printed for each ACL specified that was not already present in the ACL list
 .RE
 .PP
 -D acls
 .RS 3n
 Delete any ACLs specified on the command line. An error will be printed for each ACL specified that was not already present in the ACL list.
 .RE
 .PP
 -S acls
 .RS 3n
 This command sets the ACLs on the file with only the ones specified on the command line. All other ACLs are erased. Note that the ACL specified must contain at least a revision, type, owner and group for the call to succeed.
 .RE
 .PP
 -U username
 .RS 3n
 Specifies a username used to connect to the specified service. The username may be of the form "username" in which case the user is prompted to enter in a password and the workgroup specified in the
+program\. The format of ACLs is described in the section ACL FORMAT
+.PP
+\-a acls
+.RS 4
+Add the ACLs specified to the ACL list\. Existing access control entries are unchanged\.
+.RE
+.PP
+\-M acls
+.RS 4
+Modify the mask value (permissions) for the ACLs specified on the command line\. An error will be printed for each ACL specified that was not already present in the ACL list
+.RE
+.PP
+\-D acls
+.RS 4
+Delete any ACLs specified on the command line\. An error will be printed for each ACL specified that was not already present in the ACL list\.
+.RE
+.PP
+\-S acls
+.RS 4
+This command sets the ACLs on the file with only the ones specified on the command line\. All other ACLs are erased\. Note that the ACL specified must contain at least a revision, type, owner and group for the call to succeed\.
+.RE
+.PP
+\-U username
+.RS 4
+Specifies a username used to connect to the specified service\. The username may be of the form "username" in which case the user is prompted to enter in a password and the workgroup specified in the
 \fBsmb.conf\fR(5)
 file is used, or "username%password" or "DOMAIN\username%password" and the password and workgroup names are used as provided.
 .RE
 .PP
 -C name
 .RS 3n
+file is used, or "username%password" or "DOMAIN\eusername%password" and the password and workgroup names are used as provided\.
+.RE
+.PP
+\-C name
+.RS 4
 The owner of a file or directory can be changed to the name given using the
 \fI-C\fR
 option. The name can be a sid in the form S-1-x-y-z or a name resolved against the server specified in the first argument.
 .sp
 This command is a shortcut for -M OWNER:name.
 .RE
 .PP
 -G name
 .RS 3n
+\fI\-C\fR
+option\. The name can be a sid in the form S\-1\-x\-y\-z or a name resolved against the server specified in the first argument\.
+.sp
+This command is a shortcut for \-M OWNER:name\.
+.RE
+.PP
+\-G name
+.RS 4
 The group owner of a file or directory can be changed to the name given using the
+\fI-G\fR
+option. The name can be a sid in the form S-1-x-y-z or a name resolved against the server specified n the first argument.
+.sp
+This command is a shortcut for -M GROUP:name.
+.RE
+.PP
+--numeric
+.RS 3n
+This option displays all ACL information in numeric format. The default is to convert SIDs to names and ACE types and masks to a readable string format.
+.RE
+.PP
+-t
+.RS 3n
+Don't actually do anything, only validate the correctness of the arguments.
+.RE
+.PP
+-h|--help
+.RS 3n
+Print a summary of command line options.
+.RE
+.PP
+-V
+.RS 3n
+Prints the program version number.
+.RE
+.PP
+-s <configuration file>
+.RS 3n
+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
+\fIsmb.conf\fR
+for more information. The default configuration file name is determined at compile time.
+.RE
+.PP
+-d|--debuglevel=level
+.RS 3n
+\fI\-G\fR
+option\. The name can be a sid in the form S\-1\-x\-y\-z or a name resolved against the server specified n the first argument\.
+.sp
+This command is a shortcut for \-M GROUP:name\.
+.RE
+.PP
+\-\-numeric
+.RS 4
+This option displays all ACL information in numeric format\. The default is to convert SIDs to names and ACE types and masks to a readable string format\.
+.RE
+.PP
+\-t
+.RS 4
+Don\'t actually do anything, only validate the correctness of the arguments\.
+.RE
+.PP
+\-h|\-\-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 zero.
 .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.
+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
+\fIlog level\fR
 parameter in the
+\fIsmb.conf\fR
+file.
+.RE
+.PP
+-l|--logfile=logdirectory
+.RS 3n
+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.
+\fIsmb\.conf\fR
+file\.
+.RE
+.PP
+\-V
+.RS 4
+Prints the program version number\.
+.RE
+.PP
+\-s <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
+\fIsmb\.conf\fR
+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
 .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
+.sp
+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
+.RS 4
 .nf
 …
 GROUP:<sid or name>
 ACL:<sid or name>:<type>/<flags>/<mask>
 .fi
+.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. If a SID in the format S-1-x-y-z is specified this is used, otherwise the name specified is resolved using the server on which the file or directory resides.
+.PP
+ACLs specify permissions granted to the SID. This SID again 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 0 or 1 corresponding to ALLOWED or DENIED access to the SID. The flags values are generally zero for file ACLs and either 9 or 2 for directory ACLs. Some common flags are:
+.TP 3n
+\(bu
+.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\. If a SID in the format S\-1\-x\-y\-z is specified this is used, otherwise the name specified is resolved using the server on which the file or directory resides\.
+.PP
+ACLs specify permissions granted to the SID\. This SID again 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 0 or 1 corresponding to ALLOWED or DENIED access to the SID\. The flags values are generally zero for file ACLs and either 9 or 2 for directory ACLs\. Some common flags are:
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fB#define SEC_ACE_FLAG_OBJECT_INHERIT 0x1\fR
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fB#define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2\fR
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fB#define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4\fR
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fB#define SEC_ACE_FLAG_INHERIT_ONLY 0x8\fR
+.PP
+At present flags can only be specified as decimal or hexadecimal values.
+.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.
+.TP 3n
+\(bu
+\fBR\fR
+- Allow read access
+.TP 3n
+\(bu
+\fBW\fR
+- Allow write access
+.TP 3n
+\(bu
+\fBX\fR
+- Execute permission on the object
+.TP 3n
+\(bu
+\fBD\fR
+- Delete the object
+.TP 3n
+\(bu
+\fBP\fR
+- Change permissions
+.TP 3n
+\(bu
+\fBO\fR
+- Take ownership
+.sp
+.RE
+.PP
+At present flags can only be specified as decimal or hexadecimal values\.
+.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
+.sp
+.RE
 .PP
 The following combined permissions can be specified:
+.TP 3n
+\(bu
+\fBREAD\fR
+- Equivalent to 'RX' permissions
+.TP 3n
+\(bu
+\fBCHANGE\fR
+- Equivalent to 'RXWD' permissions
+.TP 3n
+\(bu
+\fBFULL\fR
+- Equivalent to 'RWXDPO' permissions
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\fIREAD\fR
+\- Equivalent to \'RX\' permissions
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\fICHANGE\fR
+\- Equivalent to \'RXWD\' permissions
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\fIFULL\fR
+\- Equivalent to \'RWXDPO\' permissions
 .SH "EXIT STATUS"
 .PP
 The
 smbcacls
 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, smbcacls returns and exit status of 0. If
 smbcacls
 couldn't 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.
+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, smbcacls returns and exit status of 0\. If
+smbcacls
+couldn\'t 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 "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 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
+smbcacls
+was written by Andrew Tridgell and Tim Potter.
+.PP
+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.
+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
+smbcacls
+was written by Andrew Tridgell and Tim Potter\.
+.PP
+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\.

branches/samba-3.0/docs/manpages/smbclient.1

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "SMBCLIENT" 1 "" "" ""
+.\"     Title: smbclient
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: User Commands
+.\"    Source: Samba 3.0
+.\"
+.TH "SMBCLIENT" "1" "05/21/2008" "Samba 3\.0" "User Commands"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 smbclient - ftp-like client to access SMB/CIFS resources on servers
 .SH "SYNOPSIS"
 .HP 1
 smbclient [-b <buffer size>] [-d debuglevel] [-L <netbios name>] [-U username] [-I destinationIP] [-M <netbios name>] [-m maxprotocol] [-A authfile] [-N] [-i scope] [-O <socket options>] [-p port] [-R <name resolve order>] [-s <smb config file>] [-k] [-P] [-c <command>]
+smbclient [\-b\ <buffer\ size>] [\-d\ debuglevel] [\-e] [\-L\ <netbios\ name>] [\-U\ username] [\-I\ destinationIP] [\-M\ <netbios\ name>] [\-m\ maxprotocol] [\-A\ authfile] [\-N] [\-i\ scope] [\-O\ <socket\ options>] [\-p\ port] [\-R\ <name\ resolve\ order>] [\-s\ <smb\ config\ file>] [\-k] [\-P] [\-c\ <command>]
 .HP 1
 smbclient {servicename} [password] [-b <buffer size>] [-d debuglevel] [-D Directory] [-U username] [-W workgroup] [-M <netbios name>] [-m maxprotocol] [-A authfile] [-N] [-l logdir] [-I destinationIP] [-E] [-c <command string>] [-i scope] [-O <socket options>] [-p port] [-R <name resolve order>] [-s <smb config file>] [-T<c|x>IXFqgbNan] [-k]
+smbclient {servicename} [password] [\-b\ <buffer\ size>] [\-d\ debuglevel] [\-e] [\-D\ Directory] [\-U\ username] [\-W\ workgroup] [\-M\ <netbios\ name>] [\-m\ maxprotocol] [\-A\ authfile] [\-N] [\-l\ log\-basename] [\-I\ destinationIP] [\-E] [\-c\ <command\ string>] [\-i\ scope] [\-O\ <socket\ options>] [\-p\ port] [\-R\ <name\ resolve\ order>] [\-s\ <smb\ config\ file>] [\-T<c|x>IXFqgbNan] [\-k]
 .SH "DESCRIPTION"
 .PP
 This tool is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 smbclient
 is a client that can 'talk' to an SMB/CIFS server. It offers an interface similar to that of the ftp program (see
 \fBftp\fR(1)). Operations include things like getting files from the server to the local machine, putting files from the local machine to the server, retrieving directory information from the server and so on.
+is a client that can \'talk\' to an SMB/CIFS server\. It offers an interface similar to that of the ftp program (see
+\fBftp\fR(1))\. Operations include things like getting files from the server to the local machine, putting files from the local machine to the server, retrieving directory information from the server and so on\.
 .SH "OPTIONS"
 .PP
 servicename
 .RS 3n
 servicename is the name of the service you want to use on the server. A service name takes the form
+.RS 4
+servicename is the name of the service you want to use on the server\. A service name takes the form
 \fI//server/service\fR
 where
 …
 is the NetBIOS name of the SMB/CIFS server offering the desired service and
 \fIservice\fR
 is the name of the service offered. Thus to connect to the service "printer" on the SMB/CIFS server "smbserver", you would use the servicename
+is the name of the service offered\. Thus to connect to the service "printer" on the SMB/CIFS server "smbserver", you would use the servicename
 \fI//smbserver/printer \fR
 .sp
 Note that the server name required is NOT necessarily the IP (DNS) host name of the server ! The name required is a NetBIOS server name, which may or may not be the same as the IP hostname of the machine running the server.
+Note that the server name required is NOT necessarily the IP (DNS) host name of the server ! The name required is a NetBIOS server name, which may or may not be the same as the IP hostname of the machine running the server\.
 .sp
 The server name is looked up according to either the
 \fI-R\fR
+\fI\-R\fR
 parameter to
 smbclient
 or using the name resolve order parameter in the
 \fBsmb.conf\fR(5)
 file, allowing an administrator to change the order and methods by which server names are looked up.
+file, allowing an administrator to change the order and methods by which server names are looked up\.
 .RE
 .PP
 password
 .RS 3n
 The password required to access the specified service on the specified server. If this parameter is supplied, the
 \fI-N\fR
 option (suppress password prompt) is assumed.
 .sp
 There is no default password. If no password is supplied on the command line (either by using this parameter or adding a password to the
 \fI-U\fR
+.RS 4
+The password required to access the specified service on the specified server\. If this parameter is supplied, the
+\fI\-N\fR
+option (suppress password prompt) is assumed\.
+.sp
+There is no default password\. If no password is supplied on the command line (either by using this parameter or adding a password to the
+\fI\-U\fR
 option (see below)) and the
+\fI-N\fR
+option is not specified, the client will prompt for a password, even if the desired service does not require one. (If no password is required, simply press ENTER to provide a null password.)
+.sp
+Note: Some servers (including OS/2 and Windows for Workgroups) insist on an uppercase password. Lowercase or mixed case passwords may be rejected by these servers.
+.sp
+Be cautious about including passwords in scripts.
+.RE
+.PP
+-R <name resolve order>
+.RS 3n
+This option is used by the programs in the Samba suite to determine what naming services and in what order to resolve host names to IP addresses. The option takes a space-separated string of different name resolution options.
+.sp
+The options are :"lmhosts", "host", "wins" and "bcast". They cause names to be resolved as follows:
+.RS 3n
+.TP 3n
+\(bu
+\fBlmhosts\fR: Lookup an IP address in the Samba lmhosts file. If the line in lmhosts has no name type attached to the NetBIOS name (see the
+\fI\-N\fR
+option is not specified, the client will prompt for a password, even if the desired service does not require one\. (If no password is required, simply press ENTER to provide a null password\.)
+.sp
+Note: Some servers (including OS/2 and Windows for Workgroups) insist on an uppercase password\. Lowercase or mixed case passwords may be rejected by these servers\.
+.sp
+Be cautious about including passwords in scripts\.
+.RE
+.PP
+\-R <name resolve order>
+.RS 4
+This option is used by the programs in the Samba suite to determine what naming services and in what order to resolve host names to IP addresses\. The option takes a space\-separated string of different name resolution options\.
+.sp
+The options are :"lmhosts", "host", "wins" and "bcast"\. They cause names to be resolved as follows:
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\fBlmhosts\fR: Lookup an IP address in the Samba lmhosts file\. If the line in lmhosts has no name type attached to the NetBIOS name (see the
 \fBlmhosts\fR(5)
+for details) then any name type matches for lookup.
+.TP 3n
+\(bu
+for details) then any name type matches for lookup\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fBhost\fR: Do a standard host name to IP address resolution, using the system
+\fI/etc/hosts \fR, NIS, or DNS lookups. This method of name resolution is operating system dependent, for instance on IRIX or Solaris this may be controlled by the
+\fI/etc/nsswitch.conf\fR
+file). Note that this method is only used if the NetBIOS name type being queried is the 0x20 (server) name type, otherwise it is ignored.
+.TP 3n
+\(bu
+\fI/etc/hosts \fR, NIS, or DNS lookups\. This method of name resolution is operating system dependent, for instance on IRIX or Solaris this may be controlled by the
+\fI/etc/nsswitch\.conf\fR
+file)\. Note that this method is only used if the NetBIOS name type being queried is the 0x20 (server) name type, otherwise it is ignored\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fBwins\fR: Query a name with the IP address listed in the
 \fIwins server\fR
+parameter. If no WINS server has been specified this method will be ignored.
+.TP 3n
+\(bu
+parameter\. If no WINS server has been specified this method will be ignored\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fBbcast\fR: Do a broadcast on each of the known local interfaces listed in the
 \fIinterfaces\fR
 parameter. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet.
 .RE
 .IP "" 3n
+parameter\. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet\.
+.sp
+.RE
 If this parameter is not set then the name resolve order defined in the
 \fBsmb.conf\fR(5)
 file parameter (name resolve order) will be used.
+file parameter (name resolve order) will be used\.
 .sp
 The default order is lmhosts, host, wins, bcast and without this parameter or any entry in the
 …
 parameter of the
 \fBsmb.conf\fR(5)
+file the name resolution methods will be attempted in this order.
+.RE
+.PP
+-M NetBIOS name
+.RS 3n
+This options allows you to send messages, using the "WinPopup" protocol, to another computer. Once a connection is established you then type your message, pressing ^D (control-D) to end.
+.sp
+If the receiving computer is running WinPopup the user will receive the message and probably a beep. If they are not running WinPopup the message will be lost, and no error message will occur.
+.sp
+The message is also automatically truncated if the message is over 1600 bytes, as this is the limit of the protocol.
+.sp
+One useful trick is to cat the message through
+smbclient. For example:
+.sp
+.nf
+cat mymessage.txt | smbclient -M FRED
+.fi
+will send the message in the file
+\fImymessage.txt\fR
+to the machine FRED.
+file the name resolution methods will be attempted in this order\.
+.RE
+.PP
+\-M NetBIOS name
+.RS 4
+This options allows you to send messages, using the "WinPopup" protocol, to another computer\. Once a connection is established you then type your message, pressing ^D (control\-D) to end\.
+.sp
+If the receiving computer is running WinPopup the user will receive the message and probably a beep\. If they are not running WinPopup the message will be lost, and no error message will occur\.
+.sp
+The message is also automatically truncated if the message is over 1600 bytes, as this is the limit of the protocol\.
+.sp
+One useful trick is to pipe the message through
+smbclient\. For example: smbclient \-M FRED < mymessage\.txt will send the message in the file
+\fImymessage\.txt\fR
+to the machine FRED\.
 .sp
 You may also find the
 \fI-U\fR
+\fI\-U\fR
 and
 \fI-I\fR
 options useful, as they allow you to control the FROM and TO parts of the message.
+\fI\-I\fR
+options useful, as they allow you to control the FROM and TO parts of the message\.
 .sp
 See the
 …
 parameter in the
 \fBsmb.conf\fR(5)
 for a description of how to handle incoming WinPopup messages in Samba.
 .sp
 \fBNote\fR: Copy WinPopup into the startup group on your WfWg PCs if you want them to always be able to receive messages.
 .RE
 .PP
 -p port
 .RS 3n
 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
 -P
 .RS 3n
 Make queries to the external server using the machine account of the local server.
 .RE
 .PP
 -h|--help
 .RS 3n
 Print a summary of command line options.
 .RE
 .PP
 -I IP-address
 .RS 3n
+for a description of how to handle incoming WinPopup messages in Samba\.
+.sp
+\fINote\fR: Copy WinPopup into the startup group on your WfWg PCs if you want them to always be able to receive messages\.
+.RE
+.PP
+\-p 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
+\-P
+.RS 4
+Make queries to the external server using the machine account of the local server\.
+.RE
+.PP
+\-h|\-\-help
+.RS 4
+Print a summary of command line options\.
+.RE
+.PP
+\-I 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.
+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
 -E
 .RS 3n
 This parameter causes the client to write messages to the standard error stream (stderr) rather than to the standard output stream.
 .sp
 By default, the client writes messages to standard output - typically the user's tty.
 .RE
 .PP
 -L
 .RS 3n
 This option allows you to look at what services are available on a server. You use it as
 smbclient -L host
 and a list should appear. The
 \fI-I \fR
 option may be useful if your NetBIOS names don't match your TCP/IP DNS host names or if you are trying to reach a host on another network.
 .RE
 .PP
 -t terminal code
 .RS 3n
+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
+\-E
+.RS 4
+This parameter causes the client to write messages to the standard error stream (stderr) rather than to the standard output stream\.
+.sp
+By default, the client writes messages to standard output \- typically the user\'s tty\.
+.RE
+.PP
+\-L
+.RS 4
+This option allows you to look at what services are available on a server\. You use it as
+smbclient \-L host
+and a list should appear\. The
+\fI\-I \fR
+option may be useful if your NetBIOS names don\'t match your TCP/IP DNS host names or if you are trying to reach a host on another network\.
+.RE
+.PP
+\-t terminal code
+.RS 4
 This option tells
 smbclient
 how to interpret filenames coming from the remote server. Usually Asian language multibyte UNIX implementations use different character sets than SMB/CIFS servers (\fBEUC\fR
+how to interpret filenames coming from the remote server\. Usually Asian language multibyte UNIX implementations use different character sets than SMB/CIFS servers (\fIEUC\fR
 instead of
 \fB SJIS\fR
 for example). Setting this parameter will let
+\fI SJIS\fR
+for example)\. Setting this parameter will let
 smbclient
+convert between the UNIX filenames and the SMB filenames correctly. This option has not been seriously tested and may have some problems.
+.sp
+The terminal codes include CWsjis, CWeuc, CWjis7, CWjis8, CWjunet, CWhex, CWcap. This is not a complete list, check the Samba source code for the complete list.
+.RE
+.PP
+-b buffersize
+.RS 3n
+This option changes the transmit/send buffer size when getting or putting a file from/to the server. The default is 65520 bytes. Setting this value smaller (to 1200 bytes) has been observed to speed up file transfers to and from a Win9x server.
+.RE
+.PP
+-V
+.RS 3n
+Prints the program version number.
+.RE
+.PP
+-s <configuration file>
+.RS 3n
+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
+\fIsmb.conf\fR
+for more information. The default configuration file name is determined at compile time.
+.RE
+.PP
+-d|--debuglevel=level
+.RS 3n
+convert between the UNIX filenames and the SMB filenames correctly\. This option has not been seriously tested and may have some problems\.
+.sp
+The terminal codes include CWsjis, CWeuc, CWjis7, CWjis8, CWjunet, CWhex, CWcap\. This is not a complete list, check the Samba source code for the complete list\.
+.RE
+.PP
+\-b buffersize
+.RS 4
+This option changes the transmit/send buffer size when getting or putting a file from/to the server\. The default is 65520 bytes\. Setting this value smaller (to 1200 bytes) has been observed to speed up file transfers to and from a Win9x server\.
+.RE
+.PP
+\-e
+.RS 4
+This command line parameter requires the remote server support the UNIX extensions\. Request that the connection be encrypted\. This is new for Samba 3\.2 and will only work with Samba 3\.2 or above servers\. Negotiates SMB encryption using GSSAPI\. Uses the given credentials for the encryption negotiaion (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 zero.
 .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.
+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
+\fIlog level\fR
 parameter in the
+\fIsmb.conf\fR
+file.
+.RE
+.PP
+-l|--logfile=logdirectory
+.RS 3n
+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
+-N
+.RS 3n
+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
+.RS 3n
+Try to authenticate with kerberos. Only useful in an Active Directory environment.
+.RE
+.PP
+-A|--authentication-file=filename
+.RS 3n
+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
+.sp
+\fIsmb\.conf\fR
+file\.
+.RE
+.PP
+\-V
+.RS 4
+Prints the program version number\.
+.RE
+.PP
+\-s <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
+\fIsmb\.conf\fR
+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
+\-N
+.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
+.RS 4
+Try to authenticate with kerberos\. Only useful in an Active Directory environment\.
+.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
+.sp
+.RS 4
 .nf
 username = <value>
 password = <value>
 domain   = <value>
 .fi
 .sp
 Make certain that the permissions on the file restrict access from unwanted users.
 .RE
 .PP
 -U|--user=username[%password]
 .RS 3n
 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
+.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
+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
+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
+command\. To be safe always allow
 rpcclient
 to prompt for a password and type it in directly.
 .RE
 .PP
 -n <primary NetBIOS name>
 .RS 3n
 This option allows you to override the NetBIOS name that Samba uses for itself. This is identical to setting the
+to prompt for a password and type it in directly\.
+.RE
+.PP
+\-n <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
+\fInetbios name\fR
 parameter in the
 \fIsmb.conf\fR
 file. However, a command line setting will take precedence over settings in
 \fIsmb.conf\fR.
 .RE
 .PP
 -i <scope>
 .RS 3n
+\fIsmb\.conf\fR
+file\. However, a command line setting will take precedence over settings in
+\fIsmb\.conf\fR\.
+.RE
+.PP
+\-i <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
 \fBvery\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 3n
 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
 .RS 3n
 TCP socket options to set on the client socket. See the socket options parameter in the
 \fIsmb.conf\fR
 manual page for the list of valid options.
 .RE
 .PP
 -T tar options
 .RS 3n
+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
+.RS 4
+TCP socket options to set on the client socket\. See the socket options parameter in the
+\fIsmb\.conf\fR
+manual page for the list of valid options\.
+.RE
+.PP
+\-T tar options
+.RS 4
 smbclient may be used to create
 tar(1)
+compatible backups of all the files on an SMB/CIFS share. The secondary tar flags that can be given to this option are :
+.RS 3n
+.TP 3n
+\(bu
+compatible backups of all the files on an SMB/CIFS share\. The secondary tar flags that can be given to this option are :
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fIc\fR
 - Create a tar file on UNIX. Must be followed by the name of a tar file, tape device or "-" for standard output. If using standard output you must turn the log level to its lowest value -d0 to avoid corrupting your tar file. This flag is mutually exclusive with the
+\- Create a tar file on UNIX\. Must be followed by the name of a tar file, tape device or "\-" for standard output\. If using standard output you must turn the log level to its lowest value \-d0 to avoid corrupting your tar file\. This flag is mutually exclusive with the
 \fIx\fR
+flag.
+.TP 3n
+\(bu
+flag\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fIx\fR
 - Extract (restore) a local tar file back to a share. Unless the -D option is given, the tar files will be restored from the top level of the share. Must be followed by the name of the tar file, device or "-" for standard input. Mutually exclusive with the
+\- Extract (restore) a local tar file back to a share\. Unless the \-D option is given, the tar files will be restored from the top level of the share\. Must be followed by the name of the tar file, device or "\-" for standard input\. Mutually exclusive with the
 \fIc\fR
+flag. Restored files have their creation times (mtime) set to the date saved in the tar file. Directories currently do not get their creation dates restored properly.
+.TP 3n
+\(bu
+flag\. Restored files have their creation times (mtime) set to the date saved in the tar file\. Directories currently do not get their creation dates restored properly\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fII\fR
 - Include files and directories. Is the default behavior when filenames are specified above. Causes files to be included in an extract or create (and therefore everything else to be excluded). See example below. Filename globbing works in one of two ways. See
+\- Include files and directories\. Is the default behavior when filenames are specified above\. Causes files to be included in an extract or create (and therefore everything else to be excluded)\. See example below\. Filename globbing works in one of two ways\. See
 \fIr\fR
+below.
+.TP 3n
+\(bu
+below\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fIX\fR
 - Exclude files and directories. Causes files to be excluded from an extract or create. See example below. Filename globbing works in one of two ways now. See
+\- Exclude files and directories\. Causes files to be excluded from an extract or create\. See example below\. Filename globbing works in one of two ways now\. See
 \fIr\fR
+below.
+.TP 3n
+\(bu
+below\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fIF\fR
 - File containing a list of files and directories. The
+\- File containing a list of files and directories\. The
 \fIF\fR
 causes the name following the tarfile to create to be read as a filename that contains a list of files and directories to be included in an extract or create (and therefore everything else to be excluded). See example below. Filename globbing works in one of two ways. See
+causes the name following the tarfile to create to be read as a filename that contains a list of files and directories to be included in an extract or create (and therefore everything else to be excluded)\. See example below\. Filename globbing works in one of two ways\. See
 \fIr\fR
+below.
+.TP 3n
+\(bu
+below\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fIb\fR
+- Blocksize. Must be followed by a valid (greater than zero) blocksize. Causes tar file to be written out in blocksize*TBLOCK (usually 512 byte) blocks.
+.TP 3n
+\(bu
+\- Blocksize\. Must be followed by a valid (greater than zero) blocksize\. Causes tar file to be written out in blocksize*TBLOCK (usually 512 byte) blocks\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fIg\fR
 - Incremental. Only back up files that have the archive bit set. Useful only with the
+\- Incremental\. Only back up files that have the archive bit set\. Useful only with the
 \fIc\fR
+flag.
+.TP 3n
+\(bu
+flag\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fIq\fR
+- Quiet. Keeps tar from printing diagnostics as it works. This is the same as tarmode quiet.
+.TP 3n
+\(bu
+\- Quiet\. Keeps tar from printing diagnostics as it works\. This is the same as tarmode quiet\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fIr\fR
+- Regular expression include or exclude. Uses regular expression matching for excluding or excluding files if compiled with HAVE_REGEX_H. However this mode can be very slow. If not compiled with HAVE_REGEX_H, does a limited wildcard match on '*' and '?'.
+.TP 3n
+\(bu
+\- Regular expression include or exclude\. Uses regular expression matching for excluding or excluding files if compiled with HAVE_REGEX_H\. However this mode can be very slow\. If not compiled with HAVE_REGEX_H, does a limited wildcard match on \'*\' and \'?\'\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fIN\fR
 - Newer than. Must be followed by the name of a file whose date is compared against files found on the share during a create. Only files newer than the file specified are backed up to the tar file. Useful only with the
+\- Newer than\. Must be followed by the name of a file whose date is compared against files found on the share during a create\. Only files newer than the file specified are backed up to the tar file\. Useful only with the
 \fIc\fR
+flag.
+.TP 3n
+\(bu
+flag\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fIa\fR
 - Set archive bit. Causes the archive bit to be reset when a file is backed up. Useful with the
+\- Set archive bit\. Causes the archive bit to be reset when a file is backed up\. Useful with the
 \fIg\fR
 and
 \fIc\fR
 flags.
 .RE
 .IP "" 3n
 \fBTar Long File Names\fR
 .sp
 smbclient's tar option now supports long file names both on backup and restore. However, the full path name of the file must be less than 1024 bytes. Also, when a tar archive is created,
 smbclient's tar option places all files in the archive with relative names, not absolute names.
 .sp
 \fBTar Filenames\fR
 .sp
 All file names can be given as DOS path names (with '\\' as the component separator) or as UNIX path names (with '/' as the component separator).
 .sp
 \fBExamples\fR
+flags\.
+.sp
+.RE
+\fITar Long File Names\fR
+.sp
+smbclient\'s tar option now supports long file names both on backup and restore\. However, the full path name of the file must be less than 1024 bytes\. Also, when a tar archive is created,
+smbclient\'s tar option places all files in the archive with relative names, not absolute names\.
+.sp
+\fITar Filenames\fR
+.sp
+All file names can be given as DOS path names (with \'\e\e\' as the component separator) or as UNIX path names (with \'/\' as the component separator)\.
+.sp
+\fIExamples\fR
 .sp
 Restore from tar file
 \fIbackup.tar\fR
 into myshare on mypc (no password on share).
 .sp
 smbclient //mypc/yshare "" -N -Tx backup.tar
+\fIbackup\.tar\fR
+into myshare on mypc (no password on share)\.
+.sp
+smbclient //mypc/yshare "" \-N \-Tx backup\.tar
 .sp
 Restore everything except
 \fIusers/docs\fR
 .sp
 smbclient //mypc/myshare "" -N -TXx backup.tar users/docs
+smbclient //mypc/myshare "" \-N \-TXx backup\.tar users/docs
 .sp
 Create a tar file of the files beneath
 \fI users/docs\fR.
 .sp
 smbclient //mypc/myshare "" -N -Tc backup.tar users/docs
 .sp
 Create the same tar file as above, but now use a DOS path name.
 .sp
 smbclient //mypc/myshare "" -N -tc backup.tar users\\edocs
+\fI users/docs\fR\.
+.sp
+smbclient //mypc/myshare "" \-N \-Tc backup\.tar users/docs
+.sp
+Create the same tar file as above, but now use a DOS path name\.
+.sp
+smbclient //mypc/myshare "" \-N \-tc backup\.tar users\eedocs
 .sp
 Create a tar file of the files listed in the file
 \fItarlist\fR.
 .sp
 smbclient //mypc/myshare "" -N -TcF backup.tar tarlist
 .sp
 Create a tar file of all the files and directories in the share.
 .sp
 smbclient //mypc/myshare "" -N -Tc backup.tar *
 .RE
 .PP
 -D initial directory
 .RS 3n
 Change to initial directory before starting. Probably only of any use with the tar -T option.
 .RE
 .PP
 -c command string
 .RS 3n
 command string is a semicolon-separated list of commands to be executed instead of prompting from stdin.
 \fI -N\fR
+\fItarlist\fR\.
+.sp
+smbclient //mypc/myshare "" \-N \-TcF backup\.tar tarlist
+.sp
+Create a tar file of all the files and directories in the share\.
+.sp
+smbclient //mypc/myshare "" \-N \-Tc backup\.tar *
+.RE
+.PP
+\-D initial directory
+.RS 4
+Change to initial directory before starting\. Probably only of any use with the tar \-T option\.
+.RE
+.PP
+\-c command string
+.RS 4
+command string is a semicolon\-separated list of commands to be executed instead of prompting from stdin\.
+\fI \-N\fR
 is implied by
 \fI-c\fR.
 .sp
 This is particularly useful in scripts and for printing stdin to the server, e.g.
 -c 'print -'.
+\fI\-c\fR\.
+.sp
+This is particularly useful in scripts and for printing stdin to the server, e\.g\.
+\-c \'print \-\'\.
 .RE
 .SH "OPERATIONS"
 …
 Once the client is running, the user is presented with a prompt :
 .PP
 smb:\>
 .PP
 The backslash ("\\") indicates the current working directory on the server, and will change if the current working directory is changed.
 .PP
 The prompt indicates that the client is ready and waiting to carry out a user command. Each command is a single word, optionally followed by parameters specific to that command. Command and parameters are space-delimited unless these notes specifically state otherwise. All commands are case-insensitive. Parameters to commands may or may not be case sensitive, depending on the command.
 .PP
 You can specify file names which have spaces in them by quoting the name with double quotes, for example "a long file name".
 .PP
 Parameters shown in square brackets (e.g., "[parameter]") are optional. If not given, the command will use suitable defaults. Parameters shown in angle brackets (e.g., "<parameter>") are required.
 .PP
 Note that all commands operating on the server are actually performed by issuing a request to the server. Thus the behavior may vary from server to server, depending on how the server was implemented.
 .PP
 The commands available are given here in alphabetical order.
+smb:\e>
+.PP
+The backslash ("\e\e") indicates the current working directory on the server, and will change if the current working directory is changed\.
+.PP
+The prompt indicates that the client is ready and waiting to carry out a user command\. Each command is a single word, optionally followed by parameters specific to that command\. Command and parameters are space\-delimited unless these notes specifically state otherwise\. All commands are case\-insensitive\. Parameters to commands may or may not be case sensitive, depending on the command\.
+.PP
+You can specify file names which have spaces in them by quoting the name with double quotes, for example "a long file name"\.
+.PP
+Parameters shown in square brackets (e\.g\., "[parameter]") are optional\. If not given, the command will use suitable defaults\. Parameters shown in angle brackets (e\.g\., "<parameter>") are required\.
+.PP
+Note that all commands operating on the server are actually performed by issuing a request to the server\. Thus the behavior may vary from server to server, depending on how the server was implemented\.
+.PP
+The commands available are given here in alphabetical order\.
 .PP
 ? [command]
 .RS 3n
+.RS 4
 If
 \fIcommand\fR
 is specified, the ? command will display a brief informative message about the specified command. If no command is specified, a list of available commands will be displayed.
+is specified, the ? command will display a brief informative message about the specified command\. If no command is specified, a list of available commands will be displayed\.
 .RE
 .PP
 ! [shell command]
 .RS 3n
+.RS 4
 If
 \fIshell command\fR
+is specified, the ! command will execute a shell locally and run the specified shell command. If no command is specified, a local shell will be run.
+is specified, the ! command will execute a shell locally and run the specified shell command\. If no command is specified, a local shell will be run\.
+.RE
+.PP
+allinfo file
+.RS 4
+The client will request that the server return all known information about a file or directory (including streams)\.
 .RE
 .PP
 altname file
+.RS 3n
+The client will request that the server return the "alternate" name (the 8.3 name) for a file or directory.
+.RS 4
+The client will request that the server return the "alternate" name (the 8\.3 name) for a file or directory\.
+.RE
+.PP
+archive <number>
+.RS 4
+Sets the archive level when operating on files\. 0 means ignore the archive bit, 1 means only operate on files with this bit set, 2 means only operate on files with this bit set and reset it after operation, 3 means operate on all files and reset it after operation\. The default is 0\.
+.RE
+.PP
+blocksize <number>
+.RS 4
+Sets the blocksize parameter for a tar operation\. The default is 20\. Causes tar file to be written out in blocksize*TBLOCK (normally 512 byte) units\.
+.RE
+.PP
+cancel jobid0 [jobid1] \.\.\. [jobidN]
+.RS 4
+The client will request that the server cancel the printjobs identified by the given numeric print job ids\.
 .RE
 .PP
 case_sensitive
+.RS 3n
+Toggles the setting of the flag in SMB packets that tells the server to treat filenames as case sensitive. Set to OFF by default (tells file server to treat filenames as case insensitive). Only currently affects Samba 3.0.5 and above file servers with the case sensitive parameter set to auto in the smb.conf.
+.RE
+.PP
+cancel jobid0 [jobid1] ... [jobidN]
+.RS 3n
+The client will request that the server cancel the printjobs identified by the given numeric print job ids.
+.RS 4
+Toggles the setting of the flag in SMB packets that tells the server to treat filenames as case sensitive\. Set to OFF by default (tells file server to treat filenames as case insensitive)\. Only currently affects Samba 3\.0\.5 and above file servers with the case sensitive parameter set to auto in the smb\.conf\.
+.RE
+.PP
+cd <directory name>
+.RS 4
+If "directory name" is specified, the current working directory on the server will be changed to the directory specified\. This operation will fail if for any reason the specified directory is inaccessible\.
+.sp
+If no directory name is specified, the current working directory on the server will be reported\.
 .RE
 .PP
 chmod file mode in octal
 .RS 3n
 This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not. The client requests that the server change the UNIX permissions to the given octal mode, in standard UNIX format.
+.RS 4
+This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not\. The client requests that the server change the UNIX permissions to the given octal mode, in standard UNIX format\.
 .RE
 .PP
 chown file uid gid
+.RS 3n
+This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not. The client requests that the server change the UNIX user and group ownership to the given decimal values. Note there is currently no way to remotely look up the UNIX uid and gid values for a given name. This may be addressed in future versions of the CIFS UNIX extensions.
+.RE
+.PP
+cd [directory name]
+.RS 3n
+If "directory name" is specified, the current working directory on the server will be changed to the directory specified. This operation will fail if for any reason the specified directory is inaccessible.
+.sp
+If no directory name is specified, the current working directory on the server will be reported.
+.RS 4
+This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not\. The client requests that the server change the UNIX user and group ownership to the given decimal values\. Note there is currently no way to remotely look up the UNIX uid and gid values for a given name\. This may be addressed in future versions of the CIFS UNIX extensions\.
+.RE
+.PP
+close <fileid>
+.RS 4
+Closes a file explicitly opened by the open command\. Used for internal Samba testing purposes\.
 .RE
 .PP
 del <mask>
 .RS 3n
+.RS 4
 The client will request that the server attempt to delete all files matching
 \fImask\fR
 from the current working directory on the server.
+from the current working directory on the server\.
 .RE
 .PP
 dir <mask>
 .RS 3n
+.RS 4
 A list of the files matching
 \fImask\fR
+in the current working directory on the server will be retrieved from the server and displayed.
+in the current working directory on the server will be retrieved from the server and displayed\.
+.RE
+.PP
+du <filename>
+.RS 4
+Does a directory listing and then prints out the current disk useage and free space on a share\.
+.RE
+.PP
+echo <number> <data>
+.RS 4
+Does an SMBecho request to ping the server\. Used for internal Samba testing purposes\.
 .RE
 .PP
 exit
 .RS 3n
 Terminate the connection with the server and exit from the program.
+.RS 4
+Terminate the connection with the server and exit from the program\.
 .RE
 .PP
 get <remote file name> [local file name]
 .RS 3n
+.RS 4
 Copy the file called
 \fIremote file name\fR
 from the server to the machine running the client. If specified, name the local copy
 \fIlocal file name\fR. Note that all transfers in
+from the server to the machine running the client\. If specified, name the local copy
+\fIlocal file name\fR\. Note that all transfers in
 smbclient
+are binary. See also the lowercase command.
+are binary\. See also the lowercase command\.
+.RE
+.PP
+getfacl <filename>
+.RS 4
+Requires the server support the UNIX extensions\. Requests and prints the POSIX ACL on a file\.
+.RE
+.PP
+hardlink <src> <dest<
+.RS 4
+Creates a hardlink on the server using Windows CIFS semantics\. the POSIX ACL on a file\.
 .RE
 .PP
 help [command]
+.RS 3n
+See the ? command above.
+.RS 4
+See the ? command above\.
+.RE
+.PP
+history
+.RS 4
+Displays the command history\.
+.RE
+.PP
+iosize <bytes>
+.RS 4
+When sending or receiving files, smbclient uses an internal memory buffer by default of size 64512 bytes\. This command allows this size to be set to any range between 16384 (0x4000) bytes and 16776960 (0xFFFF00) bytes\. Larger sizes may mean more efficient data transfer as smbclient will try and use the most efficient read and write calls for the connected server\.
 .RE
 .PP
 lcd [directory name]
 .RS 3n
+.RS 4
 If
 \fIdirectory name\fR
 is specified, the current working directory on the local machine will be changed to the directory specified. This operation will fail if for any reason the specified directory is inaccessible.
 .sp
 If no directory name is specified, the name of the current working directory on the local machine will be reported.
+is specified, the current working directory on the local machine will be changed to the directory specified\. This operation will fail if for any reason the specified directory is inaccessible\.
+.sp
+If no directory name is specified, the name of the current working directory on the local machine will be reported\.
 .RE
 .PP
 link target linkname
+.RS 3n
+This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not. The client requests that the server create a hard link between the linkname and target files. The linkname file must not exist.
+.RS 4
+This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not\. The client requests that the server create a hard link between the linkname and target files\. The linkname file must not exist\.
+.RE
+.PP
+listconnect
+.RS 4
+Show the current connections held for DFS purposes\.
+.RE
+.PP
+lock <filenum> <r|w> <hex\-start> <hex\-len>
+.RS 4
+This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not\. Tries to set a POSIX fcntl lock of the given type on the given range\. Used for internal Samba testing purposes\.
+.RE
+.PP
+logon <username> <password>
+.RS 4
+Establishes a new vuid for this session by logging on again\. Replaces the current vuid\. Prints out the new vuid\. Used for internal Samba testing purposes\.
 .RE
 .PP
 lowercase
 .RS 3n
 Toggle lowercasing of filenames for the get and mget commands.
 .sp
 When lowercasing is toggled ON, local filenames are converted to lowercase when using the get and mget commands. This is often useful when copying (say) MSDOS files from a server, because lowercase filenames are the norm on UNIX systems.
+.RS 4
+Toggle lowercasing of filenames for the get and mget commands\.
+.sp
+When lowercasing is toggled ON, local filenames are converted to lowercase when using the get and mget commands\. This is often useful when copying (say) MSDOS files from a server, because lowercase filenames are the norm on UNIX systems\.
 .RE
 .PP
 ls <mask>
 .RS 3n
 See the dir command above.
+.RS 4
+See the dir command above\.
 .RE
 .PP
 mask <mask>
 .RS 3n
 This command allows the user to set up a mask which will be used during recursive operation of the mget and mput commands.
 .sp
 The masks specified to the mget and mput commands act as filters for directories rather than files when recursion is toggled ON.
 .sp
 The mask specified with the mask command is necessary to filter files within those directories. For example, if the mask specified in an mget command is "source*" and the mask specified with the mask command is "*.c" and recursion is toggled ON, the mget command will retrieve all files matching "*.c" in all directories below and including all directories matching "source*" in the current working directory.
 .sp
 Note that the value for mask defaults to blank (equivalent to "*") and remains so until the mask command is used to change it. It retains the most recently specified value indefinitely. To avoid unexpected results it would be wise to change the value of mask back to "*" after using the mget or mput commands.
+.RS 4
+This command allows the user to set up a mask which will be used during recursive operation of the mget and mput commands\.
+.sp
+The masks specified to the mget and mput commands act as filters for directories rather than files when recursion is toggled ON\.
+.sp
+The mask specified with the mask command is necessary to filter files within those directories\. For example, if the mask specified in an mget command is "source*" and the mask specified with the mask command is "*\.c" and recursion is toggled ON, the mget command will retrieve all files matching "*\.c" in all directories below and including all directories matching "source*" in the current working directory\.
+.sp
+Note that the value for mask defaults to blank (equivalent to "*") and remains so until the mask command is used to change it\. It retains the most recently specified value indefinitely\. To avoid unexpected results it would be wise to change the value of mask back to "*" after using the mget or mput commands\.
 .RE
 .PP
 md <directory name>
 .RS 3n
 See the mkdir command.
+.RS 4
+See the mkdir command\.
 .RE
 .PP
 mget <mask>
 .RS 3n
+.RS 4
 Copy all files matching
 \fImask\fR
 from the server to the machine running the client.
+from the server to the machine running the client\.
 .sp
 Note that
 \fImask\fR
 is interpreted differently during recursive operation and non-recursive operation - refer to the recurse and mask commands for more information. Note that all transfers in
+is interpreted differently during recursive operation and non\-recursive operation \- refer to the recurse and mask commands for more information\. Note that all transfers in
 smbclient
 are binary. See also the lowercase command.
+are binary\. See also the lowercase command\.
 .RE
 .PP
 mkdir <directory name>
+.RS 3n
+Create a new directory on the server (user access privileges permitting) with the specified name.
+.RS 4
+Create a new directory on the server (user access privileges permitting) with the specified name\.
+.RE
+.PP
+more <file name>
+.RS 4
+Fetch a remote file and view it with the contents of your PAGER environment variable\.
 .RE
 .PP
 mput <mask>
 .RS 3n
+.RS 4
 Copy all files matching
 \fImask\fR
 in the current working directory on the local machine to the current working directory on the server.
+in the current working directory on the local machine to the current working directory on the server\.
 .sp
 Note that
 \fImask\fR
 is interpreted differently during recursive operation and non-recursive operation - refer to the recurse and mask commands for more information. Note that all transfers in
+is interpreted differently during recursive operation and non\-recursive operation \- refer to the recurse and mask commands for more information\. Note that all transfers in
 smbclient
+are binary.
+are binary\.
+.RE
+.PP
+posix
+.RS 4
+Query the remote server to see if it supports the CIFS UNIX extensions and prints out the list of capabilities supported\. If so, turn on POSIX pathname processing and large file read/writes (if available),\.
+.RE
+.PP
+posix_encrypt <domain> <username> <password>
+.RS 4
+This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not\. Attempt to negotiate SMB encryption on this connection\. If smbclient connected with kerberos credentials (\-k) the arguments to this command are ignored and the kerberos credentials are used to negotiate GSSAPI signing and sealing instead\. See also the \-e option to smbclient to force encryption on initial connection\. This command is new with Samba 3\.2\.
+.RE
+.PP
+posix_open <filename> <octal mode>
+.RS 4
+This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not\. Opens a remote file using the CIFS UNIX extensions and prints a fileid\. Used for internal Samba testing purposes\.
+.RE
+.PP
+posix_mkdir <directoryname> <octal mode>
+.RS 4
+This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not\. Creates a remote directory using the CIFS UNIX extensions with the given mode\.
+.RE
+.PP
+posix_rmdir <directoryname>
+.RS 4
+This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not\. Deletes a remote directory using the CIFS UNIX extensions\.
+.RE
+.PP
+posix_unlink <filename>
+.RS 4
+This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not\. Deletes a remote file using the CIFS UNIX extensions\.
 .RE
 .PP
 print <file name>
 .RS 3n
 Print the specified file from the local machine through a printable service on the server.
+.RS 4
+Print the specified file from the local machine through a printable service on the server\.
 .RE
 .PP
 prompt
 .RS 3n
 Toggle prompting for filenames during operation of the mget and mput commands.
 .sp
 When toggled ON, the user will be prompted to confirm the transfer of each file during these commands. When toggled OFF, all specified files will be transferred without prompting.
+.RS 4
+Toggle prompting for filenames during operation of the mget and mput commands\.
+.sp
+When toggled ON, the user will be prompted to confirm the transfer of each file during these commands\. When toggled OFF, all specified files will be transferred without prompting\.
 .RE
 .PP
 put <local file name> [remote file name]
 .RS 3n
+.RS 4
 Copy the file called
 \fIlocal file name\fR
 from the machine running the client to the server. If specified, name the remote copy
 \fIremote file name\fR. Note that all transfers in
+from the machine running the client to the server\. If specified, name the remote copy
+\fIremote file name\fR\. Note that all transfers in
 smbclient
 are binary. See also the lowercase command.
+are binary\. See also the lowercase command\.
 .RE
 .PP
 queue
 .RS 3n
 Displays the print queue, showing the job id, name, size and current status.
+.RS 4
+Displays the print queue, showing the job id, name, size and current status\.
 .RE
 .PP
 quit
 .RS 3n
 See the exit command.
+.RS 4
+See the exit command\.
 .RE
 .PP
 rd <directory name>
 .RS 3n
 See the rmdir command.
+.RS 4
+See the rmdir command\.
 .RE
 .PP
 recurse
 .RS 3n
 Toggle directory recursion for the commands mget and mput.
 .sp
 When toggled ON, these commands will process all directories in the source directory (i.e., the directory they are copying from ) and will recurse into any that match the mask specified to the command. Only files that match the mask specified using the mask command will be retrieved. See also the mask command.
 .sp
 When recursion is toggled OFF, only files from the current working directory on the source machine that match the mask specified to the mget or mput commands will be copied, and any mask specified using the mask command will be ignored.
+.RS 4
+Toggle directory recursion for the commands mget and mput\.
+.sp
+When toggled ON, these commands will process all directories in the source directory (i\.e\., the directory they are copying from ) and will recurse into any that match the mask specified to the command\. Only files that match the mask specified using the mask command will be retrieved\. See also the mask command\.
+.sp
+When recursion is toggled OFF, only files from the current working directory on the source machine that match the mask specified to the mget or mput commands will be copied, and any mask specified using the mask command will be ignored\.
 .RE
 .PP
 rm <mask>
 .RS 3n
+.RS 4
 Remove all files matching
 \fImask\fR
 from the current working directory on the server.
+from the current working directory on the server\.
 .RE
 .PP
 rmdir <directory name>
 .RS 3n
 Remove the specified directory (user access privileges permitting) from the server.
 .RE
 .PP
 setmode <filename> <perm=[+|\-]rsha>
 .RS 3n
 A version of the DOS attrib command to set file permissions. For example:
+.RS 4
+Remove the specified directory (user access privileges permitting) from the server\.
+.RE
+.PP
+setmode <filename> <perm=[+|\e\-]rsha>
+.RS 4
+A version of the DOS attrib command to set file permissions\. For example:
 .sp
 setmode myfile +r
 .sp
+would make myfile read only.
+would make myfile read only\.
+.RE
+.PP
+showconnect
+.RS 4
+Show the currently active connection held for DFS purposes\.
 .RE
 .PP
 stat file
 .RS 3n
 This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not. The client requests the UNIX basic info level and prints out the same info that the Linux stat command would about the file. This includes the size, blocks used on disk, file type, permissions, inode number, number of links and finally the three timestamps (access, modify and change). If the file is a special file (symlink, character or block device, fifo or socket) then extra information may also be printed.
+.RS 4
+This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not\. The client requests the UNIX basic info level and prints out the same info that the Linux stat command would about the file\. This includes the size, blocks used on disk, file type, permissions, inode number, number of links and finally the three timestamps (access, modify and change)\. If the file is a special file (symlink, character or block device, fifo or socket) then extra information may also be printed\.
 .RE
 .PP
 symlink target linkname
 .RS 3n
 This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not. The client requests that the server create a symbolic hard link between the target and linkname files. The linkname file must not exist. Note that the server will not create a link to any path that lies outside the currently connected share. This is enforced by the Samba server.
+.RS 4
+This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not\. The client requests that the server create a symbolic hard link between the target and linkname files\. The linkname file must not exist\. Note that the server will not create a link to any path that lies outside the currently connected share\. This is enforced by the Samba server\.
 .RE
 .PP
 tar <c|x>[IXbgNa]
 .RS 3n
 Performs a tar operation - see the
 \fI-T \fR
 command line option above. Behavior may be affected by the tarmode command (see below). Using g (incremental) and N (newer) will affect tarmode settings. Note that using the "-" option with tar x may not work - use the command line option instead.
+.RS 4
+Performs a tar operation \- see the
+\fI\-T \fR
+command line option above\. Behavior may be affected by the tarmode command (see below)\. Using g (incremental) and N (newer) will affect tarmode settings\. Note that using the "\-" option with tar x may not work \- use the command line option instead\.
 .RE
 .PP
 blocksize <blocksize>
 .RS 3n
 Blocksize. Must be followed by a valid (greater than zero) blocksize. Causes tar file to be written out in
 \fIblocksize\fR*TBLOCK (usually 512 byte) blocks.
+.RS 4
+Blocksize\. Must be followed by a valid (greater than zero) blocksize\. Causes tar file to be written out in
+\fIblocksize\fR*TBLOCK (usually 512 byte) blocks\.
 .RE
 .PP
 tarmode <full|inc|reset|noreset>
+.RS 3n
+Changes tar's behavior with regard to archive bits. In full mode, tar will back up everything regardless of the archive bit setting (this is the default mode). In incremental mode, tar will only back up files with the archive bit set. In reset mode, tar will reset the archive bit on all files it backs up (implies read/write share).
+.RS 4
+Changes tar\'s behavior with regard to archive bits\. In full mode, tar will back up everything regardless of the archive bit setting (this is the default mode)\. In incremental mode, tar will only back up files with the archive bit set\. In reset mode, tar will reset the archive bit on all files it backs up (implies read/write share)\.
+.RE
+.PP
+unlock <filenum> <hex\-start> <hex\-len>
+.RS 4
+This command depends on the server supporting the CIFS UNIX extensions and will fail if the server does not\. Tries to unlock a POSIX fcntl lock on the given range\. Used for internal Samba testing purposes\.
+.RE
+.PP
+volume
+.RS 4
+Prints the current volume name of the share\.
+.RE
+.PP
+vuid <number>
+.RS 4
+Changes the currently used vuid in the protocol to the given arbitrary number\. Without an argument prints out the current vuid being used\. Used for internal Samba testing purposes\.
 .RE
 .SH "NOTES"
 .PP
 Some servers are fussy about the case of supplied usernames, passwords, share names (AKA service names) and machine names. If you fail to connect try giving all parameters in uppercase.
 .PP
 It is often necessary to use the -n option when connecting to some types of servers. For example OS/2 LanManager insists on a valid NetBIOS name being used, so you need to supply a valid name that would be known to the server.
 .PP
 smbclient supports long file names where the server supports the LANMAN2 protocol or above.
+Some servers are fussy about the case of supplied usernames, passwords, share names (AKA service names) and machine names\. If you fail to connect try giving all parameters in uppercase\.
+.PP
+It is often necessary to use the \-n option when connecting to some types of servers\. For example OS/2 LanManager insists on a valid NetBIOS name being used, so you need to supply a valid name that would be known to the server\.
+.PP
+smbclient supports long file names where the server supports the LANMAN2 protocol or above\.
 .SH "ENVIRONMENT VARIABLES"
 .PP
 The variable
 \fBUSER\fR
 may contain the username of the person using the client. This information is used only if the protocol level is high enough to support session-level passwords.
+may contain the username of the person using the client\. This information is used only if the protocol level is high enough to support session\-level passwords\.
 .PP
 The variable
 \fBPASSWD\fR
 may contain the password of the person using the client. This information is used only if the protocol level is high enough to support session-level passwords.
+may contain the password of the person using the client\. This information is used only if the protocol level is high enough to support session\-level passwords\.
 .PP
 The variable
 \fBLIBSMB_PROG\fR
 may contain the path, executed with system(), which the client should connect to instead of connecting to a server. This functionality is primarily intended as a development aid, and works best when using a LMHOSTS file
+may contain the path, executed with system(), which the client should connect to instead of connecting to a server\. This functionality is primarily intended as a development aid, and works best when using a LMHOSTS file
 .SH "INSTALLATION"
 .PP
 The location of the client program is a matter for individual system administrators. The following are thus suggestions only.
+The location of the client program is a matter for individual system administrators\. The following are thus suggestions only\.
 .PP
 It is recommended that the smbclient software be installed in the
 …
 or
 \fI /usr/samba/bin/\fR
 directory, this directory readable by all, writeable only by root. The client program itself should be executable by all. The client should
 \fBNOT\fR
+directory, this directory readable by all, writeable only by root\. The client program itself should be executable by all\. The client should
+\fINOT\fR
 be setuid or setgid!
 .PP
 The client log files should be put in a directory readable and writeable only by the user.
 .PP
 To test the client, you will need to know the name of a running SMB/CIFS server. It is possible to run
+The client log files should be put in a directory readable and writeable only by the user\.
+.PP
+To test the client, you will need to know the name of a running SMB/CIFS server\. It is possible to run
 \fBsmbd\fR(8)
 as an ordinary user - running that server as a daemon on a user-accessible port (typically any port number over 1024) would provide a suitable test server.
+as an ordinary user \- running that server as a daemon on a user\-accessible port (typically any port number over 1024) would provide a suitable test server\.
 .SH "DIAGNOSTICS"
 .PP
 Most diagnostics issued by the client 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 client. If you have problems, set the debug level to 3 and peruse the log files.
+Most diagnostics issued by the client 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 client\. If you have problems, set the debug level to 3 and peruse the log files\.
 .SH "VERSION"
 .PP
 This man page is correct for version 3 of the Samba suite.
+This man page is correct for version 3\.2 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 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.
+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\.

branches/samba-3.0/docs/manpages/smbcontrol.1

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "SMBCONTROL" 1 "" "" ""
+.\"     Title: smbcontrol
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: User Commands
+.\"    Source: Samba 3.0
+.\"
+.TH "SMBCONTROL" "1" "05/21/2008" "Samba 3\.0" "User Commands"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 smbcontrol - send messages to smbd, nmbd or winbindd processes
 .SH "SYNOPSIS"
 .HP 1
 smbcontrol [-i] [-s]
+smbcontrol [\-i] [\-s]
 .HP 1
 smbcontrol [destination] [message-type] [parameter]
+smbcontrol [destination] [message\-type] [parameter]
 .SH "DESCRIPTION"
 .PP
 This tool is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 smbcontrol
 …
 \fBnmbd\fR(8), or a
 \fBwinbindd\fR(8)
 daemon running on the system.
+daemon running on the system\.
 .SH "OPTIONS"
 .PP
 -h|--help
 .RS 3n
 Print a summary of command line options.
 .RE
 .PP
 -s <configuration file>
 .RS 3n
 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
 \fIsmb.conf\fR
 for more information. The default configuration file name is determined at compile time.
 .RE
 .PP
 -i
 .RS 3n
 Run interactively. Individual commands of the form destination message-type parameters can be entered on STDIN. An empty command line or a "q" will quit the program.
+\-h|\-\-help
+.RS 4
+Print a summary of command line options\.
+.RE
+.PP
+\-s <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
+\fIsmb\.conf\fR
+for more information\. The default configuration file name is determined at compile time\.
+.RE
+.PP
+\-i
+.RS 4
+Run interactively\. Individual commands of the form destination message\-type parameters can be entered on STDIN\. An empty command line or a "q" will quit the program\.
 .RE
 .PP
 destination
 .RS 3n
+.RS 4
 One of
 \fInmbd\fR,
 \fIsmbd\fR
 or a process ID.
+or a process ID\.
 .sp
 The
 \fIsmbd\fR
 destination causes the message to "broadcast" to all smbd daemons.
+destination causes the message to "broadcast" to all smbd daemons\.
 .sp
 The
 \fInmbd\fR
 destination causes the message to be sent to the nmbd daemon specified in the
 \fInmbd.pid\fR
 file.
 .sp
 If a single process ID is given, the message is sent to only that process.
 .RE
 .PP
 message-type
 .RS 3n
 Type of message to send. See the section
 \fBMESSAGE-TYPES\fR
 for details.
+\fInmbd\.pid\fR
+file\.
+.sp
+If a single process ID is given, the message is sent to only that process\.
+.RE
+.PP
+message\-type
+.RS 4
+Type of message to send\. See the section
+\fBMESSAGE\-TYPES\fR
+for details\.
 .RE
 .PP
 parameters
 .RS 3n
 any parameters required for the message-type
+.RS 4
+any parameters required for the message\-type
 .RE
 .SH "MESSAGE-TYPES"
 …
 Available message types are:
 .PP
 close-share
 .RS 3n
 Order smbd to close the client connections to the named share. Note that this doesn't affect client connections to any other shares. This message-type takes an argument of the share name for which client connections will be closed, or the "*" character which will close all currently open shares. This may be useful if you made changes to the access controls on the share. This message can only be sent to
 \fBsmbd\fR.
+close\-share
+.RS 4
+Order smbd to close the client connections to the named share\. Note that this doesn\'t affect client connections to any other shares\. This message\-type takes an argument of the share name for which client connections will be closed, or the "*" character which will close all currently open shares\. This may be useful if you made changes to the access controls on the share\. This message can only be sent to
+\fBsmbd\fR\.
 .RE
 .PP
 debug
 .RS 3n
 Set debug level to the value specified by the parameter. This can be sent to any of the destinations.
 .RE
 .PP
 force-election
 .RS 3n
+.RS 4
+Set debug level to the value specified by the parameter\. This can be sent to any of the destinations\.
+.RE
+.PP
+force\-election
+.RS 4
 This message causes the
 nmbd
 daemon to force a new browse master election.
+daemon to force a new browse master election\.
 .RE
 .PP
 ping
 .RS 3n
 Send specified number of "ping" messages and wait for the same number of reply "pong" messages. This can be sent to any of the destinations.
+.RS 4
+Send specified number of "ping" messages and wait for the same number of reply "pong" messages\. This can be sent to any of the destinations\.
 .RE
 .PP
 profile
 .RS 3n
 Change profile settings of a daemon, based on the parameter. The parameter can be "on" to turn on profile stats collection, "off" to turn off profile stats collection, "count" to enable only collection of count stats (time stats are disabled), and "flush" to zero the current profile stats. This can be sent to any smbd or nmbd destinations.
+.RS 4
+Change profile settings of a daemon, based on the parameter\. The parameter can be "on" to turn on profile stats collection, "off" to turn off profile stats collection, "count" to enable only collection of count stats (time stats are disabled), and "flush" to zero the current profile stats\. This can be sent to any smbd or nmbd destinations\.
 .RE
 .PP
 debuglevel
 .RS 3n
 Request debuglevel of a certain daemon and write it to stdout. This can be sent to any of the destinations.
+.RS 4
+Request debuglevel of a certain daemon and write it to stdout\. This can be sent to any of the destinations\.
 .RE
 .PP
 profilelevel
 .RS 3n
 Request profilelevel of a certain daemon and write it to stdout. This can be sent to any smbd or nmbd destinations.
+.RS 4
+Request profilelevel of a certain daemon and write it to stdout\. This can be sent to any smbd or nmbd destinations\.
 .RE
 .PP
 printnotify
+.RS 3n
+Order smbd to send a printer notify message to any Windows NT clients connected to a printer. This message-type takes the following arguments:
+.RS 3n
+.RS 4
+Order smbd to send a printer notify message to any Windows NT clients connected to a printer\. This message\-type takes the following arguments:
 .PP
 queuepause printername
 .RS 3n
 Send a queue pause change notify message to the printer specified.
+.RS 4
+Send a queue pause change notify message to the printer specified\.
 .RE
 .PP
 queueresume printername
 .RS 3n
 Send a queue resume change notify message for the printer specified.
+.RS 4
+Send a queue resume change notify message for the printer specified\.
 .RE
 .PP
 jobpause printername unixjobid
 .RS 3n
 Send a job pause change notify message for the printer and unix jobid specified.
+.RS 4
+Send a job pause change notify message for the printer and unix jobid specified\.
 .RE
 .PP
 jobresume printername unixjobid
 .RS 3n
 Send a job resume change notify message for the printer and unix jobid specified.
+.RS 4
+Send a job resume change notify message for the printer and unix jobid specified\.
 .RE
 .PP
 jobdelete printername unixjobid
+.RS 3n
+Send a job delete change notify message for the printer and unix jobid specified.
+.RE
+.RE
+.IP "" 3n
+Note that this message only sends notification that an event has occured. It doesn't actually cause the event to happen.
+.RS 4
+Send a job delete change notify message for the printer and unix jobid specified\.
+.RE
+.sp
+Note that this message only sends notification that an event has occured\. It doesn\'t actually cause the event to happen\.
 .sp
 This message can only be sent to
 \fBsmbd\fR.
+\fBsmbd\fR\.
 .RE
 .PP
 samsync
 .RS 3n
 Order smbd to synchronise sam database from PDC (being BDC). Can only be sent to
 \fBsmbd\fR.
+.RS 4
+Order smbd to synchronise sam database from PDC (being BDC)\. Can only be sent to
+\fBsmbd\fR\.
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBNote\fR
+Note
 Not working at the moment
 .RE
 .PP
 samrepl
 .RS 3n
 Send sam replication message, with specified serial. Can only be sent to
 \fBsmbd\fR. Should not be used manually.
 .RE
 .PP
 dmalloc-mark
 .RS 3n
 Set a mark for dmalloc. Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support.
 .RE
 .PP
 dmalloc-log-changed
 .RS 3n
 Dump the pointers that have changed since the mark set by dmalloc-mark. Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support.
+.RS 4
+Send sam replication message, with specified serial\. Can only be sent to
+\fBsmbd\fR\. Should not be used manually\.
+.RE
+.PP
+dmalloc\-mark
+.RS 4
+Set a mark for dmalloc\. Can be sent to both smbd and nmbd\. Only available if samba is built with dmalloc support\.
+.RE
+.PP
+dmalloc\-log\-changed
+.RS 4
+Dump the pointers that have changed since the mark set by dmalloc\-mark\. Can be sent to both smbd and nmbd\. Only available if samba is built with dmalloc support\.
 .RE
 .PP
 shutdown
 .RS 3n
 Shut down specified daemon. Can be sent to both smbd and nmbd.
 .RE
 .PP
 pool-usage
 .RS 3n
 Print a human-readable description of all talloc(pool) memory usage by the specified daemon/process. Available for both smbd and nmbd.
+.RS 4
+Shut down specified daemon\. Can be sent to both smbd and nmbd\.
+.RE
+.PP
+pool\-usage
+.RS 4
+Print a human\-readable description of all talloc(pool) memory usage by the specified daemon/process\. Available for both smbd and nmbd\.
 .RE
 .PP
 drvupgrade
 .RS 3n
 Force clients of printers using specified driver to update their local version of the driver. Can only be sent to smbd.
 .RE
 .PP
 reload-config
 .RS 3n
 Force daemon to reload smb.conf configuration file. Can be sent to
+.RS 4
+Force clients of printers using specified driver to update their local version of the driver\. Can only be sent to smbd\.
+.RE
+.PP
+reload\-config
+.RS 4
+Force daemon to reload smb\.conf configuration file\. Can be sent to
 \fBsmbd\fR,
 \fBnmbd\fR, or
 \fBwinbindd\fR.
+\fBwinbindd\fR\.
 .RE
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 of the Samba suite\.
 .SH "SEE ALSO"
 .PP
 \fBnmbd\fR(8)
 and
 \fBsmbd\fR(8).
+\fBsmbd\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 for Samba 3.0 was done by Alexander Bokovoy.
+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\.

branches/samba-3.0/docs/manpages/smbcquotas.1

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "SMBCQUOTAS" 1 "" "" ""
+.\"     Title: smbcquotas
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: User Commands
+.\"    Source: Samba 3.0
+.\"
+.TH "SMBCQUOTAS" "1" "05/21/2008" "Samba 3\.0" "User Commands"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 smbcquotas - Set or get QUOTAs of NTFS 5 shares
 .SH "SYNOPSIS"
 .HP 1
 smbcquotas {//server/share} [-u user] [-L] [-F] [-S QUOTA_SET_COMMAND] [-n] [-t] [-v] [-d debuglevel] [-s configfile] [-l logdir] [-V] [-U username] [-N] [-k] [-A]
+smbcquotas {//server/share} [\-u\ user] [\-L] [\-F] [\-S\ QUOTA_SET_COMMAND] [\-n] [\-t] [\-v] [\-d\ debuglevel] [\-s\ configfile] [\-l\ logdir] [\-V] [\-U\ username] [\-N] [\-k] [\-A]
 .SH "DESCRIPTION"
 .PP
 This tool is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 The
 smbcquotas
 program manipulates NT Quotas on SMB file shares.
+program manipulates NT Quotas on SMB file shares\.
 .SH "OPTIONS"
 .PP
 The following options are available to the
 smbcquotas
 program.
+program\.
 .PP
 -u user
 .RS 3n
 Specifies the user of whom the quotas are get or set. By default the current user's username will be used.
+\-u user
+.RS 4
+Specifies the user of whom the quotas are get or set\. By default the current user\'s username will be used\.
 .RE
 .PP
 -L
 .RS 3n
 Lists all quota records of the share.
+\-L
+.RS 4
+Lists all quota records of the share\.
 .RE
 .PP
 -F
 .RS 3n
 Show the share quota status and default limits.
+\-F
+.RS 4
+Show the share quota status and default limits\.
 .RE
 .PP
 -S QUOTA_SET_COMMAND
 .RS 3n
 This command sets/modifies quotas for a user or on the share, depending on the QUOTA_SET_COMMAND parameter which is described later.
+\-S QUOTA_SET_COMMAND
+.RS 4
+This command sets/modifies quotas for a user or on the share, depending on the QUOTA_SET_COMMAND parameter which is described later\.
 .RE
 .PP
 -n
 .RS 3n
 This option displays all QUOTA information in numeric format. The default is to convert SIDs to names and QUOTA limits to a readable string format.
+\-n
+.RS 4
+This option displays all QUOTA information in numeric format\. The default is to convert SIDs to names and QUOTA limits to a readable string format\.
 .RE
 .PP
 -t
 .RS 3n
 Don't actually do anything, only validate the correctness of the arguments.
+\-t
+.RS 4
+Don\'t actually do anything, only validate the correctness of the arguments\.
 .RE
 .PP
 -v
 .RS 3n
 Be verbose.
+\-v
+.RS 4
+Be verbose\.
 .RE
 .PP
 -h|--help
 .RS 3n
 Print a summary of command line options.
+\-h|\-\-help
+.RS 4
+Print a summary of command line options\.
 .RE
 .PP
+-V
+.RS 3n
+Prints the program version number.
+\-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
+\fIlog level\fR
+parameter in the
+\fIsmb\.conf\fR
+file\.
 .RE
 .PP
+-s <configuration file>
+.RS 3n
+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
+\fIsmb.conf\fR
+for more information. The default configuration file name is determined at compile time.
+\-V
+.RS 4
+Prints the program version number\.
 .RE
 .PP
+-d|--debuglevel=level
+.RS 3n
+\fIlevel\fR
+is an integer from 0 to 10. The default value if this parameter is not specified is zero.
+.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
+parameter in the
+\fIsmb.conf\fR
+file.
+\-s <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
+\fIsmb\.conf\fR
+for more information\. The default configuration file name is determined at compile time\.
 .RE
 .PP
 -l|--logfile=logdirectory
 .RS 3n
 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.
+\-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
 -N
 .RS 3n
 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.
+\-N
+.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.
+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.
+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
 .RS 3n
 Try to authenticate with kerberos. Only useful in an Active Directory environment.
+\-k
+.RS 4
+Try to authenticate with kerberos\. Only useful in an Active Directory environment\.
 .RE
 .PP
 -A|--authentication-file=filename
 .RS 3n
 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
+\-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
 .sp
+.RS 4
 .nf
 username = <value>
 password = <value>
 domain   = <value>
 .fi
+.RE
 .sp
 Make certain that the permissions on the file restrict access from unwanted users.
+Make certain that the permissions on the file restrict access from unwanted users\.
 .RE
 .PP
 -U|--user=username[%password]
 .RS 3n
 Sets the SMB username or username and password.
+\-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
+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
+variable and if either exists, the string is uppercased\. If these environmental variables are not found, the username
 \fBGUEST\fR
 is used.
+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.
+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
+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
+command\. To be safe always allow
 rpcclient
 to prompt for a password and type it in directly.
+to prompt for a password and type it in directly\.
 .RE
 .SH "QUOTA_SET_COMAND"
 .PP
 The format of an the QUOTA_SET_COMMAND is an operation name followed by a set of parameters specific to that operation.
+The format of an the QUOTA_SET_COMMAND is an operation name followed by a set of parameters specific to that operation\.
 .PP
 To set user quotas for the user specified by -u or for the current username:
+To set user quotas for the user specified by \-u or for the current username:
 .PP
 \fB UQLIM:<username>:<softlimit>/<hardlimit> \fR
 …
 \fB FSQFLAGS:QUOTA_ENABLED/DENY_DISK/LOG_SOFTLIMIT/LOG_HARD_LIMIT \fR
 .PP
 All limits are specified as a number of bytes.
+All limits are specified as a number of bytes\.
 .SH "EXIT STATUS"
 .PP
 The
 smbcquotas
 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.
+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, smbcquotas returns an exit status of 0. If
+If the operation succeeded, smbcquotas returns an exit status of 0\. If
 smbcquotas
 couldn't connect to the specified server, or when there was an error getting or setting the quota(s), an exit status of 1 is returned. If there was an error parsing any command line arguments, an exit status of 2 is returned.
+couldn\'t connect to the specified server, or when there was an error getting or setting the quota(s), 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 "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 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.
+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
 smbcquotas
+was written by Stefan Metzmacher.
+was written by Stefan Metzmacher\.

branches/samba-3.0/docs/manpages/smbd.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "SMBD" 8 "" "" ""
+.\"     Title: smbd
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "SMBD" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 smbd - server to provide SMB/CIFS services to clients
 .SH "SYNOPSIS"
 .HP 1
 smbd [-D] [-F] [-S] [-i] [-h] [-V] [-b] [-d <debug level>] [-l <log directory>] [-p <port number(s)>] [-P <profiling level>] [-O <socket option>] [-s <configuration file>]
+smbd [\-D] [\-F] [\-S] [\-i] [\-h] [\-V] [\-b] [\-d\ <debug\ level>] [\-l\ <log\ directory>] [\-p\ <port\ number(s)>] [\-P\ <profiling\ level>] [\-O\ <socket\ option>] [\-s\ <configuration\ file>]
 .SH "DESCRIPTION"
 .PP
 This program is part of the
 \fBsamba\fR(7)
 suite.
 .PP
 smbd
 is the server daemon that provides filesharing and printing services to Windows clients. The server provides filespace and printer services to clients using the SMB (or CIFS) protocol. This is compatible with the LanManager protocol, and can service LanManager clients. These include MSCLIENT 3.0 for DOS, Windows for Workgroups, Windows 95/98/ME, Windows NT, Windows 2000, OS/2, DAVE for Macintosh, and smbfs for Linux.
+suite\.
+.PP
+smbd
+is the server daemon that provides filesharing and printing services to Windows clients\. The server provides filespace and printer services to clients using the SMB (or CIFS) protocol\. This is compatible with the LanManager protocol, and can service LanManager clients\. These include MSCLIENT 3\.0 for DOS, Windows for Workgroups, Windows 95/98/ME, Windows NT, Windows 2000, OS/2, DAVE for Macintosh, and smbfs 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.
+\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.
 .PP
 A session is created whenever a client requests one. Each client gets a copy of the server for each session. This copy then services all connections made by the client during that session. When all connections from its client are closed, the copy of the server for that client terminates.
 .PP
 The configuration file, and any files that it includes, are automatically reloaded every minute, if they change. You can force a reload by sending a SIGHUP to the server. Reloading the configuration file will not affect connections to any service that is already established. Either the user will have to disconnect from the service, or
 smbd
 killed and restarted.
+manual page should be regarded as mandatory reading before proceeding with installation\.
+.PP
+A session is created whenever a client requests one\. Each client gets a copy of the server for each session\. This copy then services all connections made by the client during that session\. When all connections from its client are closed, the copy of the server for that client terminates\.
+.PP
+The configuration file, and any files that it includes, are automatically reloaded every minute, if they change\. You can force a reload by sending a SIGHUP to the server\. Reloading the configuration file will not affect connections to any service that is already established\. Either the user will have to disconnect from the service, or
+smbd
+killed and restarted\.
 .SH "OPTIONS"
 .PP
 -D
 .RS 3n
 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 port. Operating the server as a daemon is the recommended way of running
 smbd
 for servers that provide more than casual use file and print services. This switch is assumed if
 smbd
 is executed on the command line of a shell.
 .RE
 .PP
 -F
 .RS 3n
+\-D
+.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 port\. Operating the server as a daemon is the recommended way of running
+smbd
+for servers that provide more than casual use file and print services\. This switch is assumed if
+smbd
+is executed on the command line of a shell\.
+.RE
+.PP
+\-F
+.RS 4
 If specified, this parameter causes the main
 smbd
 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
+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
 smbd
 under process supervisors such as
 …
 and
 svscan
 from Daniel J. Bernstein's
+from Daniel J\. Bernstein\'s
 daemontools
 package, or the AIX process monitor.
 .RE
 .PP
 -S
 .RS 3n
+package, or the AIX process monitor\.
+.RE
+.PP
+\-S
+.RS 4
 If specified, this parameter causes
 smbd
 to log to standard output rather than a file.
 .RE
 .PP
 -i
 .RS 3n
 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 deamon mode when run from the command line.
+to log to standard output rather than a file\.
+.RE
+.PP
+\-i
+.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 deamon mode when run from the command line\.
 smbd
 also logs to standard output, as if the
+-S
+parameter had been given.
+.RE
+.PP
+-V
+.RS 3n
+Prints the program version number.
+.RE
+.PP
+-s <configuration file>
+.RS 3n
+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
+\fIsmb.conf\fR
+for more information. The default configuration file name is determined at compile time.
+.RE
+.PP
+-d|--debuglevel=level
+.RS 3n
+\-S
+parameter had been given\.
+.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 zero.
 .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.
+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
+\fIlog level\fR
 parameter in the
+\fIsmb.conf\fR
+file.
+.RE
+.PP
+-l|--logfile=logdirectory
+.RS 3n
+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
+-h|--help
+.RS 3n
+Print a summary of command line options.
+.RE
+.PP
+-b
+.RS 3n
+Prints information about how Samba was built.
+.RE
+.PP
+-p|--port<port number(s)>
+.RS 3n
+\fIsmb\.conf\fR
+file\.
+.RE
+.PP
+\-V
+.RS 4
+Prints the program version number\.
+.RE
+.PP
+\-s <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
+\fIsmb\.conf\fR
+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
+\-h|\-\-help
+.RS 4
+Print a summary of command line options\.
+.RE
+.PP
+\-b
+.RS 4
+Prints information about how Samba was built\.
+.RE
+.PP
+\-p|\-\-port<port number(s)>
+.RS 4
 \fIport number(s)\fR
+is a space or comma-separated list of TCP ports smbd should listen on. The default value is taken from the
+ports parameter in
+\fIsmb.conf\fR
+.sp
+The default ports are 139 (used for SMB over NetBIOS over TCP) and port 445 (used for plain SMB over TCP).
+.RE
+.PP
+-P|--profiling-level<profiling level>
+.RS 3n
+is a space or comma\-separated list of TCP ports smbd should listen on\. The default value is taken from the
+\fIports\fR
+parameter in
+\fIsmb\.conf\fR
+.sp
+The default ports are 139 (used for SMB over NetBIOS over TCP) and port 445 (used for plain SMB over TCP)\.
+.RE
+.PP
+\-P|\-\-profiling\-level<profiling level>
+.RS 4
 \fIprofiling level\fR
 is a number specifying the level of profiling data to be collected. 0 turns off profiling, 1 turns on counter profiling only, 2 turns on complete profiling, and 3 resets all profiling data.
+is a number specifying the level of profiling data to be collected\. 0 turns off profiling, 1 turns on counter profiling only, 2 turns on complete profiling, and 3 resets all profiling data\.
 .RE
 .SH "FILES"
 .PP
 \fI/etc/inetd.conf\fR
 .RS 3n
+\fI/etc/inetd\.conf\fR
+.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.
+meta\-daemon, this file must contain suitable startup information for the meta\-daemon\.
 .RE
 .PP
 \fI/etc/rc\fR
 .RS 3n
 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.
+.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
 \fI/etc/services\fR
 .RS 3n
 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
 \fI/usr/local/samba/lib/smb.conf\fR
 .RS 3n
+.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
+\fI/usr/local/samba/lib/smb\.conf\fR
+.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
 \fI/usr/samba/lib/smb.conf\fR
+server configuration file\. Other common places that systems install this file are
+\fI/usr/samba/lib/smb\.conf\fR
 and
 \fI/etc/samba/smb.conf\fR.
 .sp
 This file describes all the services the server is to make available to clients. See
+\fI/etc/samba/smb\.conf\fR\.
+.sp
+This file describes all the services the server is to make available to clients\. See
 \fBsmb.conf\fR(5)
 for more information.
+for more information\.
 .RE
 .SH "LIMITATIONS"
 …
 On some systems
 smbd
 cannot change uid back to root after a setuid() call. Such systems are called trapdoor uid systems. If you have such a system, you will be unable to connect from a client (such as a PC) as two different users at once. Attempts to connect the second user will result in access denied or similar.
+cannot change uid back to root after a setuid() call\. Such systems are called trapdoor uid systems\. If you have such a system, you will be unable to connect from a client (such as a PC) as two different users at once\. Attempts to connect the second user will result in access denied or similar\.
 .SH "ENVIRONMENT VARIABLES"
 .PP
 \fBPRINTER\fR
 .RS 3n
+.RS 4
 If no printer name is specified to printable services, most systems will use the value of this variable (or
 \fBlp\fR
 if this variable is not defined) as the name of the printer to use. This is not specific to the server, however.
+if this variable is not defined) as the name of the printer to use\. This is not specific to the server, however\.
 .RE
 .SH "PAM INTERACTION"
 .PP
 Samba uses PAM for authentication (when presented with a plaintext password), for account checking (is this account disabled?) and for session management. The degree too which samba supports PAM is restricted by the limitations of the SMB protocol and the
+obey pam restrictions
+Samba uses PAM for authentication (when presented with a plaintext password), for account checking (is this account disabled?) and for session management\. The degree too which samba supports PAM is restricted by the limitations of the SMB protocol and the
+\fIobey pam restrictions\fR
 \fBsmb.conf\fR(5)
+paramater. When this is set, the following restrictions apply:
+.TP 3n
+\(bu
+\fBAccount Validation\fR: All accesses to a samba server are checked against PAM to see if the account is vaild, not disabled and is permitted to login at this time. This also applies to encrypted logins.
+.TP 3n
+\(bu
+\fBSession Management\fR: When not using share level secuirty, users must pass PAM's session checks before access is granted. Note however, that this is bypassed in share level secuirty. Note also that some older pam configuration files may need a line added for session support.
+paramater\. When this is set, the following restrictions apply:
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\fIAccount Validation\fR: All accesses to a samba server are checked against PAM to see if the account is vaild, not disabled and is permitted to login at this time\. This also applies to encrypted logins\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\fISession Management\fR: When not using share level secuirty, users must pass PAM\'s session checks before access is granted\. Note however, that this is bypassed in share level secuirty\. Note also that some older pam configuration files may need a line added for session support\.
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 of the Samba suite\.
 .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.
+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 "TDB FILES"
 .PP
 Samba stores it's data in several TDB (Trivial Database) files, usually located in
 \fI/var/lib/samba\fR.
 .PP
 (*) information persistent across restarts (but not necessarily important to backup).
 .PP
 account_policy.tdb*
 .RS 3n
 NT account policy settings such as pw expiration, etc...
 .RE
 .PP
 brlock.tdb
 .RS 3n
+Samba stores it\'s data in several TDB (Trivial Database) files, usually located in
+\fI/var/lib/samba\fR\.
+.PP
+(*) information persistent across restarts (but not necessarily important to backup)\.
+.PP
+account_policy\.tdb*
+.RS 4
+NT account policy settings such as pw expiration, etc\.\.\.
+.RE
+.PP
+brlock\.tdb
+.RS 4
 byte range locks
 .RE
 .PP
 browse.dat
 .RS 3n
+browse\.dat
+.RS 4
 browse lists
 .RE
 .PP
 connections.tdb
 .RS 3n
 share connections (used to enforce max connections, etc...)
 .RE
 .PP
 gencache.tdb
 .RS 3n
+connections\.tdb
+.RS 4
+share connections (used to enforce max connections, etc\.\.\.)
+.RE
+.PP
+gencache\.tdb
+.RS 4
 generic caching db
 .RE
 .PP
 group_mapping.tdb*
 .RS 3n
+group_mapping\.tdb*
+.RS 4
 group mapping information
 .RE
 .PP
 locking.tdb
 .RS 3n
+locking\.tdb
+.RS 4
 share modes & oplocks
 .RE
 .PP
 login_cache.tdb*
 .RS 3n
+login_cache\.tdb*
+.RS 4
 bad pw attempts
 .RE
 .PP
 messages.tdb
 .RS 3n
+messages\.tdb
+.RS 4
 Samba messaging system
 .RE
 .PP
 netsamlogon_cache.tdb*
 .RS 3n
+netsamlogon_cache\.tdb*
+.RS 4
 cache of user net_info_3 struct from net_samlogon() request (as a domain member)
 .RE
 .PP
 ntdrivers.tdb*
 .RS 3n
+ntdrivers\.tdb*
+.RS 4
 installed printer drivers
 .RE
 .PP
 ntforms.tdb*
 .RS 3n
+ntforms\.tdb*
+.RS 4
 installed printer forms
 .RE
 .PP
 ntprinters.tdb*
 .RS 3n
+ntprinters\.tdb*
+.RS 4
 installed printer information
 .RE
 .PP
 printing/
 .RS 3n
+.RS 4
 directory containing tdb per print queue of cached lpq output
 .RE
 .PP
 registry.tdb
 .RS 3n
 Windows registry skeleton (connect via regedit.exe)
 .RE
 .PP
 sessionid.tdb
 .RS 3n
 session information (e.g. support for 'utmp = yes')
 .RE
 .PP
 share_info.tdb*
 .RS 3n
+registry\.tdb
+.RS 4
+Windows registry skeleton (connect via regedit\.exe)
+.RE
+.PP
+sessionid\.tdb
+.RS 4
+session information (e\.g\. support for \'utmp = yes\')
+.RE
+.PP
+share_info\.tdb*
+.RS 4
 share acls
 .RE
 .PP
 winbindd_cache.tdb
 .RS 3n
 winbindd's cache of user lists, etc...
 .RE
 .PP
 winbindd_idmap.tdb*
 .RS 3n
 winbindd's local idmap db
 .RE
 .PP
 wins.dat*
 .RS 3n
 wins database when 'wins support = yes'
+winbindd_cache\.tdb
+.RS 4
+winbindd\'s cache of user lists, etc\.\.\.
+.RE
+.PP
+winbindd_idmap\.tdb*
+.RS 4
+winbindd\'s local idmap db
+.RE
+.PP
+wins\.dat*
+.RS 4
+wins database when \'wins support = yes\'
 .RE
 .SH "SIGNALS"
 …
 smbd
 a SIGHUP will cause it to reload its
 \fIsmb.conf\fR
 configuration file within a short period of time.
 .PP
 To shut down a user's
+\fIsmb\.conf\fR
+configuration file within a short period of time\.
+.PP
+To shut down a user\'s
 smbd
 process it is recommended that
 SIGKILL (-9)
 \fBNOT\fR
 be used, except as a last resort, as this may leave the shared memory area in an inconsistent state. The safe way to terminate an
 smbd
 is to send it a SIGTERM (-15) signal and wait for it to die on its own.
+SIGKILL (\-9)
+\fINOT\fR
+be used, except as a last resort, as this may leave the shared memory area in an inconsistent state\. The safe way to terminate an
+smbd
+is to send it a SIGTERM (\-15) signal and wait for it to die on its own\.
 .PP
 The debug log level of
 …
 may be raised or lowered using
 \fBsmbcontrol\fR(1)
 program (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.
 .PP
 Note that as the signal handlers send a debug write, they are not re-entrant in
 smbd. This you should wait until
 smbd
 is in a state of waiting for an incoming SMB before issuing them. It is possible to make the signal handlers safe by un-blocking the signals before the select call and re-blocking them after, however this would affect performance.
+program (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\.
+.PP
+Note that as the signal handlers send a debug write, they are not re\-entrant in
+smbd\. This you should wait until
+smbd
+is in a state of waiting for an incoming SMB before issuing them\. It is possible to make the signal handlers safe by un\-blocking the signals before the select call and re\-blocking them after, however this would affect performance\.
 .SH "SEE ALSO"
 .PP
 …
 \fBsmbclient\fR(1),
 \fBtestparm\fR(1),
 \fBtestprns\fR(1), and the Internet RFC's
 \fIrfc1001.txt\fR,
 \fIrfc1002.txt\fR. In addition the CIFS (formerly SMB) specification is available as a link from the Web page
 http://samba.org/cifs/.
+\fBtestprns\fR(1), and the Internet RFC\'s
+\fIrfc1001\.txt\fR,
+\fIrfc1002\.txt\fR\. 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.
+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\.

branches/samba-3.0/docs/manpages/smbget.1

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "SMBGET" 1 "" "" ""
+.\"     Title: smbget
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: User Commands
+.\"    Source: Samba 3.0
+.\"
+.TH "SMBGET" "1" "05/21/2008" "Samba 3\.0" "User Commands"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 smbget - wget-like utility for download files over SMB
 .SH "SYNOPSIS"
 .HP 1
 smbget [-a, --guest] [-r, --resume] [-R, --recursive] [-u, --username=STRING] [-p, --password=STRING] [-w, --workgroup=STRING] [-n, --nonprompt] [-d, --debuglevel=INT] [-D, --dots] [-P, --keep-permissions] [-o, --outputfile] [-f, --rcfile] [-q, --quiet] [-v, --verbose] [-b, --blocksize] [-?, --help] [--usage] {smb://host/share/path/to/file} [smb://url2/] [...]
+smbget [\-a,\ \-\-guest] [\-r,\ \-\-resume] [\-R,\ \-\-recursive] [\-u,\ \-\-username=STRING] [\-p,\ \-\-password=STRING] [\-w,\ \-\-workgroup=STRING] [\-n,\ \-\-nonprompt] [\-d,\ \-\-debuglevel=INT] [\-D,\ \-\-dots] [\-P,\ \-\-keep\-permissions] [\-o,\ \-\-outputfile] [\-f,\ \-\-rcfile] [\-q,\ \-\-quiet] [\-v,\ \-\-verbose] [\-b,\ \-\-blocksize] [\-?,\ \-\-help] [\-\-usage] {smb://host/share/path/to/file} [smb://url2/] [\.\.\.]
 .SH "DESCRIPTION"
 .PP
 This tool is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 smbget is a simple utility with wget-like semantics, that can download files from SMB servers. You can specify the files you would like to download on the command-line.
+smbget is a simple utility with wget\-like semantics, that can download files from SMB servers\. You can specify the files you would like to download on the command\-line\.
 .PP
 The files should be in the smb-URL standard, e.g. use smb://host/share/file for the UNC path
 \fB\\\\HOST\\SHARE\\file\fR.
+The files should be in the smb\-URL standard, e\.g\. use smb://host/share/file for the UNC path
+\fI\e\e\e\eHOST\e\eSHARE\e\efile\fR\.
 .SH "OPTIONS"
 .PP
 -a, --guest
 .RS 3n
+\-a, \-\-guest
+.RS 4
 Work as user guest
 .RE
 .PP
 -r, --resume
 .RS 3n
+\-r, \-\-resume
+.RS 4
 Automatically resume aborted files
 .RE
 .PP
 -R, --recursive
 .RS 3n
+\-R, \-\-recursive
+.RS 4
 Recursively download files
 .RE
 .PP
 -u, --username=STRING
 .RS 3n
+\-u, \-\-username=STRING
+.RS 4
 Username to use
 .RE
 .PP
 -p, --password=STRING
 .RS 3n
+\-p, \-\-password=STRING
+.RS 4
 Password to use
 .RE
 .PP
 -w, --workgroup=STRING
 .RS 3n
+\-w, \-\-workgroup=STRING
+.RS 4
 Workgroup to use (optional)
 .RE
 .PP
 -n, --nonprompt
 .RS 3n
 Don't ask anything (non-interactive)
+\-n, \-\-nonprompt
+.RS 4
+Don\'t ask anything (non\-interactive)
 .RE
 .PP
 -d, --debuglevel=INT
 .RS 3n
+\-d, \-\-debuglevel=INT
+.RS 4
 Debuglevel to use
 .RE
 .PP
 -D, --dots
 .RS 3n
+\-D, \-\-dots
+.RS 4
 Show dots as progress indication
 .RE
 .PP
 -P, --keep-permissions
 .RS 3n
 Set same permissions on local file as are set on remote file.
+\-P, \-\-keep\-permissions
+.RS 4
+Set same permissions on local file as are set on remote file\.
 .RE
 .PP
 -o, --outputfile
 .RS 3n
 Write the file that is being download to the specified file. Can not be used together with -R.
+\-o, \-\-outputfile
+.RS 4
+Write the file that is being download to the specified file\. Can not be used together with \-R\.
 .RE
 .PP
 -f, --rcfile
 .RS 3n
 Use specified rcfile. This will be loaded in the order it was specified - e.g. if you specify any options before this one, they might get overriden by the contents of the rcfile.
+\-f, \-\-rcfile
+.RS 4
+Use specified rcfile\. This will be loaded in the order it was specified \- e\.g\. if you specify any options before this one, they might get overriden by the contents of the rcfile\.
 .RE
 .PP
 -q, --quiet
 .RS 3n
+\-q, \-\-quiet
+.RS 4
 Be quiet
 .RE
 .PP
 -v, --verbose
 .RS 3n
+\-v, \-\-verbose
+.RS 4
 Be verbose
 .RE
 .PP
 -b, --blocksize
 .RS 3n
 Number of bytes to download in a block. Defaults to 64000.
+\-b, \-\-blocksize
+.RS 4
+Number of bytes to download in a block\. Defaults to 64000\.
 .RE
 .PP
 -?, --help
 .RS 3n
+\-?, \-\-help
+.RS 4
 Show help message
 .RE
 .PP
 --usage
 .RS 3n
+\-\-usage
+.RS 4
 Display brief usage message
 .RE
 .SH "SMB URLS"
 .PP
 SMB URL's should be specified in the following format:
+SMB URL\'s should be specified in the following format:
 .PP
+.RS 4
+.nf
+smb://[[[domain;]user[:password@]]server[/share[/path[/file]]]]
+.fi
+.RE
+.PP
+.RS 4
+.nf
+smb:// means all the workgroups
+.fi
+.RE
+.PP
+.RS 4
+.nf
+smb://name/ means, if \fIname\fR is a workgroup, all the servers in this workgroup, or if \fIname\fR is a server, all the shares on this server\.
+.fi
+.RE
+.SH "EXAMPLES"
 .sp
+.RS 4
 .nf
+smb://[[[domain;]user[:password@]]server[/share[/path[/file]]]]
+# Recursively download \'src\' directory
+smbget \-R smb://rhonwyn/jelmer/src
+# Download FreeBSD ISO and enable resuming
+smbget \-r smb://rhonwyn/isos/FreeBSD5\.1\.iso
+# Recursively download all ISOs
+smbget \-Rr smb://rhonwyn/isos
+# Backup my data on rhonwyn
+smbget \-Rr smb://rhonwyn/
 .fi
+.PP
+.sp
+.nf
+smb:// means all the workgroups
+.fi
+.PP
+.sp
+.nf
+smb://name/ means, if \fIname\fR is a workgroup, all the servers in this workgroup, or if \fIname\fR is a server, all the shares on this server.
+.fi
+.SH "EXAMPLES"
+.nf
+# Recursively download 'src' directory
+smbget -R smb://rhonwyn/jelmer/src
+# Download FreeBSD ISO and enable resuming
+smbget -r smb://rhonwyn/isos/FreeBSD5.1.iso
+# Recursively download all ISOs
+smbget -Rr smb://rhonwyn/isos
+# Backup my data on rhonwyn
+smbget -Rr smb://rhonwyn/
+.fi
+.RE
 .SH "BUGS"
 .PP
 Permission denied is returned in some cases where the cause of the error is unknown (such as an illegally formatted smb:// url or trying to get a directory without -R turned on).
+Permission denied is returned in some cases where the cause of the error is unknown (such as an illegally formatted smb:// url or trying to get a directory without \-R turned on)\.
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 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.
+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 smbget manpage was written by Jelmer Vernooij.
+The smbget manpage was written by Jelmer Vernooij\.

branches/samba-3.0/docs/manpages/smbgetrc.5

-              r39
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "SMBGETRC" 5 "" "" ""
+.\"     Title: smbgetrc
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: File Formats and Conventions
+.\"    Source: Samba 3.0
+.\"
+.TH "SMBGETRC" "5" "05/21/2008" "Samba 3\.0" "File Formats and Conventions"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 smbgetrc - configuration file for smbget
 …
 .PP
 This manual page documents the format and options of the
 \fBsmbgetrc\fR
 file. This is the configuration file used by the
+\fIsmbgetrc\fR
+file\. This is the configuration file used by the
 \fBsmbget\fR(1)
 utility. The file contains of key-value pairs, one pair on each line. The key and value should be separated by a space.
+utility\. The file contains of key\-value pairs, one pair on each line\. The key and value should be separated by a space\.
 .PP
 By default, smbget reads its configuration from
 \fB$HOME/.smbgetrc\fR, though other locations can be specified using the command-line options.
+\fI$HOME/\.smbgetrc\fR, though other locations can be specified using the command\-line options\.
 .SH "OPTIONS"
 .PP
 …
 .PP
 resume on|off
 .RS 3n
 Whether aborted downloads should be automatically resumed.
+.RS 4
+Whether aborted downloads should be automatically resumed\.
 .RE
 .PP
 recursive on|off
 .RS 3n
+.RS 4
 Whether directories should be downloaded recursively
 .RE
 .PP
 username \fIname\fR
 .RS 3n
 Username to use when logging in to the remote server. Use an empty string for anonymous access.
+.RS 4
+Username to use when logging in to the remote server\. Use an empty string for anonymous access\.
 .RE
 .PP
 password \fIpass\fR
 .RS 3n
 Password to use when logging in.
+.RS 4
+Password to use when logging in\.
 .RE
 .PP
 workgroup \fIwg\fR
 .RS 3n
+.RS 4
 Workgroup to use when logging in
 .RE
 .PP
 nonprompt on|off
 .RS 3n
 Turns off asking for username and password. Useful for scripts.
+.RS 4
+Turns off asking for username and password\. Useful for scripts\.
 .RE
 .PP
 debuglevel \fIint\fR
 .RS 3n
 (Samba) debuglevel to run at. Useful for tracking down protocol level problems.
+.RS 4
+(Samba) debuglevel to run at\. Useful for tracking down protocol level problems\.
 .RE
 .PP
 dots on|off
 .RS 3n
 Whether a single dot should be printed for each block that has been downloaded, instead of the default progress indicator.
+.RS 4
+Whether a single dot should be printed for each block that has been downloaded, instead of the default progress indicator\.
 .RE
 .PP
 blocksize \fIint\fR
 .RS 3n
 Number of bytes to put in a block.
+.RS 4
+Number of bytes to put in a block\.
 .RE
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 of the Samba suite\.
 .SH "SEE ALSO"
 .PP
 \fBsmbget\fR(1)
 and
 \fBSamba\fR(7).
+\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.
+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 manual page was written by Jelmer Vernooij

branches/samba-3.0/docs/manpages/smbmnt.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "SMBMNT" 8 "" "" ""
+.\"     Title: smbmnt
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual:
+.\"    Source:
+.\"
+.TH "SMBMNT" "8" "05/21/2008" "" ""
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 smbmnt - helper utility for mounting SMB filesystems
 .SH "SYNOPSIS"
 .HP 1
 smbmnt {mount-point} [-s <share>] [-r] [-u <uid>] [-g <gid>] [-f <mask>] [-d <mask>] [-o <options>] [-h]
+smbmnt {mount\-point} [\-s\ <share>] [\-r] [\-u\ <uid>] [\-g\ <gid>] [\-f\ <mask>] [\-d\ <mask>] [\-o\ <options>] [\-h]
 .SH "DESCRIPTION"
 .PP
 smbmnt
 is a helper application used by the smbmount program to do the actual mounting of SMB shares.
+is a helper application used by the smbmount program to do the actual mounting of SMB shares\.
 smbmnt
 can be installed setuid root if you want normal users to be able to mount their SMB shares.
+can be installed setuid root if you want normal users to be able to mount their SMB shares\.
 .PP
 A setuid smbmnt will only allow mounts on directories owned by the user, and that the user has write permission on.
+A setuid smbmnt will only allow mounts on directories owned by the user, and that the user has write permission on\.
 .PP
 The
 smbmnt
 program is normally invoked by
 \fBsmbmount\fR(8). It should not be invoked directly by users.
+\fBsmbmount\fR(8)\. It should not be invoked directly by users\.
 .PP
 smbmount searches the normal PATH for smbmnt. You must ensure that the smbmnt version in your path matches the smbmount used.
+smbmount searches the normal PATH for smbmnt\. You must ensure that the smbmnt version in your path matches the smbmount used\.
 .SH "OPTIONS"
 .PP
 -r
 .RS 3n
 mount the filesystem read-only
+\-r
+.RS 4
+mount the filesystem read\-only
 .RE
 .PP
 -u uid
 .RS 3n
+\-u uid
+.RS 4
 specify the uid that the files will be owned by
 .RE
 .PP
 -g gid
 .RS 3n
+\-g gid
+.RS 4
 specify the gid that the files will be owned by
 .RE
 .PP
 -f mask
 .RS 3n
+\-f mask
+.RS 4
 specify the octal file mask applied
 .RE
 .PP
 -d mask
 .RS 3n
+\-d mask
+.RS 4
 specify the octal directory mask applied
 .RE
 .PP
 -o options
 .RS 3n
 list of options that are passed as-is to smbfs, if this command is run on a 2.4 or higher Linux kernel.
+\-o options
+.RS 4
+list of options that are passed as\-is to smbfs, if this command is run on a 2\.4 or higher Linux kernel\.
 .RE
 .PP
 -h|--help
 .RS 3n
 Print a summary of command line options.
+\-h|\-\-help
+.RS 4
+Print a summary of command line options\.
 .RE
 .SH "AUTHOR"
 .PP
 Volker Lendecke, Andrew Tridgell, Michael H. Warfield and others.
+Volker Lendecke, Andrew Tridgell, Michael H\. Warfield and others\.
 .PP
 The current maintainer of smbfs and the userspace tools
 …
 smbmnt
 is
 Urban Widmark. The
+Urban Widmark\. The
 SAMBA Mailing list
 is the preferred place to ask questions regarding these programs.
+is the preferred place to ask questions regarding these programs\.
 .PP
+The conversion of this manpage for Samba 2.2 was performed by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.
+The conversion of this manpage for Samba 2\.2 was performed by Gerald Carter\. The conversion to DocBook XML 4\.2 for Samba 3\.0 was done by Alexander Bokovoy\.

branches/samba-3.0/docs/manpages/smbmount.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "SMBMOUNT" 8 "" "" ""
+.\"     Title: smbmount
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual:
+.\"    Source:
+.\"
+.TH "SMBMOUNT" "8" "05/21/2008" "" ""
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 smbmount - mount an smbfs filesystem
 .SH "SYNOPSIS"
 .HP 1
 smbmount {service} {mount-point} [-o options]
+smbmount {service} {mount\-point} [\-o\ options]
 .SH "DESCRIPTION"
 .PP
 smbmount
 mounts a Linux SMB filesystem. It is usually invoked as
 mount.smbfs
+mounts a Linux SMB filesystem\. It is usually invoked as
+mount\.smbfs
 by the
 \fBmount\fR(8)
 command when using the "-t smbfs" option. This command only works in Linux, and the kernel must support the smbfs filesystem.
+command when using the "\-t smbfs" option\. This command only works in Linux, and the kernel must support the smbfs filesystem\.
 .PP
 WARNING:
 smbmount
 is deprecated and not maintained any longer.
 mount.cifs
 (mount -t cifs) should be used instead of
 smbmount.
+is deprecated and not maintained any longer\.
+mount\.cifs
+(mount \-t cifs) should be used instead of
+smbmount\.
 .PP
 Options to
 smbmount
 are specified as a comma-separated list of key=value pairs. It is possible to send options other than those listed here, assuming that smbfs supports them. If you get mount failures, check your kernel log for errors on unknown options.
 .PP
 smbmount
 is a daemon. After mounting it keeps running until the mounted smbfs is umounted. It will log things that happen when in daemon mode using the "machine name" smbmount, so typically this output will end up in
 \fIlog.smbmount\fR. The
 smbmount
 process may also be called mount.smbfs.
+are specified as a comma\-separated list of key=value pairs\. It is possible to send options other than those listed here, assuming that smbfs supports them\. If you get mount failures, check your kernel log for errors on unknown options\.
+.PP
+smbmount
+is a daemon\. After mounting it keeps running until the mounted smbfs is umounted\. It will log things that happen when in daemon mode using the "machine name" smbmount, so typically this output will end up in
+\fIlog\.smbmount\fR\. The
+smbmount
+process may also be called mount\.smbfs\.
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBNote\fR
+Note
 .PP
 …
 calls
 \fBsmbmnt\fR(8)
 to do the actual mount. You must make sure that
+to do the actual mount\. You must make sure that
 smbmnt
 is in the path so that it can be found.
+is in the path so that it can be found\.
 .SH "OPTIONS"
 .PP
 username=<arg>
 .RS 3n
 specifies the username to connect as. If this is not given, then the environment variable
+.RS 4
+specifies the username to connect as\. If this is not given, then the environment variable
 \fB USER\fR
 is used. This option can also take the form "user%password" or "user/workgroup" or "user/workgroup%password" to allow the password and workgroup to be specified as part of the username.
+is used\. This option can also take the form "user%password" or "user/workgroup" or "user/workgroup%password" to allow the password and workgroup to be specified as part of the username\.
 .RE
 .PP
 password=<arg>
 .RS 3n
 specifies the SMB password. If this option is not given then the environment variable
+.RS 4
+specifies the SMB password\. If this option is not given then the environment variable
 PASSWD
 is used. If it can find no password
 smbmount
 will prompt for a password, unless the guest option is given.
 .sp
 Note that passwords which contain the argument delimiter character (i.e. a comma ',') will failed to be parsed correctly on the command line. However, the same password defined in the PASSWD environment variable or a credentials file (see below) will be read correctly.
+is used\. If it can find no password
+smbmount
+will prompt for a password, unless the guest option is given\.
+.sp
+Note that passwords which contain the argument delimiter character (i\.e\. a comma \',\') will failed to be parsed correctly on the command line\. However, the same password defined in the PASSWD environment variable or a credentials file (see below) will be read correctly\.
 .RE
 .PP
 credentials=<filename>
+.RS 3n
+specifies a file that contains a username and/or password. The format of the file is:
+.sp
+.RS 4
+specifies a file that contains a username and/or password\. The format of the file is:
+.sp
+.RS 4
 .nf
+username = <value>
+password = <value>
+username=value
+password=value
 .fi
+.RE
 .sp
 This is preferred over having passwords in plaintext in a shared file, such as
 \fI/etc/fstab\fR. Be sure to protect any credentials file properly.
+\fI/etc/fstab\fR\. Be sure to protect any credentials file properly\.
 .RE
 .PP
 krb
 .RS 3n
 Use kerberos (Active Directory).
+.RS 4
+Use kerberos (Active Directory)\.
 .RE
 .PP
 netbiosname=<arg>
 .RS 3n
 sets the source NetBIOS name. It defaults to the local hostname.
+.RS 4
+sets the source NetBIOS name\. It defaults to the local hostname\.
 .RE
 .PP
 uid=<arg>
 .RS 3n
 sets the uid that will own all files on the mounted filesystem. It may be specified as either a username or a numeric uid.
+.RS 4
+sets the uid that will own all files on the mounted filesystem\. It may be specified as either a username or a numeric uid\.
 .RE
 .PP
 gid=<arg>
 .RS 3n
 sets the gid that will own all files on the mounted filesystem. It may be specified as either a groupname or a numeric gid.
+.RS 4
+sets the gid that will own all files on the mounted filesystem\. It may be specified as either a groupname or a numeric gid\.
 .RE
 .PP
 port=<arg>
 .RS 3n
 sets the remote SMB port number. The default is 445, fallback is 139.
+.RS 4
+sets the remote SMB port number\. The default is 445, fallback is 139\.
 .RE
 .PP
 fmask=<arg>
 .RS 3n
 sets the file mask. This determines the permissions that remote files have in the local filesystem. This is not a umask, but the actual permissions for the files. The default is based on the current umask.
+.RS 4
+sets the file mask\. This determines the permissions that remote files have in the local filesystem\. This is not a umask, but the actual permissions for the files\. The default is based on the current umask\.
 .RE
 .PP
 dmask=<arg>
 .RS 3n
 Sets the directory mask. This determines the permissions that remote directories have in the local filesystem. This is not a umask, but the actual permissions for the directories. The default is based on the current umask.
+.RS 4
+Sets the directory mask\. This determines the permissions that remote directories have in the local filesystem\. This is not a umask, but the actual permissions for the directories\. The default is based on the current umask\.
 .RE
 .PP
 debug=<arg>
 .RS 3n
 Sets the debug level. This is useful for tracking down SMB connection problems. A suggested value to start with is 4. If set too high there will be a lot of output, possibly hiding the useful output.
+.RS 4
+Sets the debug level\. This is useful for tracking down SMB connection problems\. A suggested value to start with is 4\. If set too high there will be a lot of output, possibly hiding the useful output\.
 .RE
 .PP
 ip=<arg>
 .RS 3n
 Sets the destination host or IP address.
+.RS 4
+Sets the destination host or IP address\.
 .RE
 .PP
 workgroup=<arg>
 .RS 3n
+.RS 4
 Sets the workgroup on the destination
 .RE
 .PP
 sockopt=<arg>
 .RS 3n
 Sets the TCP socket options. See the
+.RS 4
+Sets the TCP socket options\. See the
 \fBsmb.conf\fR(5)
 \fIsocket options\fR
 option.
+option\.
 .RE
 .PP
 scope=<arg>
 .RS 3n
+.RS 4
 Sets the NetBIOS scope
 .RE
 .PP
 guest
 .RS 3n
 Don't prompt for a password
+.RS 4
+Don\'t prompt for a password
 .RE
 .PP
 ro
 .RS 3n
 mount read-only
+.RS 4
+mount read\-only
 .RE
 .PP
 rw
 .RS 3n
 mount read-write
+.RS 4
+mount read\-write
 .RE
 .PP
 iocharset=<arg>
 .RS 3n
 sets the charset used by the Linux side for codepage to charset translations (NLS). Argument should be the name of a charset, like iso8859-1. (Note: only kernel 2.4.0 or later)
+.RS 4
+sets the charset used by the Linux side for codepage to charset translations (NLS)\. Argument should be the name of a charset, like iso8859\-1\. (Note: only kernel 2\.4\.0 or later)
 .RE
 .PP
 codepage=<arg>
 .RS 3n
 sets the codepage the server uses. See the iocharset option. Example value cp850. (Note: only kernel 2.4.0 or later)
+.RS 4
+sets the codepage the server uses\. See the iocharset option\. Example value cp850\. (Note: only kernel 2\.4\.0 or later)
 .RE
 .PP
 ttl=<arg>
 .RS 3n
 sets how long a directory listing is cached in milliseconds (also affects visibility of file size and date changes). A higher value means that changes on the server take longer to be noticed but it can give better performance on large directories, especially over long distances. Default is 1000ms but something like 10000ms (10 seconds) is probably more reasonable in many cases. (Note: only kernel 2.4.2 or later)
+.RS 4
+sets how long a directory listing is cached in milliseconds (also affects visibility of file size and date changes)\. A higher value means that changes on the server take longer to be noticed but it can give better performance on large directories, especially over long distances\. Default is 1000ms but something like 10000ms (10 seconds) is probably more reasonable in many cases\. (Note: only kernel 2\.4\.2 or later)
 .RE
 .SH "ENVIRONMENT VARIABLES"
 …
 The variable
 \fBUSER\fR
 may contain the username of the person using the client. This information is used only if the protocol level is high enough to support session-level passwords. The variable can be used to set both username and password by using the format username%password.
+may contain the username of the person using the client\. This information is used only if the protocol level is high enough to support session\-level passwords\. The variable can be used to set both username and password by using the format username%password\.
 .PP
 The variable
 \fBPASSWD\fR
 may contain the password of the person using the client. This information is used only if the protocol level is high enough to support session-level passwords.
+may contain the password of the person using the client\. This information is used only if the protocol level is high enough to support session\-level passwords\.
 .PP
 The variable
 \fBPASSWD_FILE\fR
 may contain the pathname of a file to read the password from. A single line of input is read and used as the password.
+may contain the pathname of a file to read the password from\. A single line of input is read and used as the password\.
 .SH "OTHER COMMANDS"
 .PP
 …
 or the UNIX system
 umount
 command.
+command\.
 .SH "BUGS"
 .PP
 Passwords and other options containing , can not be handled. For passwords an alternative way of passing them is in a credentials file or in the PASSWD environment.
 .PP
 The credentials file does not handle usernames or passwords with leading space.
+Passwords and other options containing , can not be handled\. For passwords an alternative way of passing them is in a credentials file or in the PASSWD environment\.
+.PP
+The credentials file does not handle usernames or passwords with leading space\.
 .PP
 One smbfs bug is important enough to mention here, even if it is a bit misplaced:
+.TP 3n
+\(bu
+Mounts sometimes stop working. This is usually caused by smbmount terminating. Since smbfs needs smbmount to reconnect when the server disconnects, the mount will eventually go dead. An umount/mount normally fixes this. At least 2 ways to trigger this bug are known.
+.PP
+Note that the typical response to a bug report is suggestion to try the latest version first. So please try doing that first, and always include which versions you use of relevant software when reporting bugs (minimum: samba, kernel, distribution)
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+Mounts sometimes stop working\. This is usually caused by smbmount terminating\. Since smbfs needs smbmount to reconnect when the server disconnects, the mount will eventually go dead\. An umount/mount normally fixes this\. At least 2 ways to trigger this bug are known\.
+.sp
+.RE
+.PP
+Note that the typical response to a bug report is suggestion to try the latest version first\. So please try doing that first, and always include which versions you use of relevant software when reporting bugs (minimum: samba, kernel, distribution)
 .SH "SEE ALSO"
 .PP
 Documentation/filesystems/smbfs.txt in the linux kernel source tree may contain additional options and information.
+Documentation/filesystems/smbfs\.txt in the linux kernel source tree may contain additional options and information\.
 .PP
 FreeBSD also has a smbfs, but it is not related to smbmount
 .PP
 For Solaris, HP-UX and others you may want to look at
+For Solaris, HP\-UX and others you may want to look at
 \fBsmbsh\fR(1)
 or at other solutions, such as Sharity or perhaps replacing the SMB server with a NFS server.
+or at other solutions, such as Sharity or perhaps replacing the SMB server with a NFS server\.
 .SH "AUTHOR"
 .PP
 Volker Lendecke, Andrew Tridgell, Michael H. Warfield and others.
+Volker Lendecke, Andrew Tridgell, Michael H\. Warfield and others\.
 .PP
 The current maintainer of smbfs and the userspace tools
 …
 smbmnt
 is
 Urban Widmark. The
+Urban Widmark\. The
 SAMBA Mailing list
+is the preferred place to ask questions regarding these programs.
+.PP
+The conversion of this manpage for Samba 2.2 was performed by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.
+is the preferred place to ask questions regarding these programs\.
+.PP
+The conversion of this manpage for Samba 2\.2 was performed by Gerald Carter\. The conversion to DocBook XML 4\.2 for Samba 3\.0 was done by Alexander Bokovoy\.

branches/samba-3.0/docs/manpages/smbpasswd.5

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "SMBPASSWD" 5 "" "" ""
+.\"     Title: smbpasswd
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: File Formats and Conventions
+.\"    Source: Samba 3.0
+.\"
+.TH "SMBPASSWD" "5" "05/21/2008" "Samba 3\.0" "File Formats and Conventions"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 smbpasswd - The Samba encrypted password file
 …
 This tool is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 smbpasswd is the Samba encrypted password file. It contains the username, Unix user id and the SMB hashed passwords of the user, as well as account flag information and the time the password was last changed. This file format has been evolving with Samba and has had several different formats in the past.
+smbpasswd is the Samba encrypted password file\. It contains the username, Unix user id and the SMB hashed passwords of the user, as well as account flag information and the time the password was last changed\. This file format has been evolving with Samba and has had several different formats in the past\.
 .SH "FILE FORMAT"
 .PP
 The format of the smbpasswd file used by Samba 2.2 is very similar to the familiar Unix
+The format of the smbpasswd file used by Samba 2\.2 is very similar to the familiar Unix
 \fIpasswd(5)\fR
 file. It is an ASCII file containing one line for each user. Each field ithin each line is separated from the next by a colon. Any entry beginning with '#' is ignored. The smbpasswd file contains the following information for each user:
+file\. It is an ASCII file containing one line for each user\. Each field ithin each line is separated from the next by a colon\. Any entry beginning with \'#\' is ignored\. The smbpasswd file contains the following information for each user:
 .PP
 name
 .RS 3n
 This is the user name. It must be a name that already exists in the standard UNIX passwd file.
+.RS 4
+This is the user name\. It must be a name that already exists in the standard UNIX passwd file\.
 .RE
 .PP
 uid
 .RS 3n
 This is the UNIX uid. It must match the uid field for the same user entry in the standard UNIX passwd file. If this does not match then Samba will refuse to recognize this smbpasswd file entry as being valid for a user.
+.RS 4
+This is the UNIX uid\. It must match the uid field for the same user entry in the standard UNIX passwd file\. If this does not match then Samba will refuse to recognize this smbpasswd file entry as being valid for a user\.
 .RE
 .PP
 Lanman Password Hash
 .RS 3n
 This is the LANMAN hash of the user's password, encoded as 32 hex digits. The LANMAN hash is created by DES encrypting a well known string with the user's password as the DES key. This is the same password used by Windows 95/98 machines. Note that this password hash is regarded as weak as it is vulnerable to dictionary attacks and if two users choose the same password this entry will be identical (i.e. the password is not "salted" as the UNIX password is). If the user has a null password this field will contain the characters "NO PASSWORD" as the start of the hex string. If the hex string is equal to 32 'X' characters then the user's account is marked as
+.RS 4
+This is the LANMAN hash of the user\'s password, encoded as 32 hex digits\. The LANMAN hash is created by DES encrypting a well known string with the user\'s password as the DES key\. This is the same password used by Windows 95/98 machines\. Note that this password hash is regarded as weak as it is vulnerable to dictionary attacks and if two users choose the same password this entry will be identical (i\.e\. the password is not "salted" as the UNIX password is)\. If the user has a null password this field will contain the characters "NO PASSWORD" as the start of the hex string\. If the hex string is equal to 32 \'X\' characters then the user\'s account is marked as
 \fBdisabled\fR
 and the user will not be able to log onto the Samba server.
+and the user will not be able to log onto the Samba server\.
 .sp
 \fBWARNING !!\fR
 Note that, due to the challenge-response nature of the SMB/CIFS authentication protocol, anyone with a knowledge of this password hash will be able to impersonate the user on the network. For this reason these hashes are known as
 \fBplain text equivalents\fR
+\fIWARNING !!\fR
+Note that, due to the challenge\-response nature of the SMB/CIFS authentication protocol, anyone with a knowledge of this password hash will be able to impersonate the user on the network\. For this reason these hashes are known as
+\fIplain text equivalents\fR
 and must
 \fBNOT\fR
 be made available to anyone but the root user. To protect these passwords the smbpasswd file is placed in a directory with read and traverse access only to the root user and the smbpasswd file itself must be set to be read/write only by root, with no other access.
+\fINOT\fR
+be made available to anyone but the root user\. To protect these passwords the smbpasswd file is placed in a directory with read and traverse access only to the root user and the smbpasswd file itself must be set to be read/write only by root, with no other access\.
 .RE
 .PP
 NT Password Hash
 .RS 3n
 This is the Windows NT hash of the user's password, encoded as 32 hex digits. The Windows NT hash is created by taking the user's password as represented in 16-bit, little-endian UNICODE and then applying the MD4 (internet rfc1321) hashing algorithm to it.
+.RS 4
+This is the Windows NT hash of the user\'s password, encoded as 32 hex digits\. The Windows NT hash is created by taking the user\'s password as represented in 16\-bit, little\-endian UNICODE and then applying the MD4 (internet rfc1321) hashing algorithm to it\.
 .sp
 This password hash is considered more secure than the LANMAN Password Hash as it preserves the case of the password and uses a much higher quality hashing algorithm. However, it is still the case that if two users choose the same password this entry will be identical (i.e. the password is not "salted" as the UNIX password is).
+This password hash is considered more secure than the LANMAN Password Hash as it preserves the case of the password and uses a much higher quality hashing algorithm\. However, it is still the case that if two users choose the same password this entry will be identical (i\.e\. the password is not "salted" as the UNIX password is)\.
 .sp
 \fBWARNING !!\fR. Note that, due to the challenge-response nature of the SMB/CIFS authentication protocol, anyone with a knowledge of this password hash will be able to impersonate the user on the network. For this reason these hashes are known as
 \fBplain text equivalents\fR
+\fIWARNING !!\fR\. Note that, due to the challenge\-response nature of the SMB/CIFS authentication protocol, anyone with a knowledge of this password hash will be able to impersonate the user on the network\. For this reason these hashes are known as
+\fIplain text equivalents\fR
 and must
 \fBNOT\fR
 be made available to anyone but the root user. To protect these passwords the smbpasswd file is placed in a directory with read and traverse access only to the root user and the smbpasswd file itself must be set to be read/write only by root, with no other access.
+\fINOT\fR
+be made available to anyone but the root user\. To protect these passwords the smbpasswd file is placed in a directory with read and traverse access only to the root user and the smbpasswd file itself must be set to be read/write only by root, with no other access\.
 .RE
 .PP
 Account Flags
+.RS 3n
+This section contains flags that describe the attributes of the users account. This field is bracketed by '[' and ']' characters and is always 13 characters in length (including the '[' and ']' characters). The contents of this field may be any of the following characters:
+.RS 3n
+.TP 3n
+\(bu
+\fBU\fR
+- This means this is a "User" account, i.e. an ordinary user.
+.TP 3n
+\(bu
+\fBN\fR
+- This means the account has no password (the passwords in the fields LANMAN Password Hash and NT Password Hash are ignored). Note that this will only allow users to log on with no password if the
+.RS 4
+This section contains flags that describe the attributes of the users account\. This field is bracketed by \'[\' and \']\' characters and is always 13 characters in length (including the \'[\' and \']\' characters)\. The contents of this field may be any of the following characters:
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\fIU\fR
+\- This means this is a "User" account, i\.e\. an ordinary user\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\fIN\fR
+\- This means the account has no password (the passwords in the fields LANMAN Password Hash and NT Password Hash are ignored)\. Note that this will only allow users to log on with no password if the
 \fI null passwords\fR
 parameter is set in the
 \fBsmb.conf\fR(5)
+config file.
+.TP 3n
+\(bu
+\fBD\fR
+- This means the account is disabled and no SMB/CIFS logins will be allowed for this user.
+.TP 3n
+\(bu
+\fBX\fR
+- This means the password does not expire.
+.TP 3n
+\(bu
+\fBW\fR
+- This means this account is a "Workstation Trust" account. This kind of account is used in the Samba PDC code stream to allow Windows NT Workstations and Servers to join a Domain hosted by a Samba PDC.
+config file\.
 .RE
+.IP "" 3n
+Other flags may be added as the code is extended in future. The rest of this field space is filled in with spaces. For further information regarding the flags that are supported please refer to the man page for the
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\fID\fR
+\- This means the account is disabled and no SMB/CIFS logins will be allowed for this user\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\fIX\fR
+\- This means the password does not expire\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\fIW\fR
+\- This means this account is a "Workstation Trust" account\. This kind of account is used in the Samba PDC code stream to allow Windows NT Workstations and Servers to join a Domain hosted by a Samba PDC\.
+.sp
+.RE
+Other flags may be added as the code is extended in future\. The rest of this field space is filled in with spaces\. For further information regarding the flags that are supported please refer to the man page for the
 pdbedit
 command.
+command\.
 .RE
 .PP
 Last Change Time
 .RS 3n
 This field consists of the time the account was last modified. It consists of the characters 'LCT-' (standing for "Last Change Time") followed by a numeric encoding of the UNIX time in seconds since the epoch (1970) that the last change was made.
+.RS 4
+This field consists of the time the account was last modified\. It consists of the characters \'LCT\-\' (standing for "Last Change Time") followed by a numeric encoding of the UNIX time in seconds since the epoch (1970) that the last change was made\.
 .RE
 .PP
 All other colon separated fields are ignored at this time.
+All other colon separated fields are ignored at this time\.
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 of the Samba suite\.
 .SH "SEE ALSO"
 .PP
 \fBsmbpasswd\fR(8),
 \fBSamba\fR(7), and the Internet RFC1321 for details on the MD4 algorithm.
+\fBSamba\fR(7), and the Internet RFC1321 for details on the MD4 algorithm\.
 .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.
+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.
+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\.

branches/samba-3.0/docs/manpages/smbpasswd.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "SMBPASSWD" 8 "" "" ""
+.\"     Title: smbpasswd
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "SMBPASSWD" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 smbpasswd - change a user's SMB password
 .SH "SYNOPSIS"
 .HP 1
 smbpasswd [-a] [-c <config file>] [-x] [-d] [-e] [-D debuglevel] [-n] [-r <remote machine>] [-R <name resolve order>] [-m] [-U username[%password]] [-h] [-s] [-w pass] [-W] [-i] [-L] [username]
+smbpasswd [\-a] [\-c\ <config\ file>] [\-x] [\-d] [\-e] [\-D\ debuglevel] [\-n] [\-r\ <remote\ machine>] [\-R\ <name\ resolve\ order>] [\-m] [\-U\ username[%password]] [\-h] [\-s] [\-w\ pass] [\-W] [\-i] [\-L] [username]
 .SH "DESCRIPTION"
 .PP
 This tool is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 The smbpasswd program has several different functions, depending on whether it is run by the
 \fBroot\fR
 user or not. When run as a normal user it allows the user to change the password used for their SMB sessions on any machines that store SMB passwords.
 .PP
 By default (when run with no arguments) it will attempt to change the current user's SMB password on the local machine. This is similar to the way the
+\fIroot\fR
+user or not\. When run as a normal user it allows the user to change the password used for their SMB sessions on any machines that store SMB passwords\.
+.PP
+By default (when run with no arguments) it will attempt to change the current user\'s SMB password on the local machine\. This is similar to the way the
 passwd(1)
 program works.
+program works\.
 smbpasswd
 differs from how the passwd program works however in that it is not
 \fBsetuid root\fR
 but works in a client-server mode and communicates with a locally running
 \fBsmbd\fR(8). As a consequence in order for this to succeed the smbd daemon must be running on the local machine. On a UNIX machine the encrypted SMB passwords are usually stored in the
+\fIsetuid root\fR
+but works in a client\-server mode and communicates with a locally running
+\fBsmbd\fR(8)\. As a consequence in order for this to succeed the smbd daemon must be running on the local machine\. On a UNIX machine the encrypted SMB passwords are usually stored in the
 \fBsmbpasswd\fR(5)
 file.
 .PP
 When run by an ordinary user with no options, smbpasswd will prompt them for their old SMB password and then ask them for their new password twice, to ensure that the new password was typed correctly. No passwords will be echoed on the screen whilst being typed. If you have a blank SMB password (specified by the string "NO PASSWORD" in the smbpasswd file) then just press the <Enter> key when asked for your old password.
 .PP
 smbpasswd can also be used by a normal user to change their SMB password on remote machines, such as Windows NT Primary Domain Controllers. See the (\fI-r\fR) and
 \fI-U\fR
 options below.
 .PP
 When run by root, smbpasswd allows new users to be added and deleted in the smbpasswd file, as well as allows changes to the attributes of the user in this file to be made. When run by root,
+file\.
+.PP
+When run by an ordinary user with no options, smbpasswd will prompt them for their old SMB password and then ask them for their new password twice, to ensure that the new password was typed correctly\. No passwords will be echoed on the screen whilst being typed\. If you have a blank SMB password (specified by the string "NO PASSWORD" in the smbpasswd file) then just press the <Enter> key when asked for your old password\.
+.PP
+smbpasswd can also be used by a normal user to change their SMB password on remote machines, such as Windows NT Primary Domain Controllers\. See the (\fI\-r\fR) and
+\fI\-U\fR
+options below\.
+.PP
+When run by root, smbpasswd allows new users to be added and deleted in the smbpasswd file, as well as allows changes to the attributes of the user in this file to be made\. When run by root,
 smbpasswd
 accesses the local smbpasswd file directly, thus enabling changes to be made even if smbd is not running.
+accesses the local smbpasswd file directly, thus enabling changes to be made even if smbd is not running\.
 .SH "OPTIONS"
 .PP
 -a
 .RS 3n
 This option specifies that the username following should be added to the local smbpasswd file, with the new password typed (type <Enter> for the old password). This option is ignored if the username following already exists in the smbpasswd file and it is treated like a regular change password command. Note that the default passdb backends require the user to already exist in the system password file (usually
 \fI/etc/passwd\fR), else the request to add the user will fail.
 .sp
 This option is only available when running smbpasswd as root.
 .RE
 .PP
 -c
 .RS 3n
+\-a
+.RS 4
+This option specifies that the username following should be added to the local smbpasswd file, with the new password typed (type <Enter> for the old password)\. This option is ignored if the username following already exists in the smbpasswd file and it is treated like a regular change password command\. Note that the default passdb backends require the user to already exist in the system password file (usually
+\fI/etc/passwd\fR), else the request to add the user will fail\.
+.sp
+This option is only available when running smbpasswd as root\.
+.RE
+.PP
+\-c
+.RS 4
 This option can be used to specify the path and file name of the
 \fIsmb.conf\fR
 configuration file when it is important to use other than the default file and / or location.
 .RE
 .PP
 -x
 .RS 3n
 This option specifies that the username following should be deleted from the local smbpasswd file.
 .sp
 This option is only available when running smbpasswd as root.
 .RE
 .PP
 -d
 .RS 3n
+\fIsmb\.conf\fR
+configuration file when it is important to use other than the default file and / or location\.
+.RE
+.PP
+\-x
+.RS 4
+This option specifies that the username following should be deleted from the local smbpasswd file\.
+.sp
+This option is only available when running smbpasswd as root\.
+.RE
+.PP
+\-d
+.RS 4
 This option specifies that the username following should be
 \fBdisabled\fR
 in the local smbpasswd file. This is done by writing a
 \fB'D'\fR
 flag into the account control space in the smbpasswd file. Once this is done all attempts to authenticate via SMB using this username will fail.
 .sp
 If the smbpasswd file is in the 'old' format (pre-Samba 2.0 format) there is no space in the user's password entry to write this information and the command will FAIL. See
+in the local smbpasswd file\. This is done by writing a
+\fB\'D\'\fR
+flag into the account control space in the smbpasswd file\. Once this is done all attempts to authenticate via SMB using this username will fail\.
+.sp
+If the smbpasswd file is in the \'old\' format (pre\-Samba 2\.0 format) there is no space in the user\'s password entry to write this information and the command will FAIL\. See
 \fBsmbpasswd\fR(5)
 for details on the 'old' and new password file formats.
 .sp
 This option is only available when running smbpasswd as root.
 .RE
 .PP
 -e
 .RS 3n
+for details on the \'old\' and new password file formats\.
+.sp
+This option is only available when running smbpasswd as root\.
+.RE
+.PP
+\-e
+.RS 4
 This option specifies that the username following should be
 \fBenabled\fR
 in the local smbpasswd file, if the account was previously disabled. If the account was not disabled this option has no effect. Once the account is enabled then the user will be able to authenticate via SMB once again.
 .sp
 If the smbpasswd file is in the 'old' format, then
+in the local smbpasswd file, if the account was previously disabled\. If the account was not disabled this option has no effect\. Once the account is enabled then the user will be able to authenticate via SMB once again\.
+.sp
+If the smbpasswd file is in the \'old\' format, then
 smbpasswd
 will FAIL to enable the account. See
+will FAIL to enable the account\. See
 \fBsmbpasswd\fR(5)
 for details on the 'old' and new password file formats.
 .sp
 This option is only available when running smbpasswd as root.
 .RE
 .PP
 -D debuglevel
 .RS 3n
+for details on the \'old\' and new password file formats\.
+.sp
+This option is only available when running smbpasswd as root\.
+.RE
+.PP
+\-D debuglevel
+.RS 4
 \fIdebuglevel\fR
 is an integer from 0 to 10. The default value if this parameter is not specified is zero.
 .sp
 The higher this value, the more detail will be logged to the log files about the activities of smbpasswd. At level 0, only critical errors and serious warnings will be logged.
 .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.
 .RE
 .PP
 -n
 .RS 3n
 This option specifies that the username following should have their password set to null (i.e. a blank password) in the local smbpasswd file. This is done by writing the string "NO PASSWORD" as the first part of the first password stored in the smbpasswd file.
+is an integer from 0 to 10\. The default value if this parameter is not specified is zero\.
+.sp
+The higher this value, the more detail will be logged to the log files about the activities of smbpasswd\. At level 0, only critical errors and serious warnings will be logged\.
+.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\.
+.RE
+.PP
+\-n
+.RS 4
+This option specifies that the username following should have their password set to null (i\.e\. a blank password) in the local smbpasswd file\. This is done by writing the string "NO PASSWORD" as the first part of the first password stored in the smbpasswd file\.
 .sp
 Note that to allow users to logon to a Samba server once the password has been set to "NO PASSWORD" in the smbpasswd file the administrator must set the following parameter in the [global] section of the
 \fIsmb.conf\fR
+\fIsmb\.conf\fR
 file :
 .sp
 null passwords = yes
 .sp
 This option is only available when running smbpasswd as root.
 .RE
 .PP
 -r remote machine name
 .RS 3n
 This option allows a user to specify what machine they wish to change their password on. Without this parameter smbpasswd defaults to the local host. The
+This option is only available when running smbpasswd as root\.
+.RE
+.PP
+\-r remote machine name
+.RS 4
+This option allows a user to specify what machine they wish to change their password on\. Without this parameter smbpasswd defaults to the local host\. The
 \fIremote machine name\fR
+is the NetBIOS name of the SMB/CIFS server to contact to attempt the password change. This name is resolved into an IP address using the standard name resolution mechanism in all programs of the Samba suite. See the
+\fI-R name resolve order\fR
+parameter for details on changing this resolving mechanism.
+.sp
+The username whose password is changed is that of the current UNIX logged on user. See the
+\fI-U username\fR
+parameter for details on changing the password for a different username.
+.sp
+Note that if changing a Windows NT Domain password the remote machine specified must be the Primary Domain Controller for the domain (Backup Domain Controllers only have a read-only copy of the user account database and will not allow the password change).
+.sp
+\fBNote\fR
+that Windows 95/98 do not have a real password database so it is not possible to change passwords specifying a Win95/98 machine as remote machine target.
+.RE
+.PP
+-R name resolve order
+.RS 3n
+This option allows the user of smbpasswd to determine what name resolution services to use when looking up the NetBIOS name of the host being connected to.
+.sp
+The options are :"lmhosts", "host", "wins" and "bcast". They cause names to be resolved as follows:
+.RS 3n
+.TP 3n
+\(bu
+\fBlmhosts\fR: Lookup an IP address in the Samba lmhosts file. If the line in lmhosts has no name type attached to the NetBIOS name (see the
+is the NetBIOS name of the SMB/CIFS server to contact to attempt the password change\. This name is resolved into an IP address using the standard name resolution mechanism in all programs of the Samba suite\. See the
+\fI\-R name resolve order\fR
+parameter for details on changing this resolving mechanism\.
+.sp
+The username whose password is changed is that of the current UNIX logged on user\. See the
+\fI\-U username\fR
+parameter for details on changing the password for a different username\.
+.sp
+Note that if changing a Windows NT Domain password the remote machine specified must be the Primary Domain Controller for the domain (Backup Domain Controllers only have a read\-only copy of the user account database and will not allow the password change)\.
+.sp
+\fINote\fR
+that Windows 95/98 do not have a real password database so it is not possible to change passwords specifying a Win95/98 machine as remote machine target\.
+.RE
+.PP
+\-R name resolve order
+.RS 4
+This option allows the user of smbpasswd to determine what name resolution services to use when looking up the NetBIOS name of the host being connected to\.
+.sp
+The options are :"lmhosts", "host", "wins" and "bcast"\. They cause names to be resolved as follows:
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\fBlmhosts\fR: Lookup an IP address in the Samba lmhosts file\. If the line in lmhosts has no name type attached to the NetBIOS name (see the
 \fBlmhosts\fR(5)
+for details) then any name type matches for lookup.
+.TP 3n
+\(bu
+for details) then any name type matches for lookup\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fBhost\fR: Do a standard host name to IP address resolution, using the system
+\fI/etc/hosts \fR, NIS, or DNS lookups. This method of name resolution is operating system depended for instance on IRIX or Solaris this may be controlled by the
+\fI/etc/nsswitch.conf\fR
+file). Note that this method is only used if the NetBIOS name type being queried is the 0x20 (server) name type, otherwise it is ignored.
+.TP 3n
+\(bu
+\fI/etc/hosts \fR, NIS, or DNS lookups\. This method of name resolution is operating system depended for instance on IRIX or Solaris this may be controlled by the
+\fI/etc/nsswitch\.conf\fR
+file)\. Note that this method is only used if the NetBIOS name type being queried is the 0x20 (server) name type, otherwise it is ignored\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fBwins\fR: Query a name with the IP address listed in the
 \fIwins server\fR
+parameter. If no WINS server has been specified this method will be ignored.
+.TP 3n
+\(bu
+parameter\. If no WINS server has been specified this method will be ignored\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fBbcast\fR: Do a broadcast on each of the known local interfaces listed in the
 \fIinterfaces\fR
 parameter. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet.
 .RE
 .IP "" 3n
+parameter\. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet\.
+.sp
+.RE
 The default order is
 lmhosts, host, wins, bcast
 and without this parameter or any entry in the
 \fBsmb.conf\fR(5)
 file the name resolution methods will be attempted in this order.
 .RE
 .PP
 -m
 .RS 3n
 This option tells smbpasswd that the account being changed is a MACHINE account. Currently this is used when Samba is being used as an NT Primary Domain Controller.
 .sp
 This option is only available when running smbpasswd as root.
 .RE
 .PP
 -U username
 .RS 3n
+file the name resolution methods will be attempted in this order\.
+.RE
+.PP
+\-m
+.RS 4
+This option tells smbpasswd that the account being changed is a MACHINE account\. Currently this is used when Samba is being used as an NT Primary Domain Controller\.
+.sp
+This option is only available when running smbpasswd as root\.
+.RE
+.PP
+\-U username
+.RS 4
 This option may only be used in conjunction with the
 \fI-r\fR
 option. When changing a password on a remote machine it allows the user to specify the user name on that machine whose password will be changed. It is present to allow users who have different user names on different systems to change these passwords.
 .RE
 .PP
 -h
 .RS 3n
+\fI\-r\fR
+option\. When changing a password on a remote machine it allows the user to specify the user name on that machine whose password will be changed\. It is present to allow users who have different user names on different systems to change these passwords\.
+.RE
+.PP
+\-h
+.RS 4
 This option prints the help string for
 smbpasswd, selecting the correct one for running as root or as an ordinary user.
 .RE
 .PP
 -s
 .RS 3n
 This option causes smbpasswd to be silent (i.e. not issue prompts) and to read its old and new passwords from standard input, rather than from
+smbpasswd, selecting the correct one for running as root or as an ordinary user\.
+.RE
+.PP
+\-s
+.RS 4
+This option causes smbpasswd to be silent (i\.e\. not issue prompts) and to read its old and new passwords from standard input, rather than from
 \fI/dev/tty\fR
 (like the
 passwd(1)
 program does). This option is to aid people writing scripts to drive smbpasswd
 .RE
 .PP
 -w password
 .RS 3n
 This parameter is only available if Samba has been compiled with LDAP support. The
 \fI-w\fR
+program does)\. This option is to aid people writing scripts to drive smbpasswd
+.RE
+.PP
+\-w password
+.RS 4
+This parameter is only available if Samba has been compiled with LDAP support\. The
+\fI\-w\fR
 switch is used to specify the password to be used with the
 ldap admin dn. Note that the password is stored in the
 \fIsecrets.tdb\fR
 and is keyed off of the admin's DN. This means that if the value of
+\fIldap admin dn\fR\. Note that the password is stored in the
+\fIsecrets\.tdb\fR
+and is keyed off of the admin\'s DN\. This means that if the value of
 \fIldap admin dn\fR
 ever changes, the password will need to be manually updated as well.
 .RE
 .PP
 -W
 .RS 3n
+ever changes, the password will need to be manually updated as well\.
+.RE
+.PP
+\-W
+.RS 4
 NOTE:
 This option is same as "-w" except that the password should be entered using stdin.
 .sp
 This parameter is only available if Samba has been compiled with LDAP support. The
 \fI-W\fR
+This option is same as "\-w" except that the password should be entered using stdin\.
+.sp
+This parameter is only available if Samba has been compiled with LDAP support\. The
+\fI\-W\fR
 switch is used to specify the password to be used with the
 ldap admin dn. Note that the password is stored in the
 \fIsecrets.tdb\fR
 and is keyed off of the admin's DN. This means that if the value of
+\fIldap admin dn\fR\. Note that the password is stored in the
+\fIsecrets\.tdb\fR
+and is keyed off of the admin\'s DN\. This means that if the value of
 \fIldap admin dn\fR
 ever changes, the password will need to be manually updated as well.
 .RE
 .PP
 -i
 .RS 3n
 This option tells smbpasswd that the account being changed is an interdomain trust account. Currently this is used when Samba is being used as an NT Primary Domain Controller. The account contains the info about another trusted domain.
 .sp
 This option is only available when running smbpasswd as root.
 .RE
 .PP
 -L
 .RS 3n
 Run in local mode.
+ever changes, the password will need to be manually updated as well\.
+.RE
+.PP
+\-i
+.RS 4
+This option tells smbpasswd that the account being changed is an interdomain trust account\. Currently this is used when Samba is being used as an NT Primary Domain Controller\. The account contains the info about another trusted domain\.
+.sp
+This option is only available when running smbpasswd as root\.
+.RE
+.PP
+\-L
+.RS 4
+Run in local mode\.
 .RE
 .PP
 username
 .RS 3n
+.RS 4
 This specifies the username for all of the
 \fBroot only\fR
 options to operate on. Only root can specify this parameter as only root has the permission needed to modify attributes directly in the local smbpasswd file.
+\fIroot only\fR
+options to operate on\. Only root can specify this parameter as only root has the permission needed to modify attributes directly in the local smbpasswd file\.
 .RE
 .SH "NOTES"
 …
 Since
 smbpasswd
 works in client-server mode communicating with a local smbd for a non-root user then the smbd daemon must be running for this to work. A common problem is to add a restriction to the hosts that may access the
+works in client\-server mode communicating with a local smbd for a non\-root user then the smbd daemon must be running for this to work\. A common problem is to add a restriction to the hosts that may access the
 smbd
 running on the local machine by specifying either
 …
 entry in the
 \fBsmb.conf\fR(5)
 file and neglecting to allow "localhost" access to the smbd.
 .PP
 In addition, the smbpasswd command is only useful if Samba has been set up to use encrypted passwords.
+file and neglecting to allow "localhost" access to the smbd\.
+.PP
+In addition, the smbpasswd command is only useful if Samba has been set up to use encrypted passwords\.
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 of the Samba suite\.
 .SH "SEE ALSO"
 .PP
 \fBsmbpasswd\fR(5),
 \fBSamba\fR(7).
+\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 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.
+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\.

branches/samba-3.0/docs/manpages/smbsh.1

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "SMBSH" 1 "" "" ""
+.\"     Title: smbsh
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: User Commands
+.\"    Source: Samba 3.0
+.\"
+.TH "SMBSH" "1" "05/21/2008" "Samba 3\.0" "User Commands"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 smbsh - Allows access to remote SMB shares using UNIX commands
 .SH "SYNOPSIS"
 .HP 1
 smbsh [-W workgroup] [-U username] [-P prefix] [-R <name resolve order>] [-d <debug level>] [-l logdir] [-L libdir]
+smbsh [\-W\ workgroup] [\-U\ username] [\-P\ prefix] [\-R\ <name\ resolve\ order>] [\-d\ <debug\ level>] [\-l\ logdir] [\-L\ libdir]
 .SH "DESCRIPTION"
 .PP
 This tool is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 smbsh
 …
 ls,
 egrep, and
 rcp. You must use a shell that is dynamically linked in order for
 smbsh
 to work correctly.
+rcp\. You must use a shell that is dynamically linked in order for
+smbsh
+to work correctly\.
 .SH "OPTIONS"
 .PP
 -W WORKGROUP
 .RS 3n
+\-W WORKGROUP
+.RS 4
 Override the default workgroup specified in the workgroup parameter of the
 \fBsmb.conf\fR(5)
 file for this session. This may be needed to connect to some servers.
 .RE
 .PP
 -U username[%pass]
 .RS 3n
 Sets the SMB username or username and password. If this option is not specified, the user will be prompted for both the username and the password. If %pass is not specified, the user will be prompted for the password.
 .RE
 .PP
 -P prefix
 .RS 3n
 This option allows the user to set the directory prefix for SMB access. The default value if this option is not specified is
 \fBsmb\fR.
 .RE
 .PP
 -s <configuration file>
 .RS 3n
 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
 \fIsmb.conf\fR
 for more information. The default configuration file name is determined at compile time.
 .RE
 .PP
 -d|--debuglevel=level
 .RS 3n
+file for this session\. This may be needed to connect to some servers\.
+.RE
+.PP
+\-U username[%pass]
+.RS 4
+Sets the SMB username or username and password\. If this option is not specified, the user will be prompted for both the username and the password\. If %pass is not specified, the user will be prompted for the password\.
+.RE
+.PP
+\-P prefix
+.RS 4
+This option allows the user to set the directory prefix for SMB access\. The default value if this option is not specified is
+\fIsmb\fR\.
+.RE
+.PP
+\-s <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
+\fIsmb\.conf\fR
+for more information\. The default configuration file name is determined at compile time\.
+.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 zero.
 .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.
+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
+\fIlog level\fR
 parameter in the
+\fIsmb.conf\fR
+file.
+.RE
+.PP
+-R <name resolve order>
+.RS 3n
+This option is used to determine what naming services and in what order to resolve host names to IP addresses. The option takes a space-separated string of different name resolution options.
+.sp
+The options are: "lmhosts", "host", "wins" and "bcast". They cause names to be resolved as follows :
+.RS 3n
+.TP 3n
+\(bu
+\fBlmhosts\fR: Lookup an IP address in the Samba lmhosts file. If the line in lmhosts has no name type attached to the NetBIOS name (see the
+\fIsmb\.conf\fR
+file\.
+.RE
+.PP
+\-R <name resolve order>
+.RS 4
+This option is used to determine what naming services and in what order to resolve host names to IP addresses\. The option takes a space\-separated string of different name resolution options\.
+.sp
+The options are: "lmhosts", "host", "wins" and "bcast"\. They cause names to be resolved as follows :
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\fBlmhosts\fR: Lookup an IP address in the Samba lmhosts file\. If the line in lmhosts has no name type attached to the NetBIOS name (see the
 \fBlmhosts\fR(5)
+for details) then any name type matches for lookup.
+.TP 3n
+\(bu
+for details) then any name type matches for lookup\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fBhost\fR: Do a standard host name to IP address resolution, using the system
+\fI/etc/hosts\fR, NIS, or DNS lookups. This method of name resolution is operating system dependent, for instance on IRIX or Solaris this may be controlled by the
+\fI/etc/nsswitch.conf \fR
+file). Note that this method is only used if the NetBIOS name type being queried is the 0x20 (server) name type, otherwise it is ignored.
+.TP 3n
+\(bu
+\fI/etc/hosts\fR, NIS, or DNS lookups\. This method of name resolution is operating system dependent, for instance on IRIX or Solaris this may be controlled by the
+\fI/etc/nsswitch\.conf \fR
+file)\. Note that this method is only used if the NetBIOS name type being queried is the 0x20 (server) name type, otherwise it is ignored\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fBwins\fR: Query a name with the IP address listed in the
 \fIwins server\fR
+parameter. If no WINS server has been specified this method will be ignored.
+.TP 3n
+\(bu
+parameter\. If no WINS server has been specified this method will be ignored\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 \fBbcast\fR: Do a broadcast on each of the known local interfaces listed in the
 \fIinterfaces\fR
 parameter. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet.
 .RE
 .IP "" 3n
+parameter\. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet\.
+.sp
+.RE
 If this parameter is not set then the name resolve order defined in the
 \fIsmb.conf\fR
 file parameter () will be used.
 .sp
 The default order is lmhosts, host, wins, bcast. Without this parameter or any entry in the
+\fIsmb\.conf\fR
+file parameter (\fIname resolve order\fR) will be used\.
+.sp
+The default order is lmhosts, host, wins, bcast\. Without this parameter or any entry in the
+\fIname resolve order\fR
 parameter of the
 \fIsmb.conf\fR
 file, the name resolution methods will be attempted in this order.
 .RE
 .PP
 -L libdir
 .RS 3n
+\fIsmb\.conf\fR
+file, the name resolution methods will be attempted in this order\.
+.RE
+.PP
+\-L libdir
+.RS 4
 This parameter specifies the location of the shared libraries used by
 smbsh. The default value is specified at compile time.
+smbsh\. The default value is specified at compile time\.
 .RE
 .SH "EXAMPLES"
 …
 command, execute
 smbsh
+from the prompt and enter the username and password that authenticates you to the machine running the Windows NT operating system.
+.sp
+from the prompt and enter the username and password that authenticates you to the machine running the Windows NT operating system\.
+.sp
+.RS 4
 .nf
 system% \fBsmbsh\fR
 Username: \fBuser\fR
 Password: \fBXXXXXXX\fR
 .fi
+.RE
 .PP
 Any dynamically linked command you execute from this shell will access the
 \fI/smb\fR
 directory using the smb protocol. For example, the command
+directory using the smb protocol\. For example, the command
 ls /smb
 will show a list of workgroups. The command
+will show a list of workgroups\. The command
 ls /smb/MYGROUP
 will show all the machines in the workgroup MYGROUP. The command
 ls /smb/MYGROUP/<machine-name>
 will show the share names for that machine. You could then, for example, use the
+will show all the machines in the workgroup MYGROUP\. The command
+ls /smb/MYGROUP/<machine\-name>
+will show the share names for that machine\. You could then, for example, use the
 cd
 command to change directories,
 …
 to edit files, and
 rcp
 to copy files.
+to copy files\.
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 of the Samba suite\.
 .SH "BUGS"
 .PP
 smbsh
 works by intercepting the standard libc calls with the dynamically loaded versions in
 \fI smbwrapper.o\fR. Not all calls have been "wrapped", so some programs may not function correctly under
 smbsh.
+\fI smbwrapper\.o\fR\. Not all calls have been "wrapped", so some programs may not function correctly under
+smbsh\.
 .PP
 Programs which are not dynamically linked cannot make use of
 smbsh's functionality. Most versions of UNIX have a
+smbsh\'s functionality\. Most versions of UNIX have a
 file
 command that will describe how a program was linked.
+command that will describe how a program was linked\.
 .SH "SEE ALSO"
 .PP
 …
 .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.
+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\.

branches/samba-3.0/docs/manpages/smbspool.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "SMBSPOOL" 8 "" "" ""
+.\"     Title: smbspool
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "SMBSPOOL" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 smbspool - send a print file to an SMB printer
 …
 This tool is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 smbspool is a very small print spooling program that sends a print file to an SMB printer. The command-line arguments are position-dependent for compatibility with the Common UNIX Printing System, but you can use smbspool with any printing system or from a program or script.
+smbspool is a very small print spooling program that sends a print file to an SMB printer\. The command\-line arguments are position\-dependent for compatibility with the Common UNIX Printing System, but you can use smbspool with any printing system or from a program or script\.
 .PP
 \fBDEVICE URI\fR
+\fIDEVICE URI\fR
 .PP
+smbspool specifies the destination using a Uniform Resource Identifier ("URI") with a method of "smb". This string can take a number of forms:
+.TP 3n
+\(bu
+smbspool specifies the destination using a Uniform Resource Identifier ("URI") with a method of "smb"\. This string can take a number of forms:
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 smb://server[:port]/printer
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 smb://workgroup/server[:port]/printer
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 smb://username:password@server[:port]/printer
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 smb://username:password@workgroup/server[:port]/printer
+.sp
+.RE
 .PP
 smbspool tries to get the URI from the environment variable
 \fBDEVICE_URI\fR. If
+\fBDEVICE_URI\fR\. If
 \fBDEVICE_URI\fR
 is not present, smbspool will use argv[0] if that starts with
 \fBsmb://\fR
 or argv[1] if that is not the case.
+\(lqsmb://\(rq
+or argv[1] if that is not the case\.
 .PP
 Programs using the
 …
 functions can pass the URI in argv[0], while shell scripts must set the
 \fBDEVICE_URI\fR
 environment variable prior to running smbspool.
+environment variable prior to running smbspool\.
 .SH "OPTIONS"
+.TP 3n
+\(bu
+The job argument (argv[1]) contains the job ID number and is presently not used by smbspool.
+.TP 3n
+\(bu
+The user argument (argv[2]) contains the print user's name and is presently not used by smbspool.
+.TP 3n
+\(bu
+The title argument (argv[3]) contains the job title string and is passed as the remote file name when sending the print job.
+.TP 3n
+\(bu
+The copies argument (argv[4]) contains the number of copies to be printed of the named file. If no filename is provided then this argument is not used by smbspool.
+.TP 3n
+\(bu
+The options argument (argv[5]) contains the print options in a single string and is currently not used by smbspool.
+.TP 3n
+\(bu
+The filename argument (argv[6]) contains the name of the file to print. If this argument is not specified then the print file is read from the standard input.
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+The job argument (argv[1]) contains the job ID number and is presently not used by smbspool\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+The user argument (argv[2]) contains the print user\'s name and is presently not used by smbspool\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+The title argument (argv[3]) contains the job title string and is passed as the remote file name when sending the print job\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+The copies argument (argv[4]) contains the number of copies to be printed of the named file\. If no filename is provided then this argument is not used by smbspool\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+The options argument (argv[5]) contains the print options in a single string and is currently not used by smbspool\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+The filename argument (argv[6]) contains the name of the file to print\. If this argument is not specified then the print file is read from the standard input\.
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 of the Samba suite\.
 .SH "SEE ALSO"
 .PP
 \fBsmbd\fR(8)
 and
 \fBsamba\fR(7).
+\fBsamba\fR(7)\.
 .SH "AUTHOR"
 .PP
 smbspool
 was written by Michael Sweet at Easy Software Products.
+was written by Michael Sweet at Easy Software Products\.
 .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.
+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.
+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\.

branches/samba-3.0/docs/manpages/smbstatus.1

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "SMBSTATUS" 1 "" "" ""
+.\"     Title: smbstatus
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: User Commands
+.\"    Source: Samba 3.0
+.\"
+.TH "SMBSTATUS" "1" "05/21/2008" "Samba 3\.0" "User Commands"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 smbstatus - report on current Samba connections
 .SH "SYNOPSIS"
 .HP 1
 smbstatus [-P] [-b] [-d <debug level>] [-v] [-L] [-B] [-p] [-S] [-s <configuration file>] [-u <username>]
+smbstatus [\-P] [\-b] [\-d\ <debug\ level>] [\-v] [\-L] [\-B] [\-p] [\-S] [\-s\ <configuration\ file>] [\-u\ <username>]
 .SH "DESCRIPTION"
 .PP
 This tool is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 smbstatus
 is a very simple program to list the current Samba connections.
+is a very simple program to list the current Samba connections\.
 .SH "OPTIONS"
 .PP
 -P|--profile
 .RS 3n
 If samba has been compiled with the profiling option, print only the contents of the profiling shared memory area.
+\-P|\-\-profile
+.RS 4
+If samba has been compiled with the profiling option, print only the contents of the profiling shared memory area\.
 .RE
 .PP
 -b|--brief
 .RS 3n
 gives brief output.
+\-b|\-\-brief
+.RS 4
+gives brief output\.
 .RE
 .PP
+-V
+.RS 3n
+Prints the program version number.
+\-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
+\fIlog level\fR
+parameter in the
+\fIsmb\.conf\fR
+file\.
 .RE
 .PP
+-s <configuration file>
+.RS 3n
+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
+\fIsmb.conf\fR
+for more information. The default configuration file name is determined at compile time.
+\-V
+.RS 4
+Prints the program version number\.
 .RE
 .PP
+-d|--debuglevel=level
+.RS 3n
+\fIlevel\fR
+is an integer from 0 to 10. The default value if this parameter is not specified is zero.
+.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
+parameter in the
+\fIsmb.conf\fR
+file.
+\-s <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
+\fIsmb\.conf\fR
+for more information\. The default configuration file name is determined at compile time\.
 .RE
 .PP
 -l|--logfile=logdirectory
 .RS 3n
 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.
+\-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
 -v|--verbose
 .RS 3n
 gives verbose output.
+\-v|\-\-verbose
+.RS 4
+gives verbose output\.
 .RE
 .PP
 -L|--locks
 .RS 3n
 causes smbstatus to only list locks.
+\-L|\-\-locks
+.RS 4
+causes smbstatus to only list locks\.
 .RE
 .PP
 -B|--byterange
 .RS 3n
 causes smbstatus to include byte range locks.
+\-B|\-\-byterange
+.RS 4
+causes smbstatus to include byte range locks\.
 .RE
 .PP
 -p|--processes
 .RS 3n
+\-p|\-\-processes
+.RS 4
 print a list of
 \fBsmbd\fR(8)
 processes and exit. Useful for scripting.
+processes and exit\. Useful for scripting\.
 .RE
 .PP
 -S|--shares
 .RS 3n
 causes smbstatus to only list shares.
+\-S|\-\-shares
+.RS 4
+causes smbstatus to only list shares\.
 .RE
 .PP
 -h|--help
 .RS 3n
 Print a summary of command line options.
+\-h|\-\-help
+.RS 4
+Print a summary of command line options\.
 .RE
 .PP
 -u|--user=<username>
 .RS 3n
+\-u|\-\-user=<username>
+.RS 4
 selects information relevant to
 \fIusername\fR
 only.
+only\.
 .RE
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 of the Samba suite\.
 .SH "SEE ALSO"
 .PP
 \fBsmbd\fR(8)
 and
 \fBsmb.conf\fR(5).
+\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.
+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.
+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\.

branches/samba-3.0/docs/manpages/smbtar.1

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "SMBTAR" 1 "" "" ""
+.\"     Title: smbtar
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: User Commands
+.\"    Source: Samba 3.0
+.\"
+.TH "SMBTAR" "1" "05/21/2008" "Samba 3\.0" "User Commands"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 smbtar - shell script for backing up SMB/CIFS shares directly to UNIX tape drives
 .SH "SYNOPSIS"
 .HP 1
 smbtar [-r] [-i] [-a] [-v] {-s server} [-p password] [-x services] [-X] [-N filename] [-b blocksize] [-d directory] [-l loglevel] [-u user] [-t tape] {filenames}
+smbtar [\-r] [\-i] [\-a] [\-v] {\-s\ server} [\-p\ password] [\-x\ services] [\-X] [\-N\ filename] [\-b\ blocksize] [\-d\ directory] [\-l\ loglevel] [\-u\ user] [\-t\ tape] {filenames}
 .SH "DESCRIPTION"
 .PP
 This tool is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 smbtar
 is a very small shell script on top of
 \fBsmbclient\fR(1)
 which dumps SMB shares directly to tape.
+which dumps SMB shares directly to tape\.
 .SH "OPTIONS"
 .PP
 -s server
 .RS 3n
 The SMB/CIFS server that the share resides upon.
+\-s server
+.RS 4
+The SMB/CIFS server that the share resides upon\.
 .RE
 .PP
 -x service
 .RS 3n
 The share name on the server to connect to. The default is "backup".
+\-x service
+.RS 4
+The share name on the server to connect to\. The default is "backup"\.
 .RE
 .PP
 -X
 .RS 3n
 Exclude mode. Exclude filenames... from tar create or restore.
+\-X
+.RS 4
+Exclude mode\. Exclude filenames\.\.\. from tar create or restore\.
 .RE
 .PP
 -d directory
 .RS 3n
+\-d directory
+.RS 4
 Change to initial
 \fIdirectory \fR
 before restoring / backing up files.
+before restoring / backing up files\.
 .RE
 .PP
 -v
 .RS 3n
 Verbose mode.
+\-v
+.RS 4
+Verbose mode\.
 .RE
 .PP
 -p password
 .RS 3n
 The password to use to access a share. Default: none
+\-p password
+.RS 4
+The password to use to access a share\. Default: none
 .RE
 .PP
 -u user
 .RS 3n
 The user id to connect as. Default: UNIX login name.
+\-u user
+.RS 4
+The user id to connect as\. Default: UNIX login name\.
 .RE
 .PP
 -a
 .RS 3n
 Reset DOS archive bit mode to indicate file has been archived.
+\-a
+.RS 4
+Reset DOS archive bit mode to indicate file has been archived\.
 .RE
 .PP
 -t tape
 .RS 3n
 Tape device. May be regular file or tape device. Default:
+\-t tape
+.RS 4
+Tape device\. May be regular file or tape device\. Default:
 \fI$TAPE\fR
 environmental variable; if not set, a file called
 \fItar.out \fR.
+\fItar\.out \fR\.
 .RE
 .PP
 -b blocksize
 .RS 3n
 Blocking factor. Defaults to 20. See
+\-b blocksize
+.RS 4
+Blocking factor\. Defaults to 20\. See
 tar(1)
 for a fuller explanation.
+for a fuller explanation\.
 .RE
 .PP
 -N filename
 .RS 3n
 Backup only files newer than filename. Could be used (for example) on a log file to implement incremental backups.
+\-N filename
+.RS 4
+Backup only files newer than filename\. Could be used (for example) on a log file to implement incremental backups\.
 .RE
 .PP
 -i
 .RS 3n
 Incremental mode; tar files are only backed up if they have the archive bit set. The archive bit is reset after each file is read.
+\-i
+.RS 4
+Incremental mode; tar files are only backed up if they have the archive bit set\. The archive bit is reset after each file is read\.
 .RE
 .PP
 -r
 .RS 3n
 Restore. Files are restored to the share from the tar file.
+\-r
+.RS 4
+Restore\. Files are restored to the share from the tar file\.
 .RE
 .PP
 -l log level
 .RS 3n
 Log (debug) level. Corresponds to the
 \fI-d\fR
+\-l log level
+.RS 4
+Log (debug) level\. Corresponds to the
+\fI\-d\fR
 flag of
 \fBsmbclient\fR(1).
+\fBsmbclient\fR(1)\.
 .RE
 .SH "ENVIRONMENT VARIABLES"
 …
 The
 \fI$TAPE\fR
 variable specifies the default tape device to write to. May be overridden with the -t option.
+variable specifies the default tape device to write to\. May be overridden with the \-t option\.
 .SH "BUGS"
 .PP
 The
 smbtar
 script has different options from ordinary tar and from smbclient's tar command.
+script has different options from ordinary tar and from smbclient\'s tar command\.
 .SH "CAVEATS"
 .PP
 Sites that are more careful about security may not like the way the script handles PC passwords. Backup and restore work on entire shares; should work on file lists. smbtar works best with GNU tar and may not work well with other versions.
+Sites that are more careful about security may not like the way the script handles PC passwords\. Backup and restore work on entire shares; should work on file lists\. smbtar works best with GNU tar and may not work well with other versions\.
 .SH "DIAGNOSTICS"
 .PP
 See the
 \fBDIAGNOSTICS\fR
+\fIDIAGNOSTICS\fR
 section for the
 \fBsmbclient\fR(1)
 command.
+command\.
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 of the Samba suite\.
 .SH "SEE ALSO"
 .PP
 \fBsmbd\fR(8),
 \fBsmbclient\fR(1),
 \fBsmb.conf\fR(5).
+\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.
+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
 Ricky Poulten
 wrote the tar extension and this man page. The
+wrote the tar extension and this man page\. The
 smbtar
 script was heavily rewritten and improved by
+Martin Kraemer. Many thanks to everyone who suggested extensions, improvements, bug fixes, etc. 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.
+Martin Kraemer\. Many thanks to everyone who suggested extensions, improvements, bug fixes, etc\. 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\.

branches/samba-3.0/docs/manpages/smbtree.1

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "SMBTREE" 1 "" "" ""
+.\"     Title: smbtree
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: User Commands
+.\"    Source: Samba 3.0
+.\"
+.TH "SMBTREE" "1" "05/21/2008" "Samba 3\.0" "User Commands"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 smbtree - A text based smb network browser
 .SH "SYNOPSIS"
 .HP 1
 smbtree [-b] [-D] [-S]
+smbtree [\-b] [\-D] [\-S]
 .SH "DESCRIPTION"
 .PP
 This tool is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 smbtree
 is a smb browser program in text mode. It is similar to the "Network Neighborhood" found on Windows computers. It prints a tree with all the known domains, the servers in those domains and the shares on the servers.
+is a smb browser program in text mode\. It is similar to the "Network Neighborhood" found on Windows computers\. It prints a tree with all the known domains, the servers in those domains and the shares on the servers\.
 .SH "OPTIONS"
 .PP
 -b
 .RS 3n
 Query network nodes by sending requests as broadcasts instead of querying the local master browser.
+\-b
+.RS 4
+Query network nodes by sending requests as broadcasts instead of querying the local master browser\.
 .RE
 .PP
 -D
 .RS 3n
+\-D
+.RS 4
 Only print a list of all the domains known on broadcast or by the master browser
 .RE
 .PP
 -S
 .RS 3n
 Only print a list of all the domains and servers responding on broadcast or known by the master browser.
+\-S
+.RS 4
+Only print a list of all the domains and servers responding on broadcast or known by the master browser\.
 .RE
 .PP
+-V
+.RS 3n
+Prints the program version number.
+\-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
+\fIlog level\fR
+parameter in the
+\fIsmb\.conf\fR
+file\.
 .RE
 .PP
+-s <configuration file>
+.RS 3n
+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
+\fIsmb.conf\fR
+for more information. The default configuration file name is determined at compile time.
+\-V
+.RS 4
+Prints the program version number\.
 .RE
 .PP
+-d|--debuglevel=level
+.RS 3n
+\fIlevel\fR
+is an integer from 0 to 10. The default value if this parameter is not specified is zero.
+.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
+parameter in the
+\fIsmb.conf\fR
+file.
+\-s <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
+\fIsmb\.conf\fR
+for more information\. The default configuration file name is determined at compile time\.
 .RE
 .PP
 -l|--logfile=logdirectory
 .RS 3n
 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.
+\-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
 -N
 .RS 3n
 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.
+\-N
+.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.
+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.
+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
 .RS 3n
 Try to authenticate with kerberos. Only useful in an Active Directory environment.
+\-k
+.RS 4
+Try to authenticate with kerberos\. Only useful in an Active Directory environment\.
 .RE
 .PP
 -A|--authentication-file=filename
 .RS 3n
 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
+\-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
 .sp
+.RS 4
 .nf
 username = <value>
 password = <value>
 domain   = <value>
 .fi
+.RE
 .sp
 Make certain that the permissions on the file restrict access from unwanted users.
+Make certain that the permissions on the file restrict access from unwanted users\.
 .RE
 .PP
 -U|--user=username[%password]
 .RS 3n
 Sets the SMB username or username and password.
+\-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
+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
+variable and if either exists, the string is uppercased\. If these environmental variables are not found, the username
 \fBGUEST\fR
 is used.
+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.
+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
+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
+command\. To be safe always allow
 rpcclient
 to prompt for a password and type it in directly.
+to prompt for a password and type it in directly\.
 .RE
 .PP
 -h|--help
 .RS 3n
 Print a summary of command line options.
+\-h|\-\-help
+.RS 4
+Print a summary of command line options\.
 .RE
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 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.
+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 smbtree man page was written by Jelmer Vernooij.
+The smbtree man page was written by Jelmer Vernooij\.

branches/samba-3.0/docs/manpages/smbumount.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "SMBUMOUNT" 8 "" "" ""
+.\"     Title: smbumount
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual:
+.\"    Source:
+.\"
+.TH "SMBUMOUNT" "8" "05/21/2008" "" ""
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 smbumount - smbfs umount for normal users
 .SH "SYNOPSIS"
 .HP 1
 smbumount {mount-point}
+smbumount {mount\-point}
 .SH "DESCRIPTION"
 .PP
 With this program, normal users can unmount smb-filesystems, provided that it is suid root.
+With this program, normal users can unmount smb\-filesystems, provided that it is suid root\.
 smbumount
 has been written to give normal Linux users more control over their resources. It is safe to install this program suid root, because only the user who has mounted a filesystem is allowed to unmount it again. For root it is not necessary to use smbumount. The normal umount program works perfectly well.
+has been written to give normal Linux users more control over their resources\. It is safe to install this program suid root, because only the user who has mounted a filesystem is allowed to unmount it again\. For root it is not necessary to use smbumount\. The normal umount program works perfectly well\.
 .PP
 WARNING:
 smbumount
 is deprecated and not maintained any longer.
 umount.cifs
+is deprecated and not maintained any longer\.
+umount\.cifs
 should be used instead of
 smbumount.
+smbumount\.
 .SH "OPTIONS"
 .PP
 mount-point
 .RS 3n
 The directory to unmount.
+mount\-point
+.RS 4
+The directory to unmount\.
 .RE
 .SH "SEE ALSO"
 …
 .SH "AUTHOR"
 .PP
 Volker Lendecke, Andrew Tridgell, Michael H. Warfield and others.
+Volker Lendecke, Andrew Tridgell, Michael H\. Warfield and others\.
 .PP
 The current maintainer of smbfs and the userspace tools
 …
 smbmnt
 is
 Urban Widmark. The
+Urban Widmark\. The
 SAMBA Mailing list
 is the preferred place to ask questions regarding these programs.
+is the preferred place to ask questions regarding these programs\.
 .PP
+The conversion of this manpage for Samba 2.2 was performed by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.
+The conversion of this manpage for Samba 2\.2 was performed by Gerald Carter\. The conversion to DocBook XML 4\.2 for Samba 3\.0 was done by Alexander Bokovoy\.

branches/samba-3.0/docs/manpages/swat.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "SWAT" 8 "" "" ""
+.\"     Title: swat
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "SWAT" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 swat - Samba Web Administration Tool
 .SH "SYNOPSIS"
 .HP 1
 swat [-s <smb config file>] [-a] [-P]
+swat [\-s\ <smb\ config\ file>] [\-a] [\-P]
 .SH "DESCRIPTION"
 .PP
 This tool is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 swat
 allows a Samba administrator to configure the complex
 \fBsmb.conf\fR(5)
 file via a Web browser. In addition, a
+file via a Web browser\. In addition, a
 swat
 configuration page has help links to all the configurable options in the
 \fIsmb.conf\fR
 file allowing an administrator to easily look up the effects of any change.
+\fIsmb\.conf\fR
+file allowing an administrator to easily look up the effects of any change\.
 .PP
 swat
 …
 .SH "OPTIONS"
 .PP
 -s smb configuration file
 .RS 3n
 The default configuration file path is determined at compile time. The file specified contains the configuration details required by the
+\-s smb configuration file
+.RS 4
+The default configuration file path is determined at compile time\. The file specified contains the configuration details required by the
 \fBsmbd\fR(8)
 server. This is the file that
 swat
 will modify. 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
 \fIsmb.conf\fR
 for more information.
 .RE
 .PP
 -a
 .RS 3n
+server\. This is the file that
+swat
+will modify\. 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
+\fIsmb\.conf\fR
+for more information\.
+.RE
+.PP
+\-a
+.RS 4
 This option disables authentication and places
 swat
+in demo mode. In that mode anyone will be able to modify the
+\fIsmb.conf\fR
+file.
+.sp
+\fBWARNING: Do NOT enable this option on a production server. \fR
+.RE
+.PP
+-P
+.RS 3n
+This option restricts read-only users to the password management page.
+swat
+can then be used to change user passwords without users seeing the "View" and "Status" menu buttons.
+.RE
+.PP
+-V
+.RS 3n
+Prints the program version number.
+.RE
+.PP
+-s <configuration file>
+.RS 3n
+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
+\fIsmb.conf\fR
+for more information. The default configuration file name is determined at compile time.
+.RE
+.PP
+-d|--debuglevel=level
+.RS 3n
+in demo mode\. In that mode anyone will be able to modify the
+\fIsmb\.conf\fR
+file\.
+.sp
+\fIWARNING: Do NOT enable this option on a production server\. \fR
+.RE
+.PP
+\-P
+.RS 4
+This option restricts read\-only users to the password management page\.
+swat
+can then be used to change user passwords without users seeing the "View" and "Status" menu buttons\.
+.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 zero.
 .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.
+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
+\fIlog level\fR
 parameter in the
+\fIsmb.conf\fR
+file.
+.RE
+.PP
+-l|--logfile=logdirectory
+.RS 3n
+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
+-h|--help
+.RS 3n
+Print a summary of command line options.
+\fIsmb\.conf\fR
+file\.
+.RE
+.PP
+\-V
+.RS 4
+Prints the program version number\.
+.RE
+.PP
+\-s <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
+\fIsmb\.conf\fR
+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
+\-h|\-\-help
+.RS 4
+Print a summary of command line options\.
 .RE
 .SH "INSTALLATION"
 .PP
 Swat is included as binary package with most distributions. The package manager in this case takes care of the installation and configuration. This section is only for those who have compiled swat from scratch.
+Swat is included as binary package with most distributions\. The package manager in this case takes care of the installation and configuration\. This section is only for those who have compiled swat from scratch\.
 .PP
 After you compile SWAT you need to run
 …
 to install the
 swat
+binary and the various help files and images. A default install would put these in:
+.TP 3n
+\(bu
+binary and the various help files and images\. A default install would put these in:
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 /usr/local/samba/sbin/swat
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 /usr/local/samba/swat/images/*
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 /usr/local/samba/swat/help/*
+.sp
+.RE
 .SS "Inetd Installation"
 .PP
 You need to edit your
 \fI/etc/inetd.conf \fR
+\fI/etc/inetd\.conf \fR
 and
 \fI/etc/services\fR
 to enable SWAT to be launched via
 inetd.
+inetd\.
 .PP
 In
 …
 swat 901/tcp
 .PP
 Note for NIS/YP and LDAP users - you may need to rebuild the NIS service maps rather than alter your local
+Note for NIS/YP and LDAP users \- you may need to rebuild the NIS service maps rather than alter your local
 \fI /etc/services\fR
 file.
 .PP
 the choice of port number isn't really important except that it should be less than 1024 and not currently used (using a number above 1024 presents an obscure security hole depending on the implementation details of your
+file\.
+.PP
+the choice of port number isn\'t really important except that it should be less than 1024 and not currently used (using a number above 1024 presents an obscure security hole depending on the implementation details of your
 inetd
 daemon).
+daemon)\.
 .PP
 In
 \fI/etc/inetd.conf\fR
+\fI/etc/inetd\.conf\fR
 you should add a line like this:
 .PP
 swat stream tcp nowait.400 root /usr/local/samba/sbin/swat swat
+swat stream tcp nowait\.400 root /usr/local/samba/sbin/swat swat
 .PP
 Once you have edited
 \fI/etc/services\fR
 and
 \fI/etc/inetd.conf\fR
 you need to send a HUP signal to inetd. To do this use
 kill -1 PID
 where PID is the process ID of the inetd daemon.
+\fI/etc/inetd\.conf\fR
+you need to send a HUP signal to inetd\. To do this use
+kill \-1 PID
+where PID is the process ID of the inetd daemon\.
 .SH "LAUNCHING"
 .PP
 To launch SWAT just run your favorite web browser and point it at "http://localhost:901/".
 .PP
 Note that you can attach to SWAT from any IP connected machine but connecting from a remote machine leaves your connection open to password sniffing as passwords will be sent in the clear over the wire.
+To launch SWAT just run your favorite web browser and point it at "http://localhost:901/"\.
+.PP
+Note that you can attach to SWAT from any IP connected machine but connecting from a remote machine leaves your connection open to password sniffing as passwords will be sent in the clear over the wire\.
 .SH "FILES"
 .PP
 \fI/etc/inetd.conf\fR
 .RS 3n
 This file must contain suitable startup information for the meta-daemon.
 .RE
 .PP
 \fI/etc/services\fR
 .RS 3n
 This file must contain a mapping of service name (e.g., swat) to service port (e.g., 901) and protocol type (e.g., tcp).
 .RE
 .PP
 \fI/usr/local/samba/lib/smb.conf\fR
 .RS 3n
+\fI/etc/inetd\.conf\fR
+.RS 4
+This file must contain suitable startup information for the meta\-daemon\.
+.RE
+.PP
+\fI/etc/services\fR
+.RS 4
+This file must contain a mapping of service name (e\.g\., swat) to service port (e\.g\., 901) and protocol type (e\.g\., tcp)\.
+.RE
+.PP
+\fI/usr/local/samba/lib/smb\.conf\fR
+.RS 4
 This is the default location of the
 \fBsmb.conf\fR(5)
 server configuration file that swat edits. Other common places that systems install this file are
 \fI /usr/samba/lib/smb.conf\fR
 and
 \fI/etc/smb.conf \fR. This file describes all the services the server is to make available to clients.
+server configuration file that swat edits\. Other common places that systems install this file are
+\fI /usr/samba/lib/smb\.conf\fR
+and
+\fI/etc/smb\.conf \fR\. This file describes all the services the server is to make available to clients\.
 .RE
 .SH "WARNINGS"
 …
 will rewrite your
 \fBsmb.conf\fR(5)
 file. It will rearrange the entries and delete all comments,
+file\. It will rearrange the entries and delete all comments,
 \fIinclude=\fR
 and
 \fIcopy= \fR
 options. If you have a carefully crafted
 \fI smb.conf\fR
 then back it up or don't use swat!
+options\. If you have a carefully crafted
+\fI smb\.conf\fR
+then back it up or don\'t use swat!
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 of the Samba suite\.
 .SH "SEE ALSO"
 .PP
 …
 .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.
+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\.

branches/samba-3.0/docs/manpages/tdbbackup.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "TDBBACKUP" 8 "" "" ""
+.\"     Title: tdbbackup
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "TDBBACKUP" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 tdbbackup - tool for backing up and for validating the integrity of samba .tdb files
 .SH "SYNOPSIS"
 .HP 1
 tdbbackup [-s suffix] [-v] [-h]
+tdbbackup [\-s\ suffix] [\-v] [\-h]
 .SH "DESCRIPTION"
 .PP
 This tool is part of the
 \fBsamba\fR(1)
 suite.
+suite\.
 .PP
 tdbbackup
 is a tool that may be used to backup samba .tdb files. This tool may also be used to verify the integrity of the .tdb files prior to samba startup or during normal operation. If it finds file damage and it finds a prior backup the backup file will be restored.
+is a tool that may be used to backup samba \.tdb files\. This tool may also be used to verify the integrity of the \.tdb files prior to samba startup or during normal operation\. If it finds file damage and it finds a prior backup the backup file will be restored\.
 .SH "OPTIONS"
 .PP
 -h
 .RS 3n
 Get help information.
+\-h
+.RS 4
+Get help information\.
 .RE
 .PP
 -s suffix
 .RS 3n
+\-s suffix
+.RS 4
 The
 -s
 option allows the adminisistrator to specify a file backup extension. This way it is possible to keep a history of tdb backup files by using a new suffix for each backup.
+\-s
+option allows the adminisistrator to specify a file backup extension\. This way it is possible to keep a history of tdb backup files by using a new suffix for each backup\.
 .RE
 .PP
 -v
 .RS 3n
+\-v
+.RS 4
 The
 -v
 will check the database for damages (currupt data) which if detected causes the backup to be restored.
+\-v
+will check the database for damages (currupt data) which if detected causes the backup to be restored\.
 .RE
 .SH "COMMANDS"
 .PP
 \fBGENERAL INFORMATION\fR
+\fIGENERAL INFORMATION\fR
 .PP
 The
 tdbbackup
 utility can safely be run at any time. It was designed so that it can be used at any time to validate the integrity of tdb files, even during Samba operation. Typical usage for the command will be:
+utility can safely be run at any time\. It was designed so that it can be used at any time to validate the integrity of tdb files, even during Samba operation\. Typical usage for the command will be:
 .PP
 tdbbackup [-s suffix] *.tdb
+tdbbackup [\-s suffix] *\.tdb
 .PP
 Before restarting samba the following command may be run to validate .tdb files:
+Before restarting samba the following command may be run to validate \.tdb files:
 .PP
 tdbbackup -v [-s suffix] *.tdb
+tdbbackup \-v [\-s suffix] *\.tdb
 .PP
+Samba .tdb files are stored in various locations, be sure to run backup all .tdb file on the system. Important files includes:
+.TP 3n
+\(bu
+Samba \.tdb files are stored in various locations, be sure to run backup all \.tdb file on the system\. Important files includes:
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+secrets.tdb
+- usual location is in the /usr/local/samba/private directory, or on some systems in /etc/samba.
+.TP 3n
+\(bu
+secrets\.tdb
+\- usual location is in the /usr/local/samba/private directory, or on some systems in /etc/samba\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+passdb.tdb
+- usual location is in the /usr/local/samba/private directory, or on some systems in /etc/samba.
+.TP 3n
+\(bu
+passdb\.tdb
+\- usual location is in the /usr/local/samba/private directory, or on some systems in /etc/samba\.
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 *.tdb
 located in the /usr/local/samba/var directory or on some systems in the /var/cache or /var/lib/samba directories.
+*\.tdb
+located in the /usr/local/samba/var directory or on some systems in the /var/cache or /var/lib/samba directories\.
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 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.
+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 tdbbackup man page was written by John H Terpstra.
+The tdbbackup man page was written by John H Terpstra\.

branches/samba-3.0/docs/manpages/tdbdump.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "TDBDUMP" 8 "" "" ""
+.\"     Title: tdbdump
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "TDBDUMP" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 tdbdump - tool for printing the contents of a TDB file
 …
 This tool is part of the
 \fBsamba\fR(1)
 suite.
+suite\.
 .PP
 tdbdump
 is a very simple utility that 'dumps' the contents of a TDB (Trivial DataBase) file to standard output in a human-readable format.
+is a very simple utility that \'dumps\' the contents of a TDB (Trivial DataBase) file to standard output in a human\-readable format\.
 .PP
 This tool can be used when debugging problems with TDB files. It is intended for those who are somewhat familiar with Samba internals.
+This tool can be used when debugging problems with TDB files\. It is intended for those who are somewhat familiar with Samba internals\.
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 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.
+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 tdbdump man page was written by Jelmer Vernooij.
+The tdbdump man page was written by Jelmer Vernooij\.

branches/samba-3.0/docs/manpages/tdbtool.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "TDBTOOL" 8 "" "" ""
+.\"     Title: tdbtool
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "TDBTOOL" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 tdbtool - manipulate the contents TDB files
 …
 This tool is part of the
 \fBsamba\fR(1)
 suite.
+suite\.
 .PP
 tdbtool
 a tool for displaying and altering the contents of Samba TDB (Trivial DataBase) files. Each of the commands listed below can be entered interactively or provided on the command line.
+a tool for displaying and altering the contents of Samba TDB (Trivial DataBase) files\. Each of the commands listed below can be entered interactively or provided on the command line\.
 .SH "COMMANDS"
 .PP
 \fBcreate\fR \fITDBFILE\fR
 .RS 3n
+.RS 4
 Create a new database named
 \fITDBFILE\fR.
+\fITDBFILE\fR\.
 .RE
 .PP
 \fBopen\fR \fITDBFILE\fR
 .RS 3n
+.RS 4
 Open an existing database named
 \fITDBFILE\fR.
+\fITDBFILE\fR\.
 .RE
 .PP
 \fBerase\fR
 .RS 3n
 Erase the current database.
+.RS 4
+Erase the current database\.
 .RE
 .PP
 \fBdump\fR
 .RS 3n
 Dump the current database as strings.
+.RS 4
+Dump the current database as strings\.
 .RE
 .PP
 \fBcdump\fR
 .RS 3n
 Dump the current database as connection records.
+.RS 4
+Dump the current database as connection records\.
 .RE
 .PP
 \fBkeys\fR
 .RS 3n
 Dump the current database keys as strings.
+.RS 4
+Dump the current database keys as strings\.
 .RE
 .PP
 \fBhexkeys\fR
 .RS 3n
 Dump the current database keys as hex values.
+.RS 4
+Dump the current database keys as hex values\.
 .RE
 .PP
 \fBinfo\fR
 .RS 3n
 Print summary information about the current database.
+.RS 4
+Print summary information about the current database\.
 .RE
 .PP
 \fBinsert\fR \fIKEY\fR \fIDATA\fR
 .RS 3n
 Insert a record into the current database.
+.RS 4
+Insert a record into the current database\.
 .RE
 .PP
 \fBmove\fR \fIKEY\fR \fITDBFILE\fR
 .RS 3n
+.RS 4
 Move a record from the current database into
 \fITDBFILE\fR.
+\fITDBFILE\fR\.
 .RE
 .PP
 \fBstore\fR \fIKEY\fR \fIDATA\fR
 .RS 3n
 Store (replace) a record in the current database.
+.RS 4
+Store (replace) a record in the current database\.
 .RE
 .PP
 \fBshow\fR \fIKEY\fR
 .RS 3n
 Show a record by key.
+.RS 4
+Show a record by key\.
 .RE
 .PP
 \fBdelete\fR \fIKEY\fR
 .RS 3n
 Delete a record by key.
+.RS 4
+Delete a record by key\.
 .RE
 .PP
 \fBlist\fR
 .RS 3n
 Print the current database hash table and free list.
+.RS 4
+Print the current database hash table and free list\.
 .RE
 .PP
 \fBfree\fR
 .RS 3n
 Print the current database and free list.
+.RS 4
+Print the current database and free list\.
 .RE
 .PP
 \fB!\fR \fICOMMAND\fR
 .RS 3n
 Execute the given system command.
+.RS 4
+Execute the given system command\.
 .RE
 .PP
 \fBfirst\fR
 .RS 3n
 Print the first record in the current database.
+.RS 4
+Print the first record in the current database\.
 .RE
 .PP
 \fBnext\fR
 .RS 3n
 Print the next record in the current database.
+.RS 4
+Print the next record in the current database\.
 .RE
 .PP
 \fBquit\fR
 .RS 3n
+.RS 4
 Exit
 tdbtool.
+tdbtool\.
 .RE
 .SH "CAVEATS"
 .PP
 The contents of the Samba TDB files are private to the implementation and should not be altered with
 tdbtool.
+tdbtool\.
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0.25 of the Samba suite.
+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.
+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\.

branches/samba-3.0/docs/manpages/testparm.1

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "TESTPARM" 1 "" "" ""
+.\"     Title: testparm
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: User Commands
+.\"    Source: Samba 3.0
+.\"
+.TH "TESTPARM" "1" "05/21/2008" "Samba 3\.0" "User Commands"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 testparm - check an smb.conf configuration file for internal correctness
 .SH "SYNOPSIS"
 .HP 1
 testparm [-s] [-h] [-v] [-L <servername>] [-t <encoding>] {config filename} [hostname hostIP]
+testparm [\-s] [\-h] [\-v] [\-L\ <servername>] [\-t\ <encoding>] {config\ filename} [hostname\ hostIP]
 .SH "DESCRIPTION"
 .PP
 This tool is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 testparm
 is a very simple test program to check an
 \fBsmbd\fR(8)
 configuration file for internal correctness. If this program reports no problems, you can use the configuration file with confidence that
+configuration file for internal correctness\. If this program reports no problems, you can use the configuration file with confidence that
 smbd
 will successfully load the configuration file.
+will successfully load the configuration file\.
 .PP
 Note that this is
 \fBNOT\fR
 a guarantee that the services specified in the configuration file will be available or will operate as expected.
+\fINOT\fR
+a guarantee that the services specified in the configuration file will be available or will operate as expected\.
 .PP
 If the optional host name and host IP address are specified on the command line, this test program will run through the service entries reporting whether the specified host has access to each service.
+If the optional host name and host IP address are specified on the command line, this test program will run through the service entries reporting whether the specified host has access to each service\.
 .PP
 If
 testparm
 finds an error in the
 \fI smb.conf\fR
 file it returns an exit code of 1 to the calling program, else it returns an exit code of 0. This allows shell scripts to test the output from
 testparm.
+\fI smb\.conf\fR
+file it returns an exit code of 1 to the calling program, else it returns an exit code of 0\. This allows shell scripts to test the output from
+testparm\.
 .SH "OPTIONS"
 .PP
 -s
 .RS 3n
+\-s
+.RS 4
 Without this option,
 testparm
 will prompt for a carriage return after printing the service names and before dumping the service definitions.
+will prompt for a carriage return after printing the service names and before dumping the service definitions\.
 .RE
 .PP
 -h|--help
 .RS 3n
 Print a summary of command line options.
+\-h|\-\-help
+.RS 4
+Print a summary of command line options\.
 .RE
 .PP
 -V
 .RS 3n
 Prints the program version number.
+\-V
+.RS 4
+Prints the program version number\.
 .RE
 .PP
 -L servername
 .RS 3n
+\-L servername
+.RS 4
 Sets the value of the %L macro to
 \fIservername\fR. This is useful for testing include files specified with the %L macro.
+\fIservername\fR\. This is useful for testing include files specified with the %L macro\.
 .RE
 .PP
 -v
 .RS 3n
+\-v
+.RS 4
 If this option is specified, testparm will also output all options that were not used in
 \fBsmb.conf\fR(5)
 and are thus set to their defaults.
+and are thus set to their defaults\.
 .RE
 .PP
 -t encoding
 .RS 3n
 Output data in specified encoding.
+\-t encoding
+.RS 4
+Output data in specified encoding\.
 .RE
 .PP
 --parameter-name parametername
 .RS 3n
 Dumps the named parameter. If no section-name is set the view is limited by default to the global section. It is also possible to dump a parametrical option. Therfore the option has to be separated by a colon from the parametername.
+\-\-parameter\-name parametername
+.RS 4
+Dumps the named parameter\. If no section\-name is set the view is limited by default to the global section\. It is also possible to dump a parametrical option\. Therfore the option has to be separated by a colon from the parametername\.
 .RE
 .PP
 --section-name sectionname
 .RS 3n
 Dumps the named section.
+\-\-section\-name sectionname
+.RS 4
+Dumps the named section\.
 .RE
 .PP
 configfilename
 .RS 3n
 This is the name of the configuration file to check. If this parameter is not present then the default
+.RS 4
+This is the name of the configuration file to check\. If this parameter is not present then the default
 \fBsmb.conf\fR(5)
 file will be checked.
+file will be checked\.
 .RE
 .PP
 hostname
 .RS 3n
+.RS 4
 If this parameter and the following are specified, then
 testparm
 …
 file to determine if the hostname with this IP address would be allowed access to the
 smbd
 server. If this parameter is supplied, the hostIP parameter must also be supplied.
+server\. If this parameter is supplied, the hostIP parameter must also be supplied\.
 .RE
 .PP
 hostIP
 .RS 3n
 This is the IP address of the host specified in the previous parameter. This address must be supplied if the hostname parameter is supplied.
+.RS 4
+This is the IP address of the host specified in the previous parameter\. This address must be supplied if the hostname parameter is supplied\.
 .RE
 .SH "FILES"
 .PP
 \fBsmb.conf\fR(5)
 .RS 3n
+.RS 4
 This is usually the name of the configuration file used by
 \fBsmbd\fR(8).
+\fBsmbd\fR(8)\.
 .RE
 .SH "DIAGNOSTICS"
 .PP
 The program will issue a message saying whether the configuration file loaded OK or not. This message may be preceded by errors and warnings if the file did not load. If the file was loaded OK, the program then dumps all known service details to stdout.
+The program will issue a message saying whether the configuration file loaded OK or not\. This message may be preceded by errors and warnings if the file did not load\. If the file was loaded OK, the program then dumps all known service details to stdout\.
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 of the Samba suite\.
 .SH "SEE ALSO"
 .PP
 …
 .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.
+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.
+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\.

branches/samba-3.0/docs/manpages/umount.cifs.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "UMOUNT.CIFS" 8 "" "" ""
+.\"     Title: umount.cifs
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "UMOUNT\.CIFS" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 umount.cifs - for normal, non-root users, to unmount their own Common Internet File System (CIFS) mounts
 .SH "SYNOPSIS"
 .HP 1
 umount.cifs {mount-point} [-nVvhfle]
+umount\.cifs {mount\-point} [\-nVvhfle]
 .SH "DESCRIPTION"
 .PP
 This tool is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 umount.cifs unmounts a Linux CIFS filesystem. It can be invoked indirectly by the
+umount\.cifs unmounts a Linux CIFS filesystem\. It can be invoked indirectly by the
 \fBumount\fR(8)
 command when umount.cifs is in /sbin directory, unless you specify the "-i" option to umount. Specifying -i to umount avoids execution of umount helpers such as umount.cifs. The umount.cifs command only works in Linux, and the kernel must support the cifs filesystem. The CIFS protocol is the successor to the SMB protocol and is supported by most Windows servers and many other commercial servers and Network Attached Storage appliances as well as by the popular Open Source server Samba.
+command when umount\.cifs is in /sbin directory, unless you specify the "\-i" option to umount\. Specifying \-i to umount avoids execution of umount helpers such as umount\.cifs\. The umount\.cifs command only works in Linux, and the kernel must support the cifs filesystem\. The CIFS protocol is the successor to the SMB protocol and is supported by most Windows servers and many other commercial servers and Network Attached Storage appliances as well as by the popular Open Source server Samba\.
 .PP
 The umount.cifs utility detaches the local directory
 \fBmount-point\fR
 from the corresponding UNC name (exported network resource) and frees the associated kernel resources. It is possible to set the mode for umount.cifs to setuid root (or equivalently update the /etc/permissions file) to allow non-root users to umount shares to directories for which they have write permission. The umount.cifs utility is typically not needed if unmounts need only be performed by root users, or if user mounts and unmounts can rely on specifying explicit entries in /etc/fstab See
+The umount\.cifs utility detaches the local directory
+\fImount\-point\fR
+from the corresponding UNC name (exported network resource) and frees the associated kernel resources\. It is possible to set the mode for umount\.cifs to setuid root (or equivalently update the /etc/permissions file) to allow non\-root users to umount shares to directories for which they have write permission\. The umount\.cifs utility is typically not needed if unmounts need only be performed by root users, or if user mounts and unmounts can rely on specifying explicit entries in /etc/fstab See
 .PP
 \fBfstab\fR(5)
 .SH "OPTIONS"
 .PP
 --verbose
 .RS 3n
+\-\-verbose
+.RS 4
 print additional debugging information
 .RE
 .PP
 --no-mtab
 .RS 3n
+\-\-no\-mtab
+.RS 4
 Do not update the mtab even if unmount completes successfully (/proc/mounts will still display the correct information)
 .RE
 .SH "NOTES"
 .PP
 This command is normally intended to be installed setuid (since root users can already run unmount). An alternative to using umount.cifs is to add specfic entries for the user mounts that you wish a particular user or users to mount and unmount to /etc/fstab
+This command is normally intended to be installed setuid (since root users can already run unmount)\. An alternative to using umount\.cifs is to add specfic entries for the user mounts that you wish a particular user or users to mount and unmount to /etc/fstab
 .SH "CONFIGURATION"
 .PP
 The primary mechanism for making configuration changes and for reading debug information for the cifs vfs is via the Linux /proc filesystem. In the directory
+The primary mechanism for making configuration changes and for reading debug information for the cifs vfs is via the Linux /proc filesystem\. In the directory
 \fI/proc/fs/cifs\fR
 are various configuration files and pseudo files which can display debug information. For more information see the kernel file
 \fIfs/cifs/README\fR.
+are various configuration files and pseudo files which can display debug information\. For more information see the kernel file
+\fIfs/cifs/README\fR\.
 .SH "BUGS"
 .PP
 At this time umount.cifs does not lock the mount table using the same lock as the umount utility does, so do not attempt to do multiple unmounts from different processes (and in particular unmounts of a cifs mount and another type of filesystem mount at the same time).
+At this time umount\.cifs does not lock the mount table using the same lock as the umount utility does, so do not attempt to do multiple unmounts from different processes (and in particular unmounts of a cifs mount and another type of filesystem mount at the same time)\.
 .PP
 If the same mount point is mounted multiple times by cifs, umount.cifs will remove all of the matching entries from the mount table (although umount.cifs will actually only unmount the last one), rather than only removing the last matching entry in /etc/mtab. The pseudofile /proc/mounts will display correct information though, and the lack of an entry in /etc/mtab does not prevent subsequent unmounts.
+If the same mount point is mounted multiple times by cifs, umount\.cifs will remove all of the matching entries from the mount table (although umount\.cifs will actually only unmount the last one), rather than only removing the last matching entry in /etc/mtab\. The pseudofile /proc/mounts will display correct information though, and the lack of an entry in /etc/mtab does not prevent subsequent unmounts\.
 .PP
 Note that the typical response to a bug report is a suggestion to try the latest version first. So please try doing that first, and always include which versions you use of relevant software when reporting bugs (minimum: umount.cifs (try umount.cifs -V), kernel (see /proc/version) and server type you are trying to contact.
+Note that the typical response to a bug report is a suggestion to try the latest version first\. So please try doing that first, and always include which versions you use of relevant software when reporting bugs (minimum: umount\.cifs (try umount\.cifs \-V), kernel (see /proc/version) and server type you are trying to contact\.
 .SH "VERSION"
 .PP
 This man page is correct for version 1.34 of the cifs vfs filesystem (roughly Linux kernel 2.6.12).
+This man page is correct for version 1\.34 of the cifs vfs filesystem (roughly Linux kernel 2\.6\.12)\.
 .SH "SEE ALSO"
 .PP
 Documentation/filesystems/cifs.txt and fs/cifs/README in the linux kernel source tree may contain additional options and information.
+Documentation/filesystems/cifs\.txt and fs/cifs/README in the linux kernel source tree may contain additional options and information\.
 .PP
 \fBmount.cifs\fR(8)
 …
 Steve French
 .PP
 The syntax was loosely based on the umount utility and the manpage was loosely based on that of mount.cifs.8. The man page was created by Steve French
+The syntax was loosely based on the umount utility and the manpage was loosely based on that of mount\.cifs\.8\. The man page was created by Steve French
 .PP
 The maintainer of the Linux cifs vfs and the userspace tool
 \fBumount.cifs\fR
+\fIumount\.cifs\fR
 is
 Steve French. The
+Steve French\. The
 Linux CIFS Mailing list
+is the preferred place to ask questions regarding these programs.
+is the preferred place to ask questions regarding these programs\.

branches/samba-3.0/docs/manpages/vfs_audit.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "VFS_AUDIT" 8 "" "" ""
+.\"     Title: vfs_audit
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "VFS_AUDIT" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 vfs_audit - record selected Samba VFS operations in the system log
 …
 This VFS module is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 The
 vfs_audit
 VFS module records selected client operations to the system log using
 \fBsyslog\fR(3).
+\fBsyslog\fR(3)\.
 .PP
 The following Samba VFS operations are recorded:
 .IP "" 3n
+.IP "" 4
 connect
 .IP "" 3n
+.IP "" 4
 disconnect
 .IP "" 3n
+.IP "" 4
 opendir
 .IP "" 3n
+.IP "" 4
 mkdir
 .IP "" 3n
+.IP "" 4
 rmdir
 .IP "" 3n
+.IP "" 4
 open
 .IP "" 3n
+.IP "" 4
 close
 .IP "" 3n
+.IP "" 4
 rename
 .IP "" 3n
+.IP "" 4
 unlink
 .IP "" 3n
+.IP "" 4
 chmod
 .IP "" 3n
+.IP "" 4
 fchmod
 .IP "" 3n
+.IP "" 4
 chmod_acl
 .IP "" 3n
+.IP "" 4
 fchmod_acl
 .PP
 This module is stackable.
+This module is stackable\.
 .SH "OPTIONS"
 .PP
 audit:facility = FACILITY
 .RS 3n
+.RS 4
 Log messages to the named
 \fBsyslog\fR(3)
 facility.
+facility\.
 .RE
 .PP
 audit:priority = PRIORITY
 .RS 3n
+.RS 4
 Log messages with the named
 \fBsyslog\fR(3)
 priority.
+priority\.
 .RE
 .SH "EXAMPLES"
 .PP
 Log operations on all shares using the LOCAL1 facility and NOTICE priority:
+.sp
+.RS 4
 .nf
         \fI[global]\fR
+        vfs objects = audit
+        audit:facility = LOCAL1
+        audit:priority = NOTICE
+        \fIvfs objects = audit\fR
+        \fIaudit:facility = LOCAL1\fR
+        \fIaudit:priority = NOTICE\fR
 .fi
+.RE
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0.25 of the Samba suite.
+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.
+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\.

branches/samba-3.0/docs/manpages/vfs_cacheprime.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "VFS_CACHEPRIME" 8 "" "" ""
+.\"     Title: vfs_cacheprime
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "VFS_CACHEPRIME" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 vfs_cacheprime - prime the kernel file data cache
 …
 This VFS module is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 The
 vfs_cacheprime
 VFS module reads chunks of file data near the range requested by clients in order to make sure the data is present in the kernel file data cache at the time when it is actually requested by clients.
+VFS module reads chunks of file data near the range requested by clients in order to make sure the data is present in the kernel file data cache at the time when it is actually requested by clients\.
 .PP
 The size of the disk read operations performed by
 vfs_cacheprime
 is determined by the cacheprime:rsize option. All disk read operations are aligned on boundaries that are a multiple of this size. Each range of the file data is primed at most once during the time the client has the file open.
+is determined by the cacheprime:rsize option\. All disk read operations are aligned on boundaries that are a multiple of this size\. Each range of the file data is primed at most once during the time the client has the file open\.
 .PP
 This module is stackable.
+This module is stackable\.
 .SH "OPTIONS"
 .PP
 cacheprime:rsize = BYTES
 .RS 3n
 The number of bytes with which to prime the kernel data cache.
+.RS 4
+The number of bytes with which to prime the kernel data cache\.
 .sp
 The following suffixes may be applied to BYTES:
+.RS 3n
+.TP 3n
+\(bu
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+K
+- BYTES is a number of kilobytes
+.TP 3n
+\(bu
+\- BYTES is a number of kilobytes
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+M
+- BYTES is a number of megabytes
+.TP 3n
+\(bu
+\- BYTES is a number of megabytes
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+G
+- BYTES is a number of gigabytes
+\- BYTES is a number of gigabytes
+.sp
 .RE
 .RE
 …
 .PP
 For a hypothetical disk array, it is necessary to ensure that all read operations are of size 1 megabyte (1048576 bytes), and aligned on 1 megabyte boundaries:
+.sp
+.RS 4
 .nf
         \fI[hypothetical]\fR
+        vfs objects = cacheprime
+        cacheprime:rsize = 1M
+        \fIvfs objects = cacheprime\fR
+        \fIcacheprime:rsize = 1M\fR
 .fi
+.RE
 .SH "CAVEATS"
 .PP
 cacheprime
 is not a a substitute for a general-purpose readahead mechanism. It is intended for use only in very specific environments where disk operations must be aligned and sized to known values (as much as that is possible).
+is not a a substitute for a general\-purpose readahead mechanism\. It is intended for use only in very specific environments where disk operations must be aligned and sized to known values (as much as that is possible)\.
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0.25 of the Samba suite.
+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.
+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\.

branches/samba-3.0/docs/manpages/vfs_cap.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "VFS_CAP" 8 "" "" ""
+.\"     Title: vfs_cap
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "VFS_CAP" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 vfs_cap - CAP encode filenames
 …
 This VFS module is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 CAP (Columbia Appletalk Protocol) encoding is a technique for representing non-ASCII filenames in ASCII. The
+CAP (Columbia Appletalk Protocol) encoding is a technique for representing non\-ASCII filenames in ASCII\. The
 vfs_cap
 VFS module translates filenames to and from CAP format, allowing users to name files in their native encoding.
+VFS module translates filenames to and from CAP format, allowing users to name files in their native encoding\.
 .PP
 CAP encoding is most commonly used in Japanese language environments.
+CAP encoding is most commonly used in Japanese language environments\.
 .PP
 This module is stackable.
+This module is stackable\.
 .SH "EXAMPLES"
 .PP
 On a system using GNU libiconv, use CAP encoding to support users in the Shift_JIS locale:
+.sp
+.RS 4
 .nf
         \fI[global]\fR
+        dos charset = CP932
+        dos charset = CP932
+        vfs objects = cap
+        \fIdos charset = CP932\fR
+        \fIdos charset = CP932\fR
+        \fIvfs objects = cap\fR
 .fi
+.RE
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0.25 of the Samba suite.
+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.
+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\.

branches/samba-3.0/docs/manpages/vfs_catia.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "VFS_CATIA" 8 "" "" ""
+.\"     Title: vfs_catia
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "VFS_CATIA" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 vfs_catia - translate illegal characters in Catia filenames
 …
 This VFS module is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 The Catia CAD package commonly creates filenames that use characters that are illegal in CIFS filenames. The
+The Catia CAD package commonly creates filenames that use characters that are illegal in CIFS filenames\. The
 vfs_catia
 VFS module implements a fixed character mapping so that these files can be shared with CIFS clients.
+VFS module implements a fixed character mapping so that these files can be shared with CIFS clients\.
 .PP
 This module is stackable.
+This module is stackable\.
 .SH "EXAMPLES"
 .PP
 Map Catia filenames on the [CAD] share:
+.sp
+.RS 4
 .nf
         \fI[CAD]\fR
+        path = /data/cad
+        vfs objects = catia
+        \fIpath = /data/cad\fR
+        \fIvfs objects = catia\fR
 .fi
+.RE
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0.25 of the Samba suite.
+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.
+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\.

branches/samba-3.0/docs/manpages/vfs_commit.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "VFS_COMMIT" 8 "" "" ""
+.\"     Title: vfs_commit
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "VFS_COMMIT" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 vfs_commit - flush dirty data at specified intervals
 …
 This VFS module is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 The
 vfs_commit
 VFS module keeps track of the amount of data written to a file and synchronizes it to disk when a specified amount accumulates.
+VFS module keeps track of the amount of data written to a file and synchronizes it to disk when a specified amount accumulates\.
 .PP
 vfs_commit
 is useful in two circumstances. First, if you have very precious data, the impact of unexpected power loss can be minimized by a small commit:dthresh value. Secondly, write performance can be improved on some systems by flushing file data early and at regular intervals.
+is useful in two circumstances\. First, if you have very precious data, the impact of unexpected power loss can be minimized by a small commit:dthresh value\. Secondly, write performance can be improved on some systems by flushing file data early and at regular intervals\.
 .PP
 This module is stackable.
+This module is stackable\.
 .SH "OPTIONS"
 .PP
 commit:dthresh = BYTES
 .RS 3n
 Synchronize file data each time the specified number of bytes has been written.
+.RS 4
+Synchronize file data each time the specified number of bytes has been written\.
 .sp
 The following suffixes may be applied to BYTES:
+.RS 3n
+.TP 3n
+\(bu
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+K
+- BYTES is a number of kilobytes
+.TP 3n
+\(bu
+\- BYTES is a number of kilobytes
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+M
+- BYTES is a number of megabytes
+.TP 3n
+\(bu
+\- BYTES is a number of megabytes
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+G
+- BYTES is a number of gigabytes
+\- BYTES is a number of gigabytes
+.sp
 .RE
 .RE
 …
 .PP
 Synchronize the file data on the [precious] share after every 512 kilobytes (524288 bytes) of data is written:
+.sp
+.RS 4
 .nf
         \fI[precious]\fR
+        path = /data/precious
+        vfs objects = commit
+        commit:dthresh = 512K
+        \fIpath = /data/precious\fR
+        \fIvfs objects = commit\fR
+        \fIcommit:dthresh = 512K\fR
 .fi
+.RE
 .SH "CAVEATS"
 .PP
 On some systems, the data synchronization performed by
 commit
 may reduce performance.
+may reduce performance\.
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0.25 of the Samba suite.
+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.
+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\.

branches/samba-3.0/docs/manpages/vfs_default_quota.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "VFS_DEFAULT_QUOTA" 8 "" "" ""
+.\"     Title: vfs_default_quota
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "VFS_DEFAULT_QUOTA" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 vfs_default_quota - store default quota records for Windows clients
 …
 This VFS module is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 Many common quota implementations only store quotas for users and groups, but do not store a default quota. The
+Many common quota implementations only store quotas for users and groups, but do not store a default quota\. The
 vfs_default_quota
 module allows Samba to store default quota values which can be examined using the Windows Explorer interface.
+module allows Samba to store default quota values which can be examined using the Windows Explorer interface\.
 .PP
 By default, Samba returns NO_LIMIT the default quota and refuses to update them.
+By default, Samba returns NO_LIMIT the default quota and refuses to update them\.
 vfs_default_quota
 maps the default quota to the quota record of a user. By default the root user is taken because quota limits for root are typically not enforced.
+maps the default quota to the quota record of a user\. By default the root user is taken because quota limits for root are typically not enforced\.
 .PP
 This module is stackable.
+This module is stackable\.
 .SH "OPTIONS"
 .PP
 default_quota:uid = UID
 .RS 3n
 UID specifies the user ID of the quota record where the default user quota values are stored.
+.RS 4
+UID specifies the user ID of the quota record where the default user quota values are stored\.
 .RE
 .PP
 default_quota:gid = GID
 .RS 3n
 GID specifies the group ID of the quota record where the default group quota values are stored.
+.RS 4
+GID specifies the group ID of the quota record where the default group quota values are stored\.
 .RE
 .PP
 default_quota:uid nolimit = BOOL
 .RS 3n
 If this parameter is True, then the user whose quota record is storing the default user quota will be reported as having a quota of NO_LIMIT. Otherwise, the stored values will be reported.
+.RS 4
+If this parameter is True, then the user whose quota record is storing the default user quota will be reported as having a quota of NO_LIMIT\. Otherwise, the stored values will be reported\.
 .RE
 .PP
 default_quota:gid nolimit = BOOL
 .RS 3n
 If this parameter is True, then the group whose quota record is storing the default group quota will be reported as having a quota of NO_LIMIT. Otherwise, the stored values will be reported.
+.RS 4
+If this parameter is True, then the group whose quota record is storing the default group quota will be reported as having a quota of NO_LIMIT\. Otherwise, the stored values will be reported\.
 .RE
 .SH "EXAMPLES"
 .PP
 Store the default quota record in the quota record for the user with ID 65535 and report that user as having no quota limits:
+.sp
+.RS 4
 .nf
         \fI[global]\fR
+        vfs objects = default_quota
+        default_quota:uid = 65535
+        default_quota:uid nolimit = yes
+        \fIvfs objects = default_quota\fR
+        \fIdefault_quota:uid = 65535\fR
+        \fIdefault_quota:uid nolimit = yes\fR
 .fi
+.RE
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0.25 of the Samba suite.
+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.
+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\.

branches/samba-3.0/docs/manpages/vfs_extd_audit.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "VFS_EXTD_AUDIT" 8 "" "" ""
+.\"     Title: vfs_extd_audit
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "VFS_EXTD_AUDIT" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 vfs_extd_audit - record selected Samba VFS operations
 …
 This VFS module is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 The
 …
 \fBsmbd\fR(8)
 log and system log (using
 \fBsyslog\fR(3)).
+\fBsyslog\fR(3))\.
 .PP
 Other than logging to the
 …
 vfs_extd_audit
 is identical to
 \fBvfs_audit\fR(8).
+\fBvfs_audit\fR(8)\.
 .PP
 This module is stackable.
+This module is stackable\.
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0.25 of the Samba suite.
+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.
+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\.

branches/samba-3.0/docs/manpages/vfs_fake_perms.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "VFS_FAKE_PERMS" 8 "" "" ""
+.\"     Title: vfs_fake_perms
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "VFS_FAKE_PERMS" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 vfs_fake_perms - enable read only Roaming Profiles
 …
 This VFS module is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 The
 vfs_fake_perms
 VFS module was created to allow Roaming Profile files and directories to be set (on the Samba server under UNIX) as read only. This module will, if installed on the Profiles share, report to the client that the Profile files and directories are writeable. This satisfies the client even though the files will never be overwritten as the client logs out or shuts down.
+VFS module was created to allow Roaming Profile files and directories to be set (on the Samba server under UNIX) as read only\. This module will, if installed on the Profiles share, report to the client that the Profile files and directories are writeable\. This satisfies the client even though the files will never be overwritten as the client logs out or shuts down\.
 .PP
 This module is stackable.
+This module is stackable\.
 .SH "EXAMPLES"
+.sp
+.RS 4
 .nf
         \fI[Profiles]\fR
+        path = /profiles
+        vfs objects = fake_perms
+        \fIpath = /profiles\fR
+        \fIvfs objects = fake_perms\fR
 .fi
+.RE
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0.25 of the Samba suite.
+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.
+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\.

branches/samba-3.0/docs/manpages/vfs_full_audit.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "VFS_FULL_AUDIT" 8 "" "" ""
+.\"     Title: vfs_full_audit
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "VFS_FULL_AUDIT" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 vfs_full_audit - record Samba VFS operations in the system log
 …
 This VFS module is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 The
 vfs_full_audit
 VFS module records selected client operations to the system log using
 \fBsyslog\fR(3).
+\fBsyslog\fR(3)\.
 .PP
 vfs_full_audit
 is able to record the complete set of Samba VFS operations:
 .IP "" 3n
+.IP "" 4
 aio_cancel
 .IP "" 3n
+.IP "" 4
 aio_error
 .IP "" 3n
+.IP "" 4
 aio_fsync
 .IP "" 3n
+.IP "" 4
 aio_read
 .IP "" 3n
+.IP "" 4
 aio_return
 .IP "" 3n
+.IP "" 4
 aio_suspend
 .IP "" 3n
+.IP "" 4
 aio_write
 .IP "" 3n
+.IP "" 4
 chdir
 .IP "" 3n
+.IP "" 4
 chflags
 .IP "" 3n
+.IP "" 4
 chmod
 .IP "" 3n
+.IP "" 4
 chmod_acl
 .IP "" 3n
+.IP "" 4
 chown
 .IP "" 3n
+.IP "" 4
 close
 .IP "" 3n
+.IP "" 4
 closedir
 .IP "" 3n
+.IP "" 4
 connect
 .IP "" 3n
+.IP "" 4
 disconnect
 .IP "" 3n
+.IP "" 4
 disk_free
 .IP "" 3n
+.IP "" 4
 fchmod
 .IP "" 3n
+.IP "" 4
 fchmod_acl
 .IP "" 3n
+.IP "" 4
 fchown
 .IP "" 3n
+.IP "" 4
 fget_nt_acl
 .IP "" 3n
+.IP "" 4
 fgetxattr
 .IP "" 3n
+.IP "" 4
 flistxattr
 .IP "" 3n
+.IP "" 4
 fremovexattr
 .IP "" 3n
+.IP "" 4
 fset_nt_acl
 .IP "" 3n
+.IP "" 4
 fsetxattr
 .IP "" 3n
+.IP "" 4
 fstat
 .IP "" 3n
+.IP "" 4
 fsync
 .IP "" 3n
+.IP "" 4
 ftruncate
 .IP "" 3n
+.IP "" 4
 get_nt_acl
 .IP "" 3n
+.IP "" 4
 get_quota
 .IP "" 3n
+.IP "" 4
 get_shadow_copy_data
 .IP "" 3n
+.IP "" 4
 getlock
 .IP "" 3n
+.IP "" 4
 getwd
 .IP "" 3n
+.IP "" 4
 getxattr
 .IP "" 3n
+.IP "" 4
 kernel_flock
 .IP "" 3n
+.IP "" 4
 lgetxattr
 .IP "" 3n
+.IP "" 4
 link
 .IP "" 3n
+.IP "" 4
 linux_setlease
 .IP "" 3n
+.IP "" 4
 listxattr
 .IP "" 3n
+.IP "" 4
 llistxattr
 .IP "" 3n
+.IP "" 4
 lock
 .IP "" 3n
+.IP "" 4
 lremovexattr
 .IP "" 3n
+.IP "" 4
 lseek
 .IP "" 3n
+.IP "" 4
 lsetxattr
 .IP "" 3n
+.IP "" 4
 lstat
 .IP "" 3n
+.IP "" 4
 mkdir
 .IP "" 3n
+.IP "" 4
 mknod
 .IP "" 3n
+.IP "" 4
 open
 .IP "" 3n
+.IP "" 4
 opendir
 .IP "" 3n
+.IP "" 4
 pread
 .IP "" 3n
+.IP "" 4
 pwrite
 .IP "" 3n
+.IP "" 4
 read
 .IP "" 3n
+.IP "" 4
 readdir
 .IP "" 3n
+.IP "" 4
 readlink
 .IP "" 3n
+.IP "" 4
 realpath
 .IP "" 3n
+.IP "" 4
 removexattr
 .IP "" 3n
+.IP "" 4
 rename
 .IP "" 3n
+.IP "" 4
 rewinddir
 .IP "" 3n
+.IP "" 4
 rmdir
 .IP "" 3n
+.IP "" 4
 seekdir
 .IP "" 3n
+.IP "" 4
 sendfile
 .IP "" 3n
+.IP "" 4
 set_nt_acl
 .IP "" 3n
+.IP "" 4
 set_quota
 .IP "" 3n
+.IP "" 4
 setxattr
 .IP "" 3n
+.IP "" 4
 stat
 .IP "" 3n
+.IP "" 4
 statvfs
 .IP "" 3n
+.IP "" 4
 symlink
 .IP "" 3n
+.IP "" 4
 sys_acl_add_perm
 .IP "" 3n
+.IP "" 4
 sys_acl_clear_perms
 .IP "" 3n
+.IP "" 4
 sys_acl_create_entry
 .IP "" 3n
+.IP "" 4
 sys_acl_delete_def_file
 .IP "" 3n
+.IP "" 4
 sys_acl_free_acl
 .IP "" 3n
+.IP "" 4
 sys_acl_free_qualifier
 .IP "" 3n
+.IP "" 4
 sys_acl_free_text
 .IP "" 3n
+.IP "" 4
 sys_acl_get_entry
 .IP "" 3n
+.IP "" 4
 sys_acl_get_fd
 .IP "" 3n
+.IP "" 4
 sys_acl_get_file
 .IP "" 3n
+.IP "" 4
 sys_acl_get_perm
 .IP "" 3n
+.IP "" 4
 sys_acl_get_permset
 .IP "" 3n
+.IP "" 4
 sys_acl_get_qualifier
 .IP "" 3n
+.IP "" 4
 sys_acl_get_tag_type
 .IP "" 3n
+.IP "" 4
 sys_acl_init
 .IP "" 3n
+.IP "" 4
 sys_acl_set_fd
 .IP "" 3n
+.IP "" 4
 sys_acl_set_file
 .IP "" 3n
+.IP "" 4
 sys_acl_set_permset
 .IP "" 3n
+.IP "" 4
 sys_acl_set_qualifier
 .IP "" 3n
+.IP "" 4
 sys_acl_set_tag_type
 .IP "" 3n
+.IP "" 4
 sys_acl_to_text
 .IP "" 3n
+.IP "" 4
 sys_acl_valid
 .IP "" 3n
+.IP "" 4
 telldir
 .IP "" 3n
+.IP "" 4
 unlink
 .IP "" 3n
+.IP "" 4
 utime
 .IP "" 3n
+.IP "" 4
 write
 .PP
 In addition to these operations,
 vfs_full_audit
 recognizes the special operation names "all" and "none ", which refer to all the VFS operations and none of the VFS operations respectively.
+recognizes the special operation names "all" and "none ", which refer to all the VFS operations and none of the VFS operations respectively\.
 .PP
 vfs_full_audit
+records operations in fixed format consisting of fields separated by '|' characters. The format is:
+records operations in fixed format consisting of fields separated by \'|\' characters\. The format is:
+.sp
+.RS 4
 .nf
                 smbd_audit: PREFIX|OPERATION|RESULT|FILE
 .fi
+.RE
 .PP
 The record fields are:
+.TP 3n
+\(bu
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 PREFIX
+- the result of the full_audit:prefix string after variable substitutions
+.TP 3n
+\(bu
+\- the result of the full_audit:prefix string after variable substitutions
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 OPERATION
+- the name of the VFS operation
+.TP 3n
+\(bu
+\- the name of the VFS operation
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 RESULT
+- whether the operation succeeded or failed
+.TP 3n
+\(bu
+\- whether the operation succeeded or failed
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 FILE
+- the name of the file or directory the operation was performed on
+.PP
+This module is stackable.
+\- the name of the file or directory the operation was performed on
+.sp
+.RE
+.PP
+This module is stackable\.
 .SH "OPTIONS"
 .PP
 vfs_full_audit:prefix = STRING
 .RS 3n
 Prepend audit messages with STRING. STRING is processed for standard substitution variables listed in
 \fBsmb.conf\fR(5). The default prefix is "%u|%I".
+.RS 4
+Prepend audit messages with STRING\. STRING is processed for standard substitution variables listed in
+\fBsmb.conf\fR(5)\. The default prefix is "%u|%I"\.
 .RE
 .PP
 vfs_full_audit:success = LIST
 .RS 3n
 LIST is a list of VFS operations that should be recorded if they succeed. Operations are specified using the names listed above.
+.RS 4
+LIST is a list of VFS operations that should be recorded if they succeed\. Operations are specified using the names listed above\.
 .RE
 .PP
 vfs_full_audit:failure = LIST
 .RS 3n
 LIST is a list of VFS operations that should be recorded if they failed. Operations are specified using the names listed above.
+.RS 4
+LIST is a list of VFS operations that should be recorded if they failed\. Operations are specified using the names listed above\.
 .RE
 .PP
 full_audit:facility = FACILITY
 .RS 3n
+.RS 4
 Log messages to the named
 \fBsyslog\fR(3)
 facility.
+facility\.
 .RE
 .PP
 full_audit:priority = PRIORITY
 .RS 3n
+.RS 4
 Log messages with the named
 \fBsyslog\fR(3)
 priority.
+priority\.
 .RE
 .SH "EXAMPLES"
 .PP
 Log file and directory open operations on the [records] share using the LOCAL7 facility and ALERT priority, including the username and IP address:
+.sp
+.RS 4
 .nf
         \fI[records]\fR
+        path = /data/records
+        vfs objects = full_audit
+        full_audit:prefix = %u|%I
+        full_audit:success = open opendir
+        full_audit:failure = all
+        full_audit:facility = LOCAL7
+        full_audit:priority = ALERT
+        \fIpath = /data/records\fR
+        \fIvfs objects = full_audit\fR
+        \fIfull_audit:prefix = %u|%I\fR
+        \fIfull_audit:success = open opendir\fR
+        \fIfull_audit:failure = all\fR
+        \fIfull_audit:facility = LOCAL7\fR
+        \fIfull_audit:priority = ALERT\fR
 .fi
+.RE
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0.25 of the Samba suite.
+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.
+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\.

branches/samba-3.0/docs/manpages/vfs_netatalk.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "VFS_NETATALK" 8 "" "" ""
+.\"     Title: vfs_netatalk
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "VFS_NETATALK" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 vfs_netatalk - hide .AppleDouble files from CIFS clients
 …
 This VFS module is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 The
 vfs_netatalk
 VFS module dynamically hides .AppleDouble files, preventing spurious errors on some CIFS clients. .AppleDouble files may be created by historic implementations of AFP (Apple Filing Protocol) on servers.
+VFS module dynamically hides \.AppleDouble files, preventing spurious errors on some CIFS clients\. \.AppleDouble files may be created by historic implementations of AFP (Apple Filing Protocol) on servers\.
 .PP
 This module is stackable.
+This module is stackable\.
 .SH "EXAMPLES"
 .PP
+Hide .AppleDouble files on the [data] share:
+Hide \.AppleDouble files on the [data] share:
+.sp
+.RS 4
 .nf
         \fI[data]\fR
+        vfs objects = netatalk
+        \fIvfs objects = netatalk\fR
 .fi
+.RE
 .SH "CAVEATS"
 .PP
 This module is largely historic and unlikely to be of use in modern networks since current Apple systems are able to mount CIFS shares natively.
+This module is largely historic and unlikely to be of use in modern networks since current Apple systems are able to mount CIFS shares natively\.
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0.25 of the Samba suite.
+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.
+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\.

branches/samba-3.0/docs/manpages/vfs_prealloc.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "VFS_PREALLOC" 8 "" "" ""
+.\"     Title: vfs_prealloc
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "VFS_PREALLOC" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 vfs_prealloc - preallocate matching files to a predetermined size
 …
 This VFS module is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 The
 vfs_prealloc
 VFS module preallocates files to a specified size each time a new file is created. This is useful in environments where files are of a predetermined size will be written to a disk subsystem where extending file allocations is expensive.
+VFS module preallocates files to a specified size each time a new file is created\. This is useful in environments where files are of a predetermined size will be written to a disk subsystem where extending file allocations is expensive\.
 .PP
 This module is stackable.
+This module is stackable\.
 .SH "OPTIONS"
 .PP
 prealloc:EXT = BYTES
 .RS 3n
 Preallocate all files with the extension EXT to the size specified by BYTES.
+.RS 4
+Preallocate all files with the extension EXT to the size specified by BYTES\.
 .sp
 The following suffixes may be applied to BYTES:
+.RS 3n
+.TP 3n
+\(bu
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+K
+- BYTES is a number of kilobytes
+.TP 3n
+\(bu
+\- BYTES is a number of kilobytes
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+M
+- BYTES is a number of megabytes
+.TP 3n
+\(bu
+\- BYTES is a number of megabytes
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+G
+- BYTES is a number of gigabytes
+\- BYTES is a number of gigabytes
+.sp
 .RE
 .RE
 …
 .PP
 A process writes TIFF files to a Samba share, and the is known these files will almost always be around 4 megabytes (4194304 bytes):
+.sp
+.RS 4
 .nf
         \fI[frames]\fR
+        path = /data/frames
+        vfs objects = prealloc
+        prealloc:tiff = 4M
+        \fIpath = /data/frames\fR
+        \fIvfs objects = prealloc\fR
+        \fIprealloc:tiff = 4M\fR
 .fi
+.RE
 .SH "CAVEATS"
 .PP
 vfs_prealloc
 is not supported on all platforms and filesystems. Currently only XFS filesystems on Linux and IRIX are supported.
+is not supported on all platforms and filesystems\. Currently only XFS filesystems on Linux and IRIX are supported\.
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0.25 of the Samba suite.
+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.
+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\.

branches/samba-3.0/docs/manpages/vfs_readonly.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "VFS_READONLY" 8 "" "" ""
+.\"     Title: vfs_readonly
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "VFS_READONLY" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 vfs_readonly - make a Samba share read only for a specified time period
 …
 This VFS module is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 The
 vfs_readonly
 VFS module marks a share as read only for all clients connecting within the configured time period. Clients connecting during this time will be denied write access to all files in the share, irrespective of ther actual access privileges.
+VFS module marks a share as read only for all clients connecting within the configured time period\. Clients connecting during this time will be denied write access to all files in the share, irrespective of ther actual access privileges\.
 .PP
 This module is stackable.
+This module is stackable\.
 .SH "OPTIONS"
 .PP
 readonly:period = BEGIN, END
 .RS 3n
 Only mark the share as read only if the client connection was made between the times marked by the BEGIN and END date specifiers. The syntax of these date specifiers is the same as that accepted by the -d option of GNU
 \fBdate\fR(1).
+.RS 4
+Only mark the share as read only if the client connection was made between the times marked by the BEGIN and END date specifiers\. The syntax of these date specifiers is the same as that accepted by the \-d option of GNU
+\fBdate\fR(1)\.
 .RE
 .SH "EXAMPLES"
 .PP
 Mark all shares read only:
+.sp
+.RS 4
 .nf
         \fI[global]\fR
+        vfs objects = readonly
+        \fIvfs objects = readonly\fR
 .fi
+.RE
 .PP
 Mark the [backup] share as read only during business hours:
+.sp
+.RS 4
 .nf
         \fI[backup]\fR
+        path = /readonly
+        vfs objects = readonly
+        readonly:period = readonly:period = "today 9:00","today 17:00"
+        \fIpath = /readonly\fR
+        \fIvfs objects = readonly\fR
+        \fIreadonly:period = readonly:period = "today 9:00","today 17:00"\fR
 .fi
+.RE
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0.25 of the Samba suite.
+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.
+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\.

branches/samba-3.0/docs/manpages/vfs_recycle.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "VFS_RECYCLE" 8 "" "" ""
+.\"     Title: vfs_recycle
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "VFS_RECYCLE" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 vfs_recycle - Samba VFS recycle bin
 …
 This VFS module is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 The
 vfs_recycle
 intercepts file deletion requests and moves the affected files to a temporary repository rather than deleting them immediately. This gives the same effect as the Recycle Bin on Windows computers.
+intercepts file deletion requests and moves the affected files to a temporary repository rather than deleting them immediately\. This gives the same effect as the Recycle Bin on Windows computers\.
 .PP
 The Recycle Bin will not appear in Windows Explorer views of the network file system (share) nor on any mapped drive. Instead, a directory called .recycle will be automatically created when the first file is deleted and recycle:repository is not configured. If recycle:repository is configured, the name of the created directory depends on recycle:repository. Users can recover files from the recycle bin. If the recycle:keeptree option has been specified, deleted files will be found in a path identical with that from which the file was deleted.
+The Recycle Bin will not appear in Windows Explorer views of the network file system (share) nor on any mapped drive\. Instead, a directory called \.recycle will be automatically created when the first file is deleted and recycle:repository is not configured\. If recycle:repository is configured, the name of the created directory depends on recycle:repository\. Users can recover files from the recycle bin\. If the recycle:keeptree option has been specified, deleted files will be found in a path identical with that from which the file was deleted\.
 .PP
 This module is stackable.
+This module is stackable\.
 .SH "OPTIONS"
 .PP
 recycle:repository = PATH
 .RS 3n
 Path of the directory where deleted files should be moved.
+.RS 4
+Path of the directory where deleted files should be moved\.
 .sp
 If this option is not set, the default path .recycle is used.
+If this option is not set, the default path \.recycle is used\.
 .RE
 .PP
 recycle:directory_mode = MODE
 .RS 3n
 Set MODE to the octal mode the recycle repository should be created with. The recycle repository will be created when first file is deleted. If recycle:subdir_mode is not set, MODE also applies to subdirectories.
+.RS 4
+Set MODE to the octal mode the recycle repository should be created with\. The recycle repository will be created when first file is deleted\. If recycle:subdir_mode is not set, MODE also applies to subdirectories\.
 .sp
 If this option is not set, the default mode 0700 is used.
+If this option is not set, the default mode 0700 is used\.
 .RE
 .PP
 recycle:subdir_mode = MODE
 .RS 3n
 Set MODE to the octal mode with which sub directories of the recycle repository should be created.
+.RS 4
+Set MODE to the octal mode with which sub directories of the recycle repository should be created\.
 .sp
 If this option is not set, subdirectories will be created with the mode from recycle:directory_mode.
+If this option is not set, subdirectories will be created with the mode from recycle:directory_mode\.
 .RE
 .PP
 recycle:keeptree = BOOL
 .RS 3n
 Specifies whether the directory structure should be preserved or whether the files in a directory that is being deleted should be kept separately in the repository.
+.RS 4
+Specifies whether the directory structure should be preserved or whether the files in a directory that is being deleted should be kept separately in the repository\.
 .RE
 .PP
 recycle:versions = BOOL
 .RS 3n
 If this option is True, two files with the same name that are deleted will both be kept in the repository. Newer deleted versions of a file will be called "Copy #x of filename".
+.RS 4
+If this option is True, two files with the same name that are deleted will both be kept in the repository\. Newer deleted versions of a file will be called "Copy #x of filename"\.
 .RE
 .PP
 recycle:touch = BOOL
 .RS 3n
 Specifies whether a file's access date should be updated when the file is moved to the repository.
+.RS 4
+Specifies whether a file\'s access date should be updated when the file is moved to the repository\.
 .RE
 .PP
 recycle:touch_mtime = BOOL
 .RS 3n
 Specifies whether a file's last modified date should be updated when the file is moved to the repository.
+.RS 4
+Specifies whether a file\'s last modified date should be updated when the file is moved to the repository\.
 .RE
 .PP
 recycle:minsize = BYTES
 .RS 3n
 Files that are smaller than the number of bytes specified by this parameter will not be put into the repository.
+.RS 4
+Files that are smaller than the number of bytes specified by this parameter will not be put into the repository\.
 .RE
 .PP
 recycle:maxsize = BYTES
 .RS 3n
 Files that are larger than the number of bytes specified by this parameter will not be put into the repository.
+.RS 4
+Files that are larger than the number of bytes specified by this parameter will not be put into the repository\.
 .RE
 .PP
 recycle:exclude = LIST
 .RS 3n
 List of files that should not be put into the repository when deleted, but deleted in the normal way. Wildcards such as * and ? are supported.
+.RS 4
+List of files that should not be put into the repository when deleted, but deleted in the normal way\. Wildcards such as * and ? are supported\.
 .RE
 .PP
 recycle:exclude_dir = LIST
 .RS 3n
 List of directories whose files should not be put into the repository when deleted, but deleted in the normal way. Wildcards such as * and ? are supported.
+.RS 4
+List of directories whose files should not be put into the repository when deleted, but deleted in the normal way\. Wildcards such as * and ? are supported\.
 .RE
 .PP
 recycle:noversions = LIST
 .RS 3n
 Specifies a list of paths (wildcards such as * and ? are supported) for which no versioning should be used. Only useful when recycle:versions is enabled.
+.RS 4
+Specifies a list of paths (wildcards such as * and ? are supported) for which no versioning should be used\. Only useful when recycle:versions is enabled\.
 .RE
 .SH "EXAMPLES"
 .PP
 Log operations on all shares using the LOCAL1 facility and NOTICE priority:
+.sp
+.RS 4
 .nf
         \fI[global]\fR
+        vfs objects = recycle
+        recycle:facility = LOCAL1
+        recycle:priority = NOTICE
+        \fIvfs objects = recycle\fR
+        \fIrecycle:facility = LOCAL1\fR
+        \fIrecycle:priority = NOTICE\fR
 .fi
+.RE
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0.25 of the Samba suite.
+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.
+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\.

branches/samba-3.0/docs/manpages/vfs_shadow_copy.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "VFS_SHADOW_COPY" 8 "" "" ""
+.\"     Title: vfs_shadow_copy
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "VFS_SHADOW_COPY" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 vfs_shadow_copy - Make a Samba share read only for a specified time period
 …
 This VFS module is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 The
 vfs_shadow_copy
 VFS module functionality that is similar to Microsoft Shadow Copy services. When setup properly, this module allows Microsoft Shadow Copy clients to browse "shadow copies" on Samba shares.
+VFS module functionality that is similar to Microsoft Shadow Copy services\. When setup properly, this module allows Microsoft Shadow Copy clients to browse "shadow copies" on Samba shares\.
 .PP
 This module is stackable.
+This module is stackable\.
 .SH "CONFIGURATION"
 .PP
 vfs_shadow_copy
 relies on a filesystem snapshot implementation. Many common filesystems have native support for this.
+relies on a filesystem snapshot implementation\. Many common filesystems have native support for this\.
 .PP
 Filesystem snapshots must be mounted on specially named directories in order to be recognized by
 vfs_shadow_copy. The snapshot mount points must be immediate children of a the directory being shared.
+vfs_shadow_copy\. The snapshot mount points must be immediate children of a the directory being shared\.
 .PP
+The snapshot naming convention is @GMT-YYYY.MM.DD-hh.mm.ss, where:
+.TP 3n
+\(bu
+The snapshot naming convention is @GMT\-YYYY\.MM\.DD\-hh\.mm\.ss, where:
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 YYYY
 is the 4 digit year
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 MM
 is the 2 digit month
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 DD
 is the 2 digit day
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 hh
 is the 2 digit hour
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 mm
 is the 2 digit minute
+.TP 3n
+\(bu
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 ss
 is the 2 digit second.
+is the 2 digit second\.
 .sp
 .RE
 .PP
 The
 …
 \fBdate\fR(1)
 command:
 .sp
+.RS 4
 .nf
+        TZ=GMT date +@GMT-%Y.%m.%d-%H.%M.%S
+        TZ=GMT date +@GMT\-%Y\.%m\.%d\-%H\.%M\.%S
 .fi
+.RE
 .SH "EXAMPLES"
 .PP
 Add shadow copy support to user home directories:
+.sp
+.RS 4
 .nf
         \fI[homes]\fR
+        vfs objects = shadow_copy
+        \fIvfs objects = shadow_copy\fR
 .fi
+.RE
 .SH "CAVEATS"
 .PP
 This is not a backup, archival, or version control solution.
+This is not a backup, archival, or version control solution\.
 .PP
 With Samba or Windows servers,
 vfs_shadow_copy
 is designed to be an end-user tool only. It does not replace or enhance your backup and archival solutions and should in no way be considered as such. Additionally, if you need version control, implement a version control system.
+is designed to be an end\-user tool only\. It does not replace or enhance your backup and archival solutions and should in no way be considered as such\. Additionally, if you need version control, implement a version control system\.
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0.25 of the Samba suite.
+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.
+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\.

branches/samba-3.0/docs/manpages/vfstest.1

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "VFSTEST" 1 "" "" ""
+.\"     Title: vfstest
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: User Commands
+.\"    Source: Samba 3.0
+.\"
+.TH "VFSTEST" "1" "05/21/2008" "Samba 3\.0" "User Commands"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 vfstest - tool for testing samba VFS modules
 .SH "SYNOPSIS"
 .HP 1
 vfstest [-d debuglevel] [-c command] [-l logdir] [-h]
+vfstest [\-d\ debuglevel] [\-c\ command] [\-l\ logdir] [\-h]
 .SH "DESCRIPTION"
 .PP
 This tool is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 vfstest
 is a small command line utility that has the ability to test dso samba VFS modules. It gives the user the ability to call the various VFS functions manually and supports cascaded VFS modules.
+is a small command line utility that has the ability to test dso samba VFS modules\. It gives the user the ability to call the various VFS functions manually and supports cascaded VFS modules\.
 .SH "OPTIONS"
 .PP
+-c|--command=command
+.RS 3n
+Execute the specified (colon-separated) commands. See below for the commands that are available.
+.RE
+.PP
+-h|--help
+.RS 3n
+Print a summary of command line options.
+.RE
+.PP
+-l|--logfile=logbasename
+.RS 3n
+File name for log/debug files. The extension
+\fB'.client'\fR
+will be appended. The log file is never removed by the client.
+.RE
+.PP
+-V
+.RS 3n
+Prints the program version number.
+.RE
+.PP
+-s <configuration file>
+.RS 3n
+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
+\fIsmb.conf\fR
+for more information. The default configuration file name is determined at compile time.
+.RE
+.PP
+-d|--debuglevel=level
+.RS 3n
+\-c|\-\-command=command
+.RS 4
+Execute the specified (colon\-separated) commands\. See below for the commands that are available\.
+.RE
+.PP
+\-h|\-\-help
+.RS 4
+Print a summary of command line options\.
+.RE
+.PP
+\-l|\-\-logfile=logbasename
+.RS 4
+File name for log/debug files\. The extension
+\fB\'\.client\'\fR
+will be appended\. The log file is never removed by the client\.
+.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 zero.
 .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.
+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
+\fIlog level\fR
 parameter in the
+\fIsmb.conf\fR
+file.
+.RE
+.PP
+-l|--logfile=logdirectory
+.RS 3n
+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.
+\fIsmb\.conf\fR
+file\.
+.RE
+.PP
+\-V
+.RS 4
+Prints the program version number\.
+.RE
+.PP
+\-s <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
+\fIsmb\.conf\fR
+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
 .SH "COMMANDS"
 .PP
+\fBVFS COMMANDS\fR
+.TP 3n
+\(bu
+load <module.so>
+- Load specified VFS module
+.TP 3n
+\(bu
+\fIVFS COMMANDS\fR
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+load <module\.so>
+\- Load specified VFS module
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 populate <char> <size>
+- Populate a data buffer with the specified data
+.TP 3n
+\(bu
+\- Populate a data buffer with the specified data
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 showdata [<offset> <len>]
+- Show data currently in data buffer
+.TP 3n
+\(bu
+\- Show data currently in data buffer
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 connect
+- VFS connect()
+.TP 3n
+\(bu
+\- VFS connect()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 disconnect
+- VFS disconnect()
+.TP 3n
+\(bu
+\- VFS disconnect()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 disk_free
+- VFS disk_free()
+.TP 3n
+\(bu
+\- VFS disk_free()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 opendir
+- VFS opendir()
+.TP 3n
+\(bu
+\- VFS opendir()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 readdir
+- VFS readdir()
+.TP 3n
+\(bu
+\- VFS readdir()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 mkdir
+- VFS mkdir()
+.TP 3n
+\(bu
+\- VFS mkdir()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 rmdir
+- VFS rmdir()
+.TP 3n
+\(bu
+\- VFS rmdir()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 closedir
+- VFS closedir()
+.TP 3n
+\(bu
+\- VFS closedir()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 open
+- VFS open()
+.TP 3n
+\(bu
+\- VFS open()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 close
+- VFS close()
+.TP 3n
+\(bu
+\- VFS close()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 read
+- VFS read()
+.TP 3n
+\(bu
+\- VFS read()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 write
+- VFS write()
+.TP 3n
+\(bu
+\- VFS write()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 lseek
+- VFS lseek()
+.TP 3n
+\(bu
+\- VFS lseek()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 rename
+- VFS rename()
+.TP 3n
+\(bu
+\- VFS rename()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 fsync
+- VFS fsync()
+.TP 3n
+\(bu
+\- VFS fsync()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 stat
+- VFS stat()
+.TP 3n
+\(bu
+\- VFS stat()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 fstat
+- VFS fstat()
+.TP 3n
+\(bu
+\- VFS fstat()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 lstat
+- VFS lstat()
+.TP 3n
+\(bu
+\- VFS lstat()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 unlink
+- VFS unlink()
+.TP 3n
+\(bu
+\- VFS unlink()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 chmod
+- VFS chmod()
+.TP 3n
+\(bu
+\- VFS chmod()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 fchmod
+- VFS fchmod()
+.TP 3n
+\(bu
+\- VFS fchmod()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 chown
+- VFS chown()
+.TP 3n
+\(bu
+\- VFS chown()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 fchown
+- VFS fchown()
+.TP 3n
+\(bu
+\- VFS fchown()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 chdir
+- VFS chdir()
+.TP 3n
+\(bu
+\- VFS chdir()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 getwd
+- VFS getwd()
+.TP 3n
+\(bu
+\- VFS getwd()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 utime
+- VFS utime()
+.TP 3n
+\(bu
+\- VFS utime()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 ftruncate
+- VFS ftruncate()
+.TP 3n
+\(bu
+\- VFS ftruncate()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 lock
+- VFS lock()
+.TP 3n
+\(bu
+\- VFS lock()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 symlink
+- VFS symlink()
+.TP 3n
+\(bu
+\- VFS symlink()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 readlink
+- VFS readlink()
+.TP 3n
+\(bu
+\- VFS readlink()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 link
+- VFS link()
+.TP 3n
+\(bu
+\- VFS link()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 mknod
+- VFS mknod()
+.TP 3n
+\(bu
+\- VFS mknod()
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 realpath
+- VFS realpath()
+.PP
+\fBGENERAL COMMANDS\fR
+.TP 3n
+\(bu
+conf <smb.conf>
+- Load a different configuration file
+.TP 3n
+\(bu
+\- VFS realpath()
+.sp
+.RE
+.PP
+\fIGENERAL COMMANDS\fR
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+conf <smb\.conf>
+\- Load a different configuration file
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 help [<command>]
+- Get list of commands or info about specified command
+.TP 3n
+\(bu
+\- Get list of commands or info about specified command
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 debuglevel <level>
+- Set debug level
+.TP 3n
+\(bu
+\- Set debug level
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 freemem
+- Free memory currently in use
+.TP 3n
+\(bu
+\- Free memory currently in use
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
 exit
 - Exit vfstest
+\- Exit vfstest
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 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 vfstest man page was written by Jelmer Vernooij.
+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 vfstest man page was written by Jelmer Vernooij\.

branches/samba-3.0/docs/manpages/wbinfo.1

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "WBINFO" 1 "" "" ""
+.\"     Title: wbinfo
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: User Commands
+.\"    Source: Samba 3.0
+.\"
+.TH "WBINFO" "1" "05/21/2008" "Samba 3\.0" "User Commands"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 wbinfo - Query information from winbind daemon
 .SH "SYNOPSIS"
 .HP 1
 wbinfo [-a user%password] [--all-domains] [--allocate-gid] [--allocate-uid] [-D domain] [--domain domain] [-g] [--getdcname domain] [--get-auth-user] [-G gid] [-h] [-i user] [-I ip] [-K user%password] [-m] [-n name] [-N netbios-name] [--own-domain] [-p] [-r user] [-s sid] [--separator] [--sequence] [--set-auth-user user%password] [-S sid] [-t] [-u] [--user-domgroups sid] [--user-sids sid] [-U uid] [-V] [-Y sid]
+wbinfo [\-a\ user%password] [\-\-all\-domains] [\-\-allocate\-gid] [\-\-allocate\-uid] [\-D\ domain] [\-\-domain\ domain] [\-g] [\-\-getdcname\ domain] [\-\-get\-auth\-user] [\-G\ gid] [\-h] [\-i\ user] [\-I\ ip] [\-K\ user%password] [\-m] [\-n\ name] [\-N\ netbios\-name] [\-\-own\-domain] [\-p] [\-r\ user] [\-s\ sid] [\-\-separator] [\-\-sequence] [\-\-set\-auth\-user\ user%password] [\-S\ sid] [\-t] [\-u] [\-\-uid\-info\ uid] [\-\-user\-domgroups\ sid] [\-\-user\-sids\ sid] [\-U\ uid] [\-V] [\-Y\ sid] [\-\-verbose]
 .SH "DESCRIPTION"
 .PP
 This tool is part of the
 \fBsamba\fR(7)
 suite.
+suite\.
 .PP
 The
 …
 program queries and returns information created and used by the
 \fBwinbindd\fR(8)
 daemon.
+daemon\.
 .PP
 The
 …
 daemon must be configured and running for the
 wbinfo
 program to be able to return information.
+program to be able to return information\.
 .SH "OPTIONS"
 .PP
 -a|--authenticate username%password
 .RS 3n
 Attempt to authenticate a user via winbindd. This checks both authenticaion methods and reports its results.
+\-a|\-\-authenticate username%password
+.RS 4
+Attempt to authenticate a user via winbindd\. This checks both authenticaion methods and reports its results\.
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBNote\fR
 Do not be tempted to use this functionality for authentication in third-party applications. Instead use
 \fBntlm_auth\fR(1).
 .RE
 .PP
 --allocate-gid
 .RS 3n
+Note
+Do not be tempted to use this functionality for authentication in third\-party applications\. Instead use
+\fBntlm_auth\fR(1)\.
+.RE
+.PP
+\-\-allocate\-gid
+.RS 4
 Get a new GID out of idmap
 .RE
 .PP
 --allocate-uid
 .RS 3n
+\-\-allocate\-uid
+.RS 4
 Get a new UID out of idmap
 .RE
 .PP
 --all-domains
 .RS 3n
 List all domains (trusted and own domain).
 .RE
 .PP
 --domain name
 .RS 3n
 This parameter sets the domain on which any specified operations will performed. If special domain name '.' is used to represent the current domain to which winbindd belongs. Currently only the
 \fB--sequence\fR,
 \fB-u\fR, and
 \fB-g\fR
 options honor this parameter.
 .RE
 .PP
 -D|--domain-info domain
 .RS 3n
 Show most of the info we have about the domain.
 .RE
 .PP
 -g|--domain-groups
 .RS 3n
+\-\-all\-domains
+.RS 4
+List all domains (trusted and own domain)\.
+.RE
+.PP
+\-\-domain name
+.RS 4
+This parameter sets the domain on which any specified operations will performed\. If special domain name \'\.\' is used to represent the current domain to which winbindd belongs\. Currently only the
+\fB\-\-sequence\fR,
+\fB\-u\fR, and
+\fB\-g\fR
+options honor this parameter\.
+.RE
+.PP
+\-D|\-\-domain\-info domain
+.RS 4
+Show most of the info we have about the domain\.
+.RE
+.PP
+\-g|\-\-domain\-groups
+.RS 4
 This option will list all groups available in the Windows NT domain for which the
 \fBsamba\fR(7)
 daemon is operating in. Groups in all trusted domains will also be listed. Note that this operation does not assign group ids to any groups that have not already been seen by
 \fBwinbindd\fR(8).
 .RE
 .PP
 --get-auth-user
 .RS 3n
 Print username and password used by winbindd during session setup to a domain controller. Username and password can be set using
 \fB--set-auth-user\fR. Only available for root.
 .RE
 .PP
 --getdcname domain
 .RS 3n
 Get the DC name for the specified domain.
 .RE
 .PP
 -G|--gid-to-sid gid
 .RS 3n
 Try to convert a UNIX group id to a Windows NT SID. If the gid specified does not refer to one within the idmap gid range then the operation will fail.
 .RE
 .PP
 -i|--user-info user
 .RS 3n
 Get user info.
 .RE
 .PP
 -I|--WINS-by-ip ip
 .RS 3n
 The
 \fI-I\fR
+daemon is operating in\. Groups in all trusted domains will also be listed\. Note that this operation does not assign group ids to any groups that have not already been seen by
+\fBwinbindd\fR(8)\.
+.RE
+.PP
+\-\-get\-auth\-user
+.RS 4
+Print username and password used by winbindd during session setup to a domain controller\. Username and password can be set using
+\fB\-\-set\-auth\-user\fR\. Only available for root\.
+.RE
+.PP
+\-\-getdcname domain
+.RS 4
+Get the DC name for the specified domain\.
+.RE
+.PP
+\-G|\-\-gid\-to\-sid gid
+.RS 4
+Try to convert a UNIX group id to a Windows NT SID\. If the gid specified does not refer to one within the idmap gid range then the operation will fail\.
+.RE
+.PP
+\-i|\-\-user\-info user
+.RS 4
+Get user info\.
+.RE
+.PP
+\-I|\-\-WINS\-by\-ip ip
+.RS 4
+The
+\fI\-I\fR
 option queries
 \fBwinbindd\fR(8)
 to send a node status request to get the NetBIOS name associated with the IP address specified by the
 \fIip\fR
 parameter.
 .RE
 .PP
 -K|--krb5auth username%password
 .RS 3n
 Attempt to authenticate a user via Kerberos.
 .RE
 .PP
 -m|--trusted-domains
 .RS 3n
+parameter\.
+.RE
+.PP
+\-K|\-\-krb5auth username%password
+.RS 4
+Attempt to authenticate a user via Kerberos\.
+.RE
+.PP
+\-m|\-\-trusted\-domains
+.RS 4
 Produce a list of domains trusted by the Windows NT server
 \fBwinbindd\fR(8)
 contacts when resolving names. This list does not include the Windows NT domain the server is a Primary Domain Controller for.
 .RE
 .PP
 -n|--name-to-sid name
 .RS 3n
 The
 \fI-n\fR
+contacts when resolving names\. This list does not include the Windows NT domain the server is a Primary Domain Controller for\.
+.RE
+.PP
+\-n|\-\-name\-to\-sid name
+.RS 4
+The
+\fI\-n\fR
 option queries
 \fBwinbindd\fR(8)
 for the SID associated with the name specified. Domain names can be specified before the user name by using the winbind separator character. For example CWDOM1/Administrator refers to the Administrator user in the domain CWDOM1. If no domain is specified then the domain used is the one specified in the
+for the SID associated with the name specified\. Domain names can be specified before the user name by using the winbind separator character\. For example CWDOM1/Administrator refers to the Administrator user in the domain CWDOM1\. If no domain is specified then the domain used is the one specified in the
 \fBsmb.conf\fR(5)
 \fIworkgroup \fR
 parameter.
 .RE
 .PP
 -N|--WINS-by-name name
 .RS 3n
 The
 \fI-N\fR
+parameter\.
+.RE
+.PP
+\-N|\-\-WINS\-by\-name name
+.RS 4
+The
+\fI\-N\fR
 option queries
 \fBwinbindd\fR(8)
 to query the WINS server for the IP address associated with the NetBIOS name specified by the
 \fIname\fR
 parameter.
 .RE
 .PP
 --own-domain
 .RS 3n
 List own domain.
 .RE
 .PP
 -p|--ping
 .RS 3n
 Check whether winbindd is still alive. Prints out either 'succeeded' or 'failed'.
 .RE
 .PP
 -r|--user-groups username
 .RS 3n
 Try to obtain the list of UNIX group ids to which the user belongs. This only works for users defined on a Domain Controller.
 .RE
 .PP
 -s|--sid-to-name sid
 .RS 3n
+parameter\.
+.RE
+.PP
+\-\-own\-domain
+.RS 4
+List own domain\.
+.RE
+.PP
+\-p|\-\-ping
+.RS 4
+Check whether winbindd is still alive\. Prints out either \'succeeded\' or \'failed\'\.
+.RE
+.PP
+\-r|\-\-user\-groups username
+.RS 4
+Try to obtain the list of UNIX group ids to which the user belongs\. This only works for users defined on a Domain Controller\.
+.RE
+.PP
+\-s|\-\-sid\-to\-name sid
+.RS 4
 Use
 \fI-s\fR
 to resolve a SID to a name. This is the inverse of the
 \fI-n \fR
 option above. SIDs must be specified as ASCII strings in the traditional Microsoft format. For example, S-1-5-21-1455342024-3071081365-2475485837-500.
 .RE
 .PP
 --separator
 .RS 3n
 Get the active winbind separator.
 .RE
 .PP
 --sequence
 .RS 3n
+\fI\-s\fR
+to resolve a SID to a name\. This is the inverse of the
+\fI\-n \fR
+option above\. SIDs must be specified as ASCII strings in the traditional Microsoft format\. For example, S\-1\-5\-21\-1455342024\-3071081365\-2475485837\-500\.
+.RE
+.PP
+\-\-separator
+.RS 4
+Get the active winbind separator\.
+.RE
+.PP
+\-\-sequence
+.RS 4
 Show sequence numbers of all known domains
 .RE
 .PP
 --set-auth-user username%password
 .RS 3n
 Store username and password used by winbindd during session setup to a domain controller. This enables winbindd to operate in a Windows 2000 domain with Restrict Anonymous turned on (a.k.a. Permissions compatiable with Windows 2000 servers only).
 .RE
 .PP
 -S|--sid-to-uid sid
 .RS 3n
 Convert a SID to a UNIX user id. If the SID does not correspond to a UNIX user mapped by
 \fBwinbindd\fR(8)
 then the operation will fail.
 .RE
 .PP
 -t|--check-secret
 .RS 3n
 Verify that the workstation trust account created when the Samba server is added to the Windows NT domain is working.
 .RE
 .PP
 -u|--domain-users
 .RS 3n
+\-\-set\-auth\-user username%password
+.RS 4
+Store username and password used by winbindd during session setup to a domain controller\. This enables winbindd to operate in a Windows 2000 domain with Restrict Anonymous turned on (a\.k\.a\. Permissions compatible with Windows 2000 servers only)\.
+.RE
+.PP
+\-S|\-\-sid\-to\-uid sid
+.RS 4
+Convert a SID to a UNIX user id\. If the SID does not correspond to a UNIX user mapped by
+\fBwinbindd\fR(8)
+then the operation will fail\.
+.RE
+.PP
+\-t|\-\-check\-secret
+.RS 4
+Verify that the workstation trust account created when the Samba server is added to the Windows NT domain is working\.
+.RE
+.PP
+\-u|\-\-domain\-users
+.RS 4
 This option will list all users available in the Windows NT domain for which the
 \fBwinbindd\fR(8)
+daemon is operating in. Users in all trusted domains will also be listed. Note that this operation does not assign user ids to any users that have not already been seen by
+\fBwinbindd\fR(8)
+.
+.RE
+.PP
+--user-domgroups SID
+.RS 3n
+Get user domain groups.
+.RE
+.PP
+--user-sids SID
+.RS 3n
+Get user group SIDs for user.
+.RE
+.PP
+-U|--uid-to-sid uid
+.RS 3n
+Try to convert a UNIX user id to a Windows NT SID. If the uid specified does not refer to one within the idmap uid range then the operation will fail.
+.RE
+.PP
+-Y|--sid-to-gid sid
+.RS 3n
+Convert a SID to a UNIX group id. If the SID does not correspond to a UNIX group mapped by
+\fBwinbindd\fR(8)
+then the operation will fail.
+.RE
+.PP
+-V
+.RS 3n
+Prints the program version number.
+.RE
+.PP
+-h|--help
+.RS 3n
+Print a summary of command line options.
+daemon is operating in\. Users in all trusted domains will also be listed\. Note that this operation does not assign user ids to any users that have not already been seen by
+\fBwinbindd\fR(8)
+\.
+.RE
+.PP
+\-\-uid\-info UID
+.RS 4
+Get user info for the user conencted to user id UID\.
+.RE
+.PP
+\-\-user\-domgroups SID
+.RS 4
+Get user domain groups\.
+.RE
+.PP
+\-\-user\-sids SID
+.RS 4
+Get user group SIDs for user\.
+.RE
+.PP
+\-U|\-\-uid\-to\-sid uid
+.RS 4
+Try to convert a UNIX user id to a Windows NT SID\. If the uid specified does not refer to one within the idmap uid range then the operation will fail\.
+.RE
+.PP
+\-\-verbose
+.RS 4
+Print additional information about the query results\.
+.RE
+.PP
+\-Y|\-\-sid\-to\-gid sid
+.RS 4
+Convert a SID to a UNIX group id\. If the SID does not correspond to a UNIX group mapped by
+\fBwinbindd\fR(8)
+then the operation will fail\.
+.RE
+.PP
+\-V
+.RS 4
+Prints the program version number\.
+.RE
+.PP
+\-h|\-\-help
+.RS 4
+Print a summary of command line options\.
 .RE
 .SH "EXIT STATUS"
 .PP
 The wbinfo program returns 0 if the operation succeeded, or 1 if the operation failed. If the
+The wbinfo program returns 0 if the operation succeeded, or 1 if the operation failed\. If the
 \fBwinbindd\fR(8)
 daemon is not working
 wbinfo
 will always return failure.
+will always return failure\.
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 of the Samba suite\.
 .SH "SEE ALSO"
 .PP
 …
 .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.
+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
 wbinfo
 and
 winbindd
+were written by Tim Potter.
+.PP
+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.
+were written by Tim Potter\.
+.PP
+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\.

branches/samba-3.0/docs/manpages/winbindd.8

-              r44
+              r134
+.\"Generated by db2man.xsl. Don't modify this, modify the source.
+.de Sh \" Subsection
+.br
+.if t .Sp
+.ne 5
+.PP
+\fB\\$1\fR
+.PP
+..
+.de Sp \" Vertical space (when we can't use .PP)
+.if t .sp .5v
+.if n .sp
+..
+.de Ip \" List item
+.br
+.ie \\n(.$>=3 .ne \\$3
+.el .ne 3
+.IP "\\$1" \\$2
+..
+.TH "WINBINDD" 8 "" "" ""
+.\"     Title: winbindd
+.\"    Author:
+.\" Generator: DocBook XSL Stylesheets v1.73.2 <http://docbook.sf.net/>
+.\"      Date: 05/21/2008
+.\"    Manual: System Administration tools
+.\"    Source: Samba 3.0
+.\"
+.TH "WINBINDD" "8" "05/21/2008" "Samba 3\.0" "System Administration tools"
+.\" disable hyphenation
+.nh
+.\" disable justification (adjust text to left margin only)
+.ad l
 .SH "NAME"
 winbindd - Name Service Switch daemon for resolving names from NT servers
 .SH "SYNOPSIS"
 .HP 1
 winbindd [-F] [-S] [-i] [-Y] [-d <debug level>] [-s <smb config file>] [-n]
+winbindd [\-D] [\-F] [\-S] [\-i] [\-Y] [\-d\ <debug\ level>] [\-s\ <smb\ config\ file>] [\-n]
 .SH "DESCRIPTION"
 .PP
 This program is part of the
 \fBsamba\fR(7)
 suite.
 .PP
 winbindd
 is a daemon that provides a number of services to the Name Service Switch capability found in most modern C libraries, to arbitary applications via PAM and
+suite\.
+.PP
+winbindd
+is a daemon that provides a number of services to the Name Service Switch capability found in most modern C libraries, to arbitrary applications via PAM and
 ntlm_auth
 and to Samba itself.
+and to Samba itself\.
 .PP
 Even if winbind is not used for nsswitch, it still provides a service to
 …
 ntlm_auth
 and the
+pam_winbind.so
+PAM module, by managing connections to domain controllers. In this configuraiton the
+idmap uid and
+idmap gid parameters are not required. (This is known as `netlogon proxy only mode'.)
+.PP
+The Name Service Switch allows user and system information to be obtained from different databases services such as NIS or DNS. The exact behaviour can be configured throught the
+\fI/etc/nsswitch.conf\fR
+file. Users and groups are allocated as they are resolved to a range of user and group ids specified by the administrator of the Samba system.
+pam_winbind\.so
+PAM module, by managing connections to domain controllers\. In this configuraiton the
+\fIidmap uid\fR
+and
+\fIidmap gid\fR
+parameters are not required\. (This is known as `netlogon proxy only mode\'\.)
+.PP
+The Name Service Switch allows user and system information to be obtained from different databases services such as NIS or DNS\. The exact behaviour can be configured throught the
+\fI/etc/nsswitch\.conf\fR
+file\. Users and groups are allocated as they are resolved to a range of user and group ids specified by the administrator of the Samba system\.
 .PP
 The service provided by
 winbindd
 is called `winbind' and can be used to resolve user and group information from a Windows NT server. The service can also provide authentication services via an associated PAM module.
+is called `winbind\' and can be used to resolve user and group information from a Windows NT server\. The service can also provide authentication services via an associated PAM module\.
 .PP
 The
 …
 and
 \fIpassword\fR
 module-types. It should be noted that the
+module\-types\. It should be noted that the
 \fIaccount\fR
 module simply performs a getpwnam() to verify that the system can obtain a uid for the user, as the domain controller has already performed access control. If the
+module simply performs a getpwnam() to verify that the system can obtain a uid for the user, as the domain controller has already performed access control\. If the
 \fIlibnss_winbind\fR
 library has been correctly installed, or an alternate source of names configured, this should always succeed.
+library has been correctly installed, or an alternate source of names configured, this should always succeed\.
 .PP
 The following nsswitch databases are implemented by the winbindd service:
 .PP
+\-D
+.RS 4
+If specified, this parameter causes the server to operate as a daemon\. That is, it detaches itself and runs in the background on the appropriate port\. This switch is assumed if
+winbindd
+is executed on the command line of a shell\.
+.RE
+.PP
 hosts
 .RS 3n
 This feature is only available on IRIX. User information traditionally stored in the
+.RS 4
+This feature is only available on IRIX\. User information traditionally stored in the
 \fIhosts(5)\fR
 file and used by
 gethostbyname(3)
 functions. Names are resolved through the WINS server or by broadcast.
+functions\. Names are resolved through the WINS server or by broadcast\.
 .RE
 .PP
 passwd
 .RS 3n
+.RS 4
 User information traditionally stored in the
 \fIpasswd(5)\fR
 file and used by
 getpwent(3)
 functions.
+functions\.
 .RE
 .PP
 group
 .RS 3n
+.RS 4
 Group information traditionally stored in the
 \fIgroup(5)\fR
 file and used by
 getgrent(3)
 functions.
+functions\.
 .RE
 .PP
 For example, the following simple configuration in the
 \fI/etc/nsswitch.conf\fR
+\fI/etc/nsswitch\.conf\fR
 file can be used to initially resolve user and group information from
 \fI/etc/passwd \fR
 and
 \fI/etc/group\fR
+and then from the Windows NT server.
+.sp
+and then from the Windows NT server\.
+.sp
+.RS 4
 .nf
 passwd:         files winbind
 group:          files winbind
 ## only available on IRIX; Linux users should us libnss_wins.so
+## only available on IRIX; Linux users should us libnss_wins\.so
 hosts:          files dns winbind
 .fi
+.RE
 .PP
 The following simple configuration in the
 \fI/etc/nsswitch.conf\fR
+\fI/etc/nsswitch\.conf\fR
 file can be used to initially resolve hostnames from
 \fI/etc/hosts\fR
+and then from the WINS server.
+and then from the WINS server\.
+.sp
+.RS 4
 .nf
 hosts:          files wins
 .fi
+.RE
 .SH "OPTIONS"
 .PP
 -F
 .RS 3n
+\-F
+.RS 4
 If specified, this parameter causes the main
 winbindd
 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
+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
 winbindd
 under process supervisors such as
 …
 and
 svscan
 from Daniel J. Bernstein's
+from Daniel J\. Bernstein\'s
 daemontools
 package, or the AIX process monitor.
 .RE
 .PP
 -S
 .RS 3n
+package, or the AIX process monitor\.
+.RE
+.PP
+\-S
+.RS 4
 If specified, this parameter causes
 winbindd
+to log to standard output rather than a file.
+.RE
+.PP
+-V
+.RS 3n
+Prints the program version number.
+.RE
+.PP
+-s <configuration file>
+.RS 3n
+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
+\fIsmb.conf\fR
+for more information. The default configuration file name is determined at compile time.
+.RE
+.PP
+-d|--debuglevel=level
+.RS 3n
+to log to standard output rather than a 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 zero.
 .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.
+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
+\fIlog level\fR
 parameter in the
+\fIsmb.conf\fR
+file.
+.RE
+.PP
+-l|--logfile=logdirectory
+.RS 3n
+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
+-h|--help
+.RS 3n
+Print a summary of command line options.
+.RE
+.PP
+-i
+.RS 3n
+\fIsmb\.conf\fR
+file\.
+.RE
+.PP
+\-V
+.RS 4
+Prints the program version number\.
+.RE
+.PP
+\-s <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
+\fIsmb\.conf\fR
+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
+\-h|\-\-help
+.RS 4
+Print a summary of command line options\.
+.RE
+.PP
+\-i
+.RS 4
 Tells
 winbindd
 to not become a daemon and detach from the current terminal. This option is used by developers when interactive debugging of
 winbindd
 is required.
+to not become a daemon and detach from the current terminal\. This option is used by developers when interactive debugging of
+winbindd
+is required\.
 winbindd
 also logs to standard output, as if the
 -S
 parameter had been given.
 .RE
 .PP
 -n
 .RS 3n
 Disable caching. This means winbindd will always have to wait for a response from the domain controller before it can respond to a client and this thus makes things slower. The results will however be more accurate, since results from the cache might not be up-to-date. This might also temporarily hang winbindd if the DC doesn't respond.
 .RE
 .PP
 -Y
 .RS 3n
 Single daemon mode. This means winbindd will run as a single process (the mode of operation in Samba 2.2). Winbindd's default behavior is to launch a child process that is responsible for updating expired cache entries.
+\-S
+parameter had been given\.
+.RE
+.PP
+\-n
+.RS 4
+Disable caching\. This means winbindd will always have to wait for a response from the domain controller before it can respond to a client and this thus makes things slower\. The results will however be more accurate, since results from the cache might not be up\-to\-date\. This might also temporarily hang winbindd if the DC doesn\'t respond\.
+.RE
+.PP
+\-Y
+.RS 4
+Single daemon mode\. This means winbindd will run as a single process (the mode of operation in Samba 2\.2)\. Winbindd\'s default behavior is to launch a child process that is responsible for updating expired cache entries\.
 .RE
 .SH "NAME AND ID RESOLUTION"
 .PP
 Users and groups on a Windows NT server are assigned a security id (SID) which is globally unique when the user or group is created. To convert the Windows NT user or group into a unix user or group, a mapping between SIDs and unix user and group ids is required. This is one of the jobs that
 winbindd
 performs.
 .PP
 As winbindd users and groups are resolved from a server, user and group ids are allocated from a specified range. This is done on a first come, first served basis, although all existing users and groups will be mapped as soon as a client performs a user or group enumeration command. The allocated unix ids are stored in a database and will be remembered.
 .PP
 WARNING: The SID to unix id database is the only location where the user and group mappings are stored by winbindd. If this store is deleted or corrupted, there is no way for winbindd to determine which user and group ids correspond to Windows NT user and group rids.
+Users and groups on a Windows NT server are assigned a security id (SID) which is globally unique when the user or group is created\. To convert the Windows NT user or group into a unix user or group, a mapping between SIDs and unix user and group ids is required\. This is one of the jobs that
+winbindd
+performs\.
+.PP
+As winbindd users and groups are resolved from a server, user and group ids are allocated from a specified range\. This is done on a first come, first served basis, although all existing users and groups will be mapped as soon as a client performs a user or group enumeration command\. The allocated unix ids are stored in a database and will be remembered\.
+.PP
+WARNING: The SID to unix id database is the only location where the user and group mappings are stored by winbindd\. If this store is deleted or corrupted, there is no way for winbindd to determine which user and group ids correspond to Windows NT user and group rids\.
 .PP
 See the
+\fIidmap domains\fR
 or the old
+\fIidmap backend\fR
 parameters in
 \fIsmb.conf\fR
 for options for sharing this database, such as via LDAP.
+\fIsmb\.conf\fR
+for options for sharing this database, such as via LDAP\.
 .SH "CONFIGURATION"
 .PP
 …
 daemon is done through configuration parameters in the
 \fBsmb.conf\fR(5)
+file. All parameters should be specified in the [global] section of smb.conf.
+.TP 3n
+\(bu
+winbind separator
+.TP 3n
+\(bu
+idmap uid
+.TP 3n
+\(bu
+idmap gid
+.TP 3n
+\(bu
+idmap backend
+.TP 3n
+\(bu
+winbind cache time
+.TP 3n
+\(bu
+winbind enum users
+.TP 3n
+\(bu
+winbind enum groups
+.TP 3n
+\(bu
+template homedir
+.TP 3n
+\(bu
+template shell
+.TP 3n
+\(bu
+winbind use default domain
+.TP 3n
+\(bu
+winbind: rpc only Setting this parameter forces winbindd to use RPC instead of LDAP to retrieve information from Domain Controllers.
+file\. All parameters should be specified in the [global] section of smb\.conf\.
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\fIwinbind separator\fR
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\fIidmap uid\fR
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\fIidmap gid\fR
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\fIidmap backend\fR
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\fIwinbind cache time\fR
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\fIwinbind enum users\fR
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\fIwinbind enum groups\fR
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\fItemplate homedir\fR
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\fItemplate shell\fR
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\fIwinbind use default domain\fR
+.RE
+.sp
+.RS 4
+.ie n \{\
+\h'-04'\(bu\h'+03'\c
+.\}
+.el \{\
+.sp -1
+.IP \(bu 2.3
+.\}
+\fIwinbind: rpc only\fR
+Setting this parameter forces winbindd to use RPC instead of LDAP to retrieve information from Domain Controllers\.
 .SH "EXAMPLE SETUP"
 .PP
 To setup winbindd for user and group lookups plus authentication from a domain controller use something like the following setup. This was tested on an early Red Hat Linux box.
+To setup winbindd for user and group lookups plus authentication from a domain controller use something like the following setup\. This was tested on an early Red Hat Linux box\.
 .PP
 In
 \fI/etc/nsswitch.conf\fR
+\fI/etc/nsswitch\.conf\fR
 put the following:
+.sp
+.sp
+.RS 4
 .nf
 passwd: files winbind
 group:  files winbind
 .fi
+.RE
 .PP
 In
 \fI/etc/pam.d/*\fR
+\fI/etc/pam\.d/*\fR
 replace the
 \fI auth\fR
 lines with something like this:
+.sp
+.sp
+.RS 4
 .nf
+auth  required    /lib/security/pam_securetty.so
+auth  required    /lib/security/pam_nologin.so
+auth  sufficient  /lib/security/pam_winbind.so
+auth  required    /lib/security/pam_unix.so \
+auth  required    /lib/security/pam_securetty\.so
+auth  required    /lib/security/pam_nologin\.so
+auth  sufficient  /lib/security/pam_winbind\.so
+auth  required    /lib/security/pam_unix\.so \e
                   use_first_pass shadow nullok
 .fi
+.RE
+.sp
 .sp
 .it 1 an-trap
 …
 .nr an-break-flag 1
 .br
+\fBNote\fR
 .PP
 The PAM module pam_unix has recently replaced the module pam_pwdb. Some Linux systems use the module pam_unix2 in place of pam_unix.
+Note
+.PP
+The PAM module pam_unix has recently replaced the module pam_pwdb\. Some Linux systems use the module pam_unix2 in place of pam_unix\.
 .PP
 Note in particular the use of the
 …
 keyword and the
 \fIuse_first_pass\fR
 keyword.
+keyword\.
 .PP
 Now replace the account lines with this:
 .PP
 account required /lib/security/pam_winbind.so
 .PP
 The next step is to join the domain. To do that use the
+account required /lib/security/pam_winbind\.so
+.PP
+The next step is to join the domain\. To do that use the
 net
 program like this:
 .PP
 net join -S PDC -U Administrator
+net join \-S PDC \-U Administrator
 .PP
 The username after the
 \fI-U\fR
 can be any Domain user that has administrator privileges on the machine. Substitute the name or IP of your PDC for "PDC".
+\fI\-U\fR
+can be any Domain user that has administrator privileges on the machine\. Substitute the name or IP of your PDC for "PDC"\.
 .PP
 Next copy
 \fIlibnss_winbind.so\fR
+\fIlibnss_winbind\.so\fR
 to
 \fI/lib\fR
 and
 \fIpam_winbind.so \fR
+\fIpam_winbind\.so \fR
 to
 \fI/lib/security\fR. A symbolic link needs to be made from
 \fI/lib/libnss_winbind.so\fR
+\fI/lib/security\fR\. A symbolic link needs to be made from
+\fI/lib/libnss_winbind\.so\fR
 to
 \fI/lib/libnss_winbind.so.2\fR. If you are using an older version of glibc then the target of the link should be
 \fI/lib/libnss_winbind.so.1\fR.
+\fI/lib/libnss_winbind\.so\.2\fR\. If you are using an older version of glibc then the target of the link should be
+\fI/lib/libnss_winbind\.so\.1\fR\.
 .PP
 Finally, setup a
 \fBsmb.conf\fR(5)
 containing directives like the following:
+.sp
+.sp
+.RS 4
 .nf
 [global]
         winbind separator = +
 …
         template shell = /bin/bash
         template homedir = /home/%D/%U
         idmap uid = 10000-20000
         idmap gid = 10000-20000
+        idmap uid = 10000\-20000
+        idmap gid = 10000\-20000
         workgroup = DOMAIN
         security = domain
         password server = *
 .fi
 .PP
 Now start winbindd and you should find that your user and group database is expanded to include your NT users and groups, and that you can login to your unix box as a domain user, using the DOMAIN+user syntax for the username. You may wish to use the commands
+.RE
+.PP
+Now start winbindd and you should find that your user and group database is expanded to include your NT users and groups, and that you can login to your unix box as a domain user, using the DOMAIN+user syntax for the username\. You may wish to use the commands
 getent passwd
 and
 getent group
 to confirm the correct operation of winbindd.
+to confirm the correct operation of winbindd\.
 .SH "NOTES"
 .PP
 …
 must be running on the local machine for
 winbindd
 to work.
 .PP
 PAM is really easy to misconfigure. Make sure you know what you are doing when modifying PAM configuration files. It is possible to set up PAM such that you can no longer log into your system.
+to work\.
+.PP
+PAM is really easy to misconfigure\. Make sure you know what you are doing when modifying PAM configuration files\. It is possible to set up PAM such that you can no longer log into your system\.
 .PP
 If more than one UNIX machine is running
 winbindd, then in general the user and groups ids allocated by winbindd will not be the same. The user and group ids will only be valid for the local machine, unless a shared
 is configured.
 .PP
 If the the Windows NT SID to UNIX user and group id mapping file is damaged or destroyed then the mappings will be lost.
+winbindd, then in general the user and groups ids allocated by winbindd will not be the same\. The user and group ids will only be valid for the local machine, unless a shared
+\fIidmap backend\fR
+is configured\.
+.PP
+If the the Windows NT SID to UNIX user and group id mapping file is damaged or destroyed then the mappings will be lost\.
 .SH "SIGNALS"
 .PP
 The following signals can be used to manipulate the
 winbindd
 daemon.
+daemon\.
 .PP
 SIGHUP
 .RS 3n
+.RS 4
 Reload the
 \fBsmb.conf\fR(5)
 file and apply any parameter changes to the running version of winbindd. This signal also clears any cached user and group information. The list of other domains trusted by winbindd is also reloaded.
+file and apply any parameter changes to the running version of winbindd\. This signal also clears any cached user and group information\. The list of other domains trusted by winbindd is also reloaded\.
 .RE
 .PP
 SIGUSR2
 .RS 3n
+.RS 4
 The SIGUSR2 signal will cause
 winbindd
 to write status information to the winbind log file.
 .sp
 Log files are stored in the filename specified by the log file parameter.
+to write status information to the winbind log file\.
+.sp
+Log files are stored in the filename specified by the log file parameter\.
 .RE
 .SH "FILES"
 .PP
 \fI/etc/nsswitch.conf(5)\fR
 .RS 3n
 Name service switch configuration file.
 .RE
 .PP
 /tmp/.winbindd/pipe
 .RS 3n
+\fI/etc/nsswitch\.conf(5)\fR
+.RS 4
+Name service switch configuration file\.
+.RE
+.PP
+/tmp/\.winbindd/pipe
+.RS 4
 The UNIX pipe over which clients communicate with the
 winbindd
 program. For security reasons, the winbind client will only attempt to connect to the winbindd daemon if both the
 \fI/tmp/.winbindd\fR
+program\. For security reasons, the winbind client will only attempt to connect to the winbindd daemon if both the
+\fI/tmp/\.winbindd\fR
 directory and
 \fI/tmp/.winbindd/pipe\fR
 file are owned by root.
+\fI/tmp/\.winbindd/pipe\fR
+file are owned by root\.
 .RE
 .PP
 $LOCKDIR/winbindd_privileged/pipe
 .RS 3n
 The UNIX pipe over which 'privileged' clients communicate with the
 winbindd
 program. For security reasons, access to some winbindd functions - like those needed by the
+.RS 4
+The UNIX pipe over which \'privileged\' clients communicate with the
+winbindd
+program\. For security reasons, access to some winbindd functions \- like those needed by the
 ntlm_auth
 utility - is restricted. By default, only users in the 'root' group will get this access, however the administrator may change the group permissions on $LOCKDIR/winbindd_privileged to allow programs like 'squid' to use ntlm_auth. Note that the winbind client will only attempt to connect to the winbindd daemon if both the
+utility \- is restricted\. By default, only users in the \'root\' group will get this access, however the administrator may change the group permissions on $LOCKDIR/winbindd_privileged to allow programs like \'squid\' to use ntlm_auth\. Note that the winbind client will only attempt to connect to the winbindd daemon if both the
 \fI$LOCKDIR/winbindd_privileged\fR
 directory and
 \fI$LOCKDIR/winbindd_privileged/pipe\fR
 file are owned by root.
 .RE
 .PP
 /lib/libnss_winbind.so.X
 .RS 3n
 Implementation of name service switch library.
 .RE
 .PP
 $LOCKDIR/winbindd_idmap.tdb
 .RS 3n
 Storage for the Windows NT rid to UNIX user/group id mapping. The lock directory is specified when Samba is initially compiled using the
 \fI--with-lockdir\fR
 option. This directory is by default
 \fI/usr/local/samba/var/locks \fR.
 .RE
 .PP
 $LOCKDIR/winbindd_cache.tdb
 .RS 3n
 Storage for cached user and group information.
+file are owned by root\.
+.RE
+.PP
+/lib/libnss_winbind\.so\.X
+.RS 4
+Implementation of name service switch library\.
+.RE
+.PP
+$LOCKDIR/winbindd_idmap\.tdb
+.RS 4
+Storage for the Windows NT rid to UNIX user/group id mapping\. The lock directory is specified when Samba is initially compiled using the
+\fI\-\-with\-lockdir\fR
+option\. This directory is by default
+\fI/usr/local/samba/var/locks \fR\.
+.RE
+.PP
+$LOCKDIR/winbindd_cache\.tdb
+.RS 4
+Storage for cached user and group information\.
 .RE
 .SH "VERSION"
 .PP
 This man page is correct for version 3.0 of the Samba suite.
+This man page is correct for version 3\.0 of the Samba suite\.
 .SH "SEE ALSO"
 .PP
 \fInsswitch.conf(5)\fR,
+\fInsswitch\.conf(5)\fR,
 \fBsamba\fR(7),
 \fBwbinfo\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.
+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
 wbinfo
 and
 winbindd
+were written by Tim Potter.
+.PP
+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.
+were written by Tim Potter\.
+.PP
+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\.

Context Navigation

Legend:

Download in other formats: