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
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
|
SSSSMMMMBBBBMMMMOOOOUUUUNNNNTTTT((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBMMMMOOOOUUUUNNNNTTTT((((8888))))
NNNNAAAAMMMMEEEE
smbmount - mount an smbfs filesystem
SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
ssssmmmmbbbbmmmmoooouuuunnnntttt sssseeeerrrrvvvviiiicccceeee mmmmoooouuuunnnntttt----ppppooooiiiinnnntttt [ ----oooo ooooppppttttiiiioooonnnnssss ]
DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
ssssmmmmbbbbmmmmoooouuuunnnntttt mounts a Linux SMB filesystem. It is usually
invoked as mmmmoooouuuunnnntttt....ssssmmmmbbbbffffssss by the mmmmoooouuuunnnntttt((((8888)))) command when using
the "-t smbfs" option. This command only works in Linux, and
the kernel must support the smbfs filesystem.
Options to ssssmmmmbbbbmmmmoooouuuunnnntttt 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.
ssssmmmmbbbbmmmmoooouuuunnnntttt 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
_l_o_g._s_m_b_m_o_u_n_t. The ssssmmmmbbbbmmmmoooouuuunnnntttt process may also be called
mount.smbfs.
NNNNOOOOTTTTEEEE:::: ssssmmmmbbbbmmmmoooouuuunnnntttt calls ssssmmmmbbbbmmmmnnnntttt((((8888)))) to do the actual mount. You
must make sure that ssssmmmmbbbbmmmmnnnntttt is in the path so that it can be
found.
OOOOPPPPTTTTIIIIOOOONNNNSSSS
uuuusssseeeerrrrnnnnaaaammmmeeee====<<<<aaaarrrrgggg>>>>
specifies the username to connect as. If this is not
given, then the environment variable UUUUSSSSEEEERRRR 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.
ppppaaaasssssssswwwwoooorrrrdddd====<<<<aaaarrrrgggg>>>>
specifies the SMB password. If this option is not given
then the environment variable PPPPAAAASSSSSSSSWWWWDDDD is used. If it can
find no password ssssmmmmbbbbmmmmoooouuuunnnntttt will prompt for a passeword,
unless the guest option is given.
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.
ccccrrrreeeeddddeeeennnnttttiiiiaaaallllssss====<<<<ffffiiiilllleeeennnnaaaammmmeeee>>>>
Page 1 (printed 1/7/103)
SSSSMMMMBBBBMMMMOOOOUUUUNNNNTTTT((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBMMMMOOOOUUUUNNNNTTTT((((8888))))
specifies a file that contains a username and/or
password. The format of the file is:
username = <value>
password = <value>
This is preferred over having passwords in plaintext in
a shared file, such as /_e_t_c/_f_s_t_a_b. Be sure to protect
any credentials file properly.
nnnneeeettttbbbbiiiioooossssnnnnaaaammmmeeee====<<<<aaaarrrrgggg>>>>
sets the source NetBIOS name. It defaults to the local
hostname.
uuuuiiiidddd====<<<<aaaarrrrgggg>>>>
sets the uid that will own all files on the mounted
filesystem. It may be specified as either a username
or a numeric uid.
ggggiiiidddd====<<<<aaaarrrrgggg>>>>
sets the gid that will own all files on the mounted
filesystem. It may be specified as either a groupname
or a numeric gid.
ppppoooorrrrtttt====<<<<aaaarrrrgggg>>>>
sets the remote SMB port number. The default is 139.
ffffmmmmaaaasssskkkk====<<<<aaaarrrrgggg>>>>
sets the file mask. This determines the permissions
that remote files have in the local filesystem. The
default is based on the current umask.
ddddmmmmaaaasssskkkk====<<<<aaaarrrrgggg>>>>
sets the directory mask. This determines the
permissions that remote directories have in the local
filesystem. The default is based on the current umask.
ddddeeeebbbbuuuugggg====<<<<aaaarrrrgggg>>>>
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.
iiiipppp====<<<<aaaarrrrgggg>>>>
sets the destination host or IP address.
wwwwoooorrrrkkkkggggrrrroooouuuupppp====<<<<aaaarrrrgggg>>>>
sets the workgroup on the destination
Page 2 (printed 1/7/103)
SSSSMMMMBBBBMMMMOOOOUUUUNNNNTTTT((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBMMMMOOOOUUUUNNNNTTTT((((8888))))
ssssoooocccckkkkoooopppptttt====<<<<aaaarrrrgggg>>>>
sets the TCP socket options. See the _s_m_b._c_o_n_f
_s_o_c_k_e_t _o_p_t_i_o_n_s option.
ssssccccooooppppeeee====<<<<aaaarrrrgggg>>>>
sets the NetBIOS scope
gggguuuueeeesssstttt
don't prompt for a password
rrrroooo mount read-only
rrrrwwww mount read-write
iiiioooocccchhhhaaaarrrrsssseeeetttt====<<<<aaaarrrrgggg>>>>
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)
ccccooooddddeeeeppppaaaaggggeeee====<<<<aaaarrrrgggg>>>>
sets the codepage the server uses. See the iocharset
option. Example value cp850. (Note: only kernel 2.4.0
or later)
ttttttttllll====<<<<aaaarrrrgggg>>>>
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)
EEEENNNNVVVVIIIIRRRROOOONNNNMMMMEEEENNNNTTTT VVVVAAAARRRRIIIIAAAABBBBLLLLEEEESSSS
The variable UUUUSSSSEEEERRRR 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.
The variable PPPPAAAASSSSSSSSWWWWDDDD 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.
The variable PPPPAAAASSSSSSSSWWWWDDDD____FFFFIIIILLLLEEEE may contain the pathname of a file
to read the password from. A single line of input is read
and used as the password.
BBBBUUUUGGGGSSSS
PPPPaaaaggggeeee 3333 ((((pppprrrriiiinnnntttteeeedddd 1111////7777////111100003333))))
SSSSMMMMBBBBMMMMOOOOUUUUNNNNTTTT((((8888)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBMMMMOOOOUUUUNNNNTTTT((((8888))))
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.
The credentials file does not handle usernames or passwords
with leading space.
One smbfs bug is important enough to mention here, even if
it is a bit misplaced:
o+ 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.
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)
SSSSEEEEEEEE AAAALLLLSSSSOOOO
Documentation/filesystems/smbfs.txt in the linux kernel
source tree may contain additional options and information.
FreeBSD also has a smbfs, but it is not related to smbmount
For Solaris, HP-UX and others you may want to look at
ssssmmmmbbbbsssshhhh((((1111)))) or at other solutions, such as sharity or perhaps
replacing the SMB server with a NFS server.
AAAAUUUUTTTTHHHHOOOORRRR
Volker Lendecke, Andrew Tridgell, Michael H. Warfield and
others.
The current maintainer of smbfs and the userspace tools
ssssmmmmbbbbmmmmoooouuuunnnntttt, ssssmmmmbbbbuuuummmmoooouuuunnnntttt, and ssssmmmmbbbbmmmmnnnntttt is Urban Widmark
<URL:mailto:urban@teststation.com>. The SAMBA Mailing list
<URL:mailto:samba@samba.org> is the preferred place to ask
questions regarding these programs.
The conversion of this manpage for Samba 2.2 was performed
by Gerald Carter
Page 4 (printed 1/7/103)
|
