diff options
Diffstat (limited to 'docs/Samba3-HOWTO')
| -rw-r--r-- | docs/Samba3-HOWTO/TOSHARG-BDC.xml | 20 | ||||
| -rw-r--r-- | docs/Samba3-HOWTO/TOSHARG-CUPS-printing.xml | 18 | ||||
| -rw-r--r-- | docs/Samba3-HOWTO/TOSHARG-Diagnosis.xml | 29 | ||||
| -rw-r--r-- | docs/Samba3-HOWTO/TOSHARG-FastStart.xml | 77 | ||||
| -rw-r--r-- | docs/Samba3-HOWTO/TOSHARG-Group-Mapping.xml | 6 | ||||
| -rw-r--r-- | docs/Samba3-HOWTO/TOSHARG-Install.xml | 12 | ||||
| -rw-r--r-- | docs/Samba3-HOWTO/TOSHARG-NetworkBrowsing.xml | 40 | ||||
| -rw-r--r-- | docs/Samba3-HOWTO/TOSHARG-Other-Clients.xml | 6 | ||||
| -rw-r--r-- | docs/Samba3-HOWTO/TOSHARG-PDC.xml | 14 | ||||
| -rw-r--r-- | docs/Samba3-HOWTO/TOSHARG-Passdb.xml | 20 | ||||
| -rw-r--r-- | docs/Samba3-HOWTO/TOSHARG-Printing.xml | 20 | ||||
| -rw-r--r-- | docs/Samba3-HOWTO/TOSHARG-StandAloneServer.xml | 14 | ||||
| -rw-r--r-- | docs/Samba3-HOWTO/TOSHARG-Unicode.xml | 6 | ||||
| -rw-r--r-- | docs/Samba3-HOWTO/TOSHARG-VFS.xml | 20 | ||||
| -rw-r--r-- | docs/Samba3-HOWTO/TOSHARG-Winbind.xml | 7 | ||||
| -rw-r--r-- | docs/Samba3-HOWTO/TOSHARG-WindowsClientConfig.xml | 10 | ||||
| -rw-r--r-- | docs/Samba3-HOWTO/TOSHARG-locking.xml | 16 | ||||
| -rw-r--r-- | docs/Samba3-HOWTO/TOSHARG-msdfs.xml | 8 |
18 files changed, 192 insertions, 151 deletions
diff --git a/docs/Samba3-HOWTO/TOSHARG-BDC.xml b/docs/Samba3-HOWTO/TOSHARG-BDC.xml index 7d4ff18dd7..c553950f76 100644 --- a/docs/Samba3-HOWTO/TOSHARG-BDC.xml +++ b/docs/Samba3-HOWTO/TOSHARG-BDC.xml @@ -251,13 +251,15 @@ parameters in the <smbconfsection name="[global]"/>-section of the &smb.conf; ha Refer to <link linkend="minimalPDC">following configuration</link> for an example of the minimum required settings. </para> -<para><smbconfexample id="minimalPDC"> +<example id="minimalPDC"> <title>Minimal smb.conf for a PDC in Use With a BDC &smbmdash; LDAP Server on PDC.</title> +<smbconfblock> <smbconfoption name="workgroup">&example.workgroup;</smbconfoption> <smbconfoption name="passdb backend">ldapsam://localhost:389</smbconfoption> <smbconfoption name="domain master">yes</smbconfoption> <smbconfoption name="domain logons">yes</smbconfoption> -</smbconfexample></para> +</smbconfblock> +</example> <para> Several other things like a <smbconfsection name="[homes]"/> and a @@ -341,15 +343,15 @@ In order to have a fall-back configuration (secondary) LDAP server one would spe the secondary LDAP server in the &smb.conf; file as shown in <link linkend="mulitldapcfg">following example</link>. </para> -<para> -<smbconfexample id="mulitldapcfg"> +<example id="mulitldapcfg"> <title>Multiple LDAP Servers in &smb.conf;</title> +<smbconfblock> <member>...</member> <smbconfoption name="passdb backend"> </smbconfoption> <member><parameter>ldapsam:"ldap://master.quenya.org ldap://slave.quenya.org"</parameter></member> <member>...</member> -</smbconfexample> -</para> +</smbconfblock> +</example> </sect2> @@ -509,14 +511,16 @@ The creation of a BDC requires some steps to prepare the Samba server before done by setting Samba as shown in <link linkend="minim-bdc">the next example</link>. </para> -<para><smbconfexample id="minim-bdc"> +<example id="minim-bdc"> <title>Minimal setup for being a BDC</title> +<smbconfblock> <smbconfoption name="workgroup">&example.workgroup;</smbconfoption> <smbconfoption name="passdb backend">ldapsam:ldap://slave-ldap.quenya.org</smbconfoption> <smbconfoption name="domain master">no</smbconfoption> <smbconfoption name="domain logons">yes</smbconfoption> <smbconfoption name="idmap backend">ldap:ldap://slave-ldap.quenya.org</smbconfoption> -</smbconfexample></para> +</smbconfblock> +</example> <para> In the <smbconfsection name="[global]"/>-section of the &smb.conf; of the BDC. This makes the BDC diff --git a/docs/Samba3-HOWTO/TOSHARG-CUPS-printing.xml b/docs/Samba3-HOWTO/TOSHARG-CUPS-printing.xml index cd96ba60ab..12f797c84a 100644 --- a/docs/Samba3-HOWTO/TOSHARG-CUPS-printing.xml +++ b/docs/Samba3-HOWTO/TOSHARG-CUPS-printing.xml @@ -156,8 +156,9 @@ libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000) To summarize, <link linkend="cups-exam-simple">following example</link> shows simplest printing-related setup for &smb.conf; to enable basic CUPS support: </para> - <para><smbconfexample id="cups-exam-simple"> + <example id="cups-exam-simple"> <title>Simplest printing-related smb.conf</title> + <smbconfblock> <smbconfsection name="[global]"/> <smbconfoption name="load printers">yes</smbconfoption> <smbconfoption name="printing">cups</smbconfoption> @@ -173,7 +174,8 @@ libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000) <smbconfoption name="printable">yes</smbconfoption> <smbconfoption name="printer admin">root, @ntadmins</smbconfoption> - </smbconfexample></para> + </smbconfblock> + </example> <para> This is all you need for basic printing setup for CUPS. It will print @@ -203,8 +205,9 @@ libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000) up differently. </para> - <para><smbconfexample id="overridesettings"> + <example id="overridesettings"> <title>Overriding global CUPS settings for one printer</title> + <smbconfblock> <smbconfsection name="[global]"/> <smbconfoption name="printing">cups</smbconfoption> <smbconfoption name="printcap name">cups</smbconfoption> @@ -235,7 +238,8 @@ libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000) <smbconfoption name="printer admin">kurt</smbconfoption> <smbconfoption name="hosts deny">0.0.0.0</smbconfoption> <smbconfoption name="hosts allow">turbo_xp, 10.160.50.23, 10.160.51.60</smbconfoption> - </smbconfexample></para> + </smbconfblock> + </example> <para> This special share is only there for testing purposes. It does not write the print job to a file. It just logs the job parameters @@ -2475,8 +2479,9 @@ Prior to running <command>cupsaddsmb</command>, you need the settings in &smb.conf; as shown in <link linkend="cupsadd-ex">the next example</link>: </para> -<para><smbconfexample id="cupsadd-ex"> +<example id="cupsadd-ex"> <title>smb.conf for cupsaddsmb usage</title> +<smbconfblock> <smbconfsection name="[global]"/> <smbconfoption name="load printers">yes</smbconfoption> <smbconfoption name="printing">cups</smbconfoption> @@ -2499,7 +2504,8 @@ Prior to running <command>cupsaddsmb</command>, you need the settings in <smbconfoption name="guest ok">no</smbconfoption> <smbconfoption name="read only">yes</smbconfoption> <smbconfoption name="write list">root</smbconfoption> -</smbconfexample></para> +</smbconfblock> +</example> </sect2> <sect2> diff --git a/docs/Samba3-HOWTO/TOSHARG-Diagnosis.xml b/docs/Samba3-HOWTO/TOSHARG-Diagnosis.xml index 9f4f3dd2c0..6b844dc17e 100644 --- a/docs/Samba3-HOWTO/TOSHARG-Diagnosis.xml +++ b/docs/Samba3-HOWTO/TOSHARG-Diagnosis.xml @@ -55,14 +55,15 @@ You can add a <smbconfsection name="tmp"/> share like this by adding the lines shown in <link linkend="tmpshare">the next example</link>. </para> -<para><smbconfexample id="tmpshare"> -<title>smb.conf with [tmp] share</title> +<example id="tmpshare"> + <title>smb.conf with [tmp] share</title> + <smbconfblock> <smbconfsection name="[tmp]"/> <smbconfoption name="comment">temporary files </smbconfoption> <smbconfoption name="path">/tmp</smbconfoption> <smbconfoption name="read only">yes</smbconfoption> -</smbconfexample> -</para> +</smbconfblock> +</example> <note><para> These tests assume version 3.0.0 or later of the Samba suite. @@ -239,18 +240,16 @@ the &smb.conf; file entries as shown in <link linkend="modif1">the next example< </para> -<para> -<smbconfexample id="modif1"> +<example id="modif1"> <title>Configuration for only allowing connections from a certain subnet</title> + <smbconfblock> <smbconfsection name="[globals]"/> -<member>...</member> <smbconfoption name="hosts deny">ALL</smbconfoption> <smbconfoption name="hosts allow">xxx.xxx.xxx.xxx/yy</smbconfoption> <smbconfoption name="interfaces">eth0</smbconfoption> <smbconfoption name="bind interfaces only">Yes</smbconfoption> -<member>...</member> -</smbconfexample> -</para> +</smbconfblock> +</example> <para> In the above, no allowance has been made for any session requests that @@ -258,17 +257,15 @@ will automatically translate to the loopback adapter address 127.0.0.1. To solve this problem, change these lines as shown in <link linkend="modif2">the following example</link>. </para> -<para> -<smbconfexample id="modif2"> +<example id="modif2"> <title>Configuration for allowing connections from a certain subnet and localhost</title> + <smbconfblock> <smbconfsection name="[globals]"/> -<member>...</member> <smbconfoption name="hosts deny">ALL</smbconfoption> <smbconfoption name="hosts allow">xxx.xxx.xxx.xxx/yy 127.</smbconfoption> <smbconfoption name="interfaces">eth0 lo</smbconfoption> -<member>...</member> -</smbconfexample> -</para> +</smbconfblock> +</example> <para> <indexterm><primary>inetd</primary></indexterm> diff --git a/docs/Samba3-HOWTO/TOSHARG-FastStart.xml b/docs/Samba3-HOWTO/TOSHARG-FastStart.xml index 5395f69070..108c787d64 100644 --- a/docs/Samba3-HOWTO/TOSHARG-FastStart.xml +++ b/docs/Samba3-HOWTO/TOSHARG-FastStart.xml @@ -139,8 +139,9 @@ of the packages that are provided by the operating system vendor, or through oth <para>The configuration file is:</para> - <para><smbconfexample id="anon-example"> + <example id="anon-example"> <title>Anonymous Read-Only Server Configuration</title> + <smbconfblock> <smbconfcomment>Global parameters</smbconfcomment> <smbconfsection name="[global]"/> <smbconfoption name="workgroup">MIDEARTH</smbconfoption> @@ -152,8 +153,8 @@ of the packages that are provided by the operating system vendor, or through oth <smbconfoption name="path">/export</smbconfoption> <smbconfoption name="read only">Yes</smbconfoption> <smbconfoption name="guest ok">Yes</smbconfoption> - </smbconfexample> - </para> + </smbconfblock> + </example> <itemizedlist> <listitem><para> @@ -274,8 +275,8 @@ Added user jackb. The complete, modified &smb.conf; file is as shown in <link linkend="anon-rw"/>. </para> - <para> -<smbconfexample id="anon-rw"><title>Modified Anonymous Read-Write smb.conf</title> +<example id="anon-rw"><title>Modified Anonymous Read-Write smb.conf</title> + <smbconfblock> <smbconfcomment>Global parameters</smbconfcomment> <smbconfsection name="[global]"/> <smbconfoption name="workgroup">MIDEARTH</smbconfoption> @@ -289,8 +290,8 @@ Added user jackb. <smbconfoption name="force group">users</smbconfoption> <smbconfoption name="read only">No</smbconfoption> <smbconfoption name="guest ok">Yes</smbconfoption> -</smbconfexample> - </para> +</smbconfblock> +</example> </sect3> @@ -327,8 +328,8 @@ Added user jackb. configuration. <link linkend="anon-print"></link> is the resulting &smb.conf; file. </para> - <para> -<smbconfexample id="anon-print"><title>Anonymous Print Server smb.conf</title> +<example id="anon-print"><title>Anonymous Print Server smb.conf</title> +<smbconfblock> <smbconfcomment>Global parameters</smbconfcomment> <smbconfsection name="[global]"/> <smbconfoption name="workgroup">MIDEARTH</smbconfoption> @@ -346,8 +347,8 @@ Added user jackb. <smbconfoption name="printable">Yes</smbconfoption> <smbconfoption name="use client driver">Yes</smbconfoption> <smbconfoption name="browseable">No</smbconfoption> -</smbconfexample> - </para> +</smbconfblock> +</example> <para> The above configuration is not ideal. It uses no smart features, and it deliberately @@ -449,8 +450,10 @@ Added user jackb. <step><para> Configure the Samba &smb.conf; file as shown in <link linkend="OfficeServer"/>. -<smbconfexample id="OfficeServer"> -<title>Secure Office Server smb.conf</title> + </para> +<example id="OfficeServer"> + <title>Secure Office Server smb.conf</title> + <smbconfblock> <smbconfcomment>Global parameters</smbconfcomment> <smbconfsection name="[global]"/> <smbconfoption name="workgroup">MIDEARTH</smbconfoption> @@ -483,8 +486,8 @@ Added user jackb. <smbconfoption name="printable">Yes</smbconfoption> <smbconfoption name="use client driver">Yes</smbconfoption> <smbconfoption name="browseable">No</smbconfoption> - </smbconfexample> - </para></step> + </smbconfblock> + </example></step> <step><para> Initialize the Microsoft Windows password database with the new users: @@ -663,9 +666,9 @@ smb: \> <userinput>q</userinput> and <link linkend="fast-memberserver-shares"></link>. </para> - <para> - <smbconfexample id="fast-member-server"> + <example id="fast-member-server"> <title>Member server smb.conf (globals)</title> + <smbconfblock> <smbconfcomment>Global parameters</smbconfcomment> <smbconfsection name="[global]"/> <smbconfoption name="workgroup">MIDEARTH</smbconfoption> @@ -678,11 +681,11 @@ smb: \> <userinput>q</userinput> <smbconfoption name="idmap gid">15000-20000</smbconfoption> <smbconfoption name="winbind use default domain">Yes</smbconfoption> <smbconfoption name="printing">cups</smbconfoption> - </smbconfexample></para> + </smbconfblock></example> - <para> - <smbconfexample id="fast-memberserver-shares"> + <example id="fast-memberserver-shares"> <title>Member server smb.conf (shares and services)</title> + <smbconfblock> <smbconfsection name="[homes]"/> <smbconfoption name="comment">Home Directories</smbconfoption> <smbconfoption name="valid users">%S</smbconfoption> @@ -710,8 +713,8 @@ smb: \> <userinput>q</userinput> <smbconfoption name="printable">Yes</smbconfoption> <smbconfoption name="use client driver">Yes</smbconfoption> <smbconfoption name="browseable">No</smbconfoption> - </smbconfexample> - </para></step> + </smbconfblock> + </example></step> <step><para> @@ -892,8 +895,9 @@ maryo:x:15000:15003:Mary Orville:/home/MIDEARTH/maryo:/bin/false <para> <indexterm><primary>pdbedit</primary></indexterm> - <smbconfexample id="fast-engoffice-global"> + <example id="fast-engoffice-global"> <title>Engineering Office smb.conf (globals)</title> + <smbconfblock> <smbconfsection name="[global]"/> <smbconfoption name="workgroup">MIDEARTH</smbconfoption> <smbconfoption name="netbios name">FRODO</smbconfoption> @@ -920,10 +924,13 @@ maryo:x:15000:15003:Mary Orville:/home/MIDEARTH/maryo:/bin/false <smbconfoption name="idmap uid">15000-20000</smbconfoption> <smbconfoption name="idmap gid">15000-20000</smbconfoption> <smbconfoption name="printing">cups</smbconfoption> - </smbconfexample> + </smbconfblock> + </example> + </para> - <smbconfexample id="fast-engoffice-shares"> + <example id="fast-engoffice-shares"> <title>Engineering Office smb.conf (shares and services)</title> + <smbconfblock> <smbconfsection name="[homes]"/> <smbconfoption name="comment">Home Directories</smbconfoption> <smbconfoption name="valid users">%S</smbconfoption> @@ -963,8 +970,8 @@ maryo:x:15000:15003:Mary Orville:/home/MIDEARTH/maryo:/bin/false <smbconfoption name="profile acls">Yes</smbconfoption> <smbconfcomment>Other resource (share/printer) definitions would follow below.</smbconfcomment> - </smbconfexample> - </para></step> + </smbconfblock> + </example></step> <step><para> Create UNIX group accounts as needed using a suitable operating system tool: @@ -1156,9 +1163,9 @@ userPassword: {SSHA}0jBHgQ1vp4EDX2rEMMfIudvRMJoGwjVb The &smb.conf; file that drives this backend can be found in example <link linkend="fast-ldap"/>. </para> - <para> -<smbconfexample id="fast-ldap"> +<example id="fast-ldap"> <title>LDAP backend smb.conf for PDC</title> +<smbconfblock> <smbconfcomment>Global parameters</smbconfcomment> <smbconfsection name="[global]"/> <smbconfoption name="workgroup">MIDEARTH</smbconfoption> @@ -1193,8 +1200,8 @@ userPassword: {SSHA}0jBHgQ1vp4EDX2rEMMfIudvRMJoGwjVb <smbconfoption name="idmap uid">15000-20000</smbconfoption> <smbconfoption name="idmap gid">15000-20000</smbconfoption> <smbconfoption name="printing">cups</smbconfoption> -</smbconfexample> - </para></step> +</smbconfblock> + </example></step> <step><para> Add the LDAP password to the <filename>secrets.tdb</filename> file so Samba can update @@ -1226,8 +1233,10 @@ userPassword: {SSHA}0jBHgQ1vp4EDX2rEMMfIudvRMJoGwjVb Decide if the BDC should have its own LDAP server or not. If the BDC is to be the LDAP server change the following &smb.conf; as indicated. The default configuration in <link linkend="fast-bdc"/> uses a central LDAP server. -<smbconfexample id="fast-bdc"> + </para> +<example id="fast-bdc"> <title>Remote LDAP BDC smb.conf</title> +<smbconfblock> <smbconfcomment>Global parameters</smbconfcomment> <smbconfsection name="[global]"/> <smbconfoption name="workgroup">MIDEARTH</smbconfoption> @@ -1254,8 +1263,8 @@ userPassword: {SSHA}0jBHgQ1vp4EDX2rEMMfIudvRMJoGwjVb <smbconfoption name="idmap uid">15000-20000</smbconfoption> <smbconfoption name="idmap gid">15000-20000</smbconfoption> <smbconfoption name="printing">cups</smbconfoption> -</smbconfexample> - </para></step> +</smbconfblock> + </example></step> <step><para> Configure the NETLOGON and PROFILES directory as for the PDC in <link linkend="fast-bdc"/>. diff --git a/docs/Samba3-HOWTO/TOSHARG-Group-Mapping.xml b/docs/Samba3-HOWTO/TOSHARG-Group-Mapping.xml index b0e1a8cf48..a2625edb77 100644 --- a/docs/Samba3-HOWTO/TOSHARG-Group-Mapping.xml +++ b/docs/Samba3-HOWTO/TOSHARG-Group-Mapping.xml @@ -642,11 +642,13 @@ exit 0 <para> The &smb.conf; entry for the above script would be something like that in <link linkend="smbgrpadd">the following example</link>. -<smbconfexample id="smbgrpadd" fragment="1"> +<example id="smbgrpadd"> <title>Configuration of &smb.conf; for the add group script.</title> +<smbconfblock> <smbconfsection name="[global]"/> <smbconfoption name="add group script">/path_to_tool/smbgrpadd.sh "%g"</smbconfoption> -</smbconfexample> +</smbconfblock> +</example> </para> </sect2> diff --git a/docs/Samba3-HOWTO/TOSHARG-Install.xml b/docs/Samba3-HOWTO/TOSHARG-Install.xml index 1cec899cdd..1d9445e50b 100644 --- a/docs/Samba3-HOWTO/TOSHARG-Install.xml +++ b/docs/Samba3-HOWTO/TOSHARG-Install.xml @@ -61,8 +61,9 @@ <indexterm><primary>minimal configuration</primary></indexterm> </para> - <smbconfexample id="smbconfminimal"> + <example id="smbconfminimal"> <title>A minimal smb.conf</title> + <smbconfblock> <smbconfsection name="[global]"/> <smbconfoption name="workgroup">WKG</smbconfoption> @@ -73,7 +74,8 @@ <smbconfsection name="[share2]"/> <smbconfoption name="path">/my_shared_folder</smbconfoption> <smbconfoption name="comment">Some random files</smbconfoption> - </smbconfexample> + </smbconfblock> + </example> </sect2> @@ -149,15 +151,17 @@ <para> <indexterm><primary>simple configuration</primary></indexterm> - <smbconfexample id="simple-example"> + <example id="simple-example"> <title>Another simple smb.conf File</title> + <smbconfblock> <smbconfsection name="[global]"/> <smbconfoption name="workgroup">&example.workgroup;</smbconfoption> <smbconfsection name="[homes]"/> <smbconfoption name="guest ok">no</smbconfoption> <smbconfoption name="read only">no</smbconfoption> - </smbconfexample> + </smbconfblock> +</example> </para> <para> diff --git a/docs/Samba3-HOWTO/TOSHARG-NetworkBrowsing.xml b/docs/Samba3-HOWTO/TOSHARG-NetworkBrowsing.xml index dbbaac7b08..e9f39414d5 100644 --- a/docs/Samba3-HOWTO/TOSHARG-NetworkBrowsing.xml +++ b/docs/Samba3-HOWTO/TOSHARG-NetworkBrowsing.xml @@ -624,16 +624,16 @@ options in the <smbconfsection name="[global]"/> section of the &smb.conf; file as shown in <link linkend="dmbexample">the following example</link>: </para> -<para> -<smbconfexample id="dmbexample"> +<example id="dmbexample"> <title>Domain Master Browser smb.conf</title> +<smbconfblock> <smbconfsection name="[global]"/> <smbconfoption name="domain master">yes</smbconfoption> <smbconfoption name="local master">yes</smbconfoption> <smbconfoption name="preferred master">yes</smbconfoption> <smbconfoption name="os level">65</smbconfoption> -</smbconfexample> -</para> +</smbconfblock> +</example> <para> The Domain Master Browser may be the same machine as the WINS server, if necessary. @@ -649,16 +649,16 @@ server a Local Master Browser set the following options in the shown in <link linkend="lmbexample">following example</link>: </para> -<para> -<smbconfexample id="lmbexample"> +<example id="lmbexample"> <title>Local master browser smb.conf</title> +<smbconfblock> <smbconfsection name="[global]"/> <smbconfoption name="domain master">no</smbconfoption> <smbconfoption name="local master">yes</smbconfoption> <smbconfoption name="preferred master">yes</smbconfoption> <smbconfoption name="os level">65</smbconfoption> -</smbconfexample> -</para> +</smbconfblock> +</example> <para> Do not do this for more than one Samba server on each subnet, or they will war with @@ -678,16 +678,16 @@ becoming a Local Master Browser by setting the following options in the <smbconf &smb.conf; file as shown in <link linkend="nombexample">following example</link>: </para> -<para> -<smbconfexample id="nombexample"> +<example id="nombexample"> <title>smb.conf for not being a Master Browser</title> +<smbconfblock> <smbconfsection name="[global]"/> <smbconfoption name="domain master">no</smbconfoption> <smbconfoption name="local master">no</smbconfoption> <smbconfoption name="preferred master">no</smbconfoption> <smbconfoption name="os level">0</smbconfoption> -</smbconfexample> -</para> +</smbconfblock> +</example> </sect2> @@ -707,16 +707,16 @@ described. To make a Samba server a Local Master Browser, set the following opti of the &smb.conf; file as shown in <link linkend="remsmb">following example</link>: </para> -<para> -<smbconfexample id="remsmb"> +<example id="remsmb"> <title>Local Master Browser smb.conf</title> +<smbconfblock> <smbconfsection name="[global]"/> <smbconfoption name="domain master">no</smbconfoption> <smbconfoption name="local master">yes</smbconfoption> <smbconfoption name="preferred master">yes</smbconfoption> <smbconfoption name="os level">65</smbconfoption> -</smbconfexample> -</para> +</smbconfblock> +</example> <para> If you wish to have a Samba server fight the election with machines on the same subnet you @@ -732,16 +732,16 @@ and ever becoming a Local Master Browser by setting the following options in the <smbconfsection name="[global]"/> section of the &smb.conf; file as shown in <link linkend="xremmb">next example</link>: </para> -<para> -<smbconfexample id="xremmb"> +<example id="xremmb"> <title>&smb.conf; for not being a master browser</title> +<smbconfblock> <smbconfsection name="[global]"/> <smbconfoption name="domain master">no</smbconfoption> <smbconfoption name="local master">no</smbconfoption> <smbconfoption name="preferred master">no</smbconfoption> <smbconfoption name="os level">0</smbconfoption> -</smbconfexample> -</para> +</smbconfblock> +</example> </sect2> diff --git a/docs/Samba3-HOWTO/TOSHARG-Other-Clients.xml b/docs/Samba3-HOWTO/TOSHARG-Other-Clients.xml index 0a0d78fd91..61f100f7c6 100644 --- a/docs/Samba3-HOWTO/TOSHARG-Other-Clients.xml +++ b/docs/Samba3-HOWTO/TOSHARG-Other-Clients.xml @@ -308,15 +308,17 @@ releases prior to Samba 2.2.2. <link linkend="minimalprofile">Following example</link> provides a minimal profile share. </para> -<para><smbconfexample id="minimalprofile"> +<example id="minimalprofile"> <title>Minimal profile share</title> +<smbconfblock> <smbconfsection name="[profile]"/> <smbconfoption name="path">/export/profile</smbconfoption> <smbconfoption name="create mask">0600</smbconfoption> <smbconfoption name="directory mask">0700</smbconfoption> <smbconfoption name="nt acl support">no</smbconfoption> <smbconfoption name="read only">no</smbconfoption> -</smbconfexample></para> +</smbconfblock> +</example> <para> The reason for this bug is that the Windows 200x SP2 client copies diff --git a/docs/Samba3-HOWTO/TOSHARG-PDC.xml b/docs/Samba3-HOWTO/TOSHARG-PDC.xml index 595deaa0ca..e28de99470 100644 --- a/docs/Samba3-HOWTO/TOSHARG-PDC.xml +++ b/docs/Samba3-HOWTO/TOSHARG-PDC.xml @@ -426,9 +426,9 @@ The first step in creating a working Samba PDC is to understand the parameters n in &smb.conf;. An example &smb.conf; for acting as a PDC can be found in <link linkend="pdc-example">the next example</link>. </para> -<para> -<smbconfexample id="pdc-example"> +<example id="pdc-example"> <title>smb.conf for being a PDC</title> +<smbconfblock> <smbconfsection name="[global]"/> <smbconfoption name="netbios name"><replaceable>BELERIAND</replaceable></smbconfoption> <smbconfoption name="workgroup"><replaceable>&example.workgroup;</replaceable></smbconfoption> @@ -454,8 +454,8 @@ in &smb.conf;. An example &smb.conf; for acting as a PDC can be found in <link l <smbconfoption name="read only">no</smbconfoption> <smbconfoption name="create mask">0600</smbconfoption> <smbconfoption name="directory mask">0700</smbconfoption> -</smbconfexample> -</para> +</smbconfblock> +</example> <para> The basic options shown in <link linkend="pdc-example">this example</link> are explained as follows: @@ -582,8 +582,9 @@ must be set. <sect3> <title>Example Configuration</title> -<smbconfexample id="PDC-config"> +<example id="PDC-config"> <title>smb.conf for being a PDC</title> +<smbconfblock> <smbconfsection name="[global]"/> <smbconfoption name="domain logons">Yes</smbconfoption> <smbconfoption name="domain master">(Yes on PDC, No on BDCs)</smbconfoption> @@ -593,7 +594,8 @@ must be set. <smbconfoption name="path">/var/lib/samba/netlogon</smbconfoption> <smbconfoption name="guest ok">Yes</smbconfoption> <smbconfoption name="browseable">No</smbconfoption> -</smbconfexample> +</smbconfblock> +</example> </sect3> <sect3> diff --git a/docs/Samba3-HOWTO/TOSHARG-Passdb.xml b/docs/Samba3-HOWTO/TOSHARG-Passdb.xml index 45077188e8..00ac479e2b 100644 --- a/docs/Samba3-HOWTO/TOSHARG-Passdb.xml +++ b/docs/Samba3-HOWTO/TOSHARG-Passdb.xml @@ -418,13 +418,15 @@ Samba-3 introduces a number of new password backend capabilities. <para> <indexterm><primary>SAM backend</primary><secondary>ldapsam</secondary></indexterm> -<smbconfexample id="idmapbackendexample"> +<example id="idmapbackendexample"> <title>Example configuration with the LDAP idmap backend</title> +<smbconfblock> <smbconfsection name="[global]"/> <smbconfoption name="idmap backend">ldap:ldap://ldap-server.quenya.org:636</smbconfoption> <smbconfcomment>Alternately, this could be specified as:</smbconfcomment> <smbconfoption name="idmap backend">ldap:ldaps://ldap-server.quenya.org</smbconfoption> -</smbconfexample> +</smbconfblock> +</example> </para> <para> @@ -1148,9 +1150,9 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz use with an LDAP directory could appear as shown below. </para> -<para> -<smbconfexample id="confldapex"> +<example id="confldapex"> <title>Configuration with LDAP</title> +<smbconfblock> <smbconfsection name="[global]"/> <smbconfoption name="security">user</smbconfoption> <smbconfoption name="encrypt passwords">yes</smbconfoption> @@ -1190,8 +1192,8 @@ userPassword: {SSHA}c3ZM9tBaBo9autm1dL3waDS21+JSfQVz <smbconfcomment> generally the default ldap search filter is ok</smbconfcomment> <smbconfoption name="ldap filter">(uid=%u)</smbconfoption> -</smbconfexample> -</para> +</smbconfblock> +</example> </sect3> @@ -1634,8 +1636,9 @@ access to attrs=SambaLMPassword,SambaNTPassword <para><link linkend="mysqlsam">An example configuration</link> looks like: </para> - <smbconfexample id="mysqlsam"> + <example id="mysqlsam"> <title>Example configuration for the MySQL passdb backend</title> + <smbconfblock> <smbconfsection name="[global]"/> <smbconfoption name="passdb backend">mysql:foo</smbconfoption> <smbconfoption name="foo:mysql user">samba</smbconfoption> @@ -1650,7 +1653,8 @@ access to attrs=SambaLMPassword,SambaNTPassword <smbconfoption name="foo:nt pass column">nt_pass:</smbconfoption> <smbconfcomment>The unknown 3 column is not stored</smbconfcomment> <smbconfoption name="foo:unknown 3 column">NULL</smbconfoption> - </smbconfexample> + </smbconfblock> + </example> </sect3> <sect3> diff --git a/docs/Samba3-HOWTO/TOSHARG-Printing.xml b/docs/Samba3-HOWTO/TOSHARG-Printing.xml index 349d64f7f9..b5488fca65 100644 --- a/docs/Samba3-HOWTO/TOSHARG-Printing.xml +++ b/docs/Samba3-HOWTO/TOSHARG-Printing.xml @@ -186,9 +186,9 @@ However, in many environments these are enough to provide a valid &smb.conf; file that enables all clients to print. </para> -<para> -<smbconfexample id="simpleprc"> +<example id="simpleprc"> <title>Simple configuration with BSD printing</title> +<smbconfblock> <smbconfsection name="[global]"/> <smbconfoption name="printing">bsd</smbconfoption> <smbconfoption name="load printers">yes</smbconfoption> @@ -198,7 +198,8 @@ However, in many environments these are enough to provide a valid <smbconfoption name="printable">yes</smbconfoption> <smbconfoption name="public">yes</smbconfoption> <smbconfoption name="writable">no</smbconfoption> -</smbconfexample></para> +</smbconfblock> +</example> <para> This is only an example configuration. Samba assigns default values to @@ -446,8 +447,9 @@ by default. You could use a much leaner &smb.conf; file. Alternately, you can us file to remove all parameters that are set at default. </para> -<para><smbconfexample id="extbsdpr"> +<example id="extbsdpr"> <title>Extended BSD Printing Configuration</title> + <smbconfblock> <smbconfsection name="[global]"/> <smbconfoption name="printing">bsd</smbconfoption> <smbconfoption name="load printers">yes</smbconfoption> @@ -478,7 +480,7 @@ file to remove all parameters that are set at default. <smbconfoption name="hosts allow">0.0.0.0</smbconfoption> <smbconfoption name="hosts deny">turbo_xp, 10.160.50.23, 10.160.51.60</smbconfoption> <smbconfoption name="guest ok">no</smbconfoption> -</smbconfexample></para> +</smbconfblock></example> <para> This is an example configuration. You may not find all the settings that are in @@ -1141,9 +1143,9 @@ as <smbconfoption name="path"/> are arbitrary and should be replaced with approp site). See <link linkend="prtdollar">next example</link>. </para> -<para> -<smbconfexample id="prtdollar"> +<example id="prtdollar"> <title>[print\$] example</title> +<smbconfblock> <smbconfsection name="[global]"/> <smbconfcomment>members of the ntadmin group should be able to add drivers and set</smbconfcomment> <smbconfcomment>printer properties. root is implicitly always a 'printer admin'.</smbconfcomment> @@ -1158,8 +1160,8 @@ site). See <link linkend="prtdollar">next example</link>. <smbconfoption name="guest ok">yes</smbconfoption> <smbconfoption name="read only">yes</smbconfoption> <smbconfoption name="write list">@ntadmin, root</smbconfoption> -</smbconfexample> -</para> +</smbconfblock> +</example> <para> Of course, you also need to ensure that the directory named by the diff --git a/docs/Samba3-HOWTO/TOSHARG-StandAloneServer.xml b/docs/Samba3-HOWTO/TOSHARG-StandAloneServer.xml index ad1b69e79e..c1874d0e49 100644 --- a/docs/Samba3-HOWTO/TOSHARG-StandAloneServer.xml +++ b/docs/Samba3-HOWTO/TOSHARG-StandAloneServer.xml @@ -102,8 +102,9 @@ nobody. No home directories are shared, and there are no users in the <filename> UNIX system database. This is a simple system to administer. </para> -<smbconfexample id="simplynice"> +<example id="simplynice"> <title>smb.conf for Reference Documentation Server</title> +<smbconfblock> <smbconfcomment> Global parameters</smbconfcomment> <smbconfsection name="[global]"/> <smbconfoption name="workgroup">&example.workgroup;</smbconfoption> @@ -115,7 +116,8 @@ UNIX system database. This is a simple system to administer. <smbconfoption name="comment">Data</smbconfoption> <smbconfoption name="path">/export</smbconfoption> <smbconfoption name="guest only">Yes</smbconfoption> -</smbconfexample> +</smbconfblock> +</example> <para> In <link linkend="simplynice">the example</link> above, the machine name is set to &example.server.samba;, the workgroup is set to the name @@ -193,9 +195,9 @@ the anonymous (guest) user, two things will be required: The contents of the &smb.conf; file is shown in <link linkend="AnonPtrSvr">the next example</link>. </para> -<para> -<smbconfexample id="AnonPtrSvr"> +<example id="AnonPtrSvr"> <title>&smb.conf; for Anonymous Printing</title> +<smbconfblock> <smbconfcomment> Global parameters</smbconfcomment> <smbconfsection name="[global]"/> <smbconfoption name="workgroup">&example.workgroup;</smbconfoption> @@ -213,8 +215,8 @@ The contents of the &smb.conf; file is shown in <link linkend="AnonPtrSvr">the n <smbconfoption name="printable">Yes</smbconfoption> <smbconfoption name="use client driver">Yes</smbconfoption> <smbconfoption name="browseable">No</smbconfoption> -</smbconfexample> -</para> +</smbconfblock> +</example> <note><para> diff --git a/docs/Samba3-HOWTO/TOSHARG-Unicode.xml b/docs/Samba3-HOWTO/TOSHARG-Unicode.xml index a858a38508..761116c818 100644 --- a/docs/Samba3-HOWTO/TOSHARG-Unicode.xml +++ b/docs/Samba3-HOWTO/TOSHARG-Unicode.xml @@ -374,7 +374,8 @@ Setting up Japanese charsets is quite difficult. This is mainly because: as follows: </para> -<smbconfexample><title>VFS CAP</title> +<example><title>VFS CAP</title> + <smbconfblock> <smbconfsection name="[global]"/> <smbconfcomment>the locale name "CP932" may be different</smbconfcomment> <smbconfoption name="dos charset">CP932</smbconfoption> @@ -382,7 +383,8 @@ Setting up Japanese charsets is quite difficult. This is mainly because: <smbconfsection name="[cap-share]"/> <smbconfoption name="vfs option">cap</smbconfoption> -</smbconfexample> +</smbconfblock> +</example> <para> You should set CP932 if using GNU libiconv for unix charset. Setting this, diff --git a/docs/Samba3-HOWTO/TOSHARG-VFS.xml b/docs/Samba3-HOWTO/TOSHARG-VFS.xml index 3fdcc0ea81..0ccc1188fe 100644 --- a/docs/Samba3-HOWTO/TOSHARG-VFS.xml +++ b/docs/Samba3-HOWTO/TOSHARG-VFS.xml @@ -40,15 +40,17 @@ important parameter is the <smbconfoption name="vfs objects"/> parameter where you can list one or more VFS modules by name. For example, to log all access to files and put deleted files in a recycle bin, see <link linkend="vfsrecyc">next configuration</link>: -<smbconfexample id="vfsrecyc"> +<example id="vfsrecyc"> <title>smb.conf with VFS modules</title> + <smbconfblock> <smbconfsection name="[audit]"/> <smbconfoption name="comment">Audited /data directory</smbconfoption> <smbconfoption name="path">/data</smbconfoption> <smbconfoption name="vfs objects">audit recycle</smbconfoption> <smbconfoption name="writeable">yes</smbconfoption> <smbconfoption name="browseable">yes</smbconfoption> - </smbconfexample> + </smbconfblock> +</example> </para> <para> @@ -70,8 +72,9 @@ Samba installation (usually <filename>/usr/lib/samba/vfs</filename> or <filename Some modules can be used twice for the same share. This can be done using a configuration similar to the one shown in <link linkend="multimodule">the following example</link>. -<smbconfexample id="multimodule"> +<example id="multimodule"> <title>smb.conf with multiple VFS modules</title> + <smbconfblock> <smbconfsection name="[test]"/> <smbconfoption name="comment">VFS TEST</smbconfoption> <smbconfoption name="path">/data</smbconfoption> @@ -81,7 +84,8 @@ This can be done using a configuration similar to the one shown in <link linkend <smbconfoption name="example1: parameter">1</smbconfoption> <smbconfoption name="example: parameter">5</smbconfoption> <smbconfoption name="test: parameter">7</smbconfoption> -</smbconfexample> +</smbconfblock> +</example> </para> </sect1> @@ -502,17 +506,17 @@ This can be done using a configuration similar to the one shown in <link linkend standard. Here is our example of a share configured with the shadow_copy VFS module:</para> </formalpara> - <para> - <smbconfexample id="vfsshadow"> + <example id="vfsshadow"> <title>Share With shadow_copy VFS</title> + <smbconfblock> <smbconfsection name="[shadow_share]"/> <smbconfoption name="comment">Shadow Copy Enabled Share</smbconfoption> <smbconfoption name="path">/data/shadow_share</smbconfoption> <smbconfoption name="vfs objects">shadow_copy</smbconfoption> <smbconfoption name="writeable">yes</smbconfoption> <smbconfoption name="browseable">yes</smbconfoption> - </smbconfexample> - </para> + </smbconfblock> + </example> </listitem> <listitem> <formalpara> diff --git a/docs/Samba3-HOWTO/TOSHARG-Winbind.xml b/docs/Samba3-HOWTO/TOSHARG-Winbind.xml index 6cec77528d..9429d51a81 100644 --- a/docs/Samba3-HOWTO/TOSHARG-Winbind.xml +++ b/docs/Samba3-HOWTO/TOSHARG-Winbind.xml @@ -619,9 +619,9 @@ are described in more detail in the <citerefentry><refentrytitle>winbindd</refen linkend="winbindcfg">the next example</link>, was modified to include the necessary entries in the [global] section. </para> -<para> -<smbconfexample id="winbindcfg" fragment="1"> +<example id="winbindcfg" fragment="1"> <title>smb.conf for Winbind set-up</title> + <smbconfblock> <smbconfsection name="[global]"/> <smbconfcomment> separate domain and username with '\', like DOMAIN\username</smbconfcomment> <smbconfoption name="winbind separator">\</smbconfoption> @@ -635,7 +635,8 @@ linkend="winbindcfg">the next example</link>, was modified to include the necess <smbconfcomment> give winbind users a real shell (only needed if they have telnet access)</smbconfcomment> <smbconfoption name="template homedir">/home/winnt/%D/%U</smbconfoption> <smbconfoption name="template shell">/bin/bash</smbconfoption> -</smbconfexample></para> +</smbconfblock> +</example> </sect3> diff --git a/docs/Samba3-HOWTO/TOSHARG-WindowsClientConfig.xml b/docs/Samba3-HOWTO/TOSHARG-WindowsClientConfig.xml index 2d8b78536e..3c294406ac 100644 --- a/docs/Samba3-HOWTO/TOSHARG-WindowsClientConfig.xml +++ b/docs/Samba3-HOWTO/TOSHARG-WindowsClientConfig.xml @@ -224,7 +224,7 @@ that are in common use today. These are: Click the <guibutton>WINS</guibutton> tab to add manual WINS server entries. This step demonstrates an example system that uses manually configured WINS settings. When finished making changes, click on <guibutton>OK</guibutton> to commit the settings. - See <link linkend="w2kp005"></link>. + See <link linkend="w2kp005"/>. <figure id="w2kp005"><title>WINS Configuration.</title><imagefile>w2kp005</imagefile></figure> </para></step> @@ -255,16 +255,16 @@ that are in common use today. These are: <procedure> <step><para> In the box labeled <guimenuitem>The following network components are installed:</guimenuitem>, - click on <guimenu>Internet Protocol TCP/IP</guimenu>, now click on the <guibutton>Properties</guibutton> button. See <link linkend="WME001"></link>. + click on <guimenu>Internet Protocol TCP/IP</guimenu>, now click on the <guibutton>Properties</guibutton> button. See <link linkend="WME001"/>. <figure id="WME001"><title>The Windows Me Network Configuration Panel.</title><imagefile>WME001</imagefile></figure> </para></step> <step><para> Many network administrators will want to use DHCP to configure all client TCP/IP protocol stack settings. (For information on how to configure the ISC DHCP server - for Microsoft Windows client support see, <link linkend="DHCP"></link>. + for Microsoft Windows client support see, <link linkend="DHCP"/>. The default setting on Microsoft Windows Me workstations is for DHCP enabled operation, - i.e., <guimenu>Obtain IP address automatically</guimenu> is enabled. See <link linkend="WME002"></link>. + i.e., <guimenu>Obtain IP address automatically</guimenu> is enabled. See <link linkend="WME002"/>. <figure id="WME002"><title>IP Address.</title><imagefile>WME002</imagefile></figure> </para> @@ -286,7 +286,7 @@ that are in common use today. These are: </para></step> <step><para> - The following example uses manually configured WINS settings. See <link linkend="WME005"></link>. + The following example uses manually configured WINS settings. See <link linkend="WME005"/>. When finished making changes, click on <guibutton>OK</guibutton> to commit the settings. <figure id="WME005"><title>DNS Configuration.</title><imagefile>WME005</imagefile></figure> </para> diff --git a/docs/Samba3-HOWTO/TOSHARG-locking.xml b/docs/Samba3-HOWTO/TOSHARG-locking.xml index 2aa6b622a2..cb228658e7 100644 --- a/docs/Samba3-HOWTO/TOSHARG-locking.xml +++ b/docs/Samba3-HOWTO/TOSHARG-locking.xml @@ -666,16 +666,16 @@ enabled on a per-share basis, or globally for the entire server, in the &smb.conf; file as shown in <link linkend="far1"/>. </para> -<para> -<smbconfexample id="far1"> +<example id="far1"> <title>Share with some files oplocked</title> +<smbconfblock> <smbconfsection name="[global]"/> <smbconfoption name="veto oplock files">/filename.htm/*.txt/</smbconfoption> <smbconfsection name="[share_name]"/> <smbconfoption name="veto oplock files">/*.exe/filename.ext/</smbconfoption> -</smbconfexample> -</para> +</smbconfblock> +</example> <para> <smbconfoption name="oplock break wait time"/> is an &smb.conf; parameter @@ -699,16 +699,16 @@ Oplock break Contention Limit can be enable on a per-share basis, or globally fo the entire server, in the &smb.conf; file as shown in <link linkend="far3"/>. </para> -<para> -<smbconfexample id="far3"> +<example id="far3"> <title>Configuration with oplock break contention limit</title> + <smbconfblock> <smbconfsection name="[global]"/> <smbconfoption name="oplock break contention limit"> 2 (default)</smbconfoption> <smbconfsection name="[share_name]"/> <smbconfoption name="oplock break contention limit"> 2 (default)</smbconfoption> -</smbconfexample> -</para> +</smbconfblock> +</example> </sect3> </sect2> diff --git a/docs/Samba3-HOWTO/TOSHARG-msdfs.xml b/docs/Samba3-HOWTO/TOSHARG-msdfs.xml index 126edd0eb6..f5d066e681 100644 --- a/docs/Samba3-HOWTO/TOSHARG-msdfs.xml +++ b/docs/Samba3-HOWTO/TOSHARG-msdfs.xml @@ -61,9 +61,9 @@ </screen> </para> -<para> -<smbconfexample id="dfscfg"> +<example id="dfscfg"> <title>smb.conf with DFS configured</title> +<smbconfblock> <smbconfsection name="[global]"/> <smbconfoption name="netbios name">&example.server.samba;</smbconfoption> <smbconfoption name="host msdfs ">yes</smbconfoption> @@ -71,8 +71,8 @@ <smbconfsection name="[dfs]"/> <smbconfoption name="path">/export/dfsroot</smbconfoption> <smbconfoption name="msdfs root">yes</smbconfoption> -</smbconfexample> -</para> +</smbconfblock> +</example> <para>You should set up the permissions and ownership of the directory acting as the DFS root so that only designated |