From 1be1303f1bfdd99bd13e3270fb87bbe02dc2b69a Mon Sep 17 00:00:00 2001 From: Aurélien Aptel Date: Wed, 31 Jul 2013 17:29:10 +0200 Subject: manpages/smbclient: remove trailing whitespace MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Aurélien Aptel [ddiss@samba.org: split from tarmode documentation chages] Reviewed-by: David Disseldorp Reviewed-by: Andreas Schneider --- docs-xml/manpages/smbclient.1.xml | 288 +++++++++++++++++++------------------- 1 file changed, 144 insertions(+), 144 deletions(-) diff --git a/docs-xml/manpages/smbclient.1.xml b/docs-xml/manpages/smbclient.1.xml index 9539df3745..81a47d3f5d 100644 --- a/docs-xml/manpages/smbclient.1.xml +++ b/docs-xml/manpages/smbclient.1.xml @@ -80,171 +80,171 @@ This tool is part of the samba 7 suite. - smbclient is a client that can + smbclient is a client that can 'talk' to an SMB/CIFS server. It offers an interface similar to that of the ftp program (see ftp - 1). - 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 + 1). + 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. OPTIONS - + servicename - servicename is the name of the service + servicename is the name of the service you want to use on the server. A service name takes the form //server/service where server - is the NetBIOS name of the SMB/CIFS server - offering the desired service and service - is the name of the service offered. Thus to connect to + is the NetBIOS name of the SMB/CIFS server + offering the desired service and service + 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 //smbserver/printer - Note that the server name required is NOT necessarily - the IP (DNS) host name of the server ! The name required is + 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 smbclient or - using the name resolve order parameter in + The server name is looked up according to either + the -R parameter to smbclient or + using the name resolve order parameter in the smb.conf - 5 file, - allowing an administrator to change the order and methods + 5 file, + allowing an administrator to change the order and methods by which server names are looked up. password - The password required to access the specified - service on the specified server. If this parameter is - supplied, the -N option (suppress + 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. - 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 + 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. + 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. - + -R|--name-resolve <name resolve order> - 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 + 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 + The options are :"lmhosts", "host", "wins" and "bcast". They cause names to be resolved as follows: - 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 + 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. - - host: Do a standard host + + host: Do a standard host name to IP address resolution, using the system /etc/hosts - , 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 /etc/nsswitch.conf - file). Note that this method is only used if the NetBIOS name - type being queried is the 0x20 (server) name type, otherwise + , 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 /etc/nsswitch.conf + 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. - - wins: Query a name with + + wins: Query a name with the IP address listed in the wins server - parameter. If no WINS server has + parameter. If no WINS server has been specified this method will be ignored. - - bcast: Do a broadcast on - each of the known local interfaces listed in the + + bcast: Do a broadcast on + each of the known local interfaces listed in the interfaces - parameter. This is the least reliable of the name resolution - methods as it depends on the target host being on a locally + 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 + If this parameter is not set then the name resolve order defined in the smb.conf - 5 file parameter + 5 file parameter (name resolve order) will be used. - The default order is lmhosts, host, wins, bcast and without + The default order is lmhosts, host, wins, bcast and without this parameter or any entry in the name resolve order parameter of the smb.conf 5 file the name resolution methods will be attempted in this order. - - + + -M|--message NetBIOS name - 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 + 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 + 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. + 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 pipe the message through smbclient. - For example: smbclient -M FRED < mymessage.txt will send the - message in the file mymessage.txt to the + One useful trick is to pipe the message through smbclient. + For example: smbclient -M FRED < mymessage.txt will send the + message in the file mymessage.txt to the machine FRED. - You may also find the -U and - -I options useful, as they allow you to + 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 smb.conf - 5 for a description of how to handle incoming + 5 for a description of how to handle incoming WinPopup messages in Samba. - Note: Copy WinPopup into the startup group - on your WfWg PCs if you want them to always be able to receive + Note: Copy WinPopup into the startup group + on your WfWg PCs if you want them to always be able to receive messages. -p|--port port - This number is the TCP port number that will be used + 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 + TCP port number for an SMB/CIFS server is 139, which is the default. @@ -281,40 +281,40 @@ IP address 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 name resolve order + 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 name resolve order 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 + 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 + There is no default for this parameter. If not supplied, + it will be determined automatically by the client as described above. - + -E|--stderr - This parameter causes the client to write messages - to the standard error stream (stderr) rather than to the standard + 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 + + By default, the client writes messages to standard output - typically the user's tty. - + -L|--list - This option allows you to look at what services - are available on a server. You use it as smbclient -L + This option allows you to look at what services + are available on a server. You use it as smbclient -L host 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 + 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. - - + + -b|--send-buffer buffersize When sending or receiving files, smbclient uses an @@ -328,7 +328,7 @@ using the iosize command inside smbclient. - + -B|--browse Browse SMB servers using DNS. @@ -340,7 +340,7 @@ &popt.common.credentials; &popt.common.connection; &popt.autohelp; - + -t|--timeout <timeout-seconds> This allows the user to tune the default @@ -503,35 +503,35 @@ OPERATIONS - Once the client is running, the user is presented with + 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 + 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 + 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. + 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 + 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 + 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. - 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. + 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. @@ -776,8 +776,8 @@ lowercase Toggle lowercasing of filenames for the get and - mget commands. - + mget commands. + When lowercasing is toggled ON, local filenames are converted to lowercase when using the get and mget commands. This is @@ -992,7 +992,7 @@ rmdir <directory name> - Remove the specified directory (user access + Remove the specified directory (user access privileges permitting) from the server. @@ -1148,52 +1148,52 @@ 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 + smbclient supports long file names where the server supports the LANMAN2 protocol or above. ENVIRONMENT VARIABLES - The variable USER may contain the - username of the person using the client. This information is - used only if the protocol level is high enough to support + The variable USER 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 PASSWD may contain - the password of the person using the client. This information is - used only if the protocol level is high enough to support + The variable PASSWD 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 LIBSMB_PROG 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 + The variable LIBSMB_PROG 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 INSTALLATION - The location of the client program is a matter for + 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 /usr/local/samba/bin/ or - /usr/samba/bin/ directory, this directory readable - by all, writeable only by root. The client program itself should - be executable by all. The client should NOT be + /usr/samba/bin/ directory, this directory readable + by all, writeable only by root. The client program itself should + be executable by all. The client should NOT be setuid or setgid! - The client log files should be put in a directory readable + 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 + To test the client, you will need to know the name of a running SMB/CIFS server. It is possible to run smbd - 8 as an ordinary user - running that server as a daemon + 8 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. @@ -1202,12 +1202,12 @@ DIAGNOSTICS - Most diagnostics issued by the client are logged in a - specified log file. The log file name is specified at compile time, + 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, + 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. @@ -1221,17 +1221,17 @@ AUTHOR - - The original Samba software and related utilities + + 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 + 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 + + 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/) and updated for the Samba 2.0 - release by Jeremy Allison. The conversion to DocBook for + 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. The conversion to DocBook XML 4.2 for Samba 3.0 was done by Alexander Bokovoy. -- cgit