Ignore:
Timestamp:
Nov 14, 2012, 12:59:34 PM (13 years ago)
Author:
Silvan Scherrer
Message:

Samba Server: update vendor to 3.6.0

Location:
vendor/current/docs-xml/Samba3-HOWTO
Files:
5 edited

Legend:

Unmodified
Added
Removed

  • vendor/current/docs-xml/Samba3-HOWTO/TOSHARG-AccessControls.xml

    r414 r740  
    490490        <para>
    491491<indexterm><primary>extended attributes</primary></indexterm>
    492 <indexterm><primary>immutible</primary></indexterm>
     492<indexterm><primary>immutable</primary></indexterm>
    493493<indexterm><primary>chattr</primary></indexterm>
    494494<indexterm><primary>CAP_LINUX_IMMUTABLE</primary></indexterm>
    495495        The specific semantics of the extended attributes are not consistent across UNIX and UNIX-like systems such as Linux.
    496496        For example, it is possible on some implementations of the extended attributes to set a flag that prevents the directory
    497         or file from being deleted. The extended attribute that may achieve this is called the <constant>immutible</constant> bit.
    498         Unfortunately, the implementation of the immutible flag is NOT consistent with published documentation. For example, the
     497        or file from being deleted. The extended attribute that may achieve this is called the <constant>immutable</constant> bit.
     498        Unfortunately, the implementation of the immutable flag is NOT consistent with published documentation. For example, the
    499499        man page for the <command>chattr</command> on SUSE Linux 9.2 says:
    500500<screen>
    … …  
    504504CAP_LINUX_IMMUTABLE capability can set or clear this attribute.
    505505</screen>
    506         A simple test can be done to check if the immutible flag is supported on files in the file system of the Samba host
     506        A simple test can be done to check if the immutable flag is supported on files in the file system of the Samba host
    507507        server.
    508508        </para>
    … …  
    527527mystic:/home/hannibal > rm filename
    528528</screen>
    529         It will not be possible to delete the file if the immutible flag is correctly honored.
     529        It will not be possible to delete the file if the immutable flag is correctly honored.
    530530        </para></step>
    531531        </procedure>
    532532
    533533        <para>
    534         On operating systems and file system types that support the immutible bit, it is possible to create directories
     534        On operating systems and file system types that support the immutable bit, it is possible to create directories
    535535        that cannot be deleted. Check the man page on your particular host system to determine whether or not
    536536        immutable directories are writable. If they are not, then the entire directory and its contents will effectively
    … …  
    874874<indexterm><primary>Computer Management</primary></indexterm>
    875875        At this time Samba does not provide a tool for configuring access control settings on the share
    876         itself the only way to create those settings is to use either the NT4 Server Manager or the Windows 200x
     876        itself.  The only way to create those settings is to use either the NT4 Server Manager or the Windows 200x
    877877        Microsoft Management Console (MMC) for Computer Management. There are currently no plans to provide
    878878        this capability in the Samba command-line tool set.

  • vendor/current/docs-xml/Samba3-HOWTO/TOSHARG-Printing.xml

    r414 r740  
    523523<para>
    524524The following is a discussion of the settings from <link linkend="extbsdpr">Extended BSD Printing
    525 Configuration</link> <link linkend="extbsdpr">Extended BSD Printing Configuration</link>.
     525Configuration</link>.
    526526</para>
    527527
    … …  
    10391039in the Samba print command is <parameter>%$variable</parameter>.) To give you a working
    10401040<smbconfoption name="print command"/> example, the following will log a print job
    1041 to <filename>/tmp/print.log</filename>, print the file, then remove it. The semicolon (<quote>;</quote>
     1041to <filename>/tmp/print.log</filename>, print the file, then remove it. The semicolon (<quote>;</quote>)
    10421042is the usual separator for commands in shell scripts:
    10431043</para>
    … …  
    13191319</screen>
    13201320                 you can still mount it from any client. This can also be done from the
    1321                 <guimenu>Connect network drive menu></guimenu> from Windows Explorer.
     1321                <guimenu>Connect network drive</guimenu> menu from Windows Explorer.
    13221322                </para></listitem>
    13231323        </varlistentry>
    … …  
    16421642<indexterm><primary>UNC notation</primary></indexterm>
    16431643<indexterm><primary>Windows Explorer</primary></indexterm>
    1644 <indexterm><primary></primary></indexterm>
    16451644Since the <smbconfsection name="[print$]"/> share is usually accessible through the <guiicon>Network
    16461645Neighborhood</guiicon>, you can also use the UNC notation from Windows Explorer to poke at it. The Windows

  • vendor/current/docs-xml/Samba3-HOWTO/TOSHARG-RightsAndPriviliges.xml

    r414 r740  
    370370
    371371<sect2>
    372 <title>Privileges Suppored by Windows 2000 Domain Controllers</title>
     372<title>Privileges Supported by Windows 2000 Domain Controllers</title>
    373373
    374374<para>

  • vendor/current/docs-xml/Samba3-HOWTO/TOSHARG-Winbind.xml

    r414 r740  
    9494<indexterm><primary>idmap gid</primary></indexterm>
    9595<indexterm><primary>idmap backend</primary></indexterm>
    96 <indexterm><primary>LDAP</primary></indexterm>
    9796                Winbind maintains a database called winbind_idmap.tdb in which it stores
    9897                mappings between UNIX UIDs, GIDs, and NT SIDs. This mapping is used only
    … …  
    211210        names as they would <quote>native</quote> UNIX names. They can chown files
    212211        so they are owned by NT domain users or even login to the
    213         UNIX machine and run a UNIX X-Window session as a domain user.</para>
     212        UNIX machine and run a UNIX X Window session as a domain user.</para>
    214213
    215214        <para>
    … …  
    572571<indexterm><primary>PAM</primary></indexterm>
    573572<indexterm><primary>back up</primary></indexterm>
    574 <indexterm><primary>boot disk`</primary></indexterm>
     573<indexterm><primary>boot disk</primary></indexterm>
    575574If you have a Samba configuration file that you are currently using, <emphasis>BACK IT UP!</emphasis>
    576575If your system already uses PAM, <emphasis>back up the <filename>/etc/pam.d</filename> directory
    … …  
    603602To allow domain users the ability to access Samba shares and files, as well as potentially other services
    604603provided by your Samba machine, PAM must be set up properly on your
    605 machine. In order to compile the Winbind modules, you should have at least the PAM development libraries installed
    606 on your system. Please refer to the PAM Web site <ulink url="http://www.kernel.org/pub/linux/libs/pam/"/>.
     604machine. In order to compile the Winbind modules, the PAM development libraries should be installed
     605on your system. Please refer to the <ulink url="http://www.kernel.org/pub/linux/libs/pam/">PAM Web Site</ulink>.
    607606</para>
    608607</sect2>
    … …  
    977976<indexterm><primary>/etc/init.d/samba</primary></indexterm>
    978977<indexterm><primary>/usr/local/samba/bin</primary></indexterm>
    979 <indexterm><primary></primary></indexterm>
    980 <indexterm><primary></primary></indexterm>
    981 <indexterm><primary></primary></indexterm>
    982978The &winbindd; daemon needs to start up after the &smbd; and &nmbd; daemons are running.  To accomplish this
    983979task, you need to modify the startup scripts of your system.  They are located at
    … …  
    11201116
    11211117<para>
    1122 Again, if you would like to run Samba in dual daemon mode, replace:
     1118Again, if you would like to run winbindd in dual daemon mode, replace:
    11231119<programlisting>
    11241120/usr/local/samba/sbin/winbindd
    … …  
    12351231<indexterm><primary>ftp access</primary></indexterm>
    12361232The <filename>/etc/pam.d/ftp</filename> file can be changed to allow Winbind ftp access in a manner similar to
    1237 the samba file. My <filename>/etc/pam.d/ftp</filename> file was changed to look like this:
     1233the <filename>/etc/pam.d/samba</filename>Samba file. My <filename>/etc/pam.d/ftp</filename> file was changed to look like this:
    12381234<programlisting>
    12391235auth       required     /lib/security/pam_listfile.so item=user sense=deny \

  • vendor/current/docs-xml/Samba3-HOWTO/manpages.xml

    r414 r740  
    1818        <xi:include href="../manpages-3/lmhosts.5.xml"/>
    1919        <xi:include href="../manpages-3/log2pcap.1.xml"/>
    20         <xi:include href="../manpages-3/mount.cifs.8.xml"/>
    2120        <xi:include href="../manpages-3/net.8.xml"/>
    2221        <xi:include href="../manpages-3/nmbd.8.xml"/>
    … …  
    4948        <xi:include href="../manpages-3/wbinfo.1.xml"/>
    5049        <xi:include href="../manpages-3/winbindd.8.xml"/>
    51         <xi:include href="../manpages-3/umount.cifs.8.xml"/>
    5250        <xi:include href="../manpages-3/vfs_audit.8.xml"/>
    5351        <xi:include href="../manpages-3/vfs_cacheprime.8.xml"/>
Note: See TracChangeset for help on using the changeset viewer.