Ignore:
Timestamp:
Nov 27, 2012, 4:56:06 PM (13 years ago)
Author:
Silvan Scherrer
Message:

Samba Server: updated vendor to 3.6.9

Location:
vendor/current/docs-xml/manpages-3
Files:
21 edited

Legend:

Unmodified
Added
Removed

  • vendor/current/docs-xml/manpages-3/idmap_autorid.8.xml

    r740 r746  
    5252                        plan accordingly for your expected number of users in a domain
    5353                        with safety margins.
    54                 </para>
     54                        </para>
     55                        <para>One range will be used for local users and groups.
     56                        Thus the number of local users and groups that can be created is
     57                        limited by this option as well. If you plan to create a large amount
     58                        of local users or groups, you will need set this parameter accordingly.
     59                        </para>
    5560                <para>The default value is 100000.</para>
    5661                </listitem>

  • vendor/current/docs-xml/manpages-3/idmap_nss.8.xml

    r740 r746  
    2121
    2222        <para>The idmap_nss plugin provides a means to map Unix users and groups
    23         to Windows accounts and obseletes the &quot;winbind trusted domains only&quot;
     23        to Windows accounts and obsoletes the &quot;winbind trusted domains only&quot;
    2424        smb.conf option.  This provides a simple means of ensuring that the SID
    2525        for a Unix user named jsmith is reported as the one assigned to

  • vendor/current/docs-xml/manpages-3/libsmbclient.7.xml

    r740 r746  
    7272                        is a compile-time option. This value determines the maximum number of local master browsers to
    7373                        query for the list of workgroups.  In order to ensure that the list is complete for those present
    74                         on the network, all master browsers must be querried. If there are a large number of workgroups
     74                        on the network, all master browsers must be queried. If there are a large number of workgroups
    7575                        on the network, the time spent querying will be significant. For small networks (just a few
    7676                        workgroups), it is suggested to set this value to 0, instructing libsmbclient to query all local

  • vendor/current/docs-xml/manpages-3/net.8.xml

    r740 r746  
    6262        <variablelist>
    6363                &stdarg.help;
     64                &stdarg.kerberos;
    6465               
    6566                <varlistentry>
    … …  
    21052106<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>
    21062107
    2107 <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>
     2108<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 container. This optional parameter is only supported when joining Active Directory Domains.</para></listitem>
    21082109
    21092110<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>

  • vendor/current/docs-xml/manpages-3/ntlm_auth.1.xml

    r740 r746  
    200200                the client.
    201201                </para>
    202                       <para><example>LANMAN-Challege: 0102030405060708</example></para>
     202                      <para><example>LANMAN-Challenge: 0102030405060708</example></para>
    203203                    </listitem></varlistentry>
    204204
    … …  
    240240                  <varlistentry>
    241241                  <term>Request-User-Session-Key</term>
    242                 <listitem><para>Apon sucessful authenticaiton, return
     242                <listitem><para>Upon successful authenticaiton, return
    243243                the user session key associated with the login.
    244244                 </para>       
    … …  
    249249                  <varlistentry>
    250250                  <term>Request-LanMan-Session-Key</term>
    251                 <listitem><para>Apon sucessful authenticaiton, return
     251                <listitem><para>Upon successful authenticaiton, return
    252252                the LANMAN session key associated with the login.
    253253                 </para>       
    … …  
    256256                    </listitem></varlistentry>
    257257
    258                 <para><warning>Implementors should take care to base64 encode
     258                <para><warning>Implementers should take care to base64 encode
    259259                any data (such as usernames/passwords) that may contain malicous user data, such as
    260260                a newline.  They may also need to decode strings from
    … …  
    320320        <varlistentry>
    321321        <term>--request-lm-key</term>
    322         <listitem><para>Retreive LM session key</para></listitem>
     322        <listitem><para>Retrieve LM session key</para></listitem>
    323323        </varlistentry>
    324324
    … …  
    381381       
    382382        <para>If you're experiencing problems with authenticating Internet Explorer running
    383         under MS Windows 9X or Millenium Edition against ntlm_auth's NTLMSSP authentication
     383        under MS Windows 9X or Millennium Edition against ntlm_auth's NTLMSSP authentication
    384384        helper (--helper-protocol=squid-2.5-ntlmssp), then please read
    385385        <ulink url="http://support.microsoft.com/support/kb/articles/Q239/8/69.ASP">

  • vendor/current/docs-xml/manpages-3/pdbedit.8.xml

    r740 r746  
    7373
    7474        <para>There are five main ways to use pdbedit: adding a user account,
    75         removing a user account, modifing a user account, listing user
     75        removing a user account, modifying a user account, listing user
    7676        accounts, importing users accounts.</para>
    7777</refsect1>
    … …  
    163163                <term>-f|--fullname fullname</term>
    164164                <listitem><para>This option can be used while adding or
    165                 modifing a user account. It will specify the user's full
     165                modifying a user account. It will specify the user's full
    166166                name. </para>
    167167
    … …  
    173173                <term>-h|--homedir homedir</term>
    174174                <listitem><para>This option can be used while adding or
    175                 modifing a user account. It will specify the user's home
     175                modifying a user account. It will specify the user's home
    176176                directory network path.</para>
    177177
    … …  
    184184                <term>-D|--drive drive</term>
    185185                <listitem><para>This option can be used while adding or
    186                 modifing a user account. It will specify the windows drive
     186                modifying a user account. It will specify the windows drive
    187187                letter to be used to map the home directory.</para>
    188188
    … …  
    196196                <term>-S|--script script</term>
    197197                <listitem><para>This option can be used while adding or
    198                 modifing a user account. It will specify the user's logon
     198                modifying a user account. It will specify the user's logon
    199199                script path.</para>
    200200
    … …  
    208208                <term>-p|--profile profile</term>
    209209                <listitem><para>This option can be used while adding or
    210                 modifing a user account. It will specify the user's profile
     210                modifying a user account. It will specify the user's profile
    211211                directory.</para>
    212212
    … …  
    448448                <term>-N|--account-desc description</term>
    449449                <listitem><para>This option can be used while adding or
    450                 modifing a user account. It will specify the user's description
     450                modifying a user account. It will specify the user's description
    451451                field.</para>
    452452
    … …  
    459459                <term>-Z|--logon-hours-reset</term>
    460460                <listitem><para>This option can be used while adding or
    461                 modifing a user account. It will reset the user's allowed logon
     461                modifying a user account. It will reset the user's allowed logon
    462462                hours. A user may login at any time afterwards.</para>
    463463
    … …  
    470470                <term>-z|--bad-password-count-reset</term>
    471471                <listitem><para>This option can be used while adding or
    472                 modifing a user account. It will reset the stored bad login
     472                modifying a user account. It will reset the stored bad login
    473473                counter from a specified user.</para>
    474474
    … …  
    491491                <term>-I|--domain</term>
    492492                <listitem><para>This option can be used while adding or
    493                 modifing a user account. It will specify the user's domain field.</para>
     493                modifying a user account. It will specify the user's domain field.</para>
    494494
    495495                <para>Example: <command>-I "MYDOMAIN"</command>

  • vendor/current/docs-xml/manpages-3/profiles.1.xml

    r740 r746  
    5959                <varlistentry>
    6060                <term>-c SID1 -n SID2</term>
    61                 <listitem><para>Change all occurences of SID1 in <filename>file</filename> by SID2.
     61                <listitem><para>Change all occurrences of SID1 in <filename>file</filename> by SID2.
    6262                </para></listitem>
    6363                </varlistentry>

  • vendor/current/docs-xml/manpages-3/samba.7.xml

    r740 r746  
    217217                <manvolnum>1</manvolnum></citerefentry></term>
    218218                <listitem><para><command>profiles</command> is a command-line
    219                 utility that can be used to replace all occurences of
     219                utility that can be used to replace all occurrences of
    220220                a certain SID with another SID.
    221221                </para></listitem>

  • vendor/current/docs-xml/manpages-3/smbcacls.1.xml

    r740 r746  
    2121                <command>smbcacls</command>
    2222                <arg choice="req">//server/share</arg>
    23                 <arg choice="req">filename</arg>
     23                <arg choice="req">/filename</arg>
    2424                <arg choice="opt">-D|--delete acls</arg>
    2525                <arg choice="opt">-M|--modify acls</arg>

  • vendor/current/docs-xml/manpages-3/smbclient.1.xml

    r740 r746  
    323323                encrypted. This is new for Samba 3.2 and will only work with Samba
    324324                3.2 or above servers. Negotiates SMB encryption using GSSAPI. Uses
    325                 the given credentials for the encryption negotiaion (either kerberos
     325                the given credentials for the encryption negotiation (either kerberos
    326326                or NTLMv1/v2 if given domain/username/password triple. Fails the
    327327                connection if encryption cannot be negotiated.
    … …  
    429429                (no password on share). </para>
    430430               
    431                 <para><command>smbclient //mypc/yshare "" -N -Tx backup.tar
     431                <para><command>smbclient //mypc/myshare "" -N -Tx backup.tar
    432432                </command></para>
    433433               
    … …  
    635635                <varlistentry>
    636636                <term>du &lt;filename&gt;</term>
    637                 <listitem><para>Does a directory listing and then prints out the current disk useage and free space on a share.
     637                <listitem><para>Does a directory listing and then prints out the current disk usage and free space on a share.
    638638                </para></listitem>
    639639                </varlistentry>

  • vendor/current/docs-xml/manpages-3/smbcontrol.1.xml

    r740 r746  
    215215        <para>
    216216        Note that this message only sends notification that an
    217         event has occured.  It doesn't actually cause the
     217        event has occurred.  It doesn't actually cause the
    218218        event to happen.
    219219        </para>

  • vendor/current/docs-xml/manpages-3/smbcquotas.1.xml

    r740 r746  
    119119
    120120<refsect1>
    121         <title>QUOTA_SET_COMAND</title>
     121        <title>QUOTA_SET_COMMAND</title>
    122122
    123123        <para>The format of an the QUOTA_SET_COMMAND is an operation

  • vendor/current/docs-xml/manpages-3/smbd.8.xml

    r740 r746  
    240240        session management.  The degree too which samba supports PAM is restricted
    241241        by the limitations of the SMB protocol and the <smbconfoption name="obey pam restrictions"/> <citerefentry><refentrytitle>smb.conf</refentrytitle>
    242         <manvolnum>5</manvolnum></citerefentry> paramater.  When this is set, the following restrictions apply:
     242        <manvolnum>5</manvolnum></citerefentry> parameter.  When this is set, the following restrictions apply:
    243243        </para>
    244244
    … …  
    246246        <listitem><para><emphasis>Account Validation</emphasis>:  All accesses to a
    247247        samba server are checked
    248         against PAM to see if the account is vaild, not disabled and is permitted to
     248        against PAM to see if the account is valid, not disabled and is permitted to
    249249        login at this time.  This also applies to encrypted logins.
    250250        </para></listitem>
    251251
    252252        <listitem><para><emphasis>Session Management</emphasis>:  When not using share
    253         level secuirty, users must pass PAM's session checks before access
    254         is granted.  Note however, that this is bypassed in share level secuirty. 
     253        level security, users must pass PAM's session checks before access
     254        is granted.  Note however, that this is bypassed in share level security.
    255255        Note also that some older pam configuration files may need a line
    256256        added for session support.

  • vendor/current/docs-xml/manpages-3/tdbbackup.8.xml

    r740 r746  
    5555                <term>-s suffix</term>
    5656                <listitem><para>
    57                 The <command>-s</command> option allows the adminisistrator to specify a file
     57                The <command>-s</command> option allows the administrator to specify a file
    5858                backup extension. This way it is possible to keep a history of tdb backup
    5959                files by using a new suffix for each backup.
    … …  
    6464                <term>-v</term>
    6565                <listitem><para>
    66                 The <command>-v</command> will check the database for damages (currupt data)
     66                The <command>-v</command> will check the database for damages (corrupt data)
    6767                which if detected causes the backup to be restored.
    6868                </para></listitem>

  • vendor/current/docs-xml/manpages-3/testparm.1.xml

    r740 r746  
    9494                is limited by default to the global section.
    9595
    96                 It is also possible to dump a parametrical option.  Therfore
     96                It is also possible to dump a parametrical option.  Therefore
    9797                the option has to be separated by a colon from the
    9898                parametername.

  • vendor/current/docs-xml/manpages-3/vfs_acl_tdb.8.xml

    r740 r746  
    4141        </para>
    4242
    43         <para>Please note that this module is
    44         <emphasis>experimental</emphasis>!
    45         </para>
    46 
    4743        <para>This module is stackable.</para>
    4844</refsect1>
    … …  
    5046<refsect1>
    5147        <title>OPTIONS</title>
    52         <para>
    53         There are no options for <command>vfs_acl_tdb</command>.
    54         </para>
     48
     49        <variablelist>
     50                <!-- please keep in sync with the other acl vfs modules that provide the same options -->
     51                <varlistentry>
     52                <term>acl_tdb:ignore system acls = [yes|no]</term>
     53                <listitem>
     54                <para>
     55                When set to <emphasis>yes</emphasis>, a best effort mapping
     56                from/to the POSIX ACL layer will <emphasis>not</emphasis> be
     57                done by this module. The default is <emphasis>no</emphasis>,
     58                which means that Samba keeps setting and evaluating both the
     59                system ACLs and the NT ACLs. This is better if you need your
     60                system ACLs be set for local or NFS file access, too. If you only
     61                access the data via Samba you might set this to yes to achieve
     62                better NT ACL compatibility.
     63                </para>
     64                </listitem>
     65                </varlistentry>
     66        </variablelist>
     67
    5568</refsect1>
    5669

  • vendor/current/docs-xml/manpages-3/vfs_acl_xattr.8.xml

    r740 r746  
    4545        </para>
    4646
    47         <para>Please note that this module is
    48         <emphasis>experimental</emphasis>!
    49         </para>
    50 
    5147        <para>This module is stackable.</para>
    5248</refsect1>
    … …  
    5450<refsect1>
    5551        <title>OPTIONS</title>
    56         <para>
    57         There are no options for <command>vfs_acl_xattr</command>.
    58         </para>
     52
     53        <variablelist>
     54                <!-- please keep in sync with the other acl vfs modules that provide the same options -->
     55                <varlistentry>
     56                <term>acl_xattr:ignore system acls = [yes|no]</term>
     57                <listitem>
     58                <para>
     59                When set to <emphasis>yes</emphasis>, a best effort mapping
     60                from/to the POSIX ACL layer will <emphasis>not</emphasis> be
     61                done by this module. The default is <emphasis>no</emphasis>,
     62                which means that Samba keeps setting and evaluating both the
     63                system ACLs and the NT ACLs. This is better if you need your
     64                system ACLs be set for local or NFS file access, too. If you only
     65                access the data via Samba you might set this to yes to achieve
     66                better NT ACL compatibility.
     67                </para>
     68                </listitem>
     69                </varlistentry>
     70        </variablelist>
     71
    5972</refsect1>
    6073

  • vendor/current/docs-xml/manpages-3/vfs_readonly.8.xml

    r740 r746  
    3333        as read only for all clients connecting within the configured
    3434        time period. Clients connecting during this time will be denied
    35         write access to all files in the share, irrespective of ther
     35        write access to all files in the share, irrespective of their
    3636        actual access privileges.</para>
    3737

  • vendor/current/docs-xml/manpages-3/vfs_shadow_copy2.8.xml

    r740 r746  
    168168        <smbconfsection name="[homes]"/>
    169169        <smbconfoption name="vfs objects">shadow_copy2</smbconfoption>
    170         <smbconfoption name="shadow:snapdir">/data/snaphots</smbconfoption>
     170        <smbconfoption name="shadow:snapdir">/data/snapshots</smbconfoption>
    171171        <smbconfoption name="shadow:basedir">/data/home</smbconfoption>
    172172        <smbconfoption name="shadow:sort">desc</smbconfoption>

  • vendor/current/docs-xml/manpages-3/vfs_smb_traffic_analyzer.8.xml

    r740 r746  
    6464
    6565        <para><command>vfs_smb_traffic_analyzer</command> sends the following data
    66         in a fixed format seperated by a comma through either an internet or a
     66        in a fixed format separated by a comma through either an internet or a
    6767        unix domain socket:</para>
    6868        <programlisting>
    … …  
    7777        <listitem><para><command>DOMAIN</command> - the domain of the user</para></listitem>
    7878        <listitem><para><command>READ/WRITE</command> - either "W" for a write operation or "R" for read</para></listitem>
    79         <listitem><para><command>SHARE</command> - the name of the share on which the VFS operation occured</para></listitem>
     79        <listitem><para><command>SHARE</command> - the name of the share on which the VFS operation occurred</para></listitem>
    8080        <listitem><para><command>FILENAME</command> - the name of the file that was used by the VFS operation</para></listitem>
    81         <listitem><para><command>TIMESTAMP</command> - a timestamp, formatted as "yyyy-mm-dd hh-mm-ss.ms" indicating when the VFS operation occured</para></listitem>
     81        <listitem><para><command>TIMESTAMP</command> - a timestamp, formatted as "yyyy-mm-dd hh-mm-ss.ms" indicating when the VFS operation occurred</para></listitem>
    8282        <listitem><para><command>IP</command> - The IP Address (v4 or v6) of the client machine that initiated the VFS operation.</para></listitem>
    8383        </itemizedlist>

  • vendor/current/docs-xml/manpages-3/winbindd.8.xml

    r740 r746  
    2525                <arg choice="opt">-S</arg>
    2626                <arg choice="opt">-i</arg>
    27                 <arg choice="opt">-Y</arg>
    2827                <arg choice="opt">-d &lt;debug level&gt;</arg>
    2928                <arg choice="opt">-s &lt;smb config file&gt;</arg>
    … …  
    191190                results from the cache might not be up-to-date. This
    192191                might also temporarily hang winbindd if the DC doesn't respond.
    193                 </para></listitem>
    194                 </varlistentry>
    195 
    196                 <varlistentry>
    197                 <term>-Y</term>
    198                 <listitem><para>Single daemon mode. This means winbindd will run
    199                 as a single process (the mode of operation in Samba 2.2).  Winbindd's
    200                 default behavior is to launch a child process that is responsible for
    201                 updating expired cache entries.
    202192                </para></listitem>
    203193                </varlistentry>
Note: See TracChangeset for help on using the changeset viewer.