Timestamp:
Jun 16, 2009, 5:52:30 PM (16 years ago)
Author:
Herwig Bauernfeind
Message:

Update 3.2 to 3.2.12

Location:
branches/samba-3.2.x/docs-xml
Files:
12 edited

Legend:

Unmodified
Added
Removed
  • branches/samba-3.2.x/docs-xml/Samba3-ByExample/SBE-KerberosFastStart.xml

    r203 r272  
    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 Wor 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
     1374
    13731375                </para></listitem>
    13741376
  • branches/samba-3.2.x/docs-xml/Samba3-HOWTO/TOSHARG-FastStart.xml

    r203 r272  
    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</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</smbconfoption>
    12851285<smbconfoption name="ldap ssl">no</smbconfoption>
    12861286<smbconfoption name="ldap passwd sync">Yes</smbconfoption>
  • branches/samba-3.2.x/docs-xml/Samba3-HOWTO/TOSHARG-Install.xml

    r203 r272  
    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>mbd</primary></indexterm>
     338                        <indexterm><primary>starting samba</primary><secondary>mbd</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>mbd</primary></indexterm>
     348                        <indexterm><primary>starting samba</primary><secondary>mbd</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 documation 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.2.x/docs-xml/Samba3-HOWTO/TOSHARG-PDC.xml

    r203 r272  
    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 accomodate 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 implemention of the technology mostly requires customization to integrate applications and develop user
     379interfaces. In a nushell, that is why FIM is a big and growing industry.
    380380</para>
    381381
  • branches/samba-3.2.x/docs-xml/Samba3-HOWTO/TOSHARG-Passdb.xml

    r203 r272  
    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 indistinuishable 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>Miimum 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
    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 intial 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 Syncronization</title>
    26302630
    26312631                <para>
  • branches/samba-3.2.x/docs-xml/Samba3-HOWTO/TOSHARG-VFS.xml

    r203 r272  
    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 f recognize. There are a number of ways
    280280                by which useful logging information can be recorded.
    281281                </para>
  • branches/samba-3.2.x/docs-xml/Samba3-HOWTO/TOSHARG-foreword-cargill.xml

    r203 r272  
    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 become 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.2.x/docs-xml/Samba3-HOWTO/manpages.xml

    r203 r272  
    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..xml"/>
    2626        <xi:include href="../manpages-3/pdbedit.8.xml"/>
    2727        <xi:include href="../manpages-3/profiles.1.xml"/>
  • branches/samba-3.2.x/docs-xml/manpages-3/net.8.xml

    r227 r272  
    3636                <arg choice="opt">-d debuglevel</arg>
    3737                <arg choice="opt">-V</arg>
     38
    3839        </cmdsynopsis>
    3940</refsynopsisdiv>
     
    123124                <listitem><para>
    124125                Make queries to the external server using the machine account of the local server.
     126
     127
     128
     129
     130
     131
     132
     133
    125134                </para></listitem>
    126135                </varlistentry>
     
    15611570
    15621571<refsect2>
     1572
     1573
     1574
     1575
     1576
     1577
     1578
     1579
     1580
     1581
     1582
     1583
     1584
     1585
     1586
     1587
     1588
     1589
     1590
     1591
     1592
     1593
     1594
     1595
     1596
     1597
     1598
     1599
     1600
     1601
     1602
     1603
     1604
     1605
     1606
     1607
     1608
     1609
     1610
     1611
     1612
     1613
     1614
     1615
     1616
     1617
     1618
     1619
     1620
     1621
     1622
     1623
     1624
     1625
     1626
     1627
     1628
     1629
     1630
     1631
     1632
     1633
     1634
     1635
     1636
     1637
     1638
     1639
     1640
     1641
     1642
     1643
     1644
     1645
     1646
     1647
     1648
     1649
     1650
     1651
     1652
     1653
    15631654<title>HELP [COMMAND]</title>
    15641655
  • branches/samba-3.2.x/docs-xml/smbdotconf/logon/abortshutdownscript.xml

    r203 r272  
    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 .</para>
    1313</description>
    1414<value type="default">&quot;&quot;</value>
  • branches/samba-3.2.x/docs-xml/smbdotconf/logon/shutdownscript.xml

    r203 r272  
    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 .</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 60&quot;
     48let &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.2.x/docs-xml/smbdotconf/protocol/unixextensions.xml

    r203 r272  
    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    impl
    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.