svn commit: samba-docs r831 - in trunk/manpages-3: .
jht at samba.org
jht at samba.org
Mon Oct 17 17:49:56 GMT 2005
Author: jht
Date: 2005-10-17 17:49:56 +0000 (Mon, 17 Oct 2005)
New Revision: 831
WebSVN: http://websvn.samba.org/cgi-bin/viewcvs.cgi?view=rev&root=samba-docs&rev=831
Log:
Fixing bad XML to ascii code conversions by replacing smbconfblocks with programlisting tags. - Bug 2032.
Modified:
trunk/manpages-3/smb.conf.5.xml
Changeset:
Modified: trunk/manpages-3/smb.conf.5.xml
===================================================================
--- trunk/manpages-3/smb.conf.5.xml 2005-10-17 17:32:30 UTC (rev 830)
+++ trunk/manpages-3/smb.conf.5.xml 2005-10-17 17:49:56 UTC (rev 831)
@@ -111,27 +111,25 @@
<para>
The following sample section defines a file space share. The user has write access to the path <filename
moreinfo="none">/home/bar</filename>. The share is accessed via the share name <literal>foo</literal>:
- </para>
-
-<smbconfblock>
+<programlisting>
<smbconfsection name="[foo]"/>
<smbconfoption name="path">/home/bar</smbconfoption>
<smbconfoption name="read only">no</smbconfoption>
-</smbconfblock>
+</programlisting>
+ </para>
<para>
The following sample section defines a printable share. The share is read-only, but printable. That is,
the only write access permitted is via calls to open, write to and close a spool file. The <emphasis>guest
ok</emphasis> parameter means access will be permitted as the default guest user (specified elsewhere):
- </para>
-
-<smbconfblock>
+<programlisting>
<smbconfsection name="[aprinter]"/>
<smbconfoption name="path">/usr/spool/public</smbconfoption>
<smbconfoption name="read only">yes</smbconfoption>
<smbconfoption name="printable">yes</smbconfoption>
<smbconfoption name="guest ok">yes</smbconfoption>
-</smbconfblock>
+</programlisting>
+ </para>
</refsect1>
@@ -199,12 +197,11 @@
<para>
The [homes] section can specify all the parameters a normal service section can specify, though some make more sense
than others. The following is a typical and suitable [homes] section:
+<programlisting>
+<smbconfsection name="[homes]"/>
+<smbconfoption name="read only">no</smbconfoption>
+</programlisting>
</para>
-
- <smbconfblock>
- <smbconfsection name="[homes]"/>
- <smbconfoption name="read only">no</smbconfoption>
- </smbconfblock>
<para>
An important point is that if guest access is specified in the [homes] section, all home directories will be
@@ -260,15 +257,14 @@
<para>
Typically the path specified is that of a world-writeable spool directory with the sticky bit set on
it. A typical [printers] entry looks like this:
+<programlisting>
+<smbconfsection name="[printers]"/>
+<smbconfoption name="path">/usr/spool/public</smbconfoption>
+<smbconfoption name="guest ok">yes</smbconfoption>
+<smbconfoption name="printable">yes</smbconfoption>
+</programlisting>
</para>
- <smbconfblock>
- <smbconfsection name="[printers]"/>
- <smbconfoption name="path">/usr/spool/public</smbconfoption>
- <smbconfoption name="guest ok">yes</smbconfoption>
- <smbconfoption name="printable">yes</smbconfoption>
- </smbconfblock>
-
<para>
All aliases given for a printer in the printcap file are legitimate printer names as far as the server is concerned.
If your printing subsystem doesn't work like that, you will have to set up a pseudo-printcap. This is a file
More information about the samba-cvs
mailing list