-.\" This manpage has been automatically generated by docbook2man-spec
-.\" from a DocBook document. docbook2man-spec can be found at:
-.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
+.\" This manpage has been automatically generated by docbook2man
+.\" from a DocBook document. This tool can be found at:
+.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
-.TH "SMBCLIENT" "1" "24 April 2001" "" ""
+.TH "SMBCLIENT" "1" "04 March 2003" "" ""
.SH NAME
smbclient \- ftp-like client to access SMB/CIFS resources on servers
.SH SYNOPSIS
-.sp
-\fBsmbclient\fR \fBservicename\fR [ \fBpassword\fR ] [ \fB-b <buffer size>\fR ] [ \fB-d debuglevel\fR ] [ \fB-D Directory\fR ] [ \fB-S server\fR ] [ \fB-U username\fR ] [ \fB-W workgroup\fR ] [ \fB-M <netbios name>\fR ] [ \fB-m maxprotocol\fR ] [ \fB-A authfile\fR ] [ \fB-N\fR ] [ \fB-l logfile\fR ] [ \fB-L <netbios name>\fR ] [ \fB-I destinationIP\fR ] [ \fB-E <terminal code>\fR ] [ \fB-c <command string>\fR ] [ \fB-i scope\fR ] [ \fB-O <socket options>\fR ] [ \fB-p port\fR ] [ \fB-R <name resolve order>\fR ] [ \fB-s <smb config file>\fR ] [ \fB-T<c|x>IXFqgbNan\fR ]
+
+\fBsmbclient\fR \fBservicename\fR [ \fBpassword\fR ] [ \fB-b <buffer size>\fR ] [ \fB-d debuglevel\fR ] [ \fB-D Directory\fR ] [ \fB-U username\fR ] [ \fB-W workgroup\fR ] [ \fB-M <netbios name>\fR ] [ \fB-m maxprotocol\fR ] [ \fB-A authfile\fR ] [ \fB-N\fR ] [ \fB-l logfile\fR ] [ \fB-L <netbios name>\fR ] [ \fB-I destinationIP\fR ] [ \fB-E\fR ] [ \fB-c <command string>\fR ] [ \fB-i scope\fR ] [ \fB-O <socket options>\fR ] [ \fB-p port\fR ] [ \fB-R <name resolve order>\fR ] [ \fB-s <smb config file>\fR ] [ \fB-T<c|x>IXFqgbNan\fR ]
+
.SH "DESCRIPTION"
.PP
-This tool is part of the Sambasuite.
+This tool is part of the Samba suite.
.PP
\fBsmbclient\fR is a client that can
\&'talk' to an SMB/CIFS server. It offers an interface
-similar to that of the ftp program (see \fBftp(1)\fR).
+similar to that of the ftp program (see \fBftp(1)\fR).
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
servicename is the name of the service
you want to use on the server. A service name takes the form
\fI//server/service\fR where \fIserver
-\fRis the NetBIOS name of the SMB/CIFS server
+\fR is the NetBIOS name of the SMB/CIFS server
offering the desired service and \fIservice\fR
-is the name of the service offered. Thus to connect to
+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 \fI//smbserver/printer
\fR
+
Note that the server name required is NOT necessarily
-the IP (DNS) host name of the server ! The name required is
+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 \fI-R\fR parameter to smbclient or
-using the name resolve order parameter in the smb.conf file,
+the \fI-R\fR parameter to \fBsmbclient\fR or
+using the name resolve order parameter in the \fIsmb.conf\fR file,
allowing an administrator to change the order and methods
by which server names are looked up.
.TP
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.
+or mixed case passwords may be rejected by these servers.
Be cautious about including passwords in scripts.
.TP
.TP
\fB-O socket options\fR
TCP socket options to set on the client
-socket. See the socket options parameter in the \fI smb.conf (5)\fR manpage for the list of valid
+socket. See the socket options parameter in the \fI smb.conf (5)\fR manpage for the list of valid
options.
.TP
\fB-R <name resolve order>\fR
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
+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
\(bu
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
+no name type attached to the NetBIOS name (see the lmhosts(5) for details) then
any name type matches for lookup.
.TP 0.2i
\(bu
host : Do a standard host
name to IP address resolution, using the system \fI/etc/hosts
\fR, NIS, or DNS lookups. This method of name resolution
-is operating system depended for instance on IRIX or Solaris this
+is operating system dependent, for instance on IRIX or Solaris this
may be controlled by the \fI/etc/nsswitch.conf\fR
-file). Note that this method is only used if the NetBIOS name
+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.
.TP 0.2i
\(bu
wins : Query a name with
the IP address listed in the \fIwins server\fR
-parameter. If no WINS server has
+parameter. If no WINS server has
been specified this method will be ignored.
.TP 0.2i
\(bu
methods as it depends on the target host being on a locally
connected subnet.
.RE
-.PP
+
If this parameter is not set then the name resolve order
-defined in the \fIsmb.conf\fR file parameter
+defined in the \fIsmb.conf\fR file parameter
(name resolve order) will be used.
-.PP
-.PP
+
The default order is lmhosts, host, wins, bcast and without
this parameter or any entry in the \fIname resolve order
-\fRparameter of the smb.conf file the name resolution
+\fR parameter of the \fIsmb.conf\fR file the name resolution
methods will be attempted in this order.
-.PP
.TP
\fB-M NetBIOS name\fR
This options allows you to send messages, using
is over 1600 bytes, as this is the limit of the protocol.
One useful trick is to cat the message through
-\fBsmbclient\fR. For example: \fB cat mymessage.txt | smbclient -M FRED \fR will
+\fBsmbclient\fR. For example: \fB cat mymessage.txt | smbclient -M FRED \fR will
send the message in the file \fImymessage.txt\fR
to the machine FRED.
\fI-I\fR options useful, as they allow you to
control the FROM and TO parts of the message.
-See the message command parameter in the \fI smb.conf(5)\fR for a description of how to handle incoming
+See the message command parameter in the \fI smb.conf(5)\fR for a description of how to handle incoming
WinPopup messages in Samba.
\fBNote\fR: Copy WinPopup into the startup group
\fB-i scope\fR
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 rfc1001.txt and rfc1002.txt.
+on the use of NetBIOS scopes, see \fIrfc1001.txt\fR
+and \fIrfc1002.txt\fR.
NetBIOS scopes are \fBvery\fR rarely used, only set
this parameter if you are the system administrator in charge of all
the NetBIOS systems you communicate with.
name you wish.
.TP
\fB-d debuglevel\fR
-debuglevel is an integer from 0 to 10, or
+\fIdebuglevel\fR is an integer from 0 to 10, or
the letter 'A'.
The default value if this parameter is not specified
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 debuglevel is set to the letter 'A', then \fBall
-\fRdebug messages will be printed. This setting
+cryptic. If \fIdebuglevel\fR is set to the letter 'A', then \fBall
+\fR debug messages will be printed. This setting
is for developers only (and people who \fBreally\fR want
to know how the code works internally).
Note that specifying this parameter here will override
-the log level parameter in the \fBsmb.conf (5)\fR
+the log level parameter in the \fIsmb.conf (5)\fR
file.
.TP
\fB-p port\fR
default.
.TP
\fB-l logfilename\fR
-If specified, logfilename specifies a base filename
+If specified, \fIlogfilename\fR specifies a base filename
into which operational data from the running client will be
logged.
For example, if the name specified was "log", the debug file
would be \fIlog.client\fR.
-The log file generated is never removed by the client.
+The log file generated is never removed by the client.
.TP
\fB-h\fR
Print the usage message for the client.
.TP
\fB-I IP-address\fR
-IP address is the address of the server to connect to.
+\fIIP address\fR 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
\fB-U username[%pass]\fR
Sets the SMB username or username and password.
If %pass is not specified, The user will be prompted. The client
-will first check the USER environment variable, then the
-\fI$LOGNAME\fR variable and if either exist, the
+will first check the \fBUSER\fR environment variable, then the
+\fBLOGNAME\fR variable and if either exists, the
string is uppercased. Anything in these variables following a '%'
-sign will be treated as the password. If these environmental
+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), rpcclient will look for
-a \fI$PASSWD\fR environment variable from which
+If the password is not included in these environment
+variables (using the %pass syntax), \fBsmbclient\fR will look for
+a \fBPASSWD\fR environment variable from which
to read the password.
A third option is to use a credentials file which
-contains the plaintext of the username and password. This
+contains the plaintext of the domain name, username and password. This
option is mainly provided for scripts where the admin doesn't
-desire to pass the credentials on the command line or via environment
+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
+on the file restrict access from unwanted users. See the
\fI-A\fR for more details.
Be cautious about including passwords in scripts or in
-the \fI$PASSWD\fR environment variable. Also, on
+the \fBPASSWD\fR environment variable. Also, on
many systems the command line of a running process may be seen
via the \fBps\fR command to be safe always allow
-\fBrpcclient\fR to prompt for a password and type
+\fBsmbclient\fR to prompt for a password and type
it in directly.
.TP
\fB-A filename\fR
This option allows
-you to specify a file from which to read the username and
-password used in the connection. The format of the file is
+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
+
-.sp
.nf
username = <value>
password = <value>
+domain = <value>
-.sp
.fi
-Make certain that the permissions on the file restrict
+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.
.TP
\fB-L\fR
This option allows you to look at what services
are available on a server. You use it as \fBsmbclient -L
-host\fR and a list should appear. The \fI-I
-\fRoption 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\fR and a list should appear. The \fI-I
+\fR 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.
.TP
\fB-t terminal code\fR
-This option tells smbclient how to interpret
+This option tells \fBsmbclient\fR how to interpret
filenames coming from the remote server. Usually Asian language
multibyte UNIX implementations use different character sets than
-SMB/CIFS servers (\fBEUC\fR instead of \fB SJIS\fR for example). Setting this parameter will let
+SMB/CIFS servers (\fBEUC\fR instead of \fB SJIS\fR for example). Setting this parameter will let
\fBsmbclient\fR convert between the UNIX filenames and
the SMB filenames correctly. This option has not been seriously tested
and may have some problems.
observed to speed up file transfers to and from a Win9x server.
.TP
\fB-W WORKGROUP\fR
-Override the default workgroup specified in the
-workgroup parameter of the \fIsmb.conf\fR file
-for this connection. This may be needed to connect to some
+Override the default workgroup (domain) specified
+in the workgroup parameter of the \fIsmb.conf\fR
+file for this connection. This may be needed to connect to some
servers.
.TP
\fB-T tar options\fR
smbclient may be used to create \fBtar(1)
-\fRcompatible backups of all the files on an SMB/CIFS
+\fR compatible backups of all the files on an SMB/CIFS
share. The secondary tar flags that can be given to this option
are :
.RS
\fII\fR - 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.
+everything else to be excluded). See example below. Filename globbing
+works in one of two ways. See r below.
.TP 0.2i
\(bu
\fIX\fR - 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.
+example below. Filename globbing works in one of two ways now.
See \fIr\fR below.
.TP 0.2i
\(bu
\fIb\fR - Blocksize. Must be followed
-by a valid (greater than zero) blocksize. Causes tar file to be
+by a valid (greater than zero) blocksize. Causes tar file to be
written out in blocksize*TBLOCK (usually 512 byte) blocks.
.TP 0.2i
\(bu
.TP 0.2i
\(bu
\fIq\fR - Quiet. Keeps tar from printing
-diagnostics as it works. This is the same as tarmode quiet.
+diagnostics as it works. This is the same as tarmode quiet.
.TP 0.2i
\(bu
\fIr\fR - Regular expression include
-or exclude. Uses regular 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 '?'.
+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 '?'.
.TP 0.2i
\(bu
\fIN\fR - Newer than. Must be followed
archive bit to be reset when a file is backed up. Useful with the
\fIg\fR and \fIc\fR flags.
.RE
-.PP
+
\fBTar Long File Names\fR
-.PP
-.PP
+
\fBsmbclient\fR'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, smbclient's tar option places all
+name of the file must be less than 1024 bytes. Also, when
+a tar archive is created, \fBsmbclient\fR's tar option places all
files in the archive with relative names, not absolute names.
-.PP
-.PP
+
\fBTar Filenames\fR
-.PP
-.PP
+
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).
-.PP
-.PP
+
\fBExamples\fR
-.PP
-.PP
-Restore from tar file backup.tar into myshare on mypc
+
+Restore from tar file \fIbackup.tar\fR into myshare on mypc
(no password on share).
-.PP
-.PP
-\fBsmbclient //mypc/myshare "" -N -Tx backup.tar
-\fR.PP
-.PP
+
+\fBsmbclient //mypc/yshare "" -N -Tx backup.tar
+\fR
+
Restore everything except \fIusers/docs\fR
-.PP
-.PP
+
\fBsmbclient //mypc/myshare "" -N -TXx backup.tar
users/docs\fR
-.PP
-.PP
-Create a tar file of the files beneath \fI users/docs\fR.
-.PP
-.PP
+
+Create a tar file of the files beneath \fI users/docs\fR.
+
\fBsmbclient //mypc/myshare "" -N -Tc
backup.tar users/docs \fR
-.PP
-.PP
+
Create the same tar file as above, but now use
a DOS path name.
-.PP
-.PP
+
\fBsmbclient //mypc/myshare "" -N -tc backup.tar
users\\edocs \fR
-.PP
-.PP
+
Create a tar file of all the files and directories in
the share.
-.PP
-.PP
+
\fBsmbclient //mypc/myshare "" -N -Tc backup.tar *
-\fR.PP
+\fR
.TP
\fB-D initial directory\fR
Change to initial directory before starting. Probably
only of any use with the tar -T option.
.TP
\fB-c command string\fR
-command string is a semicolon separated list of
-commands to be executed instead of prompting from stdin. \fI -N\fR is implied by \fI-c\fR.
+command string is a semicolon-separated list of
+commands to be executed instead of prompting from stdin. \fI -N\fR is implied by \fI-c\fR.
This is particularly useful in scripts and for printing stdin
to the server, e.g. \fB-c 'print -'\fR.
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
+state otherwise. All commands are case-insensitive. Parameters to
commands may or may not be case sensitive, depending on the command.
.PP
You can specify file names which have spaces in them by quoting
the name with double quotes, for example "a long file name".
.PP
Parameters shown in square brackets (e.g., "[parameter]") are
-optional. If not given, the command will use suitable defaults. Parameters
+optional. If not given, the command will use suitable defaults. Parameters
shown in angle brackets (e.g., "<parameter>") are required.
.PP
Note that all commands operating on the server are actually
The commands available are given here in alphabetical order.
.TP
\fB? [command]\fR
-If "command" is specified, the ? command will display
-a brief informative message about the specified command. If no
+If \fIcommand\fR 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.
.TP
\fB! [shell command]\fR
-If "shell command" is specified, the !
+If \fIshell command\fR 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.
.TP
+\fBaltname file\fR
+The client will request that the server return
+the "alternate" name (the 8.3 name) for a file or directory.
+.TP
+\fBcancel jobid0 [jobid1] ... [jobidN]\fR
+The client will request that the server cancel
+the printjobs identified by the given numeric print job ids.
+.TP
+\fBchmod file mode in octal\fR
+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.
+.TP
+\fBchown file uid gid\fR
+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.
+.TP
\fBcd [directory name]\fR
If "directory name" is specified, the current
working directory on the server will be changed to the directory
.TP
\fBdel <mask>\fR
The client will request that the server attempt
-to delete all files matching "mask" from the current working
+to delete all files matching \fImask\fR from the current working
directory on the server.
.TP
\fBdir <mask>\fR
-A list of the files matching "mask" in the current
+A list of the files matching \fImask\fR in the current
working directory on the server will be retrieved from the server
and displayed.
.TP
from the program.
.TP
\fBget <remote file name> [local file name]\fR
-Copy the file called "remote file name" from
+Copy the file called \fIremote file name\fR from
the server to the machine running the client. If specified, name
-the local copy "local file name". Note that all transfers in
+the local copy \fIlocal file name\fR. Note that all transfers in
\fBsmbclient\fR are binary. See also the
lowercase command.
.TP
See the ? command above.
.TP
\fBlcd [directory name]\fR
-If "directory name" is specified, the current
+If \fIdirectory name\fR 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.
.TP
+\fBlink source destination\fR
+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.
+.TP
\fBlowercase\fR
Toggle lowercasing of filenames for the get and
mget commands.
See the mkdir command.
.TP
\fBmget <mask>\fR
-Copy all files matching mask from the server to
+Copy all files matching \fImask\fR from the server to
the machine running the client.
-Note that mask is interpreted differently during recursive
+Note that \fImask\fR 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
-smbclient are binary. See also the lowercase command.
+\fBsmbclient\fR are binary. See also the lowercase command.
.TP
\fBmkdir <directory name>\fR
Create a new directory on the server (user access
privileges permitting) with the specified name.
.TP
\fBmput <mask>\fR
-Copy all files matching mask in the current working
+Copy all files matching \fImask\fR in the current working
directory on the local machine to the current working directory on
the server.
-Note that mask is interpreted differently during recursive
+Note that \fImask\fR 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 smbclient
+commands for more information. Note that all transfers in \fBsmbclient\fR
are binary.
.TP
\fBprint <file name>\fR
OFF, all specified files will be transferred without prompting.
.TP
\fBput <local file name> [remote file name]\fR
-Copy the file called "local file name" from the
+Copy the file called \fIlocal file name\fR from the
machine running the client to the server. If specified,
-name the remote copy "remote file name". Note that all transfers
-in smbclient are binary. See also the lowercase command.
+name the remote copy \fIremote file name\fR. Note that all transfers
+in \fBsmbclient\fR are binary. See also the lowercase command.
.TP
\fBqueue\fR
Displays the print queue, showing the job id,
using the mask command will be ignored.
.TP
\fBrm <mask>\fR
-Remove all files matching mask from the current
+Remove all files matching \fImask\fR from the current
working directory on the server.
.TP
\fBrmdir <directory name>\fR
Remove the specified directory (user access
privileges permitting) from the server.
.TP
+\fBsetmode <filename> <perm=[+|\\-]rsha>\fR
+A version of the DOS attrib command to set
+file permissions. For example:
+
+\fBsetmode myfile +r \fR
+
+would make myfile read only.
+.TP
+\fBsymlink source destination\fR
+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.
+.TP
\fBtar <c|x>[IXbgNa]\fR
Performs a tar operation - see the \fI-T
-\fRcommand line option above. Behavior may be affected
+\fR 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.
\fBblocksize <blocksize>\fR
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.
+\fIblocksize\fR*TBLOCK (usually 512 byte) blocks.
.TP
\fBtarmode <full|inc|reset|noreset>\fR
Changes tar's behavior with regard to archive
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).
-.TP
-\fBsetmode <filename> <perm=[+|\\-]rsha>\fR
-A version of the DOS attrib command to set
-file permissions. For example:
-
-\fBsetmode myfile +r \fR
-
-would make myfile read only.
.SH "NOTES"
.PP
Some servers are fussy about the case of supplied usernames,
supports the LANMAN2 protocol or above.
.SH "ENVIRONMENT VARIABLES"
.PP
-The variable \fI$USER\fR 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 \fBUSER\fR 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.
.PP
-The variable \fI$PASSWD\fR may contain
-the password of the person using the client. This information is
+The variable \fBPASSWD\fR 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.
+.PP
+The variable \fBLIBSMB_PROG\fR 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
.SH "INSTALLATION"
.PP
The location of the client program is a matter for
.PP
To test the client, you will need to know the name of a
running SMB/CIFS server. It is possible to run \fBsmbd(8)
-\fRan ordinary user - running that server as a daemon
+\fR 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.
.SH "DIAGNOSTICS"
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
+release by Jeremy Allison. The conversion to DocBook for
Samba 2.2 was done by Gerald Carter
git.samba.org / ira / wip.git / blobdiff