1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
|
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbmount</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbmount.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbmount — mount an smbfs filesystem</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>smbmount</tt> {service} {mount-point} [-o options]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p><b>smbmount</b> mounts a Linux SMB filesystem. It
is usually invoked as <b>mount.smbfs</b> by
the <a href="mount.8.html">mount(8)</a> command when using the
"-t smbfs" option. This command only works in Linux, and the kernel must
support the smbfs filesystem. </p><p>Options to <b>smbmount</b> 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.</p><p><b>smbmount</b> 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 <tt>log.smbmount</tt>. The <b>
smbmount</b> process may also be called mount.smbfs.</p><p><span class="emphasis"><em>NOTE:</em></span> <b>smbmount</b>
calls <a href="smbmnt.8.html">smbmnt(8)</a> to do the actual mount. You
must make sure that <b>smbmnt</b> is in the path so
that it can be found. </p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">username=<arg></span></dt><dd><p>specifies the username to connect as. If
this is not given, then the environment variable <tt>
USER</tt> is used. This option can also take the
form "user%password" or "user/workgroup" or
"user/workgroup%password" to allow the password and workgroup
to be specified as part of the username.</p></dd><dt><span class="term">password=<arg></span></dt><dd><p>specifies the SMB password. If this
option is not given then the environment variable
<tt>PASSWD</tt> is used. If it can find
no password <b>smbmount</b> will prompt
for a passeword, unless the guest option is
given. </p><p>
Note that passwords which contain the argument 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.
</p></dd><dt><span class="term">credentials=<filename></span></dt><dd><p>specifies a file that contains a username and/or password.
The format of the file is:
</p><pre class="programlisting">
username = <value>
password = <value>
</pre><p>This is preferred over having passwords in plaintext in a
shared file, such as <tt>/etc/fstab</tt>. Be sure to protect any
credentials file properly.
</p></dd><dt><span class="term">krb</span></dt><dd><p>Use kerberos (Active Directory). </p></dd><dt><span class="term">netbiosname=<arg></span></dt><dd><p>sets the source NetBIOS name. It defaults
to the local hostname. </p></dd><dt><span class="term">uid=<arg></span></dt><dd><p>sets the uid that will own all files on
the mounted filesystem.
It may be specified as either a username or a numeric uid.
</p></dd><dt><span class="term">gid=<arg></span></dt><dd><p>sets the gid that will own all files on
the mounted filesystem.
It may be specified as either a groupname or a numeric
gid. </p></dd><dt><span class="term">port=<arg></span></dt><dd><p>sets the remote SMB port number. The default
is 139. </p></dd><dt><span class="term">fmask=<arg></span></dt><dd><p>sets the file mask. This determines the
permissions that remote files have in the local filesystem.
The default is based on the current umask. </p></dd><dt><span class="term">dmask=<arg></span></dt><dd><p>Sets the directory mask. This determines the
permissions that remote directories have in the local filesystem.
The default is based on the current umask. </p></dd><dt><span class="term">debug=<arg></span></dt><dd><p>Sets the debug level. This is useful for
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.</p></dd><dt><span class="term">ip=<arg></span></dt><dd><p>Sets the destination host or IP address.
</p></dd><dt><span class="term">workgroup=<arg></span></dt><dd><p>Sets the workgroup on the destination </p></dd><dt><span class="term">sockopt=<arg></span></dt><dd><p>Sets the TCP socket options. See the <a href="smb.conf.5.html#SOCKETOPTIONS" target="_top"><a href="smb.conf.5.html">smb.conf(5)</a></a> <i><tt>socket options</tt></i> option.
</p></dd><dt><span class="term">scope=<arg></span></dt><dd><p>Sets the NetBIOS scope </p></dd><dt><span class="term">guest</span></dt><dd><p>Don't prompt for a password </p></dd><dt><span class="term">ro</span></dt><dd><p>mount read-only </p></dd><dt><span class="term">rw</span></dt><dd><p>mount read-write </p></dd><dt><span class="term">iocharset=<arg></span></dt><dd><p>
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)
</p></dd><dt><span class="term">codepage=<arg></span></dt><dd><p>
sets the codepage the server uses. See the iocharset
option. Example value cp850. (Note: only kernel 2.4.0
or later)
</p></dd><dt><span class="term">ttl=<arg></span></dt><dd><p>
sets how long a directory listing is cached in milliseconds
(also affects visibility of file size and date
changes). A higher value means that changes on the
server take longer to be noticed but it can give
better performance on large directories, especially
over long distances. Default is 1000ms but something
like 10000ms (10 seconds) is probably more reasonable
in many cases.
(Note: only kernel 2.4.2 or later)
</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>ENVIRONMENT VARIABLES</h2><p>The variable <tt>USER</tt> may contain the username of the
person using the client. This information is used only if the
protocol level is high enough to support session-level
passwords. The variable can be used to set both username and
password by using the format username%password.</p><p>The variable <tt>PASSWD</tt> may contain the password of the
person using the client. This information is used only if the
protocol level is high enough to support session-level
passwords.</p><p>The variable <tt>PASSWD_FILE</tt> may contain the pathname
of a file to read the password from. A single line of input is
read and used as the password.</p></div><div class="refsect1" lang="en"><h2>BUGS</h2><p>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.</p><p>The credentials file does not handle usernames or passwords with
leading space.</p><p>One smbfs bug is important enough to mention here, even if it
is a bit misplaced:</p><div class="itemizedlist"><ul type="disc"><li><p>Mounts sometimes stop working. This is usually
caused by smbmount terminating. Since smbfs needs smbmount 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.</p></li></ul></div><p>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)</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p>Documentation/filesystems/smbfs.txt in the linux kernel
source tree may contain additional options and information.</p><p>FreeBSD also has a smbfs, but it is not related to smbmount</p><p>For Solaris, HP-UX and others you may want to look at <a href="smbsh.1.html">smbsh(1)</a> or at other solutions, such as
Sharity or perhaps replacing the SMB server with a NFS server.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>Volker Lendecke, Andrew Tridgell, Michael H. Warfield
and others.</p><p>The current maintainer of smbfs and the userspace
tools <b>smbmount</b>, <b>smbumount</b>,
and <b>smbmnt</b> is <a href="mailto:urban@teststation.com" target="_top">Urban Widmark</a>.
The <a href="mailto:samba@samba.org" target="_top">SAMBA Mailing list</a>
is the preferred place to ask questions regarding these programs.
</p><p>The conversion of this manpage for Samba 2.2 was performed
by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0
was done by Alexander Bokovoy.</p></div></div></body></html>
|
