Ignore:
Timestamp:
May 23, 2008, 6:56:41 AM (17 years ago)
Author:
Paul Smedley
Message:

Update source to 3.0.29

File:
1 edited

Legend:

Unmodified
Added
Removed

  • branches/samba-3.0/docs/htmldocs/manpages/winbindd.8.html

    r44 r134  
    1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>winbindd</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.71.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="winbindd.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>winbindd &#8212; Name Service Switch daemon for resolving names
    2         from NT servers</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">winbindd</code> [-F] [-S] [-i] [-Y] [-d &lt;debug level&gt;] [-s &lt;smb config file&gt;] [-n]</p></div></div><div class="refsect1" lang="en"><a name="id259558"></a><h2>DESCRIPTION</h2><p>This program is part of the <a href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">winbindd</code> is a daemon that provides
     1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>winbindd</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.73.2"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="winbindd.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>winbindd &#8212; Name Service Switch daemon for resolving names
     2        from NT servers</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">winbindd</code> [-D] [-F] [-S] [-i] [-Y] [-d &lt;debug level&gt;] [-s &lt;smb config file&gt;] [-n]</p></div></div><div class="refsect1" lang="en"><a name="id282746"></a><h2>DESCRIPTION</h2><p>This program is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">winbindd</code> is a daemon that provides
    33        a number of services to the Name Service Switch capability found
    4         in most modern C libraries, to arbitary applications via PAM
     4        in most modern C libraries, to arbitrary applications via PAM
    55        and <code class="literal">ntlm_auth</code> and to Samba itself.</p><p>Even if winbind is not used for nsswitch, it still provides a
    66        service to <code class="literal">smbd</code>, <code class="literal">ntlm_auth</code>
    77        and the <code class="literal">pam_winbind.so</code> PAM module, by managing connections to
    88        domain controllers.  In this configuraiton the
    9         <a class="indexterm" name="id259361"></a>idmap uid and
    10         <a class="indexterm" name="id259368"></a>idmap gid
    11         parameters are not required. (This is known as `netlogon proxy only mode'.)</p><p> The Name Service Switch allows user 
    12         and system information to be obtained from different databases 
    13         services such as NIS or DNS.  The exact behaviour can be configured 
    14         throught the <code class="filename">/etc/nsswitch.conf</code> file. 
    15         Users and groups are allocated as they are resolved to a range 
    16         of user and group ids specified by the administrator of the 
    17         Samba system.</p><p>The service provided by <code class="literal">winbindd</code> is called `winbind' and 
    18         can be used to resolve user and group information from a 
     9        <a class="link" href="smb.conf.5.html#IDMAPUID">idmap uid</a> and
     10        <a class="link" href="smb.conf.5.html#IDMAPGID">idmap gid</a>
     11        parameters are not required. (This is known as `netlogon proxy only mode'.)</p><p> The Name Service Switch allows user
     12        and system information to be obtained from different databases
     13        services such as NIS or DNS.  The exact behaviour can be configured
     14        throught the <code class="filename">/etc/nsswitch.conf</code> file.
     15        Users and groups are allocated as they are resolved to a range
     16        of user and group ids specified by the administrator of the
     17        Samba system.</p><p>The service provided by <code class="literal">winbindd</code> is called `winbind' and
     18        can be used to resolve user and group information from a
    1919        Windows NT server. The service can also provide authentication
    2020        services via an associated PAM module. </p><p>
    … …  
    2222        <em class="parameter"><code>auth</code></em>, <em class="parameter"><code>account</code></em>
    2323        and <em class="parameter"><code>password</code></em>
    24         module-types.  It should be noted that the 
     24        module-types.  It should be noted that the
    2525        <em class="parameter"><code>account</code></em> module simply performs a getpwnam() to verify that
    2626        the system can obtain a uid for the user, as the domain
    … …  
    2828        <code class="filename">libnss_winbind</code> library has been correctly
    2929        installed, or an alternate source of names configured, this should always succeed.
    30         </p><p>The following nsswitch databases are implemented by
    31         the winbindd service: </p><div class="variablelist"><dl><dt><span class="term">hosts</span></dt><dd><p>This feature is only available on IRIX.
    32                 User information traditionally stored in
    33                 the <code class="filename">hosts(5)</code> file and used by
     30        </p><p>The following nsswitch databases are implemented by
     31        the winbindd service: </p><div class="variablelist"><dl><dt><span class="term">-D</span></dt><dd><p>If specified, this parameter causes
     32                the server to operate as a daemon. That is, it detaches
     33                itself and runs in the background on the appropriate port.
     34                This switch is assumed if <code class="literal">winbindd</code> is
     35                executed on the command line of a shell.
     36                </p></dd><dt><span class="term">hosts</span></dt><dd><p>This feature is only available on IRIX.
     37                User information traditionally stored in
     38                the <code class="filename">hosts(5)</code> file and used by
    3439                <code class="literal">gethostbyname(3)</code> functions. Names are
    3540                resolved through the WINS server or by broadcast.
    36                 </p></dd><dt><span class="term">passwd</span></dt><dd><p>User information traditionally stored in 
    37                 the <code class="filename">passwd(5)</code> file and used by 
    38                 <code class="literal">getpwent(3)</code> functions. </p></dd><dt><span class="term">group</span></dt><dd><p>Group information traditionally stored in 
    39                 the <code class="filename">group(5)</code> file and used by             
     41                </p></dd><dt><span class="term">passwd</span></dt><dd><p>User information traditionally stored in
     42                the <code class="filename">passwd(5)</code> file and used by
     43                <code class="literal">getpwent(3)</code> functions. </p></dd><dt><span class="term">group</span></dt><dd><p>Group information traditionally stored in
     44                the <code class="filename">group(5)</code> file and used by
    4045                <code class="literal">getgrent(3)</code> functions. </p></dd></dl></div><p>For example, the following simple configuration in the
    41         <code class="filename">/etc/nsswitch.conf</code> file can be used to initially 
     46        <code class="filename">/etc/nsswitch.conf</code> file can be used to initially
    4247        resolve user and group information from <code class="filename">/etc/passwd
    43         </code> and <code class="filename">/etc/group</code> and then from the 
     48        </code> and <code class="filename">/etc/group</code> and then from the
    4449        Windows NT server.
    4550</p><pre class="programlisting">
    … …  
    5358        WINS server.</p><pre class="programlisting">
    5459hosts:          files wins
    55 </pre></div><div class="refsect1" lang="en"><a name="id260125"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-F</span></dt><dd><p>If specified, this parameter causes
     60</pre></div><div class="refsect1" lang="en"><a name="id324498"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-F</span></dt><dd><p>If specified, this parameter causes
    5661                the main <code class="literal">winbindd</code> process to not daemonize,
    5762                i.e. double-fork and disassociate with the terminal.
    … …  
    6570                </p></dd><dt><span class="term">-S</span></dt><dd><p>If specified, this parameter causes
    6671                <code class="literal">winbindd</code> to log to standard output rather
    67                 than a file.</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the program version number.
    68 </p></dd><dt><span class="term">-s &lt;configuration file&gt;</span></dt><dd><p>The file specified contains the
    69 configuration details required by the server.  The
    70 information in this file includes server-specific
    71 information such as what printcap file to use, as well
    72 as descriptions of all the services that the server is
    73 to provide. See <code class="filename">smb.conf</code> for more information.
    74 The default configuration file name is determined at
    75 compile time.</p></dd><dt><span class="term">-d|--debuglevel=level</span></dt><dd><p><em class="replaceable"><code>level</code></em> is an integer
    76 from 0 to 10.  The default value if this parameter is
    77 not specified is zero.</p><p>The higher this value, the more detail will be
     72                than a file.</p></dd><dt><span class="term">-d|--debuglevel=level</span></dt><dd><p><em class="replaceable"><code>level</code></em> is an integer
     73from 0 to 10. The default value if this parameter is
     74not specified is 0.</p><p>The higher this value, the more detail will be
    7875logged to the log files about the activities of the
    7976server. At level 0, only critical errors and serious
    … …  
    8582use only by developers and generate HUGE amounts of log
    8683data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
    87 override the <a class="indexterm" name="id300475"></a> parameter
    88 in the <code class="filename">smb.conf</code> file.</p></dd><dt><span class="term">-l|--logfile=logdirectory</span></dt><dd><p>Base directory name for log/debug files. The extension
     84override the <a class="link" href="smb.conf.5.html#LOGLEVEL">log level</a> parameter
     85in the <code class="filename">smb.conf</code> file.</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the program version number.
     86</p></dd><dt><span class="term">-s &lt;configuration file&gt;</span></dt><dd><p>The file specified contains the
     87configuration details required by the server.  The
     88information in this file includes server-specific
     89information such as what printcap file to use, as well
     90as descriptions of all the services that the server is
     91to provide. See <code class="filename">smb.conf</code> for more information.
     92The default configuration file name is determined at
     93compile time.</p></dd><dt><span class="term">-l|--log-basename=logdirectory</span></dt><dd><p>Base directory name for log/debug files. The extension
    8994<code class="constant">".progname"</code> will be appended (e.g. log.smbclient,
    9095log.smbd, etc...). The log file is never removed by the client.
    9196</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
    92 </p></dd><dt><span class="term">-i</span></dt><dd><p>Tells <code class="literal">winbindd</code> to not 
    93                 become a daemon and detach from the current terminal. This 
    94                 option is used by developers when interactive debugging 
     97</p></dd><dt><span class="term">-i</span></dt><dd><p>Tells <code class="literal">winbindd</code> to not
     98                become a daemon and detach from the current terminal. This
     99                option is used by developers when interactive debugging
    95100                of <code class="literal">winbindd</code> is required.
    96101                <code class="literal">winbindd</code> also logs to standard output,
    97102                as if the <code class="literal">-S</code> parameter had been given.
    98                 </p></dd><dt><span class="term">-n</span></dt><dd><p>Disable caching. This means winbindd will 
    99                 always have to wait for a response from the domain controller 
    100                 before it can respond to a client and this thus makes things 
    101                 slower. The results will however be more accurate, since 
    102                 results from the cache might not be up-to-date. This 
     103                </p></dd><dt><span class="term">-n</span></dt><dd><p>Disable caching. This means winbindd will
     104                always have to wait for a response from the domain controller
     105                before it can respond to a client and this thus makes things
     106                slower. The results will however be more accurate, since
     107                results from the cache might not be up-to-date. This
    103108                might also temporarily hang winbindd if the DC doesn't respond.
    104                 </p></dd><dt><span class="term">-Y</span></dt><dd><p>Single daemon mode. This means winbindd will run 
    105                 as a single process (the mode of operation in Samba 2.2).  Winbindd's 
    106                 default behavior is to launch a child process that is responsible for 
     109                </p></dd><dt><span class="term">-Y</span></dt><dd><p>Single daemon mode. This means winbindd will run
     110                as a single process (the mode of operation in Samba 2.2).  Winbindd's
     111                default behavior is to launch a child process that is responsible for
    107112                updating expired cache entries.
    108                 </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id300582"></a><h2>NAME AND ID RESOLUTION</h2><p>Users and groups on a Windows NT server are assigned
    109         a security id (SID) which is globally unique when the 
    110         user or group is created.  To convert the Windows NT user or group 
    111         into a unix user or group, a mapping between SIDs and unix user 
     113                </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id324720"></a><h2>NAME AND ID RESOLUTION</h2><p>Users and groups on a Windows NT server are assigned
     114        a security id (SID) which is globally unique when the
     115        user or group is created.  To convert the Windows NT user or group
     116        into a unix user or group, a mapping between SIDs and unix user
    112117        and group ids is required.  This is one of the jobs that <code class="literal">
    113         winbindd</code> performs. </p><p>As winbindd users and groups are resolved from a server, user 
     118        winbindd</code> performs. </p><p>As winbindd users and groups are resolved from a server, user
    114119        and group ids are allocated from a specified range.  This
    115         is done on a first come, first served basis, although all existing 
    116         users and groups will be mapped as soon as a client performs a user 
    117         or group enumeration command.  The allocated unix ids are stored 
    118         in a database and will be remembered. </p><p>WARNING: The SID to unix id database is the only location 
    119         where the user and group mappings are stored by winbindd.  If this 
    120         store is deleted or corrupted, there is no way for winbindd to 
    121         determine which user and group ids correspond to Windows NT user 
    122         and group rids. </p><p>See the <a class="indexterm" name="id300614"></a> or the old <a class="indexterm" name="id300619"></a> parameters in
     120        is done on a first come, first served basis, although all existing
     121        users and groups will be mapped as soon as a client performs a user
     122        or group enumeration command.  The allocated unix ids are stored
     123        in a database and will be remembered. </p><p>WARNING: The SID to unix id database is the only location
     124        where the user and group mappings are stored by winbindd.  If this
     125        store is deleted or corrupted, there is no way for winbindd to
     126        determine which user and group ids correspond to Windows NT user
     127        and group rids. </p><p>See the <a class="link" href="smb.conf.5.html#IDMAPDOMAINS">idmap domains</a> or the old <a class="link" href="smb.conf.5.html#IDMAPBACKEND">idmap backend</a> parameters in
    123128        <code class="filename">smb.conf</code> for options for sharing this
    124         database, such as via LDAP.</p></div><div class="refsect1" lang="en"><a name="id300634"></a><h2>CONFIGURATION</h2><p>Configuration of the <code class="literal">winbindd</code> daemon
    125         is done through configuration parameters in the <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> file.  All parameters should be specified in the
     129        database, such as via LDAP.</p></div><div class="refsect1" lang="en"><a name="id324773"></a><h2>CONFIGURATION</h2><p>Configuration of the <code class="literal">winbindd</code> daemon
     130        is done through configuration parameters in the <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> file.  All parameters should be specified in the
    126131        [global] section of smb.conf. </p><div class="itemizedlist"><ul type="disc"><li><p>
    127                 <a class="indexterm" name="id300664"></a>winbind separator</p></li><li><p>
    128                 <a class="indexterm" name="id300675"></a>idmap uid</p></li><li><p>
    129                 <a class="indexterm" name="id300687"></a>idmap gid</p></li><li><p>
    130                 <a class="indexterm" name="id300698"></a>idmap backend</p></li><li><p>
    131                 <a class="indexterm" name="id300709"></a>winbind cache time</p></li><li><p>
    132                 <a class="indexterm" name="id300721"></a>winbind enum users</p></li><li><p>
    133                 <a class="indexterm" name="id300732"></a>winbind enum groups</p></li><li><p>
    134                 <a class="indexterm" name="id300743"></a>template homedir</p></li><li><p>
    135                 <a class="indexterm" name="id300755"></a>template shell</p></li><li><p>
    136                 <a class="indexterm" name="id300766"></a>winbind use default domain</p></li><li><p>
    137                 <a class="indexterm" name="id300778"></a>winbind: rpc only
     132                <a class="link" href="smb.conf.5.html#WINBINDSEPARATOR">winbind separator</a></p></li><li><p>
     133                <a class="link" href="smb.conf.5.html#IDMAPUID">idmap uid</a></p></li><li><p>
     134                <a class="link" href="smb.conf.5.html#IDMAPGID">idmap gid</a></p></li><li><p>
     135                <a class="link" href="smb.conf.5.html#IDMAPBACKEND">idmap backend</a></p></li><li><p>
     136                <a class="link" href="smb.conf.5.html#WINBINDCACHETIME">winbind cache time</a></p></li><li><p>
     137                <a class="link" href="smb.conf.5.html#WINBINDENUMUSERS">winbind enum users</a></p></li><li><p>
     138                <a class="link" href="smb.conf.5.html#WINBINDENUMGROUPS">winbind enum groups</a></p></li><li><p>
     139                <a class="link" href="smb.conf.5.html#TEMPLATEHOMEDIR">template homedir</a></p></li><li><p>
     140                <a class="link" href="smb.conf.5.html#TEMPLATESHELL">template shell</a></p></li><li><p>
     141                <a class="link" href="smb.conf.5.html#WINBINDUSEDEFAULTDOMAIN">winbind use default domain</a></p></li><li><p>
     142                <a class="link" href="smb.conf.5.html#WINBIND:RPCONLY">winbind: rpc only</a>
    138143                Setting this parameter forces winbindd to use RPC
    139144                instead of LDAP to retrieve information from Domain
    140145                Controllers.
    141                 </p></li></ul></div></div><div class="refsect1" lang="en"><a name="id300789"></a><h2>EXAMPLE SETUP</h2><p>
    142         To setup winbindd for user and group lookups plus 
    143         authentication from a domain controller use something like the 
     146                </p></li></ul></div></div><div class="refsect1" lang="en"><a name="id324918"></a><h2>EXAMPLE SETUP</h2><p>
     147        To setup winbindd for user and group lookups plus
     148        authentication from a domain controller use something like the
    144149        following setup. This was tested on an early Red Hat Linux box.
    145         </p><p>In <code class="filename">/etc/nsswitch.conf</code> put the 
     150        </p><p>In <code class="filename">/etc/nsswitch.conf</code> put the
    146151        following:
    147152</p><pre class="programlisting">
    … …  
    163168        </p></div><p>Note in particular the use of the <em class="parameter"><code>sufficient
    164169        </code></em> keyword and the <em class="parameter"><code>use_first_pass</code></em> keyword. </p><p>Now replace the account lines with this: </p><p><code class="literal">account    required   /lib/security/pam_winbind.so
    165         </code></p><p>The next step is to join the domain. To do that use the 
     170        </code></p><p>The next step is to join the domain. To do that use the
    166171        <code class="literal">net</code> program like this:  </p><p><code class="literal">net join -S PDC -U Administrator</code></p><p>The username after the <em class="parameter"><code>-U</code></em> can be any
    167172        Domain user that has administrator privileges on the machine.
    168         Substitute the name or IP of your PDC for "PDC".</p><p>Next copy <code class="filename">libnss_winbind.so</code> to 
     173        Substitute the name or IP of your PDC for "PDC".</p><p>Next copy <code class="filename">libnss_winbind.so</code> to
    169174        <code class="filename">/lib</code> and <code class="filename">pam_winbind.so
    170175        </code> to <code class="filename">/lib/security</code>.  A symbolic link needs to be
    … …  
    172177        <code class="filename">/lib/libnss_winbind.so.2</code>.  If you are using an
    173178        older version of glibc then the target of the link should be
    174         <code class="filename">/lib/libnss_winbind.so.1</code>.</p><p>Finally, setup a <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> containing directives like the
     179        <code class="filename">/lib/libnss_winbind.so.1</code>.</p><p>Finally, setup a <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> containing directives like the
    175180        following:
    176181</p><pre class="programlisting">
    … …  
    185190        security = domain
    186191        password server = *
    187 </pre><p>Now start winbindd and you should find that your user and 
    188         group database is expanded to include your NT users and groups, 
    189         and that you can login to your unix box as a domain user, using 
    190         the DOMAIN+user syntax for the username. You may wish to use the 
     192</pre><p>Now start winbindd and you should find that your user and
     193        group database is expanded to include your NT users and groups,
     194        and that you can login to your unix box as a domain user, using
     195        the DOMAIN+user syntax for the username. You may wish to use the
    191196        commands <code class="literal">getent passwd</code> and <code class="literal">getent group
    192         </code> to confirm the correct operation of winbindd.</p></div><div class="refsect1" lang="en"><a name="id300980"></a><h2>NOTES</h2><p>The following notes are useful when configuring and
    193         running <code class="literal">winbindd</code>: </p><p><a href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> must be running on the local machine
    194         for <code class="literal">winbindd</code> to work. </p><p>PAM is really easy to misconfigure.  Make sure you know what 
    195         you are doing when modifying PAM configuration files.  It is possible 
    196         to set up PAM such that you can no longer log into your system. </p><p>If more than one UNIX machine is running <code class="literal">winbindd</code>, 
    197         then in general the user and groups ids allocated by winbindd will not 
    198         be the same.  The user and group ids will only be valid for the local 
    199         machine, unless a shared <a class="indexterm" name="id301027"></a> is configured.</p><p>If the the Windows NT SID to UNIX user and group id mapping
    200         file is damaged or destroyed then the mappings will be lost. </p></div><div class="refsect1" lang="en"><a name="id301040"></a><h2>SIGNALS</h2><p>The following signals can be used to manipulate the
    201         <code class="literal">winbindd</code> daemon. </p><div class="variablelist"><dl><dt><span class="term">SIGHUP</span></dt><dd><p>Reload the <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> file and
    202                 apply any parameter changes to the running 
    203                 version of winbindd.  This signal also clears any cached 
    204                 user and group information.  The list of other domains trusted 
     197        </code> to confirm the correct operation of winbindd.</p></div><div class="refsect1" lang="en"><a name="id325091"></a><h2>NOTES</h2><p>The following notes are useful when configuring and
     198        running <code class="literal">winbindd</code>: </p><p><a class="citerefentry" href="nmbd.8.html"><span class="citerefentry"><span class="refentrytitle">nmbd</span>(8)</span></a> must be running on the local machine
     199        for <code class="literal">winbindd</code> to work. </p><p>PAM is really easy to misconfigure.  Make sure you know what
     200        you are doing when modifying PAM configuration files.  It is possible
     201        to set up PAM such that you can no longer log into your system. </p><p>If more than one UNIX machine is running <code class="literal">winbindd</code>,
     202        then in general the user and groups ids allocated by winbindd will not
     203        be the same.  The user and group ids will only be valid for the local
     204        machine, unless a shared <a class="link" href="smb.conf.5.html#IDMAPBACKEND">idmap backend</a> is configured.</p><p>If the the Windows NT SID to UNIX user and group id mapping
     205        file is damaged or destroyed then the mappings will be lost. </p></div><div class="refsect1" lang="en"><a name="id325147"></a><h2>SIGNALS</h2><p>The following signals can be used to manipulate the
     206        <code class="literal">winbindd</code> daemon. </p><div class="variablelist"><dl><dt><span class="term">SIGHUP</span></dt><dd><p>Reload the <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a> file and
     207                apply any parameter changes to the running
     208                version of winbindd.  This signal also clears any cached
     209                user and group information.  The list of other domains trusted
    205210                by winbindd is also reloaded.  </p></dd><dt><span class="term">SIGUSR2</span></dt><dd><p>The SIGUSR2 signal will cause <code class="literal">
    206                 winbindd</code> to write status information to the winbind 
    207                 log file.</p><p>Log files are stored in the filename specified by the 
    208                 log file parameter.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id301102"></a><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><code class="filename">/etc/nsswitch.conf(5)</code></span></dt><dd><p>Name service switch configuration file.</p></dd><dt><span class="term">/tmp/.winbindd/pipe</span></dt><dd><p>The UNIX pipe over which clients communicate with
    209                 the <code class="literal">winbindd</code> program.  For security reasons, the 
    210                 winbind client will only attempt to connect to the winbindd daemon 
     211                winbindd</code> to write status information to the winbind
     212                log file.</p><p>Log files are stored in the filename specified by the
     213                log file parameter.</p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id325205"></a><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><code class="filename">/etc/nsswitch.conf(5)</code></span></dt><dd><p>Name service switch configuration file.</p></dd><dt><span class="term">/tmp/.winbindd/pipe</span></dt><dd><p>The UNIX pipe over which clients communicate with
     214                the <code class="literal">winbindd</code> program.  For security reasons, the
     215                winbind client will only attempt to connect to the winbindd daemon
    211216                if both the <code class="filename">/tmp/.winbindd</code> directory
    212                 and <code class="filename">/tmp/.winbindd/pipe</code> file are owned by 
    213                 root. </p></dd><dt><span class="term">$LOCKDIR/winbindd_privileged/pipe</span></dt><dd><p>The UNIX pipe over which 'privileged' clients 
    214                 communicate with the <code class="literal">winbindd</code> program.  For security 
    215                 reasons, access to some winbindd functions - like those needed by 
     217                and <code class="filename">/tmp/.winbindd/pipe</code> file are owned by
     218                root. </p></dd><dt><span class="term">$LOCKDIR/winbindd_privileged/pipe</span></dt><dd><p>The UNIX pipe over which 'privileged' clients
     219                communicate with the <code class="literal">winbindd</code> program.  For security
     220                reasons, access to some winbindd functions - like those needed by
    216221                the <code class="literal">ntlm_auth</code> utility - is restricted.  By default,
    217222                only users in the 'root' group will get this access, however the administrator
    218223                may change the group permissions on $LOCKDIR/winbindd_privileged to allow
    219224                programs like 'squid' to use ntlm_auth.
    220                 Note that the winbind client will only attempt to connect to the winbindd daemon 
     225                Note that the winbind client will only attempt to connect to the winbindd daemon
    221226                if both the <code class="filename">$LOCKDIR/winbindd_privileged</code> directory
    222                 and <code class="filename">$LOCKDIR/winbindd_privileged/pipe</code> file are owned by 
     227                and <code class="filename">$LOCKDIR/winbindd_privileged/pipe</code> file are owned by
    223228                root. </p></dd><dt><span class="term">/lib/libnss_winbind.so.X</span></dt><dd><p>Implementation of name service switch library.
    224                 </p></dd><dt><span class="term">$LOCKDIR/winbindd_idmap.tdb</span></dt><dd><p>Storage for the Windows NT rid to UNIX user/group 
    225                 id mapping.  The lock directory is specified when Samba is initially 
     229                </p></dd><dt><span class="term">$LOCKDIR/winbindd_idmap.tdb</span></dt><dd><p>Storage for the Windows NT rid to UNIX user/group
     230                id mapping.  The lock directory is specified when Samba is initially
    226231                compiled using the <em class="parameter"><code>--with-lockdir</code></em> option.
    227232                This directory is by default <code class="filename">/usr/local/samba/var/locks
    228233                </code>. </p></dd><dt><span class="term">$LOCKDIR/winbindd_cache.tdb</span></dt><dd><p>Storage for cached user and group information.
    229                 </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id301246"></a><h2>VERSION</h2><p>This man page is correct for version 3.0 of
    230         the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id301257"></a><h2>SEE ALSO</h2><p><code class="filename">nsswitch.conf(5)</code>, <a href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a>, <a href="wbinfo.1.html"><span class="citerefentry"><span class="refentrytitle">wbinfo</span>(1)</span></a>, <a href="ntlm_auth.8.html"><span class="citerefentry"><span class="refentrytitle">ntlm_auth</span>(8)</span></a>, <a href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>, <a href="pam_winbind.8.html"><span class="citerefentry"><span class="refentrytitle">pam_winbind</span>(8)</span></a></p></div><div class="refsect1" lang="en"><a name="id301314"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
     234                </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id325338"></a><h2>VERSION</h2><p>This man page is correct for version 3.0 of
     235        the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id325349"></a><h2>SEE ALSO</h2><p><code class="filename">nsswitch.conf(5)</code>, <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a>, <a class="citerefentry" href="wbinfo.1.html"><span class="citerefentry"><span class="refentrytitle">wbinfo</span>(1)</span></a>, <a class="citerefentry" href="ntlm_auth.8.html"><span class="citerefentry"><span class="refentrytitle">ntlm_auth</span>(8)</span></a>, <a class="citerefentry" href="smb.conf.5.html"><span class="citerefentry"><span class="refentrytitle">smb.conf</span>(5)</span></a>, <a class="citerefentry" href="pam_winbind.8.html"><span class="citerefentry"><span class="refentrytitle">pam_winbind</span>(8)</span></a></p></div><div class="refsect1" lang="en"><a name="id325404"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities
    231236        were created by Andrew Tridgell. Samba is now developed
    232         by the Samba Team as an Open Source project similar 
    233         to the way the Linux kernel is developed.</p><p><code class="literal">wbinfo</code> and <code class="literal">winbindd</code> were 
    234         written by Tim Potter.</p><p>The conversion to DocBook for Samba 2.2 was done 
     237        by the Samba Team as an Open Source project similar
     238        to the way the Linux kernel is developed.</p><p><code class="literal">wbinfo</code> and <code class="literal">winbindd</code> were
     239        written by Tim Potter.</p><p>The conversion to DocBook for Samba 2.2 was done
    235240        by Gerald Carter. The conversion to DocBook XML 4.2 for
    236241        Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
Note: See TracChangeset for help on using the changeset viewer.