1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
8 CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
28 >smbclient -- ftp-like client to access SMB/CIFS resources
31 CLASS="REFSYNOPSISDIV"
41 > {servicename} [password] [-b <buffer size>] [-d debuglevel] [-D Directory] [-U username] [-W workgroup] [-M <netbios name>] [-m maxprotocol] [-A authfile] [-N] [-l logfile] [-L <netbios name>] [-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
51 >This tool is part of the <SPAN
62 > is a client that can
63 'talk' to an SMB/CIFS server. It offers an interface
64 similar to that of the ftp program (see <SPAN
71 Operations include things like getting files from the server
72 to the local machine, putting files from the local machine to
73 the server, retrieving directory information from the server
92 >servicename is the name of the service
93 you want to use on the server. A service name takes the form
101 > is the NetBIOS name of the SMB/CIFS server
102 offering the desired service and <VAR
106 is the name of the service offered. Thus to connect to
107 the service "printer" on the SMB/CIFS server "smbserver",
108 you would use the servicename <TT
114 >Note that the server name required is NOT necessarily
115 the IP (DNS) host name of the server ! The name required is
116 a NetBIOS server name, which may or may not be the
117 same as the IP hostname of the machine running the server.
120 >The server name is looked up according to either
128 using the name resolve order parameter in
132 CLASS="REFENTRYTITLE"
136 allowing an administrator to change the order and methods
137 by which server names are looked up. </P
143 >The password required to access the specified
144 service on the specified server. If this parameter is
149 password prompt) is assumed. </P
151 >There is no default password. If no password is supplied
152 on the command line (either by using this parameter or adding
153 a password to the <VAR
161 specified, the client will prompt for a password, even if
162 the desired service does not require one. (If no password is
163 required, simply press ENTER to provide a null password.)
166 >Note: Some servers (including OS/2 and Windows for
167 Workgroups) insist on an uppercase password. Lowercase
168 or mixed case passwords may be rejected by these servers.
171 >Be cautious about including passwords in scripts.
178 >Specifies the location of the all
182 CLASS="REFENTRYTITLE"
188 >-O socket options</DT
191 >TCP socket options to set on the client
192 socket. See the socket options parameter in
196 CLASS="REFENTRYTITLE"
199 > manual page for the list of valid
203 >-R <name resolve order></DT
206 >This option is used by the programs in the Samba
207 suite to determine what naming services and in what order to resolve
208 host names to IP addresses. The option takes a space-separated
209 string of different name resolution options.</P
211 >The options are :"lmhosts", "host", "wins" and "bcast". They
212 cause names to be resolved as follows:</P
222 address in the Samba lmhosts file. If the line in lmhosts has
223 no name type attached to the NetBIOS name (see
227 CLASS="REFENTRYTITLE"
231 any name type matches for lookup.</P
238 >: Do a standard host
239 name to IP address resolution, using the system <TT
243 >, NIS, or DNS lookups. This method of name resolution
244 is operating system dependent, for instance on IRIX or Solaris this
245 may be controlled by the <TT
247 >/etc/nsswitch.conf</TT
249 file). Note that this method is only used if the NetBIOS name
250 type being queried is the 0x20 (server) name type, otherwise
259 the IP address listed in the <VAR
263 parameter. If no WINS server has
264 been specified this method will be ignored.</P
272 each of the known local interfaces listed in the
277 parameter. This is the least reliable of the name resolution
278 methods as it depends on the target host being on a locally
283 >If this parameter is not set then the name resolve order
287 CLASS="REFENTRYTITLE"
291 (name resolve order) will be used. </P
293 >The default order is lmhosts, host, wins, bcast and without
294 this parameter or any entry in the <VAR
298 > parameter of the <SPAN
301 CLASS="REFENTRYTITLE"
304 > file the name resolution
305 methods will be attempted in this order. </P
311 >This options allows you to send messages, using
312 the "WinPopup" protocol, to another computer. Once a connection is
313 established you then type your message, pressing ^D (control-D) to
316 >If the receiving computer is running WinPopup the user will
317 receive the message and probably a beep. If they are not running
318 WinPopup the message will be lost, and no error message will
321 >The message is also automatically truncated if the message
322 is over 1600 bytes, as this is the limit of the protocol.
325 >One useful trick is to cat the message through
331 > cat mymessage.txt | smbclient -M FRED </B
333 send the message in the file <TT
337 to the machine FRED. </P
339 >You may also find the <VAR
346 > options useful, as they allow you to
347 control the FROM and TO parts of the message. </P
351 >message command</VAR
352 > parameter in the <SPAN
355 CLASS="REFENTRYTITLE"
358 > for a description of how to handle incoming
359 WinPopup messages in Samba. </P
367 >: Copy WinPopup into the startup group
368 on your WfWg PCs if you want them to always be able to receive
375 >This specifies a NetBIOS scope that smbclient will
376 use to communicate with when generating NetBIOS names. For details
377 on the use of NetBIOS scopes, see <TT
385 NetBIOS scopes are <SPAN
391 > rarely used, only set
392 this parameter if you are the system administrator in charge of all
393 the NetBIOS systems you communicate with. </P
399 >If specified, this parameter suppresses the normal
400 password prompt from the client to the user. This is useful when
401 accessing a service that does not require a password. </P
403 >Unless a password is specified on the command line or
404 this parameter is specified, the client will request a
411 >By default, the client will use the local
412 machine's hostname (in uppercase) as its NetBIOS name. This parameter
413 allows you to override the host name and use whatever NetBIOS
423 > is an integer from 0 to 10, or
426 >The default value if this parameter is not specified
429 >The higher this value, the more detail will be logged to
430 the log files about the activities of the
431 client. At level 0, only critical errors and serious warnings will
432 be logged. Level 1 is a reasonable level for day to day running -
433 it generates a small amount of information about operations
436 >Levels above 1 will generate considerable amounts of log
437 data, and should only be used when investigating a problem.
438 Levels above 3 are designed for use only by developers and
439 generate HUGE amounts of log data, most of which is extremely
443 > is set to the letter 'A', then <SPAN
450 > debug messages will be printed. This setting
451 is for developers only (and people who <SPAN
458 to know how the code works internally). </P
460 >Note that specifying this parameter here will override
461 the log level parameter in the <TT
471 >This number is the TCP port number that will be used
472 when making connections to the server. The standard (well-known)
473 TCP port number for an SMB/CIFS server is 139, which is the
483 > specifies a base filename
484 into which operational data from the running client will be
487 >The default base name is specified at compile time.</P
489 >The base name is used to generate actual log file names.
490 For example, if the name specified was "log", the debug file
496 >The log file generated is never removed by the client.
503 >Print the usage message for the client. </P
512 > is the address of the server to connect to.
513 It should be specified in standard "a.b.c.d" notation. </P
515 >Normally the client would attempt to locate a named
516 SMB/CIFS server by looking it up via the NetBIOS name resolution
517 mechanism described above in the <VAR
519 >name resolve order</VAR
521 parameter above. Using this parameter will force the client
522 to assume that the server is on the machine with the specified IP
523 address and the NetBIOS name component of the resource being
524 connected to will be ignored. </P
526 >There is no default for this parameter. If not supplied,
527 it will be determined automatically by the client as described
534 >This parameter causes the client to write messages
535 to the standard error stream (stderr) rather than to the standard
538 >By default, the client writes messages to standard output
539 - typically the user's tty. </P
542 >-U username[%pass]</DT
545 >Sets the SMB username or username and password.
546 If %pass is not specified, The user will be prompted. The client
547 will first check the <VAR
550 > environment variable, then the
554 > variable and if either exists, the
555 string is uppercased. Anything in these variables following a '%'
556 sign will be treated as the password. If these environment
557 variables are not found, the username <CODE
563 >If the password is not included in these environment
564 variables (using the %pass syntax), <B
571 > environment variable from which
572 to read the password. </P
574 >A third option is to use a credentials file which
575 contains the plaintext of the domain name, username and password. This
576 option is mainly provided for scripts where the admin doesn't
577 wish to pass the credentials on the command line or via environment
578 variables. If this method is used, make certain that the permissions
579 on the file restrict access from unwanted users. See the
583 > for more details. </P
585 >Be cautious about including passwords in scripts or in
589 > environment variable. Also, on
590 many systems the command line of a running process may be seen
594 > command to be safe always allow
598 > to prompt for a password and type
606 you to specify a file from which to read the username, domain name, and
607 password used in the connection. The format of the file is
611 CLASS="PROGRAMLISTING"
612 >username = <value>
613 password = <value>
614 domain = <value></PRE
617 >If the domain parameter is missing the current workgroup name
618 is used instead. Make certain that the permissions on the file restrict
619 access from unwanted users. </P
625 >This option allows you to look at what services
626 are available on a server. You use it as <B
630 > and a list should appear. The <VAR
634 > option may be useful if your NetBIOS names don't
635 match your TCP/IP DNS host names or if you are trying to reach a
636 host on another network. </P
639 >-t terminal code</DT
642 >This option tells <B
646 filenames coming from the remote server. Usually Asian language
647 multibyte UNIX implementations use different character sets than
648 SMB/CIFS servers (<SPAN
660 > for example). Setting this parameter will let
664 > convert between the UNIX filenames and
665 the SMB filenames correctly. This option has not been seriously tested
666 and may have some problems. </P
668 >The terminal codes include CWsjis, CWeuc, CWjis7, CWjis8,
669 CWjunet, CWhex, CWcap. This is not a complete list, check the Samba
670 source code for the complete list. </P
676 >This option changes the transmit/send buffer
677 size when getting or putting a file from/to the server. The default
678 is 65520 bytes. Setting this value smaller (to 1200 bytes) has been
679 observed to speed up file transfers to and from a Win9x server.
686 >Override the default workgroup (domain) specified
687 in the workgroup parameter of the <SPAN
690 CLASS="REFENTRYTITLE"
693 > file for this connection. This may be
694 needed to connect to some servers. </P
700 >smbclient may be used to create <B
704 > compatible backups of all the files on an SMB/CIFS
705 share. The secondary tar flags that can be given to this option
715 > - Create a tar file on UNIX.
716 Must be followed by the name of a tar file, tape device
717 or "-" for standard output. If using standard output you must
718 turn the log level to its lowest value -d0 to avoid corrupting
719 your tar file. This flag is mutually exclusive with the
730 > - Extract (restore) a local
731 tar file back to a share. Unless the -D option is given, the tar
732 files will be restored from the top level of the share. Must be
733 followed by the name of the tar file, device or "-" for standard
734 input. Mutually exclusive with the <VAR
738 Restored files have their creation times (mtime) set to the
739 date saved in the tar file. Directories currently do not get
740 their creation dates restored properly. </P
747 > - Include files and directories.
748 Is the default behavior when filenames are specified above. Causes
749 tar files to be included in an extract or create (and therefore
750 everything else to be excluded). See example below. Filename globbing
751 works in one of two ways. See r below. </P
758 > - Exclude files and directories.
759 Causes tar files to be excluded from an extract or create. See
760 example below. Filename globbing works in one of two ways now.
771 > - Blocksize. Must be followed
772 by a valid (greater than zero) blocksize. Causes tar file to be
773 written out in blocksize*TBLOCK (usually 512 byte) blocks.
781 > - Incremental. Only back up
782 files that have the archive bit set. Useful only with the
793 > - Quiet. Keeps tar from printing
794 diagnostics as it works. This is the same as tarmode quiet.
802 > - Regular expression include
803 or exclude. Uses regular expression matching for
804 excluding or excluding files if compiled with HAVE_REGEX_H.
805 However this mode can be very slow. If not compiled with
806 HAVE_REGEX_H, does a limited wildcard match on '*' and '?'.
814 > - Newer than. Must be followed
815 by the name of a file whose date is compared against files found
816 on the share during a create. Only files newer than the file
817 specified are backed up to the tar file. Useful only with the
828 > - Set archive bit. Causes the
829 archive bit to be reset when a file is backed up. Useful with the
845 >Tar Long File Names</I
852 >'s tar option now supports long
853 file names both on backup and restore. However, the full path
854 name of the file must be less than 1024 bytes. Also, when
855 a tar archive is created, <B
858 >'s tar option places all
859 files in the archive with relative names, not absolute names.
870 >All file names can be given as DOS path names (with '\\'
871 as the component separator) or as UNIX path names (with '/' as
872 the component separator). </P
882 >Restore from tar file <TT
885 > into myshare on mypc
886 (no password on share). </P
890 >smbclient //mypc/yshare "" -N -Tx backup.tar
894 >Restore everything except <TT
902 >smbclient //mypc/myshare "" -N -TXx backup.tar
906 >Create a tar file of the files beneath <TT
913 >smbclient //mypc/myshare "" -N -Tc
914 backup.tar users/docs </B
917 >Create the same tar file as above, but now use
922 >smbclient //mypc/myshare "" -N -tc backup.tar
926 >Create a tar file of all the files and directories in
931 >smbclient //mypc/myshare "" -N -Tc backup.tar *
936 >-D initial directory</DT
939 >Change to initial directory before starting. Probably
940 only of any use with the tar -T option. </P
943 >-c command string</DT
946 >command string is a semicolon-separated list of
947 commands to be executed instead of prompting from stdin. <VAR
955 >This is particularly useful in scripts and for printing stdin
956 to the server, e.g. <B
965 > Try to authenticate with kerberos. Only useful in
966 an Active Directory environment.
980 >Once the client is running, the user is presented with
988 >The backslash ("\\") indicates the current working directory
989 on the server, and will change if the current working directory
992 >The prompt indicates that the client is ready and waiting to
993 carry out a user command. Each command is a single word, optionally
994 followed by parameters specific to that command. Command and parameters
995 are space-delimited unless these notes specifically
996 state otherwise. All commands are case-insensitive. Parameters to
997 commands may or may not be case sensitive, depending on the command.
1000 >You can specify file names which have spaces in them by quoting
1001 the name with double quotes, for example "a long file name". </P
1003 >Parameters shown in square brackets (e.g., "[parameter]") are
1004 optional. If not given, the command will use suitable defaults. Parameters
1005 shown in angle brackets (e.g., "<parameter>") are required.
1008 >Note that all commands operating on the server are actually
1009 performed by issuing a request to the server. Thus the behavior may
1010 vary from server to server, depending on how the server was implemented.
1013 >The commands available are given here in alphabetical order. </P
1017 CLASS="VARIABLELIST"
1026 > is specified, the ? command will display
1027 a brief informative message about the specified command. If no
1028 command is specified, a list of available commands will
1032 >! [shell command]</DT
1038 > is specified, the !
1039 command will execute a shell locally and run the specified shell
1040 command. If no command is specified, a local shell will be run.
1047 >The client will request that the server return
1048 the "alternate" name (the 8.3 name) for a file or directory.
1052 >cancel jobid0 [jobid1] ... [jobidN]</DT
1055 >The client will request that the server cancel
1056 the printjobs identified by the given numeric print job ids.
1060 >chmod file mode in octal</DT
1063 >This command depends on the server supporting the CIFS
1064 UNIX extensions and will fail if the server does not. The client requests that the server
1065 change the UNIX permissions to the given octal mode, in standard UNIX format.
1069 >chown file uid gid</DT
1072 >This command depends on the server supporting the CIFS
1073 UNIX extensions and will fail if the server does not. The client requests that the server
1074 change the UNIX user and group ownership to the given decimal values. Note there is
1075 currently no way to remotely look up the UNIX uid and gid values for a given name.
1076 This may be addressed in future versions of the CIFS UNIX extensions.
1080 >cd [directory name]</DT
1083 >If "directory name" is specified, the current
1084 working directory on the server will be changed to the directory
1085 specified. This operation will fail if for any reason the specified
1086 directory is inaccessible. </P
1088 >If no directory name is specified, the current working
1089 directory on the server will be reported. </P
1092 >del <mask></DT
1095 >The client will request that the server attempt
1096 to delete all files matching <VAR
1099 > from the current working
1100 directory on the server. </P
1103 >dir <mask></DT
1106 >A list of the files matching <VAR
1110 working directory on the server will be retrieved from the server
1117 >Terminate the connection with the server and exit
1118 from the program. </P
1121 >get <remote file name> [local file name]</DT
1124 >Copy the file called <TT
1126 >remote file name</TT
1128 the server to the machine running the client. If specified, name
1131 >local file name</TT
1132 >. Note that all transfers in
1136 > are binary. See also the
1137 lowercase command. </P
1143 >See the ? command above. </P
1146 >lcd [directory name]</DT
1151 >directory name</VAR
1152 > is specified, the current
1153 working directory on the local machine will be changed to
1154 the directory specified. This operation will fail if for any
1155 reason the specified directory is inaccessible. </P
1157 >If no directory name is specified, the name of the
1158 current working directory on the local machine will be reported.
1162 >link source destination</DT
1165 >This command depends on the server supporting the CIFS
1166 UNIX extensions and will fail if the server does not. The client requests that the server
1167 create a hard link between the source and destination files. The source file
1175 >Toggle lowercasing of filenames for the get and
1178 >When lowercasing is toggled ON, local filenames are converted
1179 to lowercase when using the get and mget commands. This is
1180 often useful when copying (say) MSDOS files from a server, because
1181 lowercase filenames are the norm on UNIX systems. </P
1184 >ls <mask></DT
1187 >See the dir command above. </P
1190 >mask <mask></DT
1193 >This command allows the user to set up a mask
1194 which will be used during recursive operation of the mget and
1197 >The masks specified to the mget and mput commands act as
1198 filters for directories rather than files when recursion is
1201 >The mask specified with the mask command is necessary
1202 to filter files within those directories. For example, if the
1203 mask specified in an mget command is "source*" and the mask
1204 specified with the mask command is "*.c" and recursion is
1205 toggled ON, the mget command will retrieve all files matching
1206 "*.c" in all directories below and including all directories
1207 matching "source*" in the current working directory. </P
1209 >Note that the value for mask defaults to blank (equivalent
1210 to "*") and remains so until the mask command is used to change it.
1211 It retains the most recently specified value indefinitely. To
1212 avoid unexpected results it would be wise to change the value of
1213 mask back to "*" after using the mget or mput commands. </P
1216 >md <directory name></DT
1219 >See the mkdir command. </P
1222 >mget <mask></DT
1225 >Copy all files matching <VAR
1228 > from the server to
1229 the machine running the client. </P
1234 > is interpreted differently during recursive
1235 operation and non-recursive operation - refer to the recurse and
1236 mask commands for more information. Note that all transfers in
1240 > are binary. See also the lowercase command. </P
1243 >mkdir <directory name></DT
1246 >Create a new directory on the server (user access
1247 privileges permitting) with the specified name. </P
1250 >mput <mask></DT
1253 >Copy all files matching <VAR
1256 > in the current working
1257 directory on the local machine to the current working directory on
1263 > is interpreted differently during recursive
1264 operation and non-recursive operation - refer to the recurse and mask
1265 commands for more information. Note that all transfers in <B
1272 >print <file name></DT
1275 >Print the specified file from the local machine
1276 through a printable service on the server. </P
1278 >See also the printmode command.</P
1281 >printmode <graphics or text></DT
1284 >Set the print mode to suit either binary data
1285 (such as graphical information) or text. Subsequent print
1286 commands will use the currently set print mode. </P
1292 >Toggle prompting for filenames during operation
1293 of the mget and mput commands. </P
1295 >When toggled ON, the user will be prompted to confirm
1296 the transfer of each file during these commands. When toggled
1297 OFF, all specified files will be transferred without prompting.
1301 >put <local file name> [remote file name]</DT
1304 >Copy the file called <TT
1306 >local file name</TT
1308 machine running the client to the server. If specified,
1309 name the remote copy <TT
1311 >remote file name</TT
1312 >. Note that all transfers
1316 > are binary. See also the lowercase command.
1323 >Displays the print queue, showing the job id,
1324 name, size and current status. </P
1330 >See the exit command. </P
1333 >rd <directory name></DT
1336 >See the rmdir command. </P
1342 >Toggle directory recursion for the commands mget
1345 >When toggled ON, these commands will process all directories
1346 in the source directory (i.e., the directory they are copying
1347 from ) and will recurse into any that match the mask specified
1348 to the command. Only files that match the mask specified using
1349 the mask command will be retrieved. See also the mask command.
1352 >When recursion is toggled OFF, only files from the current
1353 working directory on the source machine that match the mask specified
1354 to the mget or mput commands will be copied, and any mask specified
1355 using the mask command will be ignored. </P
1358 >rm <mask></DT
1361 >Remove all files matching <VAR
1365 working directory on the server. </P
1368 >rmdir <directory name></DT
1371 >Remove the specified directory (user access
1372 privileges permitting) from the server. </P
1375 >setmode <filename> <perm=[+|\-]rsha></DT
1378 >A version of the DOS attrib command to set
1379 file permissions. For example: </P
1383 >setmode myfile +r </B
1386 >would make myfile read only. </P
1389 >symlink source destination</DT
1392 >This command depends on the server supporting the CIFS
1393 UNIX extensions and will fail if the server does not. The client requests that the server
1394 create a symbolic hard link between the source and destination files. The source file
1395 must not exist. Note that the server will not create a link to any path that lies
1396 outside the currently connected share. This is enforced by the Samba server.
1400 >tar <c|x>[IXbgNa]</DT
1403 >Performs a tar operation - see the <VAR
1407 > command line option above. Behavior may be affected
1408 by the tarmode command (see below). Using g (incremental) and N
1409 (newer) will affect tarmode settings. Note that using the "-" option
1410 with tar x may not work - use the command line option instead.
1414 >blocksize <blocksize></DT
1417 >Blocksize. Must be followed by a valid (greater
1418 than zero) blocksize. Causes tar file to be written out in
1422 >*TBLOCK (usually 512 byte) blocks. </P
1425 >tarmode <full|inc|reset|noreset></DT
1428 >Changes tar's behavior with regard to archive
1429 bits. In full mode, tar will back up everything regardless of the
1430 archive bit setting (this is the default mode). In incremental mode,
1431 tar will only back up files with the archive bit set. In reset mode,
1432 tar will reset the archive bit on all files it backs up (implies
1433 read/write share). </P
1446 >Some servers are fussy about the case of supplied usernames,
1447 passwords, share names (AKA service names) and machine names.
1448 If you fail to connect try giving all parameters in uppercase.
1451 >It is often necessary to use the -n option when connecting
1452 to some types of servers. For example OS/2 LanManager insists
1453 on a valid NetBIOS name being used, so you need to supply a valid
1454 name that would be known to the server.</P
1456 >smbclient supports long file names where the server
1457 supports the LANMAN2 protocol or above. </P
1465 >ENVIRONMENT VARIABLES</H2
1471 username of the person using the client. This information is
1472 used only if the protocol level is high enough to support
1473 session-level passwords.</P
1479 the password of the person using the client. This information is
1480 used only if the protocol level is high enough to support
1481 session-level passwords. </P
1487 the path, executed with system(), which the client should connect
1488 to instead of connecting to a server. This functionality is primarily
1489 intended as a development aid, and works best when using a LMHOSTS
1500 >The location of the client program is a matter for
1501 individual system administrators. The following are thus
1502 suggestions only. </P
1504 >It is recommended that the smbclient software be installed
1507 >/usr/local/samba/bin/</TT
1510 > /usr/samba/bin/</TT
1511 > directory, this directory readable
1512 by all, writeable only by root. The client program itself should
1513 be executable by all. The client should <SPAN
1520 setuid or setgid! </P
1522 >The client log files should be put in a directory readable
1523 and writeable only by the user. </P
1525 >To test the client, you will need to know the name of a
1526 running SMB/CIFS server. It is possible to run <SPAN
1527 CLASS="CITEREFENTRY"
1529 CLASS="REFENTRYTITLE"
1532 > as an ordinary user - running that server as a daemon
1533 on a user-accessible port (typically any port number over 1024)
1534 would provide a suitable test server. </P
1544 >Most diagnostics issued by the client are logged in a
1545 specified log file. The log file name is specified at compile time,
1546 but may be overridden on the command line. </P
1548 >The number and nature of diagnostics available depends
1549 on the debug level used by the client. If you have problems,
1550 set the debug level to 3 and peruse the log files. </P
1560 >This man page is correct for version 2.2 of the Samba suite.</P
1570 >The original Samba software and related utilities
1571 were created by Andrew Tridgell. Samba is now developed
1572 by the Samba Team as an Open Source project similar
1573 to the way the Linux kernel is developed.</P
1575 >The original Samba man pages were written by Karl Auer.
1576 The man page sources were converted to YODL format (another
1577 excellent piece of Open Source software, available at <A
1578 HREF="ftp://ftp.icce.rug.nl/pub/unix/"
1580 > ftp://ftp.icce.rug.nl/pub/unix/</A
1581 >) and updated for the Samba 2.0
1582 release by Jeremy Allison. The conversion to DocBook for
1583 Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0
1584 was done by Alexander Bokovoy.</P