Ignore:
Timestamp:
Jun 17, 2009, 2:19:52 PM (16 years ago)
Author:
Herwig Bauernfeind
Message:

Update 3.3 branch to 3.3.5

Location:
branches/samba-3.3.x/docs-xml
Files:
13 edited

Legend:

Unmodified
Added
Removed

  • branches/samba-3.3.x/docs-xml/Samba3-ByExample/SBE-KerberosFastStart.xml

    r217 r274  
    13691369        <orderedlist>
    13701370                <listitem><para>
    1371                 A user opens a Work document from a network drive. The file was owned by user <constant>janetp</constant>
     1371                A user opens a Word document from a network drive. The file was owned by user <constant>janetp</constant>
    13721372                and <group>users</group>, and was set read/write-enabled for everyone.
     1373                A user opens a Word document from a network drive. The file was owned by user <constant>janetp</constant>
     1374                and <constant>users</constant>, and was set read/write-enabled for everyone.
    13731375                </para></listitem>
    13741376

  • branches/samba-3.3.x/docs-xml/Samba3-HOWTO/TOSHARG-FastStart.xml

    r217 r274  
    12151215<smbconfoption name="ldap group suffix">ou=People</smbconfoption>
    12161216<smbconfoption name="ldap idmap suffix">ou=People</smbconfoption>
    1217 <smbconfoption name="ldap admin dn">cn=Manager</smbconfoption>
     1217<smbconfoption name="ldap admin dn">cn=Manager,dc=quenya,dc=org</smbconfoption>
    12181218<smbconfoption name="ldap ssl">no</smbconfoption>
    12191219<smbconfoption name="ldap passwd sync">Yes</smbconfoption>
    … …  
    12821282<smbconfoption name="ldap group suffix">ou=People</smbconfoption>
    12831283<smbconfoption name="ldap idmap suffix">ou=People</smbconfoption>
    1284 <smbconfoption name="ldap admin dn">cn=Manager</smbconfoption>
     1284<smbconfoption name="ldap admin dn">cn=Manager,dc=quenya,dc=org</smbconfoption>
    12851285<smbconfoption name="ldap ssl">no</smbconfoption>
    12861286<smbconfoption name="ldap passwd sync">Yes</smbconfoption>

  • branches/samba-3.3.x/docs-xml/Samba3-HOWTO/TOSHARG-Install.xml

    r217 r274  
    335335                <varlistentry><term>nmbd</term>
    336336                        <listitem><para>
    337                         <indexterm><primary>smbd</primary></indexterm>
    338                         <indexterm><primary>starting samba</primary><secondary>smbd</secondary></indexterm>
     337                        <indexterm><primary>nmbd</primary></indexterm>
     338                        <indexterm><primary>starting samba</primary><secondary>nmbd</secondary></indexterm>
    339339                        This daemon handles all name registration and resolution requests. It is the primary vehicle involved
    340340                        in network browsing. It handles all UDP-based protocols. The <command>nmbd</command> daemon should
    … …  
    345345                <varlistentry><term>smbd</term>
    346346                        <listitem><para>
    347                         <indexterm><primary>nmbd</primary></indexterm>
    348                         <indexterm><primary>starting samba</primary><secondary>nmbd</secondary></indexterm>
     347                        <indexterm><primary>smbd</primary></indexterm>
     348                        <indexterm><primary>starting samba</primary><secondary>smbd</secondary></indexterm>
    349349                        This daemon handles all TCP/IP-based connection services for file- and print-based operations. It also
    350350                        manages local authentication. It should be started immediately following the startup of <command>nmbd</command>.
    … …  
    468468        be adopted is to do all documentation and configuration in a file that has another name, such as
    469469        <filename>smb.conf.master</filename>. The <command>testparm</command> utility can be used to generate a
    470         fully optimized &smb.conf; file from this master configuration and documtenation file as shown here:
     470        fully optimized &smb.conf; file from this master configuration and documentation file as shown here:
    471471<screen>
    472472&rootprompt; testparm -s smb.conf.master > smb.conf
    … …  
    485485        <indexterm><primary>swat</primary></indexterm>
    486486        SWAT is a Web-based interface that can be used to facilitate the configuration of Samba.  SWAT might not
    487         be available in the Samba package that shipped with your platform, but in a separate package. If it is
    488         necesaary to built SWAT please read the SWAT man page regarding compilation, installation, and
     487        be available in the Samba package that shipped with your platform, but in a separate package. If you need to build SWAT please read the SWAT man page regarding compilation, installation, and
    489488        configuration of SWAT from the source code.
    490489        </para>
    … …  
    499498        <para>
    500499        SWAT can be used from a browser on any IP-connected machine, but be aware that connecting from a remote
    501         machine leaves your connection open to password sniffing because passwords will be sent over the wire in the clear.
    502         </para>
    503 
    504         <para>
     500        machine leaves your connection open to password sniffing because passwords will be sent over the wire in the clear.
     501        </para>
     502
     503        <para>
     504        Please note that re-writing the configuration file using SWAT will
     505        remove all comments!
    505506        More information about SWAT can be found in <link linkend="SWAT">The Samba Web Administration Tool</link>.
    506507        </para>

  • branches/samba-3.3.x/docs-xml/Samba3-HOWTO/TOSHARG-PDC.xml

    r217 r274  
    307307SSO implementations utilize centralization of all user account information. Depending on environmental
    308308complexity and the age of the systems over which a SSO solution is implemented, it may not be possible to
    309 change the solution architecture so as to accomodate a new identity management and user authentication system.
     309change the solution architecture so as to accommodate a new identity management and user authentication system.
    310310Many SSO solutions involving legacy systems consist of a new super-structure that handles authentication on
    311311behalf of the user. The software that gets layered over the old system may simply implement a proxy
    … …  
    376376alternative specification called WS-Security. Some believe that the competing technologies and methods may
    377377converge when the SAML 2.0 standard is introduced. A few Web access-management products support SAML today,
    378 but implemention of the technology mostly requires customization to integrate applications and develop user
    379 interfaces. In a nust-shell, that is why FIM is a big and growing industry.
     378but implementation of the technology mostly requires customization to integrate applications and develop user
     379interfaces. In a nutshell, that is why FIM is a big and growing industry.
    380380</para>
    381381

  • branches/samba-3.3.x/docs-xml/Samba3-HOWTO/TOSHARG-Passdb.xml

    r217 r274  
    758758                The POSIX and sambaSamAccount components of computer (machine) accounts are both used by Samba.
    759759                Thus, machine accounts are treated inside Samba in the same way that Windows NT4/200X treats
    760                 them. A user account and a machine account are indistinquishable from each other, except that
     760                them. A user account and a machine account are indistinguishable from each other, except that
    761761                the machine account ends in a $ character, as do trust accounts.
    762762                </para>
    … …  
    10511051                    </row>
    10521052                    <row>
    1053                                         <entry><para>Mimimum Password Length</para></entry>
     1053                                        <entry><para>Minimum Password Length</para></entry>
    10541054                                        <entry><para>min password length</para></entry>
    10551055                                        <entry><para>1 - 14 (Chars)</para></entry>
    … …  
    16161616account policy value for maximum password age was 4294967295
    16171617account policy value for maximum password age is now 7776000
    1618 &rootprompt; pdbedit -P "minimum password age" -C 7
     1618&rootprompt; pdbedit -P "minimum password age" -C 604800
    16191619account policy value for minimum password age was 0
    16201620account policy value for minimum password age is now 7
    … …  
    17361736<indexterm><primary>lookups</primary></indexterm>
    17371737                The first problem is that all lookups must be performed sequentially. Given that
    1738                 there are approximately two lookups per domain logon (one during intial logon validation
     1738                there are approximately two lookups per domain logon (one during initial logon validation
    17391739                and one for a session connection setup, such as when mapping a network drive or printer), this
    17401740                is a performance bottleneck for large sites. What is needed is an indexed approach
    … …  
    26272627
    26282628                <sect3>
    2629                 <title>Using OpenLDAP Overlay for Password Syncronization</title>
     2629                <title>Using OpenLDAP Overlay for Password Synchronization</title>
    26302630
    26312631                <para>

  • branches/samba-3.3.x/docs-xml/Samba3-HOWTO/TOSHARG-VFS.xml

    r217 r274  
    277277                <para>
    278278<indexterm><primary>logging</primary></indexterm>
    279                 This auditing tool is more felxible than most people readily will recognize. There are a number of ways
     279                This auditing tool is more flexible than most people will readily recognize. There are a number of ways
    280280                by which useful logging information can be recorded.
    281281                </para>

  • branches/samba-3.3.x/docs-xml/Samba3-HOWTO/TOSHARG-foreword-cargill.xml

    r217 r274  
    3939<para>
    4040A <emphasis>good standard</emphasis> survives because people know how to use it. People know how to use a
    41 standard when it is so transparent, so obvious, and so easy that it become invisible. And a standard becomes
     41standard when it is so transparent, so obvious, and so easy that it becomes invisible. And a standard becomes
    4242invisible only when the documentation describing how to deploy it is clear, unambiguous, and correct. These
    4343three elements must be present for a standard to be useful, allowing communication and interaction between two

  • branches/samba-3.3.x/docs-xml/Samba3-HOWTO/index.xml

    r217 r274  
    44<book id="Samba-HOWTO-Collection"
    55        xmlns:xi="http://www.w3.org/2003/XInclude">
    6 <title>The Official Samba 3.2.x HOWTO and Reference Guide</title>
     6<title>The Official Samba 3.3.x HOWTO and Reference Guide</title>
    77
    88<bookinfo>

  • branches/samba-3.3.x/docs-xml/Samba3-HOWTO/manpages.xml

    r217 r274  
    2323        <xi:include href="../manpages-3/nmblookup.1.xml"/>
    2424        <xi:include href="../manpages-3/ntlm_auth.1.xml"/>
    25         <xi:include href="../manpages-3/pam_winbind.7.xml"/>
     25        <xi:include href="../manpages-3/pam_winbind.8.xml"/>
    2626        <xi:include href="../manpages-3/pdbedit.8.xml"/>
    2727        <xi:include href="../manpages-3/profiles.1.xml"/>

  • branches/samba-3.3.x/docs-xml/manpages-3/net.8.xml

    r224 r274  
    15831583
    15841584<refsect2>
     1585<title>DOM</title>
     1586
     1587<para>Starting with version 3.2.0 Samba has support for remote join and unjoin APIs, both client and server-side. Windows supports remote join capabilities since Windows 2000.
     1588</para>
     1589<para>In order for Samba to be joined or unjoined remotely an account must be used that is either member of the Domain Admins group, a member of the local Administrators group or a user that is granted the SeMachineAccountPrivilege privilege.
     1590</para>
     1591
     1592<para>The client side support for remote join is implemented in the net dom commands which are:
     1593<simplelist>
     1594<member>net dom join - Join a remote computer into a domain.</member>
     1595<member>net dom unjoin - Unjoin a remote computer from a domain.</member>
     1596</simplelist>
     1597</para>
     1598
     1599<refsect3>
     1600<title>DOM JOIN <replaceable>domain=DOMAIN</replaceable> <replaceable>ou=OU</replaceable> <replaceable>account=ACCOUNT</replaceable> <replaceable>password=PASSWORD</replaceable> <replaceable>reboot</replaceable></title>
     1601
     1602<para>
     1603Joins a computer into a domain. This command supports the following additional parameters:
     1604</para>
     1605
     1606<itemizedlist>
     1607
     1608<listitem><para><replaceable>DOMAIN</replaceable> can be a NetBIOS domain name (also known as short domain name) or a DNS domain name for Active Directory Domains. As in Windows, it is also possible to control which Domain Controller to use. This can be achieved by appending the DC name using the \ separator character. Example: MYDOM\MYDC. The <replaceable>DOMAIN</replaceable> parameter cannot be NULL.</para></listitem>
     1609
     1610<listitem><para><replaceable>OU</replaceable> can be set to a RFC 1779 LDAP DN, like <emphasis>ou=mymachines,cn=Users,dc=example,dc=com</emphasis> in order to create the machine account in a non-default LDAP containter. This optional parameter is only supported when joining Active Directory Domains.</para></listitem>
     1611
     1612<listitem><para><replaceable>ACCOUNT</replaceable> defines a domain account that will be used to join the machine to the domain. This domain account needs to have sufficient privileges to join machines.</para></listitem>
     1613
     1614<listitem><para><replaceable>PASSWORD</replaceable> defines the password for the domain account defined with <replaceable>ACCOUNT</replaceable>.</para></listitem>
     1615
     1616<listitem><para><replaceable>REBOOT</replaceable> is an optional parameter that can be set to reboot the remote machine after successful join to the domain.</para></listitem>
     1617
     1618</itemizedlist>
     1619
     1620<para>
     1621Note that you also need to use standard net paramters to connect and authenticate to the remote machine that you want to join. These additional parameters include: -S computer and -U user.
     1622</para>
     1623<para>
     1624        Example:
     1625        net dom join -S xp -U XP\\administrator%secret domain=MYDOM account=MYDOM\\administrator password=topsecret reboot.
     1626</para>
     1627<para>
     1628This example would connect to a computer named XP as the local administrator using password secret, and join the computer into a domain called MYDOM using the MYDOM domain administrator account and password topsecret. After successful join, the computer would reboot.
     1629</para>
     1630
     1631</refsect3>
     1632
     1633<refsect3>
     1634<title>DOM UNJOIN <replaceable>account=ACCOUNT</replaceable> <replaceable>password=PASSWORD</replaceable> <replaceable>reboot</replaceable></title>
     1635
     1636<para>
     1637Unjoins a computer from a domain. This command supports the following additional parameters:
     1638</para>
     1639
     1640<itemizedlist>
     1641
     1642<listitem><para><replaceable>ACCOUNT</replaceable> defines a domain account that will be used to unjoin the machine from the domain. This domain account needs to have sufficient privileges to unjoin machines.</para></listitem>
     1643
     1644<listitem><para><replaceable>PASSWORD</replaceable> defines the password for the domain account defined with <replaceable>ACCOUNT</replaceable>.</para></listitem>
     1645
     1646<listitem><para><replaceable>REBOOT</replaceable> is an optional parameter that can be set to reboot the remote machine after successful unjoin from the domain.</para></listitem>
     1647
     1648</itemizedlist>
     1649
     1650<para>
     1651Note that you also need to use standard net paramters to connect and authenticate to the remote machine that you want to unjoin. These additional parameters include: -S computer and -U user.
     1652</para>
     1653<para>
     1654        Example:
     1655        net dom unjoin -S xp -U XP\\administrator%secret account=MYDOM\\administrator password=topsecret reboot.
     1656</para>
     1657<para>
     1658This example would connect to a computer named XP as the local administrator using password secret, and unjoin the computer from the domain using the MYDOM domain administrator account and password topsecret. After successful unjoin, the computer would reboot.
     1659</para>
     1660
     1661</refsect3>
     1662
     1663</refsect2>
     1664
     1665<refsect2>
     1666
    15851667<title>HELP [COMMAND]</title>
    15861668

  • branches/samba-3.3.x/docs-xml/smbdotconf/logon/abortshutdownscript.xml

    r217 r274  
    1010               
    1111        <para>If the connected user posseses the <constant>SeRemoteShutdownPrivilege</constant>,
    12         right, this command will be run as user.</para>
     12        right, this command will be run as root.</para>
    1313</description>
    1414<value type="default">&quot;&quot;</value>

  • branches/samba-3.3.x/docs-xml/smbdotconf/logon/shutdownscript.xml

    r217 r274  
    1111
    1212        <para>If the connected user posseses the <constant>SeRemoteShutdownPrivilege</constant>,
    13         right, this command will be run as user.</para>
     13        right, this command will be run as root.</para>
    1414
    1515        <para>The %z %t %r %f variables are expanded as follows:</para>
    … …  
    4343<programlisting format="linespecific">
    4444#!/bin/bash
    45                
    46 $time=0
    47 let &quot;time/60&quot;
    48 let &quot;time++&quot;
     45
     46time=$2
     47let time=&quot;${time} / 60&quot;
     48let time=&quot;${time} + 1&quot;
    4949
    5050/sbin/shutdown $3 $4 +$time $1 &amp;
     51
    5152</programlisting>
    5253        Shutdown does not return so we need to launch it in background.

  • branches/samba-3.3.x/docs-xml/smbdotconf/protocol/unixextensions.xml

    r217 r274  
    55                 xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
    66 <description>
    7     <para>This boolean parameter controls whether Samba 
    8     implments the CIFS UNIX extensions, as defined by HP.
     7    <para>This boolean parameter controls whether Samba
     8    implements the CIFS UNIX extensions, as defined by HP.
    99    These extensions enable Samba to better serve UNIX CIFS clients
    1010    by supporting features such as symbolic links, hard links, etc...
Note: See TracChangeset for help on using the changeset viewer.