Changeset 599 for trunk/server/docs/htmldocs/manpages/smbclient.1.html
- Timestamp:
- Jul 6, 2011, 8:21:13 PM (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/server/docs/htmldocs/manpages/smbclient.1.html
r429 r599 1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbclient</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.7 4.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbclient.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbclient — ftp-like client to access SMB/CIFS resources2 on servers</p></div><div class="refsynopsisdiv" ><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">smbclient</code> [-b <buffer size>] [-d debuglevel] [-e] [-L <netbios name>] [-U username] [-I destinationIP] [-M <netbios name>] [-m maxprotocol] [-A authfile] [-N] [-C] [-g] [-i scope] [-O <socket options>] [-p port] [-R <name resolve order>] [-s <smb config file>] [-k] [-P] [-c <command>]</p></div><div class="cmdsynopsis"><p><code class="literal">smbclient</code> {servicename} [password] [-b <buffer size>] [-d debuglevel] [-e] [-D Directory] [-U username] [-W workgroup] [-M <netbios name>] [-m maxprotocol] [-A authfile] [-N] [-C] [-g] [-l log-basename] [-I destinationIP] [-E] [-c <command string>] [-i scope] [-O <socket options>] [-p port] [-R <name resolve order>] [-s <smb config file>] [-T<c|x>IXFqgbNan] [-k]</p></div></div><div class="refsect1" lang="en"><a name="id2483767"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">smbclient</code> is a client that can1 <html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbclient</title><link rel="stylesheet" href="../samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.75.2"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" title="smbclient"><a name="smbclient.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbclient — ftp-like client to access SMB/CIFS resources 2 on servers</p></div><div class="refsynopsisdiv" title="Synopsis"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="literal">smbclient</code> [-b <buffer size>] [-d debuglevel] [-e] [-L <netbios name>] [-U username] [-I destinationIP] [-M <netbios name>] [-m maxprotocol] [-A authfile] [-N] [-C] [-g] [-i scope] [-O <socket options>] [-p port] [-R <name resolve order>] [-s <smb config file>] [-k] [-P] [-c <command>]</p></div><div class="cmdsynopsis"><p><code class="literal">smbclient</code> {servicename} [password] [-b <buffer size>] [-d debuglevel] [-e] [-D Directory] [-U username] [-W workgroup] [-M <netbios name>] [-m maxprotocol] [-A authfile] [-N] [-C] [-g] [-l log-basename] [-I destinationIP] [-E] [-c <command string>] [-i scope] [-O <socket options>] [-p port] [-R <name resolve order>] [-s <smb config file>] [-T<c|x>IXFqgbNan] [-k]</p></div></div><div class="refsect1" title="DESCRIPTION"><a name="id265953"></a><h2>DESCRIPTION</h2><p>This tool is part of the <a class="citerefentry" href="samba.7.html"><span class="citerefentry"><span class="refentrytitle">samba</span>(7)</span></a> suite.</p><p><code class="literal">smbclient</code> is a client that can 3 3 'talk' to an SMB/CIFS server. It offers an interface 4 4 similar to that of the ftp program (see <a class="citerefentry" href="ftp.1.html"><span class="citerefentry"><span class="refentrytitle">ftp</span>(1)</span></a>). … … 6 6 to the local machine, putting files from the local machine to 7 7 the server, retrieving directory information from the server 8 and so on. </p></div><div class="refsect1" lang="en"><a name="id2481476"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">servicename</span></dt><dd><p>servicename is the name of the service8 and so on. </p></div><div class="refsect1" title="OPTIONS"><a name="id307046"></a><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">servicename</span></dt><dd><p>servicename is the name of the service 9 9 you want to use on the server. A service name takes the form 10 10 <code class="filename">//server/service</code> where <em class="parameter"><code>server … … 41 41 host names to IP addresses. The option takes a space-separated 42 42 string of different name resolution options.</p><p>The options are :"lmhosts", "host", "wins" and "bcast". They 43 cause names to be resolved as follows:</p><div class="itemizedlist"><ul type="disc"><li><p><code class="constant">lmhosts</code>: Lookup an IP43 cause names to be resolved as follows:</p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><code class="constant">lmhosts</code>: Lookup an IP 44 44 address in the Samba lmhosts file. If the line in lmhosts has 45 45 no name type attached to the NetBIOS name (see 46 46 the <a class="citerefentry" href="lmhosts.5.html"><span class="citerefentry"><span class="refentrytitle">lmhosts</span>(5)</span></a> for details) then 47 any name type matches for lookup.</p></li><li ><p><code class="constant">host</code>: Do a standard host47 any name type matches for lookup.</p></li><li class="listitem"><p><code class="constant">host</code>: Do a standard host 48 48 name to IP address resolution, using the system <code class="filename">/etc/hosts 49 49 </code>, NIS, or DNS lookups. This method of name resolution … … 52 52 file). Note that this method is only used if the NetBIOS name 53 53 type being queried is the 0x20 (server) name type, otherwise 54 it is ignored.</p></li><li ><p><code class="constant">wins</code>: Query a name with54 it is ignored.</p></li><li class="listitem"><p><code class="constant">wins</code>: Query a name with 55 55 the IP address listed in the <em class="parameter"><code>wins server</code></em> 56 56 parameter. If no WINS server has 57 been specified this method will be ignored.</p></li><li ><p><code class="constant">bcast</code>: Do a broadcast on57 been specified this method will be ignored.</p></li><li class="listitem"><p><code class="constant">bcast</code>: Do a broadcast on 58 58 each of the known local interfaces listed in the 59 59 <em class="parameter"><code>interfaces</code></em> … … 199 199 </code> compatible backups of all the files on an SMB/CIFS 200 200 share. The secondary tar flags that can be given to this option 201 are : </p><div class="itemizedlist"><ul type="disc"><li><p><em class="parameter"><code>c</code></em> - Create a tar file on UNIX.201 are : </p><div class="itemizedlist"><ul class="itemizedlist" type="disc"><li class="listitem"><p><em class="parameter"><code>c</code></em> - Create a tar file on UNIX. 202 202 Must be followed by the name of a tar file, tape device 203 203 or "-" for standard output. If using standard output you must 204 204 turn the log level to its lowest value -d0 to avoid corrupting 205 205 your tar file. This flag is mutually exclusive with the 206 <em class="parameter"><code>x</code></em> flag. </p></li><li ><p><em class="parameter"><code>x</code></em> - Extract (restore) a local206 <em class="parameter"><code>x</code></em> flag. </p></li><li class="listitem"><p><em class="parameter"><code>x</code></em> - Extract (restore) a local 207 207 tar file back to a share. Unless the -D option is given, the tar 208 208 files will be restored from the top level of the share. Must be … … 211 211 Restored files have their creation times (mtime) set to the 212 212 date saved in the tar file. Directories currently do not get 213 their creation dates restored properly. </p></li><li ><p><em class="parameter"><code>I</code></em> - Include files and directories.213 their creation dates restored properly. </p></li><li class="listitem"><p><em class="parameter"><code>I</code></em> - Include files and directories. 214 214 Is the default behavior when filenames are specified above. Causes 215 215 files to be included in an extract or create (and therefore 216 216 everything else to be excluded). See example below. Filename globbing 217 works in one of two ways. See <em class="parameter"><code>r</code></em> below. </p></li><li ><p><em class="parameter"><code>X</code></em> - Exclude files and directories.217 works in one of two ways. See <em class="parameter"><code>r</code></em> below. </p></li><li class="listitem"><p><em class="parameter"><code>X</code></em> - Exclude files and directories. 218 218 Causes files to be excluded from an extract or create. See 219 219 example below. Filename globbing works in one of two ways now. 220 See <em class="parameter"><code>r</code></em> below. </p></li><li ><p><em class="parameter"><code>F</code></em> - File containing a list of files and directories.220 See <em class="parameter"><code>r</code></em> below. </p></li><li class="listitem"><p><em class="parameter"><code>F</code></em> - File containing a list of files and directories. 221 221 The <em class="parameter"><code>F</code></em> causes the name following the tarfile to 222 222 create to be read as a filename that contains a list of files and directories to … … 224 224 See example below. Filename globbing works in one of two ways. 225 225 See <em class="parameter"><code>r</code></em> below. 226 </p></li><li ><p><em class="parameter"><code>b</code></em> - Blocksize. Must be followed226 </p></li><li class="listitem"><p><em class="parameter"><code>b</code></em> - Blocksize. Must be followed 227 227 by a valid (greater than zero) blocksize. Causes tar file to be 228 228 written out in blocksize*TBLOCK (usually 512 byte) blocks. 229 </p></li><li ><p><em class="parameter"><code>g</code></em> - Incremental. Only back up229 </p></li><li class="listitem"><p><em class="parameter"><code>g</code></em> - Incremental. Only back up 230 230 files that have the archive bit set. Useful only with the 231 <em class="parameter"><code>c</code></em> flag. </p></li><li ><p><em class="parameter"><code>q</code></em> - Quiet. Keeps tar from printing231 <em class="parameter"><code>c</code></em> flag. </p></li><li class="listitem"><p><em class="parameter"><code>q</code></em> - Quiet. Keeps tar from printing 232 232 diagnostics as it works. This is the same as tarmode quiet. 233 </p></li><li ><p><em class="parameter"><code>r</code></em> - Regular expression include233 </p></li><li class="listitem"><p><em class="parameter"><code>r</code></em> - Regular expression include 234 234 or exclude. Uses regular expression matching for 235 235 excluding or excluding files if compiled with HAVE_REGEX_H. 236 236 However this mode can be very slow. If not compiled with 237 237 HAVE_REGEX_H, does a limited wildcard match on '*' and '?'. 238 </p></li><li ><p><em class="parameter"><code>N</code></em> - Newer than. Must be followed238 </p></li><li class="listitem"><p><em class="parameter"><code>N</code></em> - Newer than. Must be followed 239 239 by the name of a file whose date is compared against files found 240 240 on the share during a create. Only files newer than the file 241 241 specified are backed up to the tar file. Useful only with the 242 <em class="parameter"><code>c</code></em> flag. </p></li><li ><p><em class="parameter"><code>a</code></em> - Set archive bit. Causes the242 <em class="parameter"><code>c</code></em> flag. </p></li><li class="listitem"><p><em class="parameter"><code>a</code></em> - Set archive bit. Causes the 243 243 archive bit to be reset when a file is backed up. Useful with the 244 244 <em class="parameter"><code>g</code></em> and <em class="parameter"><code>c</code></em> flags. … … 265 265 commands to be executed instead of prompting from stdin. <em class="parameter"><code> 266 266 -N</code></em> is implied by <em class="parameter"><code>-c</code></em>.</p><p>This is particularly useful in scripts and for printing stdin 267 to the server, e.g. <code class="literal">-c 'print -'</code>. </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2533296"></a><h2>OPERATIONS</h2><p>Once the client is running, the user is presented with267 to the server, e.g. <code class="literal">-c 'print -'</code>. </p></dd></dl></div></div><div class="refsect1" title="OPERATIONS"><a name="id308240"></a><h2>OPERATIONS</h2><p>Once the client is running, the user is presented with 268 268 a prompt : </p><p><code class="prompt">smb:\> </code></p><p>The backslash ("\\") indicates the current working directory 269 269 on the server, and will change if the current working directory … … 466 466 the given arbitrary number. Without an argument prints out the current 467 467 vuid being used. Used for internal Samba testing purposes. 468 </p></dd></dl></div></div><div class="refsect1" lang="en"><a name="id2534407"></a><h2>NOTES</h2><p>Some servers are fussy about the case of supplied usernames,468 </p></dd></dl></div></div><div class="refsect1" title="NOTES"><a name="id309210"></a><h2>NOTES</h2><p>Some servers are fussy about the case of supplied usernames, 469 469 passwords, share names (AKA service names) and machine names. 470 470 If you fail to connect try giving all parameters in uppercase. … … 473 473 on a valid NetBIOS name being used, so you need to supply a valid 474 474 name that would be known to the server.</p><p>smbclient supports long file names where the server 475 supports the LANMAN2 protocol or above. </p></div><div class="refsect1" lang="en"><a name="id2534432"></a><h2>ENVIRONMENT VARIABLES</h2><p>The variable <code class="envar">USER</code> may contain the475 supports the LANMAN2 protocol or above. </p></div><div class="refsect1" title="ENVIRONMENT VARIABLES"><a name="id309231"></a><h2>ENVIRONMENT VARIABLES</h2><p>The variable <code class="envar">USER</code> may contain the 476 476 username of the person using the client. This information is 477 477 used only if the protocol level is high enough to support … … 483 483 to instead of connecting to a server. This functionality is primarily 484 484 intended as a development aid, and works best when using a LMHOSTS 485 file</p></div><div class="refsect1" lang="en"><a name="id2534468"></a><h2>INSTALLATION</h2><p>The location of the client program is a matter for485 file</p></div><div class="refsect1" title="INSTALLATION"><a name="id309262"></a><h2>INSTALLATION</h2><p>The location of the client program is a matter for 486 486 individual system administrators. The following are thus 487 487 suggestions only. </p><p>It is recommended that the smbclient software be installed … … 494 494 running SMB/CIFS server. It is possible to run <a class="citerefentry" href="smbd.8.html"><span class="citerefentry"><span class="refentrytitle">smbd</span>(8)</span></a> as an ordinary user - running that server as a daemon 495 495 on a user-accessible port (typically any port number over 1024) 496 would provide a suitable test server. </p></div><div class="refsect1" lang="en"><a name="id2534520"></a><h2>DIAGNOSTICS</h2><p>Most diagnostics issued by the client are logged in a496 would provide a suitable test server. </p></div><div class="refsect1" title="DIAGNOSTICS"><a name="id309309"></a><h2>DIAGNOSTICS</h2><p>Most diagnostics issued by the client are logged in a 497 497 specified log file. The log file name is specified at compile time, 498 498 but may be overridden on the command line. </p><p>The number and nature of diagnostics available depends 499 499 on the debug level used by the client. If you have problems, 500 set the debug level to 3 and peruse the log files. </p></div><div class="refsect1" lang="en"><a name="id2534539"></a><h2>VERSION</h2><p>This man page is correct for version 3.2 of the Samba suite.</p></div><div class="refsect1" lang="en"><a name="id2534550"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities500 set the debug level to 3 and peruse the log files. </p></div><div class="refsect1" title="VERSION"><a name="id309325"></a><h2>VERSION</h2><p>This man page is correct for version 3.2 of the Samba suite.</p></div><div class="refsect1" title="AUTHOR"><a name="id309335"></a><h2>AUTHOR</h2><p>The original Samba software and related utilities 501 501 were created by Andrew Tridgell. Samba is now developed 502 502 by the Samba Team as an Open Source project similar
Note:
See TracChangeset
for help on using the changeset viewer.
