summaryrefslogtreecommitdiff
path: root/packaging/Caldera/OpenServer/man/cat.1/smbclient.1
diff options
context:
space:
mode:
Diffstat (limited to 'packaging/Caldera/OpenServer/man/cat.1/smbclient.1')
-rw-r--r--packaging/Caldera/OpenServer/man/cat.1/smbclient.11056
1 files changed, 1056 insertions, 0 deletions
diff --git a/packaging/Caldera/OpenServer/man/cat.1/smbclient.1 b/packaging/Caldera/OpenServer/man/cat.1/smbclient.1
new file mode 100644
index 00000000000..b985a9f19f4
--- /dev/null
+++ b/packaging/Caldera/OpenServer/man/cat.1/smbclient.1
@@ -0,0 +1,1056 @@
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ NNNNAAAAMMMMEEEE
+ smbclient - ftp-like client to access SMB/CIFS resources on
+ servers
+
+ SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
+ ssssmmmmbbbbcccclllliiiieeeennnntttt sssseeeerrrrvvvviiiicccceeeennnnaaaammmmeeee [ ppppaaaasssssssswwwwoooorrrrdddd ] [ ----bbbb <<<<bbbbuuuuffffffffeeeerrrr ssssiiiizzzzeeee>>>> ] [
+ ----dddd ddddeeeebbbbuuuugggglllleeeevvvveeeellll ] [ ----DDDD DDDDiiiirrrreeeeccccttttoooorrrryyyy ] [ ----UUUU uuuusssseeeerrrrnnnnaaaammmmeeee ] [ ----WWWW
+ wwwwoooorrrrkkkkggggrrrroooouuuupppp ] [ ----MMMM <<<<nnnneeeettttbbbbiiiioooossss nnnnaaaammmmeeee>>>> ] [ ----mmmm mmmmaaaaxxxxpppprrrroooottttooooccccoooollll ] [ ----AAAA
+ aaaauuuutttthhhhffffiiiilllleeee ] [ ----NNNN ] [ ----llll llllooooggggffffiiiilllleeee ] [ ----LLLL <<<<nnnneeeettttbbbbiiiioooossss nnnnaaaammmmeeee>>>> ] [
+ ----IIII ddddeeeessssttttiiiinnnnaaaattttiiiioooonnnnIIIIPPPP ] [ ----EEEE <<<<tttteeeerrrrmmmmiiiinnnnaaaallll ccccooooddddeeee>>>> ] [ ----cccc <<<<ccccoooommmmmmmmaaaannnndddd
+ ssssttttrrrriiiinnnngggg>>>> ] [ ----iiii ssssccccooooppppeeee ] [ ----OOOO <<<<ssssoooocccckkkkeeeetttt ooooppppttttiiiioooonnnnssss>>>> ] [ ----pppp ppppoooorrrrtttt
+ ] [ ----RRRR <<<<nnnnaaaammmmeeee rrrreeeessssoooollllvvvveeee oooorrrrddddeeeerrrr>>>> ] [ ----ssss <<<<ssssmmmmbbbb ccccoooonnnnffffiiiigggg ffffiiiilllleeee>>>> ] [
+ ----TTTT<<<<cccc||||xxxx>>>>IIIIXXXXFFFFqqqqggggbbbbNNNNaaaannnn ]
+
+ DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
+ This tool is part of the Samba suite.
+
+ ssssmmmmbbbbcccclllliiiieeeennnntttt is a client that can 'talk' to an SMB/CIFS server.
+ It offers an interface similar to that of the ftp program
+ (see ffffttttpppp((((1111))))). Operations include things like getting files
+ from the server to the local machine, putting files from the
+ local machine to the server, retrieving directory
+ information from the server and so on.
+
+ OOOOPPPPTTTTIIIIOOOONNNNSSSS
+ sssseeeerrrrvvvviiiicccceeeennnnaaaammmmeeee
+ servicename is the name of the service you want to use
+ on the server. A service name takes the form
+ //_s_e_r_v_e_r/_s_e_r_v_i_c_e where _s_e_r_v_e_r is the NetBIOS name of
+ the SMB/CIFS server offering the desired service and
+ _s_e_r_v_i_c_e is the name of the service offered. Thus to
+ connect to the service "printer" on the SMB/CIFS server
+ "smbserver", you would use the servicename
+ //_s_m_b_s_e_r_v_e_r/_p_r_i_n_t_e_r
+
+ Note that the server name required is NOT necessarily
+ the IP (DNS) host name of the server ! The name
+ required is a NetBIOS server name, which may or may not
+ be the same as the IP hostname of the machine running
+ the server.
+
+ The server name is looked up according to either the -_R
+ parameter to ssssmmmmbbbbcccclllliiiieeeennnntttt or using the name resolve order
+ parameter in the _s_m_b._c_o_n_f file, allowing an
+ administrator to change the order and methods by which
+ server names are looked up.
+
+ ppppaaaasssssssswwwwoooorrrrdddd
+ The password required to access the specified service
+ on the specified server. If this parameter is supplied,
+ the -_N option (suppress password prompt) is assumed.
+
+
+
+
+ Page 1 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ There is no default password. If no password is
+ supplied on the command line (either by using this
+ parameter or adding a password to the -_U option (see
+ below)) and the -_N option is not specified, the client
+ will prompt for a password, even if the desired service
+ does not require one. (If no password is required,
+ simply press ENTER to provide a null password.)
+
+ Note: Some servers (including OS/2 and Windows for
+ Workgroups) insist on an uppercase password. Lowercase
+ or mixed case passwords may be rejected by these
+ servers.
+
+ Be cautious about including passwords in scripts.
+
+ ----ssss ssssmmmmbbbb....ccccoooonnnnffff
+ Specifies the location of the all important _s_m_b._c_o_n_f
+ file.
+
+ ----OOOO ssssoooocccckkkkeeeetttt ooooppppttttiiiioooonnnnssss
+ TCP socket options to set on the client socket. See the
+ socket options parameter in the _s_m_b._c_o_n_f (_5) manpage
+ for the list of valid options.
+
+ ----RRRR <<<<nnnnaaaammmmeeee rrrreeeessssoooollllvvvveeee oooorrrrddddeeeerrrr>>>>
+ This option is used by the programs in the Samba suite
+ to determine what naming services and in what order to
+ resolve host names to IP addresses. The option takes a
+ space-separated string of different name resolution
+ options.
+
+ The options are :"lmhosts", "host", "wins" and "bcast".
+ They cause names to be resolved as follows :
+
+ o+ lmhosts : Lookup an IP address in the Samba lmhosts
+ file. If the line in lmhosts has no name type
+ attached to the NetBIOS name (see the lmhosts(5) for
+ details) then any name type matches for lookup.
+
+ o+ host : Do a standard host name to IP address
+ resolution, using the system /_e_t_c/_h_o_s_t_s , NIS, or DNS
+ lookups. This method of name resolution is operating
+ system dependent, for instance on IRIX or Solaris
+ this may be controlled by the /_e_t_c/_n_s_s_w_i_t_c_h._c_o_n_f
+ file). Note that this method is only used if the
+ NetBIOS name type being queried is the 0x20 (server)
+ name type, otherwise it is ignored.
+
+ o+ wins : Query a name with the IP address listed in the
+ _w_i_n_s _s_e_r_v_e_r parameter. If no WINS server has been
+ specified this method will be ignored.
+
+
+
+
+ Page 2 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ o+ bcast : Do a broadcast on each of the known local
+ interfaces listed in the _i_n_t_e_r_f_a_c_e_s parameter. This
+ is the least reliable of the name resolution methods
+ as it depends on the target host being on a locally
+ connected subnet.
+
+ If this parameter is not set then the name resolve order
+ defined in the _s_m_b._c_o_n_f file parameter (name resolve order)
+ will be used.
+
+ The default order is lmhosts, host, wins, bcast and without
+ this parameter or any entry in the _n_a_m_e _r_e_s_o_l_v_e _o_r_d_e_r
+ parameter of the _s_m_b._c_o_n_f file the name resolution methods
+ will be attempted in this order.
+
+ ----MMMM NNNNeeeettttBBBBIIIIOOOOSSSS nnnnaaaammmmeeee
+ This options allows you to send messages, using the
+ "WinPopup" protocol, to another computer. Once a
+ connection is established you then type your message,
+ pressing ^D (control-D) to end.
+
+ If the receiving computer is running WinPopup the user
+ will receive the message and probably a beep. If they
+ are not running WinPopup the message will be lost, and
+ no error message will occur.
+
+ The message is also automatically truncated if the
+ message is over 1600 bytes, as this is the limit of the
+ protocol.
+
+ One useful trick is to cat the message through
+ ssssmmmmbbbbcccclllliiiieeeennnntttt. For example: ccccaaaatttt mmmmyyyymmmmeeeessssssssaaaaggggeeee....ttttxxxxtttt |||| ssssmmmmbbbbcccclllliiiieeeennnntttt
+ ----MMMM FFFFRRRREEEEDDDD will send the message in the file
+ _m_y_m_e_s_s_a_g_e._t_x_t to the machine FRED.
+
+ You may also find the -_U and -_I options useful, as they
+ allow you to control the FROM and TO parts of the
+ message.
+
+ See the message command parameter in the _s_m_b._c_o_n_f(_5)
+ for a description of how to handle incoming WinPopup
+ messages in Samba.
+
+ NNNNooootttteeee: Copy WinPopup into the startup group on your WfWg
+ PCs if you want them to always be able to receive
+ messages.
+
+ ----iiii ssssccccooooppppeeee
+ This specifies a NetBIOS scope that smbclient will use
+ to communicate with when generating NetBIOS names. For
+ details on the use of NetBIOS scopes, see _r_f_c_1_0_0_1._t_x_t
+ and _r_f_c_1_0_0_2._t_x_t. NetBIOS scopes are vvvveeeerrrryyyy rarely used,
+
+
+
+ Page 3 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ only set this parameter if you are the system
+ administrator in charge of all the NetBIOS systems you
+ communicate with.
+
+ ----NNNN If specified, this parameter suppresses the normal
+ password prompt from the client to the user. This is
+ useful when accessing a service that does not require a
+ password.
+
+ Unless a password is specified on the command line or
+ this parameter is specified, the client will request a
+ password.
+
+ ----nnnn NNNNeeeettttBBBBIIIIOOOOSSSS nnnnaaaammmmeeee
+ By default, the client will use the local machine's
+ hostname (in uppercase) as its NetBIOS name. This
+ parameter allows you to override the host name and use
+ whatever NetBIOS name you wish.
+
+ ----dddd ddddeeeebbbbuuuugggglllleeeevvvveeeellll
+ _d_e_b_u_g_l_e_v_e_l is an integer from 0 to 10, or the letter
+ 'A'.
+
+ The default value if this parameter is not specified is
+ zero.
+
+ The higher this value, the more detail will be logged
+ to the log files about the activities of the client. At
+ level 0, only critical errors and serious warnings will
+ be logged. Level 1 is a reasonable level for day to day
+ running - it generates a small amount of information
+ about operations carried out.
+
+ Levels above 1 will generate considerable amounts of
+ log data, and should only be used when investigating a
+ problem. Levels above 3 are designed for use only by
+ developers and generate HUGE amounts of log data, most
+ of which is extremely cryptic. If _d_e_b_u_g_l_e_v_e_l is set to
+ the letter 'A', then aaaallllllll debug messages will be
+ printed. This setting is for developers only (and
+ people who rrrreeeeaaaallllllllyyyy want to know how the code works
+ internally).
+
+ Note that specifying this parameter here will override
+ the log level parameter in the _s_m_b._c_o_n_f (_5) file.
+
+ ----pppp ppppoooorrrrtttt
+ This number is the TCP port number that will be used
+ when making connections to the server. The standard
+ (well-known) TCP port number for an SMB/CIFS server is
+ 139, which is the default.
+
+
+
+
+ Page 4 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ ----llll llllooooggggffffiiiilllleeeennnnaaaammmmeeee
+ If specified, _l_o_g_f_i_l_e_n_a_m_e specifies a base filename
+ into which operational data from the running client
+ will be logged.
+
+ The default base name is specified at compile time.
+
+ The base name is used to generate actual log file
+ names. For example, if the name specified was "log",
+ the debug file would be _l_o_g._c_l_i_e_n_t.
+
+ The log file generated is never removed by the client.
+
+ ----hhhh Print the usage message for the client.
+
+ ----IIII IIIIPPPP----aaaaddddddddrrrreeeessssssss
+ _I_P _a_d_d_r_e_s_s is the address of the server to connect to.
+ It should be specified in standard "a.b.c.d" notation.
+
+ Normally the client would attempt to locate a named
+ SMB/CIFS server by looking it up via the NetBIOS name
+ resolution mechanism described above in the _n_a_m_e
+ _r_e_s_o_l_v_e _o_r_d_e_r parameter above. Using this parameter
+ will force the client to assume that the server is on
+ the machine with the specified IP address and the
+ NetBIOS name component of the resource being connected
+ to will be ignored.
+
+ There is no default for this parameter. If not
+ supplied, it will be determined automatically by the
+ client as described above.
+
+ ----EEEE This parameter causes the client to write messages to
+ the standard error stream (stderr) rather than to the
+ standard output stream.
+
+ By default, the client writes messages to standard
+ output - typically the user's tty.
+
+ ----UUUU uuuusssseeeerrrrnnnnaaaammmmeeee[[[[%%%%ppppaaaassssssss]]]]
+ Sets the SMB username or username and password. If
+ %pass is not specified, The user will be prompted. The
+ client will first check the UUUUSSSSEEEERRRR environment variable,
+ then the LLLLOOOOGGGGNNNNAAAAMMMMEEEE variable and if either exists, the
+ string is uppercased. Anything in these variables
+ following a '%' sign will be treated as the password.
+ If these environment variables are not found, the
+ username GUEST is used.
+
+ If the password is not included in these environment
+ variables (using the %pass syntax), ssssmmmmbbbbcccclllliiiieeeennnntttt will look
+ for a PPPPAAAASSSSSSSSWWWWDDDD environment variable from which to read
+
+
+
+ Page 5 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ the password.
+
+ A third option is to use a credentials file which
+ contains the plaintext of the domain name, username and
+ password. This option is mainly provided for scripts
+ where the admin doesn't wish to pass the credentials on
+ the command line or via environment variables. If this
+ method is used, make certain that the permissions on
+ the file restrict access from unwanted users. See the
+ -_A for more details.
+
+ Be cautious about including passwords in scripts or in
+ the PPPPAAAASSSSSSSSWWWWDDDD environment variable. Also, on many systems
+ the command line of a running process may be seen via
+ the ppppssss command to be safe always allow ssssmmmmbbbbcccclllliiiieeeennnntttt to
+ prompt for a password and type it in directly.
+
+ ----AAAA ffffiiiilllleeeennnnaaaammmmeeee
+ This option allows you to specify a file from which to
+ read the username, domain name, and password used in
+ the connection. The format of the file is
+
+
+ username = <value>
+ password = <value>
+ domain = <value>
+
+
+
+ If the domain parameter is missing the current
+ workgroup name is used instead. Make certain that the
+ permissions on the file restrict access from unwanted
+ users.
+
+ ----LLLL This option allows you to look at what services are
+ available on a server. You use it as ssssmmmmbbbbcccclllliiiieeeennnntttt ----LLLL hhhhoooosssstttt
+ and a list should appear. The -_I option may be useful
+ if your NetBIOS names don't match your TCP/IP DNS host
+ names or if you are trying to reach a host on another
+ network.
+
+ ----tttt tttteeeerrrrmmmmiiiinnnnaaaallll ccccooooddddeeee
+ This option tells ssssmmmmbbbbcccclllliiiieeeennnntttt how to interpret filenames
+ coming from the remote server. Usually Asian language
+ multibyte UNIX implementations use different character
+ sets than SMB/CIFS servers (EEEEUUUUCCCC instead of SSSSJJJJIIIISSSS for
+ example). Setting this parameter will let ssssmmmmbbbbcccclllliiiieeeennnntttt
+ convert between the UNIX filenames and the SMB
+ filenames correctly. This option has not been seriously
+ tested and may have some problems.
+
+ The terminal codes include CWsjis, CWeuc, CWjis7,
+
+
+
+ Page 6 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ CWjis8, CWjunet, CWhex, CWcap. This is not a complete
+ list, check the Samba source code for the complete
+ list.
+
+ ----bbbb bbbbuuuuffffffffeeeerrrrssssiiiizzzzeeee
+ This option changes the transmit/send buffer size when
+ getting or putting a file from/to the server. The
+ default is 65520 bytes. Setting this value smaller (to
+ 1200 bytes) has been observed to speed up file
+ transfers to and from a Win9x server.
+
+ ----WWWW WWWWOOOORRRRKKKKGGGGRRRROOOOUUUUPPPP
+ Override the default workgroup (domain) specified in
+ the workgroup parameter of the _s_m_b._c_o_n_f file for this
+ connection. This may be needed to connect to some
+ servers.
+
+ ----TTTT ttttaaaarrrr ooooppppttttiiiioooonnnnssss
+ smbclient may be used to create ttttaaaarrrr((((1111)))) compatible
+ backups of all the files on an SMB/CIFS share. The
+ secondary tar flags that can be given to this option
+ are :
+
+ o+ _c - Create a tar file on UNIX. Must be followed by
+ the name of a tar file, tape device or "-" for
+ standard output. If using standard output you must
+ turn the log level to its lowest value -d0 to avoid
+ corrupting your tar file. This flag is mutually
+ exclusive with the _x flag.
+
+ o+ _x - Extract (restore) a local tar file back to a
+ share. Unless the -D option is given, the tar files
+ will be restored from the top level of the share.
+ Must be followed by the name of the tar file, device
+ or "-" for standard input. Mutually exclusive with
+ the _c flag. Restored files have their creation times
+ (mtime) set to the date saved in the tar file.
+ Directories currently do not get their creation dates
+ restored properly.
+
+ o+ _I - Include files and directories. Is the default
+ behavior when filenames are specified above. Causes
+ tar files to be included in an extract or create (and
+ therefore everything else to be excluded). See
+ example below. Filename globbing works in one of two
+ ways. See r below.
+
+ o+ _X - Exclude files and directories. Causes tar files
+ to be excluded from an extract or create. See example
+ below. Filename globbing works in one of two ways
+ now. See _r below.
+
+
+
+
+ Page 7 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ o+ _b - Blocksize. Must be followed by a valid (greater
+ than zero) blocksize. Causes tar file to be written
+ out in blocksize*TBLOCK (usually 512 byte) blocks.
+
+ o+ _g - Incremental. Only back up files that have the
+ archive bit set. Useful only with the _c flag.
+
+ o+ _q - Quiet. Keeps tar from printing diagnostics as it
+ works. This is the same as tarmode quiet.
+
+ o+ _r - Regular expression include or exclude. Uses
+ regular expression matching for excluding or
+ excluding files if compiled with HAVE_REGEX_H.
+ However this mode can be very slow. If not compiled
+ with HAVE_REGEX_H, does a limited wildcard match on
+ '*' and '?'.
+
+ o+ _N - Newer than. Must be followed by the name of a
+ file whose date is compared against files found on
+ the share during a create. Only files newer than the
+ file specified are backed up to the tar file. Useful
+ only with the _c flag.
+
+ o+ _a - Set archive bit. Causes the archive bit to be
+ reset when a file is backed up. Useful with the _g and
+ _c flags.
+
+ TTTTaaaarrrr LLLLoooonnnngggg FFFFiiiilllleeee NNNNaaaammmmeeeessss
+
+ ssssmmmmbbbbcccclllliiiieeeennnntttt's tar option now supports long file names both on
+ backup and restore. However, the full path name of the file
+ must be less than 1024 bytes. Also, when a tar archive is
+ created, ssssmmmmbbbbcccclllliiiieeeennnntttt's tar option places all files in the
+ archive with relative names, not absolute names.
+
+ TTTTaaaarrrr FFFFiiiilllleeeennnnaaaammmmeeeessss
+
+ All file names can be given as DOS path names (with '\' as
+ the component separator) or as UNIX path names (with '/' as
+ the component separator).
+
+ EEEExxxxaaaammmmpppplllleeeessss
+
+ Restore from tar file _b_a_c_k_u_p._t_a_r into myshare on mypc (no
+ password on share).
+
+ ssssmmmmbbbbcccclllliiiieeeennnntttt ////////mmmmyyyyppppcccc////yyyysssshhhhaaaarrrreeee """""""" ----NNNN ----TTTTxxxx bbbbaaaacccckkkkuuuupppp....ttttaaaarrrr
+
+ Restore everything except _u_s_e_r_s/_d_o_c_s
+
+ ssssmmmmbbbbcccclllliiiieeeennnntttt ////////mmmmyyyyppppcccc////mmmmyyyysssshhhhaaaarrrreeee """""""" ----NNNN ----TTTTXXXXxxxx bbbbaaaacccckkkkuuuupppp....ttttaaaarrrr uuuusssseeeerrrrssss////ddddooooccccssss
+
+
+
+
+ Page 8 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ Create a tar file of the files beneath _u_s_e_r_s/_d_o_c_s.
+
+ ssssmmmmbbbbcccclllliiiieeeennnntttt ////////mmmmyyyyppppcccc////mmmmyyyysssshhhhaaaarrrreeee """""""" ----NNNN ----TTTTcccc bbbbaaaacccckkkkuuuupppp....ttttaaaarrrr uuuusssseeeerrrrssss////ddddooooccccssss
+
+ Create the same tar file as above, but now use a DOS path
+ name.
+
+ ssssmmmmbbbbcccclllliiiieeeennnntttt ////////mmmmyyyyppppcccc////mmmmyyyysssshhhhaaaarrrreeee """""""" ----NNNN ----ttttcccc bbbbaaaacccckkkkuuuupppp....ttttaaaarrrr uuuusssseeeerrrrssss\\\\eeeeddddooooccccssss
+
+ Create a tar file of all the files and directories in the
+ share.
+
+ ssssmmmmbbbbcccclllliiiieeeennnntttt ////////mmmmyyyyppppcccc////mmmmyyyysssshhhhaaaarrrreeee """""""" ----NNNN ----TTTTcccc bbbbaaaacccckkkkuuuupppp....ttttaaaarrrr ****
+
+ ----DDDD iiiinnnniiiittttiiiiaaaallll ddddiiiirrrreeeeccccttttoooorrrryyyy
+ Change to initial directory before starting. Probably
+ only of any use with the tar -T option.
+
+ ----cccc ccccoooommmmmmmmaaaannnndddd ssssttttrrrriiiinnnngggg
+ command string is a semicolon-separated list of
+ commands to be executed instead of prompting from
+ stdin. -_N is implied by -_c.
+
+ This is particularly useful in scripts and for printing
+ stdin to the server, e.g. ----cccc ''''pppprrrriiiinnnntttt ----''''.
+
+ OOOOPPPPEEEERRRRAAAATTTTIIIIOOOONNNNSSSS
+ Once the client is running, the user is presented with a
+ prompt :
+
+ smb:\>
+
+ The backslash ("\") indicates the current working directory
+ on the server, and will change if the current working
+ directory is changed.
+
+ The prompt indicates that the client is ready and waiting to
+ carry out a user command. Each command is a single word,
+ optionally followed by parameters specific to that command.
+ Command and parameters are space-delimited unless these
+ notes specifically state otherwise. All commands are case-
+ insensitive. Parameters to commands may or may not be case
+ sensitive, depending on the command.
+
+ You can specify file names which have spaces in them by
+ quoting the name with double quotes, for example "a long
+ file name".
+
+ Parameters shown in square brackets (e.g., "[parameter]")
+ are optional. If not given, the command will use suitable
+ defaults. Parameters shown in angle brackets (e.g.,
+ "<parameter>") are required.
+
+
+
+ Page 9 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ Note that all commands operating on the server are actually
+ performed by issuing a request to the server. Thus the
+ behavior may vary from server to server, depending on how
+ the server was implemented.
+
+ The commands available are given here in alphabetical order.
+
+ ???? [[[[ccccoooommmmmmmmaaaannnndddd]]]]
+ If _c_o_m_m_a_n_d is specified, the ? command will display a
+ brief informative message about the specified command.
+ If no command is specified, a list of available
+ commands will be displayed.
+
+ !!!! [[[[sssshhhheeeellllllll ccccoooommmmmmmmaaaannnndddd]]]]
+ If _s_h_e_l_l _c_o_m_m_a_n_d is specified, the ! command will
+ execute a shell locally and run the specified shell
+ command. If no command is specified, a local shell will
+ be run.
+
+ aaaallllttttnnnnaaaammmmeeee ffffiiiilllleeee
+ The client will request that the server return the
+ "alternate" name (the 8.3 name) for a file or
+ directory.
+
+ ccccaaaannnncccceeeellll jjjjoooobbbbiiiidddd0000 [[[[jjjjoooobbbbiiiidddd1111]]]] ............ [[[[jjjjoooobbbbiiiiddddNNNN]]]]
+ The client will request that the server cancel the
+ printjobs identified by the given numeric print job
+ ids.
+
+ cccchhhhmmmmoooodddd ffffiiiilllleeee mmmmooooddddeeee iiiinnnn ooooccccttttaaaallll
+ This command depends on the server supporting the CIFS
+ UNIX extensions and will fail if the server does not.
+ The client requests that the server change the UNIX
+ permissions to the given octal mode, in standard UNIX
+ format.
+
+ cccchhhhoooowwwwnnnn ffffiiiilllleeee uuuuiiiidddd ggggiiiidddd
+ This command depends on the server supporting the CIFS
+ UNIX extensions and will fail if the server does not.
+ The client requests that the server change the UNIX
+ user and group ownership to the given decimal values.
+ Note there is currently no way to remotely look up the
+ UNIX uid and gid values for a given name. This may be
+ addressed in future versions of the CIFS UNIX
+ extensions.
+
+ ccccdddd [[[[ddddiiiirrrreeeeccccttttoooorrrryyyy nnnnaaaammmmeeee]]]]
+ If "directory name" is specified, the current working
+ directory on the server will be changed to the
+ directory specified. This operation will fail if for
+ any reason the specified directory is inaccessible.
+
+
+
+
+ Page 10 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ If no directory name is specified, the current working
+ directory on the server will be reported.
+
+ ddddeeeellll <<<<mmmmaaaasssskkkk>>>>
+ The client will request that the server attempt to
+ delete all files matching _m_a_s_k from the current working
+ directory on the server.
+
+ ddddiiiirrrr <<<<mmmmaaaasssskkkk>>>>
+ A list of the files matching _m_a_s_k in the current
+ working directory on the server will be retrieved from
+ the server and displayed.
+
+ eeeexxxxiiiitttt Terminate the connection with the server and exit from
+ the program.
+
+ ggggeeeetttt <<<<rrrreeeemmmmooootttteeee ffffiiiilllleeee nnnnaaaammmmeeee>>>> [[[[llllooooccccaaaallll ffffiiiilllleeee nnnnaaaammmmeeee]]]]
+ Copy the file called _r_e_m_o_t_e _f_i_l_e _n_a_m_e from the server
+ to the machine running the client. If specified, name
+ the local copy _l_o_c_a_l _f_i_l_e _n_a_m_e. Note that all transfers
+ in ssssmmmmbbbbcccclllliiiieeeennnntttt are binary. See also the lowercase
+ command.
+
+ hhhheeeellllpppp [[[[ccccoooommmmmmmmaaaannnndddd]]]]
+ See the ? command above.
+
+ llllccccdddd [[[[ddddiiiirrrreeeeccccttttoooorrrryyyy nnnnaaaammmmeeee]]]]
+ If _d_i_r_e_c_t_o_r_y _n_a_m_e is specified, the current working
+ directory on the local machine will be changed to the
+ directory specified. This operation will fail if for
+ any reason the specified directory is inaccessible.
+
+ If no directory name is specified, the name of the
+ current working directory on the local machine will be
+ reported.
+
+ lllliiiinnnnkkkk ssssoooouuuurrrrcccceeee ddddeeeessssttttiiiinnnnaaaattttiiiioooonnnn
+ This command depends on the server supporting the CIFS
+ UNIX extensions and will fail if the server does not.
+ The client requests that the server create a hard link
+ between the source and destination files. The source
+ file must not exist.
+
+ lllloooowwwweeeerrrrccccaaaasssseeee
+ Toggle lowercasing of filenames for the get and mget
+ commands.
+
+ When lowercasing is toggled ON, local filenames are
+ converted to lowercase when using the get and mget
+ commands. This is often useful when copying (say) MSDOS
+ files from a server, because lowercase filenames are
+ the norm on UNIX systems.
+
+
+
+ Page 11 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ llllssss <<<<mmmmaaaasssskkkk>>>>
+ See the dir command above.
+
+ mmmmaaaasssskkkk <<<<mmmmaaaasssskkkk>>>>
+ This command allows the user to set up a mask which
+ will be used during recursive operation of the mget and
+ mput commands.
+
+ The masks specified to the mget and mput commands act
+ as filters for directories rather than files when
+ recursion is toggled ON.
+
+ The mask specified with the mask command is necessary
+ to filter files within those directories. For example,
+ if the mask specified in an mget command is "source*"
+ and the mask specified with the mask command is "*.c"
+ and recursion is toggled ON, the mget command will
+ retrieve all files matching "*.c" in all directories
+ below and including all directories matching "source*"
+ in the current working directory.
+
+ Note that the value for mask defaults to blank
+ (equivalent to "*") and remains so until the mask
+ command is used to change it. It retains the most
+ recently specified value indefinitely. To avoid
+ unexpected results it would be wise to change the value
+ of mask back to "*" after using the mget or mput
+ commands.
+
+ mmmmdddd <<<<ddddiiiirrrreeeeccccttttoooorrrryyyy nnnnaaaammmmeeee>>>>
+ See the mkdir command.
+
+ mmmmggggeeeetttt <<<<mmmmaaaasssskkkk>>>>
+ Copy all files matching _m_a_s_k from the server to the
+ machine running the client.
+
+ Note that _m_a_s_k is interpreted differently during
+ recursive operation and non-recursive operation - refer
+ to the recurse and mask commands for more information.
+ Note that all transfers in ssssmmmmbbbbcccclllliiiieeeennnntttt are binary. See
+ also the lowercase command.
+
+ mmmmkkkkddddiiiirrrr <<<<ddddiiiirrrreeeeccccttttoooorrrryyyy nnnnaaaammmmeeee>>>>
+ Create a new directory on the server (user access
+ privileges permitting) with the specified name.
+
+ mmmmppppuuuutttt <<<<mmmmaaaasssskkkk>>>>
+ Copy all files matching _m_a_s_k in the current working
+ directory on the local machine to the current working
+ directory on the server.
+
+ Note that _m_a_s_k is interpreted differently during
+
+
+
+ Page 12 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ recursive operation and non-recursive operation - refer
+ to the recurse and mask commands for more information.
+ Note that all transfers in ssssmmmmbbbbcccclllliiiieeeennnntttt are binary.
+
+ pppprrrriiiinnnntttt <<<<ffffiiiilllleeee nnnnaaaammmmeeee>>>>
+ Print the specified file from the local machine through
+ a printable service on the server.
+
+ See also the printmode command.
+
+ pppprrrriiiinnnnttttmmmmooooddddeeee <<<<ggggrrrraaaapppphhhhiiiiccccssss oooorrrr tttteeeexxxxtttt>>>>
+ Set the print mode to suit either binary data (such as
+ graphical information) or text. Subsequent print
+ commands will use the currently set print mode.
+
+ pppprrrroooommmmpppptttt
+ Toggle prompting for filenames during operation of the
+ mget and mput commands.
+
+ When toggled ON, the user will be prompted to confirm
+ the transfer of each file during these commands. When
+ toggled OFF, all specified files will be transferred
+ without prompting.
+
+ ppppuuuutttt <<<<llllooooccccaaaallll ffffiiiilllleeee nnnnaaaammmmeeee>>>> [[[[rrrreeeemmmmooootttteeee ffffiiiilllleeee nnnnaaaammmmeeee]]]]
+ Copy the file called _l_o_c_a_l _f_i_l_e _n_a_m_e from the machine
+ running the client to the server. If specified, name
+ the remote copy _r_e_m_o_t_e _f_i_l_e _n_a_m_e. Note that all
+ transfers in ssssmmmmbbbbcccclllliiiieeeennnntttt are binary. See also the
+ lowercase command.
+
+ qqqquuuueeeeuuuueeee
+ Displays the print queue, showing the job id, name,
+ size and current status.
+
+ qqqquuuuiiiitttt See the exit command.
+
+ rrrrdddd <<<<ddddiiiirrrreeeeccccttttoooorrrryyyy nnnnaaaammmmeeee>>>>
+ See the rmdir command.
+
+ rrrreeeeccccuuuurrrrsssseeee
+ Toggle directory recursion for the commands mget and
+ mput.
+
+ When toggled ON, these commands will process all
+ directories in the source directory (i.e., the
+ directory they are copying from ) and will recurse into
+ any that match the mask specified to the command. Only
+ files that match the mask specified using the mask
+ command will be retrieved. See also the mask command.
+
+ When recursion is toggled OFF, only files from the
+
+
+
+ Page 13 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ current working directory on the source machine that
+ match the mask specified to the mget or mput commands
+ will be copied, and any mask specified using the mask
+ command will be ignored.
+
+ rrrrmmmm <<<<mmmmaaaasssskkkk>>>>
+ Remove all files matching _m_a_s_k from the current working
+ directory on the server.
+
+ rrrrmmmmddddiiiirrrr <<<<ddddiiiirrrreeeeccccttttoooorrrryyyy nnnnaaaammmmeeee>>>>
+ Remove the specified directory (user access privileges
+ permitting) from the server.
+
+ sssseeeettttmmmmooooddddeeee <<<<ffffiiiilllleeeennnnaaaammmmeeee>>>> <<<<ppppeeeerrrrmmmm====[[[[++++||||----]]]]rrrrsssshhhhaaaa>>>>
+ A version of the DOS attrib command to set file
+ permissions. For example:
+
+ sssseeeettttmmmmooooddddeeee mmmmyyyyffffiiiilllleeee ++++rrrr
+
+ would make myfile read only.
+
+ ssssyyyymmmmlllliiiinnnnkkkk ssssoooouuuurrrrcccceeee ddddeeeessssttttiiiinnnnaaaattttiiiioooonnnn
+ This command depends on the server supporting the CIFS
+ UNIX extensions and will fail if the server does not.
+ The client requests that the server create a symbolic
+ hard link between the source and destination files. The
+ source file must not exist. Note that the server will
+ not create a link to any path that lies outside the
+ currently connected share. This is enforced by the
+ Samba server.
+
+ ttttaaaarrrr <<<<cccc||||xxxx>>>>[[[[IIIIXXXXbbbbggggNNNNaaaa]]]]
+ Performs a tar operation - see the -_T command line
+ option above. Behavior may be affected by the tarmode
+ command (see below). Using g (incremental) and N
+ (newer) will affect tarmode settings. Note that using
+ the "-" option with tar x may not work - use the
+ command line option instead.
+
+ bbbblllloooocccckkkkssssiiiizzzzeeee <<<<bbbblllloooocccckkkkssssiiiizzzzeeee>>>>
+ Blocksize. Must be followed by a valid (greater than
+ zero) blocksize. Causes tar file to be written out in
+ _b_l_o_c_k_s_i_z_e*TBLOCK (usually 512 byte) blocks.
+
+ ttttaaaarrrrmmmmooooddddeeee <<<<ffffuuuullllllll||||iiiinnnncccc||||rrrreeeesssseeeetttt||||nnnnoooorrrreeeesssseeeetttt>>>>
+ Changes tar's behavior with regard to archive bits. In
+ full mode, tar will back up everything regardless of
+ the archive bit setting (this is the default mode). In
+ incremental mode, tar will only back up files with the
+ archive bit set. In reset mode, tar will reset the
+ archive bit on all files it backs up (implies
+ read/write share).
+
+
+
+ Page 14 (printed 1/7/103)
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ NNNNOOOOTTTTEEEESSSS
+ Some servers are fussy about the case of supplied usernames,
+ passwords, share names (AKA service names) and machine
+ names. If you fail to connect try giving all parameters in
+ uppercase.
+
+ It is often necessary to use the -n option when connecting
+ to some types of servers. For example OS/2 LanManager
+ insists on a valid NetBIOS name being used, so you need to
+ supply a valid name that would be known to the server.
+
+ smbclient supports long file names where the server supports
+ the LANMAN2 protocol or above.
+
+ 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 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 LLLLIIIIBBBBSSSSMMMMBBBB____PPPPRRRROOOOGGGG may contain the path, executed with
+ system(), which the client should connect to instead of
+ connecting to a server. This functionality is primarily
+ intended as a development aid, and works best when using a
+ LMHOSTS file
+
+ IIIINNNNSSSSTTTTAAAALLLLLLLLAAAATTTTIIIIOOOONNNN
+ The location of the client program is a matter for
+ individual system administrators. The following are thus
+ suggestions only.
+
+ It is recommended that the smbclient software be installed
+ in the /_u_s_r/_l_o_c_a_l/_s_a_m_b_a/_b_i_n/ or /_u_s_r/_s_a_m_b_a/_b_i_n/ directory,
+ this directory readable by all, writeable only by root. The
+ client program itself should be executable by all. The
+ client should NNNNOOOOTTTT be setuid or setgid!
+
+ The client log files should be put in a directory readable
+ and writeable only by the user.
+
+ To test the client, you will need to know the name of a
+ running SMB/CIFS server. It is possible to run ssssmmmmbbbbdddd((((8888)))) as an
+ ordinary user - running that server as a daemon on a user-
+ accessible port (typically any port number over 1024) would
+ provide a suitable test server.
+
+ DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
+
+
+
+ PPPPaaaaggggeeee 11115555 ((((pppprrrriiiinnnntttteeeedddd 1111////7777////111100003333))))
+
+
+
+
+
+
+ SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111)))) UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV ((((00003333 SSSSeeeepppptttteeeemmmmbbbbeeeerrrr 2222000000002222)))) SSSSMMMMBBBBCCCCLLLLIIIIEEEENNNNTTTT((((1111))))
+
+
+
+ Most diagnostics issued by the client are logged in a
+ specified log file. The log file name is specified at
+ compile time, but may be overridden on the command line.
+
+ The number and nature of diagnostics available depends on
+ the debug level used by the client. If you have problems,
+ set the debug level to 3 and peruse the log files.
+
+ VVVVEEEERRRRSSSSIIIIOOOONNNN
+ This man page is correct for version 2.2 of the Samba suite.
+
+ AAAAUUUUTTTTHHHHOOOORRRR
+ The original Samba software and related utilities were
+ created by Andrew Tridgell. Samba is now developed by the
+ Samba Team as an Open Source project similar to the way the
+ Linux kernel is developed.
+
+ The original Samba man pages were written by Karl Auer. The
+ man page sources were converted to YODL format (another
+ excellent piece of Open Source software, available at
+ ftp://ftp.icce.rug.nl/pub/unix/
+ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the
+ Samba 2.0 release by Jeremy Allison. The conversion to
+ DocBook for Samba 2.2 was done by Gerald Carter
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Page 16 (printed 1/7/103)
+
+
+