summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorAlexander Bokovoy <ab@samba.org>2003-04-15 12:35:52 +0000
committerAlexander Bokovoy <ab@samba.org>2003-04-15 12:35:52 +0000
commit4bde67ef6011aecc023be5b0f56687da3ca7a875 (patch)
tree7bf68a3a25236eb90015c445340d984c45c64d32 /docs
parent4e3f7c85093466955a95836a76bdc8c6b4b30d8e (diff)
downloadsamba-4bde67ef6011aecc023be5b0f56687da3ca7a875.tar.gz
samba-4bde67ef6011aecc023be5b0f56687da3ca7a875.tar.bz2
samba-4bde67ef6011aecc023be5b0f56687da3ca7a875.zip
Fix smb.conf.5.xml and friends:
addressable IDs should be specified at section level, not in titles or it does not work with both HTML and PDF generation (for former one link is created but target does not). (This used to be commit 297ffdb21aeb816eb07ea650fac514c2747493cb)
Diffstat (limited to 'docs')
-rw-r--r--docs/docbook/smbdotconf/filename/vetofiles.xml3
-rw-r--r--docs/docbook/smbdotconf/printing/useclientdriver.xml3
-rw-r--r--docs/docbook/smbdotconf/smb.conf.5.xml20
3 files changed, 14 insertions, 12 deletions
diff --git a/docs/docbook/smbdotconf/filename/vetofiles.xml b/docs/docbook/smbdotconf/filename/vetofiles.xml
index 073645c611..567286580d 100644
--- a/docs/docbook/smbdotconf/filename/vetofiles.xml
+++ b/docs/docbook/smbdotconf/filename/vetofiles.xml
@@ -34,7 +34,8 @@
<para>Default: <emphasis>No files or directories are vetoed.
</emphasis></para>
-<para>Examples:<programlisting format="linespecific">
+ <para>Examples:
+<programlisting format="linespecific">
; Veto any files containing the word Security,
; any ending in .tmp, and any directory containing the
; word root.
diff --git a/docs/docbook/smbdotconf/printing/useclientdriver.xml b/docs/docbook/smbdotconf/printing/useclientdriver.xml
index bc4162333b..67c8cbf8d0 100644
--- a/docs/docbook/smbdotconf/printing/useclientdriver.xml
+++ b/docs/docbook/smbdotconf/printing/useclientdriver.xml
@@ -32,7 +32,8 @@
on a print share which has valid print driver installed on the Samba
server.</emphasis></para>
- <para>See also <link linkend="DISABLESPOOLSS">disable spoolss</link></para>
+ <para>See also <link linkend="DISABLESPOOLSS"><parameter
+ moreinfo="none">disable spoolss</parameter></link></para>
<para>Default: <command moreinfo="none">use client driver = no</command></para>
</listitem>
diff --git a/docs/docbook/smbdotconf/smb.conf.5.xml b/docs/docbook/smbdotconf/smb.conf.5.xml
index edb94573df..2a5d190f69 100644
--- a/docs/docbook/smbdotconf/smb.conf.5.xml
+++ b/docs/docbook/smbdotconf/smb.conf.5.xml
@@ -28,8 +28,8 @@
description of the file format and possible parameters held within
are here for reference purposes.</para> </refsect1>
-<refsect1>
- <title id="FILEFORMATSECT">FILE FORMAT</title>
+<refsect1 id="FILEFORMATSECT">
+ <title>FILE FORMAT</title>
<para>The file consists of sections and parameters. A section
begins with the name of the section in square brackets and continues
@@ -147,8 +147,8 @@
under PARAMETERS for more information.</para>
</refsect2>
- <refsect2>
- <title id="HOMESECT">The [homes] section</title>
+ <refsect2 id="HOMESECT">
+ <title>The [homes] section</title>
<para>If a section called homes is included in the
configuration file, services connecting clients to their
@@ -218,8 +218,8 @@
any auto home directories visible.</para>
</refsect2>
- <refsect2>
- <title id="PRINTERSSECT">The [printers] section</title>
+ <refsect2 id="PRINTERSSECT">
+ <title>The [printers] section</title>
<para>This section works like [homes],
but for printers.</para>
@@ -479,8 +479,8 @@ alias|alias|alias|alias...
with these substitutions and other smb.conf options.</para>
</refsect1>
-<refsect1>
- <title id="NAMEMANGLINGSECT">NAME MANGLING</title>
+<refsect1 id="NAMEMANGLINGSECT">
+ <title>NAME MANGLING</title>
<para>Samba supports &quot;name mangling&quot; so that DOS and
Windows clients can use files that don't conform to the 8.3 format.
@@ -542,8 +542,8 @@ alias|alias|alias|alias...
</refsect1>
-<refsect1>
- <title id="VALIDATIONSECT">NOTE ABOUT USERNAME/PASSWORD VALIDATION</title>
+<refsect1 id="VALIDATIONSECT">
+ <title>NOTE ABOUT USERNAME/PASSWORD VALIDATION</title>
<para>There are a number of ways in which a user can connect
to a service. The server uses the following steps in determining