summaryrefslogtreecommitdiff
path: root/docs/docbook/manpages/smbmount.8.sgml
diff options
context:
space:
mode:
Diffstat (limited to 'docs/docbook/manpages/smbmount.8.sgml')
-rw-r--r--docs/docbook/manpages/smbmount.8.sgml70
1 files changed, 48 insertions, 22 deletions
diff --git a/docs/docbook/manpages/smbmount.8.sgml b/docs/docbook/manpages/smbmount.8.sgml
index 391d7d6882..b4a77e51c9 100644
--- a/docs/docbook/manpages/smbmount.8.sgml
+++ b/docs/docbook/manpages/smbmount.8.sgml
@@ -24,22 +24,23 @@
<refsect1>
<title>DESCRIPTION</title>
- <para><command>smbmount</command> mounts a SMB filesystem. It
- is usually invoked as <command>mount.smb</command> from
+ <para><command>smbmount</command> mounts a Linux SMB filesystem. It
+ is usually invoked as <command>mount.smbfs</command> by
the <command>mount(8)</command> command when using the
- "-t smb" option. The kernel must support the smbfs filesystem. </para>
+ "-t smbfs" option. This command only works in Linux, and the kernel must
+ support the smbfs filesystem. </para>
- <para>Options to smbmount are specified as a comma separated
+ <para>Options to <command>smbmount</command> are specified as a comma-separated
list of key=value pairs. It is possible to send options other
than those listed here, assuming that smbfs supports them. If
you get mount failures, check your kernel log for errors on
unknown options.</para>
- <para>smbmount is a daemon. After mounting it keeps running until
+ <para><command>smbmount</command> is a daemon. After mounting it keeps running until
the mounted smbfs is umounted. It will log things that happen
when in daemon mode using the "machine name" smbmount, so
- typically this output will end up in log.smbmount. The
- smbmount process may also be called mount.smbfs.</para>
+ typically this output will end up in <filename>log.smbmount</filename>. The
+ <command>smbmount</command> process may also be called mount.smbfs.</para>
<para><emphasis>NOTE:</emphasis> <command>smbmount</command>
calls <command>smbmnt(8)</command> to do the actual mount. You
@@ -69,7 +70,16 @@
<envar>PASSWD</envar> is used. If it can find
no password <command>smbmount</command> will prompt
for a passeword, unless the guest option is
- given. </para></listitem>
+ given. </para>
+
+ <para>
+ Note that password which contain the arguement delimiter
+ character (i.e. a comma ',') will failed to be parsed correctly
+ on the command line. However, the same password defined
+ in the PASSWD environment variable or a credentials file (see
+ below) will be read correctly.
+ </para>
+ </listitem>
</varlistentry>
<varlistentry>
@@ -85,7 +95,7 @@
</para>
<para>This is preferred over having passwords in plaintext in a
- shared file, such as /etc/fstab. Be sure to protect any
+ shared file, such as <filename>/etc/fstab</filename>. Be sure to protect any
credentials file properly.
</para></listitem>
</varlistentry>
@@ -131,7 +141,7 @@
<varlistentry>
<term>dmask=&lt;arg&gt;</term>
- <listitem><para>sets the directory mask. This deterines the
+ <listitem><para>sets the directory mask. This determines the
permissions that remote directories have in the local filesystem.
The default is based on the current umask. </para></listitem>
</varlistentry>
@@ -140,7 +150,9 @@
<varlistentry>
<term>debug=&lt;arg&gt;</term>
<listitem><para>sets the debug level. This is useful for
- tracking down SMB connection problems. </para></listitem>
+ tracking down SMB connection problems. A suggested value to
+ start with is 4. If set too high there will be a lot of
+ output, possibly hiding the useful output.</para></listitem>
</varlistentry>
@@ -191,7 +203,7 @@
<varlistentry>
<term>iocharset=&lt;arg&gt;</term>
<listitem><para>
- sets the charset used by the linux side for codepage
+ sets the charset used by the Linux side for codepage
to charset translations (NLS). Argument should be the
name of a charset, like iso8859-1. (Note: only kernel
2.4.0 or later)
@@ -241,29 +253,36 @@
protocol level is high enough to support session-level
passwords.</para>
- <para>The variable <envar>PASSWD_FILE</envar> may contain the pathname of
- a file to read the password from. A single line of input is
- read and used as password.</para>
+ <para>The variable <envar>PASSWD_FILE</envar> may contain the pathname
+ of a file to read the password from. A single line of input is
+ read and used as the password.</para>
</refsect1>
<refsect1>
<title>BUGS</title>
- <para>Not many known smbmount bugs. But one smbfs bug is
- important enough to mention here anyway:</para>
+ <para>Passwords and other options containing , can not be handled.
+ For passwords an alternative way of passing them is in a credentials
+ file or in the PASSWD environment.</para>
+
+ <para>The credentials file does not handle usernames or passwords with
+ leading space.</para>
+
+ <para>One smbfs bug is important enough to mention here, even if it
+ is a bit misplaced:</para>
<itemizedlist>
<listitem><para>Mounts sometimes stop working. This is usually
caused by smbmount terminating. Since smbfs needs smbmount to
- reconnect when the server disconnects, the mount will go
- dead. A re-mount normally fixes this. At least 2 ways to
+ reconnect when the server disconnects, the mount will eventually go
+ dead. An umount/mount normally fixes this. At least 2 ways to
trigger this bug are known.</para></listitem>
</itemizedlist>
- <para>Note that the typical response to a bugreport is suggestion
+ <para>Note that the typical response to a bug report is suggestion
to try the latest version first. So please try doing that first,
and always include which versions you use of relevant software
when reporting bugs (minimum: samba, kernel, distribution)</para>
@@ -274,8 +293,15 @@
<refsect1>
<title>SEE ALSO</title>
- <para>Documentation/filesystems/smbfs.txt in the kernel source tree
- may contain additional options and information.</para>
+ <para>Documentation/filesystems/smbfs.txt in the linux kernel
+ source tree may contain additional options and information.</para>
+
+ <para>FreeBSD also has a smbfs, but it is not related to smbmount</para>
+
+ <para>For Solaris, HP-UX and others you may want to look at
+ <ulink url="smbsh.1.html"><command>smbsh(1)</command></ulink> or at other
+ solutions, such as sharity or perhaps replacing the SMB server with
+ a NFS server.</para>
</refsect1>