Changeset 988 for vendor/current/docs-xml/using_samba
- Timestamp:
- Nov 24, 2016, 1:14:11 PM (9 years ago)
- Location:
- vendor/current/docs-xml/using_samba
- Files:
-
- 10 edited
Legend:
- Unmodified
- Added
- Removed
-
vendor/current/docs-xml/using_samba/appc.xml
r740 r988 67 67 </refentry> 68 68 69 <refentry id="appc-refentry-4">70 <refmeta>71 <refmiscinfo class="allowable values">NT, Win95, WfW</refmiscinfo>72 <refmiscinfo class="default">NT</refmiscinfo>73 </refmeta>74 <refnamediv>75 <refname>[global] announce as = system type</refname>76 </refnamediv>77 <refsynopsisdiv>78 <para>Have Samba announce itself as something other than an NT server. Discouraged because it interferes with serving browse lists.</para>79 80 </refsynopsisdiv>81 </refentry>82 83 <refentry id="appc-refentry-5">84 <refmeta>85 <refmiscinfo class="allowable values">any</refmiscinfo>86 <refmiscinfo class="default">4.2</refmiscinfo>87 </refmeta>88 <refnamediv>89 <refname>[global] announce version = number.number</refname>90 </refnamediv>91 <refsynopsisdiv>92 <para>Instructs Samba to announce itself as an older version SMB server. Discouraged.</para>93 94 </refsynopsisdiv>95 </refentry>96 97 69 <refentry id="appc-refentry-6"> 98 70 <refmeta> … … 1883 1855 <refsynopsisdiv> 1884 1856 <para>Sets the command used to change user's password. Will be run as <literal>root</literal>. Supports <literal>%u</literal> (user).</para> 1885 1886 </refsynopsisdiv>1887 </refentry>1888 1889 <refentry id="appc-refentry-134">1890 <refmeta>1891 <refmiscinfo class="allowable values">number</refmiscinfo>1892 <refmiscinfo class="default">0</refmiscinfo>1893 </refmeta>1894 <refnamediv>1895 <refname>[global] password level = number</refname>1896 </refnamediv>1897 <refsynopsisdiv>1898 <para>Specifies the number of uppercase letter permutations used to match passwords. Workaround for clients that change passwords to a single case before sending them to the Samba server. Causes repeated login attempts with passwords in different cases, which can trigger account lockouts.</para>1899 1857 1900 1858 </refsynopsisdiv> … … 2515 2473 <refsynopsisdiv> 2516 2474 <para>Overrides compiled-in path to <filename>smbrun</filename> binary. Avoid changing.</para> 2517 2518 </refsynopsisdiv>2519 </refentry>2520 2521 <refentry id="appc-refentry-179">2522 <refmeta>2523 <refmiscinfo class="allowable values">YES, NO</refmiscinfo>2524 <refmiscinfo class="default">YES</refmiscinfo>2525 </refmeta>2526 <refnamediv>2527 <refname>share modes = boolean</refname>2528 </refnamediv>2529 <refsynopsisdiv>2530 <para>If set to YES, this option supports Windows-style whole-file (deny mode) locks.</para>2531 2475 2532 2476 </refsynopsisdiv> -
vendor/current/docs-xml/using_samba/appd.xml
r414 r988 292 292 293 293 294 <sect2 role="" label="D.1.4" id="appd-SECT-1.4">295 <title>smbsh</title>296 297 298 <para>The <emphasis>smbsh</emphasis>299 <indexterm id="appd-idx-993744-0"><primary>smbsh program</primary></indexterm> program lets you use a remote Windows share on your Samba server as if the share was a regular Unix directory. When it's run, it provides an extra directory tree under <filename>/smb</filename>. Subdirectories of <filename>/smb</filename> are servers, and subdirectories of the servers are their individual disk and printer shares. Commands run by <emphasis>smbsh</emphasis> treat the <filename>/smb</filename> filesystem as if it were local to Unix. This means that you don't need <emphasis>smbmount</emphasis> in your kernel to mount Windows filesystems the way you mount with NFS filesystems. However, you do need to configure Samba with the <literal>--with-smbwrappers</literal> option to enable <filename>smbsh</filename>.</para>300 301 302 294 <sect3 role="" label="D.1.4.1" id="appd-SECT-1.4.1"> 303 295 <title>Options</title> … … 1324 1316 1325 1317 1326 <sect2 role="" label="D.1.11" id="appd-SECT-1.11">1327 <title>testprns</title>1328 1329 1330 <para>The<indexterm id="appd-idx-993761-0"><primary>testprns program</primary></indexterm>1331 <indexterm id="appd-idx-993761-1"><primary>printers</primary><secondary>names</secondary><tertiary>checking</tertiary></indexterm> <emphasis>testprns</emphasis> program checks a specified printer name against the system printer capabilities (<filename>printcap</filename>) file. Its command line is:</para>1332 1333 1334 <programlisting>testprns <replaceable>printername</replaceable> [<replaceable>printcapname</replaceable>]</programlisting>1335 1336 1337 <para>If the <literal>printcapname</literal> isn't specified, Samba attempts to use one located in the <filename>smb.conf</filename> file. If one isn't specified there, Samba will try <filename>/etc/printcap</filename>. If that fails, the program will generate an error.</para>1338 </sect2>1339 1340 1341 1342 1343 1344 1318 <sect2 role="" label="D.1.12" id="appd-SECT-1.12"> 1345 1319 <title>rpcclient</title> -
vendor/current/docs-xml/using_samba/appf.xml
r414 r988 90 90 91 91 read prediction = yes 92 share modes = yes93 92 max xmit = 17384 94 93 read size = 512</programlisting> -
vendor/current/docs-xml/using_samba/ch01.xml
r414 r988 1376 1376 1377 1377 1378 <varlistentry><term>testprns</term>1379 <listitem><para>A program that tests whether various printers are recognized by the <filename>smbd</filename> daemon</para></listitem>1380 </varlistentry>1381 </variablelist>1382 1383 1384 1378 <para>Each significant release of Samba goes through a significant exposure test before it's announced. In addition, it is quickly updated afterward if problems or unwanted side-effects are found. The latest stable distribution as of this writing is Samba 2.0.5, the long-awaited production version of Samba 2.0. This book focuses on the functionality supported in Samba 2.0, as opposed to the older 1.9.<emphasis>x</emphasis> versions of Samba, which are now obsolete.</para> 1385 1379 </sect1> … … 1517 1511 1518 1512 1519 <sect2 role="" label="1.7.6" id="ch01-SECT-7.6">1520 <title>Smbwrapper</title>1521 1522 1523 <para>Finally, there is an entirely new version of the Unix client called <firstterm>smbwrapper</firstterm>1524 <indexterm id="ch01-idx-951955-0"><primary>smbwrapper client</primary></indexterm>. Instead of a kernel module that allows Linux to act as a Samba client, there is now a command-line entry to load the library that provides a complete SMB filesystem on some brands of Unix. Once loaded, the command <literal>ls</literal> <literal>/smb</literal> will list all the machines in your workgroup, and <literal>cd</literal> <literal>/smb/</literal><replaceable>server_name</replaceable><literal>/</literal><replaceable>share_name</replaceable> will take you to a particular <indexterm id="ch01-idx-951956-0"><primary>shares</primary></indexterm>1525 <indexterm id="ch01-idx-951956-1"><primary>shared directory/resources</primary><see>shares</see></indexterm>share (shared directory), similar to the <indexterm id="ch01-idx-951957-0"><primary>Network File System (NFS)</primary></indexterm>1526 <indexterm id="ch01-idx-951957-1"><primary>NFS (Network File System)</primary></indexterm>Network File System (NFS). As of this writing, <emphasis>smbwrapper</emphasis> currently runs on Linux, Solaris, SunOS 4, IRIX, and OSF/1, and is expected to run on several more operating systems in the near future.</para>1527 </sect2>1528 </sect1>1529 1530 1513 1531 1514 -
vendor/current/docs-xml/using_samba/ch02.xml
r414 r988 137 137 138 138 139 <para>This is especially true with programs that use <emphasis>glibc-2.1</emphasis> (which comes standard with Red Hat Linux 6). This library caused quite a consternation in the development community when it was released because it was incompat able with previous versions of <emphasis>g</emphasis><filename>libc</filename>.</para>139 <para>This is especially true with programs that use <emphasis>glibc-2.1</emphasis> (which comes standard with Red Hat Linux 6). This library caused quite a consternation in the development community when it was released because it was incompatible with previous versions of <emphasis>g</emphasis><filename>libc</filename>.</para> 140 140 141 141 … … 236 236 237 237 238 <variablelist>239 <varlistentry><term><literal>--with-smbwrapper</literal></term>240 <listitem><para>Include SMB <indexterm id="ch02-idx-947350-0"><primary>SMB (Server Message Block)</primary><secondary>wrapper support</secondary></indexterm>241 <indexterm id="ch02-idx-947350-1"><primary>wrapper support for SMB (Server Message Block)</primary></indexterm>wrapper support, which allows executables on the Unix side to access <indexterm id="ch02-idx-947351-0"><primary>SMB/CIFS protocol</primary><secondary>filesystems</secondary></indexterm>SMB/CIFS filesystems as if they were regular Unix filesystems. We recommend using this option. However, at this time this book went to press, there were several incompatibilities between the <filename>smbwrapper</filename>242 <indexterm id="ch02-idx-947352-0"><primary>smbwrapper package</primary></indexterm> package and the GNU <filename>libc</filename> version 2.1, and it would not compile on Red Hat 6.0. Look for more information on these incompatibilities on the Samba home page.</para></listitem>243 </varlistentry>244 245 246 238 <varlistentry><term><literal>--with-afs</literal></term> 247 239 <listitem><para>Include support of the <indexterm id="ch02-idx-947353-0"><primary>Andrew Filesystem</primary><see>AFS files</see></indexterm>Andrew Filesystem from <indexterm id="ch02-idx-947354-0"><primary>Carnegie Mellon University</primary></indexterm>Carnegie Mellon University. If you're going to serve <indexterm id="ch02-idx-947355-0"><primary>AFS files, support for</primary></indexterm>AFS files via Samba, we recommend compiling Samba once first without enabling this feature to ensure that everything runs smoothly. Once that version is working smoothly, recompile Samba with this feature enabled and compare any errors you might receive against the previous setup.</para></listitem> … … 267 259 <varlistentry><term><literal>--with-automount</literal></term> 268 260 <listitem><para>Include support for <indexterm id="ch02-idx-947365-0"><primary>automounter, support for</primary></indexterm>automounter, a feature often used on sites that offer NFS.</para></listitem> 269 </varlistentry>270 271 272 <varlistentry><term><literal>--with-smbmount</literal></term>273 <listitem><para>Include <emphasis>smbmount</emphasis>274 <indexterm id="ch02-idx-947366-0"><primary>smbmount, support for</primary></indexterm> support, which is for <indexterm id="ch02-idx-947367-0"><primary>Linux</primary><secondary>submount and</secondary></indexterm>Linux only. This feature wasn't being maintained at the time the book was written, so the Samba team made it an optional feature and provided <emphasis>smbwrapper</emphasis> instead. The <emphasis>smbwrapper</emphasis> feature works on more Unix platforms than <emphasis>smbmount</emphasis>, so you'll usually want to use <literal>--with-smbwrapper</literal> instead of this option.</para></listitem>275 261 </varlistentry> 276 262 -
vendor/current/docs-xml/using_samba/ch05.xml
r414 r988 524 524 <row> 525 525 526 <entry colname="col1"><para><literal>announce as</literal></para></entry>527 528 <entry colname="col2"><para><literal>NT</literal>529 <indexterm id="ch05-idx-969670-0"><primary>browsing</primary><secondary>options for, list of</secondary></indexterm> or <literal>Win95</literal> or <literal>Wf W</literal></para></entry>530 531 <entry colname="col3"><para>Sets the operating system that Samba will announce itself as.</para></entry>532 533 <entry colname="col4"><para><literal>N T</literal></para></entry>534 535 <entry colname="col5"><para>Global</para></entry>536 537 </row>538 539 <row>540 541 <entry colname="col1"><para><literal>announce version</literal></para></entry>542 543 <entry colname="col2"><para>numerical</para></entry>544 545 <entry colname="col3"><para>Sets the version of the operating system that Samba will announce itself as.</para></entry>546 547 <entry colname="col4"><para><literal>4.2</literal></para></entry>548 549 <entry colname="col5"><para>Global</para></entry>550 551 </row>552 553 <row>554 555 526 <entry colname="col1"><para><literal>browseable (browsable)</literal></para></entry> 556 527 … … 1037 1008 1038 1009 1039 <para>The <literal>dont</literal> <literal>descend</literal> directive specifies a list of <indexterm id="ch05-idx-969715-0"><primary>directories</primary><secondary>barring users from viewing contents</secondary></indexterm>directories whose contents Samba should not allow to be visible. Note that we say <emphasis>contents</emphasis>, not the directory itself. Users will be able to enter a directory marked as such, but they are prohibited from descending the directory tree any farther—they will always see an empty folder. For example, let's use this option with a more basic form of the share that we defined earlier in the chapter:</para>1010 <para>The <literal>dont</literal> <literal>descend</literal> directive specifies a list of <indexterm id="ch05-idx-969715-0"><primary>directories</primary><secondary>barring users from viewing contents</secondary></indexterm>directories whose contents Samba should not allow one to be visible. Note that we say <emphasis>contents</emphasis>, not the directory itself. Users will be able to enter a directory marked as such, but they are prohibited from descending the directory tree any farther—they will always see an empty folder. For example, let's use this option with a more basic form of the share that we defined earlier in the chapter:</para> 1040 1011 1041 1012 … … 2722 2693 </table> 2723 2694 2724 2725 <para>The <literal>share</literal> <literal>modes</literal> parameter, which enforces the use of these locks, is enabled by default. To disable it, use the following command:</para>2726 2727 2728 <programlisting>[accounting]2729 share modes = no</programlisting>2730 2731 2732 <para>We highly recommend against disabling the default locking mechanism unless you have a justifiable reason for doing so. Most Windows and DOS applications rely on these locking mechanisms in order to work correctly, and will complain bitterly if this functionality is taken away.</para>2733 2695 </sect3> 2734 2696 -
vendor/current/docs-xml/using_samba/ch06.xml
r740 r988 1579 1579 <row> 1580 1580 1581 <entry colname="col1"><para><literal>password level</literal></para></entry>1582 1583 <entry colname="col2"><para>numeric</para></entry>1584 1585 <entry colname="col3"><para>Sets the number of capital letter permutations to attempt when matching a client's password.</para></entry>1586 1587 <entry colname="col4"><para>None</para></entry>1588 1589 <entry colname="col5"><para>Global</para></entry>1590 1591 </row>1592 1593 <row>1594 1595 1581 <entry colname="col1"><para><literal>null passwords</literal></para></entry> 1596 1582 -
vendor/current/docs-xml/using_samba/ch07.xml
r746 r988 307 307 308 308 309 <para>Second, try the command <literal>testprns</literal> <replaceable>printername</replaceable>. This is a simple program that verifies that the specified printer is available in your <emphasis>printcap</emphasis> file. If your <emphasis>printcap</emphasis> file is not in the usual place, you can specify its full pathname as the second argument to the <emphasis>testprns</emphasis> command:</para>310 311 312 <programlisting># testprns lp /etc/printcap313 Looking for printer lp in printcap file /etc/printcap314 Printer name lp is valid.</programlisting>315 316 317 309 <para>Next, log on as the guest user, go to the spooling directory, and ensure that you can print using the same command that <emphasis>testparm</emphasis> says Samba will use. As mentioned before, this will tell you if you need to change the guest account, as the default account may not be allowed to print.</para> 318 310 -
vendor/current/docs-xml/using_samba/ch08.xml
r414 r988 1796 1796 1797 1797 1798 1799 1800 1801 <sect2 role="" label="8.6.13" id="ch08-SECT-6.0.13"> 1802 <indexterm id="ch08-idx-965993-0"><primary>set directory option</primary></indexterm> 1803 <title> 1804 set directory</title> 1805 1806 1807 <para>This boolean share-level option allows <indexterm id="ch08-idx-965497-0"><primary>Digital Pathworks clients, option for</primary></indexterm>Digital Pathworks clients to use the <literal>setdir</literal> command to change directories on the server. If you are not using the Digital Pathworks client, you should not need to alter this option. The default value for this option is <literal>no</literal>. You can override it per share as follows:</para> 1808 1809 1810 <programlisting>[data] 1811 set directory = yes</programlisting> 1812 </sect2> 1813 1814 1815 1816 1817 1818 <sect2 role="" label="8.6.14" id="ch08-SECT-6.0.14"> 1798 <sect2 role="" label="8.6.13" id="ch08-SECT-6.0.14"> 1819 1799 <indexterm id="ch08-idx-965994-0"><primary>smbrun option</primary></indexterm> 1820 1800 <title> … … 1833 1813 1834 1814 1835 <sect2 role="" label="8.6.1 5" id="ch08-SECT-6.0.15">1815 <sect2 role="" label="8.6.14" id="ch08-SECT-6.0.15"> 1836 1816 <indexterm id="ch08-idx-965995-0"><primary>status option</primary></indexterm> 1837 1817 <title> … … 1851 1831 1852 1832 1853 <sect2 role="" label="8.6.1 6" id="ch08-SECT-6.0.16">1833 <sect2 role="" label="8.6.15" id="ch08-SECT-6.0.16"> 1854 1834 <indexterm id="ch08-idx-965996-0"><primary>strict sync option</primary></indexterm> 1855 1835 <title> … … 1868 1848 1869 1849 1870 <sect2 role="" label="8.6.1 7" id="ch08-SECT-6.0.17">1850 <sect2 role="" label="8.6.16" id="ch08-SECT-6.0.17"> 1871 1851 <indexterm id="ch08-idx-965997-0"><primary>sync always option</primary></indexterm> 1872 1852 <title> … … 1885 1865 1886 1866 1887 <sect2 role="" label="8.6.1 8" id="ch08-SECT-6.0.18">1867 <sect2 role="" label="8.6.17" id="ch08-SECT-6.0.18"> 1888 1868 <indexterm id="ch08-idx-965998-0"><primary>strip dot option</primary></indexterm> 1889 1869 <title> -
vendor/current/docs-xml/using_samba/ch09.xml
r414 r988 1926 1926 1927 1927 1928 <variablelist> 1929 <varlistentry><term><email>samba-binaries@samba.org</email></term> 1930 <listitem><para>This mailing list has information on precompiled binaries for the Samba platform.</para></listitem> 1931 </varlistentry> 1932 1933 1934 <varlistentry><term><email>samba-bugs@samba.org</email></term> 1935 <listitem><para>This mailing list is the place to report suspected bugs in Samba.</para></listitem> 1936 </varlistentry> 1937 1938 1939 <varlistentry><term><email>samba-ntdom@samba.org</email></term> 1940 <listitem><para>This mailing list has information on support for domains (particularly Windows NT) with the Samba product.</para></listitem> 1941 </varlistentry> 1942 1943 1944 <varlistentry><term><email>samba-technical@samba.org</email></term> 1928 <varlistentry><term><email>samba-technical@lists.samba.org</email></term> 1945 1929 <listitem><para>This mailing list maintains debate about where the future of Samba is headed.</para></listitem> 1946 1930 </varlistentry> 1947 1931 1948 1932 1949 <varlistentry><term><email>samba@ samba.org</email></term>1933 <varlistentry><term><email>samba@lists.samba.org</email></term> 1950 1934 <listitem><para>This is the primary Samba mailing list that contains general questions and HOW-TO information on Samba.</para></listitem> 1951 1935 </varlistentry>
Note:
See TracChangeset
for help on using the changeset viewer.
