mirror of
https://github.com/samba-team/samba.git
synced 2025-03-05 20:58:40 +03:00
- added example config section to winbindd man page
- reran yodldocs with newer version of yodl (This used to be commit faa3f49430775fd1bd327237f369f7b5df6fc0c6)
This commit is contained in:
Andrew Tridgell
parent
30129251f2
commit
69a26b387b
@ -3,9 +3,10 @@
|
||||
|
||||
|
||||
|
||||
|
||||
<html><head><title>Joining an NT Domain with Samba 2.0</title>
|
||||
|
||||
<link rev="made" href="mailto:samba-bugs@samba.org">
|
||||
<link rev="made" href="mailto:samba@samba.org">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
@ -15,79 +16,79 @@
|
||||
<h2>Jeremy Allison, Samba Team</h2>
|
||||
<h2>7th October 1999</h2>
|
||||
|
||||
|
||||
<h1>Table of Contents </h1><p></p>
|
||||
|
||||
<p><hr><p><br>
|
||||
<p><br><center>Joining an NT Domain with Samba 2.0 </center>
|
||||
<p><center>Joining an NT Domain with Samba 2.0 </center>
|
||||
<center>----------------------------------- </center>
|
||||
<p><br>In order for a Samba-2 server to join an NT domain, you must first add
|
||||
<p>In order for a Samba-2 server to join an NT domain, you must first add
|
||||
the NetBIOS name of the Samba server to the NT domain on the PDC using
|
||||
Server Manager for Domains. This creates the machine account in the
|
||||
domain (PDC) SAM. Note that you should add the Samba server as a "Windows
|
||||
NT Workstation or Server", <em>NOT</em> as a Primary or backup domain controller.
|
||||
<p><br>Assume you have a Samba-2 server with a NetBIOS name of <code>SERV1</code> and are
|
||||
<p>Assume you have a Samba-2 server with a NetBIOS name of <code>SERV1</code> and are
|
||||
joining an NT domain called <code>DOM</code>, which has a PDC with a NetBIOS name
|
||||
of <code>DOMPDC</code> and two backup domain controllers with NetBIOS names <code>DOMBDC1</code>
|
||||
and <code>DOMBDC2</code>.
|
||||
<p><br>In order to join the domain, first stop all Samba daemons and run the
|
||||
<p>In order to join the domain, first stop all Samba daemons and run the
|
||||
command
|
||||
<p><br><code>smbpasswd -j DOM -r DOMPDC</code>
|
||||
<p><br>as we are joining the domain DOM and the PDC for that domain (the only
|
||||
machine that has write access to the domain SAM database). If this is
|
||||
<p><code>smbpasswd -j DOM -r DOMPDC</code>
|
||||
<p>as we are joining the domain DOM and the PDC for that domain (the only
|
||||
machine that has write access to the domain SAM database) is DOMPDC. If this is
|
||||
successful you will see the message:
|
||||
<p><br><code>smbpasswd: Joined domain DOM.</code>
|
||||
<p><br>in your terminal window. See the <a href="smbpasswd.8.html"><strong>smbpasswd</strong></a>
|
||||
<p><code>smbpasswd: Joined domain DOM.</code>
|
||||
<p>in your terminal window. See the <a href="smbpasswd.8.html"><strong>smbpasswd</strong></a>
|
||||
man page for more details.
|
||||
<p><br>This command goes through the machine account password change
|
||||
<p>This command goes through the machine account password change
|
||||
protocol, then writes the new (random) machine account password for
|
||||
this Samba server into the a file in the same directory in which an
|
||||
smbpasswd file would be stored (normally :
|
||||
<p><br><code>/usr/local/samba/private</code>
|
||||
<p><br>The filename looks like this:
|
||||
<p><br><code><NT DOMAIN NAME>.<Samba Server Name>.mac</code>
|
||||
<p><br>The <code>.mac</code> suffix stands for machine account password file. So in
|
||||
this Samba server into a file in the same directory in which an
|
||||
smbpasswd file would be stored - normally :
|
||||
<p><code>/usr/local/samba/private</code>
|
||||
<p>The filename looks like this:
|
||||
<p><code><NT DOMAIN NAME>.<Samba Server Name>.mac</code>
|
||||
<p>The <code>.mac</code> suffix stands for machine account password file. So in
|
||||
our example above, the file would be called:
|
||||
<p><br><code>DOM.SERV1.mac</code>
|
||||
<p><br>This file is created and owned by root and is not readable by any
|
||||
<p><code>DOM.SERV1.mac</code>
|
||||
<p>This file is created and owned by root and is not readable by any
|
||||
other user. It is the key to the domain-level security for your
|
||||
system, and should be treated as carefully as a shadow password file.
|
||||
<p><br>Now, before restarting the Samba daemons you must edit your
|
||||
<p>Now, before restarting the Samba daemons you must edit your
|
||||
<a href="smb.conf.5.html"><strong>smb.conf</strong></a> file to tell Samba it should now
|
||||
use domain security.
|
||||
<p><br>Change (or add) your
|
||||
<p><br><a href="smb.conf.5.html#security"><strong>"security ="</strong></a>
|
||||
<p><br>line in the <a href="smb.conf.5.html#global"><strong>[global]</strong></a> section of your
|
||||
<p>Change (or add) your
|
||||
<p><a href="smb.conf.5.html#security"><strong>"security ="</strong></a>
|
||||
<p>line in the <a href="smb.conf.5.html#global"><strong>[global]</strong></a> section of your
|
||||
<a href="smb.conf.5.html"><strong>smb.conf</strong></a> to read:
|
||||
<p><br><code>security = domain</code>
|
||||
<p><br>Next change the
|
||||
<p><br><a href="smb.conf.5.html#workgroup"><strong>"workgroup ="</strong></a>
|
||||
<p><br>line in the <a href="smb.conf.5.html#global"><strong>[global]</strong></a> section to read:
|
||||
<p><br><code>workgroup = DOM</code>
|
||||
<p><br>as this is the name of the domain we are joining.
|
||||
<p><br>You must also have the parameter <a href="smb.conf.5.html#encryptpasswords"><strong>"encrypt passwords"</strong></a>
|
||||
<p><code>security = domain</code>
|
||||
<p>Next change the
|
||||
<p><a href="smb.conf.5.html#workgroup"><strong>"workgroup ="</strong></a>
|
||||
<p>line in the <a href="smb.conf.5.html#global"><strong>[global]</strong></a> section to read:
|
||||
<p><code>workgroup = DOM</code>
|
||||
<p>as this is the name of the domain we are joining.
|
||||
<p>You must also have the parameter <a href="smb.conf.5.html#encryptpasswords"><strong>"encrypt passwords"</strong></a>
|
||||
set to <code>"yes"</code> in order for your users to authenticate to the
|
||||
NT PDC.
|
||||
<p><br>Finally, add (or modify) a:
|
||||
<p><br><a href="smb.conf.5.html#passwordserver"><strong>"password server ="</strong></a>
|
||||
<p><br>line in the <a href="smb.conf.5.html#global"><strong>[global]</strong></a> section to read:
|
||||
<p><br><code>password server = DOMPDC DOMBDC1 DOMBDC2</code>
|
||||
<p><br>These are the primary and backup domain controllers Samba will attempt
|
||||
<p>Finally, add (or modify) a:
|
||||
<p><a href="smb.conf.5.html#passwordserver"><strong>"password server ="</strong></a>
|
||||
<p>line in the <a href="smb.conf.5.html#global"><strong>[global]</strong></a> section to read:
|
||||
<p><code>password server = DOMPDC DOMBDC1 DOMBDC2</code>
|
||||
<p>These are the primary and backup domain controllers Samba will attempt
|
||||
to contact in order to authenticate users. Samba will try to contact
|
||||
each of these servers in order, so you may want to rearrange this list
|
||||
in order to spread out the authentication load among domain
|
||||
controllers.
|
||||
<p><br>Alternatively, if you want smbd to automatically determine the
|
||||
<p>Alternatively, if you want smbd to automatically determine the
|
||||
list of Domain controllers to use for authentication, you may set this line to be :
|
||||
<p><br><code>password server = *</code>
|
||||
<p><br>This method, which is new in Samba 2.0.6 and above, allows Samba
|
||||
<p><code>password server = *</code>
|
||||
<p>This method, which is new in Samba 2.0.6 and above, allows Samba
|
||||
to use exactly the same mechanism that NT does. This method either broadcasts or
|
||||
uses a WINS database in order to find domain controllers to
|
||||
authenticate against.
|
||||
<p><br>Finally, restart your Samba daemons and get ready for clients to begin
|
||||
<p>Finally, restart your Samba daemons and get ready for clients to begin
|
||||
using domain security!
|
||||
<p><br><center>Why is this better than security = server? </center>
|
||||
<p><center>Why is this better than security = server? </center>
|
||||
<center>------------------------------------------ </center>
|
||||
<p><br>Currently, domain security in Samba doesn't free you from having to
|
||||
<p>Currently, domain security in Samba doesn't free you from having to
|
||||
create local Unix users to represent the users attaching to your
|
||||
server. This means that if domain user <code>DOM\fred</code> attaches to your
|
||||
domain security Samba server, there needs to be a local Unix user fred
|
||||
@ -95,14 +96,14 @@ to represent that user in the Unix filesystem. This is very similar to
|
||||
the older Samba security mode <a href="smb.conf.5.html#securityequalserver"><strong>"security=server"</strong></a>, where Samba would pass
|
||||
through the authentication request to a Windows NT server in the same
|
||||
way as a Windows 95 or Windows 98 server would.
|
||||
<p><br>The advantage to domain-level security is that the authentication in
|
||||
<p>The advantage to domain-level security is that the authentication in
|
||||
domain-level security is passed down the authenticated RPC channel in
|
||||
exactly the same way that an NT server would do it. This means Samba
|
||||
servers now participate in domain trust relationships in exactly the
|
||||
same way NT servers do (i.e., you can add Samba servers into a
|
||||
resource domain and have the authentication passed on from a resource
|
||||
domain PDC to an account domain PDC.
|
||||
<p><br>In addition, with <a href="smb.conf.5.html#securityequalserver"><strong>"security=server"</strong></a> every Samba daemon on a
|
||||
<p>In addition, with <a href="smb.conf.5.html#securityequalserver"><strong>"security=server"</strong></a> every Samba daemon on a
|
||||
server has to keep a connection open to the authenticating server for
|
||||
as long as that daemon lasts. This can drain the connection resources
|
||||
on a Microsoft NT server and cause it to run out of available
|
||||
@ -110,7 +111,7 @@ connections. With <a href="smb.conf.5.html#securityequaldomain"><strong>"securit
|
||||
daemons connect to the PDC/BDC only for as long as is necessary to
|
||||
authenticate the user, and then drop the connection, thus conserving
|
||||
PDC connection resources.
|
||||
<p><br>And finally, acting in the same manner as an NT server authenticating
|
||||
<p>And finally, acting in the same manner as an NT server authenticating
|
||||
to a PDC means that as part of the authentication reply, the Samba
|
||||
server gets the user identification information such as the user SID,
|
||||
the list of NT groups the user belongs to, etc. All this information
|
||||
@ -120,7 +121,7 @@ users will be necessary, and Samba will generate Unix uids and gids
|
||||
from the information passed back from the PDC when a user is
|
||||
authenticated, making a Samba server truly plug and play in an NT
|
||||
domain environment. Watch for this code soon.
|
||||
<p><br><em>NOTE:</em> Much of the text of this document was first published in the
|
||||
<p><em>NOTE:</em> Much of the text of this document was first published in the
|
||||
Web magazine <a href="http://www.linuxworld.com"><strong>"LinuxWorld"</strong></a> as the article <a href="http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html"><strong>"Doing the NIS/NT Samba"</strong></a>.
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -3,9 +3,10 @@
|
||||
|
||||
|
||||
|
||||
|
||||
<html><head><title>lmhosts (5)</title>
|
||||
|
||||
<link rev="made" href="mailto:samba-bugs@samba.org">
|
||||
<link rev="made" href="mailto:samba@samba.org">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
@ -15,79 +16,78 @@
|
||||
<h2>Samba</h2>
|
||||
<h2>23 Oct 1998</h2>
|
||||
|
||||
|
||||
|
||||
|
||||
<p><br><a name="NAME"></a>
|
||||
<p><a name="NAME"></a>
|
||||
<h2>NAME</h2>
|
||||
lmhosts - The Samba NetBIOS hosts file
|
||||
<p><br><a name="SYNOPSIS"></a>
|
||||
<p><a name="SYNOPSIS"></a>
|
||||
<h2>SYNOPSIS</h2>
|
||||
|
||||
<p><br>lmhosts is the <strong>Samba</strong> NetBIOS name to IP address mapping file.
|
||||
<p><br><a name="DESCRIPTION"></a>
|
||||
<p>lmhosts is the <strong>Samba</strong> NetBIOS name to IP address mapping file.
|
||||
<p><a name="DESCRIPTION"></a>
|
||||
<h2>DESCRIPTION</h2>
|
||||
|
||||
<p><br>This file is part of the <strong>Samba</strong> suite.
|
||||
<p><br><strong>lmhosts</strong> is the <strong>Samba</strong> NetBIOS name to IP address mapping file. It
|
||||
<p>This file is part of the <strong>Samba</strong> suite.
|
||||
<p><strong>lmhosts</strong> is the <strong>Samba</strong> NetBIOS name to IP address mapping file. It
|
||||
is very similar to the <strong>/etc/hosts</strong> file format, except that the
|
||||
hostname component must correspond to the NetBIOS naming format.
|
||||
<p><br><a name="FILEFORMAT"></a>
|
||||
<p><a name="FILEFORMAT"></a>
|
||||
<h2>FILE FORMAT</h2>
|
||||
|
||||
<p><br>It is an ASCII file containing one line for NetBIOS name. The two
|
||||
<p>It is an ASCII file containing one line for NetBIOS name. The two
|
||||
fields on each line are separated from each other by white space. Any
|
||||
entry beginning with # is ignored. Each line in the lmhosts file
|
||||
contains the following information :
|
||||
<p><br><ul>
|
||||
<p><br><li > <strong>IP Address</strong> - in dotted decimal format.
|
||||
<p><br><li > <strong>NetBIOS Name</strong> - This name format is a maximum fifteen
|
||||
<p><dl>
|
||||
<p><li > <strong>IP Address</strong> - in dotted decimal format.
|
||||
<p><li > <strong>NetBIOS Name</strong> - This name format is a maximum fifteen
|
||||
character host name, with an optional trailing <code>'#'</code> character
|
||||
followed by the NetBIOS name type as two hexadecimal digits.
|
||||
<p><br>If the trailing <code>'#'</code> is omitted then the given IP address will be
|
||||
<p>If the trailing <code>'#'</code> is omitted then the given IP address will be
|
||||
returned for all names that match the given name, whatever the NetBIOS
|
||||
name type in the lookup.
|
||||
<p><br></ul>
|
||||
<p><br>An example follows :
|
||||
<p><br># <br>
|
||||
<p></dl>
|
||||
<p>An example follows :
|
||||
<p># <br>
|
||||
# Sample Samba lmhosts file. <br>
|
||||
# <br>
|
||||
192.9.200.1 TESTPC <br>
|
||||
192.9.200.20 NTSERVER#20 <br>
|
||||
192.9.200.21 SAMBASERVER <br>
|
||||
<p><br>Contains three IP to NetBIOS name mappings. The first and third will
|
||||
<p>Contains three IP to NetBIOS name mappings. The first and third will
|
||||
be returned for any queries for the names <code>"TESTPC"</code> and
|
||||
<code>"SAMBASERVER"</code> respectively, whatever the type component of the
|
||||
NetBIOS name requested.
|
||||
<p><br>The second mapping will be returned only when the <code>"0x20"</code> name type
|
||||
<p>The second mapping will be returned only when the <code>"0x20"</code> name type
|
||||
for a name <code>"NTSERVER"</code> is queried. Any other name type will not be
|
||||
resolved.
|
||||
<p><br>The default location of the <strong>lmhosts</strong> file is in the same directory
|
||||
<p>The default location of the <strong>lmhosts</strong> file is in the same directory
|
||||
as the <a href="smb.conf.html"><strong>smb.conf</strong></a> file.
|
||||
<p><br><a name="VERSION"></a>
|
||||
<p><a name="VERSION"></a>
|
||||
<h2>VERSION</h2>
|
||||
|
||||
<p><br>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><br><a name="SEEALSO"></a>
|
||||
<p>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><a name="SEEALSO"></a>
|
||||
<h2>SEE ALSO</h2>
|
||||
|
||||
<p><br><a href="smb.conf.5.html#nameresolveorder"><strong>smb.conf (5)</strong></a>,
|
||||
<p><a href="smb.conf.5.html#nameresolveorder"><strong>smb.conf (5)</strong></a>,
|
||||
<a href="smbclient.1.html#minusR"><strong>smbclient (1)</strong></a>,
|
||||
<a href="smbpasswd.8.html#minusR"><strong>smbpasswd (8)</strong></a>, <a href="samba.7.html"><strong>samba (7)</strong></a>.
|
||||
<p><br><a name="AUTHOR"></a>
|
||||
<p><a name="AUTHOR"></a>
|
||||
<h2>AUTHOR</h2>
|
||||
|
||||
<p><br>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed
|
||||
<p>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed.
|
||||
<p><br>The original Samba man pages were written by Karl Auer. The man page
|
||||
<p>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
|
||||
<a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>)
|
||||
and updated for the Samba2.0 release by Jeremy Allison.
|
||||
<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>.
|
||||
<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
|
||||
<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>.
|
||||
<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
comments etc.
|
||||
</body>
|
||||
|
||||
@ -3,9 +3,10 @@
|
||||
|
||||
|
||||
|
||||
|
||||
<html><head><title>make_smbcodepage (1)</title>
|
||||
|
||||
<link rev="made" href="mailto:samba-bugs@samba.org">
|
||||
<link rev="made" href="mailto:samba@samba.org">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
@ -15,45 +16,44 @@
|
||||
<h2>Samba</h2>
|
||||
<h2>23 Oct 1998</h2>
|
||||
|
||||
|
||||
|
||||
|
||||
<p><br><a name="NAME"></a>
|
||||
<p><a name="NAME"></a>
|
||||
<h2>NAME</h2>
|
||||
make_codepage - Construct a codepage file for Samba
|
||||
<p><br><a name="SYNOPSIS"></a>
|
||||
<p><a name="SYNOPSIS"></a>
|
||||
<h2>SYNOPSIS</h2>
|
||||
|
||||
<p><br><strong>make_smbcodepage</strong> [<a href="make_smbcodepage.1.html#cord">c|d</a>] <a href="make_smbcodepage.1.html#codepage">codepage</a> <a href="make_smbcodepage.1.html#inputfile">inputfile</a> <a href="make_smbcodepage.1.html#outputfile">outputfile</a>
|
||||
<p><br><a name="DESCRIPTION"></a>
|
||||
<p><strong>make_smbcodepage</strong> [<a href="make_smbcodepage.1.html#cord">c|d</a>] <a href="make_smbcodepage.1.html#codepage">codepage</a> <a href="make_smbcodepage.1.html#inputfile">inputfile</a> <a href="make_smbcodepage.1.html#outputfile">outputfile</a>
|
||||
<p><a name="DESCRIPTION"></a>
|
||||
<h2>DESCRIPTION</h2>
|
||||
|
||||
<p><br>This program is part of the <strong>Samba</strong> suite.
|
||||
<p><br><strong>make_smbcodepage</strong> compiles or de-compiles codepage files for use
|
||||
<p>This program is part of the <strong>Samba</strong> suite.
|
||||
<p><strong>make_smbcodepage</strong> compiles or de-compiles codepage files for use
|
||||
with the internationalization features of Samba 2.0
|
||||
<p><br><a name="OPTIONS"></a>
|
||||
<p><a name="OPTIONS"></a>
|
||||
<h2>OPTIONS</h2>
|
||||
|
||||
<p><br><ul>
|
||||
<p><br><a name="cord"></a>
|
||||
<li><strong>c|d</strong> This tells <strong>make_smbcodepage</strong> if it is compiling (<strong>c</strong>) a text
|
||||
<p><dl>
|
||||
<p><a name="cord"></a>
|
||||
<p></p><dt><strong>c|d</strong><dd> This tells <strong>make_smbcodepage</strong> if it is compiling (<strong>c</strong>) a text
|
||||
format code page file to binary, or (<strong>d</strong>) de-compiling a binary codepage
|
||||
file to text.
|
||||
<p><br><a name="codepage"></a>
|
||||
<li><strong>codepage</strong> This is the codepage we are processing (a number, e.g. 850).
|
||||
<p><br><a name="inputfile"></a>
|
||||
<li><strong>inputfile</strong> This is the input file to process. In the '<strong>c</strong>' case this
|
||||
<p><a name="codepage"></a>
|
||||
<p></p><dt><strong>codepage</strong><dd> This is the codepage we are processing (a number, e.g. 850).
|
||||
<p><a name="inputfile"></a>
|
||||
<p></p><dt><strong>inputfile</strong><dd> This is the input file to process. In the '<strong>c</strong>' case this
|
||||
will be a text codepage definition file such as the ones found in the
|
||||
Samba <em>source/codepages</em> directory. In the '<strong>d</strong>' case this will be the
|
||||
binary format codepage definition file normally found in the
|
||||
<em>lib/codepages</em> directory in the Samba install directory path.
|
||||
<p><br><a name="outputfile"></a>
|
||||
<li><strong>outputfile</strong> This is the output file to produce.
|
||||
<p><br></ul>
|
||||
<p><br><a name="SambaCodepageFiles"></a>
|
||||
<p><a name="outputfile"></a>
|
||||
<p></p><dt><strong>outputfile</strong><dd> This is the output file to produce.
|
||||
<p></dl>
|
||||
<p><a name="SambaCodepageFiles"></a>
|
||||
<h2>Samba Codepage Files</h2>
|
||||
|
||||
<p><br>A text Samba codepage definition file is a description that tells
|
||||
<p>A text Samba codepage definition file is a description that tells
|
||||
Samba how to map from upper to lower case for characters greater than
|
||||
ascii 127 in the specified DOS code page. Note that for certain DOS
|
||||
codepages (437 for example) mapping from lower to upper case may be
|
||||
@ -61,10 +61,10 @@ non-symmetrical. For example, in code page 437 lower case a acute maps to
|
||||
a plain upper case A when going from lower to upper case, but
|
||||
plain upper case A maps to plain lower case a when lower casing a
|
||||
character.
|
||||
<p><br>A binary Samba codepage definition file is a binary representation of
|
||||
<p>A binary Samba codepage definition file is a binary representation of
|
||||
the same information, including a value that specifies what codepage
|
||||
this file is describing.
|
||||
<p><br>As Samba does not yet use UNICODE (current for Samba version 2.0) you
|
||||
<p>As Samba does not yet use UNICODE (current for Samba version 2.0) you
|
||||
must specify the client code page that your DOS and Windows clients
|
||||
are using if you wish to have case insensitivity done correctly for
|
||||
your particular language. The default codepage Samba uses is 850
|
||||
@ -74,70 +74,70 @@ provided in the Samba distribution for codepages 437 (USA), 737
|
||||
866 (Cyrillic), 932 (Kanji SJIS), 936 (Simplified Chinese), 949
|
||||
(Hangul) and 950 (Traditional Chinese). Users are encouraged to write
|
||||
text codepage definition files for their own code pages and donate
|
||||
them to <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. All codepage files in the
|
||||
them to <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. All codepage files in the
|
||||
Samba <em>source/codepages</em> directory are compiled and installed when a
|
||||
<em>'make install'</em> command is issued there.
|
||||
<p><br>The client codepage used by the <a href="smbd.8.html"><strong>smbd</strong></a> server is
|
||||
<p>The client codepage used by the <a href="smbd.8.html"><strong>smbd</strong></a> server is
|
||||
configured using the <a href="smb.conf.5.html#clientcodepage"><strong>client code
|
||||
page</strong></a> parameter in the
|
||||
<a href="smb.conf.5.html"><strong>smb.conf</strong></a> file.
|
||||
<p><br><a name="FILES"></a>
|
||||
<p><a name="FILES"></a>
|
||||
<h2>FILES</h2>
|
||||
|
||||
<p><br><strong>codepage_def.<codepage></strong>
|
||||
<p><br>These are the input (text) codepage files provided in the Samba
|
||||
<p><strong>codepage_def.<codepage></strong>
|
||||
<p>These are the input (text) codepage files provided in the Samba
|
||||
<em>source/codepages</em> directory.
|
||||
<p><br>A text codepage definition file consists of multiple lines
|
||||
<p>A text codepage definition file consists of multiple lines
|
||||
containing four fields. These fields are :
|
||||
<p><br><ul>
|
||||
<p><br><li > <strong>lower</strong>: which is the (hex) lower case character mapped on this
|
||||
<p><dl>
|
||||
<p><li > <strong>lower</strong>: which is the (hex) lower case character mapped on this
|
||||
line.
|
||||
<p><br><li > <strong>upper</strong>: which is the (hex) upper case character that the lower
|
||||
<p><li > <strong>upper</strong>: which is the (hex) upper case character that the lower
|
||||
case character will map to.
|
||||
<p><br><li > <strong>map upper to lower</strong> which is a boolean value (put either True
|
||||
<p><li > <strong>map upper to lower</strong> which is a boolean value (put either True
|
||||
or False here) which tells Samba if it is to map the given upper case
|
||||
character to the given lower case character when lower casing a
|
||||
filename.
|
||||
<p><br><li > <strong>map lower to upper</strong> which is a boolean value (put either True
|
||||
<p><li > <strong>map lower to upper</strong> which is a boolean value (put either True
|
||||
or False here) which tells Samba if it is to map the given lower case
|
||||
character to the given upper case character when upper casing a
|
||||
filename.
|
||||
<p><br></ul>
|
||||
<p><br><strong>codepage.<codepage></strong> These are the output (binary) codepage files
|
||||
<p></dl>
|
||||
<p><strong>codepage.<codepage></strong> These are the output (binary) codepage files
|
||||
produced and placed in the Samba destination <em>lib/codepage</em>
|
||||
directory.
|
||||
<p><br><a name="INSTALLATION"></a>
|
||||
<p><a name="INSTALLATION"></a>
|
||||
<h2>INSTALLATION</h2>
|
||||
|
||||
<p><br>The location of the server and its support files is a matter for
|
||||
<p>The location of the server and its support files is a matter for
|
||||
individual system administrators. The following are thus suggestions
|
||||
only.
|
||||
<p><br>It is recommended that the <strong>make_smbcodepage</strong> program be installed
|
||||
<p>It is recommended that the <strong>make_smbcodepage</strong> program be installed
|
||||
under the <em>/usr/local/samba</em> hierarchy, in a directory readable by
|
||||
all, writeable only by root. The program itself should be executable
|
||||
by all. The program should NOT be setuid or setgid!
|
||||
<p><br><a name="VERSION"></a>
|
||||
<p><a name="VERSION"></a>
|
||||
<h2>VERSION</h2>
|
||||
|
||||
<p><br>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><br><a name="SEEALSO"></a>
|
||||
<p>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><a name="SEEALSO"></a>
|
||||
<h2>SEE ALSO</h2>
|
||||
|
||||
<p><br><a href="smb.conf.5.html"><strong>smb.conf(5)</strong></a>, <a href="smbd.8.html"><strong>smbd (8)</strong></a>
|
||||
<p><br><a name="AUTHOR"></a>
|
||||
<p><a href="smb.conf.5.html"><strong>smb.conf(5)</strong></a>, <a href="smbd.8.html"><strong>smbd (8)</strong></a>
|
||||
<p><a name="AUTHOR"></a>
|
||||
<h2>AUTHOR</h2>
|
||||
|
||||
<p><br>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed
|
||||
<p>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed.
|
||||
<p><br>The original Samba man pages were written by Karl Auer. The man page
|
||||
<p>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
|
||||
<a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>)
|
||||
and updated for the Samba2.0 release by Jeremy Allison.
|
||||
<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>.
|
||||
<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
|
||||
<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>.
|
||||
<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
comments etc.
|
||||
</body>
|
||||
|
||||
@ -3,9 +3,10 @@
|
||||
|
||||
|
||||
|
||||
|
||||
<html><head><title>nmbd</title>
|
||||
|
||||
<link rev="made" href="mailto:samba-bugs@samba.org">
|
||||
<link rev="made" href="mailto:samba@samba.org">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
@ -15,30 +16,29 @@
|
||||
<h2>Samba</h2>
|
||||
<h2>23 Oct 1998</h2>
|
||||
|
||||
|
||||
|
||||
|
||||
<p><br><a name="NAME"></a>
|
||||
<p><a name="NAME"></a>
|
||||
<h2>NAME</h2>
|
||||
nmbd - NetBIOS name server to provide NetBIOS over IP
|
||||
naming services to clients
|
||||
<p><br><a name="SYNOPSIS"></a>
|
||||
<p><a name="SYNOPSIS"></a>
|
||||
<h2>SYNOPSIS</h2>
|
||||
|
||||
<p><br><strong>nmbd</strong> [<a href="nmbd.8.html#minusD">-D</a>] [<a href="nmbd.8.html#minusa">-a</a>] [<a href="nmbd.8.html#minuso">-o</a>] [<a href="nmbd.8.html#minush">-h</a>] [<a href="nmbd.8.html#minusV">-V</a>] [<a href="nmbd.8.html#minusH">-H lmhosts file</a>] [<a href="nmbd.8.html#minusd">-d debuglevel</a>] [<a href="nmbd.8.html#minusl">-l log file basename</a>] [<a href="nmbd.8.html#minusn">-n primary NetBIOS name</a>] [<a href="nmbd.8.html#minusp">-p port number</a>] [<a href="nmbd.8.html#minuss">-s configuration file</a>] [<a href="nmbd.8.html#minusi">-i NetBIOS scope</a>]
|
||||
<p><br><a name="DESCRIPTION"></a>
|
||||
<p><strong>nmbd</strong> [<a href="nmbd.8.html#minusD">-D</a>] [<a href="nmbd.8.html#minusa">-a</a>] [<a href="nmbd.8.html#minuso">-o</a>] [<a href="nmbd.8.html#minush">-h</a>] [<a href="nmbd.8.html#minusV">-V</a>] [<a href="nmbd.8.html#minusH">-H lmhosts file</a>] [<a href="nmbd.8.html#minusd">-d debuglevel</a>] [<a href="nmbd.8.html#minusl">-l log file basename</a>] [<a href="nmbd.8.html#minusn">-n primary NetBIOS name</a>] [<a href="nmbd.8.html#minusp">-p port number</a>] [<a href="nmbd.8.html#minuss">-s configuration file</a>]
|
||||
<p><a name="DESCRIPTION"></a>
|
||||
<h2>DESCRIPTION</h2>
|
||||
|
||||
<p><br>This program is part of the <strong>Samba</strong> suite.
|
||||
<p><br><strong>nmbd</strong> is a server that understands and can reply to NetBIOS over IP
|
||||
<p>This program is part of the <strong>Samba</strong> suite.
|
||||
<p><strong>nmbd</strong> is a server that understands and can reply to NetBIOS over IP
|
||||
name service requests, like those produced by SMBD/CIFS clients such
|
||||
as Windows 95/98, Windows NT and LanManager clients. It also
|
||||
participates in the browsing protocols which make up the Windows
|
||||
"Network Neighborhood" view.
|
||||
<p><br>SMB/CIFS clients, when they start up, may wish to locate an SMB/CIFS
|
||||
<p>SMB/CIFS clients, when they start up, may wish to locate an SMB/CIFS
|
||||
server. That is, they wish to know what IP number a specified host is
|
||||
using.
|
||||
<p><br>Amongst other services, <strong>nmbd</strong> will listen for such requests,
|
||||
<p>Amongst other services, <strong>nmbd</strong> will listen for such requests,
|
||||
and if its own NetBIOS name is specified it will respond with the IP
|
||||
number of the host it is running on. Its "own NetBIOS name" is by
|
||||
default the primary DNS name of the host it is running on, but this
|
||||
@ -46,37 +46,37 @@ can be overridden with the <strong>-n</strong> option (see <a href="nmbd.8.html#
|
||||
<strong>nmbd</strong> will reply to broadcast queries for its own name(s). Additional
|
||||
names for <strong>nmbd</strong> to respond on can be set via parameters in the
|
||||
<a href="smb.conf.5.html"><strong>smb.conf(5)</strong></a> configuration file.
|
||||
<p><br><strong>nmbd</strong> can also be used as a WINS (Windows Internet Name Server)
|
||||
<p><strong>nmbd</strong> can also be used as a WINS (Windows Internet Name Server)
|
||||
server. What this basically means is that it will act as a WINS
|
||||
database server, creating a database from name registration requests
|
||||
that it receives and replying to queries from clients for these names.
|
||||
<p><br>In addition, <strong>nmbd</strong> can act as a WINS proxy, relaying broadcast queries
|
||||
<p>In addition, <strong>nmbd</strong> can act as a WINS proxy, relaying broadcast queries
|
||||
from clients that do not understand how to talk the WINS protocol to a
|
||||
WIN server.
|
||||
<p><br><a name="OPTIONS"></a>
|
||||
<p><a name="OPTIONS"></a>
|
||||
<h2>OPTIONS</h2>
|
||||
|
||||
<p><br><ul>
|
||||
<p><br><a name="minusD"></a>
|
||||
<li><strong><strong>-D</strong></strong> If specified, this parameter causes <strong>nmbd</strong> to operate
|
||||
<p><dl>
|
||||
<p><a name="minusD"></a>
|
||||
<p></p><dt><strong><strong>-D</strong></strong><dd> If specified, this parameter causes <strong>nmbd</strong> to operate
|
||||
as a daemon. That is, it detaches itself and runs in the background,
|
||||
fielding requests on the appropriate port. By default, <strong>nmbd</strong> will
|
||||
NOT operate as a daemon. nmbd can also be operated from the inetd
|
||||
meta-daemon, although this is not recommended.
|
||||
<p><br><a name="minusa"></a>
|
||||
<li><strong><strong>-a</strong></strong> If this parameter is specified, each new connection will
|
||||
<p><a name="minusa"></a>
|
||||
<p></p><dt><strong><strong>-a</strong></strong><dd> If this parameter is specified, each new connection will
|
||||
append log messages to the log file. This is the default.
|
||||
<p><br><a name="minuso"></a>
|
||||
<li><strong><strong>-o</strong></strong> If this parameter is specified, the log files will be
|
||||
<p><a name="minuso"></a>
|
||||
<p></p><dt><strong><strong>-o</strong></strong><dd> If this parameter is specified, the log files will be
|
||||
overwritten when opened. By default, the log files will be appended
|
||||
to.
|
||||
<p><br><a name="minush"></a>
|
||||
<li><strong><strong>-h</strong></strong> Prints the help information (usage) for <strong>nmbd</strong>.
|
||||
<p><br><a name="minusV"></a>
|
||||
<li><strong><strong>-V</strong></strong> Prints the version number for <strong>nmbd</strong>.
|
||||
<p><br><a name="minusH"></a>
|
||||
<li><strong><strong>-H filename</strong></strong> NetBIOS lmhosts file.
|
||||
<p><br>The lmhosts file is a list of NetBIOS names to IP addresses that is
|
||||
<p><a name="minush"></a>
|
||||
<p></p><dt><strong><strong>-h</strong></strong><dd> Prints the help information (usage) for <strong>nmbd</strong>.
|
||||
<p><a name="minusV"></a>
|
||||
<p></p><dt><strong><strong>-V</strong></strong><dd> Prints the version number for <strong>nmbd</strong>.
|
||||
<p><a name="minusH"></a>
|
||||
<p></p><dt><strong><strong>-H filename</strong></strong><dd> NetBIOS lmhosts file.
|
||||
<p>The lmhosts file is a list of NetBIOS names to IP addresses that is
|
||||
loaded by the nmbd server and used via the name resolution mechanism
|
||||
<a href="smb.conf.5.html#nameresolveorder"><strong>name resolve order</strong></a> described in
|
||||
<a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> to resolve any
|
||||
@ -84,92 +84,85 @@ NetBIOS name queries needed by the server. Note that the contents of
|
||||
this file are <em>NOT</em> used by <strong>nmbd</strong> to answer any name queries. Adding
|
||||
a line to this file affects name NetBIOS resolution from this host
|
||||
<em>ONLY</em>.
|
||||
<p><br>The default path to this file is compiled into Samba as part of the
|
||||
<p>The default path to this file is compiled into Samba as part of the
|
||||
build process. Common defaults are <em>/usr/local/samba/lib/lmhosts</em>,
|
||||
<em>/usr/samba/lib/lmhosts</em> or <em>/etc/lmhosts</em>. See the
|
||||
<a href="lmhosts.5.html"><strong>lmhosts (5)</strong></a> man page for details on the contents of this file.
|
||||
<p><br><a name="minusd"></a>
|
||||
<li><strong><strong>-d debuglevel</strong></strong> debuglevel is an integer from 0 to 10.
|
||||
<p><br>The default value if this parameter is not specified is zero.
|
||||
<p><br>The higher this value, the more detail will be logged to the log files
|
||||
<p><a name="minusd"></a>
|
||||
<p></p><dt><strong><strong>-d debuglevel</strong></strong><dd> debuglevel is an integer from 0 to 10.
|
||||
<p>The default value if this parameter is not specified is zero.
|
||||
<p>The higher this value, the more detail will be logged to the log files
|
||||
about the activities of the server. 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.
|
||||
<p><br>Levels above 1 will generate considerable amounts of log data, and
|
||||
<p>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.
|
||||
<p><br>Note that specifying this parameter here will override the <a href="smb.conf.5.html#loglevel"><strong>log
|
||||
<p>Note that specifying this parameter here will override the <a href="smb.conf.5.html#loglevel"><strong>log
|
||||
level</strong></a> parameter in the <a href="smb.conf.5.html"><strong>smb.conf
|
||||
(5)</strong></a> file.
|
||||
<p><br><a name="minusl"></a>
|
||||
<li><strong><strong>-l logfile</strong></strong> The <strong>-l</strong> parameter specifies a path and base
|
||||
<p><a name="minusl"></a>
|
||||
<p></p><dt><strong><strong>-l logfile</strong></strong><dd> The <strong>-l</strong> parameter specifies a path and base
|
||||
filename into which operational data from the running nmbd server will
|
||||
be logged. The actual log file name is generated by appending the
|
||||
extension ".nmb" to the specified base name. For example, if the name
|
||||
specified was "log" then the file log.nmb would contain the debugging
|
||||
data.
|
||||
<p><br>The default log file path is compiled into Samba as part of the
|
||||
<p>The default log file path is compiled into Samba as part of the
|
||||
build process. Common defaults are <em>/usr/local/samba/var/log.nmb</em>,
|
||||
<em>/usr/samba/var/log.nmb</em> or <em>/var/log/log.nmb</em>.
|
||||
<p><br><a name="minusn"></a>
|
||||
<li><strong><strong>-n primary NetBIOS name</strong></strong> This option allows you to override
|
||||
<p><a name="minusn"></a>
|
||||
<p></p><dt><strong><strong>-n primary NetBIOS name</strong></strong><dd> This option allows you to override
|
||||
the NetBIOS name that Samba uses for itself. This is identical to
|
||||
setting the <a href="smb.conf.5.html#netbiosname"><strong>NetBIOS name</strong></a> parameter
|
||||
in the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file
|
||||
but will override the setting in the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file.
|
||||
<p><br><a name="minusp"></a>
|
||||
<li><strong><strong>-p UDP port number</strong></strong> UDP port number is a positive integer value.
|
||||
<p><br>This option changes the default UDP port number (normally 137) that
|
||||
<p><a name="minusp"></a>
|
||||
<p></p><dt><strong><strong>-p UDP port number</strong></strong><dd> UDP port number is a positive integer value.
|
||||
<p>This option changes the default UDP port number (normally 137) that
|
||||
<strong>nmbd</strong> responds to name queries on. Don't use this option unless you are
|
||||
an expert, in which case you won't need help!
|
||||
<p><br><a name="minuss"></a>
|
||||
<li><strong><strong>-s configuration file</strong></strong> The default configuration file name is
|
||||
<p><a name="minuss"></a>
|
||||
<p></p><dt><strong><strong>-s configuration file</strong></strong><dd> The default configuration file name is
|
||||
set at build time, typically as <em>/usr/local/samba/lib/smb.conf</em>, but
|
||||
this may be changed when Samba is autoconfigured.
|
||||
<p><br>The file specified contains the configuration details required by the
|
||||
<p>The file specified contains the configuration details required by the
|
||||
server. See <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> for more information.
|
||||
<p><br><a name="minusi"></a>
|
||||
<li><strong><strong>-i scope</strong></strong> This specifies a NetBIOS scope that <strong>nmbd</strong> will use
|
||||
to communicate with when generating NetBIOS names. For details on the
|
||||
use of NetBIOS scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes
|
||||
are <em>very</em> rarely used, only set this parameter if you are the
|
||||
system administrator in charge of all the NetBIOS systems you
|
||||
communicate with.
|
||||
<p><br></ul>
|
||||
<p><br><a name="FILES"></a>
|
||||
<p></dl>
|
||||
<p><a name="FILES"></a>
|
||||
<h2>FILES</h2>
|
||||
|
||||
<p><br><strong>/etc/inetd.conf</strong>
|
||||
<p><br>If the server is to be run by the inetd meta-daemon, this file must
|
||||
<p><strong>/etc/inetd.conf</strong>
|
||||
<p>If the server is to be run by the inetd meta-daemon, this file must
|
||||
contain suitable startup information for the meta-daemon.
|
||||
<p><br><strong>/etc/rc</strong>
|
||||
<p><br>(or whatever initialization script your system uses).
|
||||
<p><br>If running the server as a daemon at startup, this file will need to
|
||||
<p><strong>/etc/rc</strong>
|
||||
<p>(or whatever initialization script your system uses).
|
||||
<p>If running the server as a daemon at startup, this file will need to
|
||||
contain an appropriate startup sequence for the server.
|
||||
<p><br><strong>/usr/local/samba/lib/smb.conf</strong>
|
||||
<p><br>This is the default location of the
|
||||
<p><strong>/usr/local/samba/lib/smb.conf</strong>
|
||||
<p>This is the default location of the
|
||||
<a href="smb.conf.5.html"><strong>smb.conf</strong></a> server configuration
|
||||
file. Other common places that systems install this file are
|
||||
<em>/usr/samba/lib/smb.conf</em> and <em>/etc/smb.conf</em>.
|
||||
<p><br>When run as a <strong>WINS</strong> server (see the <a href="smb.conf.5.html#winssupport"><strong>wins support</strong></a>
|
||||
<p>When run as a <strong>WINS</strong> server (see the <a href="smb.conf.5.html#winssupport"><strong>wins support</strong></a>
|
||||
parameter in the <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> man page), <strong>nmbd</strong> will
|
||||
store the WINS database in the file <code>wins.dat</code> in the <code>var/locks</code> directory
|
||||
configured under wherever Samba was configured to install itself.
|
||||
<p><br>If <strong>nmbd</strong> is acting as a <strong>browse master</strong> (see the <a href="smb.conf.5.html#localmaster"><strong>local master</strong></a>
|
||||
<p>If <strong>nmbd</strong> is acting as a <strong>browse master</strong> (see the <a href="smb.conf.5.html#localmaster"><strong>local master</strong></a>
|
||||
parameter in the <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> man page), <strong>nmbd</strong> will
|
||||
store the browsing database in the file <code>browse.dat</code> in the <code>var/locks</code> directory
|
||||
configured under wherever Samba was configured to install itself.
|
||||
<p><br><a name="SIGNALS"></a>
|
||||
<p><a name="SIGNALS"></a>
|
||||
<h2>SIGNALS</h2>
|
||||
|
||||
<p><br>To shut down an <strong>nmbd</strong> process it is recommended that SIGKILL (-9)
|
||||
<p>To shut down an <strong>nmbd</strong> process it is recommended that SIGKILL (-9)
|
||||
<em>NOT</em> be used, except as a last resort, as this may leave the name
|
||||
database in an inconsistent state. The correct way to terminate
|
||||
<strong>nmbd</strong> is to send it a SIGTERM (-15) signal and wait for it to die on
|
||||
its own.
|
||||
<p><br><strong>nmbd</strong> will accept SIGHUP, which will cause it to dump out it's
|
||||
<p><strong>nmbd</strong> will accept SIGHUP, which will cause it to dump out it's
|
||||
namelists into the file <code>namelist.debug</code> in the
|
||||
<em>/usr/local/samba/var/locks</em> directory (or the <em>var/locks</em>
|
||||
directory configured under wherever Samba was configured to install
|
||||
@ -179,34 +172,34 @@ by sending it a SIGUSR1 (<code>kill -USR1 <nmbd-pid></code>) and lowered b
|
||||
SIGUSR2 (<code>kill -USR2 <nmbd-pid></code>). This is to allow transient
|
||||
problems to be diagnosed, whilst still running at a normally low log
|
||||
level.
|
||||
<p><br><a name="VERSION"></a>
|
||||
<p><a name="VERSION"></a>
|
||||
<h2>VERSION</h2>
|
||||
|
||||
<p><br>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><br><a name="SEEALSO"></a>
|
||||
<p>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><a name="SEEALSO"></a>
|
||||
<h2>SEE ALSO</h2>
|
||||
|
||||
<p><br><strong>inetd (8)</strong>, <a href="smbd.8.html"><strong>smbd (8)</strong></a>, <a href="smb.conf.5.html"><strong>smb.conf
|
||||
<p><strong>inetd (8)</strong>, <a href="smbd.8.html"><strong>smbd (8)</strong></a>, <a href="smb.conf.5.html"><strong>smb.conf
|
||||
(5)</strong></a>, <a href="smbclient.1.html"><strong>smbclient (1)</strong></a>,
|
||||
<a href="testparm.1.html"><strong>testparm (1)</strong></a>, <a href="testprns.1.html"><strong>testprns
|
||||
(1)</strong></a>, and the Internet RFC's <strong>rfc1001.txt</strong>,
|
||||
<strong>rfc1002.txt</strong>. In addition the CIFS (formerly SMB) specification is
|
||||
available as a link from the Web page :
|
||||
<a href="http://samba.org/cifs/">http://samba.org/cifs/</a>.
|
||||
<p><br><a name="AUTHOR"></a>
|
||||
<p><a name="AUTHOR"></a>
|
||||
<h2>AUTHOR</h2>
|
||||
|
||||
<p><br>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed
|
||||
<p>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed.
|
||||
<p><br>The original Samba man pages were written by Karl Auer. The man page
|
||||
<p>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
|
||||
<a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>)
|
||||
and updated for the Samba2.0 release by Jeremy Allison.
|
||||
<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>.
|
||||
<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
|
||||
<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>.
|
||||
<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
comments etc.
|
||||
</body>
|
||||
|
||||
@ -3,9 +3,10 @@
|
||||
|
||||
|
||||
|
||||
|
||||
<html><head><title>nmblookup (1)</title>
|
||||
|
||||
<link rev="made" href="mailto:samba-bugs@samba.org">
|
||||
<link rev="made" href="mailto:samba@samba.org">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
@ -15,139 +16,138 @@
|
||||
<h2>Samba</h2>
|
||||
<h2>23 Oct 1998</h2>
|
||||
|
||||
|
||||
|
||||
|
||||
<p><br><a name="NAME"></a>
|
||||
<p><a name="NAME"></a>
|
||||
<h2>NAME</h2>
|
||||
nmblookup - NetBIOS over TCP/IP client used to lookup NetBIOS names
|
||||
<p><br><a name="SYNOPSIS"></a>
|
||||
<p><a name="SYNOPSIS"></a>
|
||||
<h2>SYNOPSIS</h2>
|
||||
|
||||
<p><br><strong>nmblookup</strong> [<a href="nmblookup.1.html#minusM">-M</a>] [<a href="nmblookup.1.html#minusR">-R</a>] [<a href="nmblookup.1.html#minusS">-S</a>] [<a href="nmblookup.1.html#minusr">-r</a>] [<a href="nmblookup.1.html#minusA">-A</a>] [<a href="nmblookup.1.html#minush">-h</a>] [<a href="nmblookup.1.html#minusB">-B broadcast address</a>] [<a href="nmblookup.1.html#minusU">-U unicast address</a>] [<a href="nmblookup.1.html#minusd">-d debuglevel</a>] [<a href="nmblookup.1.html#minuss">-s smb config file</a>] [<a href="nmblookup.1.html#minusi">-i NetBIOS scope</a>] [<a href="nmblookup.1.html#minusT">-T</a>] <a href="nmblookup.1.html#name">name</a>
|
||||
<p><br><a name="DESCRIPTION"></a>
|
||||
<p><strong>nmblookup</strong> [<a href="nmblookup.1.html#minusM">-M</a>] [<a href="nmblookup.1.html#minusR">-R</a>] [<a href="nmblookup.1.html#minusS">-S</a>] [<a href="nmblookup.1.html#minusr">-r</a>] [<a href="nmblookup.1.html#minusA">-A</a>] [<a href="nmblookup.1.html#minush">-h</a>] [<a href="nmblookup.1.html#minusB">-B broadcast address</a>] [<a href="nmblookup.1.html#minusU">-U unicast address</a>] [<a href="nmblookup.1.html#minusd">-d debuglevel</a>] [<a href="nmblookup.1.html#minuss">-s smb config file</a>] [<a href="nmblookup.1.html#minusi">-i NetBIOS scope</a>] [<a href="nmblookup.1.html#minusT">-T</a>] <a href="nmblookup.1.html#name">name</a>
|
||||
<p><a name="DESCRIPTION"></a>
|
||||
<h2>DESCRIPTION</h2>
|
||||
|
||||
<p><br>This program is part of the <strong>Samba</strong> suite.
|
||||
<p><br><strong>nmblookup</strong> is used to query NetBIOS names and map them to IP
|
||||
<p>This program is part of the <strong>Samba</strong> suite.
|
||||
<p><strong>nmblookup</strong> is used to query NetBIOS names and map them to IP
|
||||
addresses in a network using NetBIOS over TCP/IP queries. The options
|
||||
allow the name queries to be directed at a particular IP broadcast area
|
||||
or to a particular machine. All queries are done over UDP.
|
||||
<p><br><a name="OPTIONS"></a>
|
||||
<p><a name="OPTIONS"></a>
|
||||
<h2>OPTIONS</h2>
|
||||
|
||||
<p><br><ul>
|
||||
<p><br><a name="minusM"></a>
|
||||
<li><strong><strong>-M</strong></strong> Searches for a master browser by looking up the
|
||||
<p><dl>
|
||||
<p><a name="minusM"></a>
|
||||
<p></p><dt><strong><strong>-M</strong></strong><dd> Searches for a master browser by looking up the
|
||||
NetBIOS name <a href="nmblookup.1.html#name"><strong>name</strong></a> with a type of 0x1d. If <a href="nmblookup.1.html#name"><strong>name</strong></a>
|
||||
is <code>"-"</code> then it does a lookup on the special name <code>__MSBROWSE__</code>.
|
||||
<p><br><a name="minusR"></a>
|
||||
<li><strong><strong>-R</strong></strong> Set the recursion desired bit in the packet to do a
|
||||
<p><a name="minusR"></a>
|
||||
<p></p><dt><strong><strong>-R</strong></strong><dd> Set the recursion desired bit in the packet to do a
|
||||
recursive lookup. This is used when sending a name query to a machine
|
||||
running a WINS server and the user wishes to query the names in the
|
||||
WINS server. If this bit is unset the normal (broadcast responding)
|
||||
NetBIOS processing code on a machine is used instead. See rfc1001,
|
||||
rfc1002 for details.
|
||||
<p><br><a name="minusS"></a>
|
||||
<li><strong><strong>-S</strong></strong> Once the name query has returned an IP address then do a
|
||||
<p><a name="minusS"></a>
|
||||
<p></p><dt><strong><strong>-S</strong></strong><dd> Once the name query has returned an IP address then do a
|
||||
node status query as well. A node status query returns the NetBIOS names
|
||||
registered by a host.
|
||||
<p><br><a name="minusr"></a>
|
||||
<li><strong><strong>-r</strong></strong> Try and bind to UDP port 137 to send and receive UDP
|
||||
<p><a name="minusr"></a>
|
||||
<p></p><dt><strong><strong>-r</strong></strong><dd> Try and bind to UDP port 137 to send and receive UDP
|
||||
datagrams. The reason for this option is a bug in Windows 95 where it
|
||||
ignores the source port of the requesting packet and only replies to
|
||||
UDP port 137. Unfortunately, on most UNIX systems root privilage is
|
||||
needed to bind to this port, and in addition, if the
|
||||
<a href="nmbd.8.html"><strong>nmbd</strong></a> daemon is running on this machine it also
|
||||
binds to this port.
|
||||
<p><br><a name="minusA"></a>
|
||||
<li><strong><strong>-A</strong></strong> Interpret <name> as an IP Address and do a node status
|
||||
<p><a name="minusA"></a>
|
||||
<p></p><dt><strong><strong>-A</strong></strong><dd> Interpret <name> as an IP Address and do a node status
|
||||
query on this address.
|
||||
<p><br><a name="minush"></a>
|
||||
<li><strong><strong>-h</strong></strong> Print a help (usage) message.
|
||||
<p><br><a name="minusB"></a>
|
||||
<li><strong><strong>-B broadcast address</strong></strong> Send the query to the given broadcast
|
||||
<p><a name="minush"></a>
|
||||
<p></p><dt><strong><strong>-h</strong></strong><dd> Print a help (usage) message.
|
||||
<p><a name="minusB"></a>
|
||||
<p></p><dt><strong><strong>-B broadcast address</strong></strong><dd> Send the query to the given broadcast
|
||||
address. Without this option the default behavior of nmblookup is to
|
||||
send the query to the broadcast address of the network
|
||||
interfaces as either auto-detected or defined in the
|
||||
<a href="smb.conf.5.html#interfaces"><strong>interfaces</strong></a> parameter of the
|
||||
<a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> file.
|
||||
<p><br><a name="minusU"></a>
|
||||
<li><strong><strong>-U unicast address</strong></strong> Do a unicast query to the specified
|
||||
<p><a name="minusU"></a>
|
||||
<p></p><dt><strong><strong>-U unicast address</strong></strong><dd> Do a unicast query to the specified
|
||||
address or host <code>"unicast address"</code>. This option (along with the
|
||||
<a href="nmblookup.1.html#minusR"><strong>-R</strong></a> option) is needed to query a WINS server.
|
||||
<p><br><a name="minusd"></a>
|
||||
<li><strong><strong>-d debuglevel</strong></strong> debuglevel is an integer from 0 to 10.
|
||||
<p><br>The default value if this parameter is not specified is zero.
|
||||
<p><br>The higher this value, the more detail will be logged about the
|
||||
<p><a name="minusd"></a>
|
||||
<p></p><dt><strong><strong>-d debuglevel</strong></strong><dd> debuglevel is an integer from 0 to 10.
|
||||
<p>The default value if this parameter is not specified is zero.
|
||||
<p>The higher this value, the more detail will be logged about the
|
||||
activities of <strong>nmblookup</strong>. At level 0, only critical errors and
|
||||
serious warnings will be logged.
|
||||
<p><br>Levels above 1 will generate considerable amounts of log data, and
|
||||
<p>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
|
||||
data, most of which is extremely cryptic.
|
||||
<p><br>Note that specifying this parameter here will override the <a href="smb.conf.5.html#loglevel"><strong>log
|
||||
<p>Note that specifying this parameter here will override the <a href="smb.conf.5.html#loglevel"><strong>log
|
||||
level</strong></a> parameter in the <a href="smb.conf.5.html"><strong>smb.conf
|
||||
(5)</strong></a> file.
|
||||
<p><br><a name="minuss"></a>
|
||||
<li><strong><strong>-s smb.conf</strong></strong> This parameter specifies the pathname to the
|
||||
<p><a name="minuss"></a>
|
||||
<p></p><dt><strong><strong>-s smb.conf</strong></strong><dd> This parameter specifies the pathname to the
|
||||
Samba configuration file, <a href="smb.conf.5.html"><strong>smb.conf</strong></a>.
|
||||
This file controls all aspects of
|
||||
the Samba setup on the machine.
|
||||
<p><br><a name="minusi"></a>
|
||||
<li><strong><strong>-i scope</strong></strong> This specifies a NetBIOS scope that <strong>nmblookup</strong> will use
|
||||
<p><a name="minusi"></a>
|
||||
<p></p><dt><strong><strong>-i scope</strong></strong><dd> This specifies a NetBIOS scope that <strong>nmblookup</strong> will use
|
||||
to communicate with when generating NetBIOS names. For details on the
|
||||
use of NetBIOS scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes
|
||||
are <em>very</em> rarely used, only set this parameter if you are the
|
||||
system administrator in charge of all the NetBIOS systems you
|
||||
communicate with.
|
||||
<p><br><a name="minusT"></a>
|
||||
<li><strong><strong>-T</strong></strong> This causes any IP addresses found in the lookup to be
|
||||
<p><a name="minusT"></a>
|
||||
<p></p><dt><strong><strong>-T</strong></strong><dd> This causes any IP addresses found in the lookup to be
|
||||
looked up via a reverse DNS lookup into a DNS name, and printed out
|
||||
before each <code>"IP address NetBIOS name"</code> pair that is the normal
|
||||
output.
|
||||
<p><br><a name="name"></a>
|
||||
<li><strong><strong>name</strong></strong> This is the NetBIOS name being queried. Depending upon
|
||||
<p><a name="name"></a>
|
||||
<p></p><dt><strong><strong>name</strong></strong><dd> This is the NetBIOS name being queried. Depending upon
|
||||
the previous options this may be a NetBIOS name or IP address. If a
|
||||
NetBIOS name then the different name types may be specified by
|
||||
appending <code>#<type></code> to the name. This name may also be <code>"*"</code>,
|
||||
which will return all registered names within a broadcast area.
|
||||
<p><br></ul>
|
||||
<p><br><a name="EXAMPLES"></a>
|
||||
<p></dl>
|
||||
<p><a name="EXAMPLES"></a>
|
||||
<h2>EXAMPLES</h2>
|
||||
|
||||
<p><br><strong>nmblookup</strong> can be used to query a WINS server (in the same way
|
||||
<p><strong>nmblookup</strong> can be used to query a WINS server (in the same way
|
||||
<strong>nslookup</strong> is used to query DNS servers). To query a WINS server,
|
||||
<strong>nmblookup</strong> must be called like this:
|
||||
<p><br><code>nmblookup -U server -R 'name'</code>
|
||||
<p><br>For example, running :
|
||||
<p><br><code>nmblookup -U samba.org -R IRIX#1B'</code>
|
||||
<p><br>would query the WINS server samba.org for the domain master
|
||||
<p><code>nmblookup -U server -R 'name'</code>
|
||||
<p>For example, running :
|
||||
<p><code>nmblookup -U samba.org -R IRIX#1B'</code>
|
||||
<p>would query the WINS server samba.org for the domain master
|
||||
browser (1B name type) for the IRIX workgroup.
|
||||
<p><br><a name="VERSION"></a>
|
||||
<p><a name="VERSION"></a>
|
||||
<h2>VERSION</h2>
|
||||
|
||||
<p><br>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><br><a name="SEEALSO"></a>
|
||||
<p>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><a name="SEEALSO"></a>
|
||||
<h2>SEE ALSO</h2>
|
||||
|
||||
<p><br><a href="samba.7.html"><strong>samba (7)</strong></a>, <a href="nmbd.8.html"><strong>nmbd (8)</strong></a>,
|
||||
<p><a href="samba.7.html"><strong>samba (7)</strong></a>, <a href="nmbd.8.html"><strong>nmbd (8)</strong></a>,
|
||||
<a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>
|
||||
<p><br><a name="AUTHOR"></a>
|
||||
<p><a name="AUTHOR"></a>
|
||||
<h2>AUTHOR</h2>
|
||||
|
||||
<p><br>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed
|
||||
<p>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed.
|
||||
<p><br>The original Samba man pages were written by Karl Auer. The man page
|
||||
<p>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
|
||||
<a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>)
|
||||
and updated for the Samba2.0 release by Jeremy Allison.
|
||||
<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>.
|
||||
<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
|
||||
<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>.
|
||||
<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
comments etc.
|
||||
<p><br></body>
|
||||
<p></body>
|
||||
</html>
|
||||
|
||||
@ -2,9 +2,10 @@
|
||||
|
||||
|
||||
|
||||
|
||||
<html><head><title>Samba (7)</title>
|
||||
|
||||
<link rev="made" href="mailto:samba-bugs@samba.org">
|
||||
<link rev="made" href="mailto:samba@samba.org">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
@ -14,105 +15,104 @@
|
||||
<h2>Samba</h2>
|
||||
<h2>23 Oct 1998</h2>
|
||||
|
||||
|
||||
|
||||
|
||||
<p><br><a name="NAME"></a>
|
||||
<p><a name="NAME"></a>
|
||||
<h2>NAME</h2>
|
||||
Samba - A Windows SMB/CIFS fileserver for UNIX
|
||||
<p><br><a name="SYNOPSIS"></a>
|
||||
<p><a name="SYNOPSIS"></a>
|
||||
<h2>SYNOPSIS</h2>
|
||||
|
||||
<strong>Samba</strong>
|
||||
<p><br><a name="DESCRIPTION"></a>
|
||||
<p><a name="DESCRIPTION"></a>
|
||||
<h2>DESCRIPTION</h2>
|
||||
|
||||
<p><br>The Samba software suite is a collection of programs that implements
|
||||
<p>The Samba software suite is a collection of programs that implements
|
||||
the Server Message Block(commonly abbreviated as SMB) protocol for
|
||||
UNIX systems. This protocol is sometimes also referred to as the
|
||||
Common Internet File System (CIFS), LanManager or NetBIOS protocol.
|
||||
<p><br><a name="COMPONENTS"></a>
|
||||
<p><a name="COMPONENTS"></a>
|
||||
<h2>COMPONENTS</h2>
|
||||
|
||||
<p><br>The Samba suite is made up of several components. Each component is
|
||||
<p>The Samba suite is made up of several components. Each component is
|
||||
described in a separate manual page. It is strongly recommended that
|
||||
you read the documentation that comes with Samba and the manual pages
|
||||
of those components that you use. If the manual pages aren't clear
|
||||
enough then please send a patch or bug report
|
||||
to <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>.
|
||||
<p><br><ul>
|
||||
<p><br><li><strong><a href="smbd.8.html"><strong>smbd</strong></a></strong> <br> <br> The <a href="smbd.8.html"><strong>smbd</strong>
|
||||
to <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>.
|
||||
<p><dl>
|
||||
<p><p></p><dt><strong><a href="smbd.8.html"><strong>smbd</strong></a></strong><dd> <br> <br> The <a href="smbd.8.html"><strong>smbd</strong>
|
||||
(8)</a> daemon provides the file and print services to SMB
|
||||
clients, such as Windows 95/98, Windows NT, Windows for Workgroups or
|
||||
LanManager. The configuration file for this daemon is described in
|
||||
<a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>.
|
||||
<p><br><li><strong><a href="nmbd.8.html"><strong>nmbd</strong></a></strong> <br> <br> The <a href="nmbd.8.html"><strong>nmbd</strong>
|
||||
<p><p></p><dt><strong><a href="nmbd.8.html"><strong>nmbd</strong></a></strong><dd> <br> <br> The <a href="nmbd.8.html"><strong>nmbd</strong>
|
||||
(8)</a> daemon provides NetBIOS nameserving and browsing
|
||||
support. The configuration file for this daemon is described in
|
||||
<a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>.
|
||||
<p><br><li><strong><a href="smbclient.1.html"><strong>smbclient</strong></a></strong> <br> <br> The <a href="smbclient.1.html"><strong>smbclient</strong>
|
||||
<p><p></p><dt><strong><a href="smbclient.1.html"><strong>smbclient</strong></a></strong><dd> <br> <br> The <a href="smbclient.1.html"><strong>smbclient</strong>
|
||||
(1)</a> program implements a simple ftp-like
|
||||
client. This is useful for accessing SMB shares on other compatible
|
||||
servers (such as Windows NT), and can also be used to allow a UNIX box
|
||||
to print to a printer attached to any SMB server (such as a PC running
|
||||
Windows NT).
|
||||
<p><br><li><strong><a href="testparm.1.html"><strong>testparm</strong></a></strong> <br> <br> The <a href="testparm.1.html"><strong>testparm
|
||||
<p><p></p><dt><strong><a href="testparm.1.html"><strong>testparm</strong></a></strong><dd> <br> <br> The <a href="testparm.1.html"><strong>testparm
|
||||
(1)</strong></a> utility allows you to test your <a href="smb.conf.5.html"><strong>smb.conf
|
||||
(5)</strong></a> configuration file.
|
||||
<p><br><li><strong><a href="testprns.1.html"><strong>testprns</strong></a></strong> <br> <br> the <a href="testprns.1.html"><strong>testprns
|
||||
<p><p></p><dt><strong><a href="testprns.1.html"><strong>testprns</strong></a></strong><dd> <br> <br> the <a href="testprns.1.html"><strong>testprns
|
||||
(1)</strong></a> utility allows you to test the printers defined
|
||||
in your printcap file.
|
||||
<p><br><li><strong><a href="smbstatus.1.html"><strong>smbstatus</strong></a></strong> <br> <br> The <a href="smbstatus.1.html"><strong>smbstatus</strong>
|
||||
<p><p></p><dt><strong><a href="smbstatus.1.html"><strong>smbstatus</strong></a></strong><dd> <br> <br> The <a href="smbstatus.1.html"><strong>smbstatus</strong>
|
||||
(1)</a> utility allows you list current connections to the
|
||||
<a href="smbd.8.html"><strong>smbd (8)</strong></a> server.
|
||||
<p><br><li><strong><a href="nmblookup.1.html"><strong>nmblookup</strong></a></strong> <br> <br> the
|
||||
<p><p></p><dt><strong><a href="nmblookup.1.html"><strong>nmblookup</strong></a></strong><dd> <br> <br> the
|
||||
<a href="nmblookup.1.html"><strong>nmblookup (1)</strong></a> utility allows NetBIOS name
|
||||
queries to be made from the UNIX machine.
|
||||
<p><br><li><strong><a href="make_smbcodepage.1.html"><strong>make_smbcodepage</strong></a></strong> <br> <br> The
|
||||
<p><p></p><dt><strong><a href="make_smbcodepage.1.html"><strong>make_smbcodepage</strong></a></strong><dd> <br> <br> The
|
||||
<a href="make_smbcodepage.1.html"><strong>make_smbcodepage (1)</strong></a> utility allows
|
||||
you to create SMB code page definition files for your <a href="smbd.8.html"><strong>smbd
|
||||
(8)</strong></a> server.
|
||||
<p><br><li><strong><a href="smbpasswd.8.html"><strong>smbpasswd</strong></a></strong> <br> <br> The <a href="smbpasswd.8.html"><strong>smbpasswd
|
||||
<p><p></p><dt><strong><a href="smbpasswd.8.html"><strong>smbpasswd</strong></a></strong><dd> <br> <br> The <a href="smbpasswd.8.html"><strong>smbpasswd
|
||||
(8)</strong></a> utility allows you to change SMB encrypted
|
||||
passwords on Samba and Windows NT(tm) servers.
|
||||
<p><br></ul>
|
||||
<p><br><a name="AVAILABILITY"></a>
|
||||
<p></dl>
|
||||
<p><a name="AVAILABILITY"></a>
|
||||
<h2>AVAILABILITY</h2>
|
||||
|
||||
<p><br>The Samba software suite is licensed under the GNU Public License
|
||||
<p>The Samba software suite is licensed under the GNU Public License
|
||||
(GPL). A copy of that license should have come with the package in the
|
||||
file COPYING. You are encouraged to distribute copies of the Samba
|
||||
suite, but please obey the terms of this license.
|
||||
<p><br>The latest version of the Samba suite can be obtained via anonymous
|
||||
<p>The latest version of the Samba suite can be obtained via anonymous
|
||||
ftp from samba.org in the directory pub/samba/. It is
|
||||
also available on several mirror sites worldwide.
|
||||
<p><br>You may also find useful information about Samba on the newsgroup
|
||||
<p>You may also find useful information about Samba on the newsgroup
|
||||
comp.protocols.smb and the Samba mailing list. Details on how to join
|
||||
the mailing list are given in the README file that comes with Samba.
|
||||
<p><br>If you have access to a WWW viewer (such as Netscape or Mosaic) then
|
||||
<p>If you have access to a WWW viewer (such as Netscape or Mosaic) then
|
||||
you will also find lots of useful information, including back issues
|
||||
of the Samba mailing list, at
|
||||
<a href="http://samba.org/samba/">http://samba.org/samba/</a>.
|
||||
<p><br><a name="VERSION"></a>
|
||||
<p><a name="VERSION"></a>
|
||||
<h2>VERSION</h2>
|
||||
|
||||
<p><br>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><br><a name="CONTRIBUTIONS"></a>
|
||||
<p>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><a name="CONTRIBUTIONS"></a>
|
||||
<h2>CONTRIBUTIONS</h2>
|
||||
|
||||
<p><br>If you wish to contribute to the Samba project, then I suggest you
|
||||
<p>If you wish to contribute to the Samba project, then I suggest you
|
||||
join the Samba mailing list at <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. See the
|
||||
Web page at
|
||||
<a href="http://samba.org/listproc">http://samba.org/listproc</a>
|
||||
for details on how to do this.
|
||||
<p><br>If you have patches to submit or bugs to report then you may mail them
|
||||
directly to <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Note, however, that due to
|
||||
<p>If you have patches to submit or bugs to report then you may mail them
|
||||
directly to <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Note, however, that due to
|
||||
the enormous popularity of this package the Samba Team may take some
|
||||
time to respond to mail. We prefer patches in <em>diff -u</em> format.
|
||||
<p><br><a name="CREDITS"></a>
|
||||
<p><a name="CREDITS"></a>
|
||||
<h2>CREDITS</h2>
|
||||
|
||||
<p><br>Contributors to the project are now too numerous to mention here but
|
||||
<p>Contributors to the project are now too numerous to mention here but
|
||||
all deserve the thanks of all Samba users. To see a full list, look at
|
||||
<a href="ftp://samba.org/pub/samba/alpha/change-log">ftp://samba.org/pub/samba/alpha/change-log</a>
|
||||
for the pre-CVS changes and at
|
||||
@ -120,21 +120,21 @@ for the pre-CVS changes and at
|
||||
for the contributors to Samba post-CVS. CVS is the Open Source source
|
||||
code control system used by the Samba Team to develop Samba. The
|
||||
project would have been unmanageable without it.
|
||||
<p><br>In addition, several commercial organizations now help fund the Samba
|
||||
<p>In addition, several commercial organizations now help fund the Samba
|
||||
Team with money and equipment. For details see the Samba Web pages at
|
||||
<a href="http://samba.org/samba/samba-thanks.html">http://samba.org/samba/samba-thanks.html</a>.
|
||||
<p><br><a name="AUTHOR"></a>
|
||||
<p><a name="AUTHOR"></a>
|
||||
<h2>AUTHOR</h2>
|
||||
|
||||
<p><br>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed
|
||||
<p>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed.
|
||||
<p><br>The original Samba man pages were written by Karl Auer. The man page
|
||||
<p>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
|
||||
<a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>)
|
||||
and updated for the Samba2.0 release by Jeremy Allison.
|
||||
<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>.
|
||||
<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>.
|
||||
</body>
|
||||
</html>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -3,9 +3,10 @@
|
||||
|
||||
|
||||
|
||||
|
||||
<html><head><title>smbclient (1)</title>
|
||||
|
||||
<link rev="made" href="mailto:samba-bugs@samba.org">
|
||||
<link rev="made" href="mailto:samba@samba.org">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
@ -15,575 +16,574 @@
|
||||
<h2>Samba</h2>
|
||||
<h2>23 Oct 1998</h2>
|
||||
|
||||
|
||||
|
||||
|
||||
<p><br><a name="NAME"></a>
|
||||
<p><a name="NAME"></a>
|
||||
<h2>NAME</h2>
|
||||
smbclient - ftp-like client to access SMB/CIFS resources on servers
|
||||
<p><br><a name="SYNOPSIS"></a>
|
||||
<p><a name="SYNOPSIS"></a>
|
||||
<h2>SYNOPSIS</h2>
|
||||
|
||||
<p><br><strong>smbclient</strong> <a href="smbclient.1.html#servicename">servicename</a> [<a href="smbclient.1.html#minuss">-s smb.conf</a>] [<a href="smbclient.1.html#minusO">-O socket options</a>][<a href="smbclient.1.html#minusR">-R name resolve order</a>] [<a href="smbclient.1.html#minusM">-M NetBIOS name</a>] [<a href="smbclient.1.html#minusi">-i scope</a>] [<a href="smbclient.1.html#minusN">-N</a>] [<a href="smbclient.1.html#minusn">-n NetBIOS name</a>] [<a href="smbclient.1.html#minusd">-d debuglevel</a>] [<a href="smbclient.1.html#minusP">-P</a>] [<a href="smbclient.1.html#minusp">-p port</a>] [<a href="smbclient.1.html#minusl">-l log basename</a>] [<a href="smbclient.1.html#minush">-h</a>] [<a href="smbclient.1.html#minusI">-I dest IP</a>] [<a href="smbclient.1.html#minusE">-E</a>] [<a href="smbclient.1.html#minusU">-U username</a>] [<a href="smbclient.1.html#minusL">-L NetBIOS name</a>] [<a href="smbclient.1.html#minust">-t terminal code</a>] [<a href="smbclient.1.html#minusm">-m max protocol</a>] [<a href="smbclient.1.html#minusb">-b buffersize</a>] [<a href="smbclient.1.html#minusW">-W workgroup</a>] [<a href="smbclient.1.html#minusT">-T<c|x>IXFqgbNan</a>] [<a href="smbclient.1.html#minusD">-D directory</a>] [<a href="smbclient.1.html#minusc">-c command string</a>]
|
||||
<p><br><a name="DESCRIPTION"></a>
|
||||
<p><strong>smbclient</strong> <a href="smbclient.1.html#servicename">servicename</a> [<a href="smbclient.1.html#minuss">-s smb.conf</a>] [<a href="smbclient.1.html#minusO">-O socket options</a>][<a href="smbclient.1.html#minusR">-R name resolve order</a>] [<a href="smbclient.1.html#minusM">-M NetBIOS name</a>] [<a href="smbclient.1.html#minusi">-i scope</a>] [<a href="smbclient.1.html#minusN">-N</a>] [<a href="smbclient.1.html#minusn">-n NetBIOS name</a>] [<a href="smbclient.1.html#minusd">-d debuglevel</a>] [<a href="smbclient.1.html#minusP">-P</a>] [<a href="smbclient.1.html#minusp">-p port</a>] [<a href="smbclient.1.html#minusl">-l log basename</a>] [<a href="smbclient.1.html#minush">-h</a>] [<a href="smbclient.1.html#minusI">-I dest IP</a>] [<a href="smbclient.1.html#minusE">-E</a>] [<a href="smbclient.1.html#minusU">-U username</a>] [<a href="smbclient.1.html#minusL">-L NetBIOS name</a>] [<a href="smbclient.1.html#minust">-t terminal code</a>] [<a href="smbclient.1.html#minusm">-m max protocol</a>] [<a href="smbclient.1.html#minusb">-b buffersize</a>] [<a href="smbclient.1.html#minusW">-W workgroup</a>] [<a href="smbclient.1.html#minusT">-T<c|x>IXFqgbNan</a>] [<a href="smbclient.1.html#minusD">-D directory</a>] [<a href="smbclient.1.html#minusc">-c command string</a>]
|
||||
<p><a name="DESCRIPTION"></a>
|
||||
<h2>DESCRIPTION</h2>
|
||||
|
||||
<p><br>This program is part of the <strong>Samba</strong> suite.
|
||||
<p><br><strong>smbclient</strong> is a client that can 'talk' to an SMB/CIFS server. It
|
||||
<p>This program is part of the <strong>Samba</strong> suite.
|
||||
<p><strong>smbclient</strong> is a client that can 'talk' to an SMB/CIFS server. It
|
||||
offers an interface similar to that of the ftp program (see <strong>ftp
|
||||
(1)</strong>). 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.
|
||||
<p><br><a name="OPTIONS"></a>
|
||||
<p><a name="OPTIONS"></a>
|
||||
<h2>OPTIONS</h2>
|
||||
|
||||
<p><br><ul>
|
||||
<p><br><a name="servicename"></a>
|
||||
<li><strong><strong>servicename</strong></strong> servicename is the name of the service you want
|
||||
<p><dl>
|
||||
<p><a name="servicename"></a>
|
||||
<p></p><dt><strong><strong>servicename</strong></strong><dd> servicename is the name of the service you want
|
||||
to use on the server. A service name takes the form
|
||||
<code>//server/service</code> where <em>server</em> is the NetBIOS name of the SMB/CIFS
|
||||
server offering the desired service and <em>service</em> is the name
|
||||
of the service offered. Thus to connect to the service <em>printer</em> on
|
||||
the SMB/CIFS server <em>smbserver</em>, you would use the servicename
|
||||
<p><br><code>//smbserver/printer</code>
|
||||
<p><br>Note that the server name required is NOT necessarily the IP (DNS)
|
||||
<p><code>//smbserver/printer</code>
|
||||
<p>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.
|
||||
<p><br>The server name is looked up according to either the
|
||||
<p>The server name is looked up according to either the
|
||||
<a href="smbclient.1.html#minusR"><strong>-R</strong></a> parameter to <strong>smbclient</strong> or using the
|
||||
<a href="smb.conf.5.html#nameresolveorder"><strong>name resolve order</strong></a>
|
||||
parameter in the smb.conf file, allowing an administrator to change
|
||||
the order and methods by which server names are looked up.
|
||||
<p><br><a name="password"></a>
|
||||
<li><strong><strong>password</strong></strong> password is the password required to access the
|
||||
<p><a name="password"></a>
|
||||
<p></p><dt><strong><strong>password</strong></strong><dd> password is the password required to access the
|
||||
specified service on the specified server. If this parameter is
|
||||
supplied, the <a href="smbclient.1.html#minusN"><strong>-N</strong></a> option (suppress password prompt) is assumed.
|
||||
<p><br>There is no default password. If no password is supplied on the
|
||||
<p>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 <a href="smbclient.1.html#minusU"><strong>-U</strong></a> option (see below)) and the <a href="smbclient.1.html#minusN"><strong>-N</strong></a> 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.)
|
||||
<p><br>Note: Some servers (including OS/2 and Windows for Workgroups) insist
|
||||
<p>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.
|
||||
<p><br>Be cautious about including passwords in scripts.
|
||||
<p><br><a name="minuss"></a>
|
||||
<li><strong><strong>-s smb.conf</strong></strong> This parameter specifies the pathname to the
|
||||
<p>Be cautious about including passwords in scripts.
|
||||
<p><a name="minuss"></a>
|
||||
<p></p><dt><strong><strong>-s smb.conf</strong></strong><dd> This parameter specifies the pathname to the
|
||||
Samba configuration file, smb.conf. This file controls all aspects of
|
||||
the Samba setup on the machine and smbclient also needs to read this
|
||||
file.
|
||||
<p><br><a name="minusO"></a>
|
||||
<li><strong><strong>-O socket options</strong></strong> TCP socket options to set on the client
|
||||
<p><a name="minusO"></a>
|
||||
<p></p><dt><strong><strong>-O socket options</strong></strong><dd> TCP socket options to set on the client
|
||||
socket. See the <a href="smb.conf.5.html#socketoptions">socket options</a>
|
||||
parameter in the <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> manpage for
|
||||
the list of valid options.
|
||||
<p><br><a name="minusR"></a>
|
||||
<li><strong><strong>-R name resolve order</strong></strong> This option allows the user of
|
||||
<p><a name="minusR"></a>
|
||||
<p></p><dt><strong><strong>-R name resolve order</strong></strong><dd> This option allows the user of
|
||||
smbclient to determine what name resolution services to use when
|
||||
looking up the NetBIOS name of the host being connected to.
|
||||
<p><br>The options are :"lmhosts", "host", "wins" and "bcast". They cause
|
||||
<p>The options are :"lmhosts", "host", "wins" and "bcast". They cause
|
||||
names to be resolved as follows :
|
||||
<p><br><ul>
|
||||
<p><br><li > <strong>lmhosts</strong> : Lookup an IP address in the Samba lmhosts file.
|
||||
<p><dl>
|
||||
<p><li > <strong>lmhosts</strong> : Lookup an IP address in the Samba lmhosts file.
|
||||
The lmhosts file is stored in the same directory as the
|
||||
<a href="smb.conf.5.html"><strong>smb.conf</strong></a> file.
|
||||
<p><br><li > <strong>host</strong> : Do a standard host name to IP address resolution,
|
||||
<p><li > <strong>host</strong> : 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 depended for instance on IRIX or
|
||||
Solaris this may be controlled by the <em>/etc/nsswitch.conf</em> file).
|
||||
<p><br><li > <strong>wins</strong> : Query a name with the IP address listed in the <a href="smb.conf.5.html#winsserver"><strong>wins
|
||||
<p><li > <strong>wins</strong> : Query a name with the IP address listed in the <a href="smb.conf.5.html#winsserver"><strong>wins
|
||||
server</strong></a> parameter in the smb.conf file. If
|
||||
no WINS server has been specified this method will be ignored.
|
||||
<p><br><li > <strong>bcast</strong> : Do a broadcast on each of the known local interfaces
|
||||
<p><li > <strong>bcast</strong> : Do a broadcast on each of the known local interfaces
|
||||
listed in the <a href="smb.conf.5.html#interfaces"><strong>interfaces</strong></a> parameter
|
||||
in the smb.conf file. This is the least reliable of the name resolution
|
||||
methods as it depends on the target host being on a locally connected
|
||||
subnet.
|
||||
<p><br></ul>
|
||||
<p><br>If this parameter is not set then the name resolve order defined
|
||||
<p></dl>
|
||||
<p>If this parameter is not set then the name resolve order defined
|
||||
in the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file parameter
|
||||
<a href="smb.conf.5.html#nameresolveorder">(<strong>name resolve order</strong>)</a>
|
||||
will be used.
|
||||
<p><br>The default order is lmhosts, host, wins, bcast and without this
|
||||
<p>The default order is lmhosts, host, wins, bcast and without this
|
||||
parameter or any entry in the <a href="smb.conf.5.html#nameresolveorder"><strong>"name resolve
|
||||
order"</strong></a> parameter of the
|
||||
<a href="smb.conf.5.html"><strong>smb.conf</strong></a> file the name resolution methods
|
||||
will be attempted in this order.
|
||||
<p><br><a name="minusM"></a>
|
||||
<li><strong><strong>-M NetBIOS name</strong></strong> This options allows you to send messages,
|
||||
<p><a name="minusM"></a>
|
||||
<p></p><dt><strong><strong>-M NetBIOS name</strong></strong><dd> 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.
|
||||
<p><br>If the receiving computer is running WinPopup the user will receive
|
||||
<p>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.
|
||||
<p><br>The message is also automatically truncated if the message is over
|
||||
<p>The message is also automatically truncated if the message is over
|
||||
1600 bytes, as this is the limit of the protocol.
|
||||
<p><br>One useful trick is to cat the message through <strong>smbclient</strong>.
|
||||
<p>One useful trick is to cat the message through <strong>smbclient</strong>.
|
||||
For example:
|
||||
<p><br><code>cat mymessage.txt | smbclient -M FRED</code>
|
||||
<p><br>will send the message in the file <em>mymessage.txt</em> to the machine FRED.
|
||||
<p><br>You may also find the <a href="smbclient.1.html#minusU"><strong>-U</strong></a> and <a href="smbclient.1.html#minusI"><strong>-I</strong></a> options useful, as they allow
|
||||
<p><code>cat mymessage.txt | smbclient -M FRED</code>
|
||||
<p>will send the message in the file <em>mymessage.txt</em> to the machine FRED.
|
||||
<p>You may also find the <a href="smbclient.1.html#minusU"><strong>-U</strong></a> and <a href="smbclient.1.html#minusI"><strong>-I</strong></a> options useful, as they allow
|
||||
you to control the FROM and TO parts of the message.
|
||||
<p><br>See the <a href="smb.conf.5.html#messagecommand"><strong>message command</strong></a>
|
||||
<p>See the <a href="smb.conf.5.html#messagecommand"><strong>message command</strong></a>
|
||||
parameter in the <strong>smb.conf (5)</strong> for a description of how to handle
|
||||
incoming WinPopup messages in Samba.
|
||||
<p><br>Note: Copy WinPopup into the startup group on your WfWg PCs if you
|
||||
<p>Note: Copy WinPopup into the startup group on your WfWg PCs if you
|
||||
want them to always be able to receive messages.
|
||||
<p><br><a name="minusi"></a>
|
||||
<li><strong><strong>-i scope</strong></strong> This specifies a NetBIOS scope that smbclient will use
|
||||
<p><a name="minusi"></a>
|
||||
<p></p><dt><strong><strong>-i scope</strong></strong><dd> 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. NetBIOS scopes
|
||||
are <em>very</em> rarely used, only set this parameter if you are the
|
||||
system administrator in charge of all the NetBIOS systems you
|
||||
communicate with.
|
||||
<p><br><a name="minusN"></a>
|
||||
<li><strong><strong>-N</strong></strong> If specified, this parameter suppresses the normal
|
||||
<p><a name="minusN"></a>
|
||||
<p></p><dt><strong><strong>-N</strong></strong><dd> 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.
|
||||
<p><br>Unless a password is specified on the command line or this parameter
|
||||
<p>Unless a password is specified on the command line or this parameter
|
||||
is specified, the client will request a password.
|
||||
<p><br><a name="minusn"></a>
|
||||
<li><strong><strong>-n NetBIOS name</strong></strong> By default, the client will use the local
|
||||
<p><a name="minusn"></a>
|
||||
<p></p><dt><strong><strong>-n NetBIOS name</strong></strong><dd> 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.
|
||||
<p><br><a name="minusd"></a>
|
||||
<li><strong><strong>-d debuglevel</strong></strong> debuglevel is an integer from 0 to 10, or the
|
||||
<p><a name="minusd"></a>
|
||||
<p></p><dt><strong><strong>-d debuglevel</strong></strong><dd> debuglevel is an integer from 0 to 10, or the
|
||||
letter 'A'.
|
||||
<p><br>The default value if this parameter is not specified is zero.
|
||||
<p><br>The higher this value, the more detail will be logged to the log files
|
||||
<p>The default value if this parameter is not specified is zero.
|
||||
<p>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.
|
||||
<p><br>Levels above 1 will generate considerable amounts of log data, and
|
||||
<p>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 debuglevel is set to the
|
||||
letter 'A', then <em>all</em> debug messages will be printed. This setting
|
||||
is for developers only (and people who <em>really</em> want to know how the
|
||||
code works internally).
|
||||
<p><br>Note that specifying this parameter here will override the <a href="smb.conf.5.html#loglevel"><strong>log
|
||||
<p>Note that specifying this parameter here will override the <a href="smb.conf.5.html#loglevel"><strong>log
|
||||
level</strong></a> parameter in the <a href="smb.conf.5.html"><strong>smb.conf
|
||||
(5)</strong></a> file.
|
||||
<p><br><a name="minusP"></a>
|
||||
<li><strong><strong>-P</strong></strong> This option is no longer used. The code in Samba2.0
|
||||
<p><a name="minusP"></a>
|
||||
<p></p><dt><strong><strong>-P</strong></strong><dd> This option is no longer used. The code in Samba2.0
|
||||
now lets the server decide the device type, so no printer specific
|
||||
flag is needed.
|
||||
<p><br><a name="minusp"></a>
|
||||
<li><strong><strong>-p port</strong></strong> This number is the TCP port number that will be used
|
||||
<p><a name="minusp"></a>
|
||||
<p></p><dt><strong><strong>-p port</strong></strong><dd> 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.
|
||||
<p><br><a name="minusl"></a>
|
||||
<li><strong><strong>-l logfilename</strong></strong> If specified, logfilename specifies a base
|
||||
<p><a name="minusl"></a>
|
||||
<p></p><dt><strong><strong>-l logfilename</strong></strong><dd> If specified, logfilename specifies a base
|
||||
filename into which operational data from the running client will be
|
||||
logged.
|
||||
<p><br>The default base name is specified at compile time.
|
||||
<p><br>The base name is used to generate actual log file names. For example,
|
||||
<p>The default base name is specified at compile time.
|
||||
<p>The base name is used to generate actual log file names. For example,
|
||||
if the name specified was "log", the debug file would be
|
||||
<code>log.client</code>.
|
||||
<p><br>The log file generated is never removed by the client.
|
||||
<p><br><a name="minush"></a>
|
||||
<li><strong><strong>-h</strong></strong> Print the usage message for the client.
|
||||
<p><br><a name="minusI"></a>
|
||||
<li><strong><strong>-I IP address</strong></strong> IP address is the address of the server to
|
||||
<p>The log file generated is never removed by the client.
|
||||
<p><a name="minush"></a>
|
||||
<p></p><dt><strong><strong>-h</strong></strong><dd> Print the usage message for the client.
|
||||
<p><a name="minusI"></a>
|
||||
<p></p><dt><strong><strong>-I IP address</strong></strong><dd> IP address is the address of the server to
|
||||
connect to. It should be specified in standard "a.b.c.d" notation.
|
||||
<p><br>Normally the client would attempt to locate a named SMB/CIFS server by
|
||||
<p>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 <a href="smbclient.1.html#minusR"><strong>name resolve order</strong></a> 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.
|
||||
<p><br>There is no default for this parameter. If not supplied, it will be
|
||||
<p>There is no default for this parameter. If not supplied, it will be
|
||||
determined automatically by the client as described above.
|
||||
<p><br><a name="minusE"></a>
|
||||
<li><strong><strong>-E</strong></strong> This parameter causes the client to write messages to the
|
||||
<p><a name="minusE"></a>
|
||||
<p></p><dt><strong><strong>-E</strong></strong><dd> This parameter causes the client to write messages to the
|
||||
standard error stream (stderr) rather than to the standard output
|
||||
stream.
|
||||
<p><br>By default, the client writes messages to standard output - typically
|
||||
<p>By default, the client writes messages to standard output - typically
|
||||
the user's tty.
|
||||
<p><br><a name="minusU"></a>
|
||||
<li><strong><strong>-U username</strong></strong> This specifies the user name that will be used by
|
||||
<p><a name="minusU"></a>
|
||||
<p></p><dt><strong><strong>-U username</strong></strong><dd> This specifies the user name that will be used by
|
||||
the client to make a connection, assuming your server is not a downlevel
|
||||
server that is running a protocol level that uses passwords on shares,
|
||||
not on usernames.
|
||||
<p><br>Some servers are fussy about the case of this name, and some insist
|
||||
<p>Some servers are fussy about the case of this name, and some insist
|
||||
that it must be a valid NetBIOS name.
|
||||
<p><br>If no username is supplied, it will default to an uppercase version of
|
||||
<p>If no username is supplied, it will default to an uppercase version of
|
||||
the environment variable <code>USER</code> or <code>LOGNAME</code> in that order. If no
|
||||
username is supplied and neither environment variable exists the
|
||||
username "GUEST" will be used.
|
||||
<p><br>If the <code>USER</code> environment variable contains a '%' character,
|
||||
<p>If the <code>USER</code> environment variable contains a '%' character,
|
||||
everything after that will be treated as a password. This allows you
|
||||
to set the environment variable to be <code>USER=username%password</code> so
|
||||
that a password is not passed on the command line (where it may be
|
||||
seen by the ps command).
|
||||
<p><br>If the service you are connecting to requires a password, it can be
|
||||
<p>If the service you are connecting to requires a password, it can be
|
||||
supplied using the <a href="smbclient.1.html#minusU"><strong>-U</strong></a> option, by appending a percent symbol ("%")
|
||||
then the password to username. For example, to attach to a service as
|
||||
user <code>"fred"</code> with password <code>"secret"</code>, you would specify. <br>
|
||||
<p><br><code>-U fred%secret</code> <br>
|
||||
<p><br>on the command line. Note that there are no spaces around the percent
|
||||
<p><code>-U fred%secret</code> <br>
|
||||
<p>on the command line. Note that there are no spaces around the percent
|
||||
symbol.
|
||||
<p><br>If you specify the password as part of username then the <a href="smbclient.1.html#minusN"><strong>-N</strong></a> option
|
||||
<p>If you specify the password as part of username then the <a href="smbclient.1.html#minusN"><strong>-N</strong></a> option
|
||||
(suppress password prompt) is assumed.
|
||||
<p><br>If you specify the password as a parameter <em>AND</em> as part of username
|
||||
<p>If you specify the password as a parameter <em>AND</em> as part of username
|
||||
then the password as part of username will take precedence. Putting
|
||||
nothing before or nothing after the percent symbol will cause an empty
|
||||
username or an empty password to be used, respectively.
|
||||
<p><br>The password may also be specified by setting up an environment
|
||||
<p>The password may also be specified by setting up an environment
|
||||
variable called <code>PASSWD</code> that contains the users password. Note
|
||||
that this may be very insecure on some systems but on others allows
|
||||
users to script smbclient commands without having a password appear in
|
||||
the command line of a process listing.
|
||||
<p><br>Note: Some servers (including OS/2 and Windows for Workgroups) insist
|
||||
<p>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.
|
||||
<p><br>Be cautious about including passwords in scripts or in the
|
||||
<p>Be cautious about including passwords in scripts or in the
|
||||
<code>PASSWD</code> environment variable. Also, on many systems the command
|
||||
line of a running process may be seen via the <code>ps</code> command to be
|
||||
safe always allow smbclient to prompt for a password and type it in
|
||||
directly.
|
||||
<p><br><a name="minusL"></a>
|
||||
<li><strong><strong>-L</strong></strong> This option allows you to look at what services are
|
||||
<p><a name="minusL"></a>
|
||||
<p></p><dt><strong><strong>-L</strong></strong><dd> This option allows you to look at what services are
|
||||
available on a server. You use it as <code>"smbclient -L host"</code> and a
|
||||
list should appear. The <a href="smbclient.1.html#minusI"><strong>-I</strong></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.
|
||||
<p><br><a name="minust"></a>
|
||||
<li><strong><strong>-t terminal code</strong></strong> This option tells smbclient how to interpret
|
||||
<p><a name="minust"></a>
|
||||
<p></p><dt><strong><strong>-t terminal code</strong></strong><dd> This option tells smbclient how to interpret
|
||||
filenames coming from the remote server. Usually Asian language
|
||||
multibyte UNIX implementations use different character sets than
|
||||
SMB/CIFS servers (<em>EUC</em> instead of <em>SJIS</em> for example). Setting
|
||||
this parameter will let smbclient convert between the UNIX filenames
|
||||
and the SMB filenames correctly. This option has not been seriously
|
||||
tested and may have some problems.
|
||||
<p><br>The terminal codes include <code>sjis</code>, <code>euc</code>, <code>jis7</code>, <code>jis8</code>,
|
||||
<p>The terminal codes include <code>sjis</code>, <code>euc</code>, <code>jis7</code>, <code>jis8</code>,
|
||||
<code>junet</code>, <code>hex</code>, <code>cap</code>. This is not a complete list, check the
|
||||
Samba source code for the complete list.
|
||||
<p><br><a name="minusm"></a>
|
||||
<li><strong><strong>-m max protocol level</strong></strong> With the new code in Samba2.0,
|
||||
<p><a name="minusm"></a>
|
||||
<p></p><dt><strong><strong>-m max protocol level</strong></strong><dd> With the new code in Samba2.0,
|
||||
<strong>smbclient</strong> always attempts to connect at the maximum
|
||||
protocols level the server supports. This parameter is
|
||||
preserved for backwards compatibility, but any string
|
||||
following the <strong>-m</strong> will be ignored.
|
||||
<p><br><a name="minusb"></a>
|
||||
<li><strong><strong>-b buffersize</strong></strong> This option changes the transmit/send buffer
|
||||
<p><a name="minusb"></a>
|
||||
<p></p><dt><strong><strong>-b buffersize</strong></strong><dd> 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.
|
||||
<p><br><a name="minusW"></a>
|
||||
<li><strong><strong>-W WORKGROUP</strong></strong> Override the default workgroup specified in the
|
||||
<p><a name="minusW"></a>
|
||||
<p></p><dt><strong><strong>-W WORKGROUP</strong></strong><dd> Override the default workgroup specified in the
|
||||
<a href="smb.conf.5.html#workgroup"><strong>workgroup</strong></a> parameter of the
|
||||
<a href="smb.conf.5.html"><strong>smb.conf</strong></a> file for this connection. This may
|
||||
be needed to connect to some servers.
|
||||
<p><br><a name="minusT"></a> <li><strong><strong>-T tar options</strong></strong> smbclient may be used to create
|
||||
<p><a name="minusT"></a> <p></p><dt><strong><strong>-T tar options</strong></strong><dd> smbclient may be used to create
|
||||
<strong>tar (1)</strong> compatible backups of all the files on an SMB/CIFS
|
||||
share. The secondary tar flags that can be given to this option are :
|
||||
<p><br><ul>
|
||||
<p><br><li><strong><strong>c</strong></strong> Create a tar file on UNIX. Must be followed by the
|
||||
<p><dl>
|
||||
<p><p></p><dt><strong><strong>c</strong></strong><dd> Create a tar file on UNIX. Must be followed by the
|
||||
name of a tar file, tape device or <code>"-"</code> for standard output. If
|
||||
using standard output you must turn the log level to its lowest value
|
||||
<code>-d0</code> to avoid corrupting your tar file. This flag is
|
||||
mutually exclusive with the <strong>x</strong> flag.
|
||||
<p><br><li><strong><strong>x</strong></strong> Extract (restore) a local tar file back to a
|
||||
<p><p></p><dt><strong><strong>x</strong></strong><dd> Extract (restore) a local tar file back to a
|
||||
share. Unless the <a href="smbclient.1.html#minusD"><strong>-D</strong></a> 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 <code>"-"</code> for standard input. Mutually exclusive
|
||||
with the <strong>c</strong> 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.
|
||||
<p><br><li><strong><strong>I</strong></strong> Include files and directories. Is the default
|
||||
<p><p></p><dt><strong><strong>I</strong></strong><dd> 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 <strong>r</strong> below.
|
||||
<p><br><li><strong><strong>X</strong></strong> Exclude files and directories. Causes tar files to
|
||||
<p><p></p><dt><strong><strong>X</strong></strong><dd> 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 <strong>r</strong> below.
|
||||
<p><br><li><strong><strong>b</strong></strong> Blocksize. Must be followed by a valid (greater than
|
||||
<p><p></p><dt><strong><strong>b</strong></strong><dd> 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.
|
||||
<p><br><li><strong><strong>g</strong></strong> Incremental. Only back up files that have the
|
||||
<p><p></p><dt><strong><strong>g</strong></strong><dd> Incremental. Only back up files that have the
|
||||
archive bit set. Useful only with the <strong>c</strong> flag.
|
||||
<p><br><li><strong><strong>q</strong></strong> Quiet. Keeps tar from printing diagnostics as it
|
||||
<p><p></p><dt><strong><strong>q</strong></strong><dd> Quiet. Keeps tar from printing diagnostics as it
|
||||
works. This is the same as tarmode quiet.
|
||||
<p><br><li><strong><strong>r</strong></strong> Regular expression include or exclude. Uses regular
|
||||
<p><p></p><dt><strong><strong>r</strong></strong><dd> 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
|
||||
?.
|
||||
<p><br><li><strong><strong>N</strong></strong> Newer than. Must be followed by the name of a file
|
||||
<p><p></p><dt><strong><strong>N</strong></strong><dd> 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 <strong>c</strong> flag.
|
||||
<p><br><li><strong><strong>a</strong></strong> Set archive bit. Causes the archive bit to be reset
|
||||
<p><p></p><dt><strong><strong>a</strong></strong><dd> Set archive bit. Causes the archive bit to be reset
|
||||
when a file is backed up. Useful with the <strong>g</strong> and <strong>c</strong> flags.
|
||||
<p><br></ul>
|
||||
<p><br><em>Tar Long File Names</em>
|
||||
<p><br>smbclient's tar option now supports long file names both on backup and
|
||||
<p></dl>
|
||||
<p><em>Tar Long File Names</em>
|
||||
<p>smbclient'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 files in the archive with relative names, not
|
||||
absolute names.
|
||||
<p><br><em>Tar Filenames</em>
|
||||
<p><br>All file names can be given as DOS path names (with <code>\</code> as the
|
||||
<p><em>Tar Filenames</em>
|
||||
<p>All file names can be given as DOS path names (with <code>\</code> as the
|
||||
component separator) or as UNIX path names (with <code>/</code> as the
|
||||
component separator).
|
||||
<p><br><em>Examples</em>
|
||||
<p><br><ul>
|
||||
<p><br><li > Restore from tar file backup.tar into myshare on mypc (no password on share).
|
||||
<p><br><code>smbclient //mypc/myshare "" -N -Tx backup.tar</code>
|
||||
<p><br><li > Restore everything except users/docs
|
||||
<p><br><code>smbclient //mypc/myshare "" -N -TXx backup.tar users/docs</code>
|
||||
<p><br><li > Create a tar file of the files beneath users/docs.
|
||||
<p><br><code>smbclient //mypc/myshare "" -N -Tc backup.tar users/docs</code>
|
||||
<p><br><li > Create the same tar file as above, but now use a DOS path name.
|
||||
<p><br><code>smbclient //mypc/myshare "" -N -tc backup.tar users\edocs</code>
|
||||
<p><br><li > Create a tar file of all the files and directories in the share.
|
||||
<p><br><code>smbclient //mypc/myshare "" -N -Tc backup.tar *</code>
|
||||
<p><br></ul>
|
||||
<p><br><a name="minusD"></a>
|
||||
<li><strong><strong>-D initial directory</strong></strong> Change to initial directory before
|
||||
<p><em>Examples</em>
|
||||
<p><dl>
|
||||
<p><li > Restore from tar file backup.tar into myshare on mypc (no password on share).
|
||||
<p><code>smbclient //mypc/myshare "" -N -Tx backup.tar</code>
|
||||
<p><li > Restore everything except users/docs
|
||||
<p><code>smbclient //mypc/myshare "" -N -TXx backup.tar users/docs</code>
|
||||
<p><li > Create a tar file of the files beneath users/docs.
|
||||
<p><code>smbclient //mypc/myshare "" -N -Tc backup.tar users/docs</code>
|
||||
<p><li > Create the same tar file as above, but now use a DOS path name.
|
||||
<p><code>smbclient //mypc/myshare "" -N -tc backup.tar users\edocs</code>
|
||||
<p><li > Create a tar file of all the files and directories in the share.
|
||||
<p><code>smbclient //mypc/myshare "" -N -Tc backup.tar *</code>
|
||||
<p></dl>
|
||||
<p><a name="minusD"></a>
|
||||
<p></p><dt><strong><strong>-D initial directory</strong></strong><dd> Change to initial directory before
|
||||
starting. Probably only of any use with the tar <a href="smbclient.1.html#minusT"><strong>-T</strong></a> option.
|
||||
<p><br><a name="minusc"></a>
|
||||
<li><strong><strong>-c command string</strong></strong> command string is a semicolon separated
|
||||
<p><a name="minusc"></a>
|
||||
<p></p><dt><strong><strong>-c command string</strong></strong><dd> command string is a semicolon separated
|
||||
list of commands to be executed instead of prompting from stdin.
|
||||
<a href="smbclient.1.html#minusN"><strong>-N</strong></a> is implied by <strong>-c</strong>.
|
||||
<p><br>This is particularly useful in scripts and for printing stdin to the
|
||||
<p>This is particularly useful in scripts and for printing stdin to the
|
||||
server, e.g. <code>-c 'print -'</code>.
|
||||
<p><br></ul>
|
||||
<p><br><a name="OPERATIONS"></a>
|
||||
<p></dl>
|
||||
<p><a name="OPERATIONS"></a>
|
||||
<h2>OPERATIONS</h2>
|
||||
|
||||
<p><br>Once the client is running, the user is presented with a prompt :
|
||||
<p><br><code>smb:\></code>
|
||||
<p><br>The backslash ("\") indicates the current working directory on the
|
||||
<p>Once the client is running, the user is presented with a prompt :
|
||||
<p><code>smb:\></code>
|
||||
<p>The backslash ("\") indicates the current working directory on the
|
||||
server, and will change if the current working directory is changed.
|
||||
<p><br>The prompt indicates that the client is ready and waiting to carry out
|
||||
<p>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.
|
||||
<p><br>You can specify file names which have spaces in them by quoting the
|
||||
<p>You can specify file names which have spaces in them by quoting the
|
||||
name with double quotes, for example "a long file name".
|
||||
<p><br>Parameters shown in square brackets (e.g., "[parameter]") are
|
||||
<p>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.
|
||||
<p><br>Note that all commands operating on the server are actually performed
|
||||
<p>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.
|
||||
<p><br>The commands available are given here in alphabetical order.
|
||||
<p><br><ul>
|
||||
<p><br><a name="questionmark"></a> <li><strong><strong>? [command]</strong></strong> If "command" is specified,
|
||||
<p>The commands available are given here in alphabetical order.
|
||||
<p><dl>
|
||||
<p><a name="questionmark"></a> <p></p><dt><strong><strong>? [command]</strong></strong><dd> If "command" is specified,
|
||||
the <strong>?</strong> command will display a brief informative message about the
|
||||
specified command. If no command is specified, a list of available
|
||||
commands will be displayed.
|
||||
<p><br><a name="exclaimationmark"></a> <li><strong><strong>! [shell command]</strong></strong> If "shell command"
|
||||
<p><a name="exclaimationmark"></a> <p></p><dt><strong><strong>! [shell command]</strong></strong><dd> If "shell command"
|
||||
is specified, the <strong>!</strong> command will execute a shell locally and run
|
||||
the specified shell command. If no command is specified, a local shell
|
||||
will be run.
|
||||
<p><br><a name="cd"></a> <li><strong><strong>cd [directory name]</strong></strong> If "directory name" is
|
||||
<p><a name="cd"></a> <p></p><dt><strong><strong>cd [directory name]</strong></strong><dd> 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.
|
||||
<p><br>If no directory name is specified, the current working directory on
|
||||
<p>If no directory name is specified, the current working directory on
|
||||
the server will be reported.
|
||||
<p><br><a name="del"></a> <li><strong><strong>del <mask></strong></strong> The client will request that the server
|
||||
<p><a name="del"></a> <p></p><dt><strong><strong>del <mask></strong></strong><dd> The client will request that the server
|
||||
attempt to delete all files matching "mask" from the current working
|
||||
directory on the server.
|
||||
<p><br><a name="dir"></a> <li><strong><strong>dir <mask></strong></strong> A list of the files matching "mask" in
|
||||
<p><a name="dir"></a> <p></p><dt><strong><strong>dir <mask></strong></strong><dd> A list of the files matching "mask" in
|
||||
the current working directory on the server will be retrieved from the
|
||||
server and displayed.
|
||||
<p><br><a name="exit"></a> <li><strong><strong>exit</strong></strong> Terminate the connection with the server and
|
||||
<p><a name="exit"></a> <p></p><dt><strong><strong>exit</strong></strong><dd> Terminate the connection with the server and
|
||||
exit from the program.
|
||||
<p><br><a name="get"></a> <li><strong><strong>get <remote file name> [local file name]</strong></strong> Copy the
|
||||
<p><a name="get"></a> <p></p><dt><strong><strong>get <remote file name> [local file name]</strong></strong><dd> Copy the
|
||||
file called "remote file name" from the server to the machine running
|
||||
the client. If specified, name the local copy "local file name". Note
|
||||
that all transfers in smbclient are binary. See also the
|
||||
<a href="smbclient.1.html#lowercase"><strong>lowercase</strong></a> command.
|
||||
<p><br><a name="help"></a> <li><strong><strong>help [command]</strong></strong> See the <a href="smbclient.1.html#questionmark"><strong>?</strong></a>
|
||||
<p><a name="help"></a> <p></p><dt><strong><strong>help [command]</strong></strong><dd> See the <a href="smbclient.1.html#questionmark"><strong>?</strong></a>
|
||||
command above.
|
||||
<p><br><a name="lcd"></a> <li><strong><strong>lcd [directory name]</strong></strong> If "directory name" is
|
||||
<p><a name="lcd"></a> <p></p><dt><strong><strong>lcd [directory name]</strong></strong><dd> If "directory name" 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.
|
||||
<p><br>If no directory name is specified, the name of the current working
|
||||
<p>If no directory name is specified, the name of the current working
|
||||
directory on the local machine will be reported.
|
||||
<p><br><a name="lowercase"></a> <li><strong><strong>lowercase</strong></strong> Toggle lowercasing of filenames
|
||||
<p><a name="lowercase"></a> <p></p><dt><strong><strong>lowercase</strong></strong><dd> Toggle lowercasing of filenames
|
||||
for the <a href="smbclient.1.html#get"><strong>get</strong></a> and <a href="smbclient.1.html#mget"><strong>mget</strong></a> commands.
|
||||
<p><br>When lowercasing is toggled ON, local filenames are converted to
|
||||
<p>When lowercasing is toggled ON, local filenames are converted to
|
||||
lowercase when using the <a href="smbclient.1.html#get"><strong>get</strong></a> and <a href="smbclient.1.html#mget"><strong>mget</strong></a>
|
||||
commands. This is often useful when copying (say) MSDOS files from a
|
||||
server, because lowercase filenames are the norm on UNIX systems.
|
||||
<p><br><a name="ls"></a> <li><strong><strong>ls <mask></strong></strong> See the <a href="smbclient.1.html#dir"><strong>dir</strong></a> command above.
|
||||
<p><br><a name="mask"></a> <li><strong><strong>mask <mask></strong></strong> This command allows the user to set
|
||||
<p><a name="ls"></a> <p></p><dt><strong><strong>ls <mask></strong></strong><dd> See the <a href="smbclient.1.html#dir"><strong>dir</strong></a> command above.
|
||||
<p><a name="mask"></a> <p></p><dt><strong><strong>mask <mask></strong></strong><dd> This command allows the user to set
|
||||
up a mask which will be used during recursive operation of the
|
||||
<a href="smbclient.1.html#mget"><strong>mget</strong></a> and <a href="smbclient.1.html#mput"><strong>mput</strong></a> commands.
|
||||
<p><br>The masks specified to the <a href="smbclient.1.html#mget"><strong>mget</strong></a> and
|
||||
<p>The masks specified to the <a href="smbclient.1.html#mget"><strong>mget</strong></a> and
|
||||
<a href="smbclient.1.html#mput"><strong>mput</strong></a> commands act as filters for directories rather
|
||||
than files when recursion is toggled ON.
|
||||
<p><br>The mask specified with the .B mask command is necessary to filter
|
||||
<p>The mask specified with the .B mask command is necessary to filter
|
||||
files within those directories. For example, if the mask specified in
|
||||
an <a href="smbclient.1.html#mget"><strong>mget</strong></a> command is "source*" and the mask specified
|
||||
with the mask command is "*.c" and recursion is toggled ON, the
|
||||
<a href="smbclient.1.html#mget"><strong>mget</strong></a> command will retrieve all files matching "*.c" in
|
||||
all directories below and including all directories matching "source*"
|
||||
in the current working directory.
|
||||
<p><br>Note that the value for mask defaults to blank (equivalent to "*") and
|
||||
<p>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 .I mask back to "*"
|
||||
after using the <a href="smbclient.1.html#mget"><strong>mget</strong></a> or <a href="smbclient.1.html#mput"><strong>mput</strong></a> commands.
|
||||
<p><br><a name="md"></a> <li><strong><strong>md <directory name></strong></strong> See the <a href="smbclient.1.html#mkdir"><strong>mkdir</strong></a>
|
||||
<p><a name="md"></a> <p></p><dt><strong><strong>md <directory name></strong></strong><dd> See the <a href="smbclient.1.html#mkdir"><strong>mkdir</strong></a>
|
||||
command.
|
||||
<p><br><a name="mget"></a> <li><strong><strong>mget <mask></strong></strong> Copy all files matching mask from the
|
||||
<p><a name="mget"></a> <p></p><dt><strong><strong>mget <mask></strong></strong><dd> Copy all files matching mask from the
|
||||
server to the machine running the client.
|
||||
<p><br>Note that mask is interpreted differently during recursive operation
|
||||
<p>Note that mask is interpreted differently during recursive operation
|
||||
and non-recursive operation - refer to the <a href="smbclient.1.html#recurse"><strong>recurse</strong></a>
|
||||
and <a href="smbclient.1.html#mask"><strong>mask</strong></a> commands for more information. Note that all
|
||||
transfers in .B smbclient are binary. See also the
|
||||
<a href="smbclient.1.html#lowercase"><strong>lowercase</strong></a> command.
|
||||
<p><br><a name="mkdir"></a> <li><strong><strong>mkdir <directory name></strong></strong> Create a new directory on
|
||||
<p><a name="mkdir"></a> <p></p><dt><strong><strong>mkdir <directory name></strong></strong><dd> Create a new directory on
|
||||
the server (user access privileges permitting) with the specified
|
||||
name.
|
||||
<p><br><a name="mput"></a> <li><strong><strong>mput <mask></strong></strong> Copy all files matching mask in
|
||||
<p><a name="mput"></a> <p></p><dt><strong><strong>mput <mask></strong></strong><dd> Copy all files matching mask in
|
||||
the current working directory on the local machine to the current
|
||||
working directory on the server.
|
||||
<p><br>Note that mask is interpreted differently during recursive operation
|
||||
<p>Note that mask is interpreted differently during recursive operation
|
||||
and non-recursive operation - refer to the <a href="smbclient.1.html#recurse"><strong>recurse</strong></a>
|
||||
and <a href="smbclient.1.html#mask"><strong>mask</strong></a> commands for more information. Note that all
|
||||
transfers in .B smbclient are binary.
|
||||
<p><br><a name="print"></a> <li><strong><strong>print <file name></strong></strong> Print the specified file
|
||||
<p><a name="print"></a> <p></p><dt><strong><strong>print <file name></strong></strong><dd> Print the specified file
|
||||
from the local machine through a printable service on the server.
|
||||
<p><br>See also the <a href="smbclient.1.html#printmode"><strong>printmode</strong></a> command.
|
||||
<p><br><a name="printmode"></a> <li><strong><strong>printmode <graphics or text></strong></strong> Set the print
|
||||
<p>See also the <a href="smbclient.1.html#printmode"><strong>printmode</strong></a> command.
|
||||
<p><a name="printmode"></a> <p></p><dt><strong><strong>printmode <graphics or text></strong></strong><dd> 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.
|
||||
<p><br><a name="prompt"></a> <li><strong><strong>prompt</strong></strong> Toggle prompting for filenames during
|
||||
<p><a name="prompt"></a> <p></p><dt><strong><strong>prompt</strong></strong><dd> Toggle prompting for filenames during
|
||||
operation of the <a href="smbclient.1.html#mget"><strong>mget</strong></a> and <a href="smbclient.1.html#mput"><strong>mput</strong></a>
|
||||
commands.
|
||||
<p><br>When toggled ON, the user will be prompted to confirm the transfer of
|
||||
<p>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.
|
||||
<p><br><a name="put"></a> <li><strong><strong>put <local file name> [remote file name]</strong></strong> Copy the
|
||||
<p><a name="put"></a> <p></p><dt><strong><strong>put <local file name> [remote file name]</strong></strong><dd> Copy the
|
||||
file called "local file name" 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
|
||||
<a href="smbclient.1.html#lowercase"><strong>lowercase</strong></a> command.
|
||||
<p><br><a name="queue"></a> <li><strong><strong>queue</strong></strong> Displays the print queue, showing the job
|
||||
<p><a name="queue"></a> <p></p><dt><strong><strong>queue</strong></strong><dd> Displays the print queue, showing the job
|
||||
id, name, size and current status.
|
||||
<p><br><a name="quit"></a> <li><strong><strong>quit</strong></strong> See the <a href="smbclient.1.html#exit"><strong>exit</strong></a> command.
|
||||
<p><br><a name="rd"></a> <li><strong><strong>rd <directory name></strong></strong> See the <a href="smbclient.1.html#rmdir"><strong>rmdir</strong></a>
|
||||
<p><a name="quit"></a> <p></p><dt><strong><strong>quit</strong></strong><dd> See the <a href="smbclient.1.html#exit"><strong>exit</strong></a> command.
|
||||
<p><a name="rd"></a> <p></p><dt><strong><strong>rd <directory name></strong></strong><dd> See the <a href="smbclient.1.html#rmdir"><strong>rmdir</strong></a>
|
||||
command.
|
||||
<p><br><a name="recurse"></a> <li><strong><strong>recurse</strong></strong> Toggle directory recursion for the
|
||||
<p><a name="recurse"></a> <p></p><dt><strong><strong>recurse</strong></strong><dd> Toggle directory recursion for the
|
||||
commands <a href="smbclient.1.html#mget"><strong>mget</strong></a> and <a href="smbclient.1.html#mput"><strong>mput</strong></a>.
|
||||
<p><br>When toggled ON, these commands will process all directories in the
|
||||
<p>When toggled ON, these commands will process all directories in the
|
||||
source directory (i.e., the directory they are copying .IR from ) and
|
||||
will recurse into any that match the mask specified to the
|
||||
command. Only files that match the mask specified using the
|
||||
<a href="smbclient.1.html#mask"><strong>mask</strong></a> command will be retrieved. See also the
|
||||
<a href="smbclient.1.html#mask"><strong>mask</strong></a> command.
|
||||
<p><br>When recursion is toggled OFF, only files from the current working
|
||||
<p>When recursion is toggled OFF, only files from the current working
|
||||
directory on the source machine that match the mask specified to the
|
||||
<a href="smbclient.1.html#mget"><strong>mget</strong></a> or <a href="smbclient.1.html#mput"><strong>mput</strong></a> commands will be copied,
|
||||
and any mask specified using the <a href="smbclient.1.html#mask"><strong>mask</strong></a> command will be
|
||||
ignored.
|
||||
<p><br><a name="rm"></a> <li><strong><strong>rm <mask></strong></strong> Remove all files matching mask from
|
||||
<p><a name="rm"></a> <p></p><dt><strong><strong>rm <mask></strong></strong><dd> Remove all files matching mask from
|
||||
the current working directory on the server.
|
||||
<p><br><a name="rmdir"></a> <li><strong><strong>rmdir <directory name></strong></strong> Remove the specified
|
||||
<p><a name="rmdir"></a> <p></p><dt><strong><strong>rmdir <directory name></strong></strong><dd> Remove the specified
|
||||
directory (user access privileges permitting) from the server.
|
||||
<p><br><a name="tar"></a> <li><strong><strong>tar <c|x>[IXbgNa]</strong></strong> Performs a tar operation - see
|
||||
<p><a name="tar"></a> <p></p><dt><strong><strong>tar <c|x>[IXbgNa]</strong></strong><dd> Performs a tar operation - see
|
||||
the <a href="smbclient.1.html#minusT"><strong>-T</strong></a> command line option above. Behavior may be
|
||||
affected by the <a href="smbclient.1.html#tarmode"><strong>tarmode</strong></a> 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.
|
||||
<p><br><a name="blocksize"></a> <li><strong><strong>blocksize <blocksize></strong></strong> Blocksize. Must be
|
||||
<p><a name="blocksize"></a> <p></p><dt><strong><strong>blocksize <blocksize></strong></strong><dd> 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.
|
||||
<p><br><a name="tarmode"></a> <li><strong><strong>tarmode <full|inc|reset|noreset></strong></strong> Changes tar's
|
||||
<p><a name="tarmode"></a> <p></p><dt><strong><strong>tarmode <full|inc|reset|noreset></strong></strong><dd> 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).
|
||||
<p><br><a name="setmode"></a> <li><strong><strong>setmode <filename> <perm=[+|\-]rsha></strong></strong> A version
|
||||
<p><a name="setmode"></a> <p></p><dt><strong><strong>setmode <filename> <perm=[+|\-]rsha></strong></strong><dd> A version
|
||||
of the DOS attrib command to set file permissions. For example:
|
||||
<p><br><code>setmode myfile +r</code>
|
||||
<p><br>would make myfile read only.
|
||||
<p><br></ul>
|
||||
<p><br><a name="NOTES"></a>
|
||||
<p><code>setmode myfile +r</code>
|
||||
<p>would make myfile read only.
|
||||
<p></dl>
|
||||
<p><a name="NOTES"></a>
|
||||
<h2>NOTES</h2>
|
||||
|
||||
<p><br>Some servers are fussy about the case of supplied usernames,
|
||||
<p>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.
|
||||
<p><br>It is often necessary to use the <a href="smbclient.1.html#minusn"><strong>-n</strong></a> option when connecting to some
|
||||
<p>It is often necessary to use the <a href="smbclient.1.html#minusn"><strong>-n</strong></a> 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.
|
||||
<p><br>smbclient supports long file names where the server supports the
|
||||
<p>smbclient supports long file names where the server supports the
|
||||
LANMAN2 protocol or above.
|
||||
<p><br><a name="ENVIRONMENTVARIABLES"></a>
|
||||
<p><a name="ENVIRONMENTVARIABLES"></a>
|
||||
<h2>ENVIRONMENT VARIABLES</h2>
|
||||
|
||||
<p><br>The variable <strong>USER</strong> may contain the username of the person using the
|
||||
<p>The variable <strong>USER</strong> 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.
|
||||
<p><br>The variable <strong>PASSWD</strong> may contain the password of the person using
|
||||
<p>The variable <strong>PASSWD</strong> 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.
|
||||
<p><br><a name="INSTALLATION"></a>
|
||||
<p><a name="INSTALLATION"></a>
|
||||
<h2>INSTALLATION</h2>
|
||||
|
||||
<p><br>The location of the client program is a matter for individual system
|
||||
<p>The location of the client program is a matter for individual system
|
||||
administrators. The following are thus suggestions only.
|
||||
<p><br>It is recommended that the smbclient software be installed in the
|
||||
<p>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 <em>NOT</em> be setuid or
|
||||
setgid!
|
||||
<p><br>The client log files should be put in a directory readable and
|
||||
<p>The client log files should be put in a directory readable and
|
||||
writeable only by the user.
|
||||
<p><br>To test the client, you will need to know the name of a running
|
||||
<p>To test the client, you will need to know the name of a running
|
||||
SMB/CIFS server. It is possible to run <a href="smbd.8.html"><strong>smbd (8)</strong></a>
|
||||
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.
|
||||
<p><br><a name="DIAGNOSTICS"></a>
|
||||
<p><a name="DIAGNOSTICS"></a>
|
||||
<h2>DIAGNOSTICS</h2>
|
||||
|
||||
<p><br>Most diagnostics issued by the client are logged in a specified log
|
||||
<p>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.
|
||||
<p><br>The number and nature of diagnostics available depends on the debug
|
||||
<p>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.
|
||||
<p><br><a name="VERSION"></a>
|
||||
<p><a name="VERSION"></a>
|
||||
<h2>VERSION</h2>
|
||||
|
||||
<p><br>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><br><a name="AUTHOR"></a>
|
||||
<p>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><a name="AUTHOR"></a>
|
||||
<h2>AUTHOR</h2>
|
||||
|
||||
<p><br>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed
|
||||
<p>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed.
|
||||
<p><br>The original Samba man pages were written by Karl Auer. The man page
|
||||
<p>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
|
||||
<a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>)
|
||||
and updated for the Samba2.0 release by Jeremy Allison.
|
||||
<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>.
|
||||
<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
|
||||
<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>.
|
||||
<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
comments etc.
|
||||
</body>
|
||||
|
||||
@ -3,9 +3,10 @@
|
||||
|
||||
|
||||
|
||||
|
||||
<html><head><title>smbd (8)</title>
|
||||
|
||||
<link rev="made" href="mailto:samba-bugs@samba.org">
|
||||
<link rev="made" href="mailto:samba@samba.org">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
@ -15,178 +16,170 @@
|
||||
<h2>Samba</h2>
|
||||
<h2>23 Oct 1998</h2>
|
||||
|
||||
|
||||
|
||||
|
||||
<p><br><a name="NAME"></a>
|
||||
<p><a name="NAME"></a>
|
||||
<h2>NAME</h2>
|
||||
smbd - server to provide SMB/CIFS services to clients
|
||||
<p><br><a name="SYNOPSIS"></a>
|
||||
<p><a name="SYNOPSIS"></a>
|
||||
<h2>SYNOPSIS</h2>
|
||||
|
||||
<p><br><strong>smbd</strong> [<a href="smbd.8.html#minusD">-D</a>] [<a href="smbd.8.html#minusa">-a</a>] [<a href="smbd.8.html#minuso">-o</a>] [<a href="smbd.8.html#minusP">-P</a>] [<a href="smbd.8.html#minush">-h</a>] [<a href="smbd.8.html#minusV">-V</a>] [<a href="smbd.8.html#minusd">-d debuglevel</a>] [<a href="smbd.8.html#minusl">-l log file</a>] [<a href="smbd.8.html#minusp">-p port number</a>] [<a href="smbd.8.html#minusO">-O socket options</a>] [<a href="smbd.8.html#minuss">-s configuration file</a>] [<a href="smbd.8.html#minusi">-i scope</a>]
|
||||
<p><br><a name="DESCRIPTION"></a>
|
||||
<p><strong>smbd</strong> [<a href="smbd.8.html#minusD">-D</a>] [<a href="smbd.8.html#minusa">-a</a>] [<a href="smbd.8.html#minuso">-o</a>] [<a href="smbd.8.html#minusP">-P</a>] [<a href="smbd.8.html#minush">-h</a>] [<a href="smbd.8.html#minusV">-V</a>] [<a href="smbd.8.html#minusd">-d debuglevel</a>] [<a href="smbd.8.html#minusl">-l log file</a>] [<a href="smbd.8.html#minusp">-p port number</a>] [<a href="smbd.8.html#minusO">-O socket options</a>] [<a href="smbd.8.html#minuss">-s configuration file</a>]
|
||||
<p><a name="DESCRIPTION"></a>
|
||||
<h2>DESCRIPTION</h2>
|
||||
|
||||
<p><br>This program is part of the <strong>Samba</strong> suite.
|
||||
<p><br><strong>smbd</strong> is the server daemon that provides filesharing and printing
|
||||
<p>This program is part of the <strong>Samba</strong> suite.
|
||||
<p><strong>smbd</strong> is the server daemon that provides filesharing and printing
|
||||
services to
|
||||
Windows clients. The server provides filespace and printer services to
|
||||
clients using the SMB (or CIFS) protocol. This is compatible with the
|
||||
LanManager protocol, and can service LanManager clients. These
|
||||
include MSCLIENT 3.0 for DOS, Windows for Workgroups, Windows 95,
|
||||
Windows NT, OS/2, DAVE for Macintosh, and smbfs for Linux.
|
||||
<p><br>An extensive description of the services that the server can provide
|
||||
<p>An extensive description of the services that the server can provide
|
||||
is given in the man page for the configuration file controlling the
|
||||
attributes of those services (see
|
||||
<a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>. This man page
|
||||
will not describe the services, but will concentrate on the
|
||||
administrative aspects of running the server.
|
||||
<p><br>Please note that there are significant security implications to
|
||||
<p>Please note that there are significant security implications to
|
||||
running this server, and the
|
||||
<a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> manpage should be
|
||||
regarded as mandatory reading before proceeding with installation.
|
||||
<p><br>A session is created whenever a client requests one. Each client gets
|
||||
<p>A session is created whenever a client requests one. Each client gets
|
||||
a copy of the server for each session. This copy then services all
|
||||
connections made by the client during that session. When all
|
||||
connections from its client are closed, the copy of the server for
|
||||
that client terminates.
|
||||
<p><br>The configuration file, and any files that it includes, are
|
||||
<p>The configuration file, and any files that it includes, are
|
||||
automatically reloaded every minute, if they change. You can force a
|
||||
reload by sending a SIGHUP to the server. Reloading the configuration
|
||||
file will not affect connections to any service that is already
|
||||
established. Either the user will have to disconnect from the
|
||||
service, or smbd killed and restarted.
|
||||
<p><br><a name="OPTIONS"></a>
|
||||
<p><a name="OPTIONS"></a>
|
||||
<h2>OPTIONS</h2>
|
||||
|
||||
<p><br><ul>
|
||||
<p><br><a name="minusD"></a>
|
||||
<li><strong><strong>-D</strong></strong> If specified, this parameter causes the server to operate as a
|
||||
<p><dl>
|
||||
<p><a name="minusD"></a>
|
||||
<p></p><dt><strong><strong>-D</strong></strong><dd> If specified, this parameter causes the server to operate as a
|
||||
daemon. That is, it detaches itself and runs in the background,
|
||||
fielding requests on the appropriate port. Operating the server as a
|
||||
daemon is the recommended way of running smbd for servers that provide
|
||||
more than casual use file and print services.
|
||||
<p><br>By default, the server will NOT operate as a daemon.
|
||||
<p><br><a name="minusa"></a>
|
||||
<li><strong><strong>-a</strong></strong> If this parameter is specified, each new connection will
|
||||
<p>By default, the server will NOT operate as a daemon.
|
||||
<p><a name="minusa"></a>
|
||||
<p></p><dt><strong><strong>-a</strong></strong><dd> If this parameter is specified, each new connection will
|
||||
append log messages to the log file. This is the default.
|
||||
<p><br><a name="minuso"></a>
|
||||
<li><strong><strong>-o</strong></strong> If this parameter is specified, the log files will be
|
||||
<p><a name="minuso"></a>
|
||||
<p></p><dt><strong><strong>-o</strong></strong><dd> If this parameter is specified, the log files will be
|
||||
overwritten when opened. By default, the log files will be appended
|
||||
to.
|
||||
<p><br><a name="minusP"></a>
|
||||
<li><strong><strong>-P</strong></strong> Passive option. Causes smbd not to send any network traffic
|
||||
<p><a name="minusP"></a>
|
||||
<p></p><dt><strong><strong>-P</strong></strong><dd> Passive option. Causes smbd not to send any network traffic
|
||||
out. Used for debugging by the developers only.
|
||||
<p><br><a name="minush"></a>
|
||||
<li><strong><strong>-h</strong></strong> Prints the help information (usage) for <strong>smbd</strong>.
|
||||
<p><br><a name="minusV"></a>
|
||||
<li><strong><strong>-V</strong></strong> Prints the version number for <strong>smbd</strong>.
|
||||
<p><br><a name="minusd"></a>
|
||||
<li><strong><strong>-d debuglevel</strong></strong> debuglevel is an integer from 0 to 10.
|
||||
<p><br>The default value if this parameter is not specified is zero.
|
||||
<p><br>The higher this value, the more detail will be logged to the log files
|
||||
<p><a name="minush"></a>
|
||||
<p></p><dt><strong><strong>-h</strong></strong><dd> Prints the help information (usage) for <strong>smbd</strong>.
|
||||
<p><a name="minusV"></a>
|
||||
<p></p><dt><strong><strong>-V</strong></strong><dd> Prints the version number for <strong>smbd</strong>.
|
||||
<p><a name="minusd"></a>
|
||||
<p></p><dt><strong><strong>-d debuglevel</strong></strong><dd> debuglevel is an integer from 0 to 10.
|
||||
<p>The default value if this parameter is not specified is zero.
|
||||
<p>The higher this value, the more detail will be logged to the log files
|
||||
about the activities of the server. 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.
|
||||
<p><br>Levels above 1 will generate considerable amounts of log data, and
|
||||
<p>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.
|
||||
<p><br>Note that specifying this parameter here will override the <a href="smb.conf.5.html#loglevel"><strong>log
|
||||
<p>Note that specifying this parameter here will override the <a href="smb.conf.5.html#loglevel"><strong>log
|
||||
level</strong></a> parameter in the <a href="smb.conf.5.html"><strong>smb.conf
|
||||
(5)</strong></a> file.
|
||||
<p><br><a name="minusl"></a>
|
||||
<li><strong><strong>-l log file</strong></strong> If specified, <em>log file</em> specifies
|
||||
<p><a name="minusl"></a>
|
||||
<p></p><dt><strong><strong>-l log file</strong></strong><dd> If specified, <em>log file</em> specifies
|
||||
a log filename into which informational and debug messages from the
|
||||
running server will be logged. The log file generated is never removed
|
||||
by the server although its size may be controlled by the <a href="smb.conf.5.html#maxlogsize"><strong>max
|
||||
log size</strong></a> option in the <a href="smb.conf.5.html"><strong>smb.conf
|
||||
(5)</strong></a> file. The default log file name is specified
|
||||
at compile time.
|
||||
<p><br><a name="minusO"></a>
|
||||
<li><strong><strong>-O socket options</strong></strong> See the <a href="smb.conf.5.html#socketoptions"><strong>socket
|
||||
<p><a name="minusO"></a>
|
||||
<p></p><dt><strong><strong>-O socket options</strong></strong><dd> See the <a href="smb.conf.5.html#socketoptions"><strong>socket
|
||||
options</strong></a> parameter in the
|
||||
<a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> file for details.
|
||||
<p><br><a name="minusp"></a>
|
||||
<li><strong><strong>-p port number</strong></strong> port number is a positive integer value. The
|
||||
<p><a name="minusp"></a>
|
||||
<p></p><dt><strong><strong>-p port number</strong></strong><dd> port number is a positive integer value. The
|
||||
default value if this parameter is not specified is 139.
|
||||
<p><br>This number is the port number that will be used when making
|
||||
<p>This number is the port number that will be used when making
|
||||
connections to the server from client software. The standard
|
||||
(well-known) port number for the SMB over TCP is 139, hence the
|
||||
default. If you wish to run the server as an ordinary user rather than
|
||||
as root, most systems will require you to use a port number greater
|
||||
than 1024 - ask your system administrator for help if you are in this
|
||||
situation.
|
||||
<p><br>In order for the server to be useful by most clients, should you
|
||||
<p>In order for the server to be useful by most clients, should you
|
||||
configure it on a port other than 139, you will require port
|
||||
redirection services on port 139, details of which are outlined in
|
||||
rfc1002.txt section 4.3.5.
|
||||
<p><br>This parameter is not normally specified except in the above
|
||||
<p>This parameter is not normally specified except in the above
|
||||
situation.
|
||||
<p><br><a name="minuss"></a>
|
||||
<li><strong><strong>-s configuration file</strong></strong>
|
||||
<p><a name="minuss"></a>
|
||||
<p></p><dt><strong><strong>-s configuration file</strong></strong><dd>
|
||||
The file specified contains the configuration details required by the
|
||||
server. The information in this file includes server-specific
|
||||
information such as what printcap file to use, as well as descriptions
|
||||
of all the services that the server is to provide. See <strong>smb.conf
|
||||
(5)</strong> for more information.
|
||||
The default configuration file name is determined at compile time.
|
||||
<p><br><a name="minusi"></a>
|
||||
<li><strong><strong>-i scope</strong></strong> This specifies a NetBIOS scope that the server will use
|
||||
to communicate with when generating NetBIOS names. For details on the
|
||||
use of NetBIOS scopes, see rfc1001.txt and rfc1002.txt. NetBIOS scopes
|
||||
are <em>very</em> rarely used, only set this parameter if you are the
|
||||
system administrator in charge of all the NetBIOS systems you
|
||||
communicate with.
|
||||
<p><br></ul>
|
||||
<p><br><a name="FILES"></a>
|
||||
<p></dl>
|
||||
<p><a name="FILES"></a>
|
||||
<h2>FILES</h2>
|
||||
|
||||
<p><br><strong>/etc/inetd.conf</strong>
|
||||
<p><br>If the server is to be run by the inetd meta-daemon, this file must
|
||||
<p><strong>/etc/inetd.conf</strong>
|
||||
<p>If the server is to be run by the inetd meta-daemon, this file must
|
||||
contain suitable startup information for the meta-daemon. See the
|
||||
section <a href="smbd.8.html#INSTALLATION">INSTALLATION</a> below.
|
||||
<p><br><strong>/etc/rc</strong>
|
||||
<p><br>(or whatever initialization script your system uses).
|
||||
<p><br>If running the server as a daemon at startup, this file will need to
|
||||
<p><strong>/etc/rc</strong>
|
||||
<p>(or whatever initialization script your system uses).
|
||||
<p>If running the server as a daemon at startup, this file will need to
|
||||
contain an appropriate startup sequence for the server. See the
|
||||
section <a href="smbd.8.html#INSTALLATION">INSTALLATION</a> below.
|
||||
<p><br><strong>/etc/services</strong>
|
||||
<p><br>If running the server via the meta-daemon inetd, this file must
|
||||
<p><strong>/etc/services</strong>
|
||||
<p>If running the server via the meta-daemon inetd, this file must
|
||||
contain a mapping of service name (e.g., netbios-ssn) to service port
|
||||
(e.g., 139) and protocol type (e.g., tcp). See the section
|
||||
<a href="smbd.8.html#INSTALLATION">INSTALLATION</a> below.
|
||||
<p><br><strong>/usr/local/samba/lib/smb.conf</strong>
|
||||
<p><br>This is the default location of the <em>smb.conf</em> server configuration
|
||||
<p><strong>/usr/local/samba/lib/smb.conf</strong>
|
||||
<p>This is the default location of the <em>smb.conf</em> server configuration
|
||||
file. Other common places that systems install this file are
|
||||
<em>/usr/samba/lib/smb.conf</em> and <em>/etc/smb.conf</em>.
|
||||
<p><br>This file describes all the services the server is to make available
|
||||
<p>This file describes all the services the server is to make available
|
||||
to clients. See <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> for more information.
|
||||
<p><br><a name="LIMITATIONS"></a>
|
||||
<p><a name="LIMITATIONS"></a>
|
||||
<h2>LIMITATIONS</h2>
|
||||
|
||||
<p><br>On some systems <strong>smbd</strong> cannot change uid back to root after a
|
||||
<p>On some systems <strong>smbd</strong> cannot change uid back to root after a
|
||||
setuid() call. Such systems are called "trapdoor" uid systems. If you
|
||||
have such a system, you will be unable to connect from a client (such
|
||||
as a PC) as two different users at once. Attempts to connect the
|
||||
second user will result in "access denied" or similar.
|
||||
<p><br><a name="ENVIRONMENTVARIABLES"></a>
|
||||
<p><a name="ENVIRONMENTVARIABLES"></a>
|
||||
<h2>ENVIRONMENT VARIABLES</h2>
|
||||
|
||||
<p><br><strong>PRINTER</strong>
|
||||
<p><br>If no printer name is specified to printable services, most systems
|
||||
<p><strong>PRINTER</strong>
|
||||
<p>If no printer name is specified to printable services, most systems
|
||||
will use the value of this variable (or "lp" if this variable is not
|
||||
defined) as the name of the printer to use. This is not specific to
|
||||
the server, however.
|
||||
<p><br><a name="INSTALLATION"></a>
|
||||
<p><a name="INSTALLATION"></a>
|
||||
<h2>INSTALLATION</h2>
|
||||
|
||||
<p><br>The location of the server and its support files is a matter for
|
||||
<p>The location of the server and its support files is a matter for
|
||||
individual system administrators. The following are thus suggestions
|
||||
only.
|
||||
<p><br>It is recommended that the server software be installed under the
|
||||
<p>It is recommended that the server software be installed under the
|
||||
/usr/local/samba hierarchy, in a directory readable by all, writeable
|
||||
only by root. The server program itself should be executable by all,
|
||||
as users may wish to run the server themselves (in which case it will
|
||||
@ -200,93 +193,93 @@ fix has only been confirmed on old versions (pre-kernel 2.0) of Linux
|
||||
at the time this was written. It is possible that this hole only
|
||||
exists in Linux, as testing on other systems has thus far shown them
|
||||
to be immune.
|
||||
<p><br>The server log files should be put in a directory readable and
|
||||
<p>The server log files should be put in a directory readable and
|
||||
writeable only by root, as the log files may contain sensitive
|
||||
information.
|
||||
<p><br>The configuration file should be placed in a directory readable and
|
||||
<p>The configuration file should be placed in a directory readable and
|
||||
writeable only by root, as the configuration file controls security for
|
||||
the services offered by the server. The configuration file can be made
|
||||
readable by all if desired, but this is not necessary for correct
|
||||
operation of the server and is not recommended. A sample configuration
|
||||
file "smb.conf.sample" is supplied with the source to the server -
|
||||
this may be renamed to "smb.conf" and modified to suit your needs.
|
||||
<p><br>The remaining notes will assume the following:
|
||||
<p><br><ul>
|
||||
<p><br><li > <strong>smbd</strong> (the server program) installed in /usr/local/samba/bin
|
||||
<p><br><li > <strong>smb.conf</strong> (the configuration file) installed in /usr/local/samba/lib
|
||||
<p><br><li > log files stored in /var/adm/smblogs
|
||||
<p><br></ul>
|
||||
<p><br>The server may be run either as a daemon by users or at startup, or it
|
||||
<p>The remaining notes will assume the following:
|
||||
<p><dl>
|
||||
<p><li > <strong>smbd</strong> (the server program) installed in /usr/local/samba/bin
|
||||
<p><li > <strong>smb.conf</strong> (the configuration file) installed in /usr/local/samba/lib
|
||||
<p><li > log files stored in /var/adm/smblogs
|
||||
<p></dl>
|
||||
<p>The server may be run either as a daemon by users or at startup, or it
|
||||
may be run from a meta-daemon such as inetd upon request. If run as a
|
||||
daemon, the server will always be ready, so starting sessions will be
|
||||
faster. If run from a meta-daemon some memory will be saved and
|
||||
utilities such as the tcpd TCP-wrapper may be used for extra security.
|
||||
For serious use as file server it is recommended that <strong>smbd</strong> be run
|
||||
as a daemon.
|
||||
<p><br>When you've decided, continue with either
|
||||
<p>When you've decided, continue with either
|
||||
<a href="smbd.8.html#RUNNINGTHESERVERASADAEMON">RUNNING THE SERVER AS A DAEMON</a> or
|
||||
<a href="smbd.8.html#RUNNINGTHESERVERONREQUEST">RUNNING THE SERVER ON REQUEST</a>.
|
||||
<p><br><a name="RUNNINGTHESERVERASADAEMON"></a>
|
||||
<p><a name="RUNNINGTHESERVERASADAEMON"></a>
|
||||
<h2>RUNNING THE SERVER AS A DAEMON</h2>
|
||||
|
||||
<p><br>To run the server as a daemon from the command line, simply put the
|
||||
<p>To run the server as a daemon from the command line, simply put the
|
||||
<a href="smbd.8.html#minusD"><strong>-D</strong></a> option on the command line. There is no need to place an
|
||||
ampersand at the end of the command line - the <a href="smbd.8.html#minusD"><strong>-D</strong></a> option causes
|
||||
the server to detach itself from the tty anyway.
|
||||
<p><br>Any user can run the server as a daemon (execute permissions
|
||||
<p>Any user can run the server as a daemon (execute permissions
|
||||
permitting, of course). This is useful for testing purposes, and may
|
||||
even be useful as a temporary substitute for something like ftp. When
|
||||
run this way, however, the server will only have the privileges of the
|
||||
user who ran it.
|
||||
<p><br>To ensure that the server is run as a daemon whenever the machine is
|
||||
<p>To ensure that the server is run as a daemon whenever the machine is
|
||||
started, and to ensure that it runs as root so that it can serve
|
||||
multiple clients, you will need to modify the system startup
|
||||
files. Wherever appropriate (for example, in /etc/rc), insert the
|
||||
following line, substituting port number, log file location,
|
||||
configuration file location and debug level as desired:
|
||||
<p><br><code>/usr/local/samba/bin/smbd -D -l /var/adm/smblogs/log -s /usr/local/samba/lib/smb.conf</code>
|
||||
<p><br>(The above should appear in your initialization script as a single line.
|
||||
<p><code>/usr/local/samba/bin/smbd -D -l /var/adm/smblogs/log -s /usr/local/samba/lib/smb.conf</code>
|
||||
<p>(The above should appear in your initialization script as a single line.
|
||||
Depending on your terminal characteristics, it may not appear that way in
|
||||
this man page. If the above appears as more than one line, please treat any
|
||||
newlines or indentation as a single space or TAB character.)
|
||||
<p><br>If the options used at compile time are appropriate for your system,
|
||||
<p>If the options used at compile time are appropriate for your system,
|
||||
all parameters except <a href="smbd.8.html#minusD"><strong>-D</strong></a> may be
|
||||
omitted. See the section <a href="smbd.8.html#OPTIONS">OPTIONS</a> above.
|
||||
<p><br><a name="RUNNINGTHESERVERONREQUEST"></a>
|
||||
<p><a name="RUNNINGTHESERVERONREQUEST"></a>
|
||||
<h2>RUNNING THE SERVER ON REQUEST</h2>
|
||||
|
||||
<p><br>If your system uses a meta-daemon such as <strong>inetd</strong>, you can arrange to
|
||||
<p>If your system uses a meta-daemon such as <strong>inetd</strong>, you can arrange to
|
||||
have the smbd server started whenever a process attempts to connect to
|
||||
it. This requires several changes to the startup files on the host
|
||||
machine. If you are experimenting as an ordinary user rather than as
|
||||
root, you will need the assistance of your system administrator to
|
||||
modify the system files.
|
||||
<p><br>You will probably want to set up the NetBIOS name server <a href="nmbd.8.html"><strong>nmbd</strong></a> at
|
||||
<p>You will probably want to set up the NetBIOS name server <a href="nmbd.8.html"><strong>nmbd</strong></a> at
|
||||
the same time as <strong>smbd</strong>. To do this refer to the man page for
|
||||
<a href="nmbd.8.html"><strong>nmbd (8)</strong></a>.
|
||||
<p><br>First, ensure that a port is configured in the file <code>/etc/services</code>. The
|
||||
<p>First, ensure that a port is configured in the file <code>/etc/services</code>. The
|
||||
well-known port 139 should be used if possible, though any port may be
|
||||
used.
|
||||
<p><br>Ensure that a line similar to the following is in <code>/etc/services</code>:
|
||||
<p><br><code>netbios-ssn 139/tcp</code>
|
||||
<p><br>Note for NIS/YP users - you may need to rebuild the NIS service maps
|
||||
<p>Ensure that a line similar to the following is in <code>/etc/services</code>:
|
||||
<p><code>netbios-ssn 139/tcp</code>
|
||||
<p>Note for NIS/YP users - you may need to rebuild the NIS service maps
|
||||
rather than alter your local <code>/etc/services file</code>.
|
||||
<p><br>Next, put a suitable line in the file <code>/etc/inetd.conf</code> (in the unlikely
|
||||
<p>Next, put a suitable line in the file <code>/etc/inetd.conf</code> (in the unlikely
|
||||
event that you are using a meta-daemon other than inetd, you are on
|
||||
your own). Note that the first item in this line matches the service
|
||||
name in <code>/etc/services</code>. Substitute appropriate values for your system
|
||||
in this line (see <strong>inetd (8)</strong>):
|
||||
<p><br><code>netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd -d1 -l/var/adm/smblogs/log -s/usr/local/samba/lib/smb.conf</code>
|
||||
<p><br>(The above should appear in <code>/etc/inetd.conf</code> as a single
|
||||
<p><code>netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd -d1 -l/var/adm/smblogs/log -s/usr/local/samba/lib/smb.conf</code>
|
||||
<p>(The above should appear in <code>/etc/inetd.conf</code> as a single
|
||||
line. Depending on your terminal characteristics, it may not appear
|
||||
that way in this man page. If the above appears as more than one
|
||||
line, please treat any newlines or indentation as a single space or
|
||||
TAB character.)
|
||||
<p><br>Note that there is no need to specify a port number here, even if you
|
||||
<p>Note that there is no need to specify a port number here, even if you
|
||||
are using a non-standard port number.
|
||||
<p><br>Lastly, edit the configuration file to provide suitable services. To
|
||||
<p>Lastly, edit the configuration file to provide suitable services. To
|
||||
start with, the following two services should be all you need:
|
||||
<p><br><pre>
|
||||
<p><pre>
|
||||
|
||||
|
||||
[homes]
|
||||
@ -301,85 +294,85 @@ start with, the following two services should be all you need:
|
||||
|
||||
</pre>
|
||||
|
||||
<p><br>This will allow you to connect to your home directory and print to any
|
||||
<p>This will allow you to connect to your home directory and print to any
|
||||
printer supported by the host (user privileges permitting).
|
||||
<p><br><a name="TESTINGTHEINSTALLATION"></a>
|
||||
<p><a name="TESTINGTHEINSTALLATION"></a>
|
||||
<h2>TESTING THE INSTALLATION</h2>
|
||||
|
||||
<p><br>If running the server as a daemon, execute it before proceeding. If
|
||||
<p>If running the server as a daemon, execute it before proceeding. If
|
||||
using a meta-daemon, either restart the system or kill and restart the
|
||||
meta-daemon. Some versions of inetd will reread their configuration
|
||||
tables if they receive a HUP signal.
|
||||
<p><br>If your machine's name is "fred" and your name is "mary", you should
|
||||
<p>If your machine's name is "fred" and your name is "mary", you should
|
||||
now be able to connect to the service <code>\\fred\mary</code>.
|
||||
<p><br>To properly test and experiment with the server, we recommend using
|
||||
<p>To properly test and experiment with the server, we recommend using
|
||||
the smbclient program (see
|
||||
<a href="smbclient.1.html"><strong>smbclient (1)</strong></a>) and also going through
|
||||
the steps outlined in the file <em>DIAGNOSIS.txt</em> in the <em>docs/</em>
|
||||
directory of your Samba installation.
|
||||
<p><br><a name="VERSION"></a>
|
||||
<p><a name="VERSION"></a>
|
||||
<h2>VERSION</h2>
|
||||
|
||||
<p><br>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><br><a name="DIAGNOSTICS"></a>
|
||||
<p>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><a name="DIAGNOSTICS"></a>
|
||||
<h2>DIAGNOSTICS</h2>
|
||||
|
||||
<p><br>Most diagnostics issued by the server are logged in a specified log
|
||||
<p>Most diagnostics issued by the server are logged in a specified log
|
||||
file. The log file name is specified at compile time, but may be
|
||||
overridden on the command line.
|
||||
<p><br>The number and nature of diagnostics available depends on the debug
|
||||
<p>The number and nature of diagnostics available depends on the debug
|
||||
level used by the server. If you have problems, set the debug level to
|
||||
3 and peruse the log files.
|
||||
<p><br>Most messages are reasonably self-explanatory. Unfortunately, at the time
|
||||
<p>Most messages are reasonably self-explanatory. Unfortunately, at the time
|
||||
this man page was created, there are too many diagnostics available
|
||||
in the source code to warrant describing each and every diagnostic. At
|
||||
this stage your best bet is still to grep the source code and inspect
|
||||
the conditions that gave rise to the diagnostics you are seeing.
|
||||
<p><br><a name="SIGNALS"></a>
|
||||
<p><a name="SIGNALS"></a>
|
||||
<h2>SIGNALS</h2>
|
||||
|
||||
<p><br>Sending the smbd a SIGHUP will cause it to re-load its smb.conf
|
||||
<p>Sending the smbd a SIGHUP will cause it to re-load its smb.conf
|
||||
configuration file within a short period of time.
|
||||
<p><br>To shut down a users smbd process it is recommended that SIGKILL (-9)
|
||||
<p>To shut down a users smbd process it is recommended that SIGKILL (-9)
|
||||
<em>NOT</em> be used, except as a last resort, as this may leave the shared
|
||||
memory area in an inconsistent state. The safe way to terminate an
|
||||
smbd is to send it a SIGTERM (-15) signal and wait for it to die on
|
||||
its own.
|
||||
<p><br>The debug log level of smbd may be raised
|
||||
<p>The debug log level of smbd may be raised
|
||||
by sending it a SIGUSR1 <code>(kill -USR1 <smbd-pid>)</code> and lowered by
|
||||
sending it a SIGUSR2 <code>(kill -USR2 <smbd-pid>)</code>. This is to allow
|
||||
transient problems to be diagnosed, whilst still running at a normally
|
||||
low log level.
|
||||
<p><br>Note that as the signal handlers send a debug write, they are not
|
||||
<p>Note that as the signal handlers send a debug write, they are not
|
||||
re-entrant in smbd. This you should wait until smbd is in a state of
|
||||
waiting for an incoming smb before issuing them. It is possible to
|
||||
make the signal handlers safe by un-blocking the signals before the
|
||||
select call and re-blocking them after, however this would affect
|
||||
performance.
|
||||
<p><br><a name="SEEALSO"></a>
|
||||
<p><a name="SEEALSO"></a>
|
||||
<h2>SEE ALSO</h2>
|
||||
|
||||
<p><br><strong>hosts_access (5)</strong>, <strong>inetd (8)</strong>, <a href="nmbd.8.html"><strong>nmbd (8)</strong></a>,
|
||||
<p><strong>hosts_access (5)</strong>, <strong>inetd (8)</strong>, <a href="nmbd.8.html"><strong>nmbd (8)</strong></a>,
|
||||
<a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>, <a href="smbclient.1.html"><strong>smbclient
|
||||
(1)</strong></a>, <a href="testparm.1.html"><strong>testparm (1)</strong></a>,
|
||||
<a href="testprns.1.html"><strong>testprns (1)</strong></a>, and the Internet RFC's
|
||||
<strong>rfc1001.txt</strong>, <strong>rfc1002.txt</strong>. In addition the CIFS (formerly SMB)
|
||||
specification is available as a link from the Web page :
|
||||
<a href="http://samba.org/cifs/">http://samba.org/cifs/</a>.
|
||||
<p><br><a name="AUTHOR"></a>
|
||||
<p><a name="AUTHOR"></a>
|
||||
<h2>AUTHOR</h2>
|
||||
|
||||
<p><br>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed
|
||||
<p>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed.
|
||||
<p><br>The original Samba man pages were written by Karl Auer. The man page
|
||||
<p>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
|
||||
<a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>)
|
||||
and updated for the Samba2.0 release by Jeremy Allison.
|
||||
<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>.
|
||||
<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full list of contributors
|
||||
<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>.
|
||||
<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full list of contributors
|
||||
and details on how to submit bug reports, comments etc.
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -3,9 +3,10 @@
|
||||
|
||||
|
||||
|
||||
|
||||
<html><head><title>smbpasswd (5)</title>
|
||||
|
||||
<link rev="made" href="mailto:samba-bugs@samba.org">
|
||||
<link rev="made" href="mailto:samba@samba.org">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
@ -15,47 +16,46 @@
|
||||
<h2>Samba</h2>
|
||||
<h2>23 Oct 1998</h2>
|
||||
|
||||
|
||||
|
||||
|
||||
<p><br><a name="NAME"></a>
|
||||
<p><a name="NAME"></a>
|
||||
<h2>NAME</h2>
|
||||
smbpasswd - The Samba encrypted password file
|
||||
<p><br><a name="SYNOPSIS"></a>
|
||||
<p><a name="SYNOPSIS"></a>
|
||||
<h2>SYNOPSIS</h2>
|
||||
|
||||
<p><br>smbpasswd is the <strong>Samba</strong> encrypted password file.
|
||||
<p><br><a name="DESCRIPTION"></a>
|
||||
<p>smbpasswd is the <strong>Samba</strong> encrypted password file.
|
||||
<p><a name="DESCRIPTION"></a>
|
||||
<h2>DESCRIPTION</h2>
|
||||
|
||||
<p><br>This file is part of the <strong>Samba</strong> suite.
|
||||
<p><br>smbpasswd is the <strong>Samba</strong> encrypted password file. It contains
|
||||
<p>This file is part of the <strong>Samba</strong> suite.
|
||||
<p>smbpasswd is the <strong>Samba</strong> encrypted password file. It contains
|
||||
the username, Unix user id and the SMB hashed passwords of the
|
||||
user, as well as account flag information and the time the password
|
||||
was last changed. This file format has been evolving with Samba
|
||||
and has had several different formats in the past.
|
||||
<p><br><a name="FILEFORMAT"></a>
|
||||
<p><a name="FILEFORMAT"></a>
|
||||
<h2>FILE FORMAT</h2>
|
||||
|
||||
<p><br>The format of the smbpasswd file used by Samba 2.0 is very similar to
|
||||
<p>The format of the smbpasswd file used by Samba 2.0 is very similar to
|
||||
the familiar Unix <strong>passwd (5)</strong> file. It is an ASCII file containing
|
||||
one line for each user. Each field within each line is separated from
|
||||
the next by a colon. Any entry beginning with # is ignored. The
|
||||
smbpasswd file contains the following information for each user:
|
||||
<p><br><ul>
|
||||
<p><br><a name="name"></a>
|
||||
<li><strong><strong>name</strong></strong> <br> <br>
|
||||
<p><br>This is the user name. It must be a name that already exists
|
||||
<p><dl>
|
||||
<p><a name="name"></a>
|
||||
<p></p><dt><strong><strong>name</strong></strong><dd> <br> <br>
|
||||
<p>This is the user name. It must be a name that already exists
|
||||
in the standard UNIX passwd file.
|
||||
<p><br><a name="uid"></a>
|
||||
<li><strong><strong>uid</strong></strong> <br> <br>
|
||||
<p><br>This is the UNIX uid. It must match the uid field for the same
|
||||
<p><a name="uid"></a>
|
||||
<p></p><dt><strong><strong>uid</strong></strong><dd> <br> <br>
|
||||
<p>This is the UNIX uid. It must match the uid field for the same
|
||||
user entry in the standard UNIX passwd file. If this does not
|
||||
match then Samba will refuse to recognize this <strong>smbpasswd</strong> file entry
|
||||
as being valid for a user.
|
||||
<p><br><a name="LanmanPasswordHash"></a>
|
||||
<li><strong><strong>Lanman Password Hash</strong></strong> <br> <br>
|
||||
<p><br>This is the <em>LANMAN</em> hash of the users password, encoded as 32 hex
|
||||
<p><a name="LanmanPasswordHash"></a>
|
||||
<p></p><dt><strong><strong>Lanman Password Hash</strong></strong><dd> <br> <br>
|
||||
<p>This is the <em>LANMAN</em> hash of the users password, encoded as 32 hex
|
||||
digits. The <em>LANMAN</em> hash is created by DES encrypting a well known
|
||||
string with the users password as the DES key. This is the same
|
||||
password used by Windows 95/98 machines. Note that this password hash
|
||||
@ -67,7 +67,7 @@ smbpasswd file contains the following information for each user:
|
||||
is equal to 32 <code>'X'</code> characters then the users account is marked as
|
||||
<em>disabled</em> and the user will not be able to log onto the Samba
|
||||
server.
|
||||
<p><br><em>WARNING !!</em>. Note that, due to the challenge-response nature of the
|
||||
<p><em>WARNING !!</em>. Note that, due to the challenge-response nature of the
|
||||
SMB/CIFS authentication protocol, anyone with a knowledge of this
|
||||
password hash will be able to impersonate the user on the network.
|
||||
For this reason these hashes are known as <em>"plain text equivalent"</em>
|
||||
@ -76,19 +76,19 @@ smbpasswd file contains the following information for each user:
|
||||
directory with read and traverse access only to the root user and the
|
||||
<strong>smbpasswd</strong> file itself must be set to be read/write only by root,
|
||||
with no other access.
|
||||
<p><br><a name="NTPasswordHash"></a>
|
||||
<li><strong><strong>NT Password Hash</strong></strong> <br> <br>
|
||||
<p><br>This is the <em>Windows NT</em> hash of the users password, encoded as 32
|
||||
<p><a name="NTPasswordHash"></a>
|
||||
<p></p><dt><strong><strong>NT Password Hash</strong></strong><dd> <br> <br>
|
||||
<p>This is the <em>Windows NT</em> hash of the users password, encoded as 32
|
||||
hex digits. The <em>Windows NT</em> hash is created by taking the users
|
||||
password as represented in 16-bit, little-endian UNICODE and then
|
||||
applying the <em>MD4</em> (internet rfc1321) hashing algorithm to it.
|
||||
<p><br>This password hash is considered more secure than the <a href="smbpasswd.5.html#LanmanPasswordHash"><strong>Lanman
|
||||
<p>This password hash is considered more secure than the <a href="smbpasswd.5.html#LanmanPasswordHash"><strong>Lanman
|
||||
Password Hash</strong></a> as it preserves the case of the
|
||||
password and uses a much higher quality hashing algorithm. However, it
|
||||
is still the case that if two users choose the same password this
|
||||
entry will be identical (i.e. the password is not <em>"salted"</em> as the
|
||||
UNIX password is).
|
||||
<p><br><em>WARNING !!</em>. Note that, due to the challenge-response nature of the
|
||||
<p><em>WARNING !!</em>. Note that, due to the challenge-response nature of the
|
||||
SMB/CIFS authentication protocol, anyone with a knowledge of this
|
||||
password hash will be able to impersonate the user on the network.
|
||||
For this reason these hashes are known as <em>"plain text equivalent"</em>
|
||||
@ -97,48 +97,48 @@ smbpasswd file contains the following information for each user:
|
||||
directory with read and traverse access only to the root user and the
|
||||
<strong>smbpasswd</strong> file itself must be set to be read/write only by root,
|
||||
with no other access.
|
||||
<p><br><a name="AccountFlags"></a>
|
||||
<li><strong><strong>Account Flags</strong></strong> <br> <br>
|
||||
<p><br>This section contains flags that describe the attributes of the users
|
||||
<p><a name="AccountFlags"></a>
|
||||
<p></p><dt><strong><strong>Account Flags</strong></strong><dd> <br> <br>
|
||||
<p>This section contains flags that describe the attributes of the users
|
||||
account. In the <strong>Samba2.0</strong> release this field is bracketed by <code>'['</code>
|
||||
and <code>']'</code> characters and is always 13 characters in length (including
|
||||
the <code>'['</code> and <code>']'</code> characters). The contents of this field may be
|
||||
any of the characters.
|
||||
<p><br><ul>
|
||||
<p><br><a name="capU"></a>
|
||||
<p><dl>
|
||||
<p><a name="capU"></a>
|
||||
<li > <strong>'U'</strong> This means this is a <em>"User"</em> account, i.e. an ordinary
|
||||
user. Only <strong>User</strong> and <a href="smbpasswd.5.html#capW"><strong>Workstation Trust</strong></a> accounts are
|
||||
currently supported in the <strong>smbpasswd</strong> file.
|
||||
<p><br><a name="capN"></a>
|
||||
<p><a name="capN"></a>
|
||||
<li > <strong>'N'</strong> This means the account has <em>no</em> password (the passwords
|
||||
in the fields <a href="smbpasswd.5.html#LanmanPasswordHash"><strong>Lanman Password Hash</strong></a> and
|
||||
<a href="smbpasswd.5.html#NTPasswordHash"><strong>NT Password Hash</strong></a> are ignored). Note that this
|
||||
will only allow users to log on with no password if the
|
||||
<a href="smb.conf.5.html#nullpasswords"><strong>null passwords</strong></a> parameter is set
|
||||
in the <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> config file.
|
||||
<p><br><a name="capD"></a>
|
||||
<p><a name="capD"></a>
|
||||
<li > <strong>'D'</strong> This means the account is disabled and no SMB/CIFS logins
|
||||
will be allowed for this user.
|
||||
<p><br><a name="capW"></a>
|
||||
<p><a name="capW"></a>
|
||||
<li > <strong>'W'</strong> This means this account is a <em>"Workstation Trust"</em> account.
|
||||
This kind of account is used in the Samba PDC code stream to allow Windows
|
||||
NT Workstations and Servers to join a Domain hosted by a Samba PDC.
|
||||
<p><br></ul>
|
||||
<p><br>Other flags may be added as the code is extended in future. The rest of
|
||||
<p></dl>
|
||||
<p>Other flags may be added as the code is extended in future. The rest of
|
||||
this field space is filled in with spaces.
|
||||
<p><br><a name="LastChangeTime"></a>
|
||||
<li><strong><strong>Last Change Time</strong></strong> <br> <br>
|
||||
<p><br>This field consists of the time the account was last modified. It consists of
|
||||
<p><a name="LastChangeTime"></a>
|
||||
<p></p><dt><strong><strong>Last Change Time</strong></strong><dd> <br> <br>
|
||||
<p>This field consists of the time the account was last modified. It consists of
|
||||
the characters <code>LCT-</code> (standing for <em>"Last Change Time"</em>) followed by a numeric
|
||||
encoding of the UNIX time in seconds since the epoch (1970) that the last change
|
||||
was made.
|
||||
<p><br><li><strong><strong>Following fields</strong></strong> <br> <br>
|
||||
<p><br>All other colon separated fields are ignored at this time.
|
||||
<p><br></ul>
|
||||
<p><br><a name="NOTES"></a>
|
||||
<p><p></p><dt><strong><strong>Following fields</strong></strong><dd> <br> <br>
|
||||
<p>All other colon separated fields are ignored at this time.
|
||||
<p></dl>
|
||||
<p><a name="NOTES"></a>
|
||||
<h2>NOTES</h2>
|
||||
|
||||
<p><br>In previous versions of Samba (notably the 1.9.18 series) this file
|
||||
<p>In previous versions of Samba (notably the 1.9.18 series) this file
|
||||
did not contain the <a href="smbpasswd.5.html#AccountFlags"><strong>Account Flags</strong></a> or
|
||||
<a href="smbpasswd.5.html#LastChangeTime"><strong>Last Change Time</strong></a> fields. The Samba 2.0
|
||||
code will read and write these older password files but will not be able to
|
||||
@ -147,11 +147,11 @@ modify the old entries to add the new fields. New entries added with
|
||||
in the added accounts however. Thus an older <strong>smbpasswd</strong> file used
|
||||
with Samba 2.0 may end up with some accounts containing the new fields
|
||||
and some not.
|
||||
<p><br>In order to convert from an old-style <strong>smbpasswd</strong> file to a new
|
||||
<p>In order to convert from an old-style <strong>smbpasswd</strong> file to a new
|
||||
style, run the script <strong>convert_smbpasswd</strong>, installed in the
|
||||
Samba <code>bin/</code> directory (the same place that the <a href="smbd.8.html"><strong>smbd</strong></a>
|
||||
and <a href="nmbd.8.html"><strong>nmbd</strong></a> binaries are installed) as follows:
|
||||
<p><br><pre>
|
||||
<p><pre>
|
||||
|
||||
|
||||
cat old_smbpasswd_file | convert_smbpasswd > new_smbpasswd_file
|
||||
@ -159,36 +159,36 @@ and <a href="nmbd.8.html"><strong>nmbd</strong></a> binaries are installed) as f
|
||||
|
||||
</pre>
|
||||
|
||||
<p><br>The <strong>convert_smbpasswd</strong> script reads from stdin and writes to stdout
|
||||
<p>The <strong>convert_smbpasswd</strong> script reads from stdin and writes to stdout
|
||||
so as not to overwrite any files by accident.
|
||||
<p><br>Once this script has been run, check the contents of the new smbpasswd
|
||||
<p>Once this script has been run, check the contents of the new smbpasswd
|
||||
file to ensure that it has not been damaged by the conversion script
|
||||
(which uses <strong>awk</strong>), and then replace the <code><old smbpasswd file></code>
|
||||
with the <code><new smbpasswd file></code>.
|
||||
<p><br><a name="VERSION"></a>
|
||||
<p><a name="VERSION"></a>
|
||||
<h2>VERSION</h2>
|
||||
|
||||
<p><br>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><br><a name="SEEALSO"></a>
|
||||
<p>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><a name="SEEALSO"></a>
|
||||
<h2>SEE ALSO</h2>
|
||||
|
||||
<p><br><a href="smbpasswd.8.html"><strong>smbpasswd (8)</strong></a>, <a href="samba.7.html"><strong>samba
|
||||
<p><a href="smbpasswd.8.html"><strong>smbpasswd (8)</strong></a>, <a href="samba.7.html"><strong>samba
|
||||
(7)</strong></a>, and the Internet RFC1321 for details on the MD4
|
||||
algorithm.
|
||||
<p><br><a name="AUTHOR"></a>
|
||||
<p><a name="AUTHOR"></a>
|
||||
<h2>AUTHOR</h2>
|
||||
|
||||
<p><br>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed
|
||||
<p>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed.
|
||||
<p><br>The original Samba man pages were written by Karl Auer. The man page
|
||||
<p>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
|
||||
<a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>)
|
||||
and updated for the Samba2.0 release by Jeremy
|
||||
Allison, <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>.
|
||||
<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
|
||||
Allison, <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>.
|
||||
<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
comments etc.
|
||||
</body>
|
||||
|
||||
@ -3,9 +3,10 @@
|
||||
|
||||
|
||||
|
||||
|
||||
<html><head><title>smbpasswd (8)</title>
|
||||
|
||||
<link rev="made" href="mailto:samba-bugs@samba.org">
|
||||
<link rev="made" href="mailto:samba@samba.org">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
@ -15,25 +16,24 @@
|
||||
<h2>Samba</h2>
|
||||
<h2>23 Oct 1998</h2>
|
||||
|
||||
|
||||
|
||||
|
||||
<p><br><a name="NAME"></a>
|
||||
<p><a name="NAME"></a>
|
||||
<h2>NAME</h2>
|
||||
smbpasswd - change a users SMB password
|
||||
<p><br><a name="SYNOPSIS"></a>
|
||||
<p><a name="SYNOPSIS"></a>
|
||||
<h2>SYNOPSIS</h2>
|
||||
|
||||
<p><br><strong>smbpasswd</strong> [<a href="smbpasswd.8.html#minusa">-a</a>] [<a href="smbpasswd.8.html#minusd">-d</a>] [<a href="smbpasswd.8.html#minuse">-e</a>] [<a href="smbpasswd.8.html#minusD">-D debug level</a>] [<a href="smbpasswd.8.html#minusn">-n</a>] [<a href="smbpasswd.8.html#minusr">-r remote_machine</a>] [<a href="smbpasswd.8.html#minusR">-R name resolve order</a>] [<a href="smbpasswd.8.html#minusm">-m</a>] [<a href="smbpasswd.8.html#minusj">-j DOMAIN</a>] [<a href="smbpasswd.8.html#minusU">-U username</a>] [<a href="smbpasswd.8.html#minush">-h</a>] [<a href="smbpasswd.8.html#minuss">-s</a>] <a href="smbpasswd.8.html#username">username</a>
|
||||
<p><br><a name="DESCRIPTION"></a>
|
||||
<p><strong>smbpasswd</strong> [<a href="smbpasswd.8.html#minusa">-a</a>] [<a href="smbpasswd.8.html#minusx">-x</a>] [<a href="smbpasswd.8.html#minusd">-d</a>] [<a href="smbpasswd.8.html#minuse">-e</a>] [<a href="smbpasswd.8.html#minusD">-D debug level</a>] [<a href="smbpasswd.8.html#minusn">-n</a>] [<a href="smbpasswd.8.html#minusr">-r remote_machine</a>] [<a href="smbpasswd.8.html#minusR">-R name resolve order</a>] [<a href="smbpasswd.8.html#minusm">-m</a>] [<a href="smbpasswd.8.html#minusj">-j DOMAIN</a>] [<a href="smbpasswd.8.html#minusU">-U username</a>] [<a href="smbpasswd.8.html#minush">-h</a>] [<a href="smbpasswd.8.html#minuss">-s</a>] <a href="smbpasswd.8.html#username">username</a>
|
||||
<p><a name="DESCRIPTION"></a>
|
||||
<h2>DESCRIPTION</h2>
|
||||
|
||||
<p><br>This program is part of the <strong>Samba</strong> suite.
|
||||
<p><br>The <strong>smbpasswd</strong> program has several different functions, depending
|
||||
<p>This program is part of the <strong>Samba</strong> suite.
|
||||
<p>The <strong>smbpasswd</strong> program has several different functions, depending
|
||||
on whether it is run by the <em>root</em> user or not. When run as a normal
|
||||
user it allows the user to change the password used for their SMB
|
||||
sessions on any machines that store SMB passwords.
|
||||
<p><br>By default (when run with no arguments) it will attempt to change the
|
||||
<p>By default (when run with no arguments) it will attempt to change the
|
||||
current users SMB password on the local machine. This is similar to
|
||||
the way the <strong>passwd (1)</strong> program works. <strong>smbpasswd</strong> differs from how
|
||||
the <strong>passwd</strong> program works however in that it is not <em>setuid root</em>
|
||||
@ -42,29 +42,29 @@ running <a href="smbd.8.html"><strong>smbd</strong></a>. As a consequence in ord
|
||||
to succeed the <a href="smbd.8.html"><strong>smbd</strong></a> daemon must be running on
|
||||
the local machine. On a UNIX machine the encrypted SMB passwords are
|
||||
usually stored in the <a href="smbpasswd.5.html"><strong>smbpasswd (5)</strong></a> file.
|
||||
<p><br>When run by an ordinary user with no options. <strong>smbpasswd</strong> will
|
||||
<p>When run by an ordinary user with no options. <strong>smbpasswd</strong> will
|
||||
prompt them for their old smb password and then ask them for their new
|
||||
password twice, to ensure that the new password was typed
|
||||
correctly. No passwords will be echoed on the screen whilst being
|
||||
typed. If you have a blank smb password (specified by the string "NO
|
||||
PASSWORD" in the <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file) then just
|
||||
press the <Enter> key when asked for your old password.
|
||||
<p><br><strong>smbpasswd</strong> can also be used by a normal user to change their SMB
|
||||
<p><strong>smbpasswd</strong> can also be used by a normal user to change their SMB
|
||||
password on remote machines, such as Windows NT Primary Domain
|
||||
Controllers. See the <a href="smbpasswd.8.html#minusr">(<strong>-r</strong>)</a> and
|
||||
<a href="smbpasswd.8.html#minusU"><strong>-U</strong></a> options below.
|
||||
<p><br>When run by root, <strong>smbpasswd</strong> allows new users to be added and
|
||||
<p>When run by root, <strong>smbpasswd</strong> allows new users to be added and
|
||||
deleted in the <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file, as well as
|
||||
allows changes to the attributes of the user in this file to be made. When
|
||||
run by root, <strong>smbpasswd</strong> accesses the local
|
||||
<a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file directly, thus enabling
|
||||
changes to be made even if <a href="smbd.8.html"><strong>smbd</strong></a> is not running.
|
||||
<p><br><a name="OPTIONS"></a>
|
||||
<p><a name="OPTIONS"></a>
|
||||
<h2>OPTIONS</h2>
|
||||
|
||||
<p><br><ul>
|
||||
<p><br><a name="minusa"></a>
|
||||
<li><strong><strong>-a</strong></strong> This option specifies that the username following should
|
||||
<p><dl>
|
||||
<p><a name="minusa"></a>
|
||||
<p></p><dt><strong><strong>-a</strong></strong><dd> This option specifies that the username following should
|
||||
be added to the local <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file, with
|
||||
the new password typed (type <Enter> for the old password). This
|
||||
option is ignored if the username following already exists in the
|
||||
@ -72,60 +72,65 @@ option is ignored if the username following already exists in the
|
||||
regular change password command. Note that the user to be added
|
||||
<strong>must</strong> already exist in the system password file (usually /etc/passwd)
|
||||
else the request to add the user will fail.
|
||||
<p><br>This option is only available when running <strong>smbpasswd</strong> as
|
||||
<p>This option is only available when running <strong>smbpasswd</strong> as
|
||||
root.
|
||||
<p><br><a name="minusd"></a>
|
||||
<li><strong><strong>-d</strong></strong> This option specifies that the username following should be
|
||||
<p><a name="minusx"></a>
|
||||
<p></p><dt><strong><strong>-x</strong></strong><dd> This option specifies that the username following should
|
||||
be deleted from the local <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file.
|
||||
<p>This option is only available when running <strong>smbpasswd</strong> as
|
||||
root.
|
||||
<p><a name="minusd"></a>
|
||||
<p></p><dt><strong><strong>-d</strong></strong><dd> This option specifies that the username following should be
|
||||
<em>disabled</em> in the local <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file.
|
||||
This is done by writing a <em>'D'</em> flag into the account control space
|
||||
in the <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file. Once this is done
|
||||
all attempts to authenticate via SMB using this username will fail.
|
||||
<p><br>If the <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file is in the 'old'
|
||||
<p>If the <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file is in the 'old'
|
||||
format (pre-Samba 2.0 format) there is no space in the users password
|
||||
entry to write this information and so the user is disabled by writing
|
||||
'X' characters into the password space in the
|
||||
<a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file. See <a href="smbpasswd.5.html"><strong>smbpasswd
|
||||
(5)</strong></a> for details on the 'old' and new password file
|
||||
formats.
|
||||
<p><br>This option is only available when running <strong>smbpasswd</strong> as root.
|
||||
<p><br><a name="minuse"></a>
|
||||
<li><strong><strong>-e</strong></strong> This option specifies that the username following should be
|
||||
<p>This option is only available when running <strong>smbpasswd</strong> as root.
|
||||
<p><a name="minuse"></a>
|
||||
<p></p><dt><strong><strong>-e</strong></strong><dd> This option specifies that the username following should be
|
||||
<em>enabled</em> in the local <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file,
|
||||
if the account was previously disabled. If the account was not
|
||||
disabled this option has no effect. Once the account is enabled
|
||||
then the user will be able to authenticate via SMB once again.
|
||||
<p><br>If the smbpasswd file is in the 'old' format then <strong>smbpasswd</strong> will
|
||||
<p>If the smbpasswd file is in the 'old' format then <strong>smbpasswd</strong> will
|
||||
prompt for a new password for this user, otherwise the account will be
|
||||
enabled by removing the <em>'D'</em> flag from account control space in the
|
||||
<a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file. See <a href="smbpasswd.5.html"><strong>smbpasswd
|
||||
(5)</strong></a> for details on the 'old' and new password file
|
||||
formats.
|
||||
<p><br>This option is only available when running <strong>smbpasswd</strong> as root.
|
||||
<p><br><a name="minusD"></a>
|
||||
<li><strong><strong>-D debuglevel</strong></strong> debuglevel is an integer from 0
|
||||
<p>This option is only available when running <strong>smbpasswd</strong> as root.
|
||||
<p><a name="minusD"></a>
|
||||
<p></p><dt><strong><strong>-D debuglevel</strong></strong><dd> debuglevel is an integer from 0
|
||||
to 10. The default value if this parameter is not specified is zero.
|
||||
<p><br>The higher this value, the more detail will be logged to the log files
|
||||
<p>The higher this value, the more detail will be logged to the log files
|
||||
about the activities of smbpasswd. At level 0, only critical errors
|
||||
and serious warnings will be logged.
|
||||
<p><br>Levels above 1 will generate considerable amounts of log data, and
|
||||
<p>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.
|
||||
<p><br><a name="minusn"></a>
|
||||
<li><strong><strong>-n</strong></strong> This option specifies that the username following should
|
||||
<p><a name="minusn"></a>
|
||||
<p></p><dt><strong><strong>-n</strong></strong><dd> This option specifies that the username following should
|
||||
have their password set to null (i.e. a blank password) in the local
|
||||
<a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file. This is done by writing the
|
||||
string "NO PASSWORD" as the first part of the first password stored in
|
||||
the <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file.
|
||||
<p><br>Note that to allow users to logon to a Samba server once the password
|
||||
<p>Note that to allow users to logon to a Samba server once the password
|
||||
has been set to "NO PASSWORD" in the
|
||||
<a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file the administrator must set
|
||||
the following parameter in the [global] section of the
|
||||
<a href="smb.conf.5.html"><strong>smb.conf</strong></a> file :
|
||||
<p><br><a href="smb.conf.5.html#nullpasswords">null passwords = true</a>
|
||||
<p><br>This option is only available when running <strong>smbpasswd</strong> as root.
|
||||
<p><br><a name="minusr"></a>
|
||||
<li><strong><strong>-r remote machine name</strong></strong> This option allows a
|
||||
<p><a href="smb.conf.5.html#nullpasswords">null passwords = true</a>
|
||||
<p>This option is only available when running <strong>smbpasswd</strong> as root.
|
||||
<p><a name="minusr"></a>
|
||||
<p></p><dt><strong><strong>-r remote machine name</strong></strong><dd> This option allows a
|
||||
user to specify what machine they wish to change their password
|
||||
on. Without this parameter <strong>smbpasswd</strong> defaults to the local
|
||||
host. The <em>"remote machine name"</em> is the NetBIOS name of the
|
||||
@ -134,71 +139,71 @@ is resolved into an IP address using the standard name resolution
|
||||
mechanism in all programs of the <a href="samba.7.html"><strong>Samba</strong></a>
|
||||
suite. See the <a href="smbpasswd.8.html#minusR"><strong>-R name resolve order</strong></a> parameter for details on changing this resolving
|
||||
mechanism.
|
||||
<p><br>The username whose password is changed is that of the current UNIX
|
||||
<p>The username whose password is changed is that of the current UNIX
|
||||
logged on user. See the <a href="smbpasswd.8.html#minusU"><strong>-U username</strong></a>
|
||||
parameter for details on changing the password for a different
|
||||
username.
|
||||
<p><br>Note that if changing a Windows NT Domain password the remote machine
|
||||
<p>Note that if changing a Windows NT Domain password the remote machine
|
||||
specified must be the Primary Domain Controller for the domain (Backup
|
||||
Domain Controllers only have a read-only copy of the user account
|
||||
database and will not allow the password change).
|
||||
<p><br><em>Note</em> that Windows 95/98 do not have a real password database
|
||||
<p><em>Note</em> that Windows 95/98 do not have a real password database
|
||||
so it is not possible to change passwords specifying a Win95/98
|
||||
machine as remote machine target.
|
||||
<p><br><a name="minusR"></a>
|
||||
<li><strong><strong>-R name resolve order</strong></strong> This option allows the user of
|
||||
<p><a name="minusR"></a>
|
||||
<p></p><dt><strong><strong>-R name resolve order</strong></strong><dd> This option allows the user of
|
||||
smbclient to determine what name resolution services to use when
|
||||
looking up the NetBIOS name of the host being connected to.
|
||||
<p><br>The options are :<a href="smbpasswd.8.html#lmhosts">"lmhosts"</a>, <a href="smbpasswd.8.html#host">"host"</a>,
|
||||
<p>The options are :<a href="smbpasswd.8.html#lmhosts">"lmhosts"</a>, <a href="smbpasswd.8.html#host">"host"</a>,
|
||||
<a href="smbpasswd.8.html#wins">"wins"</a> and <a href="smbpasswd.8.html#bcast">"bcast"</a>. They cause names to be
|
||||
resolved as follows :
|
||||
<p><br><ul>
|
||||
<p><br><a name="lmhosts"></a>
|
||||
<p><dl>
|
||||
<p><a name="lmhosts"></a>
|
||||
<li > <strong>lmhosts</strong> : Lookup an IP address in the Samba lmhosts file.
|
||||
<p><br><a name="host"></a>
|
||||
<p><a name="host"></a>
|
||||
<li > <strong>host</strong> : 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 <em>/etc/nsswitch.conf</em> file).
|
||||
<p><br><a name="wins"></a>
|
||||
<p><a name="wins"></a>
|
||||
<li > <strong>wins</strong> : Query a name with the IP address listed in the
|
||||
<a href="smb.conf.5.html#winsserver"><strong>wins server</strong></a> parameter in the
|
||||
<a href="smb.conf.5.html"><strong>smb.conf file</strong></a>. If
|
||||
no WINS server has been specified this method will be ignored.
|
||||
<p><br><a name="bcast"></a>
|
||||
<p><a name="bcast"></a>
|
||||
<li > <strong>bcast</strong> : Do a broadcast on each of the known local interfaces
|
||||
listed in the <a href="smb.conf.5.html#interfaces"><strong>interfaces</strong></a> parameter
|
||||
in the smb.conf file. This is the least reliable of the name resolution
|
||||
methods as it depends on the target host being on a locally connected
|
||||
subnet.
|
||||
<p><br></ul>
|
||||
<p><br>If this parameter is not set then the name resolve order defined
|
||||
<p></dl>
|
||||
<p>If this parameter is not set then the name resolve order defined
|
||||
in the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file parameter
|
||||
<a href="smb.conf.5.html#nameresolveorder"><strong>name resolve order</strong></a>
|
||||
will be used.
|
||||
<p><br>The default order is lmhosts, host, wins, bcast and without this
|
||||
<p>The default order is lmhosts, host, wins, bcast and without this
|
||||
parameter or any entry in the <a href="smb.conf.5.html"><strong>smb.conf</strong></a>
|
||||
file the name resolution methods will be attempted in this order.
|
||||
<p><br><a name="minusm"></a>
|
||||
<li><strong><strong>-m</strong></strong> This option tells <strong>smbpasswd</strong> that the account being
|
||||
<p><a name="minusm"></a>
|
||||
<p></p><dt><strong><strong>-m</strong></strong><dd> This option tells <strong>smbpasswd</strong> that the account being
|
||||
changed is a <em>MACHINE</em> account. Currently this is used when Samba is
|
||||
being used as an NT Primary Domain Controller. PDC support is not a
|
||||
supported feature in Samba2.0 but will become supported in a later
|
||||
release. If you wish to know more about using Samba as an NT PDC then
|
||||
please subscribe to the mailing list
|
||||
<a href="mailto:samba-ntdom@samba.org"><em>samba-ntdom@samba.org</em></a>.
|
||||
<p><br>This option is only available when running <strong>smbpasswd</strong> as root.
|
||||
<p><br><a name="minusj"></a>
|
||||
<li><strong><strong>-j DOMAIN</strong></strong> This option is used to add a Samba server into a
|
||||
<p>This option is only available when running <strong>smbpasswd</strong> as root.
|
||||
<p><a name="minusj"></a>
|
||||
<p></p><dt><strong><strong>-j DOMAIN</strong></strong><dd> This option is used to add a Samba server into a
|
||||
Windows NT Domain, as a Domain member capable of authenticating user
|
||||
accounts to any Domain Controller in the same way as a Windows NT
|
||||
Server. See the <a href="smb.conf.5.html#security"><strong>security=domain</strong></a>
|
||||
option in the <a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a> man page.
|
||||
<p><br>In order to be used in this way, the Administrator for the Windows
|
||||
<p>In order to be used in this way, the Administrator for the Windows
|
||||
NT Domain must have used the program <em>"Server Manager for Domains"</em>
|
||||
to add the <a href="smb.conf.5.html#netbiosname">primary NetBIOS name</a> of
|
||||
the Samba server as a member of the Domain.
|
||||
<p><br>After this has been done, to join the Domain invoke <strong>smbpasswd</strong> with
|
||||
<p>After this has been done, to join the Domain invoke <strong>smbpasswd</strong> with
|
||||
this parameter. <strong>smbpasswd</strong> will then look up the Primary Domain
|
||||
Controller for the Domain (found in the
|
||||
<a href="smb.conf.5.html"><strong>smb.conf</strong></a> file in the parameter
|
||||
@ -208,39 +213,39 @@ communication. This password is then stored by <strong>smbpasswd</strong> in a
|
||||
file, read only by root, called <code><Domain>.<Machine>.mac</code> where
|
||||
<code><Domain></code> is the name of the Domain we are joining and <code><Machine></code>
|
||||
is the primary NetBIOS name of the machine we are running on.
|
||||
<p><br>Once this operation has been performed the
|
||||
<p>Once this operation has been performed the
|
||||
<a href="smb.conf.5.html"><strong>smb.conf</strong></a> file may be updated to set the
|
||||
<a href="smb.conf.5.html#security"><strong>security=domain</strong></a> option and all
|
||||
future logins to the Samba server will be authenticated to the Windows
|
||||
NT PDC.
|
||||
<p><br>Note that even though the authentication is being done to the PDC all
|
||||
<p>Note that even though the authentication is being done to the PDC all
|
||||
users accessing the Samba server must still have a valid UNIX account
|
||||
on that machine.
|
||||
<p><br>This option is only available when running <strong>smbpasswd</strong> as root.
|
||||
<p><br><a name="minusU"></a>
|
||||
<li><strong><strong>-U username</strong></strong> This option may only be used in
|
||||
<p>This option is only available when running <strong>smbpasswd</strong> as root.
|
||||
<p><a name="minusU"></a>
|
||||
<p></p><dt><strong><strong>-U username</strong></strong><dd> This option may only be used in
|
||||
conjunction with the <a href="smbpasswd.8.html#minusr"><strong>-r</strong></a>
|
||||
option. When changing a password on a remote machine it allows the
|
||||
user to specify the user name on that machine whose password will be
|
||||
changed. It is present to allow users who have different user names on
|
||||
different systems to change these passwords.
|
||||
<p><br><a name="minush"></a>
|
||||
<li><strong><strong>-h</strong></strong> This option prints the help string for <strong>smbpasswd</strong>,
|
||||
<p><a name="minush"></a>
|
||||
<p></p><dt><strong><strong>-h</strong></strong><dd> This option prints the help string for <strong>smbpasswd</strong>,
|
||||
selecting the correct one for running as root or as an ordinary user.
|
||||
<p><br><a name="minuss"></a>
|
||||
<li><strong><strong>-s</strong></strong> This option causes <strong>smbpasswd</strong> to be silent (i.e. not
|
||||
<p><a name="minuss"></a>
|
||||
<p></p><dt><strong><strong>-s</strong></strong><dd> This option causes <strong>smbpasswd</strong> to be silent (i.e. not
|
||||
issue prompts) and to read it's old and new passwords from standard
|
||||
input, rather than from <code>/dev/tty</code> (like the <strong>passwd (1)</strong> program
|
||||
does). This option is to aid people writing scripts to drive <strong>smbpasswd</strong>
|
||||
<p><br><a name="username"></a>
|
||||
<li><strong><strong>username</strong></strong> This specifies the username for all of the <em>root
|
||||
<p><a name="username"></a>
|
||||
<p></p><dt><strong><strong>username</strong></strong><dd> This specifies the username for all of the <em>root
|
||||
only</em> options to operate on. Only root can specify this parameter as
|
||||
only root has the permission needed to modify attributes directly
|
||||
in the local <a href="smbpasswd.5.html"><strong>smbpasswd</strong></a> file.
|
||||
<p><br><a name="NOTES"></a>
|
||||
<p><a name="NOTES"></a>
|
||||
<h2>NOTES</h2>
|
||||
|
||||
<p><br>Since <strong>smbpasswd</strong> works in client-server mode communicating with a
|
||||
<p>Since <strong>smbpasswd</strong> works in client-server mode communicating with a
|
||||
local <a href="smbd.8.html"><strong>smbd</strong></a> for a non-root user then the <strong>smbd</strong>
|
||||
daemon must be running for this to work. A common problem is to add a
|
||||
restriction to the hosts that may access the <strong>smbd</strong> running on the
|
||||
@ -249,27 +254,27 @@ hosts"</strong></a> or <a href="smb.conf.5.html#denyhosts"><strong>"deny
|
||||
hosts"</strong></a> entry in the
|
||||
<a href="smb.conf.5.html"><strong>smb.conf</strong></a> file and neglecting to allow
|
||||
<em>"localhost"</em> access to the <strong>smbd</strong>.
|
||||
<p><br>In addition, the <strong>smbpasswd</strong> command is only useful if <strong>Samba</strong> has
|
||||
<p>In addition, the <strong>smbpasswd</strong> command is only useful if <strong>Samba</strong> has
|
||||
been set up to use encrypted passwords. See the file <strong>ENCRYPTION.txt</strong>
|
||||
in the docs directory for details on how to do this.
|
||||
<p><br><a name="VERSION"></a>
|
||||
<p><a name="VERSION"></a>
|
||||
<h2>VERSION</h2>
|
||||
|
||||
<p><br>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><br><a name="AUTHOR"></a>
|
||||
<p>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><a name="AUTHOR"></a>
|
||||
<h2>AUTHOR</h2>
|
||||
|
||||
<p><br>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed
|
||||
<p>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed.
|
||||
<p><br>The original Samba man pages were written by Karl Auer. The man page
|
||||
<p>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
|
||||
<a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>)
|
||||
and updated for the Samba2.0 release by Jeremy Allison.
|
||||
<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>.
|
||||
<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
|
||||
<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>.
|
||||
<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
comments etc.
|
||||
</body>
|
||||
|
||||
@ -3,9 +3,10 @@
|
||||
|
||||
|
||||
|
||||
|
||||
<html><head><title>smbrun (1)</title>
|
||||
|
||||
<link rev="made" href="mailto:samba-bugs@samba.org">
|
||||
<link rev="made" href="mailto:samba@samba.org">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
@ -15,71 +16,70 @@
|
||||
<h2>Samba</h2>
|
||||
<h2>23 Oct 1998</h2>
|
||||
|
||||
|
||||
|
||||
|
||||
<p><br><a name="NAME"></a>
|
||||
<p><a name="NAME"></a>
|
||||
<h2>NAME</h2>
|
||||
smbrun - interface program between smbd and external programs
|
||||
<p><br><a name="SYNOPSIS"></a>
|
||||
<p><a name="SYNOPSIS"></a>
|
||||
<h2>SYNOPSIS</h2>
|
||||
|
||||
<p><br><strong>smbrun</strong> <a href="smbrun.1.html#shellcommand">shell-command</a>
|
||||
<p><br><a name="DESCRIPTION"></a>
|
||||
<p><strong>smbrun</strong> <a href="smbrun.1.html#shellcommand">shell-command</a>
|
||||
<p><a name="DESCRIPTION"></a>
|
||||
<h2>DESCRIPTION</h2>
|
||||
|
||||
<p><br>This program is part of the <strong>Samba</strong> suite.
|
||||
<p><br><strong>smbrun</strong> is a very small 'glue' program, which runs shell commands
|
||||
<p>This program is part of the <strong>Samba</strong> suite.
|
||||
<p><strong>smbrun</strong> is a very small 'glue' program, which runs shell commands
|
||||
for the <a href="smbd.8.html"><strong>smbd</strong></a> daemon <a href="smbd.8.html"><strong>smbd
|
||||
(8)</strong></a>.
|
||||
<p><br>It first changes to the highest effective user and group ID that it
|
||||
<p>It first changes to the highest effective user and group ID that it
|
||||
can, then runs the command line provided using the system() call. This
|
||||
program is necessary to allow some operating systems to run external
|
||||
programs as non-root.
|
||||
<p><br><a name="OPTIONS"></a>
|
||||
<p><a name="OPTIONS"></a>
|
||||
<h2>OPTIONS</h2>
|
||||
|
||||
<p><br><ul>
|
||||
<p><br><a name="shellcommand"></a>
|
||||
<li><strong><strong>shell-command</strong></strong> The shell command to execute. The command
|
||||
<p><dl>
|
||||
<p><a name="shellcommand"></a>
|
||||
<p></p><dt><strong><strong>shell-command</strong></strong><dd> The shell command to execute. The command
|
||||
should have a fully-qualified path.
|
||||
<p><br></ul>
|
||||
<p><br><a name="ENVIRONMENTVARIABLES"></a>
|
||||
<p></dl>
|
||||
<p><a name="ENVIRONMENTVARIABLES"></a>
|
||||
<h2>ENVIRONMENT VARIABLES</h2>
|
||||
|
||||
<p><br>The <em>PATH</em> variable set for the environment in which <strong>smbrun</strong> is
|
||||
<p>The <em>PATH</em> variable set for the environment in which <strong>smbrun</strong> is
|
||||
executed will affect what executables are located and executed if a
|
||||
fully-qualified path is not given in the command.
|
||||
<p><br><a name="DIAGNOSTICS"></a>
|
||||
<p><a name="DIAGNOSTICS"></a>
|
||||
<h2>DIAGNOSTICS</h2>
|
||||
|
||||
<p><br>If <strong>smbrun</strong> cannot be located or cannot be executed by
|
||||
<p>If <strong>smbrun</strong> cannot be located or cannot be executed by
|
||||
<a href="smbd.8.html"><strong>smbd</strong></a> then appropriate messages will be found in
|
||||
the <a href="smbd.8.html"><strong>smbd</strong></a> logs. Other diagnostics are dependent
|
||||
on the shell-command being run. It is advisable for your shell
|
||||
commands to issue suitable diagnostics to aid trouble-shooting.
|
||||
<p><br><a name="VERSION"></a>
|
||||
<p><a name="VERSION"></a>
|
||||
<h2>VERSION</h2>
|
||||
|
||||
<p><br>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><br><a name="SEEALSO"></a>
|
||||
<p>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><a name="SEEALSO"></a>
|
||||
<h2>SEE ALSO</h2>
|
||||
|
||||
<p><br><a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>, <a href="smbd.8.html"><strong>smbd (8)</strong></a>
|
||||
<p><br><a name="AUTHOR"></a>
|
||||
<p><a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>, <a href="smbd.8.html"><strong>smbd (8)</strong></a>
|
||||
<p><a name="AUTHOR"></a>
|
||||
<h2>AUTHOR</h2>
|
||||
|
||||
<p><br>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed
|
||||
<p>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed.
|
||||
<p><br>The original Samba man pages were written by Karl Auer. The man page
|
||||
<p>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
|
||||
<a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>)
|
||||
and updated for the Samba2.0 release by Jeremy Allison.
|
||||
<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>.
|
||||
<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
|
||||
<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>.
|
||||
<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
comments etc.
|
||||
</body>
|
||||
|
||||
@ -3,9 +3,10 @@
|
||||
|
||||
|
||||
|
||||
|
||||
<html><head><title>smbstatus (1)</title>
|
||||
|
||||
<link rev="made" href="mailto:samba-bugs@samba.org">
|
||||
<link rev="made" href="mailto:samba@samba.org">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
@ -15,71 +16,70 @@
|
||||
<h2>Samba</h2>
|
||||
<h2>23 Oct 1998</h2>
|
||||
|
||||
|
||||
|
||||
|
||||
<p><br><a name="NAME"></a>
|
||||
<p><a name="NAME"></a>
|
||||
<h2>NAME</h2>
|
||||
smbstatus - report on current Samba connections
|
||||
<p><br><a name="SYNOPSIS"></a>
|
||||
<p><a name="SYNOPSIS"></a>
|
||||
<h2>SYNOPSIS</h2>
|
||||
|
||||
<p><br><strong>smbstatus</strong> [<a href="smbstatus.1.html#minusP">-P</a>] [<a href="smbstatus.1.html#minusb">-b</a>] [<a href="smbstatus.1.html#minusd">-d</a>] [<a href="smbstatus.1.html#minusL">-L</a>] [<a href="smbstatus.1.html#minusp">-p</a>] [<a href="smbstatus.1.html#minusS">-S</a>] [<a href="smbstatus.1.html#minuss">-s configuration file</a>] [<a href="smbstatus.1.html#minusu">-u username</a>]
|
||||
<p><br><a name="DESCRIPTION"></a>
|
||||
<p><strong>smbstatus</strong> [<a href="smbstatus.1.html#minusP">-P</a>] [<a href="smbstatus.1.html#minusb">-b</a>] [<a href="smbstatus.1.html#minusd">-d</a>] [<a href="smbstatus.1.html#minusL">-L</a>] [<a href="smbstatus.1.html#minusp">-p</a>] [<a href="smbstatus.1.html#minusS">-S</a>] [<a href="smbstatus.1.html#minuss">-s configuration file</a>] [<a href="smbstatus.1.html#minusu">-u username</a>]
|
||||
<p><a name="DESCRIPTION"></a>
|
||||
<h2>DESCRIPTION</h2>
|
||||
|
||||
<p><br>This program is part of the <strong>Samba</strong> suite.
|
||||
<p><br><strong>smbstatus</strong> is a very simple program to list the current Samba
|
||||
<p>This program is part of the <strong>Samba</strong> suite.
|
||||
<p><strong>smbstatus</strong> is a very simple program to list the current Samba
|
||||
connections.
|
||||
<p><br><a name="OPTIONS"></a>
|
||||
<p><a name="OPTIONS"></a>
|
||||
<h2>OPTIONS</h2>
|
||||
|
||||
<p><br><ul>
|
||||
<p><br><a name="minusP"></a>
|
||||
<li><strong><strong>-P</strong></strong> If samba has been compiled with the profiling option,
|
||||
<p><dl>
|
||||
<p><a name="minusP"></a>
|
||||
<p></p><dt><strong><strong>-P</strong></strong><dd> If samba has been compiled with the profiling option,
|
||||
print only the contents of the profiling shared memory area.
|
||||
<p><br><a name="minusb"></a>
|
||||
<li><strong><strong>-b</strong></strong> gives brief output.
|
||||
<p><br><a name="minusd"></a>
|
||||
<li><strong><strong>-d</strong></strong> gives verbose output.
|
||||
<p><br><a name="minusL"></a>
|
||||
<li><strong><strong>-L</strong></strong> causes smbstatus to only list locks.
|
||||
<p><br><a name="minusp"></a>
|
||||
<li><strong><strong>-p</strong></strong> print a list of <a href="smbd.8.html"><strong>smbd</strong></a>
|
||||
<p><a name="minusb"></a>
|
||||
<p></p><dt><strong><strong>-b</strong></strong><dd> gives brief output.
|
||||
<p><a name="minusd"></a>
|
||||
<p></p><dt><strong><strong>-d</strong></strong><dd> gives verbose output.
|
||||
<p><a name="minusL"></a>
|
||||
<p></p><dt><strong><strong>-L</strong></strong><dd> causes smbstatus to only list locks.
|
||||
<p><a name="minusp"></a>
|
||||
<p></p><dt><strong><strong>-p</strong></strong><dd> print a list of <a href="smbd.8.html"><strong>smbd</strong></a>
|
||||
processes and exit. Useful for scripting.
|
||||
<p><br><a name="minusS"></a>
|
||||
<li><strong><strong>-S</strong></strong> causes smbstatus to only list shares.
|
||||
<p><br><a name="minuss"></a>
|
||||
<li><strong><strong>-s configuration file</strong></strong> The default configuration file name is
|
||||
<p><a name="minusS"></a>
|
||||
<p></p><dt><strong><strong>-S</strong></strong><dd> causes smbstatus to only list shares.
|
||||
<p><a name="minuss"></a>
|
||||
<p></p><dt><strong><strong>-s configuration file</strong></strong><dd> The default configuration file name is
|
||||
determined at compile time. The file specified contains the
|
||||
configuration details required by the server. See <a href="smb.conf.5.html"><strong>smb.conf
|
||||
(5)</strong></a> for more information.
|
||||
<p><br><a name="minusu"></a>
|
||||
<li><strong><strong>-u username</strong></strong> selects information relevant to <em>username</em>
|
||||
<p><a name="minusu"></a>
|
||||
<p></p><dt><strong><strong>-u username</strong></strong><dd> selects information relevant to <em>username</em>
|
||||
only.
|
||||
<p><br></ul>
|
||||
<p><br><a name="VERSION"></a>
|
||||
<p></dl>
|
||||
<p><a name="VERSION"></a>
|
||||
<h2>VERSION</h2>
|
||||
|
||||
<p><br>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><br><a name="SEEALSO"></a>
|
||||
<p>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><a name="SEEALSO"></a>
|
||||
<h2>SEE ALSO</h2>
|
||||
|
||||
<p><br><a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>, <a href="smbd.8.html"><strong>smbd (8)</strong></a>
|
||||
<p><br><a name="AUTHOR"></a>
|
||||
<p><a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>, <a href="smbd.8.html"><strong>smbd (8)</strong></a>
|
||||
<p><a name="AUTHOR"></a>
|
||||
<h2>AUTHOR</h2>
|
||||
|
||||
<p><br>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed
|
||||
<p>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed.
|
||||
<p><br>The original Samba man pages were written by Karl Auer. The man page
|
||||
<p>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
|
||||
<a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>)
|
||||
and updated for the Samba2.0 release by Jeremy Allison.
|
||||
<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>.
|
||||
<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
|
||||
<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>.
|
||||
<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
comments etc.
|
||||
</body>
|
||||
|
||||
@ -3,9 +3,10 @@
|
||||
|
||||
|
||||
|
||||
|
||||
<html><head><title>smbtar (1)</title>
|
||||
|
||||
<link rev="made" href="mailto:samba-bugs@samba.org">
|
||||
<link rev="made" href="mailto:samba@samba.org">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
@ -15,106 +16,105 @@
|
||||
<h2>Samba</h2>
|
||||
<h2>23 Oct 1998</h2>
|
||||
|
||||
|
||||
|
||||
|
||||
<p><br><a name="NAME"></a>
|
||||
<p><a name="NAME"></a>
|
||||
<h2>NAME</h2>
|
||||
smbtar - shell script for backing up SMB/CIFS shares directly to UNIX tape drives
|
||||
<p><br><a name="SYNOPSIS"></a>
|
||||
<p><a name="SYNOPSIS"></a>
|
||||
<h2>SYNOPSIS</h2>
|
||||
|
||||
<p><br><strong>smbtar</strong> <a href="smbtar.1.html#minuss">-s server</a> [<a href="smbtar.1.html#minusp">-p password</a>] [<a href="smbtar.1.html#minusx">-x service</a>] [<a href="smbtar.1.html#minusX">-X</a>] [<a href="smbtar.1.html#minusd">-d directory</a>] [<a href="smbtar.1.html#minusu">-u user</a>] [<a href="smbtar.1.html#minust">-t tape</a>] [<a href="smbtar.1.html#minusb">-b blocksize</a>] [<a href="smbtar.1.html#minusN">-N filename</a>] [<a href="smbtar.1.html#minusi">-i</a>] [<a href="smbtar.1.html#minusr">-r</a>] [<a href="smbtar.1.html#minusl">-l log level</a>] [<a href="smbtar.1.html#minusv">-v</a>] filenames
|
||||
<p><br><a name="DESCRIPTION"></a>
|
||||
<p><strong>smbtar</strong> <a href="smbtar.1.html#minuss">-s server</a> [<a href="smbtar.1.html#minusp">-p password</a>] [<a href="smbtar.1.html#minusx">-x service</a>] [<a href="smbtar.1.html#minusX">-X</a>] [<a href="smbtar.1.html#minusd">-d directory</a>] [<a href="smbtar.1.html#minusu">-u user</a>] [<a href="smbtar.1.html#minust">-t tape</a>] [<a href="smbtar.1.html#minusb">-b blocksize</a>] [<a href="smbtar.1.html#minusN">-N filename</a>] [<a href="smbtar.1.html#minusi">-i</a>] [<a href="smbtar.1.html#minusr">-r</a>] [<a href="smbtar.1.html#minusl">-l log level</a>] [<a href="smbtar.1.html#minusv">-v</a>] filenames
|
||||
<p><a name="DESCRIPTION"></a>
|
||||
<h2>DESCRIPTION</h2>
|
||||
|
||||
<p><br>This program is part of the <strong>Samba</strong> suite.
|
||||
<p><br><strong>smbtar</strong> is a very small shell script on top of
|
||||
<p>This program is part of the <strong>Samba</strong> suite.
|
||||
<p><strong>smbtar</strong> is a very small shell script on top of
|
||||
<a href="smbclient.1.html"><strong>smbclient</strong></a> which dumps SMB shares directly
|
||||
to tape.
|
||||
<p><br><a name="OPTIONS"></a>
|
||||
<p><a name="OPTIONS"></a>
|
||||
<h2>OPTIONS</h2>
|
||||
|
||||
<p><br><ul>
|
||||
<p><br><a name="minuss"></a>
|
||||
<li><strong><strong>-s server</strong></strong> The SMB/CIFS server that the share resides upon.
|
||||
<p><br><a name="minusx"></a>
|
||||
<li><strong><strong>-x service</strong></strong> The share name on the server to connect
|
||||
<p><dl>
|
||||
<p><a name="minuss"></a>
|
||||
<p></p><dt><strong><strong>-s server</strong></strong><dd> The SMB/CIFS server that the share resides upon.
|
||||
<p><a name="minusx"></a>
|
||||
<p></p><dt><strong><strong>-x service</strong></strong><dd> The share name on the server to connect
|
||||
to. The default is <code>backup</code>.
|
||||
<p><br><a name="minusX"></a>
|
||||
<li><strong><strong>-X</strong></strong> Exclude mode. Exclude filenames... from tar create or
|
||||
<p><a name="minusX"></a>
|
||||
<p></p><dt><strong><strong>-X</strong></strong><dd> Exclude mode. Exclude filenames... from tar create or
|
||||
restore.
|
||||
<p><br><a name="minusd"></a>
|
||||
<li><strong><strong>-d directory</strong></strong> Change to initial <em>directory</em> before restoring
|
||||
<p><a name="minusd"></a>
|
||||
<p></p><dt><strong><strong>-d directory</strong></strong><dd> Change to initial <em>directory</em> before restoring
|
||||
/ backing up files.
|
||||
<p><br><a name="minusv"></a>
|
||||
<li><strong><strong>-v</strong></strong> Verbose mode.
|
||||
<p><br><a name="minusp"></a>
|
||||
<li><strong><strong>-p password</strong></strong> The password to use to access a share. Default:
|
||||
<p><a name="minusv"></a>
|
||||
<p></p><dt><strong><strong>-v</strong></strong><dd> Verbose mode.
|
||||
<p><a name="minusp"></a>
|
||||
<p></p><dt><strong><strong>-p password</strong></strong><dd> The password to use to access a share. Default:
|
||||
none
|
||||
<p><br><a name="minusu"></a>
|
||||
<li><strong><strong>-u user</strong></strong> The user id to connect as. Default: UNIX login name.
|
||||
<p><br><a name="minust"></a>
|
||||
<li><strong><strong>-t tape</strong></strong> Tape device. May be regular file or tape
|
||||
<p><a name="minusu"></a>
|
||||
<p></p><dt><strong><strong>-u user</strong></strong><dd> The user id to connect as. Default: UNIX login name.
|
||||
<p><a name="minust"></a>
|
||||
<p></p><dt><strong><strong>-t tape</strong></strong><dd> Tape device. May be regular file or tape
|
||||
device. Default: <em>TAPE</em> environmental variable; if not set, a file
|
||||
called <code>tar.out</code>.
|
||||
<p><br><a name="minusb"></a>
|
||||
<li><strong><strong>-b blocksize</strong></strong> Blocking factor. Defaults to 20. See <strong>tar (1)</strong>
|
||||
<p><a name="minusb"></a>
|
||||
<p></p><dt><strong><strong>-b blocksize</strong></strong><dd> Blocking factor. Defaults to 20. See <strong>tar (1)</strong>
|
||||
for a fuller explanation.
|
||||
<p><br><a name="minusN"></a>
|
||||
<li><strong><strong>-N filename</strong></strong> Backup only files newer than filename. Could be
|
||||
<p><a name="minusN"></a>
|
||||
<p></p><dt><strong><strong>-N filename</strong></strong><dd> Backup only files newer than filename. Could be
|
||||
used (for example) on a log file to implement incremental backups.
|
||||
<p><br><a name="minusi"></a>
|
||||
<li><strong><strong>-i</strong></strong> Incremental mode; tar files are only backed up if they
|
||||
<p><a name="minusi"></a>
|
||||
<p></p><dt><strong><strong>-i</strong></strong><dd> Incremental mode; tar files are only backed up if they
|
||||
have the archive bit set. The archive bit is reset after each file is
|
||||
read.
|
||||
<p><br><a name="minusr"></a>
|
||||
<li><strong><strong>-r</strong></strong> Restore. Files are restored to the share from the tar
|
||||
<p><a name="minusr"></a>
|
||||
<p></p><dt><strong><strong>-r</strong></strong><dd> Restore. Files are restored to the share from the tar
|
||||
file.
|
||||
<p><br><a name="minusl"></a>
|
||||
<li><strong><strong>-l log level</strong></strong> Log (debug) level. Corresponds to the
|
||||
<p><a name="minusl"></a>
|
||||
<p></p><dt><strong><strong>-l log level</strong></strong><dd> Log (debug) level. Corresponds to the
|
||||
<a href="smbclient.1.html#minusd"><strong>-d</strong></a> flag of <a href="smbclient.1.html"><strong>smbclient
|
||||
(1)</strong></a>.
|
||||
<p><br></ul>
|
||||
<p><br><a name="ENVIRONMENTVARIABLES"></a>
|
||||
<p></dl>
|
||||
<p><a name="ENVIRONMENTVARIABLES"></a>
|
||||
<h2>ENVIRONMENT VARIABLES</h2>
|
||||
|
||||
<p><br>The TAPE variable specifies the default tape device to write to. May
|
||||
<p>The TAPE variable specifies the default tape device to write to. May
|
||||
be overridden with the <a href="smbtar.1.html#minust"><strong>-t</strong></a> option.
|
||||
<p><br><a name="BUGS"></a>
|
||||
<p><a name="BUGS"></a>
|
||||
<h2>BUGS</h2>
|
||||
|
||||
<p><br>The <strong>smbtar</strong> script has different options from ordinary tar and tar
|
||||
<p>The <strong>smbtar</strong> script has different options from ordinary tar and tar
|
||||
called from <a href="smbclient.1.html"><strong>smbclient</strong></a>.
|
||||
<p><br><a name="CAVEATS"></a>
|
||||
<p><a name="CAVEATS"></a>
|
||||
<h2>CAVEATS</h2>
|
||||
|
||||
<p><br>Sites that are more careful about security may not like the way the
|
||||
<p>Sites that are more careful about security may not like the way the
|
||||
script handles PC passwords. Backup and restore work on entire shares,
|
||||
should work on file lists. <strong>smbtar</strong> works best with GNU tar and may
|
||||
not work well with other versions.
|
||||
<p><br><a name="VERSION"></a>
|
||||
<p><a name="VERSION"></a>
|
||||
<h2>VERSION</h2>
|
||||
|
||||
<p><br>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><br><a name="SEEALSO"></a>
|
||||
<p>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><a name="SEEALSO"></a>
|
||||
<h2>SEE ALSO</h2>
|
||||
|
||||
<p><br><a href="smbclient.1.html"><strong>smbclient (1)</strong></a>, <a href="smb.conf.5.html"><strong>smb.conf
|
||||
<p><a href="smbclient.1.html"><strong>smbclient (1)</strong></a>, <a href="smb.conf.5.html"><strong>smb.conf
|
||||
(5)</strong></a>
|
||||
<p><br><a name="DIAGNOSTICS"></a>
|
||||
<p><a name="DIAGNOSTICS"></a>
|
||||
<h2>DIAGNOSTICS</h2>
|
||||
|
||||
<p><br>See the <a href="smbclient.1.html#DIAGNOSTICS"><strong>DIAGNOSTICS</strong></a> section for
|
||||
<p>See the <a href="smbclient.1.html#DIAGNOSTICS"><strong>DIAGNOSTICS</strong></a> section for
|
||||
the <a href="smbclient.1.html"><strong>smbclient</strong></a> command.
|
||||
<p><br><a name="AUTHOR"></a>
|
||||
<p><a name="AUTHOR"></a>
|
||||
<h2>AUTHOR</h2>
|
||||
|
||||
<p><br>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed
|
||||
<p>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed.
|
||||
<p><br>Ricky Poulten <a href="mailto:poultenr@logica.co.uk"><em>poultenr@logica.co.uk</em></a> wrote the tar extension and
|
||||
<p>Ricky Poulten <a href="mailto:poultenr@logica.co.uk"><em>poultenr@logica.co.uk</em></a> wrote the tar extension and
|
||||
this man page. The <strong>smbtar</strong> script was heavily rewritten and
|
||||
improved by Martin Kraemer <a href="mailto:Martin.Kraemer@mch.sni.de"><em>Martin.Kraemer@mch.sni.de</em></a>. Many
|
||||
thanks to everyone who suggested extensions, improvements, bug fixes,
|
||||
@ -122,9 +122,9 @@ etc. The man page sources were converted to YODL format (another
|
||||
excellent piece of Open Source software available at
|
||||
<a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>)
|
||||
and updated for the Samba2.0 release by Jeremy Allison,
|
||||
<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>.
|
||||
<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
|
||||
<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>.
|
||||
<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
comments etc.
|
||||
<p><br></body>
|
||||
<p></body>
|
||||
</html>
|
||||
|
||||
@ -3,9 +3,10 @@
|
||||
|
||||
|
||||
|
||||
|
||||
<html><head><title>swat (8)</title>
|
||||
|
||||
<link rev="made" href="mailto:samba-bugs@samba.org">
|
||||
<link rev="made" href="mailto:samba@samba.org">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
@ -15,53 +16,52 @@
|
||||
<h2>Samba</h2>
|
||||
<h2>23 Oct 1998</h2>
|
||||
|
||||
|
||||
|
||||
|
||||
<p><br><a name="NAME"></a>
|
||||
<p><a name="NAME"></a>
|
||||
<h2>NAME</h2>
|
||||
swat - Samba Web Administration Tool
|
||||
<p><br><a name="SYNOPSIS"></a>
|
||||
<p><a name="SYNOPSIS"></a>
|
||||
<h2>SYNOPSIS</h2>
|
||||
|
||||
<p><br><strong>swat</strong> [<a href="swat.8.html#minuss">-s smb config file</a>] [<a href="swat.8.html#minusa">-a</a>]
|
||||
<p><br><a name="DESCRIPTION"></a>
|
||||
<p><strong>swat</strong> [<a href="swat.8.html#minuss">-s smb config file</a>] [<a href="swat.8.html#minusa">-a</a>]
|
||||
<p><a name="DESCRIPTION"></a>
|
||||
<h2>DESCRIPTION</h2>
|
||||
|
||||
<p><br>This program is part of the <strong>Samba</strong> suite.
|
||||
<p><br><strong>swat</strong> allows a Samba administrator to configure the complex
|
||||
<p>This program is part of the <strong>Samba</strong> suite.
|
||||
<p><strong>swat</strong> allows a Samba administrator to configure the complex
|
||||
<a href="smb.conf.5.html"><strong>smb.conf</strong></a> file via a Web browser. In
|
||||
addition, a swat configuration page has help links to all the
|
||||
configurable options in the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file
|
||||
allowing an administrator to easily look up the effects of any change.
|
||||
<p><br><strong>swat</strong> is run from <strong>inetd</strong>
|
||||
<p><br><a name="OPTIONS"></a>
|
||||
<p><strong>swat</strong> is run from <strong>inetd</strong>
|
||||
<p><a name="OPTIONS"></a>
|
||||
<h2>OPTIONS</h2>
|
||||
|
||||
<p><br><ul>
|
||||
<p><br><a name="minuss"></a>
|
||||
<li><strong><strong>-s smb configuration file</strong></strong> The default configuration file path is
|
||||
<p><dl>
|
||||
<p><a name="minuss"></a>
|
||||
<p></p><dt><strong><strong>-s smb configuration file</strong></strong><dd> The default configuration file path is
|
||||
determined at compile time.
|
||||
<p><br>The file specified contains the configuration details required by the
|
||||
<p>The file specified contains the configuration details required by the
|
||||
<a href="smbd.8.html"><strong>smbd</strong></a> server. This is the file that <strong>swat</strong> will
|
||||
modify. The information in this file includes server-specific
|
||||
information such as what printcap file to use, as well as descriptions
|
||||
of all the services that the server is to provide. See <a href="smb.conf.5.html">smb.conf
|
||||
(5)</a> for more information.
|
||||
<p><br><a name="minusa"></a>
|
||||
<li><strong><strong>-a</strong></strong>
|
||||
<p><br>This option disables authentication and puts <strong>swat</strong> in demo mode. In
|
||||
<p><a name="minusa"></a>
|
||||
<p></p><dt><strong><strong>-a</strong></strong><dd>
|
||||
<p>This option disables authentication and puts <strong>swat</strong> in demo mode. In
|
||||
that mode anyone will be able to modify the
|
||||
<a href="smb.conf.5.html"><strong>smb.conf</strong></a> file.
|
||||
<p><br>Do NOT enable this option on a production server.
|
||||
<p><br></ul>
|
||||
<p><br><a name="INSTALLATION"></a>
|
||||
<p>Do NOT enable this option on a production server.
|
||||
<p></dl>
|
||||
<p><a name="INSTALLATION"></a>
|
||||
<h2>INSTALLATION</h2>
|
||||
|
||||
<p><br>After you compile SWAT you need to run <code>"make install"</code> to install the
|
||||
<p>After you compile SWAT you need to run <code>"make install"</code> to install the
|
||||
swat binary and the various help files and images. A default install
|
||||
would put these in:
|
||||
<p><br><pre>
|
||||
<p><pre>
|
||||
|
||||
/usr/local/samba/bin/swat
|
||||
/usr/local/samba/swat/images/*
|
||||
@ -69,79 +69,79 @@ would put these in:
|
||||
|
||||
</pre>
|
||||
|
||||
<p><br><a name="INETD"></a>
|
||||
<p><a name="INETD"></a>
|
||||
<h2>INETD INSTALLATION</h2>
|
||||
|
||||
<p><br>You need to edit your <code>/etc/inetd.conf</code> and <code>/etc/services</code> to
|
||||
<p>You need to edit your <code>/etc/inetd.conf</code> and <code>/etc/services</code> to
|
||||
enable <strong>SWAT</strong> to be launched via inetd.
|
||||
<p><br>In <code>/etc/services</code> you need to add a line like this:
|
||||
<p><br><code>swat 901/tcp</code>
|
||||
<p><br>Note for NIS/YP users - you may need to rebuild the NIS service maps
|
||||
<p>In <code>/etc/services</code> you need to add a line like this:
|
||||
<p><code>swat 901/tcp</code>
|
||||
<p>Note for NIS/YP users - you may need to rebuild the NIS service maps
|
||||
rather than alter your local <code>/etc/services</code> file.
|
||||
<p><br>the choice of port number isn't really important except that it should
|
||||
<p>the choice of port number isn't really important except that it should
|
||||
be less than 1024 and not currently used (using a number above 1024
|
||||
presents an obscure security hole depending on the implementation
|
||||
details of your <strong>inetd</strong> daemon).
|
||||
<p><br>In <code>/etc/inetd.conf</code> you should add a line like this:
|
||||
<p><br><code>swat stream tcp nowait.400 root /usr/local/samba/bin/swat swat</code>
|
||||
<p><br>One you have edited <code>/etc/services</code> and <code>/etc/inetd.conf</code> you need
|
||||
<p>In <code>/etc/inetd.conf</code> you should add a line like this:
|
||||
<p><code>swat stream tcp nowait.400 root /usr/local/samba/bin/swat swat</code>
|
||||
<p>One you have edited <code>/etc/services</code> and <code>/etc/inetd.conf</code> you need
|
||||
to send a HUP signal to inetd. To do this use <code>"kill -1 PID"</code> where
|
||||
PID is the process ID of the inetd daemon.
|
||||
<p><br><a name="LAUNCHING"></a>
|
||||
<p><a name="LAUNCHING"></a>
|
||||
<h2>LAUNCHING</h2>
|
||||
|
||||
<p><br>To launch <strong>swat</strong> just run your favorite web browser and point it at
|
||||
<p>To launch <strong>swat</strong> just run your favorite web browser and point it at
|
||||
<code>http://localhost:901/</code>.
|
||||
<p><br><strong>Note that you can attach to <strong>swat</strong> from any IP connected machine but
|
||||
<p><strong>Note that you can attach to <strong>swat</strong> from any IP connected machine but
|
||||
connecting from a remote machine leaves your connection open to
|
||||
password sniffing as passwords will be sent in the clear over the
|
||||
wire.</strong>
|
||||
<p><br><h2>FILES</h2>
|
||||
<p><h2>FILES</h2>
|
||||
|
||||
<p><br><strong>/etc/inetd.conf</strong>
|
||||
<p><br>This file must contain suitable startup information for the
|
||||
<p><strong>/etc/inetd.conf</strong>
|
||||
<p>This file must contain suitable startup information for the
|
||||
meta-daemon.
|
||||
<p><br><strong>/etc/services</strong>
|
||||
<p><br>This file must contain a mapping of service name (e.g., swat) to
|
||||
<p><strong>/etc/services</strong>
|
||||
<p>This file must contain a mapping of service name (e.g., swat) to
|
||||
service port (e.g., 901) and protocol type (e.g., tcp).
|
||||
<p><br><strong>/usr/local/samba/lib/smb.conf</strong>
|
||||
<p><br>This is the default location of the <em>smb.conf</em> server configuration
|
||||
<p><strong>/usr/local/samba/lib/smb.conf</strong>
|
||||
<p>This is the default location of the <em>smb.conf</em> server configuration
|
||||
file that <strong>swat</strong> edits. Other common places that systems install
|
||||
this file are <em>/usr/samba/lib/smb.conf</em> and <em>/etc/smb.conf</em>.
|
||||
<p><br>This file describes all the services the server is to make available
|
||||
<p>This file describes all the services the server is to make available
|
||||
to clients. See <strong>smb.conf (5)</strong> for more information.
|
||||
<p><br><a name="WARNINGS"></a>
|
||||
<p><a name="WARNINGS"></a>
|
||||
<h2>WARNINGS</h2>
|
||||
|
||||
<p><br><strong>swat</strong> will rewrite your <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file. It
|
||||
<p><strong>swat</strong> will rewrite your <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file. It
|
||||
will rearrange the entries and delete all comments,
|
||||
<a href="smb.conf.5.html#include"><strong>"include="</strong></a> and
|
||||
<a href="smb.conf.5.html#copy"><strong>"copy="</strong></a> options. If you have a
|
||||
carefully crafted <a href="smb.conf.5.html"><strong>smb.conf</strong></a> then back it up
|
||||
or don't use <strong>swat</strong>!
|
||||
<p><br><a name="VERSION"></a>
|
||||
<p><a name="VERSION"></a>
|
||||
<h2>VERSION</h2>
|
||||
|
||||
<p><br>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><br><a name="SEEALSO"></a>
|
||||
<p>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><a name="SEEALSO"></a>
|
||||
<h2>SEE ALSO</h2>
|
||||
|
||||
<p><br><strong>inetd (8)</strong>, <a href="nmbd.8.html"><strong>nmbd (8)</strong></a>,
|
||||
<p><strong>inetd (8)</strong>, <a href="nmbd.8.html"><strong>nmbd (8)</strong></a>,
|
||||
<a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>.
|
||||
<p><br><a name="AUTHOR"></a>
|
||||
<p><a name="AUTHOR"></a>
|
||||
<h2>AUTHOR</h2>
|
||||
|
||||
<p><br>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell (samba-bugs@samba.org). Samba is now developed
|
||||
<p>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell (samba@samba.org). Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed.
|
||||
<p><br>The original Samba man pages were written by Karl Auer. The man page
|
||||
<p>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
|
||||
<a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>)
|
||||
and updated for the Samba2.0 release by Jeremy Allison.
|
||||
<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>.
|
||||
<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
|
||||
<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>.
|
||||
<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
comments etc.
|
||||
</body>
|
||||
|
||||
@ -3,9 +3,10 @@
|
||||
|
||||
|
||||
|
||||
|
||||
<html><head><title>testparm (1)</title>
|
||||
|
||||
<link rev="made" href="mailto:samba-bugs@samba.org">
|
||||
<link rev="made" href="mailto:samba@samba.org">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
@ -15,53 +16,52 @@
|
||||
<h2>Samba</h2>
|
||||
<h2>23 Oct 1998</h2>
|
||||
|
||||
|
||||
|
||||
|
||||
<p><br><a name="NAME"></a>
|
||||
<p><a name="NAME"></a>
|
||||
<h2>NAME</h2>
|
||||
testparm - check an smb.conf configuration file for internal correctness
|
||||
<p><br><a name="SYNOPSIS"></a>
|
||||
<p><a name="SYNOPSIS"></a>
|
||||
<h2>SYNOPSIS</h2>
|
||||
|
||||
<p><br><strong>testparm</strong> [<a href="testparm.1.html#minuss">-s</a>] [<a href="testparm.1.html#minush">-h</a>] [<a href="testparm.1.html#minusL">-L servername</a>] [<a href="testparm.1.html#configfilename">configfilename</a>] [<a href="testparm.1.html#hostname">hostname</a> <a href="testparm.1.html#hostIP">hostIP</a>]
|
||||
<p><br><a name="DESCRIPTION"></a>
|
||||
<p><strong>testparm</strong> [<a href="testparm.1.html#minuss">-s</a>] [<a href="testparm.1.html#minush">-h</a>] [<a href="testparm.1.html#minusL">-L servername</a>] [<a href="testparm.1.html#configfilename">configfilename</a>] [<a href="testparm.1.html#hostname">hostname</a> <a href="testparm.1.html#hostIP">hostIP</a>]
|
||||
<p><a name="DESCRIPTION"></a>
|
||||
<h2>DESCRIPTION</h2>
|
||||
|
||||
<p><br>This program is part of the <strong>Samba</strong> suite.
|
||||
<p><br><strong>testparm</strong> is a very simple test program to check an
|
||||
<p>This program is part of the <strong>Samba</strong> suite.
|
||||
<p><strong>testparm</strong> is a very simple test program to check an
|
||||
<a href="smbd.8.html"><strong>smbd</strong></a> configuration file for internal
|
||||
correctness. If this program reports no problems, you can use the
|
||||
configuration file with confidence that <a href="smbd.8.html"><strong>smbd</strong></a>
|
||||
will successfully load the configuration file.
|
||||
<p><br>Note that this is <em>NOT</em> a guarantee that the services specified in the
|
||||
<p>Note that this is <em>NOT</em> a guarantee that the services specified in the
|
||||
configuration file will be available or will operate as expected.
|
||||
<p><br>If the optional host name and host IP address are specified on the
|
||||
<p>If the optional host name and host IP address are specified on the
|
||||
command line, this test program will run through the service entries
|
||||
reporting whether the specified host has access to each service.
|
||||
<p><br>If <strong>testparm</strong> finds an error in the <a href="smb.conf.5.html"><strong>smb.conf</strong></a>
|
||||
<p>If <strong>testparm</strong> finds an error in the <a href="smb.conf.5.html"><strong>smb.conf</strong></a>
|
||||
file it returns an exit code of 1 to the calling program, else it returns
|
||||
an exit code of 0. This allows shell scripts to test the output from
|
||||
<strong>testparm</strong>.
|
||||
<p><br><a name="OPTIONS"></a>
|
||||
<p><a name="OPTIONS"></a>
|
||||
<h2>OPTIONS</h2>
|
||||
|
||||
<p><br><ul>
|
||||
<p><br><a name="minuss"></a>
|
||||
<li><strong><strong>-s</strong></strong> Without this option, <strong>testparm</strong> will prompt for a
|
||||
<p><dl>
|
||||
<p><a name="minuss"></a>
|
||||
<p></p><dt><strong><strong>-s</strong></strong><dd> Without this option, <strong>testparm</strong> will prompt for a
|
||||
carriage return after printing the service names and before dumping
|
||||
the service definitions.
|
||||
<p><br><a name="minush"></a>
|
||||
<li><strong><strong>-h</strong></strong> Print usage message
|
||||
<p><br><a name="minusL"></a>
|
||||
<li><strong><strong>-L servername</strong></strong> Sets the value of the %L macro to servername. This
|
||||
<p><a name="minush"></a>
|
||||
<p></p><dt><strong><strong>-h</strong></strong><dd> Print usage message
|
||||
<p><a name="minusL"></a>
|
||||
<p></p><dt><strong><strong>-L servername</strong></strong><dd> Sets the value of the %L macro to servername. This
|
||||
is useful for testing include files specified with the %L macro.
|
||||
<p><br><a name="configfilename"></a>
|
||||
<li><strong><strong>configfilename</strong></strong> This is the name of the configuration file to
|
||||
<p><a name="configfilename"></a>
|
||||
<p></p><dt><strong><strong>configfilename</strong></strong><dd> This is the name of the configuration file to
|
||||
check. If this parameter is not present then the default
|
||||
<a href="smb.conf.5.html"><strong>smb.conf</strong></a> file will be checked.
|
||||
<p><br><a name="hostname"></a>
|
||||
<li><strong><strong>hostname</strong></strong> If this parameter and the following are specified,
|
||||
<p><a name="hostname"></a>
|
||||
<p></p><dt><strong><strong>hostname</strong></strong><dd> If this parameter and the following are specified,
|
||||
then testparm will examine the <a href="smb.conf.5.html#hostsallow"><strong>"hosts
|
||||
allow"</strong></a> and <a href="smb.conf.5.html#hostsdeny"><strong>"hosts
|
||||
deny"</strong></a> parameters in the
|
||||
@ -69,45 +69,45 @@ deny"</strong></a> parameters in the
|
||||
with this IP address would be allowed access to the
|
||||
<a href="smbd.8.html"><strong>smbd</strong></a> server. If this parameter is supplied, the
|
||||
<a href="testparm.1.html#hostIP">hostIP</a> parameter must also be supplied.
|
||||
<p><br><a name="hostIP"></a>
|
||||
<li><strong><strong>hostIP</strong></strong> This is the IP address of the host specified in the
|
||||
<p><a name="hostIP"></a>
|
||||
<p></p><dt><strong><strong>hostIP</strong></strong><dd> This is the IP address of the host specified in the
|
||||
previous parameter. This address must be supplied if the hostname
|
||||
parameter is supplied.
|
||||
<p><br></ul>
|
||||
<p><br><a name="FILES"></a>
|
||||
<p></dl>
|
||||
<p><a name="FILES"></a>
|
||||
<h2>FILES</h2>
|
||||
|
||||
<p><br><a href="smb.conf.5.html"><strong>smb.conf</strong></a>. This is usually the name of the
|
||||
<p><a href="smb.conf.5.html"><strong>smb.conf</strong></a>. This is usually the name of the
|
||||
configuration file used by <a href="smbd.8.html"><strong>smbd</strong></a>.
|
||||
<p><br><a name="DIAGNOSTICS"></a>
|
||||
<p><a name="DIAGNOSTICS"></a>
|
||||
<h2>DIAGNOSTICS</h2>
|
||||
|
||||
<p><br>The program will issue a message saying whether the configuration file
|
||||
<p>The program will issue a message saying whether the configuration file
|
||||
loaded OK or not. This message may be preceded by errors and warnings
|
||||
if the file did not load. If the file was loaded OK, the program then
|
||||
dumps all known service details to stdout.
|
||||
<p><br><a name="VERSION"></a>
|
||||
<p><a name="VERSION"></a>
|
||||
<h2>VERSION</h2>
|
||||
|
||||
<p><br>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><br><a name="SEEALSO"></a>
|
||||
<p>This man page is correct for version 2.0 of the Samba suite.
|
||||
<p><a name="SEEALSO"></a>
|
||||
<h2>SEE ALSO</h2>
|
||||
|
||||
<p><br><a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>, <a href="smbd.8.html"><strong>smbd (8)</strong></a>
|
||||
<p><br><a name="AUTHOR"></a>
|
||||
<p><a href="smb.conf.5.html"><strong>smb.conf (5)</strong></a>, <a href="smbd.8.html"><strong>smbd (8)</strong></a>
|
||||
<p><a name="AUTHOR"></a>
|
||||
<h2>AUTHOR</h2>
|
||||
|
||||
<p><br>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed
|
||||
<p>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed.
|
||||
<p><br>The original Samba man pages were written by Karl Auer. The man page
|
||||
<p>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
|
||||
<a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>)
|
||||
and updated for the Samba2.0 release by Jeremy Allison.
|
||||
<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>.
|
||||
<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
|
||||
<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>.
|
||||
<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
comments etc.
|
||||
</body>
|
||||
|
||||
@ -3,9 +3,10 @@
|
||||
|
||||
|
||||
|
||||
|
||||
<html><head><title>testprns (1)</title>
|
||||
|
||||
<link rev="made" href="mailto:samba-bugs@samba.org">
|
||||
<link rev="made" href="mailto:samba@samba.org">
|
||||
</head>
|
||||
<body>
|
||||
|
||||
@ -15,33 +16,32 @@
|
||||
<h2>Samba</h2>
|
||||
<h2>23 Oct 1998</h2>
|
||||
|
||||
|
||||
|
||||
|
||||
<p><br><a name="NAME"></a>
|
||||
<p><a name="NAME"></a>
|
||||
<h2>NAME</h2>
|
||||
testprns - check printer name for validity with smbd
|
||||
<p><br><a name="SYNOPSIS"></a>
|
||||
<p><a name="SYNOPSIS"></a>
|
||||
<h2>SYNOPSIS</h2>
|
||||
|
||||
<p><br><strong>testprns</strong> <a href="testprns.1.html#printername">printername</a> [<a href="testprns.1.html#printcapname">printcapname</a>]
|
||||
<p><br><a name="DESCRIPTION"></a>
|
||||
<p><strong>testprns</strong> <a href="testprns.1.html#printername">printername</a> [<a href="testprns.1.html#printcapname">printcapname</a>]
|
||||
<p><a name="DESCRIPTION"></a>
|
||||
<h2>DESCRIPTION</h2>
|
||||
|
||||
<p><br>This program is part of the <strong>Samba</strong> suite.
|
||||
<p><br><strong>testprns</strong> is a very simple test program to determine whether a
|
||||
<p>This program is part of the <strong>Samba</strong> suite.
|
||||
<p><strong>testprns</strong> is a very simple test program to determine whether a
|
||||
given printer name is valid for use in a service to be provided by
|
||||
<a href="smbd.8.html"><strong>smbd</strong></a>.
|
||||
<p><br>"Valid" in this context means "can be found in the printcap
|
||||
<p>"Valid" in this context means "can be found in the printcap
|
||||
specified". This program is very stupid - so stupid in fact that it
|
||||
would be wisest to always specify the printcap file to use.
|
||||
<p><br><a name="OPTIONS"></a>
|
||||
<p><a name="OPTIONS"></a>
|
||||
<h2>OPTIONS</h2>
|
||||
|
||||
<p><br><ul>
|
||||
<p><br><a name="printername"></a>
|
||||
<li><strong><strong>printername</strong></strong> The printer name to validate.
|
||||
<p><br>Printer names are taken from the first field in each record in the
|
||||
<p><dl>
|
||||
<p><a name="printername"></a>
|
||||
<p></p><dt><strong><strong>printername</strong></strong><dd> The printer name to validate.
|
||||
<p>Printer names are taken from the first field in each record in the
|
||||
printcap file, single printer names and sets of aliases separated by
|
||||
vertical bars ("|") are recognized. Note that no validation or
|
||||
checking of the printcap syntax is done beyond that required to
|
||||
@ -49,49 +49,49 @@ extract the printer name. It may be that the print spooling system is
|
||||
more forgiving or less forgiving than <strong>testprns</strong>. However, if
|
||||
<strong>testprns</strong> finds the printer then <a href="smbd.8.html"><strong>smbd</strong></a> should
|
||||
do so as well.
|
||||
<p><br><a name="printcapname"></a>
|
||||
<li><strong><strong>printcapname</strong></strong> This is the name of the printcap file within
|
||||
<p><a name="printcapname"></a>
|
||||
<p></p><dt><strong><strong>printcapname</strong></strong><dd> This is the name of the printcap file within
|
||||
which to search for the given printer name.
|
||||
<p><br>If no printcap name is specified <strong>testprns</strong> will attempt to scan the
|
||||
<p>If no printcap name is specified <strong>testprns</strong> will attempt to scan the
|
||||
printcap file name specified at compile time.
|
||||
<p><br></ul>
|
||||
<p><br><a name="FILES"></a>
|
||||
<p></dl>
|
||||
<p><a name="FILES"></a>
|
||||
<h2>FILES</h2>
|
||||
|
||||
<p><br><strong>/etc/printcap</strong> This is usually the default printcap file to
|
||||
<p><strong>/etc/printcap</strong> This is usually the default printcap file to
|
||||
scan. See <strong>printcap (5)</strong>.
|
||||
<p><br><a name="DIAGNOSTICS"></a>
|
||||
<p><a name="DIAGNOSTICS"></a>
|
||||
<h2>DIAGNOSTICS</h2>
|
||||
|
||||
<p><br>If a printer is found to be valid, the message "Printer name
|
||||
<p>If a printer is found to be valid, the message "Printer name
|
||||
<printername> is valid" will be displayed.
|
||||
<p><br>If a printer is found to be invalid, the message "Printer name
|
||||
<p>If a printer is found to be invalid, the message "Printer name
|
||||
<printername> is not valid" will be displayed.
|
||||
<p><br>All messages that would normally be logged during operation of the
|
||||
<p>All messages that would normally be logged during operation of the
|
||||
<a href="samba.7.html"><strong>Samba</strong></a> daemons are logged by this program to the
|
||||
file <code>test.log</code> in the current directory. The program runs at
|
||||
debuglevel 3, so quite extensive logging information is written. The
|
||||
log should be checked carefully for errors and warnings.
|
||||
<p><br>Other messages are self-explanatory.
|
||||
<p><br><a name="SEEALSO"></a>
|
||||
<p>Other messages are self-explanatory.
|
||||
<p><a name="SEEALSO"></a>
|
||||
<h2>SEE ALSO</h2>
|
||||
|
||||
<p><br><strong>printcap (5)</strong>, <a href="smbd.8.html"><strong>smbd (8)</strong></a>, <a href="smbclient.1.html"><strong>smbclient
|
||||
<p><strong>printcap (5)</strong>, <a href="smbd.8.html"><strong>smbd (8)</strong></a>, <a href="smbclient.1.html"><strong>smbclient
|
||||
(1)</strong></a>
|
||||
<p><br><a name="AUTHOR"></a>
|
||||
<p><a name="AUTHOR"></a>
|
||||
<h2>AUTHOR</h2>
|
||||
|
||||
<p><br>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed
|
||||
<p>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed.
|
||||
<p><br>The original Samba man pages were written by Karl Auer. The man page
|
||||
<p>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
|
||||
<a href="ftp://ftp.icce.rug.nl/pub/unix/"><strong>ftp://ftp.icce.rug.nl/pub/unix/</strong></a>)
|
||||
and updated for the Samba2.0 release by Jeremy Allison.
|
||||
<a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>.
|
||||
<p><br>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
|
||||
<a href="mailto:samba@samba.org"><em>samba@samba.org</em></a>.
|
||||
<p>See <a href="samba.7.html"><strong>samba (7)</strong></a> to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
comments etc.
|
||||
</body>
|
||||
|
||||
@ -36,8 +36,10 @@ different databases services such as NIS or DNS. The exact behaviour can
|
||||
be configured throught the <code>/etc/nsswitch.conf</code> file. Users and groups
|
||||
are allocated as they are resolved to a range of user and group ids
|
||||
specified by the administrator of the Samba system.
|
||||
<p>The service provided by <strong>winbindd</strong> is called `winbind' and can be used to
|
||||
resolve user and group information from a Windows NT server.
|
||||
<p>The service provided by <strong>winbindd</strong> is called `winbind' and can be
|
||||
used to resolve user and group information from a Windows NT server.
|
||||
The service can also provide authentication services via an associated
|
||||
PAM module.
|
||||
<p>The following nsswitch databases are implemented by the <strong>winbindd</strong>
|
||||
service:
|
||||
<p><dl>
|
||||
@ -52,8 +54,13 @@ service:
|
||||
<code>/etc/nsswitch.conf</code> file can be used to initially resolve user and group
|
||||
information from <code>/etc/passwd</code> and <code>/etc/group</code> and then from the
|
||||
Windows NT server.
|
||||
<p><code>passwd: files winbind</code>
|
||||
<p><code>group: files winbind</code>
|
||||
<p><pre>
|
||||
|
||||
passwd: files winbind
|
||||
group: files winbind
|
||||
|
||||
</pre>
|
||||
|
||||
<p><a name="OPTIONS"></a>
|
||||
<h2>OPTIONS</h2>
|
||||
|
||||
@ -96,6 +103,20 @@ parameters in the <a href="smb.conf.5.html"><strong>smb.conf</strong></a> file.
|
||||
should be specified in the [global] section of
|
||||
<a href="smb.conf.5.html"><strong>smb.conf</strong></a>.
|
||||
<p><dl>
|
||||
<p><p></p><dt><strong>winbind separator</strong><dd>
|
||||
<p>The winbind separator option allows you to specify how NT domain names
|
||||
and user names are combined into unix user names when presented to
|
||||
users. By default winbind will use the traditional \ separator so
|
||||
that the unix user names look like DOMAIN\username. In some cases
|
||||
this separator character may cause problems as the \ character has
|
||||
special meaning in unix shells. In that case you can use the winbind
|
||||
separator option to specify an alternative sepataror character. Good
|
||||
alternatives may be / (although that conflicts with the unix directory
|
||||
separator) or a + character. The + character appears to be the best
|
||||
choice for 100% compatibility with existing unix utilities, but may be
|
||||
an aesthetically bad choice depending on your taste.
|
||||
<p><strong>Example:</strong>
|
||||
<code> winbind separator = +</code>
|
||||
<p><p></p><dt><strong>winbind uid</strong><dd>
|
||||
<p>The winbind uid parameter specifies the range of user ids that are
|
||||
allocated by the <a href="winbindd.8.html"><strong>winbindd</strong></a> daemon. This range of
|
||||
@ -117,9 +138,16 @@ conflicts can occur otherwise.
|
||||
<p><p></p><dt><strong>winbind cache time</strong><dd>
|
||||
<p>This parameter specifies the number of seconds the
|
||||
<a href="winbindd.8.html"><strong>winbindd</strong></a> daemon will cache user and group
|
||||
information before querying a Windows NT server again.
|
||||
information before querying a Windows NT server again. When a item in
|
||||
the cache is older than this time winbindd will ask the domain
|
||||
controller for the sequence number of the servers account database. If
|
||||
the sequence number has not changed then the cached item is marked as
|
||||
valid for a further "winbind cache time" seconds. Otherwise the item
|
||||
is fetched from the server. This means that as long as the account
|
||||
database is not actively changing winbindd will only have to send one
|
||||
sequence number query packet every "winbind cache time" seconds.
|
||||
<p><strong>Default:</strong>
|
||||
<code> winbind cache type = 15</code>
|
||||
<code> winbind cache time = 15</code>
|
||||
<p><p></p><dt><strong>template homedir</strong><dd>
|
||||
<p>When filling out the user information for a Windows NT user, the
|
||||
<a href="winbindd.8.html"><strong>winbindd</strong></a> daemon uses this parameter to fill in
|
||||
@ -131,12 +159,85 @@ is present it is substituted with the user's Windows NT user name.
|
||||
<p><p></p><dt><strong>template shell</strong><dd>
|
||||
<p>When filling out the user information for a Windows NT user, the
|
||||
<a href="winbindd.8.html"><strong>winbindd</strong></a> daemon uses this parameter to fill in
|
||||
the home directory for that user. If the string <code>%D</code> is present it is
|
||||
substituted with the user's Windows NT domain name. If the string <code>%U</code>
|
||||
is present it is substituted with the user's Windows NT user name.
|
||||
the shell for that user.
|
||||
<p><strong>Default:</strong>
|
||||
<code> template homedir = /home/%D/%U</code>
|
||||
<code> template shell = /bin/false</code>
|
||||
<p></dl>
|
||||
<p><a name="EXAMPLESETUP"></a>
|
||||
<h2>EXAMPLE SETUP</h2>
|
||||
|
||||
<p>To setup winbindd for user and group lookups plus authentication from
|
||||
a domain controller use something like the following setup. This was
|
||||
tested on a RedHat 6.2 Linux box.
|
||||
<p>In /etc/nsswitch.conf put the following:
|
||||
<pre>
|
||||
|
||||
passwd: files winbind
|
||||
group: files winbind
|
||||
|
||||
</pre>
|
||||
|
||||
<p>In /etc/pam.d/* replace the auth lines with something like this:
|
||||
<pre>
|
||||
|
||||
auth required /lib/security/pam_securetty.so
|
||||
auth required /lib/security/pam_nologin.so
|
||||
auth sufficient /lib/security/pam_winbind.so
|
||||
auth required /lib/security/pam_pwdb.so use_first_pass shadow nullok
|
||||
|
||||
</pre>
|
||||
|
||||
<p>Note in particular the use of the sufficient keyword and the
|
||||
use_first_pass keyword.
|
||||
<p>Now replace the account lines with this:
|
||||
<pre>
|
||||
|
||||
account required /lib/security/pam_winbind.so
|
||||
|
||||
</pre>
|
||||
|
||||
<p>The next step is to join the domain. To do that use the samedit
|
||||
program like this:
|
||||
<pre>
|
||||
|
||||
samedit -S '*' -W DOMAIN -UAdministrator
|
||||
|
||||
</pre>
|
||||
|
||||
<p>Then within samedit run the command:
|
||||
<pre>
|
||||
|
||||
createuser MACHINE$ -j DOMAIN -L
|
||||
|
||||
</pre>
|
||||
|
||||
<p>This assumes your domain is called DOMAIN and your Samba workstation
|
||||
is called MACHINE.
|
||||
<p>Next copy libnss_winbind.so.2 to /lib and pam_winbind.so to
|
||||
/lib/security.
|
||||
<p>Finally, setup a smb.conf containing directives like the following:
|
||||
<pre>
|
||||
|
||||
[global]
|
||||
winbind separator = +
|
||||
winbind cache time = 10
|
||||
template shell = /bin/bash
|
||||
template homedir = /home/%D/%U
|
||||
winbind uid = 10000-20000
|
||||
winbind gid = 10000-20000
|
||||
workgroup = DOMAIN
|
||||
security = domain
|
||||
password server = *
|
||||
|
||||
</pre>
|
||||
|
||||
<p>Now start winbindd and you should find that your user and group
|
||||
database is expanded to include your NT users and groups, and that you
|
||||
can login to your unix box as a domain user, using the DOMAIN+user
|
||||
syntax for the username. You may wish to use the commands "getent
|
||||
passwd" and "getent group" to confirm the correct operation of
|
||||
winbindd.
|
||||
<p>NOTE: nmbd must be running on the local machine for winbindd to work.
|
||||
<p><a name="FILES"></a>
|
||||
<h2>FILES</h2>
|
||||
|
||||
@ -170,9 +271,8 @@ is damaged or destroyed then the mappings will be lost.
|
||||
<h2>AUTHOR</h2>
|
||||
|
||||
<p>The original Samba software and related utilities were created by
|
||||
Andrew Tridgell <a href="mailto:samba-bugs@samba.org"><em>samba-bugs@samba.org</em></a>. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed.
|
||||
Andrew Tridgell. Samba is now developed by the Samba Team as an Open
|
||||
Source project.
|
||||
<p>Winbindd was written by Tim Potter.
|
||||
</body>
|
||||
</html>
|
||||
|
||||
@ -76,7 +76,7 @@ This man page is correct for version 2\&.0 of the Samba suite\&.
|
||||
.SH "AUTHOR"
|
||||
.PP
|
||||
The original Samba software and related utilities were created by
|
||||
Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed
|
||||
Andrew Tridgell samba@samba\&.org\&. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed\&.
|
||||
.PP
|
||||
@ -85,7 +85,7 @@ sources were converted to YODL format (another excellent piece of Open
|
||||
Source software, available at
|
||||
\fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP)
|
||||
and updated for the Samba2\&.0 release by Jeremy Allison\&.
|
||||
\fIsamba-bugs@samba\&.org\fP\&.
|
||||
samba@samba\&.org\&.
|
||||
.PP
|
||||
See \fBsamba (7)\fP to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
|
||||
@ -61,7 +61,7 @@ provided in the Samba distribution for codepages 437 (USA), 737
|
||||
866 (Cyrillic), 932 (Kanji SJIS), 936 (Simplified Chinese), 949
|
||||
(Hangul) and 950 (Traditional Chinese)\&. Users are encouraged to write
|
||||
text codepage definition files for their own code pages and donate
|
||||
them to \fIsamba-bugs@samba\&.org\fP\&. All codepage files in the
|
||||
them to samba@samba\&.org\&. All codepage files in the
|
||||
Samba \fIsource/codepages\fP directory are compiled and installed when a
|
||||
\fI\'make install\'\fP command is issued there\&.
|
||||
.PP
|
||||
@ -128,7 +128,7 @@ This man page is correct for version 2\&.0 of the Samba suite\&.
|
||||
.SH "AUTHOR"
|
||||
.PP
|
||||
The original Samba software and related utilities were created by
|
||||
Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed
|
||||
Andrew Tridgell samba@samba\&.org\&. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed\&.
|
||||
.PP
|
||||
@ -137,7 +137,7 @@ sources were converted to YODL format (another excellent piece of Open
|
||||
Source software, available at
|
||||
\fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP)
|
||||
and updated for the Samba2\&.0 release by Jeremy Allison\&.
|
||||
\fIsamba-bugs@samba\&.org\fP\&.
|
||||
samba@samba\&.org\&.
|
||||
.PP
|
||||
See \fBsamba (7)\fP to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
|
||||
@ -6,7 +6,7 @@ naming services to clients
|
||||
.PP
|
||||
.SH "SYNOPSIS"
|
||||
.PP
|
||||
\fBnmbd\fP [-D] [-a] [-o] [-h] [-V] [-H lmhosts file] [-d debuglevel] [-l log file basename] [-n primary NetBIOS name] [-p port number] [-s configuration file] [-i NetBIOS scope]
|
||||
\fBnmbd\fP [-D] [-a] [-o] [-h] [-V] [-H lmhosts file] [-d debuglevel] [-l log file basename] [-n primary NetBIOS name] [-p port number] [-s configuration file]
|
||||
.PP
|
||||
.SH "DESCRIPTION"
|
||||
.PP
|
||||
@ -136,14 +136,6 @@ this may be changed when Samba is autoconfigured\&.
|
||||
The file specified contains the configuration details required by the
|
||||
server\&. See \fBsmb\&.conf (5)\fP for more information\&.
|
||||
.IP
|
||||
.IP "\fB-i scope\fP"
|
||||
This specifies a NetBIOS scope that \fBnmbd\fP will use
|
||||
to communicate with when generating NetBIOS names\&. For details on the
|
||||
use of NetBIOS scopes, see rfc1001\&.txt and rfc1002\&.txt\&. NetBIOS scopes
|
||||
are \fIvery\fP rarely used, only set this parameter if you are the
|
||||
system administrator in charge of all the NetBIOS systems you
|
||||
communicate with\&.
|
||||
.IP
|
||||
.PP
|
||||
.SH "FILES"
|
||||
.PP
|
||||
@ -212,7 +204,7 @@ http://samba\&.org/cifs/\&.
|
||||
.SH "AUTHOR"
|
||||
.PP
|
||||
The original Samba software and related utilities were created by
|
||||
Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed
|
||||
Andrew Tridgell samba@samba\&.org\&. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed\&.
|
||||
.PP
|
||||
@ -221,7 +213,7 @@ sources were converted to YODL format (another excellent piece of Open
|
||||
Source software, available at
|
||||
\fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP)
|
||||
and updated for the Samba2\&.0 release by Jeremy Allison\&.
|
||||
\fIsamba-bugs@samba\&.org\fP\&.
|
||||
samba@samba\&.org\&.
|
||||
.PP
|
||||
See \fBsamba (7)\fP to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
|
||||
@ -139,7 +139,7 @@ This man page is correct for version 2\&.0 of the Samba suite\&.
|
||||
.SH "AUTHOR"
|
||||
.PP
|
||||
The original Samba software and related utilities were created by
|
||||
Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed
|
||||
Andrew Tridgell samba@samba\&.org\&. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed\&.
|
||||
.PP
|
||||
@ -148,7 +148,7 @@ sources were converted to YODL format (another excellent piece of Open
|
||||
Source software, available at
|
||||
\fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP)
|
||||
and updated for the Samba2\&.0 release by Jeremy Allison\&.
|
||||
\fIsamba-bugs@samba\&.org\fP\&.
|
||||
samba@samba\&.org\&.
|
||||
.PP
|
||||
See \fBsamba (7)\fP to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
|
||||
@ -20,7 +20,7 @@ described in a separate manual page\&. It is strongly recommended that
|
||||
you read the documentation that comes with Samba and the manual pages
|
||||
of those components that you use\&. If the manual pages aren\'t clear
|
||||
enough then please send a patch or bug report
|
||||
to \fIsamba-bugs@samba\&.org\fP\&.
|
||||
to samba@samba\&.org\&.
|
||||
.PP
|
||||
.IP
|
||||
.IP "\fBsmbd\fP"
|
||||
@ -121,13 +121,13 @@ This man page is correct for version 2\&.0 of the Samba suite\&.
|
||||
.SH "CONTRIBUTIONS"
|
||||
.PP
|
||||
If you wish to contribute to the Samba project, then I suggest you
|
||||
join the Samba mailing list at \fIsamba@samba\&.org\fP\&. See the
|
||||
join the Samba mailing list at samba@samba\&.org\&. See the
|
||||
Web page at
|
||||
http://samba\&.org/listproc
|
||||
for details on how to do this\&.
|
||||
.PP
|
||||
If you have patches to submit or bugs to report then you may mail them
|
||||
directly to \fIsamba-bugs@samba\&.org\fP\&. Note, however, that due to
|
||||
directly to samba@samba\&.org\&. Note, however, that due to
|
||||
the enormous popularity of this package the Samba Team may take some
|
||||
time to respond to mail\&. We prefer patches in \fIdiff -u\fP format\&.
|
||||
.PP
|
||||
@ -149,7 +149,7 @@ http://samba\&.org/samba/samba-thanks\&.html\&.
|
||||
.SH "AUTHOR"
|
||||
.PP
|
||||
The original Samba software and related utilities were created by
|
||||
Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed
|
||||
Andrew Tridgell samba@samba\&.org\&. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed\&.
|
||||
.PP
|
||||
@ -158,4 +158,4 @@ sources were converted to YODL format (another excellent piece of Open
|
||||
Source software, available at
|
||||
\fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP)
|
||||
and updated for the Samba2\&.0 release by Jeremy Allison\&.
|
||||
\fIsamba-bugs@samba\&.org\fP\&.
|
||||
samba@samba\&.org\&.
|
||||
|
||||
@ -86,7 +86,7 @@ write access to the path \f(CW/home/bar\fP\&. The share is accessed via
|
||||
the share name "foo":
|
||||
.PP
|
||||
|
||||
.DS
|
||||
.nf
|
||||
|
||||
|
||||
|
||||
@ -95,7 +95,7 @@ the share name "foo":
|
||||
writeable = true
|
||||
|
||||
|
||||
.DE
|
||||
.fi
|
||||
|
||||
|
||||
.PP
|
||||
@ -106,7 +106,7 @@ is via calls to open, write to and close a spool file\&. The
|
||||
as the default guest user (specified elsewhere):
|
||||
.PP
|
||||
|
||||
.DS
|
||||
.nf
|
||||
|
||||
|
||||
[aprinter]
|
||||
@ -115,7 +115,7 @@ as the default guest user (specified elsewhere):
|
||||
printable = true
|
||||
guest ok = true
|
||||
|
||||
.DE
|
||||
.fi
|
||||
|
||||
|
||||
.PP
|
||||
@ -175,13 +175,13 @@ section can specify, though some make more sense than others\&. The
|
||||
following is a typical and suitable [homes] section:
|
||||
.IP
|
||||
|
||||
.DS
|
||||
.nf
|
||||
|
||||
|
||||
[homes]
|
||||
writeable = yes
|
||||
|
||||
.DE
|
||||
.fi
|
||||
|
||||
|
||||
.IP
|
||||
@ -237,7 +237,7 @@ directory with the sticky bit set on it\&. A typical \fB[printers]\fP entry
|
||||
would look like this:
|
||||
.IP
|
||||
|
||||
.DS
|
||||
.nf
|
||||
|
||||
|
||||
[printers]
|
||||
@ -245,7 +245,7 @@ would look like this:
|
||||
guest ok = yes
|
||||
printable = yes
|
||||
|
||||
.DE
|
||||
.fi
|
||||
|
||||
|
||||
.IP
|
||||
@ -256,10 +256,10 @@ pseudo-printcap\&. This is a file consisting of one or more lines like
|
||||
this:
|
||||
.IP
|
||||
|
||||
.DS
|
||||
.nf
|
||||
|
||||
alias|alias|alias|alias\&.\&.\&.
|
||||
.DE
|
||||
.fi
|
||||
|
||||
|
||||
.IP
|
||||
@ -377,7 +377,7 @@ negotiation\&. It can be one of CORE, COREPLUS, LANMAN1, LANMAN2 or NT1\&.
|
||||
machine\&. Only some are recognized, and those may not be 100%
|
||||
reliable\&. It currently recognizes Samba, WfWg, WinNT and
|
||||
Win95\&. Anything else will be known as "UNKNOWN"\&. If it gets it wrong
|
||||
then sending a level 3 log to \fIsamba@samba\&.org\fP
|
||||
then sending a level 3 log to samba@samba\&.org
|
||||
should allow it to be fixed\&.
|
||||
.IP
|
||||
.IP o
|
||||
@ -1993,7 +1993,7 @@ interesting things\&.
|
||||
.IP
|
||||
\fBExample:\fP
|
||||
|
||||
.DS
|
||||
.nf
|
||||
|
||||
|
||||
default service = pub
|
||||
@ -2001,7 +2001,7 @@ interesting things\&.
|
||||
[pub]
|
||||
path = /%S
|
||||
|
||||
.DE
|
||||
.fi
|
||||
|
||||
|
||||
.IP
|
||||
@ -2138,26 +2138,26 @@ and remaining space will be used\&.\fP
|
||||
Where the script dfree (which must be made executable) could be:
|
||||
.IP
|
||||
|
||||
.DS
|
||||
.nf
|
||||
|
||||
|
||||
#!/bin/sh
|
||||
df $1 | tail -1 | awk \'{print $2" "$4}\'
|
||||
|
||||
.DE
|
||||
.fi
|
||||
|
||||
|
||||
.IP
|
||||
or perhaps (on Sys V based systems):
|
||||
.IP
|
||||
|
||||
.DS
|
||||
.nf
|
||||
|
||||
|
||||
#!/bin/sh
|
||||
/usr/bin/df -k $1 | tail -1 | awk \'{print $3" "$5}\'
|
||||
|
||||
.DE
|
||||
.fi
|
||||
|
||||
|
||||
.IP
|
||||
@ -2267,7 +2267,7 @@ Samba NT Domain Controller Code\&. It may be removed in a later release\&.
|
||||
To work with the latest code builds that may have more support for
|
||||
Samba NT Domain Controller functionality please subscribe to the
|
||||
mailing list \fBSamba-ntdom\fP available by sending email to
|
||||
\fIlistproc@samba\&.org\fP
|
||||
listproc@samba\&.org
|
||||
.IP
|
||||
.IP "\fBdomain admin users (G)\fP"
|
||||
.IP
|
||||
@ -2276,7 +2276,7 @@ Samba NT Domain Controller Code\&. It may be removed in a later release\&.
|
||||
To work with the latest code builds that may have more support for
|
||||
Samba NT Domain Controller functionality please subscribe to the
|
||||
mailing list \fBSamba-ntdom\fP available by sending email to
|
||||
\fIlistproc@samba\&.org\fP
|
||||
listproc@samba\&.org
|
||||
.IP
|
||||
.IP "\fBdomain groups (G)\fP"
|
||||
.IP
|
||||
@ -2285,7 +2285,7 @@ Samba NT Domain Controller Code\&. It may be removed in a later release\&.
|
||||
To work with the latest code builds that may have more support for
|
||||
Samba NT Domain Controller functionality please subscribe to the
|
||||
mailing list \fBSamba-ntdom\fP available by sending email to
|
||||
\fIlistproc@samba\&.org\fP
|
||||
listproc@samba\&.org
|
||||
.IP
|
||||
.IP "\fBdomain guest group (G)\fP"
|
||||
.IP
|
||||
@ -2294,7 +2294,7 @@ Samba NT Domain Controller Code\&. It may be removed in a later release\&.
|
||||
To work with the latest code builds that may have more support for
|
||||
Samba NT Domain Controller functionality please subscribe to the
|
||||
mailing list \fBSamba-ntdom\fP available by sending email to
|
||||
\fIlistproc@samba\&.org\fP
|
||||
listproc@samba\&.org
|
||||
.IP
|
||||
.IP "\fBdomain guest users (G)\fP"
|
||||
.IP
|
||||
@ -2303,7 +2303,7 @@ Samba NT Domain Controller Code\&. It may be removed in a later release\&.
|
||||
To work with the latest code builds that may have more support for
|
||||
Samba NT Domain Controller functionality please subscribe to the
|
||||
mailing list \fBSamba-ntdom\fP available by sending email to
|
||||
\fIlistproc@samba\&.org\fP
|
||||
listproc@samba\&.org
|
||||
.IP
|
||||
.IP "\fBdomain logons (G)\fP"
|
||||
.IP
|
||||
@ -2796,13 +2796,13 @@ files"\fP and \fB"case sensitive"\fP\&.
|
||||
.IP
|
||||
\fBDefault\fP
|
||||
|
||||
.DS
|
||||
.nf
|
||||
|
||||
|
||||
No files or directories are hidden by this option (dot files are
|
||||
hidden by default because of the "hide dot files" option)\&.
|
||||
|
||||
.DE
|
||||
.fi
|
||||
|
||||
|
||||
.IP
|
||||
@ -4480,20 +4480,20 @@ debug"\fP\&.
|
||||
.IP
|
||||
\fBExample:\fP
|
||||
|
||||
.DS
|
||||
.nf
|
||||
|
||||
passwd chat = "*Enter OLD password*" %o\en "*Enter NEW password*" %n\en "*Reenter NEW password*" %n\en "*Password changed*"
|
||||
|
||||
.DE
|
||||
.fi
|
||||
|
||||
|
||||
.IP
|
||||
\fBDefault:\fP
|
||||
|
||||
.DS
|
||||
.nf
|
||||
|
||||
passwd chat = *old*password* %o\en *new*password* %n\en *new*password* %n\en *changed*
|
||||
.DE
|
||||
.fi
|
||||
|
||||
|
||||
.IP
|
||||
@ -4745,12 +4745,12 @@ An interesting example is to send the users a welcome message every
|
||||
time they log in\&. Maybe a message of the day? Here is an example:
|
||||
.IP
|
||||
|
||||
.DS
|
||||
.nf
|
||||
|
||||
|
||||
preexec = csh -c \'echo \e"Welcome to %S!\e" | /usr/local/samba/bin/smbclient -M %m -I %I\' &
|
||||
|
||||
.DE
|
||||
.fi
|
||||
|
||||
|
||||
.IP
|
||||
@ -4923,7 +4923,7 @@ to obtain a printer list\&.
|
||||
A minimal printcap file would look something like this:
|
||||
.IP
|
||||
|
||||
.DS
|
||||
.nf
|
||||
|
||||
|
||||
print1|My Printer 1
|
||||
@ -4932,7 +4932,7 @@ A minimal printcap file would look something like this:
|
||||
print4|My Printer 4
|
||||
print5|My Printer 5
|
||||
|
||||
.DE
|
||||
.fi
|
||||
|
||||
|
||||
.IP
|
||||
@ -5807,7 +5807,7 @@ You may find that on some systems Samba will say "Unknown socket
|
||||
option" when you supply an option\&. This means you either incorrectly
|
||||
typed it or you need to add an include file to includes\&.h for your OS\&.
|
||||
If the latter is the case please send the patch to
|
||||
\fIsamba@samba\&.org\fP\&.
|
||||
samba@samba\&.org\&.
|
||||
.IP
|
||||
Any of the supported socket options may be combined in any way you
|
||||
like, as long as your OS allows it\&.
|
||||
@ -6474,13 +6474,13 @@ information on how this parameter determines access to the services\&.
|
||||
.IP
|
||||
\fBExamples:\fP
|
||||
|
||||
.DS
|
||||
.nf
|
||||
|
||||
|
||||
username = fred
|
||||
username = fred, mary, jack, jane, @users, @pcgroup
|
||||
|
||||
.DE
|
||||
.fi
|
||||
|
||||
|
||||
.IP
|
||||
@ -6564,13 +6564,13 @@ and map the rest to guest\&. Note the use of the \f(CW\'!\'\fP to tell Samba
|
||||
to stop processing if it gets a match on that line\&.
|
||||
.IP
|
||||
|
||||
.DS
|
||||
.nf
|
||||
|
||||
|
||||
!sys = mary fred
|
||||
guest = *
|
||||
|
||||
.DE
|
||||
.fi
|
||||
|
||||
|
||||
.IP
|
||||
@ -6686,14 +6686,14 @@ is a pointless thing to do as it\'s already there) you could do one of
|
||||
the following
|
||||
.IP
|
||||
|
||||
.DS
|
||||
.nf
|
||||
|
||||
|
||||
valid chars = Z
|
||||
valid chars = z:Z
|
||||
valid chars = 0132:0172
|
||||
|
||||
.DE
|
||||
.fi
|
||||
|
||||
|
||||
.IP
|
||||
@ -6710,13 +6710,13 @@ See also the \fB"client code page"\fP parameter\&.
|
||||
.IP
|
||||
\fBDefault:\fP
|
||||
|
||||
.DS
|
||||
.nf
|
||||
|
||||
|
||||
Samba defaults to using a reasonable set of valid characters
|
||||
for English systems
|
||||
|
||||
.DE
|
||||
.fi
|
||||
|
||||
|
||||
.IP
|
||||
@ -6728,7 +6728,7 @@ them\&.
|
||||
.IP
|
||||
NOTE: It is actually quite difficult to correctly produce a \fB"valid
|
||||
chars"\fP line for a particular system\&. To automate the process
|
||||
\fItino@augsburg\&.net\fP has written a package called \fB"validchars"\fP
|
||||
tino@augsburg\&.net has written a package called \fB"validchars"\fP
|
||||
which will automatically produce a complete \fB"valid chars"\fP line for
|
||||
a given client system\&. Look in the examples/validchars/ subdirectory
|
||||
of your Samba source code distribution for this package\&.
|
||||
@ -6792,7 +6792,7 @@ sensitive"\fP\&.
|
||||
Example 1\&.
|
||||
.IP
|
||||
|
||||
.DS
|
||||
.nf
|
||||
|
||||
|
||||
|
||||
@ -6802,14 +6802,14 @@ Example 1\&.
|
||||
|
||||
veto files = /*Security*/*\&.tmp/*root*/
|
||||
|
||||
.DE
|
||||
.fi
|
||||
|
||||
|
||||
.IP
|
||||
Example 2\&.
|
||||
.IP
|
||||
|
||||
.DS
|
||||
.nf
|
||||
|
||||
|
||||
Veto the Apple specific files that a NetAtalk server
|
||||
@ -6817,7 +6817,7 @@ Example 2\&.
|
||||
|
||||
veto files = /\&.AppleDouble/\&.bin/\&.AppleDesktop/Network Trash Folder/
|
||||
|
||||
.DE
|
||||
.fi
|
||||
|
||||
|
||||
.IP
|
||||
@ -7037,14 +7037,14 @@ permitting), but only via spooling operations\&.
|
||||
.IP
|
||||
\fBExamples:\fP
|
||||
|
||||
.DS
|
||||
.nf
|
||||
|
||||
|
||||
read only = no
|
||||
writeable = yes
|
||||
write ok = yes
|
||||
|
||||
.DE
|
||||
.fi
|
||||
|
||||
|
||||
.IP
|
||||
@ -7083,7 +7083,7 @@ This man page is correct for version 2\&.0 of the Samba suite\&.
|
||||
.SH "AUTHOR"
|
||||
.PP
|
||||
The original Samba software and related utilities were created by
|
||||
Andrew Tridgell \fIsamba@samba\&.org\fP\&. Samba is now developed
|
||||
Andrew Tridgell samba@samba\&.org\&. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed\&.
|
||||
.PP
|
||||
@ -7092,7 +7092,7 @@ sources were converted to YODL format (another excellent piece of Open
|
||||
Source software, available at
|
||||
\fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP)
|
||||
and updated for the Samba2\&.0 release by Jeremy Allison\&.
|
||||
\fIsamba@samba\&.org\fP\&.
|
||||
samba@samba\&.org\&.
|
||||
.PP
|
||||
See \fBsamba (7)\fP to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
|
||||
@ -760,7 +760,7 @@ This man page is correct for version 2\&.0 of the Samba suite\&.
|
||||
.SH "AUTHOR"
|
||||
.PP
|
||||
The original Samba software and related utilities were created by
|
||||
Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed
|
||||
Andrew Tridgell samba@samba\&.org\&. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed\&.
|
||||
.PP
|
||||
@ -769,7 +769,7 @@ sources were converted to YODL format (another excellent piece of Open
|
||||
Source software, available at
|
||||
\fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP)
|
||||
and updated for the Samba2\&.0 release by Jeremy Allison\&.
|
||||
\fIsamba-bugs@samba\&.org\fP\&.
|
||||
samba@samba\&.org\&.
|
||||
.PP
|
||||
See \fBsamba (7)\fP to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
|
||||
@ -5,7 +5,7 @@ smbd \- server to provide SMB/CIFS services to clients
|
||||
.PP
|
||||
.SH "SYNOPSIS"
|
||||
.PP
|
||||
\fBsmbd\fP [-D] [-a] [-o] [-P] [-h] [-V] [-d debuglevel] [-l log file] [-p port number] [-O socket options] [-s configuration file] [-i scope]
|
||||
\fBsmbd\fP [-D] [-a] [-o] [-P] [-h] [-V] [-d debuglevel] [-l log file] [-p port number] [-O socket options] [-s configuration file]
|
||||
.PP
|
||||
.SH "DESCRIPTION"
|
||||
.PP
|
||||
@ -137,14 +137,6 @@ of all the services that the server is to provide\&. See \fBsmb\&.conf
|
||||
(5)\fP for more information\&.
|
||||
The default configuration file name is determined at compile time\&.
|
||||
.IP
|
||||
.IP "\fB-i scope\fP"
|
||||
This specifies a NetBIOS scope that the server will use
|
||||
to communicate with when generating NetBIOS names\&. For details on the
|
||||
use of NetBIOS scopes, see rfc1001\&.txt and rfc1002\&.txt\&. NetBIOS scopes
|
||||
are \fIvery\fP rarely used, only set this parameter if you are the
|
||||
system administrator in charge of all the NetBIOS systems you
|
||||
communicate with\&.
|
||||
.IP
|
||||
.PP
|
||||
.SH "FILES"
|
||||
.PP
|
||||
@ -329,7 +321,7 @@ Lastly, edit the configuration file to provide suitable services\&. To
|
||||
start with, the following two services should be all you need:
|
||||
.PP
|
||||
|
||||
.DS
|
||||
.nf
|
||||
|
||||
|
||||
|
||||
@ -343,7 +335,7 @@ start with, the following two services should be all you need:
|
||||
public = yes
|
||||
|
||||
|
||||
.DE
|
||||
.fi
|
||||
|
||||
|
||||
.PP
|
||||
@ -423,7 +415,7 @@ http://samba\&.org/cifs/\&.
|
||||
.SH "AUTHOR"
|
||||
.PP
|
||||
The original Samba software and related utilities were created by
|
||||
Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed
|
||||
Andrew Tridgell samba@samba\&.org\&. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed\&.
|
||||
.PP
|
||||
@ -432,7 +424,7 @@ sources were converted to YODL format (another excellent piece of Open
|
||||
Source software, available at
|
||||
\fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP)
|
||||
and updated for the Samba2\&.0 release by Jeremy Allison\&.
|
||||
\fIsamba-bugs@samba\&.org\fP\&.
|
||||
samba@samba\&.org\&.
|
||||
.PP
|
||||
See \fBsamba (7)\fP to find out how to get a full list of contributors
|
||||
and details on how to submit bug reports, comments etc\&.
|
||||
|
||||
@ -166,14 +166,14 @@ Samba \f(CWbin/\fP directory (the same place that the \fBsmbd\fP
|
||||
and \fBnmbd\fP binaries are installed) as follows:
|
||||
.PP
|
||||
|
||||
.DS
|
||||
.nf
|
||||
|
||||
|
||||
|
||||
cat old_smbpasswd_file | convert_smbpasswd > new_smbpasswd_file
|
||||
|
||||
|
||||
.DE
|
||||
.fi
|
||||
|
||||
|
||||
.PP
|
||||
@ -198,7 +198,7 @@ algorithm\&.
|
||||
.SH "AUTHOR"
|
||||
.PP
|
||||
The original Samba software and related utilities were created by
|
||||
Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed
|
||||
Andrew Tridgell samba@samba\&.org\&. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed\&.
|
||||
.PP
|
||||
@ -207,7 +207,7 @@ sources were converted to YODL format (another excellent piece of Open
|
||||
Source software, available at
|
||||
\fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP)
|
||||
and updated for the Samba2\&.0 release by Jeremy
|
||||
Allison, \fIsamba-bugs@samba\&.org\fP\&.
|
||||
Allison, samba@samba\&.org\&.
|
||||
.PP
|
||||
See \fBsamba (7)\fP to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
|
||||
@ -5,7 +5,7 @@ smbpasswd \- change a users SMB password
|
||||
.PP
|
||||
.SH "SYNOPSIS"
|
||||
.PP
|
||||
\fBsmbpasswd\fP [-a] [-d] [-e] [-D debug level] [-n] [-r remote_machine] [-R name resolve order] [-m] [-j DOMAIN] [-U username] [-h] [-s] username
|
||||
\fBsmbpasswd\fP [-a] [-x] [-d] [-e] [-D debug level] [-n] [-r remote_machine] [-R name resolve order] [-m] [-j DOMAIN] [-U username] [-h] [-s] username
|
||||
.PP
|
||||
.SH "DESCRIPTION"
|
||||
.PP
|
||||
@ -62,6 +62,13 @@ else the request to add the user will fail\&.
|
||||
This option is only available when running \fBsmbpasswd\fP as
|
||||
root\&.
|
||||
.IP
|
||||
.IP "\fB-x\fP"
|
||||
This option specifies that the username following should
|
||||
be deleted from the local \fBsmbpasswd\fP file\&.
|
||||
.IP
|
||||
This option is only available when running \fBsmbpasswd\fP as
|
||||
root\&.
|
||||
.IP
|
||||
.IP "\fB-d\fP"
|
||||
This option specifies that the username following should be
|
||||
\fIdisabled\fP in the local \fBsmbpasswd\fP file\&.
|
||||
@ -199,7 +206,7 @@ being used as an NT Primary Domain Controller\&. PDC support is not a
|
||||
supported feature in Samba2\&.0 but will become supported in a later
|
||||
release\&. If you wish to know more about using Samba as an NT PDC then
|
||||
please subscribe to the mailing list
|
||||
\fIsamba-ntdom@samba\&.org\fP\&.
|
||||
samba-ntdom@samba\&.org\&.
|
||||
.IP
|
||||
This option is only available when running \fBsmbpasswd\fP as root\&.
|
||||
.IP
|
||||
@ -285,7 +292,7 @@ This man page is correct for version 2\&.0 of the Samba suite\&.
|
||||
.SH "AUTHOR"
|
||||
.IP
|
||||
The original Samba software and related utilities were created by
|
||||
Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed
|
||||
Andrew Tridgell samba@samba\&.org\&. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed\&.
|
||||
.IP
|
||||
@ -294,7 +301,7 @@ sources were converted to YODL format (another excellent piece of Open
|
||||
Source software, available at
|
||||
\fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP)
|
||||
and updated for the Samba2\&.0 release by Jeremy Allison\&.
|
||||
\fIsamba-bugs@samba\&.org\fP\&.
|
||||
samba@samba\&.org\&.
|
||||
.IP
|
||||
See \fBsamba (7)\fP to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
|
||||
@ -53,7 +53,7 @@ This man page is correct for version 2\&.0 of the Samba suite\&.
|
||||
.SH "AUTHOR"
|
||||
.PP
|
||||
The original Samba software and related utilities were created by
|
||||
Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed
|
||||
Andrew Tridgell samba@samba\&.org\&. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed\&.
|
||||
.PP
|
||||
@ -62,7 +62,7 @@ sources were converted to YODL format (another excellent piece of Open
|
||||
Source software, available at
|
||||
\fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP)
|
||||
and updated for the Samba2\&.0 release by Jeremy Allison\&.
|
||||
\fIsamba-bugs@samba\&.org\fP\&.
|
||||
samba@samba\&.org\&.
|
||||
.PP
|
||||
See \fBsamba (7)\fP to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
|
||||
@ -59,7 +59,7 @@ This man page is correct for version 2\&.0 of the Samba suite\&.
|
||||
.SH "AUTHOR"
|
||||
.PP
|
||||
The original Samba software and related utilities were created by
|
||||
Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed
|
||||
Andrew Tridgell samba@samba\&.org\&. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed\&.
|
||||
.PP
|
||||
@ -68,7 +68,7 @@ sources were converted to YODL format (another excellent piece of Open
|
||||
Source software, available at
|
||||
\fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP)
|
||||
and updated for the Samba2\&.0 release by Jeremy Allison\&.
|
||||
\fIsamba-bugs@samba\&.org\fP\&.
|
||||
samba@samba\&.org\&.
|
||||
.PP
|
||||
See \fBsamba (7)\fP to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
|
||||
@ -105,19 +105,19 @@ the \fBsmbclient\fP command\&.
|
||||
.SH "AUTHOR"
|
||||
.PP
|
||||
The original Samba software and related utilities were created by
|
||||
Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed
|
||||
Andrew Tridgell samba@samba\&.org\&. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed\&.
|
||||
.PP
|
||||
Ricky Poulten \fIpoultenr@logica\&.co\&.uk\fP wrote the tar extension and
|
||||
Ricky Poulten poultenr@logica\&.co\&.uk wrote the tar extension and
|
||||
this man page\&. The \fBsmbtar\fP script was heavily rewritten and
|
||||
improved by Martin Kraemer \fIMartin\&.Kraemer@mch\&.sni\&.de\fP\&. Many
|
||||
improved by Martin Kraemer Martin\&.Kraemer@mch\&.sni\&.de\&. Many
|
||||
thanks to everyone who suggested extensions, improvements, bug fixes,
|
||||
etc\&. The man page sources were converted to YODL format (another
|
||||
excellent piece of Open Source software available at
|
||||
\fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP)
|
||||
and updated for the Samba2\&.0 release by Jeremy Allison,
|
||||
\fIsamba-bugs@samba\&.org\fP\&.
|
||||
samba@samba\&.org\&.
|
||||
.PP
|
||||
See \fBsamba (7)\fP to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
|
||||
@ -49,14 +49,14 @@ swat binary and the various help files and images\&. A default install
|
||||
would put these in:
|
||||
.PP
|
||||
|
||||
.DS
|
||||
.nf
|
||||
|
||||
|
||||
/usr/local/samba/bin/swat
|
||||
/usr/local/samba/swat/images/*
|
||||
/usr/local/samba/swat/help/*
|
||||
|
||||
.DE
|
||||
.fi
|
||||
|
||||
|
||||
.PP
|
||||
@ -137,7 +137,7 @@ This man page is correct for version 2\&.0 of the Samba suite\&.
|
||||
.SH "AUTHOR"
|
||||
.PP
|
||||
The original Samba software and related utilities were created by
|
||||
Andrew Tridgell (samba-bugs@samba\&.org)\&. Samba is now developed
|
||||
Andrew Tridgell (samba@samba\&.org)\&. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed\&.
|
||||
.PP
|
||||
@ -146,7 +146,7 @@ sources were converted to YODL format (another excellent piece of Open
|
||||
Source software, available at
|
||||
\fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP)
|
||||
and updated for the Samba2\&.0 release by Jeremy Allison\&.
|
||||
\fIsamba-bugs@samba\&.org\fP\&.
|
||||
samba@samba\&.org\&.
|
||||
.PP
|
||||
See \fBsamba (7)\fP to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
|
||||
@ -88,7 +88,7 @@ This man page is correct for version 2\&.0 of the Samba suite\&.
|
||||
.SH "AUTHOR"
|
||||
.PP
|
||||
The original Samba software and related utilities were created by
|
||||
Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed
|
||||
Andrew Tridgell samba@samba\&.org\&. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed\&.
|
||||
.PP
|
||||
@ -97,7 +97,7 @@ sources were converted to YODL format (another excellent piece of Open
|
||||
Source software, available at
|
||||
\fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP)
|
||||
and updated for the Samba2\&.0 release by Jeremy Allison\&.
|
||||
\fIsamba-bugs@samba\&.org\fP\&.
|
||||
samba@samba\&.org\&.
|
||||
.PP
|
||||
See \fBsamba (7)\fP to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
|
||||
@ -71,7 +71,7 @@ Other messages are self-explanatory\&.
|
||||
.SH "AUTHOR"
|
||||
.PP
|
||||
The original Samba software and related utilities were created by
|
||||
Andrew Tridgell \fIsamba-bugs@samba\&.org\fP\&. Samba is now developed
|
||||
Andrew Tridgell samba@samba\&.org\&. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed\&.
|
||||
.PP
|
||||
@ -80,7 +80,7 @@ sources were converted to YODL format (another excellent piece of Open
|
||||
Source software, available at
|
||||
\fBftp://ftp\&.icce\&.rug\&.nl/pub/unix/\fP)
|
||||
and updated for the Samba2\&.0 release by Jeremy Allison\&.
|
||||
\fIsamba-bugs@samba\&.org\fP\&.
|
||||
samba@samba\&.org\&.
|
||||
.PP
|
||||
See \fBsamba (7)\fP to find out how to get a full
|
||||
list of contributors and details on how to submit bug reports,
|
||||
|
||||
@ -20,8 +20,10 @@ be configured throught the \f(CW/etc/nsswitch\&.conf\fP file\&. Users and group
|
||||
are allocated as they are resolved to a range of user and group ids
|
||||
specified by the administrator of the Samba system\&.
|
||||
.PP
|
||||
The service provided by \fBwinbindd\fP is called `winbind\' and can be used to
|
||||
resolve user and group information from a Windows NT server\&.
|
||||
The service provided by \fBwinbindd\fP is called `winbind\' and can be
|
||||
used to resolve user and group information from a Windows NT server\&.
|
||||
The service can also provide authentication services via an associated
|
||||
PAM module\&.
|
||||
.PP
|
||||
The following nsswitch databases are implemented by the \fBwinbindd\fP
|
||||
service:
|
||||
@ -43,9 +45,16 @@ For example, the following simple configuration in the
|
||||
information from \f(CW/etc/passwd\fP and \f(CW/etc/group\fP and then from the
|
||||
Windows NT server\&.
|
||||
.PP
|
||||
\f(CWpasswd: files winbind\fP
|
||||
.PP
|
||||
\f(CWgroup: files winbind\fP
|
||||
|
||||
.nf
|
||||
|
||||
|
||||
passwd: files winbind
|
||||
group: files winbind
|
||||
|
||||
.fi
|
||||
|
||||
|
||||
.PP
|
||||
.SH "OPTIONS"
|
||||
.PP
|
||||
@ -91,6 +100,23 @@ should be specified in the [global] section of
|
||||
\fBsmb\&.conf\fP\&.
|
||||
.PP
|
||||
.IP
|
||||
.IP "winbind separator"
|
||||
.IP
|
||||
The winbind separator option allows you to specify how NT domain names
|
||||
and user names are combined into unix user names when presented to
|
||||
users\&. By default winbind will use the traditional \e separator so
|
||||
that the unix user names look like DOMAIN\eusername\&. In some cases
|
||||
this separator character may cause problems as the \e character has
|
||||
special meaning in unix shells\&. In that case you can use the winbind
|
||||
separator option to specify an alternative sepataror character\&. Good
|
||||
alternatives may be / (although that conflicts with the unix directory
|
||||
separator) or a + character\&. The + character appears to be the best
|
||||
choice for 100% compatibility with existing unix utilities, but may be
|
||||
an aesthetically bad choice depending on your taste\&.
|
||||
.IP
|
||||
\fBExample:\fP
|
||||
\f(CW winbind separator = +\fP
|
||||
.IP
|
||||
.IP "winbind uid"
|
||||
.IP
|
||||
The winbind uid parameter specifies the range of user ids that are
|
||||
@ -121,10 +147,17 @@ conflicts can occur otherwise\&.
|
||||
.IP
|
||||
This parameter specifies the number of seconds the
|
||||
\fBwinbindd\fP daemon will cache user and group
|
||||
information before querying a Windows NT server again\&.
|
||||
information before querying a Windows NT server again\&. When a item in
|
||||
the cache is older than this time winbindd will ask the domain
|
||||
controller for the sequence number of the servers account database\&. If
|
||||
the sequence number has not changed then the cached item is marked as
|
||||
valid for a further "winbind cache time" seconds\&. Otherwise the item
|
||||
is fetched from the server\&. This means that as long as the account
|
||||
database is not actively changing winbindd will only have to send one
|
||||
sequence number query packet every "winbind cache time" seconds\&.
|
||||
.IP
|
||||
\fBDefault:\fP
|
||||
\f(CW winbind cache type = 15\fP
|
||||
\f(CW winbind cache time = 15\fP
|
||||
.IP
|
||||
.IP "template homedir"
|
||||
.IP
|
||||
@ -141,14 +174,116 @@ is present it is substituted with the user\'s Windows NT user name\&.
|
||||
.IP
|
||||
When filling out the user information for a Windows NT user, the
|
||||
\fBwinbindd\fP daemon uses this parameter to fill in
|
||||
the home directory for that user\&. If the string \f(CW%D\fP is present it is
|
||||
substituted with the user\'s Windows NT domain name\&. If the string \f(CW%U\fP
|
||||
is present it is substituted with the user\'s Windows NT user name\&.
|
||||
the shell for that user\&.
|
||||
.IP
|
||||
\fBDefault:\fP
|
||||
\f(CW template homedir = /home/%D/%U\fP
|
||||
\f(CW template shell = /bin/false\fP
|
||||
.IP
|
||||
.PP
|
||||
.SH "EXAMPLE SETUP"
|
||||
.PP
|
||||
To setup winbindd for user and group lookups plus authentication from
|
||||
a domain controller use something like the following setup\&. This was
|
||||
tested on a RedHat 6\&.2 Linux box\&.
|
||||
.PP
|
||||
In /etc/nsswitch\&.conf put the following:
|
||||
|
||||
.nf
|
||||
|
||||
|
||||
passwd: files winbind
|
||||
group: files winbind
|
||||
|
||||
.fi
|
||||
|
||||
|
||||
.PP
|
||||
In /etc/pam\&.d/* replace the auth lines with something like this:
|
||||
|
||||
.nf
|
||||
|
||||
|
||||
auth required /lib/security/pam_securetty\&.so
|
||||
auth required /lib/security/pam_nologin\&.so
|
||||
auth sufficient /lib/security/pam_winbind\&.so
|
||||
auth required /lib/security/pam_pwdb\&.so use_first_pass shadow nullok
|
||||
|
||||
.fi
|
||||
|
||||
|
||||
.PP
|
||||
Note in particular the use of the sufficient keyword and the
|
||||
use_first_pass keyword\&.
|
||||
.PP
|
||||
Now replace the account lines with this:
|
||||
|
||||
.nf
|
||||
|
||||
|
||||
account required /lib/security/pam_winbind\&.so
|
||||
|
||||
.fi
|
||||
|
||||
|
||||
.PP
|
||||
The next step is to join the domain\&. To do that use the samedit
|
||||
program like this:
|
||||
|
||||
.nf
|
||||
|
||||
|
||||
samedit -S \'*\' -W DOMAIN -UAdministrator
|
||||
|
||||
.fi
|
||||
|
||||
|
||||
.PP
|
||||
Then within samedit run the command:
|
||||
|
||||
.nf
|
||||
|
||||
|
||||
createuser MACHINE$ -j DOMAIN -L
|
||||
|
||||
.fi
|
||||
|
||||
|
||||
.PP
|
||||
This assumes your domain is called DOMAIN and your Samba workstation
|
||||
is called MACHINE\&.
|
||||
.PP
|
||||
Next copy libnss_winbind\&.so\&.2 to /lib and pam_winbind\&.so to
|
||||
/lib/security\&.
|
||||
.PP
|
||||
Finally, setup a smb\&.conf containing directives like the following:
|
||||
|
||||
.nf
|
||||
|
||||
|
||||
[global]
|
||||
winbind separator = +
|
||||
winbind cache time = 10
|
||||
template shell = /bin/bash
|
||||
template homedir = /home/%D/%U
|
||||
winbind uid = 10000-20000
|
||||
winbind gid = 10000-20000
|
||||
workgroup = DOMAIN
|
||||
security = domain
|
||||
password server = *
|
||||
|
||||
.fi
|
||||
|
||||
|
||||
.PP
|
||||
Now start winbindd and you should find that your user and group
|
||||
database is expanded to include your NT users and groups, and that you
|
||||
can login to your unix box as a domain user, using the DOMAIN+user
|
||||
syntax for the username\&. You may wish to use the commands "getent
|
||||
passwd" and "getent group" to confirm the correct operation of
|
||||
winbindd\&.
|
||||
.PP
|
||||
NOTE: nmbd must be running on the local machine for winbindd to work\&.
|
||||
.PP
|
||||
.SH "FILES"
|
||||
.PP
|
||||
The following files are relevant to the operation of the \fBwinbindd\fP
|
||||
@ -192,8 +327,7 @@ Storage for cached user and group information\&.
|
||||
.SH "AUTHOR"
|
||||
.PP
|
||||
The original Samba software and related utilities were created by
|
||||
Andrew Tridgell samba-bugs@samba\&.org\&. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed\&.
|
||||
Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open
|
||||
Source project\&.
|
||||
.PP
|
||||
Winbindd was written by Tim Potter\&.
|
||||
|
||||
@ -3,7 +3,7 @@ TITLE INFORMATION: Joining an NT Domain with Samba 2.0
|
||||
AUTHOR INFORMATION: Jeremy Allison, Samba Team
|
||||
DATE INFORMATION: 7th October 1999
|
||||
|
||||
Contents
|
||||
Table of Contents
|
||||
|
||||
Joining an NT Domain with Samba 2.0
|
||||
-----------------------------------
|
||||
@ -25,7 +25,7 @@ command
|
||||
smbpasswd -j DOM -r DOMPDC
|
||||
|
||||
as we are joining the domain DOM and the PDC for that domain (the only
|
||||
machine that has write access to the domain SAM database). If this is
|
||||
machine that has write access to the domain SAM database) is DOMPDC. If this is
|
||||
successful you will see the message:
|
||||
|
||||
smbpasswd: Joined domain DOM.
|
||||
@ -35,8 +35,8 @@ man page for more details.
|
||||
|
||||
This command goes through the machine account password change
|
||||
protocol, then writes the new (random) machine account password for
|
||||
this Samba server into the a file in the same directory in which an
|
||||
smbpasswd file would be stored (normally :
|
||||
this Samba server into a file in the same directory in which an
|
||||
smbpasswd file would be stored - normally :
|
||||
|
||||
/usr/local/samba/private
|
||||
|
||||
|
||||
@ -23,8 +23,10 @@ be configured throught the tt(/etc/nsswitch.conf) file. Users and groups
|
||||
are allocated as they are resolved to a range of user and group ids
|
||||
specified by the administrator of the Samba system.
|
||||
|
||||
The service provided by bf(winbindd) is called `winbind' and can be used to
|
||||
resolve user and group information from a Windows NT server.
|
||||
The service provided by bf(winbindd) is called `winbind' and can be
|
||||
used to resolve user and group information from a Windows NT server.
|
||||
The service can also provide authentication services via an associated
|
||||
PAM module.
|
||||
|
||||
The following nsswitch databases are implemented by the bf(winbindd)
|
||||
service:
|
||||
@ -48,9 +50,10 @@ tt(/etc/nsswitch.conf) file can be used to initially resolve user and group
|
||||
information from tt(/etc/passwd) and tt(/etc/group) and then from the
|
||||
Windows NT server.
|
||||
|
||||
tt(passwd: files winbind)
|
||||
|
||||
tt(group: files winbind)
|
||||
verb(
|
||||
passwd: files winbind
|
||||
group: files winbind
|
||||
)
|
||||
|
||||
label(OPTIONS)
|
||||
manpageoptions()
|
||||
@ -104,6 +107,23 @@ url(bf(smb.conf))(smb.conf.5.html).
|
||||
|
||||
startdit()
|
||||
|
||||
dit(winbind separator)
|
||||
|
||||
The winbind separator option allows you to specify how NT domain names
|
||||
and user names are combined into unix user names when presented to
|
||||
users. By default winbind will use the traditional \ separator so
|
||||
that the unix user names look like DOMAIN\username. In some cases
|
||||
this separator character may cause problems as the \ character has
|
||||
special meaning in unix shells. In that case you can use the winbind
|
||||
separator option to specify an alternative sepataror character. Good
|
||||
alternatives may be / (although that conflicts with the unix directory
|
||||
separator) or a + character. The + character appears to be the best
|
||||
choice for 100% compatibility with existing unix utilities, but may be
|
||||
an aesthetically bad choice depending on your taste.
|
||||
|
||||
bf(Example:)
|
||||
tt( winbind separator = +)
|
||||
|
||||
dit(winbind uid)
|
||||
|
||||
The winbind uid parameter specifies the range of user ids that are
|
||||
@ -134,10 +154,17 @@ dit(winbind cache time)
|
||||
|
||||
This parameter specifies the number of seconds the
|
||||
url(bf(winbindd))(winbindd.8.html) daemon will cache user and group
|
||||
information before querying a Windows NT server again.
|
||||
information before querying a Windows NT server again. When a item in
|
||||
the cache is older than this time winbindd will ask the domain
|
||||
controller for the sequence number of the servers account database. If
|
||||
the sequence number has not changed then the cached item is marked as
|
||||
valid for a further "winbind cache time" seconds. Otherwise the item
|
||||
is fetched from the server. This means that as long as the account
|
||||
database is not actively changing winbindd will only have to send one
|
||||
sequence number query packet every "winbind cache time" seconds.
|
||||
|
||||
bf(Default:)
|
||||
tt( winbind cache type = 15)
|
||||
tt( winbind cache time = 15)
|
||||
|
||||
dit(template homedir)
|
||||
|
||||
@ -154,15 +181,83 @@ dit(template shell)
|
||||
|
||||
When filling out the user information for a Windows NT user, the
|
||||
url(bf(winbindd))(winbindd.8.html) daemon uses this parameter to fill in
|
||||
the home directory for that user. If the string tt(%D) is present it is
|
||||
substituted with the user's Windows NT domain name. If the string tt(%U)
|
||||
is present it is substituted with the user's Windows NT user name.
|
||||
the shell for that user.
|
||||
|
||||
bf(Default:)
|
||||
tt( template homedir = /home/%D/%U)
|
||||
tt( template shell = /bin/false)
|
||||
|
||||
enddit()
|
||||
|
||||
|
||||
label(EXAMPLESETUP)
|
||||
manpagesection(EXAMPLE SETUP)
|
||||
|
||||
To setup winbindd for user and group lookups plus authentication from
|
||||
a domain controller use something like the following setup. This was
|
||||
tested on a RedHat 6.2 Linux box.
|
||||
|
||||
In /etc/nsswitch.conf put the following:
|
||||
verb(
|
||||
passwd: files winbind
|
||||
group: files winbind
|
||||
)
|
||||
|
||||
In /etc/pam.d/* replace the auth lines with something like this:
|
||||
verb(
|
||||
auth required /lib/security/pam_securetty.so
|
||||
auth required /lib/security/pam_nologin.so
|
||||
auth sufficient /lib/security/pam_winbind.so
|
||||
auth required /lib/security/pam_pwdb.so use_first_pass shadow nullok
|
||||
)
|
||||
|
||||
Note in particular the use of the sufficient keyword and the
|
||||
use_first_pass keyword.
|
||||
|
||||
Now replace the account lines with this:
|
||||
verb(
|
||||
account required /lib/security/pam_winbind.so
|
||||
)
|
||||
|
||||
The next step is to join the domain. To do that use the samedit
|
||||
program like this:
|
||||
verb(
|
||||
samedit -S '*' -W DOMAIN -UAdministrator
|
||||
)
|
||||
|
||||
Then within samedit run the command:
|
||||
verb(
|
||||
createuser MACHINE$ -j DOMAIN -L
|
||||
)
|
||||
|
||||
This assumes your domain is called DOMAIN and your Samba workstation
|
||||
is called MACHINE.
|
||||
|
||||
Next copy libnss_winbind.so.2 to /lib and pam_winbind.so to
|
||||
/lib/security.
|
||||
|
||||
Finally, setup a smb.conf containing directives like the following:
|
||||
verb(
|
||||
[global]
|
||||
winbind separator = +
|
||||
winbind cache time = 10
|
||||
template shell = /bin/bash
|
||||
template homedir = /home/%D/%U
|
||||
winbind uid = 10000-20000
|
||||
winbind gid = 10000-20000
|
||||
workgroup = DOMAIN
|
||||
security = domain
|
||||
password server = *
|
||||
)
|
||||
|
||||
Now start winbindd and you should find that your user and group
|
||||
database is expanded to include your NT users and groups, and that you
|
||||
can login to your unix box as a domain user, using the DOMAIN+user
|
||||
syntax for the username. You may wish to use the commands "getent
|
||||
passwd" and "getent group" to confirm the correct operation of
|
||||
winbindd.
|
||||
|
||||
NOTE: nmbd must be running on the local machine for winbindd to work.
|
||||
|
||||
label(FILES)
|
||||
manpagefiles()
|
||||
|
||||
@ -211,8 +306,7 @@ label(AUTHOR)
|
||||
manpageauthor()
|
||||
|
||||
The original Samba software and related utilities were created by
|
||||
Andrew Tridgell email(samba-bugs@samba.org). Samba is now developed
|
||||
by the Samba Team as an Open Source project similar to the way the
|
||||
Linux kernel is developed.
|
||||
Andrew Tridgell. Samba is now developed by the Samba Team as an Open
|
||||
Source project.
|
||||
|
||||
Winbindd was written by Tim Potter.
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user