Context Navigation

← Previous Change
Next Change →

winbindd.8

Timestamp:

May 23, 2008, 6:56:41 AM (17 years ago)

Author:

Paul Smedley

Message:

Update source to 3.0.29

File:

: 1 edited

branches/samba-3.0/docs/manpages/winbindd.8 (modified) (10 diffs)

Legend:

: Unmodified
: Added
: Removed

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\.

Note: See TracChangeset for help on using the changeset viewer.

Context Navigation

Changeset 134 for branches/samba-3.0/docs/manpages/winbindd.8

Legend:

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

Download in other formats: