summaryrefslogtreecommitdiffstats
path: root/docs/htmldocs
diff options
context:
space:
mode:
Diffstat (limited to 'docs/htmldocs')
-rw-r--r--docs/htmldocs/Samba-HOWTO-Collection.html1108
-rw-r--r--docs/htmldocs/nmbd.8.html23
-rw-r--r--docs/htmldocs/rpcclient.1.html2
-rw-r--r--docs/htmldocs/smb.conf.5.html177
-rw-r--r--docs/htmldocs/smbd.8.html47
-rw-r--r--docs/htmldocs/winbind.html28
-rw-r--r--docs/htmldocs/winbindd.8.html44
7 files changed, 702 insertions, 727 deletions
diff --git a/docs/htmldocs/Samba-HOWTO-Collection.html b/docs/htmldocs/Samba-HOWTO-Collection.html
index a7f23ace5ba..988766d5340 100644
--- a/docs/htmldocs/Samba-HOWTO-Collection.html
+++ b/docs/htmldocs/Samba-HOWTO-Collection.html
@@ -558,101 +558,96 @@ HREF="#AEN1098"
></DT
><DT
>8.3. <A
-HREF="#AEN1137"
+HREF="#AEN1140"
>Configuring the Samba Domain Controller</A
></DT
><DT
>8.4. <A
-HREF="#AEN1180"
->Creating Machine Trust Accounts and Joining Clients to the
-Domain</A
+HREF="#AEN1182"
+>Creating Machine Trust Accounts and Joining Clients
+to the Domain</A
></DT
><DD
><DL
><DT
>8.4.1. <A
-HREF="#AEN1199"
->Manual Creation of Machine Trust Accounts</A
+HREF="#AEN1196"
+>Manually creating machine trust accounts</A
></DT
><DT
>8.4.2. <A
-HREF="#AEN1234"
->"On-the-Fly" Creation of Machine Trust Accounts</A
-></DT
-><DT
->8.4.3. <A
-HREF="#AEN1243"
->Joining the Client to the Domain</A
+HREF="#AEN1227"
+>Creating machine trust accounts "on the fly"</A
></DT
></DL
></DD
><DT
>8.5. <A
-HREF="#AEN1258"
+HREF="#AEN1238"
>Common Problems and Errors</A
></DT
><DT
>8.6. <A
-HREF="#AEN1306"
+HREF="#AEN1286"
>System Policies and Profiles</A
></DT
><DT
>8.7. <A
-HREF="#AEN1350"
->What other help can I get?</A
+HREF="#AEN1330"
+>What other help can I get ?</A
></DT
><DT
>8.8. <A
-HREF="#AEN1464"
+HREF="#AEN1444"
>Domain Control for Windows 9x/ME</A
></DT
><DD
><DL
><DT
>8.8.1. <A
-HREF="#AEN1490"
+HREF="#AEN1474"
>Configuration Instructions: Network Logons</A
></DT
><DT
>8.8.2. <A
-HREF="#AEN1509"
+HREF="#AEN1508"
>Configuration Instructions: Setting up Roaming User Profiles</A
></DT
><DD
><DL
><DT
>8.8.2.1. <A
-HREF="#AEN1517"
+HREF="#AEN1516"
>Windows NT Configuration</A
></DT
><DT
>8.8.2.2. <A
-HREF="#AEN1525"
+HREF="#AEN1524"
>Windows 9X Configuration</A
></DT
><DT
>8.8.2.3. <A
-HREF="#AEN1533"
+HREF="#AEN1532"
>Win9X and WinNT Configuration</A
></DT
><DT
>8.8.2.4. <A
-HREF="#AEN1540"
+HREF="#AEN1539"
>Windows 9X Profile Setup</A
></DT
><DT
>8.8.2.5. <A
-HREF="#AEN1576"
+HREF="#AEN1575"
>Windows NT Workstation 4.0</A
></DT
><DT
>8.8.2.6. <A
-HREF="#AEN1589"
+HREF="#AEN1588"
>Windows NT Server</A
></DT
><DT
>8.8.2.7. <A
-HREF="#AEN1592"
+HREF="#AEN1591"
>Sharing Profiles between W95 and NT Workstation 4.0</A
></DT
></DL
@@ -661,7 +656,7 @@ HREF="#AEN1592"
></DD
><DT
>8.9. <A
-HREF="#AEN1602"
+HREF="#AEN1601"
>DOMAIN_CONTROL.txt : Windows NT Domain Control &#38; Samba</A
></DT
></DL
@@ -675,126 +670,119 @@ HREF="#WINBIND"
><DL
><DT
>9.1. <A
-HREF="#AEN1652"
+HREF="#AEN1644"
>Abstract</A
></DT
><DT
>9.2. <A
-HREF="#AEN1656"
+HREF="#AEN1648"
>Introduction</A
></DT
><DT
>9.3. <A
-HREF="#AEN1669"
+HREF="#AEN1661"
>What Winbind Provides</A
></DT
><DD
><DL
><DT
>9.3.1. <A
-HREF="#AEN1676"
+HREF="#AEN1668"
>Target Uses</A
></DT
></DL
></DD
><DT
>9.4. <A
-HREF="#AEN1680"
+HREF="#AEN1672"
>How Winbind Works</A
></DT
><DD
><DL
><DT
>9.4.1. <A
-HREF="#AEN1685"
+HREF="#AEN1677"
>Microsoft Remote Procedure Calls</A
></DT
><DT
>9.4.2. <A
-HREF="#AEN1689"
+HREF="#AEN1681"
>Name Service Switch</A
></DT
><DT
>9.4.3. <A
-HREF="#AEN1705"
+HREF="#AEN1697"
>Pluggable Authentication Modules</A
></DT
><DT
>9.4.4. <A
-HREF="#AEN1713"
+HREF="#AEN1705"
>User and Group ID Allocation</A
></DT
><DT
>9.4.5. <A
-HREF="#AEN1717"
+HREF="#AEN1709"
>Result Caching</A
></DT
></DL
></DD
><DT
>9.5. <A
-HREF="#AEN1720"
+HREF="#AEN1712"
>Installation and Configuration</A
></DT
><DD
><DL
><DT
>9.5.1. <A
-HREF="#AEN1725"
+HREF="#AEN1717"
>Introduction</A
></DT
><DT
>9.5.2. <A
-HREF="#AEN1738"
+HREF="#AEN1730"
>Requirements</A
></DT
><DT
>9.5.3. <A
-HREF="#AEN1752"
+HREF="#AEN1738"
>Testing Things Out</A
></DT
><DD
><DL
><DT
>9.5.3.1. <A
-HREF="#AEN1763"
+HREF="#AEN1747"
>Configure and compile SAMBA</A
></DT
><DT
>9.5.3.2. <A
-HREF="#AEN1782"
->Configure <TT
-CLASS="FILENAME"
->nsswitch.conf</TT
-> and the
-winbind libraries</A
+HREF="#AEN1759"
+>Configure nsswitch.conf and the winbind libraries</A
></DT
><DT
>9.5.3.3. <A
-HREF="#AEN1807"
+HREF="#AEN1778"
>Configure smb.conf</A
></DT
><DT
>9.5.3.4. <A
-HREF="#AEN1823"
+HREF="#AEN1787"
>Join the SAMBA server to the PDC domain</A
></DT
><DT
>9.5.3.5. <A
-HREF="#AEN1834"
+HREF="#AEN1797"
>Start up the winbindd daemon and test it!</A
></DT
><DT
>9.5.3.6. <A
-HREF="#AEN1870"
->Fix the <TT
-CLASS="FILENAME"
->/etc/rc.d/init.d/smb</TT
-> startup files</A
+HREF="#AEN1824"
+>Fix the /etc/rc.d/init.d/smb startup files</A
></DT
><DT
>9.5.3.7. <A
-HREF="#AEN1892"
+HREF="#AEN1841"
>Configure Winbind and PAM</A
></DT
></DL
@@ -803,12 +791,12 @@ HREF="#AEN1892"
></DD
><DT
>9.6. <A
-HREF="#AEN1939"
+HREF="#AEN1882"
>Limitations</A
></DT
><DT
>9.7. <A
-HREF="#AEN1949"
+HREF="#AEN1892"
>Conclusion</A
></DT
></DL
@@ -822,32 +810,32 @@ HREF="#OS2"
><DL
><DT
>10.1. <A
-HREF="#AEN1963"
+HREF="#AEN1906"
>FAQs</A
></DT
><DD
><DL
><DT
>10.1.1. <A
-HREF="#AEN1965"
+HREF="#AEN1908"
>How can I configure OS/2 Warp Connect or
OS/2 Warp 4 as a client for Samba?</A
></DT
><DT
>10.1.2. <A
-HREF="#AEN1980"
+HREF="#AEN1923"
>How can I configure OS/2 Warp 3 (not Connect),
OS/2 1.2, 1.3 or 2.x for Samba?</A
></DT
><DT
>10.1.3. <A
-HREF="#AEN1989"
+HREF="#AEN1932"
>Are there any other issues when OS/2 (any version)
is used as a client?</A
></DT
><DT
>10.1.4. <A
-HREF="#AEN1993"
+HREF="#AEN1936"
>How do I get printer driver download working
for OS/2 clients?</A
></DT
@@ -864,24 +852,24 @@ HREF="#CVS-ACCESS"
><DL
><DT
>11.1. <A
-HREF="#AEN2009"
+HREF="#AEN1952"
>Introduction</A
></DT
><DT
>11.2. <A
-HREF="#AEN2014"
+HREF="#AEN1957"
>CVS Access to samba.org</A
></DT
><DD
><DL
><DT
>11.2.1. <A
-HREF="#AEN2017"
+HREF="#AEN1960"
>Access via CVSweb</A
></DT
><DT
>11.2.2. <A
-HREF="#AEN2022"
+HREF="#AEN1965"
>Access via cvs</A
></DT
></DL
@@ -890,7 +878,7 @@ HREF="#AEN2022"
></DD
><DT
><A
-HREF="#AEN2050"
+HREF="#AEN1993"
>Index</A
></DT
></DL
@@ -5577,33 +5565,32 @@ CLASS="NOTE"
><B
>Note: </B
><EM
->Author's Note:</EM
+>Author's Note :</EM
> This document is a combination
-of David Bannon's "Samba 2.2 PDC HOWTO" and "Samba NT Domain FAQ".
+of David Bannon's Samba 2.2 PDC HOWTO and the Samba NT Domain FAQ.
Both documents are superseded by this one.</P
></BLOCKQUOTE
></DIV
><P
->Versions of Samba prior to release 2.2 had marginal capabilities to act
-as a Windows NT 4.0 Primary Domain Controller
-
-(PDC). With Samba 2.2.0, we are proud to announce official support for
-Windows NT 4.0-style domain logons from Windows NT 4.0 and Windows
-2000 clients. This article outlines the steps
-necessary for configuring Samba as a PDC. It is necessary to have a
-working Samba server prior to implementing the PDC functionality. If
-you have not followed the steps outlined in <A
+>Version of Samba prior to release 2.2 had marginal capabilities to
+act as a Windows NT 4.0 Primary DOmain Controller (PDC). Beginning with
+Samba 2.2.0, we are proud to announce official support for Windows NT 4.0
+style domain logons from Windows NT 4.0 (through SP6) and Windows 2000 (through
+SP1) clients. This article outlines the steps necessary for configuring Samba
+as a PDC. It is necessary to have a working Samba server prior to implementing the
+PDC functionality. If you have not followed the steps outlined in
+<A
HREF="UNIX_INSTALL.html"
TARGET="_top"
> UNIX_INSTALL.html</A
->, please make sure
-that your server is configured correctly before proceeding. Another
-good resource in the <A
+>, please make sure
+that your server is configured correctly before proceeding. Another good
+resource in the <A
HREF="smb.conf.5.html"
TARGET="_top"
->smb.conf(5) man
+>smb.conf(5) man
page</A
->. The following functionality should work in 2.2:</P
+>. The following functionality should work in 2.2:</P
><P
></P
><UL
@@ -5630,10 +5617,36 @@ page</A
></LI
><LI
><P
-> Windows NT 4.0-style system policies
+> Windows NT 4.0 style system policies
</P
></LI
></UL
+><DIV
+CLASS="WARNING"
+><P
+></P
+><TABLE
+CLASS="WARNING"
+BORDER="1"
+WIDTH="100%"
+><TR
+><TD
+ALIGN="CENTER"
+><B
+>Windows 2000 Service Pack 2 Clients</B
+></TD
+></TR
+><TR
+><TD
+ALIGN="LEFT"
+><P
+> Samba 2.2.1 is required for PDC functionality when using Windows 2000
+ SP2 clients.
+ </P
+></TD
+></TR
+></TABLE
+></DIV
><P
>The following pieces of functionality are not included in the 2.2 release:</P
><P
@@ -5665,7 +5678,7 @@ page</A
><P
>Please note that Windows 9x clients are not true members of a domain
for reasons outlined in this article. Therefore the protocol for
-support Windows 9x-style domain logons is completely different
+support Windows 9x style domain logons is completely different
from NT4 domain logons and has been officially supported for some
time.</P
><P
@@ -5698,7 +5711,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
-NAME="AEN1137"
+NAME="AEN1140"
>8.3. Configuring the Samba Domain Controller</A
></H1
><P
@@ -5713,10 +5726,7 @@ man page</A
>. For convenience, the parameters have been
linked with the actual smb.conf description.</P
><P
->Here is an example <TT
-CLASS="FILENAME"
->smb.conf</TT
-> for acting as a PDC:</P
+>Here is an example smb.conf for acting as a PDC:</P
><P
><TABLE
BORDER="0"
@@ -5828,10 +5838,10 @@ TARGET="_top"
>path</A
> = /usr/local/samba/lib/netlogon
<A
-HREF="smb.conf.5.html#READONLY"
+HREF="smb.conf.5.html#WRITEABLE"
TARGET="_top"
->read only</A
-> = yes
+>writeable</A
+> = no
<A
HREF="smb.conf.5.html#WRITELIST"
TARGET="_top"
@@ -5851,10 +5861,10 @@ TARGET="_top"
>path</A
> = /export/smb/ntprofile
<A
-HREF="smb.conf.5.html#READONLY"
+HREF="smb.conf.5.html#WRITEABLE"
TARGET="_top"
->read only</A
-> = no
+>writeable</A
+> = yes
<A
HREF="smb.conf.5.html#CREATEMASK"
TARGET="_top"
@@ -5903,89 +5913,72 @@ CLASS="FILENAME"
></LI
></UL
><P
->As Samba 2.2 does not offer a complete implementation of group mapping
-between Windows NT groups and Unix groups (this is really quite
-complicated to explain in a short space), you should refer to the
-<A
+>As Samba 2.2 does not offer a complete implementation of group mapping between
+Windows NT groups and UNIX groups (this is really quite complicated to explain
+in a short space), you should refer to the <A
HREF="smb.conf.5.html#DOMAINADMINGROUP"
TARGET="_top"
->domain admin
-group</A
-> smb.conf parameter for information of creating "Domain
-Admins" style accounts.</P
+>domain
+admin group</A
+> smb.conf parameter for information of creating "Domain Admins"
+style accounts.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
-NAME="AEN1180"
->8.4. Creating Machine Trust Accounts and Joining Clients to the
-Domain</A
+NAME="AEN1182"
+>8.4. Creating Machine Trust Accounts and Joining Clients
+to the Domain</A
></H1
><P
->A machine trust account is a Samba account that is used to
-authenticate a client machine (rather than a user) to the Samba
-server. In Windows terminology, this is known as a "Computer
-Account."</P
-><P
->The password of a machine trust account acts as the shared secret for
-secure communication with the Domain Controller. This is a security
-feature to prevent an unauthorized machine with the same NetBIOS name
-from joining the domain and gaining access to domain user/group
-accounts. Windows NT and 2000 clients use machine trust accounts, but
-Windows 9x clients do not. Hence, a Windows 9x client is never a true
-member of a domain because it does not possess a machine trust
-account, and thus has no shared secret with the domain controller.</P
-><P
->A Windows PDC stores each machine trust account in the Windows
-Registry. A Samba PDC, however, stores each machine trust account
-in two parts, as follows:
-
-<P
-></P
-><UL
-><LI
+>A machine trust account is a samba user account owned by a computer.
+The account password acts as the shared secret for secure
+communication with the Domain Controller. This is a security feature
+to prevent an unauthorized machine with the same NetBIOS name from
+joining the domain and gaining access to domain user/group accounts.
+Hence a Windows 9x host is never a true member of a domain because it does
+not posses a machine trust account, and thus has no shared secret with the DC.</P
><P
->A Samba account, stored in the same location as user
- LanMan and NT password hashes (currently
- <TT
+>On a Windows NT PDC, these machine trust account passwords are stored
+in the registry. A Samba PDC stores these accounts in the same location
+as user LanMan and NT password hashes (currently <TT
CLASS="FILENAME"
>smbpasswd</TT
->). The Samba account
- possesses and uses only the NT password hash.</P
-></LI
-><LI
+>).
+However, machine trust accounts only possess and use the NT password hash.</P
><P
->A corresponding Unix account, typically stored in
- <TT
+>Because Samba requires machine accounts to possess a UNIX uid from
+which an Windows NT SID can be generated, all of these accounts
+must have an entry in <TT
CLASS="FILENAME"
>/etc/passwd</TT
->. (Future releases will alleviate the need to
- create <TT
+> and smbpasswd.
+Future releases will alleviate the need to create
+<TT
CLASS="FILENAME"
>/etc/passwd</TT
-> entries.) </P
-></LI
-></UL
-></P
+> entries. </P
><P
->There are two ways to create machine trust accounts:</P
+>There are two means of creating machine trust accounts.</P
><P
></P
><UL
><LI
><P
-> Manual creation. Both the Samba and corresponding
- Unix account are created by hand.</P
+> Manual creation before joining the client to the domain. In this case,
+ the password is set to a known value -- the lower case of the
+ machine's NetBIOS name.
+ </P
></LI
><LI
><P
-> "On-the-fly" creation. The Samba machine trust
- account is automatically created by Samba at the time the client
- is joined to the domain. (For security, this is the
- recommended method.) The corresponding Unix account may be
- created automatically or manually. </P
+> Creation of the account at the time of joining the domain. In
+ this case, the session key of the administrative account used to join
+ the client to the domain acts as an encryption key for setting the
+ password to a random value (This is the recommended method).
+ </P
></LI
></UL
><DIV
@@ -5993,28 +5986,22 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
-NAME="AEN1199"
->8.4.1. Manual Creation of Machine Trust Accounts</A
+NAME="AEN1196"
+>8.4.1. Manually creating machine trust accounts</A
></H2
><P
->The first step in manually creating a machine trust account is to
-manually create the corresponding Unix account in
-<TT
-CLASS="FILENAME"
->/etc/passwd</TT
->. This can be done using
-<B
+>The first step in creating a machine trust account by hand is to
+create an entry for the machine in /etc/passwd. This can be done
+using <B
CLASS="COMMAND"
>vipw</B
-> or other 'add user' command that is normally
-used to create new Unix accounts. The following is an example for a
-Linux based Samba server:</P
+> or any 'add userr' command which is normally
+used to create new UNIX accounts. The following is an example for a Linux
+based Samba server:</P
><P
-> <TT
+><TT
CLASS="PROMPT"
>root# </TT
-><B
-CLASS="COMMAND"
>/usr/sbin/useradd -g 100 -d /dev/null -c <TT
CLASS="REPLACEABLE"
><I
@@ -6026,32 +6013,28 @@ CLASS="REPLACEABLE"
><I
>machine_name</I
></TT
->$ </B
-></P
+>$ </P
><P
><TT
CLASS="PROMPT"
>root# </TT
-><B
-CLASS="COMMAND"
>passwd -l <TT
CLASS="REPLACEABLE"
><I
>machine_name</I
></TT
->$</B
-></P
+>$</P
><P
>The <TT
CLASS="FILENAME"
>/etc/passwd</TT
> entry will list the machine name
-with a "$" appended, won't have a password, will have a null shell and no
-home directory. For example a machine named 'doppy' would have an
+with a $ appended, won't have a passwd, will have a null shell and no
+home directory. For example a machine called 'doppy' would have an
<TT
CLASS="FILENAME"
>/etc/passwd</TT
-> entry like this:</P
+> entry like this :</P
><P
><TABLE
BORDER="0"
@@ -6077,21 +6060,19 @@ CLASS="REPLACEABLE"
><I
>machine_nickname</I
></TT
-> can be any
-descriptive name for the client, i.e., BasementComputer.
-<TT
+> can be any descriptive name for the
+pc i.e. BasementComputer. The <TT
CLASS="REPLACEABLE"
><I
>machine_name</I
></TT
-> absolutely must be the NetBIOS
-name of the client to be joined to the domain. The "$" must be
-appended to the NetBIOS name of the client or Samba will not recognize
-this as a machine trust account.</P
-><P
->Now that the corresponding Unix account has been created, the next step is to create
-the Samba account for the client containing the well-known initial
-machine trust account password. This can be done using the <A
+> absolutely must be
+the NetBIOS name of the pc to be added to the domain. The "$" must append the NetBIOS
+name of the pc or samba will not recognize this as a machine account</P
+><P
+>Now that the UNIX account has been created, the next step is to create
+the smbpasswd entry for the machine containing the well known initial
+trust account password. This can be done using the <A
HREF="smbpasswd.6.html"
TARGET="_top"
><B
@@ -6104,14 +6085,11 @@ as shown here:</P
><TT
CLASS="PROMPT"
>root# </TT
-><B
-CLASS="COMMAND"
->smbpasswd -a -m <TT
+> smbpasswd -a -m <TT
CLASS="REPLACEABLE"
><I
>machine_name</I
></TT
-></B
></P
><P
>where <TT
@@ -6120,8 +6098,7 @@ CLASS="REPLACEABLE"
>machine_name</I
></TT
> is the machine's NetBIOS
-name. The RID of the new machine account is generated from the UID of
-the corresponding Unix account.</P
+name. </P
><DIV
CLASS="WARNING"
><P
@@ -6142,9 +6119,9 @@ ALIGN="CENTER"
ALIGN="LEFT"
><P
> Manually creating a machine trust account using this method is the
- equivalent of creating a machine trust account on a Windows NT PDC using
+ equivalent of creating a machine account on a Windows NT PDC using
the "Server Manager". From the time at which the account is created
- to the time which the client joins the domain and changes the password,
+ to the time which th client joins the domain and changes the password,
your domain is vulnerable to an intruder joining your domain using a
a machine with the same NetBIOS name. A PDC inherently trusts
members of the domain and will serve out a large degree of user
@@ -6160,30 +6137,18 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
-NAME="AEN1234"
->8.4.2. "On-the-Fly" Creation of Machine Trust Accounts</A
+NAME="AEN1227"
+>8.4.2. Creating machine trust accounts "on the fly"</A
></H2
><P
->The second (and recommended) way of creating machine trust accounts is
-simply to allow the Samba server to create them as needed when the client
-is joined to the domain. </P
-><P
->Since each Samba machine trust account requires a corresponding
-Unix account, a method for automatically creating the
-Unix account is usually supplied; this requires configuration of the
-<A
+>The second, and most recommended way of creating machine trust accounts
+is to create them as needed at the time the client is joined to
+the domain. You will need to include a value for the <A
HREF="smb.conf.5.html#ADDUSERSCRIPT"
TARGET="_top"
>add user script</A
->
-option in <TT
-CLASS="FILENAME"
->smb.conf</TT
->. This
-method is not required, however; corresponding Unix accounts may also
-be created manually.</P
-><P
->Below is an example for a RedHat 6.2 Linux system.</P
+>
+parameter. Below is an example from a RedHat 6.2 Linux system.</P
><P
><TABLE
BORDER="0"
@@ -6193,72 +6158,26 @@ WIDTH="100%"
><TD
><PRE
CLASS="PROGRAMLISTING"
->[global]
- # &#60;...remainder of parameters...&#62;
- add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u </PRE
+>add user script = /usr/sbin/useradd -d /dev/null -g 100 -s /bin/false -M %u </PRE
></TD
></TR
></TABLE
></P
-></DIV
-><DIV
-CLASS="SECT2"
-><HR><H2
-CLASS="SECT2"
-><A
-NAME="AEN1243"
->8.4.3. Joining the Client to the Domain</A
-></H2
-><P
->The procedure for joining a client to the domain varies with the
-version of Windows.</P
-><P
-></P
-><UL
-><LI
-><P
-><EM
->Windows 2000</EM
-></P
><P
-> When the user elects to join the client to a domain, Windows prompts for
- an account and password that is privileged to join the domain. A
- Samba administrative account (i.e., a Samba account that has root
- privileges on the Samba server) must be entered here; the
- operation will fail if an ordinary user account is given.
- The password for this account should be
- set to a different password than the associated
- <TT
+>In Samba 2.2.1, <EM
+>only the root account</EM
+> can be used to create
+machine accounts like this. Therefore, it is required to create
+an entry in smbpasswd for <EM
+>root</EM
+>. The password
+<EM
+>SHOULD</EM
+> be set to a different password that the
+associated <TT
CLASS="FILENAME"
>/etc/passwd</TT
-> entry, for security
- reasons. </P
-><P
->The session key of the Samba administrative account acts as an
- encryption key for setting the password of the machine trust
- account. The machine trust account will be created on-the-fly, or
- updated if it already exists.</P
-></LI
-><LI
-><P
-><EM
->Windows NT</EM
-></P
-><P
-> If the machine trust account was created manually, on the
- Identification Changes menu enter the domain name, but do not
- check the box "Create a Computer Account in the Domain." In this case,
- the existing machine trust account is used to join the machine to
- the domain.</P
-><P
-> If the machine trust account is to be created
- on-the-fly, on the Identification Changes menu enter the domain
- name, and check the box "Create a Computer Account in the Domain." In
- this case, joining the domain proceeds as above for Windows 2000
- (i.e., you must supply a Samba administrative account when
- prompted).</P
-></LI
-></UL
+> entry for security reasons.</P
></DIV
></DIV
><DIV
@@ -6266,7 +6185,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
-NAME="AEN1258"
+NAME="AEN1238"
>8.5. Common Problems and Errors</A
></H1
><P
@@ -6286,7 +6205,7 @@ CLASS="FILENAME"
>/etc/passwd</TT
>
of the machine name with a '$' appended. FreeBSD (and other BSD
- systems?) won't create a user with a '$' in their name.
+ systems ?) won't create a user with a '$' in their name.
</P
><P
> The problem is only in the program used to make the entry, once
@@ -6296,7 +6215,7 @@ CLASS="COMMAND"
>vipw</B
> to edit the entry, adding the '$'. Or create
the whole entry with vipw if you like, make sure you use a
- unique User ID !
+ unique uid !
</P
></LI
><LI
@@ -6304,11 +6223,11 @@ CLASS="COMMAND"
> <EM
>I get told "You already have a connection to the Domain...."
or "Cannot join domain, the credentials supplied conflict with an
- existing set.." when creating a machine trust account.</EM
+ existing set.." when creating a machine account.</EM
>
</P
><P
-> This happens if you try to create a machine trust account from the
+> This happens if you try to create a machine account from the
machine itself and already have a connection (e.g. mapped drive)
to a share (or IPC$) on the Samba PDC. The following command
will remove all network drive connections:
@@ -6360,17 +6279,17 @@ CLASS="COMMAND"
><LI
><P
> <EM
->The machine trust account for this computer either does not
+>The machine account for this computer either does not
exist or is not accessible.</EM
>
</P
><P
> When I try to join the domain I get the message "The machine account
- for this computer either does not exist or is not accessible". What's
+ for this computer either does not exist or is not accessible". Whats
wrong?
</P
><P
-> This problem is caused by the PDC not having a suitable machine trust account.
+> This problem is caused by the PDC not having a suitable machine account.
If you are using the <TT
CLASS="PARAMETER"
><I
@@ -6383,7 +6302,7 @@ CLASS="PARAMETER"
><P
> Alternatively if you are creating account entries manually then they
have not been created correctly. Make sure that you have the entry
- correct for the machine trust account in smbpasswd file on the Samba PDC.
+ correct for the machine account in smbpasswd file on the Samba PDC.
If you added the account using an editor rather than using the smbpasswd
utility, make sure that the account name is the machine NetBIOS name
with a '$' appended to it ( i.e. computer_name$ ). There must be an entry
@@ -6465,7 +6384,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
-NAME="AEN1306"
+NAME="AEN1286"
>8.6. System Policies and Profiles</A
></H1
><P
@@ -6486,7 +6405,7 @@ Profiles and Policies in Windows NT 4.0</A
><LI
><P
> <EM
->What about Windows NT Policy Editor?</EM
+>What about Windows NT Policy Editor ?</EM
>
</P
><P
@@ -6545,7 +6464,7 @@ CLASS="COMMAND"
><LI
><P
> <EM
->Can Win95 do Policies?</EM
+>Can Win95 do Policies ?</EM
>
</P
><P
@@ -6576,7 +6495,7 @@ CLASS="FILENAME"
</P
><P
> Since I don't need to buy an NT Server CD now, how do I get
- the 'User Manager for Domains', the 'Server Manager'?
+ the 'User Manager for Domains', the 'Server Manager' ?
</P
><P
> Microsoft distributes a version of these tools called nexus for
@@ -6622,8 +6541,8 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
-NAME="AEN1350"
->8.7. What other help can I get?</A
+NAME="AEN1330"
+>8.7. What other help can I get ?</A
></H1
><P
>There are many sources of information available in the form
@@ -6686,7 +6605,7 @@ HREF="http://www.tcpdump.org/"
TARGET="_top"
>http://www.tcpdup.org/</A
>.
- Ethereal, another good packet sniffer for Unix and Win32
+ Ethereal, another good packet sniffer for UNIX and Win32
hosts, can be downloaded from <A
HREF="http://www.ethereal.com/"
TARGET="_top"
@@ -6883,7 +6802,7 @@ TARGET="_top"
><LI
><P
> <EM
->How do I get help from the mailing lists?</EM
+>How do I get help from the mailing lists ?</EM
>
</P
><P
@@ -6975,14 +6894,14 @@ TARGET="_top"
>Please think carefully before attaching a document to an email.
Consider pasting the relevant parts into the body of the message. The samba
mailing lists go to a huge number of people, do they all need a copy of your
- smb.conf in their attach directory?</P
+ smb.conf in their attach directory ?</P
></LI
></UL
></LI
><LI
><P
> <EM
->How do I get off the mailing lists?</EM
+>How do I get off the mailing lists ?</EM
>
</P
><P
@@ -7018,7 +6937,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
-NAME="AEN1464"
+NAME="AEN1444"
>8.8. Domain Control for Windows 9x/ME</A
></H1
><DIV
@@ -7030,10 +6949,8 @@ CLASS="NOTE"
>Note: </B
>The following section contains much of the original
DOMAIN.txt file previously included with Samba. Much of
-the material is based on what went into the book <EM
->Special
-Edition, Using Samba</EM
->, by Richard Sharpe.</P
+the material is based on what went into the book Special
+Edition, Using Samba. (Richard Sharpe)</P
></BLOCKQUOTE
></DIV
><P
@@ -7048,12 +6965,11 @@ other systems based on NT server support this, as does at least Samba TNG now).<
server in the domain should accept the same authentication information.
Network browsing functionality of domains and workgroups is
identical and is explained in BROWSING.txt. It should be noted, that browsing
-is totally orthogonal to logon support.</P
+is total orthogonal to logon support.</P
><P
>Issues related to the single-logon network model are discussed in this
-section. Samba supports domain logons, network logon scripts, and user
-profiles for MS Windows for workgroups and MS Windows 9X/ME clients
-which will be the focus of this section.</P
+document. Samba supports domain logons, network logon scripts, and user
+profiles for MS Windows for workgroups and MS Windows 9X clients.</P
><P
>When an SMB client in a domain wishes to logon it broadcast requests for a
logon server. The first one to reply gets the job, and validates its
@@ -7064,12 +6980,37 @@ servers advertising themselves as participating in a domain. This
demonstrates how authentication is quite different from but closely
involved with domains.</P
><P
+>Another thing commonly associated with single-logon domains is remote
+administration over the SMB protocol. Again, there is no reason why this
+cannot be implemented with an underlying username database which is
+different from the Windows NT SAM. Support for the Remote Administration
+Protocol is planned for a future release of Samba.</P
+><P
+>Network logon support as discussed in this section is aimed at Window for
+Workgroups, and Windows 9X clients. </P
+><P
+>Support for profiles is confirmed as working for Win95, NT 4.0 and NT 3.51.
+It is possible to specify: the profile location; script file to be loaded
+on login; the user's home directory; and for NT a kick-off time could also
+now easily be supported. However, there are some differences between Win9X
+profile support and WinNT profile support. These are discussed below.</P
+><P
+>With NT Workstations, all this does not require the use or intervention of
+an NT 4.0 or NT 3.51 server: Samba can now replace the logon services
+provided by an NT server, to a limited and experimental degree (for example,
+running "User Manager for Domains" will not provide you with access to
+a domain created by a Samba Server).</P
+><P
+>With Win95, the help of an NT server can be enlisted, both for profile storage
+and for user authentication. For details on user authentication, see
+security_level.txt. For details on profile storage, see below.</P
+><P
>Using these features you can make your clients verify their logon via
the Samba server; make clients run a batch file when they logon to
the network and download their preferences, desktop and start menu.</P
><P
->Before launching into the configuration instructions, it is
-worthwhile lookingat how a Windows 9x/ME client performs a logon:</P
+>Before launching into the configuration instructions, it is worthwhile looking
+at how a Win9X client performs a logon:</P
><P
></P
><OL
@@ -7077,7 +7018,7 @@ TYPE="1"
><LI
><P
> The client broadcasts (to the IP broadcast address of the subnet it is in)
- a NetLogon request. This is sent to the NetBIOS name DOMAIN&#60;1c&#62; at the
+ a NetLogon request. This is sent to the NetBIOS address DOMAIN&#60;00&#62; at the
NetBIOS layer. The client chooses the first response it receives, which
contains the NetBIOS name of the logon server to use in the format of
\\SERVER.
@@ -7132,27 +7073,122 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
-NAME="AEN1490"
+NAME="AEN1474"
>8.8.1. Configuration Instructions: Network Logons</A
></H2
><P
->The main difference between a PDC and a Windows 9x logon
-server configuration is that</P
+>To use domain logons and profiles you need to do the following:</P
><P
></P
-><UL
+><OL
+TYPE="1"
><LI
><P
->Password encryption is not required for a Windows 9x logon server.</P
+> Create a share called [netlogon] in your smb.conf. This share should
+ be readable by all users, and probably should not be writeable. This
+ share will hold your network logon scripts, and the CONFIG.POL file
+ (Note: for details on the CONFIG.POL file, how to use it, what it is,
+ refer to the Microsoft Windows NT Administration documentation.
+ The format of these files is not known, so you will need to use
+ Microsoft tools).
+ </P
+><P
+> For example I have used:
+ </P
+><P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="90%"
+><TR
+><TD
+><PRE
+CLASS="PROGRAMLISTING"
+>[netlogon]
+ path = /data/dos/netlogon
+ writeable = no
+ guest ok = no</PRE
+></TD
+></TR
+></TABLE
+></P
+><P
+> Note that it is important that this share is not writeable by ordinary
+ users, in a secure environment: ordinary users should not be allowed
+ to modify or add files that another user's computer would then download
+ when they log in.
+ </P
></LI
><LI
><P
->Windows 9x/ME clients do not possess machine trust accounts.</P
+> in the [global] section of smb.conf set the following:
+ </P
+><P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="90%"
+><TR
+><TD
+><PRE
+CLASS="PROGRAMLISTING"
+>domain logons = yes
+logon script = %U.bat
+ </PRE
+></TD
+></TR
+></TABLE
+></P
+><P
+> The choice of batch file is, of course, up to you. The above would
+ give each user a separate batch file as the %U will be changed to
+ their username automatically. The other standard % macros may also be
+ used. You can make the batch files come from a subdirectory by using
+ something like:
+ </P
+><P
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="90%"
+><TR
+><TD
+><PRE
+CLASS="PROGRAMLISTING"
+>logon script = scripts\%U.bat
+ </PRE
+></TD
+></TR
+></TABLE
+></P
></LI
-></UL
+><LI
+><P
+> create the batch files to be run when the user logs in. If the batch
+ file doesn't exist then no batch file will be run.
+ </P
><P
->Therefore, a Samba PDC will also act as a Windows 9x logon
-server.</P
+> In the batch files you need to be careful to use DOS style cr/lf line
+ endings. If you don't then DOS may get confused. I suggest you use a
+ DOS editor to remotely edit the files if you don't know how to produce
+ DOS style files under unix.
+ </P
+></LI
+><LI
+><P
+> Use smbclient with the -U option for some users to make sure that
+ the \\server\NETLOGON share is available, the batch files are
+ visible and they are readable by the users.
+ </P
+></LI
+><LI
+><P
+> you will probably find that your clients automatically mount the
+ \\SERVER\NETLOGON share as drive z: while logging in. You can put
+ some useful programs there to execute from the batch files.
+ </P
+></LI
+></OL
><DIV
CLASS="WARNING"
><P
@@ -7192,7 +7228,7 @@ CLASS="CONSTANT"
>
mode security is really just a variation on SMB user level security.</P
><P
->Actually, this issue is also closely tied to the debate on whether
+>Actually, this issue is also closer tied to the debate on whether
or not Samba must be the domain master browser for its workgroup
when operating as a DC. While it may technically be possible
to configure a server as such (after all, browsing and domain logons
@@ -7226,7 +7262,7 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
-NAME="AEN1509"
+NAME="AEN1508"
>8.8.2. Configuration Instructions: Setting up Roaming User Profiles</A
></H2
><DIV
@@ -7273,11 +7309,11 @@ CLASS="SECT3"
><HR><H3
CLASS="SECT3"
><A
-NAME="AEN1517"
+NAME="AEN1516"
>8.8.2.1. Windows NT Configuration</A
></H3
><P
->To support WinNT clients, in the [global] section of smb.conf set the
+>To support WinNT clients, inn the [global] section of smb.conf set the
following (for example):</P
><P
><TABLE
@@ -7317,7 +7353,7 @@ CLASS="SECT3"
><HR><H3
CLASS="SECT3"
><A
-NAME="AEN1525"
+NAME="AEN1524"
>8.8.2.2. Windows 9X Configuration</A
></H3
><P
@@ -7357,7 +7393,7 @@ CLASS="SECT3"
><HR><H3
CLASS="SECT3"
><A
-NAME="AEN1533"
+NAME="AEN1532"
>8.8.2.3. Win9X and WinNT Configuration</A
></H3
><P
@@ -7395,7 +7431,7 @@ CLASS="SECT3"
><HR><H3
CLASS="SECT3"
><A
-NAME="AEN1540"
+NAME="AEN1539"
>8.8.2.4. Windows 9X Profile Setup</A
></H3
><P
@@ -7467,7 +7503,7 @@ the newest folders and short-cuts from each set.</P
>If you have made the folders / files read-only on the samba server,
then you will get errors from the w95 machine on logon and logout, as
it attempts to merge the local and the remote profile. Basically, if
-you have any errors reported by the w95 machine, check the Unix file
+you have any errors reported by the w95 machine, check the unix file
permissions and ownership rights on the profile directory contents,
on the samba server.</P
><P
@@ -7551,7 +7587,7 @@ CLASS="SECT3"
><HR><H3
CLASS="SECT3"
><A
-NAME="AEN1576"
+NAME="AEN1575"
>8.8.2.5. Windows NT Workstation 4.0</A
></H3
><P
@@ -7633,7 +7669,7 @@ CLASS="SECT3"
><HR><H3
CLASS="SECT3"
><A
-NAME="AEN1589"
+NAME="AEN1588"
>8.8.2.6. Windows NT Server</A
></H3
><P
@@ -7647,7 +7683,7 @@ CLASS="SECT3"
><HR><H3
CLASS="SECT3"
><A
-NAME="AEN1592"
+NAME="AEN1591"
>8.8.2.7. Sharing Profiles between W95 and NT Workstation 4.0</A
></H3
><DIV
@@ -7712,7 +7748,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
-NAME="AEN1602"
+NAME="AEN1601"
>8.9. DOMAIN_CONTROL.txt : Windows NT Domain Control &#38; Samba</A
></H1
><DIV
@@ -7841,7 +7877,7 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN1652"
+NAME="AEN1644"
>9.1. Abstract</A
></H1
><P
@@ -7864,7 +7900,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
-NAME="AEN1656"
+NAME="AEN1648"
>9.2. Introduction</A
></H1
><P
@@ -7918,7 +7954,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
-NAME="AEN1669"
+NAME="AEN1661"
>9.3. What Winbind Provides</A
></H1
><P
@@ -7960,7 +7996,7 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
-NAME="AEN1676"
+NAME="AEN1668"
>9.3.1. Target Uses</A
></H2
><P
@@ -7984,7 +8020,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
-NAME="AEN1680"
+NAME="AEN1672"
>9.4. How Winbind Works</A
></H1
><P
@@ -8004,7 +8040,7 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
-NAME="AEN1685"
+NAME="AEN1677"
>9.4.1. Microsoft Remote Procedure Calls</A
></H2
><P
@@ -8030,7 +8066,7 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
-NAME="AEN1689"
+NAME="AEN1681"
>9.4.2. Name Service Switch</A
></H2
><P
@@ -8110,7 +8146,7 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
-NAME="AEN1705"
+NAME="AEN1697"
>9.4.3. Pluggable Authentication Modules</A
></H2
><P
@@ -8159,7 +8195,7 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
-NAME="AEN1713"
+NAME="AEN1705"
>9.4.4. User and Group ID Allocation</A
></H2
><P
@@ -8185,7 +8221,7 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
-NAME="AEN1717"
+NAME="AEN1709"
>9.4.5. Result Caching</A
></H2
><P
@@ -8208,7 +8244,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
-NAME="AEN1720"
+NAME="AEN1712"
>9.5. Installation and Configuration</A
></H1
><P
@@ -8227,7 +8263,7 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
-NAME="AEN1725"
+NAME="AEN1717"
>9.5.1. Introduction</A
></H2
><P
@@ -8278,24 +8314,17 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
-NAME="AEN1738"
+NAME="AEN1730"
>9.5.2. Requirements</A
></H2
><P
>If you have a samba configuration file that you are currently
-using... <EM
->BACK IT UP!</EM
-> If your system already uses PAM,
-<EM
->back up the <TT
+using... BACK IT UP! If your system already uses PAM, BACK UP
+THE <TT
CLASS="FILENAME"
>/etc/pam.d</TT
-> directory
-contents!</EM
-> If you haven't already made a boot disk,
-<EM
->MAKE ONE NOW!</EM
-></P
+> directory contents! If you
+haven't already made a boot disk, MAKE ON NOW!</P
><P
>Messing with the pam configuration files can make it nearly impossible
to log in to yourmachine. That's why you want to be able to boot back
@@ -8306,15 +8335,10 @@ CLASS="FILENAME"
> back to the original state they were in if
you get frustrated with the way things are going. ;-)</P
><P
->The latest version of SAMBA (version 2.2.2 as of this writing), now
-includes a functioning winbindd daemon. Please refer to the
-<A
-HREF="http://samba.org/"
-TARGET="_top"
->main SAMBA web page</A
-> or,
-better yet, your closest SAMBA mirror site for instructions on
-downloading the source code.</P
+>The newest version of SAMBA (version 2.2.2), available from
+cvs.samba.org, now include a functioning winbindd daemon. Please refer
+to the main SAMBA web page or, better yet, your closest SAMBA mirror
+site for instructions on downloading the source code.</P
><P
>To allow Domain users the ability to access SAMBA shares and
files, as well as potentially other services provided by your
@@ -8322,21 +8346,15 @@ SAMBA machine, PAM (pluggable authentication modules) must
be setup properly on your machine. In order to compile the
winbind modules, you should have at least the pam libraries resident
on your system. For recent RedHat systems (7.1, for instance), that
-means <TT
-CLASS="FILENAME"
->pam-0.74-22</TT
->. For best results, it is helpful to also
-install the development packages in <TT
-CLASS="FILENAME"
->pam-devel-0.74-22</TT
->.</P
+means 'pam-0.74-22'. For best results, it is helpful to also
+install the development packages in 'pam-devel-0.74-22'.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
-NAME="AEN1752"
+NAME="AEN1738"
>9.5.3. Testing Things Out</A
></H2
><P
@@ -8367,26 +8385,19 @@ CLASS="FILENAME"
>/usr/man</TT
> entries for pam. Winbind built better
in SAMBA if the pam-devel package was also installed. This package includes
-the header files needed to compile pam-aware applications. For instance,
-my RedHat system has both <TT
-CLASS="FILENAME"
->pam-0.74-22</TT
-> and
-<TT
-CLASS="FILENAME"
->pam-devel-0.74-22</TT
-> RPMs installed.</P
+the header files needed to compile pam-aware applications. For instance, my RedHat
+system has both 'pam-0.74-22' and 'pam-devel-0.74-22' RPMs installed.</P
><DIV
CLASS="SECT3"
><HR><H3
CLASS="SECT3"
><A
-NAME="AEN1763"
+NAME="AEN1747"
>9.5.3.1. Configure and compile SAMBA</A
></H3
><P
>The configuration and compilation of SAMBA is pretty straightforward.
-The first three steps may not be necessary depending upon
+The first three steps maynot be necessary depending upon
whether or not you have previously built the Samba binaries.</P
><P
><TABLE
@@ -8399,56 +8410,35 @@ WIDTH="100%"
CLASS="PROGRAMLISTING"
><TT
CLASS="PROMPT"
->root#</TT
-> <B
-CLASS="COMMAND"
->autoconf</B
->
+>root# </TT
+> autoconf
<TT
CLASS="PROMPT"
->root#</TT
-> <B
-CLASS="COMMAND"
->make clean</B
->
+>root# </TT
+> make clean
<TT
CLASS="PROMPT"
->root#</TT
-> <B
-CLASS="COMMAND"
->rm config.cache</B
->
+>root# </TT
+> rm config.cache
<TT
CLASS="PROMPT"
->root#</TT
-> <B
-CLASS="COMMAND"
->./configure --with-winbind</B
->
+>root# </TT
+> ./configure --with-winbind
<TT
CLASS="PROMPT"
->root#</TT
-> <B
-CLASS="COMMAND"
->make</B
->
+>root# </TT
+> make
<TT
CLASS="PROMPT"
->root#</TT
-> <B
-CLASS="COMMAND"
->make install</B
-></PRE
+>root# </TT
+> make install</PRE
></TD
></TR
></TABLE
></P
><P
->This will, by default, install SAMBA in <TT
-CLASS="FILENAME"
->/usr/local/samba</TT
->.
-See the main SAMBA documentation if you want to install SAMBA somewhere else.
+>This will, by default, install SAMBA in /usr/local/samba. See the
+main SAMBA documentation if you want to install SAMBA somewhere else.
It will also build the winbindd executable and libraries. </P
></DIV
><DIV
@@ -8456,37 +8446,24 @@ CLASS="SECT3"
><HR><H3
CLASS="SECT3"
><A
-NAME="AEN1782"
->9.5.3.2. Configure <TT
-CLASS="FILENAME"
->nsswitch.conf</TT
-> and the
-winbind libraries</A
+NAME="AEN1759"
+>9.5.3.2. Configure nsswitch.conf and the winbind libraries</A
></H3
><P
->The libraries needed to run the <B
-CLASS="COMMAND"
->winbindd</B
-> daemon
-through nsswitch need to be copied to their proper locations, so</P
+>The libraries needed to run the winbind daemon through nsswitch
+need to be copied to their proper locations, so</P
><P
><TT
CLASS="PROMPT"
->root#</TT
-> <B
-CLASS="COMMAND"
->cp ../samba/source/nsswitch/libnss_winbind.so /lib</B
-></P
+>root# </TT
+> cp ../samba/source/nsswitch/libnss_winbind.so /lib</P
><P
>I also found it necessary to make the following symbolic link:</P
><P
><TT
CLASS="PROMPT"
->root#</TT
-> <B
-CLASS="COMMAND"
->ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2</B
-></P
+>root# </TT
+> ln -s /lib/libnss_winbind.so /lib/libnss_winbind.so.2</P
><P
>Now, as root you need to edit <TT
CLASS="FILENAME"
@@ -8496,11 +8473,11 @@ allow user and group entries to be visible from the <B
CLASS="COMMAND"
>winbindd</B
>
-daemon. My <TT
+daemon, as well as from your /etc/hosts files and NIS servers. My
+<TT
CLASS="FILENAME"
>/etc/nsswitch.conf</TT
-> file look like
-this after editing:</P
+> file look like this after editing:</P
><P
><TABLE
BORDER="0"
@@ -8511,7 +8488,7 @@ WIDTH="100%"
><PRE
CLASS="PROGRAMLISTING"
> passwd: files winbind
- shadow: files
+ shadow: files winbind
group: files winbind</PRE
></TD
></TR
@@ -8520,20 +8497,13 @@ CLASS="PROGRAMLISTING"
><P
>
The libraries needed by the winbind daemon will be automatically
-entered into the <B
-CLASS="COMMAND"
->ldconfig</B
-> cache the next time
-your system reboots, but it
+entered into the ldconfig cache the next time your system reboots, but it
is faster (and you don't need to reboot) if you do it manually:</P
><P
><TT
CLASS="PROMPT"
->root#</TT
-> <B
-CLASS="COMMAND"
->/sbin/ldconfig -v | grep winbind</B
-></P
+>root# </TT
+> /sbin/ldconfig -v | grep winbind</P
><P
>This makes <TT
CLASS="FILENAME"
@@ -8546,7 +8516,7 @@ CLASS="SECT3"
><HR><H3
CLASS="SECT3"
><A
-NAME="AEN1807"
+NAME="AEN1778"
>9.5.3.3. Configure smb.conf</A
></H3
><P
@@ -8581,45 +8551,16 @@ CLASS="PROGRAMLISTING"
>[global]
&#60;...&#62;
# separate domain and username with '+', like DOMAIN+username
- <A
-HREF="winbindd.8.html#WINBINDSEPARATOR"
-TARGET="_top"
->winbind separator</A
-> = +
+ winbind separator = +
# use uids from 10000 to 20000 for domain users
- <A
-HREF="winbindd.8.html#WINBINDUID"
-TARGET="_top"
->winbind uid</A
-> = 10000-20000
+ winbind uid = 10000-20000
# use gids from 10000 to 20000 for domain groups
- <A
-HREF="winbindd.8.html#WINBINDGID"
-TARGET="_top"
->winbind gid</A
-> = 10000-20000
+ winbind gid = 10000-20000
# allow enumeration of winbind users and groups
- <A
-HREF="winbindd.8.html#WINBINDENUMUSERS"
-TARGET="_top"
->winbind enum users</A
-> = yes
- <A
-HREF="winbindd.8.html#WINBINDENUMGROUP"
-TARGET="_top"
->winbind enum groups</A
-> = yes
+ winbind enum users = yes
+ winbind enum groups = yes
# give winbind users a real shell (only needed if they have telnet access)
- <A
-HREF="winbindd.8.html#TEMPLATEHOMEDIR"
-TARGET="_top"
->template homedir</A
-> = /home/winnt/%D/%U
- <A
-HREF="winbindd.8.html#TEMPLATESHELL"
-TARGET="_top"
->template shell</A
-> = /bin/bash</PRE
+ template shell = /bin/bash</PRE
></TD
></TR
></TABLE
@@ -8630,7 +8571,7 @@ CLASS="SECT3"
><HR><H3
CLASS="SECT3"
><A
-NAME="AEN1823"
+NAME="AEN1787"
>9.5.3.4. Join the SAMBA server to the PDC domain</A
></H3
><P
@@ -8651,11 +8592,8 @@ a domain user who has administrative privileges in the domain.</P
><P
><TT
CLASS="PROMPT"
->root#</TT
-> <B
-CLASS="COMMAND"
->/usr/local/samba/bin/smbpasswd -j DOMAIN -r PDC -U Administrator</B
-></P
+>root# </TT
+>/usr/local/samba/bin/smbpasswd -j DOMAIN -r PDC -U Administrator</P
><P
>The proper response to the command should be: "Joined the domain
<TT
@@ -8676,7 +8614,7 @@ CLASS="SECT3"
><HR><H3
CLASS="SECT3"
><A
-NAME="AEN1834"
+NAME="AEN1797"
>9.5.3.5. Start up the winbindd daemon and test it!</A
></H3
><P
@@ -8688,37 +8626,25 @@ command as root:</P
><P
><TT
CLASS="PROMPT"
->root#</TT
-> <B
-CLASS="COMMAND"
->/usr/local/samba/bin/winbindd</B
-></P
+>root# </TT
+>/usr/local/samba/bin/winbindd</P
><P
>I'm always paranoid and like to make sure the daemon
is really running...</P
><P
><TT
CLASS="PROMPT"
->root#</TT
-> <B
-CLASS="COMMAND"
->ps -ae | grep winbindd</B
-></P
-><P
->This command should produce output like this, if the daemon is running</P
-><P
->3025 ? 00:00:00 winbindd</P
+>root# </TT
+> ps -ae | grep winbindd
+3025 ? 00:00:00 winbindd</P
><P
>Now... for the real test, try to get some information about the
users on your PDC</P
><P
><TT
CLASS="PROMPT"
->root#</TT
-> <B
-CLASS="COMMAND"
->/usr/local/samba/bin/wbinfo -u</B
-></P
+>root# </TT
+> # /usr/local/samba/bin/wbinfo -u</P
><P
>
This should echo back a list of users on your Windows users on
@@ -8743,13 +8669,7 @@ CEO+TsInternetUser</PRE
></TABLE
></P
><P
->Obviously, I have named my domain 'CEO' and my <TT
-CLASS="PARAMETER"
-><I
->winbindd
-separator</I
-></TT
-> is '+'.</P
+>Obviously, I have named my domain 'CEO' and my winbindd separator is '+'.</P
><P
>You can do the same sort of thing to get group information from
the PDC:</P
@@ -8764,11 +8684,8 @@ WIDTH="100%"
CLASS="PROGRAMLISTING"
><TT
CLASS="PROMPT"
->root#</TT
-> <B
-CLASS="COMMAND"
->/usr/local/samba/bin/wbinfo -g</B
->
+>root# </TT
+>/usr/local/samba/bin/wbinfo -g
CEO+Domain Admins
CEO+Domain Users
CEO+Domain Guests
@@ -8789,11 +8706,8 @@ Try the following command:</P
><P
><TT
CLASS="PROMPT"
->root#</TT
-> <B
-CLASS="COMMAND"
->getent passwd</B
-></P
+>root# </TT
+> getent passwd</P
><P
>You should get a list that looks like your <TT
CLASS="FILENAME"
@@ -8806,22 +8720,16 @@ directories and default shells.</P
><P
><TT
CLASS="PROMPT"
->root#</TT
-> <B
-CLASS="COMMAND"
->getent group</B
-></P
+>root# </TT
+> getent group</P
></DIV
><DIV
CLASS="SECT3"
><HR><H3
CLASS="SECT3"
><A
-NAME="AEN1870"
->9.5.3.6. Fix the <TT
-CLASS="FILENAME"
->/etc/rc.d/init.d/smb</TT
-> startup files</A
+NAME="AEN1824"
+>9.5.3.6. Fix the /etc/rc.d/init.d/smb startup files</A
></H3
><P
>The <B
@@ -8927,81 +8835,47 @@ CLASS="PROGRAMLISTING"
></TR
></TABLE
></P
-><P
->If you restart the <B
-CLASS="COMMAND"
->smbd</B
->, <B
-CLASS="COMMAND"
->nmbd</B
->,
-and <B
-CLASS="COMMAND"
->winbindd</B
-> daemons at this point, you
-should be able to connect to the samba server as a domain member just as
-if you were a local user.</P
></DIV
><DIV
CLASS="SECT3"
><HR><H3
CLASS="SECT3"
><A
-NAME="AEN1892"
+NAME="AEN1841"
>9.5.3.7. Configure Winbind and PAM</A
></H3
><P
->If you have made it this far, you know that winbindd and samba are working
-together. If you want to use winbind to provide authentication for other
-services, keep reading. The pam configuration files need to be altered in
+>If you have made it this far, you know that winbindd is working.
+Now it is time to integrate it into the operation of samba and other
+services. The pam configuration files need to be altered in
this step. (Did you remember to make backups of your original
<TT
CLASS="FILENAME"
>/etc/pam.d</TT
> files? If not, do it now.)</P
><P
->You will need a pam module to use winbindd with these other services. This
-module will be compiled in the <TT
-CLASS="FILENAME"
->../source/nsswitch</TT
-> directory
-by invoking the command</P
-><P
-><TT
-CLASS="PROMPT"
->root#</TT
-> <B
-CLASS="COMMAND"
->make nsswitch/pam_winbind.so</B
-></P
-><P
->from the <TT
-CLASS="FILENAME"
->../source</TT
-> directory. The
+>To get samba to allow domain users and groups, I modified the
<TT
CLASS="FILENAME"
->pam_winbind.so</TT
-> file should be copied to the location of
-your other pam security modules. On my RedHat system, this was the
-<TT
-CLASS="FILENAME"
->/lib/security</TT
-> directory.</P
+>/etc/pam.d/samba</TT
+> file from</P
><P
-><TT
-CLASS="PROMPT"
->root#</TT
-> <B
-CLASS="COMMAND"
->cp ../samba/source/nsswitch/pam_winbind.so /lib/security</B
+><TABLE
+BORDER="0"
+BGCOLOR="#E0E0E0"
+WIDTH="100%"
+><TR
+><TD
+><PRE
+CLASS="PROGRAMLISTING"
+>auth required /lib/security/pam_stack.so service=system-auth
+account required /lib/security/pam_stack.so service=system-auth</PRE
+></TD
+></TR
+></TABLE
></P
><P
->The <TT
-CLASS="FILENAME"
->/etc/pam.d/samba</TT
-> file does not need to be changed. I
-just left this fileas it was:</P
+>to</P
><P
><TABLE
BORDER="0"
@@ -9011,7 +8885,9 @@ WIDTH="100%"
><TD
><PRE
CLASS="PROGRAMLISTING"
->auth required /lib/security/pam_stack.so service=system-auth
+>auth required /lib/security/pam_winbind.so
+auth required /lib/security/pam_stack.so service=system-auth
+account required /lib/security/pam_winbind.so
account required /lib/security/pam_stack.so service=system-auth</PRE
></TD
></TR
@@ -9102,11 +8978,10 @@ WIDTH="100%"
><TD
><PRE
CLASS="PROGRAMLISTING"
->auth required /lib/security/pam_listfile.so item=user sense=deny file=/etc/ftpusers onerr=succeed
-auth sufficient /lib/security/pam_winbind.so
+>auth sufficient /lib/security/pam_winbind.so
+auth required /lib/security/pam_listfile.so item=user sense=deny file=/etc/ftpusers onerr=succeed
auth required /lib/security/pam_stack.so service=system-auth
auth required /lib/security/pam_shells.so
-account sufficient /lib/security/pam_winbind.so
account required /lib/security/pam_stack.so service=system-auth
session required /lib/security/pam_stack.so service=system-auth</PRE
></TD
@@ -9161,6 +9036,15 @@ CLASS="COMMAND"
>winbind.so</B
> line to get rid of annoying
double prompts for passwords.</P
+><P
+>Finally, don't forget to copy the winbind pam modules from
+the source directory in which you originally compiled the new
+SAMBA up to the /lib/security directory so that pam can use it:</P
+><P
+><TT
+CLASS="PROMPT"
+>root# </TT
+> cp ../samba/source/nsswitch/pam_winbind.so /lib/security</P
></DIV
></DIV
></DIV
@@ -9169,7 +9053,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
-NAME="AEN1939"
+NAME="AEN1882"
>9.6. Limitations</A
></H1
><P
@@ -9210,7 +9094,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
-NAME="AEN1949"
+NAME="AEN1892"
>9.7. Conclusion</A
></H1
><P
@@ -9234,7 +9118,7 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN1963"
+NAME="AEN1906"
>10.1. FAQs</A
></H1
><DIV
@@ -9242,7 +9126,7 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
-NAME="AEN1965"
+NAME="AEN1908"
>10.1.1. How can I configure OS/2 Warp Connect or
OS/2 Warp 4 as a client for Samba?</A
></H2
@@ -9301,7 +9185,7 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
-NAME="AEN1980"
+NAME="AEN1923"
>10.1.2. How can I configure OS/2 Warp 3 (not Connect),
OS/2 1.2, 1.3 or 2.x for Samba?</A
></H2
@@ -9354,7 +9238,7 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
-NAME="AEN1989"
+NAME="AEN1932"
>10.1.3. Are there any other issues when OS/2 (any version)
is used as a client?</A
></H2
@@ -9376,7 +9260,7 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
-NAME="AEN1993"
+NAME="AEN1936"
>10.1.4. How do I get printer driver download working
for OS/2 clients?</A
></H2
@@ -9432,7 +9316,7 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN2009"
+NAME="AEN1952"
>11.1. Introduction</A
></H1
><P
@@ -9454,7 +9338,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
-NAME="AEN2014"
+NAME="AEN1957"
>11.2. CVS Access to samba.org</A
></H1
><P
@@ -9467,7 +9351,7 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
-NAME="AEN2017"
+NAME="AEN1960"
>11.2.1. Access via CVSweb</A
></H2
><P
@@ -9488,7 +9372,7 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
-NAME="AEN2022"
+NAME="AEN1965"
>11.2.2. Access via cvs</A
></H2
><P
@@ -9594,12 +9478,12 @@ CLASS="COMMAND"
></DIV
><HR><H1
><A
-NAME="AEN2050"
+NAME="AEN1993"
>Index</A
></H1
><DL
><DT
->Primary Domain Controller,
+>Primary Domain Controller,
<A
HREF="x1098.htm"
>Background</A
diff --git a/docs/htmldocs/nmbd.8.html b/docs/htmldocs/nmbd.8.html
index ad8c7c61ab7..31afa11cf89 100644
--- a/docs/htmldocs/nmbd.8.html
+++ b/docs/htmldocs/nmbd.8.html
@@ -37,7 +37,7 @@ NAME="AEN8"
><B
CLASS="COMMAND"
>nmbd</B
-> [-D] [-a] [-o] [-P] [-h] [-V] [-d &#60;debug level&#62;] [-H &#60;lmhosts file&#62;] [-l &#60;log directory&#62;] [-n &#60;primary netbios name&#62;] [-p &#60;port number&#62;] [-s &#60;configuration file&#62;]</P
+> [-D] [-a] [-o] [-P] [-h] [-V] [-d &#60;debug level&#62;] [-H &#60;lmhosts file&#62;] [-l &#60;log file&#62;] [-n &#60;primary netbios name&#62;] [-p &#60;port number&#62;] [-s &#60;configuration file&#62;]</P
></DIV
><DIV
CLASS="REFSECT1"
@@ -275,19 +275,22 @@ CLASS="FILENAME"
> file.</P
></DD
><DT
->-l &#60;log directory&#62;</DT
+>-l &#60;log file&#62;</DT
><DD
><P
->The -l parameter specifies a directory
- into which the "log.nmbd" log file will be created
- for operational data from the running
- <B
+>The -l parameter specifies a path
+ and base filename into which operational data from
+ the running <B
CLASS="COMMAND"
>nmbd</B
-> server.</P
-><P
->The default log directory is compiled into Samba
- as part of the build process. Common defaults are <TT
+> server will
+ be logged. The actual log file name is generated by
+ appending the extension ".nmb" to the specified base
+ name. For example, if the name specified was "log"
+ then the file log.nmb would contain the debugging data.</P
+><P
+>The default log file path is compiled into Samba as
+ part of the build process. Common defaults are <TT
CLASS="FILENAME"
> /usr/local/samba/var/log.nmb</TT
>, <TT
diff --git a/docs/htmldocs/rpcclient.1.html b/docs/htmldocs/rpcclient.1.html
index 98a19c6ea2d..53a0ea98dd2 100644
--- a/docs/htmldocs/rpcclient.1.html
+++ b/docs/htmldocs/rpcclient.1.html
@@ -197,7 +197,7 @@ CLASS="FILENAME"
><P
>Sets the SMB username or username and password. </P
><P
->If %password is not specified, the user will be prompted. The
+>If %password is not specified, The user will be prompted. The
client will first check the <TT
CLASS="ENVAR"
>USER</TT
diff --git a/docs/htmldocs/smb.conf.5.html b/docs/htmldocs/smb.conf.5.html
index 29d0e2553ba..7f1a44c835c 100644
--- a/docs/htmldocs/smb.conf.5.html
+++ b/docs/htmldocs/smb.conf.5.html
@@ -7632,11 +7632,11 @@ CLASS="PARAMETER"
> it is in. Samba 2.2 also
has limited capability to act as a domain controller for Windows
NT 4 Domains. For more details on setting up this feature see
- the Samba-PDC-HOWTO included in the <TT
+ the file DOMAINS.txt in the Samba documentation directory <TT
CLASS="FILENAME"
->htmldocs/</TT
->
- directory shipped with the source code.</P
+>docs/
+ </TT
+> shipped with the source code.</P
><P
>Default: <B
CLASS="COMMAND"
@@ -8187,6 +8187,22 @@ CLASS="PARAMETER"
>
parameter is applied.</P
><P
+>Note that by default this parameter does not apply to permissions
+ set by Windows NT/2000 ACL editors. If the administrator wishes to enforce
+ this mask on access control lists also, they need to set the <A
+HREF="#RESTRICTACLWITHMASK"
+><TT
+CLASS="PARAMETER"
+><I
+>restrict acl with
+ mask</I
+></TT
+></A
+> to <TT
+CLASS="CONSTANT"
+>true</TT
+>.</P
+><P
>See also the parameter <A
HREF="#CREATEMASK"
><TT
@@ -8246,6 +8262,22 @@ CLASS="PARAMETER"
> is
applied.</P
><P
+>Note that by default this parameter does not apply to permissions
+ set by Windows NT/2000 ACL editors. If the administrator wishes to enforce
+ this mask on access control lists also, they need to set the <A
+HREF="#RESTRICTACLWITHMASK"
+><TT
+CLASS="PARAMETER"
+><I
+>restrict acl with
+ mask</I
+></TT
+></A
+> to <TT
+CLASS="CONSTANT"
+>true</TT
+>.</P
+><P
>See also the parameter <A
HREF="#DIRECTORYMASK"
><TT
@@ -12302,7 +12334,7 @@ CLASS="COMMAND"
> --with-msdfs</B
> option. If set to <TT
CLASS="CONSTANT"
->yes</TT
+>yes&#62;</TT
>,
Samba treats the share as a Dfs root and allows clients to browse
the distributed file system tree rooted at the share directory.
@@ -12382,7 +12414,7 @@ CLASS="FILENAME"
CLASS="FILENAME"
>/etc/nsswitch.conf</TT
>
- file. Note that this method is only used if the NetBIOS name
+ 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.</P
></LI
@@ -13171,7 +13203,7 @@ CLASS="PARAMETER"
></TT
></A
> parameter is set to true, the chat pairs
- may be matched in any order, and success is determined by the PAM result,
+ may be matched in any order, and sucess is determined by the PAM result,
not any particular output. The \n macro is ignored for PAM conversions.
</P
><P
@@ -14157,7 +14189,7 @@ CLASS="COMMAND"
><P
>For <B
CLASS="COMMAND"
->printing = SYSV or HPUX :</B
+>printing = SYS or HPUX :</B
></P
><P
><B
@@ -14640,7 +14672,7 @@ CLASS="PARAMETER"
> if specified in the
[global] section.</P
><P
->Currently nine printing styles are supported. They are
+>Currently eight printing styles are supported. They are
<TT
CLASS="CONSTANT"
>BSD</TT
@@ -15119,6 +15151,108 @@ CLASS="COMMAND"
></DD
><DT
><A
+NAME="RESTRICTACLWITHMASK"
+></A
+>restrict acl with mask (S)</DT
+><DD
+><P
+>This is a boolean parameter. If set to <TT
+CLASS="CONSTANT"
+>false</TT
+> (default), then
+ creation of files with access control lists (ACLS) and modification of ACLs
+ using the Windows NT/2000 ACL editor will be applied directly to the file
+ or directory.</P
+><P
+>If set to <TT
+CLASS="CONSTANT"
+>true</TT
+>, then all requests to set an ACL on a file will have the
+ parameters <A
+HREF="#CREATEMASK"
+><TT
+CLASS="PARAMETER"
+><I
+>create mask</I
+></TT
+></A
+>,
+ <A
+HREF="#FORCECREATEMODE"
+><TT
+CLASS="PARAMETER"
+><I
+>force create mode</I
+></TT
+></A
+>
+ applied before setting the ACL, and all requests to set an ACL on a directory will
+ have the parameters <A
+HREF="#DIRECTORYMASK"
+><TT
+CLASS="PARAMETER"
+><I
+>directory
+ mask</I
+></TT
+></A
+>, <A
+HREF="#FORCEDIRECTORYMODE"
+><TT
+CLASS="PARAMETER"
+><I
+>force
+ directory mode</I
+></TT
+></A
+> applied before setting the ACL.
+ </P
+><P
+>See also <A
+HREF="#CREATEMASK"
+><TT
+CLASS="PARAMETER"
+><I
+>create mask</I
+></TT
+></A
+>,
+ <A
+HREF="#FORCECREATEMODE"
+><TT
+CLASS="PARAMETER"
+><I
+>force create mode</I
+></TT
+></A
+>,
+ <A
+HREF="#DIRECTORYMASK"
+><TT
+CLASS="PARAMETER"
+><I
+>directory mask</I
+></TT
+></A
+>,
+ <A
+HREF="#FORCEDIRECTORYMODE"
+><TT
+CLASS="PARAMETER"
+><I
+>force directory mode</I
+></TT
+></A
+>
+ </P
+><P
+>Default: <B
+CLASS="COMMAND"
+>restrict acl with mask = no</B
+></P
+></DD
+><DT
+><A
NAME="RESTRICTANONYMOUS"
></A
>restrict anonymous (G)</DT
@@ -15420,7 +15554,7 @@ CLASS="COMMAND"
</B
>.</P
><P
->In versions of Samba prior to 2.0.0, the default was
+>In versions of Samba prior to 2..0, the default was
<B
CLASS="COMMAND"
>security = share</B
@@ -18451,14 +18585,15 @@ WIDTH="90%"
><TD
><PRE
CLASS="PROGRAMLISTING"
->; Veto any files containing the word Security,
-; any ending in .tmp, and any directory containing the
-; word root.
-veto files = /*Security*/*.tmp/*root*/
+> ; Veto any files containing the word Security,
+ ; 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/</PRE
+ ; Veto the Apple specific files that a NetAtalk server
+ ; creates.
+ veto files = /.AppleDouble/.bin/.AppleDesktop/Network Trash Folder/
+ </PRE
></TD
></TR
></TABLE
@@ -19181,7 +19316,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN6051"
+NAME="AEN6086"
></A
><H2
>WARNINGS</H2
@@ -19211,7 +19346,7 @@ TARGET="_top"
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN6057"
+NAME="AEN6092"
></A
><H2
>VERSION</H2
@@ -19222,7 +19357,7 @@ NAME="AEN6057"
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN6060"
+NAME="AEN6095"
></A
><H2
>SEE ALSO</H2
@@ -19301,7 +19436,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN6080"
+NAME="AEN6115"
></A
><H2
>AUTHOR</H2
diff --git a/docs/htmldocs/smbd.8.html b/docs/htmldocs/smbd.8.html
index e093a05f646..be82ef6d4ec 100644
--- a/docs/htmldocs/smbd.8.html
+++ b/docs/htmldocs/smbd.8.html
@@ -36,7 +36,7 @@ NAME="AEN8"
><B
CLASS="COMMAND"
>smbd</B
-> [-D] [-a] [-o] [-P] [-h] [-V] [-d &#60;debug level&#62;] [-l &#60;log directory&#62;] [-p &#60;port number&#62;] [-O &#60;socket option&#62;] [-s &#60;configuration file&#62;]</P
+> [-D] [-a] [-o] [-P] [-h] [-V] [-d &#60;debug level&#62;] [-l &#60;log file&#62;] [-p &#60;port number&#62;] [-O &#60;socket option&#62;] [-s &#60;configuration file&#62;]</P
></DIV
><DIV
CLASS="REFSECT1"
@@ -228,19 +228,17 @@ CLASS="FILENAME"
> file.</P
></DD
><DT
->-l &#60;log directory&#62;</DT
+>-l &#60;log file&#62;</DT
><DD
><P
->If specified,
- <TT
+>If specified, <TT
CLASS="REPLACEABLE"
><I
->log directory</I
+>log file</I
></TT
>
- specifies a log directory into which the "log.smbd" log
- file will be created for informational and debug
- messages from the running server. The log
+ specifies a log filename into which informational and debug
+ messages from the running server will be logged. The log
file generated is never removed by the server although
its size may be controlled by the <A
HREF="smb.conf.5.html#maxlogsize"
@@ -254,11 +252,8 @@ TARGET="_top"
CLASS="FILENAME"
> smb.conf(5)</TT
></A
-> file.
- </P
-><P
->The default log directory is specified at
- compile time.</P
+> file. The default log
+ file name is specified at compile time.</P
></DD
><DT
>-O &#60;socket options&#62;</DT
@@ -336,7 +331,7 @@ CLASS="FILENAME"
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN110"
+NAME="AEN109"
></A
><H2
>FILES</H2
@@ -434,7 +429,7 @@ CLASS="FILENAME"
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN143"
+NAME="AEN142"
></A
><H2
>LIMITATIONS</H2
@@ -453,7 +448,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN147"
+NAME="AEN146"
></A
><H2
>ENVIRONMENTVARIABLES</H2
@@ -484,7 +479,7 @@ CLASS="CONSTANT"
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN156"
+NAME="AEN155"
></A
><H2
>INSTALLATION</H2
@@ -606,7 +601,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN189"
+NAME="AEN188"
></A
><H2
>RUNNING THE SERVER AS A DAEMON</H2
@@ -661,7 +656,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN202"
+NAME="AEN201"
></A
><H2
>RUNNING THE SERVER ON REQUEST</H2
@@ -797,7 +792,7 @@ CLASS="COMPUTEROUTPUT"
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN234"
+NAME="AEN233"
></A
><H2
>PAM INTERACTION</H2
@@ -842,7 +837,7 @@ TARGET="_top"
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN245"
+NAME="AEN244"
></A
><H2
>TESTING THE INSTALLATION</H2
@@ -900,7 +895,7 @@ CLASS="FILENAME"
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN259"
+NAME="AEN258"
></A
><H2
>VERSION</H2
@@ -911,7 +906,7 @@ NAME="AEN259"
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN262"
+NAME="AEN261"
></A
><H2
>DIAGNOSTICS</H2
@@ -934,7 +929,7 @@ NAME="AEN262"
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN267"
+NAME="AEN266"
></A
><H2
>SIGNALS</H2
@@ -999,7 +994,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN284"
+NAME="AEN283"
></A
><H2
>SEE ALSO</H2
@@ -1065,7 +1060,7 @@ TARGET="_top"
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN301"
+NAME="AEN300"
></A
><H2
>AUTHOR</H2
diff --git a/docs/htmldocs/winbind.html b/docs/htmldocs/winbind.html
index 8ab39e5903d..addf74935c1 100644
--- a/docs/htmldocs/winbind.html
+++ b/docs/htmldocs/winbind.html
@@ -759,29 +759,11 @@ CLASS="PROMPT"
>I'm always paranoid and like to make sure the daemon
is really running...</P
><P
-><PRE
-CLASS="PROGRAMLISTING"
><TT
CLASS="PROMPT"
>root# </TT
> ps -ae | grep winbindd
-3025 ? 00:00:00 winbindd</PRE
-></P
-><P
->The reply <B
-CLASS="COMMAND"
->3025 ? 00:00:00 winbind</B
->' indicates that
-I have <B
-CLASS="COMMAND"
->winbindd</B
-> running as process #3025 on my system. You will get a
-different process number, but you should see the <B
-CLASS="COMMAND"
->winbindd</B
->
-daemon. If it is NOT running, you will get no response from your system and will
-simply be returned the command prompt.</P
+3025 ? 00:00:00 winbindd</P
><P
>Now... for the real test, try to get some information about the
users on your PDC</P
@@ -855,7 +837,7 @@ CLASS="SECT3"
><HR><H3
CLASS="SECT3"
><A
-NAME="AEN188"
+NAME="AEN183"
>Fix the /etc/rc.d/init.d/smb startup files</A
></H3
><P
@@ -950,7 +932,7 @@ CLASS="SECT3"
><HR><H3
CLASS="SECT3"
><A
-NAME="AEN205"
+NAME="AEN200"
>Configure Winbind and PAM</A
></H3
><P
@@ -1108,7 +1090,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
-NAME="AEN246"
+NAME="AEN241"
>Limitations</A
></H1
><P
@@ -1149,7 +1131,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
-NAME="AEN256"
+NAME="AEN251"
>Conclusion</A
></H1
><P
diff --git a/docs/htmldocs/winbindd.8.html b/docs/htmldocs/winbindd.8.html
index 0147861284f..ad54228a6f4 100644
--- a/docs/htmldocs/winbindd.8.html
+++ b/docs/htmldocs/winbindd.8.html
@@ -77,30 +77,6 @@ CLASS="COMMAND"
Windows NT server. The service can also provide authentication
services via an associated PAM module. </P
><P
-> The <TT
-CLASS="FILENAME"
->pam_winbind</TT
-> module in the 2.2.2 release only
- supports the <TT
-CLASS="PARAMETER"
-><I
->auth</I
-></TT
-> and <TT
-CLASS="PARAMETER"
-><I
->account</I
-></TT
->
- module-types. The latter is simply
- performs a getpwnam() to verify that the system can obtain a uid for the
- user. If the <TT
-CLASS="FILENAME"
->libnss_winbind</TT
-> library has been correctly
- installed, this should always suceed.
- </P
-><P
>The following nsswitch databases are implemented by
the winbindd service: </P
><P
@@ -173,7 +149,7 @@ group: files winbind
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN48"
+NAME="AEN43"
></A
><H2
>OPTIONS</H2
@@ -212,7 +188,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN61"
+NAME="AEN56"
></A
><H2
>NAME AND ID RESOLUTION</H2
@@ -243,7 +219,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN67"
+NAME="AEN62"
></A
><H2
>CONFIGURATION</H2
@@ -508,7 +484,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN149"
+NAME="AEN144"
></A
><H2
>EXAMPLE SETUP</H2
@@ -686,7 +662,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN188"
+NAME="AEN183"
></A
><H2
>NOTES</H2
@@ -744,7 +720,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN204"
+NAME="AEN199"
></A
><H2
>SIGNALS</H2
@@ -795,7 +771,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN221"
+NAME="AEN216"
></A
><H2
>FILES</H2
@@ -871,7 +847,7 @@ CLASS="FILENAME"
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN250"
+NAME="AEN245"
></A
><H2
>VERSION</H2
@@ -882,7 +858,7 @@ NAME="AEN250"
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN253"
+NAME="AEN248"
></A
><H2
>SEE ALSO</H2
@@ -910,7 +886,7 @@ TARGET="_top"
><DIV
CLASS="REFSECT1"
><A
-NAME="AEN260"
+NAME="AEN255"
></A
><H2
>AUTHOR</H2
generated by cgit (git 2.34.1) at 2025-09-16 13:40:21 +0000