Changeset fc290c7


Ignore:
Timestamp:
06/05/2005 10:26:10 PM (19 years ago)
Author:
Randy McMurchy <randy@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
Children:
dba3e736
Parents:
b785ab29
Message:

Added a Samba-client instruction page; updated the Samba server instructions with Alexander's comments; added an Stunnel-less SWAT setup in the Samba server instructions; removed Stunnel as a dependency of Samba server

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@4551 af4574ff-66df-0310-9fd7-8a98e5e911e0

Files:
1 added
4 edited

Legend:

Unmodified
Added
Removed

  • basicnet/netprogs/netprogs.xml

    rb785ab29 rfc290c7  
    1616  are support programs for daemons that you may have running on your machine.</para>
    1717
     18  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="cvs.xml"/>
     19  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="inetutils.xml"/>
    1820  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="ncftp.xml"/>
     21  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="ncpfs.xml"/>
     22  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="net-tools.xml"/>
     23  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="ntp.xml"/>
    1924  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="openssh-client.xml"/>
     25  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="portmap.xml"/>
    2026  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="rsync-client.xml"/>
    21   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="cvs.xml"/>
     27  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="samba3-client.xml"/>
    2228  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="subversion.xml"/>
     29  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="tcpwrappers.xml"/>
    2330  <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="wget.xml"/>
    24   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="tcpwrappers.xml"/>
    25   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="portmap.xml"/>
    26   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="inetutils.xml"/>
    27   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="ncpfs.xml"/>
    28   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="ntp.xml"/>
    29   <xi:include xmlns:xi="http://www.w3.org/2003/XInclude" href="net-tools.xml"/>
    3031
    3132</chapter>

  • general.ent

    rb785ab29 rfc290c7  
    211211
    212212<!-- Chapter 18 -->
     213<!ENTITY cvs-version                  "1.11.20">
     214<!ENTITY inetutils-version            "1.4.2">
    213215<!ENTITY ncftp-version                "3.1.7">
     216<!ENTITY ncpfs-version                "2.2.4">
     217<!ENTITY net-tools-version            "1.60">
     218<!ENTITY ntp-version                  "4.2.0">
    214219<!ENTITY openssh-version              "4.1p1">
     220<!ENTITY portmap-version              "5beta">
    215221<!ENTITY rsync-version                "2.6.5">
    216 <!ENTITY cvs-version                  "1.11.20">
     222<!ENTITY samba3-version               "3.0.14a">
    217223<!ENTITY subversion-version           "1.1.4">
     224<!ENTITY tcpwrappers-version          "7.6">
    218225<!ENTITY wget-version                 "1.9.1">
    219 <!ENTITY tcpwrappers-version          "7.6">
    220 <!ENTITY portmap-version              "5beta">
    221 <!ENTITY inetutils-version            "1.4.2">
    222 <!ENTITY ncpfs-version                "2.2.4">
    223 <!ENTITY ntp-version                  "4.2.0">
    224 <!ENTITY net-tools-version            "1.60">
    225226
    226227<!-- Chapter 19 -->
    … …  
    246247<!-- openssh (chapter 18) -->
    247248<!ENTITY proftpd-version              "1.2.10">
    248 <!ENTITY samba3-version               "3.0.14a">
     249<!-- samba3 (chapter 18) -->
    249250<!ENTITY vsftpd-version               "2.0.1">
    250251<!ENTITY xinetd-version               "2.3.13">

  • introduction/welcome/changelog.xml

    rb785ab29 rfc290c7  
    2424
    2525  <itemizedlist>
     26
     27    <listitem>
     28      <para>June 5th, 2005 [randy]: Created Samba client instruction page,
     29      suggested by Alexander Patrakov; added additional configuration text to
     30      the Samba server instructions, submitted by Alexander Patrakov; added
     31      SWAT (without Stunnel) configuration instructions to the Samba server
     32      instructions, suggested by Jim Gifford; removed Stunnel as a dependency
     33      of the Samba package.</para>
     34    </listitem>
    2635
    2736    <listitem>

  • server/major/samba3.xml

    rb785ab29 rfc290c7  
    7272    <xref linkend="python"/>,
    7373    <xref linkend="xinetd"/>,
    74     <ulink url="http://valgrind.kde.org/">Valgrind</ulink> and
    75     <xref linkend="stunnel"/> (used to encrypt access to SWAT)</para>
     74    <xref linkend="xfs"/> and
     75    <ulink url="http://valgrind.kde.org/">Valgrind</ulink></para>
    7676
    7777  </sect2>
    … …  
    187187
    188188    <sect3>
     189      <title>Printing to SMB Clients</title>
     190
     191      <para>If you use <application>CUPS</application> for print services,
     192      and you wish to print to a printer attached to an SMB client, you
     193      need to create an SMB backend device. To create the device, issue the
     194      following command as the <systemitem class="username">root</systemitem>
     195      user:</para>
     196
     197<screen role="root"><userinput>ln -v -sf /usr/bin/smbspool /usr/lib/cups/backend/smb</userinput></screen>
     198
     199    </sect3>
     200
     201    <sect3>
    189202      <title>Configuration Information</title>
    190203
    191       <para>The installation commands installed a default configuration file
    192       which you can use as an example to set the values for your system and
    193       network. At a minimum, ensure you set the following value to an
    194       appropriate setting for your network in the
    195       <filename>/etc/samba/smb.conf</filename> configuration file:</para>
    196 
    197 <screen><literal>workgroup = <replaceable>WORKGROUP</replaceable></literal></screen>
    198 
    199       <para>Also, for non-English locales, ensure the following values are
    200       set properly in the [global] section:</para>
    201 
    202 <screen><literal>dos charset = <replaceable>cp850</replaceable>
    203 unix charset = <replaceable>ISO-8859-1</replaceable></literal></screen>
    204 
    205     </sect3>
    206 
    207     <sect3>
    208       <title>Configuration Overview and Available Documentation</title>
    209 
    210204      <para>Due to the complexity and the many various uses for
    211       <application>Samba</application>, complete configuration is well beyond
    212       the scope of the BLFS book. Advanced configurations including setting up
    213       Primary and Backup Domain Controllers are advanced topics and cannot be
    214       adequately covered in BLFS (it should be noted, however, that a
    215       <application>Samba</application> BDC cannot be used as a fallback for a
    216       <application>Windows</application> PDC, and conversely, a
    217       <application>Windows</application> BDC cannot be used as a
    218       fallback for a <application>Samba</application> PDC). Many
    219       complete books have been written on these topics alone.</para>
    220 
    221       <para>There is quite a bit of documentation available which covers many
    222       of these advanced configurations. Point your web browser to the links
    223       below to view some of the documentation included with the
    224       <application>Samba</application> package:</para>
    225 
    226       <itemizedlist spacing='compact'>
    227         <listitem>
    228           <para>Using Samba, 2nd Edition; a popular book published by O'Reilly
    229           <ulink url="file:///usr/share/samba/swat/using_samba/toc.html"/></para>
    230         </listitem>
    231         <listitem>
    232           <para>The Official Samba HOWTO and Reference Guide <ulink
    233           url="file:///usr/share/samba/swat/help/Samba-HOWTO-Collection/index.html"/>
    234           </para>
    235         </listitem>
    236         <listitem>
    237           <para>Samba-3 by Example
    238           <ulink url="file:///usr/share/samba/swat/help/Samba-Guide/index.html"/>
    239           </para>
    240         </listitem>
    241         <listitem>
    242           <para>The Samba-3 man Pages
    243           <ulink url="file:///usr/share/samba/swat/help/samba.7.html"/></para>
    244         </listitem>
    245       </itemizedlist>
     205      <application>Samba</application>, complete configuration for all the
     206      package's cababilities is well beyond the scope of the BLFS book. This
     207      section provides instructions to configure the
     208      <filename>/etc/samba/smb.conf</filename> file for two common scenarios.
     209      The complete contents of <filename>/etc/samba/smb.conf</filename> will
     210      depend on the purpose of <application>Samba</application>
     211      installation.</para>
     212
     213      <note>
     214        <para>You may find it easier to copy the configuration parameters shown
     215        below into an empty <filename>/etc/samba/smb.conf</filename> file
     216        instead of copying and editing the default file as mentioned in the
     217        <quote>Command Explanations</quote> section. How you create/edit the
     218        <filename>/etc/samba/smb.conf</filename> file will be left up to
     219        you. Do ensure the file is only writeable by the
     220        <systemitem class="username">root</systemitem> user (mode 644).</para>
     221      </note>
     222
     223      <sect4>
     224        <title>Scenario 1: Minimal Standalone Client-Only Installation</title>
     225
     226        <para>Choose this variant if you only want to transfer files using
     227        <command>smbclient</command>, mount Windows shares and print to Windows
     228        printers, and don't want to share your files and printers to Windows
     229        machines.</para>
     230
     231        <para>A <filename>/etc/samba/smb.conf</filename> file with the following
     232        three parameters is sufficient:</para>
     233
     234<screen role='root'><literal>[global]
     235    workgroup = <replaceable>MYGROUP</replaceable>
     236    dos charset = <replaceable>cp850</replaceable>
     237    unix charset = <replaceable>ISO-8859-1</replaceable></literal></screen>
     238
     239        <para>The values in this example specify that the computer belongs to a
     240        Windows workgroup named
     241        <quote><replaceable>MYGROUP</replaceable></quote>, uses the
     242        <quote><replaceable>cp850</replaceable></quote> character set on the
     243        wire when talking to MS-DOS and MS Windows 9x, and that the filenames
     244        are stored in the <quote><replaceable>ISO-8859-1</replaceable></quote>
     245        encoding on the disk. Adjust these values appropriately for your
     246        installation. The <quote>unix charset</quote> value must be the same as
     247        the output of <command>locale charmap</command> when executed with the
     248        <envar>LANG</envar> variable set to your preferred locale, otherwise the
     249        <command>ls</command> command may not display correct filenames of
     250        downloaded files.</para>
     251
     252        <para>There is no need to run any <application>Samba</application>
     253        servers in this scenario, thus you don't need to install the provided
     254        bootscripts.</para>
     255
     256      </sect4>
     257
     258      <sect4>
     259        <title>Scenario 2: Standalone File/Print Server</title>
     260
     261        <para>Choose this variant if you want to share your files and printers
     262        to Windows machines in your workgroup in addition to the capabilities
     263        described in Scenario 1.</para>
     264
     265        <para>In this case, the <filename>/etc/samba/smb.conf.default</filename>
     266        file may be a good template to start from. Also add
     267        <quote>dos charset</quote> and <quote>unix charset</quote> parameters
     268        to the <quote>[global]</quote> section as described in Scenario 1 in
     269        order to prevent filename corruption.</para>
     270
     271        <para>The following configuration file creates a separate share for each
     272        user's home directory and also makes all printers available to Windows
     273        machines:</para>
     274
     275<screen role='root'><literal>[global]
     276    workgroup = <replaceable>MYGROUP</replaceable>
     277    dos charset = <replaceable>cp850</replaceable>
     278    unix charset = <replaceable>ISO-8859-1</replaceable>
     279
     280[homes]
     281    comment = Home Directories
     282    browseable = no
     283    writable = yes
     284
     285[printers]
     286    comment = All Printers
     287    path = /var/spool/samba
     288    browseable = no
     289    guest ok = no
     290    printable = yes</literal></screen>
     291
     292        <para>Other parameters you may wish to customize in the
     293        <quote>[global]</quote> section include:</para>
     294
     295<screen role='root'><literal>    server string =
     296    security =
     297    hosts allow =
     298    load printers =
     299    log file =
     300    max log size =
     301    socket options =
     302    local master =</literal></screen>
     303
     304        <para>Reference the comments in the
     305        <filename>/etc/samba/smb.conf.default</filename> file for information
     306        regarding these parameters.</para>
     307
     308        <para>Since the <command>smbd</command> and <command>nmbd</command>
     309        daemons are needed in this case, install the <filename>samba</filename>
     310        bootscript. Be sure to run <command>smbpasswd</command> (with the
     311        <option>-a</option> option to add users) to enable and
     312        set passwords for all accounts that need
     313        <application>Samba</application> access, or use the SWAT web interface
     314        (see below) to do the same. Using the default
     315        <application>Samba</application> passdb backend, any user you attempt
     316        to add will also be required to exist in the
     317        <filename>/etc/passwd</filename> file.</para>
     318
     319      </sect4>
     320
     321      <sect4>
     322        <title>Advanced Requirements</title>
     323
     324        <para>More complex scenarios involving domain control or membership are
     325        possible if the right flags are passed to the ./configure script when
     326        the package is built. Such setups are advanced topics and cannot be
     327        adequately covered in BLFS. Many complete books have been written on
     328        these topics alone. It should be noted, however, that a
     329        <application>Samba</application> BDC cannot be used as a fallback
     330        for a Windows PDC, and conversely, a Windows BDC cannot be used as a
     331        fallback for a <application>Samba</application> PDC. Also in some
     332        domain mambership scenarios, the <command>winbindd</command> daemon and
     333        the corresponding bootscript are needed.</para>
     334
     335        <para>There is quite a bit of documentation available which covers many
     336        of these advanced configurations. Point your web browser to the links
     337        below to view some of the documentation included with the
     338        <application>Samba</application> package:</para>
     339
     340        <itemizedlist spacing='compact'>
     341          <listitem>
     342            <para>Using Samba, 2nd Edition; a popular book published by O'Reilly
     343            <ulink url="file:///usr/share/samba/swat/using_samba/toc.html"/></para>
     344          </listitem>
     345          <listitem>
     346            <para>The Official Samba HOWTO and Reference Guide <ulink
     347            url="file:///usr/share/samba/swat/help/Samba-HOWTO-Collection/index.html"/>
     348            </para>
     349          </listitem>
     350          <listitem>
     351            <para>Samba-3 by Example
     352            <ulink url="file:///usr/share/samba/swat/help/Samba-Guide/index.html"/>
     353            </para>
     354          </listitem>
     355          <listitem>
     356            <para>The Samba-3 man Pages
     357            <ulink url="file:///usr/share/samba/swat/help/samba.7.html"/></para>
     358          </listitem>
     359        </itemizedlist>
     360
     361      </sect4>
    246362
    247363    </sect3>
    … …  
    255371      be inconvenient, undesireable or perhaps even impossible to gain
    256372      access to the console, BLFS recommends setting up access to SWAT using
    257       <application>Stunnel</application>.</para>
     373      <application>Stunnel</application>. Without
     374      <application>Stunnel</application>, the
     375      <systemitem class="username">root</systemitem> password is transmitted
     376      in clear text over the wire, and is considered an unacceptable security
     377      risk. After considering the security implications of using SWAT without
     378      <application>Stunnel</application>, and you still wish to implement SWAT
     379      without it, instructions are provided at this end of this section.</para>
    258380
    259381      <indexterm zone="samba3 samba3-swat-config">
    … …  
    261383      </indexterm>
    262384
    263       <para>First you must add entries to <filename>/etc/services</filename>
    264       and modify the <command>inetd</command>/<command>xinetd</command>
    265       configuration.</para>
    266 
    267       <indexterm zone="samba3 samba3-swat-config">
    268         <primary sortas="e-etc-services">/etc/services</primary>
    269       </indexterm>
    270 
    271       <indexterm zone="samba3 samba3-swat-config">
    272         <primary sortas="e-etc-inetd.conf">/etc/inetd.conf</primary>
    273       </indexterm>
    274 
    275       <indexterm zone="samba3 samba3-swat-config">
    276         <primary sortas="e-etc-xinetd.conf">/etc/xinetd.conf</primary>
    277       </indexterm>
    278 
    279       <para>Add swat and swat_tunnel entries to
    280       <filename>/etc/services</filename> with the following commands issued
    281       as the <systemitem class="username">root</systemitem> user:</para>
     385      <sect4>
     386        <title>Setting up SWAT using Stunnel</title>
     387
     388        <para>First install, or ensure you have already installed, the
     389        <xref linkend="stunnel"/> package.</para>
     390
     391        <para>Next you must add entries to <filename>/etc/services</filename>
     392        and modify the <command>inetd</command>/<command>xinetd</command>
     393        configuration.</para>
     394
     395        <indexterm zone="samba3 samba3-swat-config">
     396          <primary sortas="e-etc-services">/etc/services</primary>
     397        </indexterm>
     398
     399        <indexterm zone="samba3 samba3-swat-config">
     400          <primary sortas="e-etc-inetd.conf">/etc/inetd.conf</primary>
     401        </indexterm>
     402
     403        <indexterm zone="samba3 samba3-swat-config">
     404          <primary sortas="e-etc-xinetd.conf">/etc/xinetd.conf</primary>
     405        </indexterm>
     406
     407        <para>Add swat and swat_tunnel entries to
     408        <filename>/etc/services</filename> with the following commands issued
     409        as the <systemitem class="username">root</systemitem> user:</para>
    282410
    283411<screen role="root"><userinput>echo "swat            901/tcp" &gt;&gt; /etc/services &amp;&amp;
    284412echo "swat_tunnel     902/tcp" &gt;&gt; /etc/services</userinput></screen>
    285413
    286       <para>If <command>inetd</command> is used, the following command will
    287       add the swat_tunnel entry to <filename>/etc/inetd.conf</filename> (as
    288       user <systemitem class="username">root</systemitem>):</para>
     414        <para>If <command>inetd</command> is used, the following command will
     415        add the swat_tunnel entry to <filename>/etc/inetd.conf</filename> (as
     416        user <systemitem class="username">root</systemitem>):</para>
    289417
    290418<screen role="root"><userinput>echo "swat_tunnel stream tcp nowait.400 root /usr/sbin/swat swat" \
    291419    &gt;&gt; /etc/inetd.conf</userinput></screen>
    292420
    293       <para>Issue a <command>killall -HUP inetd</command> to reread the
    294       changed <filename>inetd.conf</filename> file.</para>
    295 
    296       <para>If you use <command>xinetd</command>, the following command will
    297       create the <application>Samba</application> file as
    298       <filename>/etc/xinetd.d/swat_tunnel</filename> (you may need to modify
    299       or remove the <quote>only_from</quote> line to include the desired
    300       host[s]):</para>
     421        <para>Issue a <command>killall -HUP inetd</command> to reread the
     422        changed <filename>inetd.conf</filename> file.</para>
     423
     424        <para>If you use <command>xinetd</command>, the following command will
     425        create the <application>Samba</application> file as
     426        <filename>/etc/xinetd.d/swat_tunnel</filename> (you may need to modify
     427        or remove the <quote>only_from</quote> line to include the desired
     428        host[s]):</para>
    301429
    302430<screen role="root"><userinput>cat &gt;&gt; /etc/xinetd.d/swat_tunnel &lt;&lt; "EOF"
    … …  
    317445EOF</userinput></screen>
    318446
    319       <indexterm zone="samba3 samba3-swat-config">
    320         <primary sortas="e-etc-xinetd.d-swat-tunnel">/etc/xinetd.d/swat_tunnel</primary>
    321       </indexterm>
    322 
    323       <para>Issue a <command>killall -HUP xinetd</command> to reread the
    324       changed <filename>xinetd.conf</filename> file.</para>
    325 
    326       <para>Next, you must add an entry for the swat service to the
    327       <filename>/etc/stunnel/stunnel.conf</filename> file (as user
    328       <systemitem class="username">root</systemitem>):</para>
    329 
    330       <indexterm zone="samba3 samba3-swat-config">
    331         <primary sortas="e-etc-stunnel-stunnel.conf">/etc/stunnel/stunnel.conf</primary>
    332       </indexterm>
     447        <indexterm zone="samba3 samba3-swat-config">
     448          <primary sortas="e-etc-xinetd.d-swat-tunnel">/etc/xinetd.d/swat_tunnel</primary>
     449        </indexterm>
     450
     451        <para>Issue a <command>killall -HUP xinetd</command> to read the new
     452        <filename>/etc/xinetd.d/swat_tunnel</filename> file.</para>
     453
     454        <para>Next, you must add an entry for the swat service to the
     455        <filename>/etc/stunnel/stunnel.conf</filename> file (as user
     456        <systemitem class="username">root</systemitem>):</para>
     457
     458        <indexterm zone="samba3 samba3-swat-config">
     459          <primary sortas="e-etc-stunnel-stunnel.conf">/etc/stunnel/stunnel.conf</primary>
     460        </indexterm>
    333461
    334462<screen role="root"><userinput>cat &gt;&gt; /etc/stunnel/stunnel.conf &lt;&lt; "EOF"
    … …  
    339467EOF</userinput></screen>
    340468
    341       <para>Restart the <command>stunnel</command> daemon using the following
    342       command as the <systemitem class="username">root</systemitem> user:</para>
     469        <para>Restart the <command>stunnel</command> daemon using the following
     470        command as the <systemitem class="username">root</systemitem> user:</para>
    343471
    344472<screen role="root"><userinput>/etc/rc.d/init.d/stunnel restart</userinput></screen>
    … …  
    350478      <replaceable>[CA_DN_field]</replaceable>.</para>
    351479
     480      </sect4>
     481
     482      <sect4>
     483        <title>Setting up SWAT without Stunnel</title>
     484
     485        <warning>
     486          <para>BLFS does not recommend using these procedures because of the
     487          security risk involved. However, in a home network environment and
     488          disclosure of the root password is an acceptable risk, the following
     489          instructions are provided for your convenience.</para>
     490        </warning>
     491
     492        <para>Add a swat entry to <filename>/etc/services</filename> with the
     493        following command issued as the
     494        <systemitem class='username'>root</systemitem> user:</para>
     495
     496<screen role='root'><userinput>echo "swat            901/tcp" &gt;&gt; /etc/services</userinput></screen>
     497
     498        <para>If <command>inetd</command> is used, the following command
     499        issed as the <systemitem class='username'>root</systemitem> user will
     500        add a swat entry to the <filename>/etc/inetd.conf</filename> file:</para>
     501
     502<screen role='root'><userinput>echo "swat stream tcp nowait.400 root /usr/sbin/swat swat" \
     503    &gt;&gt; /etc/inetd.conf</userinput></screen>
     504
     505        <para>Issue a <command>killall -HUP inetd</command> to reread the
     506        changed <filename>inetd.conf</filename> file.</para>
     507
     508        <para>If <command>xinetd</command> is used, the following command
     509        issued as the <systemitem class='username'>root</systemitem> user
     510        will create an <filename>/etc/xinetd.d/swat</filename> file:</para>
     511
     512<screen role='root'><userinput>cat &gt;&gt; /etc/xinetd.d/swat &lt;&lt; "EOF"
     513<literal># Begin /etc/xinetd.d/swat
     514
     515service swat
     516{
     517    port            = 901
     518    socket_type     = stream
     519    wait            = no
     520    only_from       = 127.0.0.1
     521    user            = root
     522    server          = /usr/sbin/swat
     523    log_on_failure  += USERID
     524}
     525
     526# End /etc/xinetd.d/swat</literal>
     527EOF</userinput></screen>
     528
     529        <para>Issue a <command>killall -HUP xinetd</command> to read the
     530        new <filename>/etc/xinetd.d/swat</filename> file.</para>
     531
     532        <para>SWAT can be launched by pointing your web browser to
     533        http://localhost:901.</para>
     534
     535      </sect4>
     536
     537    </sect3>
     538
     539    <sect3>
     540      <title/>
     541
    352542      <note>
    353543        <para>If you linked <application>Linux-PAM</application> into the
    … …  
    359549        <primary sortas="e-etc-pam.d-samba">/etc/pam.d/samba</primary>
    360550      </indexterm>
    361 
    362     </sect3>
    363 
    364     <sect3>
    365       <title>Printing to SMB Clients</title>
    366 
    367       <para>If you use <application>CUPS</application> for print services,
    368       and you wish to print to a printer attached to an SMB client, you
    369       need to create an SMB backend device. To create the device, issue the
    370       following command as the <systemitem class="username">root</systemitem>
    371       user:</para>
    372 
    373 <screen role="root"><userinput>ln -v -sf /usr/bin/smbspool /usr/lib/cups/backend/smb</userinput></screen>
    374551
    375552    </sect3>
    … …  
    394571        <primary sortas="f-winbind">winbind</primary>
    395572      </indexterm>
     573
     574      <para>The default <application>Samba</application> installation uses the
     575      <systemitem class='username'>nobody</systemitem> user for guest access
     576      to the server. This can be overridden by setting the
     577      <option>guest account =</option> parameter in the
     578      <filename>/etc/samba/smb.conf</filename> file. If you utilize the
     579      <option>guest account =</option> parameter, ensure this user exists in
     580      the <filename>/etc/passwd</filename> file. To use the default user,
     581      issue the following commands as the
     582      <systemitem class='username'>root</systemitem> user:</para>
     583
     584<screen><userinput>groupadd -g 99 nogroup &amp;&amp;
     585useradd -c "Unprivileged Nobody" -d /dev/null -g nogroup \
     586    -s /bin/false -u 99 nobody</userinput></screen>
    396587
    397588      <para>Install the <filename>samba</filename> script with the following
Note: See TracChangeset for help on using the changeset viewer.