mirror of
https://github.com/samba-team/samba.git
synced 2025-03-08 04:58:40 +03:00
Rebuild docs
(This used to be commit 7cafdf9e9576f7988d72fccbc2fad3fbcd3c67df)
This commit is contained in:
Alexander Bokovoy
parent
721195f77b
commit
94f33628d8
Binary file not shown.
Binary file not shown.
52
docs/faq/FAQ-ClientApp.html
Normal file
52
docs/faq/FAQ-ClientApp.html
Normal file
@ -0,0 +1,52 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 4. Specific client application problems</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-Config.html" title="Chapter 3. Configuration problems"><link rel="next" href="FAQ-errors.html" title="Chapter 5. Common errors"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 4. Specific client application problems</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-Config.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="FAQ-errors.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="FAQ-ClientApp"></a>Chapter 4. Specific client application problems</h2></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-ClientApp.html#id2808466">MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"</a></dt><dt><a href="FAQ-ClientApp.html#id2808495">How to use a Samba share as an administrative share for MS Office, etc.</a></dt><dt><a href="FAQ-ClientApp.html#id2808433">Microsoft Access database opening errors</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2808466"></a>MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"</h2></div></div><p>
|
||||
When installing MS Office on a Samba drive for which you have admin
|
||||
user permissions, ie. admin users = username, you will find the
|
||||
setup program unable to complete the installation.
|
||||
</p><p>
|
||||
To get around this problem, do the installation without admin user
|
||||
permissions The problem is that MS Office Setup checks that a file is
|
||||
rdonly by trying to open it for writing.
|
||||
</p><p>
|
||||
Admin users can always open a file for writing, as they run as root.
|
||||
You just have to install as a non-admin user and then use "chown -R"
|
||||
to fix the owner.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2808495"></a>How to use a Samba share as an administrative share for MS Office, etc.</h2></div></div><p>
|
||||
Microsoft Office products can be installed as an administrative installation
|
||||
from which the application can either be run off the administratively installed
|
||||
product that resides on a shared resource, or from which that product can be
|
||||
installed onto workstation clients.
|
||||
</p><p>
|
||||
The general mechanism for implementing an adminstrative installation involves
|
||||
running <b>X:\setup /A</b>, where X is the drive letter of either CDROM or floppy.
|
||||
</p><p>
|
||||
This installation process will NOT install the product for use per se, but
|
||||
rather results in unpacking of the compressed distribution files into a target
|
||||
shared folder. For this process you need write privilidge to the share and it
|
||||
is desirable to enable file locking and share mode operation during this
|
||||
process.
|
||||
</p><p>
|
||||
Subsequent installation of MS Office from this share will FAIL unless certain
|
||||
precautions are taken. This failure will be caused by share mode operation
|
||||
which will prevent the MS Office installation process from re-opening various
|
||||
dynamic link library files and will cause sporadic file not found problems.
|
||||
</p><div class="itemizedlist"><ul type="disc"><li><p>
|
||||
As soon as the administrative installation (unpacking) has completed
|
||||
set the following parameters on the share containing it:
|
||||
</p><pre class="programlisting">
|
||||
[MSOP95]
|
||||
path = /where_you_put_it
|
||||
comment = Your comment
|
||||
volume = "The_CD_ROM_Label"
|
||||
read only = yes
|
||||
available = yes
|
||||
share modes = no
|
||||
locking = no
|
||||
browseable = yes
|
||||
public = yes
|
||||
</pre></li><li><p>Now you are ready to run the setup program from the Microsoft Windows
|
||||
workstation as follows: <b>\\"Server_Name"\MSOP95\msoffice\setup</b>
|
||||
</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2808433"></a>Microsoft Access database opening errors</h2></div></div><p>
|
||||
Here are some notes on running MS-Access on a Samba drive from <a href="stefank@esi.com.au" target="_top">Stefan Kjellberg</a>
|
||||
</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Opening a database in 'exclusive' mode does NOT work. Samba ignores r/w/share modes on file open.</td></tr><tr><td>Make sure that you open the database as 'shared' and to 'lock modified records'</td></tr><tr><td>Of course locking must be enabled for the particular share (smb.conf)</td></tr></table><p>
|
||||
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="FAQ-Config.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="samba-faq.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="FAQ-errors.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 3. Configuration problems </td><td width="20%" align="center"><a accesskey="h" href="samba-faq.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 5. Common errors</td></tr></table></div></body></html>
|
||||
16
docs/faq/FAQ-Config.html
Normal file
16
docs/faq/FAQ-Config.html
Normal file
@ -0,0 +1,16 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 3. Configuration problems</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-Install.html" title="Chapter 2. Compiling and installing Samba on a Unix host"><link rel="next" href="FAQ-ClientApp.html" title="Chapter 4. Specific client application problems"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 3. Configuration problems</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-Install.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="FAQ-ClientApp.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="FAQ-Config"></a>Chapter 3. Configuration problems</h2></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-Config.html#id2811370">I have set 'force user' and samba still makes 'root' the owner of all the files I touch!</a></dt><dt><a href="FAQ-Config.html#id2811387">I have just installed samba and I'm trying to log in from Windows, but samba refuses all logins!</a></dt><dt><a href="FAQ-Config.html#id2811409">How can I make samba use netbios scope ID's</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2811370"></a>I have set 'force user' and samba still makes 'root' the owner of all the files I touch!</h2></div></div><p>
|
||||
When you have a user in 'admin users', samba will always do file operations for
|
||||
this user as 'root', even if 'force user' has been set.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2811387"></a>I have just installed samba and I'm trying to log in from Windows, but samba refuses all logins!</h2></div></div><p>
|
||||
Newer windows clients(NT4, 2000, XP) send encrypted passwords. Samba can't compare these
|
||||
passwords to the unix password database, so it needs it's own user database. You can
|
||||
add users to this database using "smbpasswd -a user-name".
|
||||
</p><p>
|
||||
See also the "User database" chapter of the samba HOWTO Collection.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2811409"></a>How can I make samba use netbios scope ID's</h2></div></div><p>By default Samba uses a blank scope ID. This means
|
||||
all your windows boxes must also have a blank scope ID.
|
||||
If you really want to use a non-blank scope ID then you will
|
||||
need to use the 'netbios scope' smb.conf option.
|
||||
All your PCs will need to have the same setting for
|
||||
this to work. Scope ID's are not recommended.</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="FAQ-Install.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="samba-faq.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="FAQ-ClientApp.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 2. Compiling and installing Samba on a Unix host </td><td width="20%" align="center"><a accesskey="h" href="samba-faq.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 4. Specific client application problems</td></tr></table></div></body></html>
|
||||
194
docs/faq/FAQ-Install.html
Normal file
194
docs/faq/FAQ-Install.html
Normal file
@ -0,0 +1,194 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 2. Compiling and installing Samba on a Unix host</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-general.html" title="Chapter 1. General Information"><link rel="next" href="FAQ-Config.html" title="Chapter 3. Configuration problems"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 2. Compiling and installing Samba on a Unix host</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-general.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="FAQ-Config.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="FAQ-Install"></a>Chapter 2. Compiling and installing Samba on a Unix host</h2></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-Install.html#id2808542">I can't see the Samba server in any browse lists!</a></dt><dt><a href="FAQ-Install.html#id2811456">Some files that I KNOW are on the server don't show up when I view the files from my client!</a></dt><dt><a href="FAQ-Install.html#id2811470">Some files on the server show up with really wierd filenames when I view the files from my client!</a></dt><dt><a href="FAQ-Install.html#id2860743">My client reports "cannot locate specified computer" or similar</a></dt><dt><a href="FAQ-Install.html#id2860797">My client reports "cannot locate specified share name" or similar</a></dt><dt><a href="FAQ-Install.html#id2806029">Printing doesn't work</a></dt><dt><a href="FAQ-Install.html#id2807904">My client reports "This server is not configured to list shared resources"</a></dt><dt><a href="FAQ-Install.html#id2807925">Log message "you appear to have a trapdoor uid system" </a></dt><dt><a href="FAQ-Install.html#id2807990">Why are my file's timestamps off by an hour, or by a few hours?</a></dt><dt><a href="FAQ-Install.html#id2811127">How do I set the printer driver name correctly?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2808542"></a>I can't see the Samba server in any browse lists!</h2></div></div><p>
|
||||
See Browsing.html in the docs directory of the samba source
|
||||
for more information on browsing.
|
||||
</p><p>
|
||||
If your GUI client does not permit you to select non-browsable
|
||||
servers, you may need to do so on the command line. For example, under
|
||||
Lan Manager you might connect to the above service as disk drive M:
|
||||
thusly:
|
||||
</p><pre class="programlisting">
|
||||
net use M: \\mary\fred
|
||||
</pre><p>
|
||||
The details of how to do this and the specific syntax varies from
|
||||
client to client - check your client's documentation.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2811456"></a>Some files that I KNOW are on the server don't show up when I view the files from my client!</h2></div></div><p>See the next question.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2811470"></a>Some files on the server show up with really wierd filenames when I view the files from my client!</h2></div></div><p>
|
||||
If you check what files are not showing up, you will note that they
|
||||
are files which contain upper case letters or which are otherwise not
|
||||
DOS-compatible (ie, they are not legal DOS filenames for some reason).
|
||||
</p><p>
|
||||
The Samba server can be configured either to ignore such files
|
||||
completely, or to present them to the client in "mangled" form. If you
|
||||
are not seeing the files at all, the Samba server has most likely been
|
||||
configured to ignore them. Consult the man page smb.conf(5) for
|
||||
details of how to change this - the parameter you need to set is
|
||||
"mangled names = yes".
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2860743"></a>My client reports "cannot locate specified computer" or similar</h2></div></div><p>
|
||||
This indicates one of three things: You supplied an incorrect server
|
||||
name, the underlying TCP/IP layer is not working correctly, or the
|
||||
name you specified cannot be resolved.
|
||||
</p><p>
|
||||
After carefully checking that the name you typed is the name you
|
||||
should have typed, try doing things like pinging a host or telnetting
|
||||
to somewhere on your network to see if TCP/IP is functioning OK. If it
|
||||
is, the problem is most likely name resolution.
|
||||
</p><p>
|
||||
If your client has a facility to do so, hardcode a mapping between the
|
||||
hosts IP and the name you want to use. For example, with Lan Manager
|
||||
or Windows for Workgroups you would put a suitable entry in the file
|
||||
LMHOSTS. If this works, the problem is in the communication between
|
||||
your client and the netbios name server. If it does not work, then
|
||||
there is something fundamental wrong with your naming and the solution
|
||||
is beyond the scope of this document.
|
||||
</p><p>
|
||||
If you do not have any server on your subnet supplying netbios name
|
||||
resolution, hardcoded mappings are your only option. If you DO have a
|
||||
netbios name server running (such as the Samba suite's nmbd program),
|
||||
the problem probably lies in the way it is set up. Refer to Section
|
||||
Two of this FAQ for more ideas.
|
||||
</p><p>
|
||||
By the way, remember to REMOVE the hardcoded mapping before further
|
||||
tests :-)
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2860797"></a>My client reports "cannot locate specified share name" or similar</h2></div></div><p>
|
||||
This message indicates that your client CAN locate the specified
|
||||
server, which is a good start, but that it cannot find a service of
|
||||
the name you gave.
|
||||
</p><p>
|
||||
The first step is to check the exact name of the service you are
|
||||
trying to connect to (consult your system administrator). Assuming it
|
||||
exists and you specified it correctly (read your client's docs on how
|
||||
to specify a service name correctly), read on:
|
||||
</p><table class="simplelist" border="0" summary="Simple list"><tr><td>Many clients cannot accept or use service names longer than eight characters.</td></tr><tr><td>Many clients cannot accept or use service names containing spaces.</td></tr><tr><td>Some servers (not Samba though) are case sensitive with service names.</td></tr><tr><td>Some clients force service names into upper case.</td></tr></table></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2806029"></a>Printing doesn't work</h2></div></div><p>
|
||||
Make sure that the specified print command for the service you are
|
||||
connecting to is correct and that it has a fully-qualified path (eg.,
|
||||
use "/usr/bin/lpr" rather than just "lpr").
|
||||
</p><p>
|
||||
Make sure that the spool directory specified for the service is
|
||||
writable by the user connected to the service. In particular the user
|
||||
"nobody" often has problems with printing, even if it worked with an
|
||||
earlier version of Samba. Try creating another guest user other than
|
||||
"nobody".
|
||||
</p><p>
|
||||
Make sure that the user specified in the service is permitted to use
|
||||
the printer.
|
||||
</p><p>
|
||||
Check the debug log produced by smbd. Search for the printer name and
|
||||
see if the log turns up any clues. Note that error messages to do with
|
||||
a service ipc$ are meaningless - they relate to the way the client
|
||||
attempts to retrieve status information when using the LANMAN1
|
||||
protocol.
|
||||
</p><p>
|
||||
If using WfWg then you need to set the default protocol to TCP/IP, not
|
||||
Netbeui. This is a WfWg bug.
|
||||
</p><p>
|
||||
If using the Lanman1 protocol (the default) then try switching to
|
||||
coreplus. Also not that print status error messages don't mean
|
||||
printing won't work. The print status is received by a different
|
||||
mechanism.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2807904"></a>My client reports "This server is not configured to list shared resources"</h2></div></div><p>
|
||||
Your guest account is probably invalid for some reason. Samba uses the
|
||||
guest account for browsing in smbd. Check that your guest account is
|
||||
valid.
|
||||
</p><p>See also 'guest account' in smb.conf man page.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2807925"></a>Log message "you appear to have a trapdoor uid system" </h2></div></div><p>
|
||||
This can have several causes. It might be because you are using a uid
|
||||
or gid of 65535 or -1. This is a VERY bad idea, and is a big security
|
||||
hole. Check carefully in your /etc/passwd file and make sure that no
|
||||
user has uid 65535 or -1. Especially check the "nobody" user, as many
|
||||
broken systems are shipped with nobody setup with a uid of 65535.
|
||||
</p><p>It might also mean that your OS has a trapdoor uid/gid system :-)</p><p>
|
||||
This means that once a process changes effective uid from root to
|
||||
another user it can't go back to root. Unfortunately Samba relies on
|
||||
being able to change effective uid from root to non-root and back
|
||||
again to implement its security policy. If your OS has a trapdoor uid
|
||||
system this won't work, and several things in Samba may break. Less
|
||||
things will break if you use user or server level security instead of
|
||||
the default share level security, but you may still strike
|
||||
problems.
|
||||
</p><p>
|
||||
The problems don't give rise to any security holes, so don't panic,
|
||||
but it does mean some of Samba's capabilities will be unavailable.
|
||||
In particular you will not be able to connect to the Samba server as
|
||||
two different uids at once. This may happen if you try to print as a
|
||||
"guest" while accessing a share as a normal user. It may also affect
|
||||
your ability to list the available shares as this is normally done as
|
||||
the guest user.
|
||||
</p><p>
|
||||
Complain to your OS vendor and ask them to fix their system.
|
||||
</p><p>
|
||||
Note: the reason why 65535 is a VERY bad choice of uid and gid is that
|
||||
it casts to -1 as a uid, and the setreuid() system call ignores (with
|
||||
no error) uid changes to -1. This means any daemon attempting to run
|
||||
as uid 65535 will actually run as root. This is not good!
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2807990"></a>Why are my file's timestamps off by an hour, or by a few hours?</h2></div></div><p>
|
||||
This is from Paul Eggert eggert@twinsun.com.
|
||||
</p><p>
|
||||
Most likely it's a problem with your time zone settings.
|
||||
</p><p>
|
||||
Internally, Samba maintains time in traditional Unix format,
|
||||
namely, the number of seconds since 1970-01-01 00:00:00 Universal Time
|
||||
(or ``GMT''), not counting leap seconds.
|
||||
</p><p>
|
||||
On the server side, Samba uses the Unix TZ variable to convert
|
||||
internal timestamps to and from local time. So on the server side, there are
|
||||
two things to get right.
|
||||
</p><table class="simplelist" border="0" summary="Simple list"><tr><td>The Unix system clock must have the correct Universal time. Use the shell command "sh -c 'TZ=UTC0 date'" to check this.</td></tr><tr><td>The TZ environment variable must be set on the server before Samba is invoked. The details of this depend on the server OS, but typically you must edit a file whose name is /etc/TIMEZONE or /etc/default/init, or run the command `zic -l'.</td></tr></table><p>
|
||||
</p><p>TZ must have the correct value.</p><p>
|
||||
If possible, use geographical time zone settings
|
||||
(e.g. TZ='America/Los_Angeles' or perhaps
|
||||
TZ=':US/Pacific'). These are supported by most
|
||||
popular Unix OSes, are easier to get right, and are
|
||||
more accurate for historical timestamps. If your
|
||||
operating system has out-of-date tables, you should be
|
||||
able to update them from the public domain time zone
|
||||
tables at <a href="ftp://elsie.nci.nih.gov/pub/" target="_top">ftp://elsie.nci.nih.gov/pub/</a>.
|
||||
</p><p>If your system does not support geographical timezone
|
||||
settings, you must use a Posix-style TZ strings, e.g.
|
||||
TZ='PST8PDT,M4.1.0/2,M10.5.0/2' for US Pacific time.
|
||||
Posix TZ strings can take the following form (with optional
|
||||
items in brackets):
|
||||
</p><pre class="programlisting">
|
||||
StdOffset[Dst[Offset],Date/Time,Date/Time]
|
||||
</pre><p>
|
||||
where:
|
||||
</p><table class="simplelist" border="0" summary="Simple list"><tr><td>`Std' is the standard time designation (e.g. `PST').</td></tr><tr><td>`Offset' is the number of hours behind UTC (e.g. `8').
|
||||
Prepend a `-' if you are ahead of UTC, and
|
||||
append `:30' if you are at a half-hour offset.
|
||||
Omit all the remaining items if you do not use
|
||||
daylight-saving time.</td></tr><tr><td>`Dst' is the daylight-saving time designation
|
||||
(e.g. `PDT').</td></tr><tr><td>The optional second `Offset' is the number of
|
||||
hours that daylight-saving time is behind UTC.
|
||||
The default is 1 hour ahead of standard time.
|
||||
</td></tr><tr><td>`Date/Time,Date/Time' specify when daylight-saving
|
||||
time starts and ends. The format for a date is
|
||||
`Mm.n.d', which specifies the dth day (0 is Sunday)
|
||||
of the nth week of the mth month, where week 5 means
|
||||
the last such day in the month. The format for a
|
||||
time is [h]h[:mm[:ss]], using a 24-hour clock.
|
||||
</td></tr></table><p>
|
||||
</p><p>
|
||||
Other Posix string formats are allowed but you don't want
|
||||
to know about them.</p><p>
|
||||
On the client side, you must make sure that your client's clock and
|
||||
time zone is also set appropriately. [[I don't know how to do this.]]
|
||||
Samba traditionally has had many problems dealing with time zones, due
|
||||
to the bizarre ways that Microsoft network protocols handle time
|
||||
zones.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2811127"></a>How do I set the printer driver name correctly?</h2></div></div><p>Question:
|
||||
“ On NT, I opened "Printer Manager" and "Connect to Printer".
|
||||
Enter ["\\ptdi270\ps1"] in the box of printer. I got the
|
||||
following error message
|
||||
”</p><p>
|
||||
</p><pre class="programlisting">
|
||||
You do not have sufficient access to your machine
|
||||
to connect to the selected printer, since a driver
|
||||
needs to be installed locally.
|
||||
</pre><p>
|
||||
</p><p>Answer:</p><p>In the more recent versions of Samba you can now set the "printer
|
||||
driver" in smb.conf. This tells the client what driver to use. For
|
||||
example:</p><pre class="programlisting">
|
||||
printer driver = HP LaserJet 4L
|
||||
</pre><p>With this, NT knows to use the right driver. You have to get this string
|
||||
exactly right.</p><p>To find the exact string to use, you need to get to the dialog box in
|
||||
your client where you select which printer driver to install. The
|
||||
correct strings for all the different printers are shown in a listbox
|
||||
in that dialog box.</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="FAQ-general.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="samba-faq.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="FAQ-Config.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 1. General Information </td><td width="20%" align="center"><a accesskey="h" href="samba-faq.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 3. Configuration problems</td></tr></table></div></body></html>
|
||||
16
docs/faq/FAQ-Printing.html
Normal file
16
docs/faq/FAQ-Printing.html
Normal file
@ -0,0 +1,16 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 7. Printing problems</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-features.html" title="Chapter 6. Features"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 7. Printing problems</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-features.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> </td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="FAQ-Printing"></a>Chapter 7. Printing problems</h2></div><div><div class="author"><h3 class="author">Ronan Waide</h3></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-Printing.html#id2875214">setdriver or cupsaddsmb failes</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2875214"></a>setdriver or cupsaddsmb failes</h2></div></div><p>
|
||||
setdriver expects the following setup:
|
||||
|
||||
</p><table class="simplelist" border="0" summary="Simple list"><tr><td>you are a printer admin, or root. this is the smb.conf printer admin group, not the Printer Operators group in NT. I've not tried the latter, but I don't believe it will work based on the current code.</td></tr><tr><td>printer admins has to be defined in [global]</td></tr><tr><td>upload the driver files to \\server\print$\w32x86 and win40 as appropriate. DON'T put them in the 0 or 2 subdirectories.</td></tr><tr><td>Make sure that the user you're connecting as is able to write to the print$ directories</td></tr><tr><td>Use adddriver (with appropriate parameters) to create the driver. note, this will not just update samba's notion of drivers, it will also move the files from the w32x86 and win40 directories to an appropriate subdirectory (based on driver version, I think, but not important enough for me to find out)</td></tr><tr><td>Use setdriver to associate the driver with a printer</td></tr></table><p>
|
||||
</p><p>
|
||||
The setdriver call will fail if the printer doesn't already exist in
|
||||
samba's view of the world. Either create the printer in cups and
|
||||
restart samba, or create an add printer command (see smb.conf doco)
|
||||
and use RPC calls to create a printer. NB the add printer command MUST
|
||||
return a single line of text indicating which port the printer was
|
||||
added on. If it doesn't, Samba won't reload the printer
|
||||
definitions. Although samba doesn't really support the notion of
|
||||
ports, suitable add printer command and enumport command settings can
|
||||
allow you pretty good remote control of the samba printer setup.
|
||||
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="FAQ-features.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="samba-faq.html">Up</a></td><td width="40%" align="right"> </td></tr><tr><td width="40%" align="left" valign="top">Chapter 6. Features </td><td width="20%" align="center"><a accesskey="h" href="samba-faq.html">Home</a></td><td width="40%" align="right" valign="top"> </td></tr></table></div></body></html>
|
||||
99
docs/faq/FAQ-errors.html
Normal file
99
docs/faq/FAQ-errors.html
Normal file
@ -0,0 +1,99 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 5. Common errors</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-ClientApp.html" title="Chapter 4. Specific client application problems"><link rel="next" href="FAQ-features.html" title="Chapter 6. Features"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 5. Common errors</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-ClientApp.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="FAQ-features.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="FAQ-errors"></a>Chapter 5. Common errors</h2></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-errors.html#id2811288">Not listening for calling name</a></dt><dt><a href="FAQ-errors.html#id2811329">System Error 1240</a></dt><dt><a href="FAQ-errors.html#id2811215">smbclient ignores -N !</a></dt><dt><a href="FAQ-errors.html#id2811270">The data on the CD-Drive I've shared seems to be corrupted!</a></dt><dt><a href="FAQ-errors.html#id2874350">Why can users access home directories of other users?</a></dt><dt><a href="FAQ-errors.html#id2874436">Until a few minutes after samba has started, clients get the error "Domain Controller Unavailable"</a></dt><dt><a href="FAQ-errors.html#id2874451">I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2811288"></a>Not listening for calling name</h2></div></div><p>
|
||||
</p><pre class="programlisting">
|
||||
Session request failed (131,129) with myname=HOBBES destname=CALVIN
|
||||
Not listening for calling name
|
||||
</pre><p>
|
||||
</p><p>
|
||||
If you get this when talking to a Samba box then it means that your
|
||||
global "hosts allow" or "hosts deny" settings are causing the Samba
|
||||
server to refuse the connection.
|
||||
</p><p>
|
||||
Look carefully at your "hosts allow" and "hosts deny" lines in the
|
||||
global section of smb.conf.
|
||||
</p><p>
|
||||
It can also be a problem with reverse DNS lookups not functioning
|
||||
correctly, leading to the remote host identity not being able to
|
||||
be confirmed, but that is less likely.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2811329"></a>System Error 1240</h2></div></div><p>
|
||||
System error 1240 means that the client is refusing to talk
|
||||
to a non-encrypting server. Microsoft changed WinNT in service
|
||||
pack 3 to refuse to connect to servers that do not support
|
||||
SMB password encryption.
|
||||
</p><p>There are two main solutions:
|
||||
</p><table class="simplelist" border="0" summary="Simple list"><tr><td>enable SMB password encryption in Samba. See the encryption part of
|
||||
the samba HOWTO Collection</td></tr><tr><td>disable this new behaviour in NT. See the section about
|
||||
Windows NT in the chapter "Portability" of the samba HOWTO collection
|
||||
</td></tr></table><p>
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2811215"></a>smbclient ignores -N !</h2></div></div><p>
|
||||
“When getting the list of shares available on a host using the command
|
||||
<b>smbclient -N -L</b>
|
||||
the program always prompts for the password if the server is a Samba server.
|
||||
It also ignores the "-N" argument when querying some (but not all) of our
|
||||
NT servers.
|
||||
”
|
||||
</p><p>
|
||||
No, it does not ignore -N, it is just that your server rejected the
|
||||
null password in the connection, so smbclient prompts for a password
|
||||
to try again.
|
||||
</p><p>
|
||||
To get the behaviour that you probably want use <b>smbclient -L host -U%</b>
|
||||
</p><p>
|
||||
This will set both the username and password to null, which is
|
||||
an anonymous login for SMB. Using -N would only set the password
|
||||
to null, and this is not accepted as an anonymous login for most
|
||||
SMB servers.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2811270"></a>The data on the CD-Drive I've shared seems to be corrupted!</h2></div></div><p>
|
||||
Some OSes (notably Linux) default to auto detection of file type on
|
||||
cdroms and do cr/lf translation. This is a very bad idea when use with
|
||||
Samba. It causes all sorts of stuff ups.
|
||||
</p><p>
|
||||
To overcome this problem use conv=binary when mounting the cdrom
|
||||
before exporting it with Samba.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874350"></a>Why can users access home directories of other users?</h2></div></div><p>
|
||||
“
|
||||
We are unable to keep individual users from mapping to any other user's
|
||||
home directory once they have supplied a valid password! They only need
|
||||
to enter their own password. I have not found *any* method that I can
|
||||
use to configure samba to enforce that only a user may map their own
|
||||
home directory.
|
||||
”
|
||||
</p><p>“
|
||||
User xyzzy can map his home directory. Once mapped user xyzzy can also map
|
||||
*anyone* elses home directory!
|
||||
”</p><p>
|
||||
This is not a security flaw, it is by design. Samba allows
|
||||
users to have *exactly* the same access to the UNIX filesystem
|
||||
as they would if they were logged onto the UNIX box, except
|
||||
that it only allows such views onto the file system as are
|
||||
allowed by the defined shares.
|
||||
</p><p>
|
||||
This means that if your UNIX home directories are set up
|
||||
such that one user can happily cd into another users
|
||||
directory and do an ls, the UNIX security solution is to
|
||||
change the UNIX file permissions on the users home directories
|
||||
such that the cd and ls would be denied.
|
||||
</p><p>
|
||||
Samba tries very hard not to second guess the UNIX administrators
|
||||
security policies, and trusts the UNIX admin to set
|
||||
the policies and permissions he or she desires.
|
||||
</p><p>
|
||||
Samba does allow the setup you require when you have set the
|
||||
"only user = yes" option on the share, is that you have not set the
|
||||
valid users list for the share.
|
||||
</p><p>
|
||||
Note that only user works in conjunction with the users= list,
|
||||
so to get the behavior you require, add the line :
|
||||
</p><pre class="programlisting">
|
||||
users = %S
|
||||
</pre><p>
|
||||
this is equivalent to:
|
||||
</p><pre class="programlisting">
|
||||
valid users = %S
|
||||
</pre><p>
|
||||
to the definition of the [homes] share, as recommended in
|
||||
the smb.conf man page.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874436"></a>Until a few minutes after samba has started, clients get the error "Domain Controller Unavailable"</h2></div></div><p>
|
||||
A domain controller has to announce on the network who it is. This usually takes a while.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874451"></a>I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs</h2></div></div><p>Your loopback device isn't working correctly. Make sure it's running.
|
||||
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="FAQ-ClientApp.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="samba-faq.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="FAQ-features.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 4. Specific client application problems </td><td width="20%" align="center"><a accesskey="h" href="samba-faq.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 6. Features</td></tr></table></div></body></html>
|
||||
214
docs/faq/FAQ-features.html
Normal file
214
docs/faq/FAQ-features.html
Normal file
@ -0,0 +1,214 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 6. Features</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="FAQ-errors.html" title="Chapter 5. Common errors"><link rel="next" href="FAQ-Printing.html" title="Chapter 7. Printing problems"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 6. Features</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="FAQ-errors.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="FAQ-Printing.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="FAQ-features"></a>Chapter 6. Features</h2></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-features.html#id2874269">How can I prevent my samba server from being used to distribute the Nimda worm?</a></dt><dt><a href="FAQ-features.html#id2874209">How can I use samba as a fax server?</a></dt><dd><dl><dt><a href="FAQ-features.html#id2874628">Tools for printing faxes</a></dt><dt><a href="FAQ-features.html#id2874681">Making the fax-server</a></dt><dt><a href="FAQ-features.html#id2874774">Installing the client drivers</a></dt><dt><a href="FAQ-features.html#id2874858">Example smb.conf</a></dt></dl></dd><dt><a href="FAQ-features.html#id2874883">Samba doesn't work well together with DHCP!</a></dt><dt><a href="FAQ-features.html#id2874531">How can I assign NetBIOS names to clients with DHCP?</a></dt><dt><a href="FAQ-features.html#id2874581">How do I convert between unix and dos text formats?</a></dt><dt><a href="FAQ-features.html#id2874612">Does samba have wins replication support?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874269"></a>How can I prevent my samba server from being used to distribute the Nimda worm?</h2></div></div><p>Author: HASEGAWA Yosuke (translated by <a href="monyo@samba.gr.jp" target="_top">TAKAHASHI Motonobu</a>)</p><p>
|
||||
Nimba Worm is infected through shared disks on a network, as well as through
|
||||
Microsoft IIS, Internet Explorer and mailer of Outlook series.
|
||||
</p><p>
|
||||
At this time, the worm copies itself by the name *.nws and *.eml on
|
||||
the shared disk, moreover, by the name of Riched20.dll in the folder
|
||||
where *.doc file is included.
|
||||
</p><p>
|
||||
To prevent infection through the shared disk offered by Samba, set
|
||||
up as follows:
|
||||
</p><p>
|
||||
</p><pre class="programlisting">
|
||||
[global]
|
||||
...
|
||||
# This can break Administration installations of Office2k.
|
||||
# in that case, don't veto the riched20.dll
|
||||
veto files = /*.eml/*.nws/riched20.dll/
|
||||
</pre><p>
|
||||
</p><p>
|
||||
By setting the "veto files" parameter, matched files on the Samba
|
||||
server are completely hidden from the clients and making it impossible
|
||||
to access them at all.
|
||||
</p><p>
|
||||
In addition to it, the following setting is also pointed out by the
|
||||
samba-jp:09448 thread: when the
|
||||
"readme.txt.{3050F4D8-98B5-11CF-BB82-00AA00BDCE0B}" file exists on
|
||||
a Samba server, it is visible only as "readme.txt" and dangerous
|
||||
code may be executed if this file is double-clicked.
|
||||
</p><p>
|
||||
Setting the following,
|
||||
</p><pre class="programlisting">
|
||||
veto files = /*.{*}/
|
||||
</pre><p>
|
||||
any files having CLSID in its file extension will be inaccessible from any
|
||||
clients.
|
||||
</p><p>
|
||||
This technical article is created based on the discussion of
|
||||
samba-jp:09448 and samba-jp:10900 threads.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874209"></a>How can I use samba as a fax server?</h2></div></div><p>Contributor: <a href="mailto:zuber@berlin.snafu.de" target="_top">Gerhard Zuber</a></p><p>Requirements:
|
||||
</p><table class="simplelist" border="0" summary="Simple list"><tr><td>UNIX box (Linux preferred) with SAMBA and a faxmodem</td></tr><tr><td>ghostscript package</td></tr><tr><td>mgetty+sendfax package</td></tr><tr><td>pbm package (portable bitmap tools)</td></tr></table><p>
|
||||
</p><p>First, install and configure the required packages. Be sure to read the mgetty+sendfax
|
||||
manual carefully.</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2874628"></a>Tools for printing faxes</h3></div></div><p>Your incomed faxes are in:
|
||||
<tt>/var/spool/fax/incoming</tt>. Print it with:</p><pre class="programlisting">
|
||||
for i in *
|
||||
do
|
||||
g3cat $i | g3tolj | lpr -P hp
|
||||
done
|
||||
</pre><p>
|
||||
</p><p>
|
||||
g3cat is in the tools-section, g3tolj is in the contrib-section
|
||||
for printing to HP lasers.
|
||||
</p><p>
|
||||
If you want to produce files for displaying and printing with Windows, use
|
||||
some tools from the pbm-package like the following command: <b>g3cat $i | g3topbm - | ppmtopcx - >$i.pcx</b>
|
||||
and view it with your favourite Windows tool (maybe paintbrush)
|
||||
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2874681"></a>Making the fax-server</h3></div></div><p>fetch the file <tt>mgetty+sendfax/frontends/winword/faxfilter</tt> and place it in <tt>/usr/local/etc/mgetty+sendfax/</tt>(replace /usr/local/ with whatever place you installed mgetty+sendfax)</p><p>prepare your faxspool file as mentioned in this file
|
||||
edit fax/faxspool.in and reinstall or change the final
|
||||
/usr/local/bin/faxspool too.
|
||||
</p><pre class="programlisting">
|
||||
if [ "$user" = "root" -o "$user" = "fax" -o \
|
||||
"$user" = "lp" -o "$user" = "daemon" -o "$user" = "bin" ]
|
||||
</pre><p>find the first line and change it to the second.</p><p>
|
||||
make sure you have pbmtext (from the pbm-package). This is
|
||||
needed for creating the small header line on each page.
|
||||
</p><p>Prepare your faxheader <tt>/usr/local/etc/mgetty+sendfax/faxheader</tt></p><p>
|
||||
Edit your /etc/printcap file:
|
||||
</p><pre class="programlisting">
|
||||
# FAX
|
||||
lp3|fax:\
|
||||
:lp=/dev/null:\
|
||||
:sd=/usr/spool/lp3:\
|
||||
:if=/usr/local/etc/mgetty+sendfax/faxfilter:sh:sf:mx#0:\
|
||||
:lf=/usr/spool/lp3/fax-log:
|
||||
</pre><p>Now, edit your <tt>smb.conf</tt> so you have a smb based printer named "fax"</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2874774"></a>Installing the client drivers</h3></div></div><p>
|
||||
Now you have a printer called "fax" which can be used via
|
||||
TCP/IP-printing (lpd-system) or via SAMBA (windows printing).
|
||||
</p><p>
|
||||
On every system you are able to produce postscript-files you
|
||||
are ready to fax.
|
||||
</p><p>
|
||||
On Windows 3.1 95 and NT:
|
||||
</p><p>
|
||||
Install a printer wich produces postscript output,
|
||||
e.g. apple laserwriter
|
||||
</p><p>Connect the "fax" to your printer.</p><p>
|
||||
Now write your first fax. Use your favourite wordprocessor,
|
||||
write, winword, notepad or whatever you want, and start
|
||||
with the headerpage.
|
||||
</p><p>
|
||||
Usually each fax has a header page. It carries your name,
|
||||
your address, your phone/fax-number.
|
||||
</p><p>
|
||||
It carries also the recipient, his address and his *** fax
|
||||
number ***. Now here is the trick:
|
||||
</p><p>
|
||||
Use the text:
|
||||
</p><pre class="programlisting">
|
||||
Fax-Nr: 123456789
|
||||
</pre><p>
|
||||
as the recipients fax-number. Make sure this text does not
|
||||
occur in regular text ! Make sure this text is not broken
|
||||
by formatting information, e.g. format it as a single entity.
|
||||
(Windows Write and Win95 Wordpad are functional, maybe newer
|
||||
versions of Winword are breaking formatting information).
|
||||
</p><p>
|
||||
The trick is that postscript output is human readable and
|
||||
the faxfilter program scans the text for this pattern and
|
||||
uses the found number as the fax-destination-number.
|
||||
</p><p>
|
||||
Now print your fax through the fax-printer and it will be
|
||||
queued for later transmission. Use faxrunq for sending the
|
||||
queue out.
|
||||
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2874858"></a>Example smb.conf</h3></div></div><pre class="programlisting">
|
||||
[global]
|
||||
printcap name = /etc/printcap
|
||||
print command = /usr/bin/lpr -r -P %p %s
|
||||
lpq command = /usr/bin/lpq -P %p
|
||||
lprm command = /usr/bin/lprm -P %p %j
|
||||
|
||||
[fax]
|
||||
comment = FAX (mgetty+sendfax)
|
||||
path = /tmp
|
||||
printable = yes
|
||||
public = yes
|
||||
writable = no
|
||||
create mode = 0700
|
||||
browseable = yes
|
||||
guest ok = no
|
||||
</pre></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874883"></a>Samba doesn't work well together with DHCP!</h2></div></div><p>
|
||||
We wish to help those folks who wish to use the ISC DHCP Server and provide
|
||||
sample configuration settings. Most operating systems today come ship with
|
||||
the ISC DHCP Server. ISC DHCP is available from:
|
||||
<a href="ftp://ftp.isc.org/isc/dhcp" target="_top">ftp://ftp.isc.org/isc/dhcp</a>
|
||||
</p><p>
|
||||
Incorrect configuration of MS Windows clients (Windows9X, Windows ME, Windows
|
||||
NT/2000) will lead to problems with browsing and with general network
|
||||
operation. Windows 9X/ME users often report problems where the TCP/IP and related
|
||||
network settings will inadvertantly become reset at machine start-up resulting
|
||||
in loss of configuration settings. This results in increased maintenance
|
||||
overheads as well as serious user frustration.
|
||||
</p><p>
|
||||
In recent times users on one mailing list incorrectly attributed the cause of
|
||||
network operating problems to incorrect configuration of Samba.
|
||||
</p><p>
|
||||
One user insisted that the only way to provent Windows95 from periodically
|
||||
performing a full system reset and hardware detection process on start-up was
|
||||
to install the NetBEUI protocol in addition to TCP/IP. This assertion is not
|
||||
correct.
|
||||
</p><p>
|
||||
In the first place, there is NO need for NetBEUI. All Microsoft Windows clients
|
||||
natively run NetBIOS over TCP/IP, and that is the only protocol that is
|
||||
recognised by Samba. Installation of NetBEUI and/or NetBIOS over IPX will
|
||||
cause problems with browse list operation on most networks. Even Windows NT
|
||||
networks experience these problems when incorrectly configured Windows95
|
||||
systems share the same name space. It is important that only those protocols
|
||||
that are strictly needed for site specific reasons should EVER be installed.
|
||||
</p><p>
|
||||
Secondly, and totally against common opinion, DHCP is NOT an evil design but is
|
||||
an extension of the BOOTP protocol that has been in use in Unix environments
|
||||
for many years without any of the melt-down problems that some sensationalists
|
||||
would have us believe can be experienced with DHCP. In fact, DHCP in covered by
|
||||
rfc1541 and is a very safe method of keeping an MS Windows desktop environment
|
||||
under control and for ensuring stable network operation.
|
||||
</p><p>
|
||||
Please note that MS Windows systems as of MS Windows NT 3.1 and MS Windows 95
|
||||
store all network configuration settings a registry. There are a few reports
|
||||
from MS Windows network administrators that warrant mention here. It would appear
|
||||
that when one sets certain MS TCP/IP protocol settings (either directly or via
|
||||
DHCP) that these do get written to the registry. Even though a subsequent
|
||||
change of setting may occur the old value may persist in the registry. This
|
||||
has been known to create serious networking problems.
|
||||
</p><p>
|
||||
An example of this occurs when a manual TCP/IP environment is configured to
|
||||
include a NetBIOS Scope. In this event, when the administrator then changes the
|
||||
configuration of the MS TCP/IP protocol stack, without first deleting the
|
||||
current settings, by simply checking the box to configure the MS TCP/IP stack
|
||||
via DHCP then the NetBIOS Scope that is still persistent in the registry WILL be
|
||||
applied to the resulting DHCP offered settings UNLESS the DHCP server also sets
|
||||
a NetBIOS Scope. It may therefore be prudent to forcibly apply a NULL NetBIOS
|
||||
Scope from your DHCP server. The can be done in the dhcpd.conf file with the
|
||||
parameter:
|
||||
<b>option netbios-scope "";</b>
|
||||
</p><p>
|
||||
While it is true that the Microsoft DHCP server that comes with Windows NT
|
||||
Server provides only a sub-set of rfc1533 functionality this is hardly an issue
|
||||
in those sites that already have a large investment and commitment to Unix
|
||||
systems and technologies. The current state of the art of the DHCP Server
|
||||
specification in covered in rfc2132.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874531"></a>How can I assign NetBIOS names to clients with DHCP?</h2></div></div><p>
|
||||
SMB network clients need to be configured so that all standard TCP/IP name to
|
||||
address resolution works correctly. Once this has been achieved the SMB
|
||||
environment provides additional tools and services that act as helper agents in
|
||||
the translation of SMB (NetBIOS) names to their appropriate IP Addresses. One
|
||||
such helper agent is the NetBIOS Name Server (NBNS) or as Microsoft called it
|
||||
in their Windows NT Server implementation WINS (Windows Internet Name Server).
|
||||
</p><p>
|
||||
A client needs to be configured so that it has a unique Machine (Computer)
|
||||
Name.
|
||||
</p><p>
|
||||
This can be done, but needs a few NT registry hacks and you need to be able to
|
||||
speak UNICODE, which is of course no problem for a True Wizzard(tm) :)
|
||||
Instructions on how to do this (including a small util for less capable
|
||||
Wizzards) can be found at
|
||||
</p><p><a href="http://www.unixtools.org/~nneul/sw/nt/dhcp-netbios-hostname.html" target="_top">http://www.unixtools.org/~nneul/sw/nt/dhcp-netbios-hostname.html</a></p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874581"></a>How do I convert between unix and dos text formats?</h2></div></div><p>
|
||||
Jim barry has written an <a href="ftp://samba.org/pub/samba/contributed/fixcrlf.zip" target="_top">
|
||||
excellent drag-and-drop cr/lf converter for
|
||||
windows</a>. Just drag your file onto the icon and it converts the file.
|
||||
</p><p>
|
||||
The utilities unix2dos and dos2unix(in the mtools package) should do
|
||||
the job under unix.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2874612"></a>Does samba have wins replication support?</h2></div></div><p>
|
||||
At the time of writing there is currently being worked on a wins replication implementation(wrepld).
|
||||
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="FAQ-errors.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="samba-faq.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="FAQ-Printing.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 5. Common errors </td><td width="20%" align="center"><a accesskey="h" href="samba-faq.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 7. Printing problems</td></tr></table></div></body></html>
|
||||
50
docs/faq/FAQ-general.html
Normal file
50
docs/faq/FAQ-general.html
Normal file
@ -0,0 +1,50 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 1. General Information</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="samba-faq.html" title="Samba FAQ"><link rel="up" href="samba-faq.html" title="Samba FAQ"><link rel="previous" href="samba-faq.html" title="Samba FAQ"><link rel="next" href="FAQ-Install.html" title="Chapter 2. Compiling and installing Samba on a Unix host"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 1. General Information</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="samba-faq.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="FAQ-Install.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="FAQ-general"></a>Chapter 1. General Information</h2></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="FAQ-general.html#id2808041">Where can I get it?</a></dt><dt><a href="FAQ-general.html#id2808063">What do the version numbers mean?</a></dt><dt><a href="FAQ-general.html#id2808152">What platforms are supported?</a></dt><dt><a href="FAQ-general.html#id2808341">How do I subscribe to the Samba Mailing Lists?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2808041"></a>Where can I get it?</h2></div></div><p>
|
||||
The Samba suite is available at the <a href="http://samba.org/" target="_top">samba website</a>.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2808063"></a>What do the version numbers mean?</h2></div></div><p>
|
||||
It is not recommended that you run a version of Samba with the word
|
||||
"alpha" in its name unless you know what you are doing and are willing
|
||||
to do some debugging. Many, many people just get the latest
|
||||
recommended stable release version and are happy. If you are brave, by
|
||||
all means take the plunge and help with the testing and development -
|
||||
but don't install it on your departmental server. Samba is typically
|
||||
very stable and safe, and this is mostly due to the policy of many
|
||||
public releases.
|
||||
</p><p>
|
||||
How the scheme works:
|
||||
</p><table class="simplelist" border="0" summary="Simple list"><tr><td>When major changes are made the version number is increased. For
|
||||
example, the transition from 1.9.15 to 1.9.16. However, this version
|
||||
number will not appear immediately and people should continue to use
|
||||
1.9.15 for production systems (see next point.)</td></tr><tr><td>Just after major changes are made the software is considered
|
||||
unstable, and a series of alpha releases are distributed, for example
|
||||
1.9.16alpha1. These are for testing by those who know what they are
|
||||
doing. The "alpha" in the filename will hopefully scare off those who
|
||||
are just looking for the latest version to install.</td></tr><tr><td>When the release manager, currently Jerry, thinks that the alphas have stabilised to the point
|
||||
where he would recommend new users install it, he renames it to the
|
||||
same version number without the alpha, for example 1.9.16.</td></tr><tr><td>Inevitably bugs are found in the "stable" releases and minor patch
|
||||
levels are released which give us the pXX series, for example 1.9.16p2.</td></tr></table><p>
|
||||
</p><p>
|
||||
So the progression goes:
|
||||
|
||||
</p><pre class="programlisting">
|
||||
1.9.15p7 (production)
|
||||
1.9.15p8 (production)
|
||||
1.9.16alpha1 (test sites only)
|
||||
:
|
||||
1.9.16alpha20 (test sites only)
|
||||
1.9.16 (production)
|
||||
1.9.16p1 (production)
|
||||
</pre><p>
|
||||
</p><p>
|
||||
The above system means that whenever someone looks at the samba ftp
|
||||
site they will be able to grab the highest numbered release without an
|
||||
alpha in the name and be sure of getting the current recommended
|
||||
version.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2808152"></a>What platforms are supported?</h2></div></div><p>
|
||||
Many different platforms have run Samba successfully. The platforms
|
||||
most widely used and thus best tested are Linux and SunOS.</p><p>
|
||||
At time of writing, there is support (or has been support for in earlier
|
||||
versions):
|
||||
</p><table class="simplelist" border="0" summary="Simple list"><tr><td>A/UX 3.0</td></tr><tr><td>AIX</td></tr><tr><td>Altos Series 386/1000</td></tr><tr><td>Amiga</td></tr><tr><td>Apollo Domain/OS sr10.3</td></tr><tr><td>BSDI </td></tr><tr><td>B.O.S. (Bull Operating System)</td></tr><tr><td>Cray, Unicos 8.0</td></tr><tr><td>Convex</td></tr><tr><td>DGUX. </td></tr><tr><td>DNIX.</td></tr><tr><td>FreeBSD</td></tr><tr><td>HP-UX</td></tr><tr><td>Intergraph. </td></tr><tr><td>Linux with/without shadow passwords and quota</td></tr><tr><td>LYNX 2.3.0</td></tr><tr><td>MachTen (a unix like system for Macintoshes)</td></tr><tr><td>Motorola 88xxx/9xx range of machines</td></tr><tr><td>NetBSD</td></tr><tr><td>NEXTSTEP Release 2.X, 3.0 and greater (including OPENSTEP for Mach).</td></tr><tr><td>OS/2 using EMX 0.9b</td></tr><tr><td>OSF1</td></tr><tr><td>QNX 4.22</td></tr><tr><td>RiscIX. </td></tr><tr><td>RISCOs 5.0B</td></tr><tr><td>SEQUENT. </td></tr><tr><td>SCO (including: 3.2v2, European dist., OpenServer 5)</td></tr><tr><td>SGI.</td></tr><tr><td>SMP_DC.OSx v1.1-94c079 on Pyramid S series</td></tr><tr><td>SONY NEWS, NEWS-OS (4.2.x and 6.1.x)</td></tr><tr><td>SUNOS 4</td></tr><tr><td>SUNOS 5.2, 5.3, and 5.4 (Solaris 2.2, 2.3, and '2.4 and later')</td></tr><tr><td>Sunsoft ISC SVR3V4</td></tr><tr><td>SVR4</td></tr><tr><td>System V with some berkely extensions (Motorola 88k R32V3.2).</td></tr><tr><td>ULTRIX.</td></tr><tr><td>UNIXWARE</td></tr><tr><td>UXP/DS</td></tr></table></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2808341"></a>How do I subscribe to the Samba Mailing Lists?</h2></div></div><p>
|
||||
Look at <a href="http://samba.org/samba/archives.html" target="_top">the samba mailing list page</a>
|
||||
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="samba-faq.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="samba-faq.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="FAQ-Install.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Samba FAQ </td><td width="20%" align="center"><a accesskey="h" href="samba-faq.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 2. Compiling and installing Samba on a Unix host</td></tr></table></div></body></html>
|
||||
@ -1,281 +0,0 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>Specific client application problems</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
||||
REL="HOME"
|
||||
TITLE="Samba FAQ"
|
||||
HREF="samba-faq.html"><LINK
|
||||
REL="PREVIOUS"
|
||||
TITLE="Configuration problems"
|
||||
HREF="faq-config.html"><LINK
|
||||
REL="NEXT"
|
||||
TITLE="Common errors"
|
||||
HREF="faq-errors.html"></HEAD
|
||||
><BODY
|
||||
CLASS="CHAPTER"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><DIV
|
||||
CLASS="NAVHEADER"
|
||||
><TABLE
|
||||
SUMMARY="Header navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TH
|
||||
COLSPAN="3"
|
||||
ALIGN="center"
|
||||
>Samba FAQ</TH
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="left"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="faq-config.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="80%"
|
||||
ALIGN="center"
|
||||
VALIGN="bottom"
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="right"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="faq-errors.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
></TABLE
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"></DIV
|
||||
><DIV
|
||||
CLASS="CHAPTER"
|
||||
><H1
|
||||
><A
|
||||
NAME="FAQ-CLIENTAPP"
|
||||
></A
|
||||
>Chapter 4. Specific client application problems</H1
|
||||
><DIV
|
||||
CLASS="TOC"
|
||||
><DL
|
||||
><DT
|
||||
><B
|
||||
>Table of Contents</B
|
||||
></DT
|
||||
><DT
|
||||
>4.1. <A
|
||||
HREF="faq-clientapp.html#AEN178"
|
||||
>MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"</A
|
||||
></DT
|
||||
><DT
|
||||
>4.2. <A
|
||||
HREF="faq-clientapp.html#AEN183"
|
||||
>How to use a Samba share as an administrative share for MS Office, etc.</A
|
||||
></DT
|
||||
><DT
|
||||
>4.3. <A
|
||||
HREF="faq-clientapp.html#AEN198"
|
||||
>Microsoft Access database opening errors</A
|
||||
></DT
|
||||
></DL
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN178"
|
||||
>4.1. MS Office Setup reports "Cannot change properties of '\\MSOFFICE\\SETUP.INI'"</A
|
||||
></H1
|
||||
><P
|
||||
>When installing MS Office on a Samba drive for which you have admin
|
||||
user permissions, ie. admin users = username, you will find the
|
||||
setup program unable to complete the installation.</P
|
||||
><P
|
||||
>To get around this problem, do the installation without admin user
|
||||
permissions The problem is that MS Office Setup checks that a file is
|
||||
rdonly by trying to open it for writing.</P
|
||||
><P
|
||||
>Admin users can always open a file for writing, as they run as root.
|
||||
You just have to install as a non-admin user and then use "chown -R"
|
||||
to fix the owner.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN183"
|
||||
>4.2. How to use a Samba share as an administrative share for MS Office, etc.</A
|
||||
></H1
|
||||
><P
|
||||
>Microsoft Office products can be installed as an administrative installation
|
||||
from which the application can either be run off the administratively installed
|
||||
product that resides on a shared resource, or from which that product can be
|
||||
installed onto workstation clients.</P
|
||||
><P
|
||||
>The general mechanism for implementing an adminstrative installation involves
|
||||
running <B
|
||||
CLASS="COMMAND"
|
||||
>X:\setup /A</B
|
||||
>, where X is the drive letter of either CDROM or floppy.</P
|
||||
><P
|
||||
>This installation process will NOT install the product for use per se, but
|
||||
rather results in unpacking of the compressed distribution files into a target
|
||||
shared folder. For this process you need write privilidge to the share and it
|
||||
is desirable to enable file locking and share mode operation during this
|
||||
process.</P
|
||||
><P
|
||||
>Subsequent installation of MS Office from this share will FAIL unless certain
|
||||
precautions are taken. This failure will be caused by share mode operation
|
||||
which will prevent the MS Office installation process from re-opening various
|
||||
dynamic link library files and will cause sporadic file not found problems.</P
|
||||
><P
|
||||
></P
|
||||
><UL
|
||||
><LI
|
||||
><P
|
||||
>As soon as the administrative installation (unpacking) has completed
|
||||
set the following parameters on the share containing it:</P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
>[MSOP95]
|
||||
path = /where_you_put_it
|
||||
comment = Your comment
|
||||
volume = "The_CD_ROM_Label"
|
||||
read only = yes
|
||||
available = yes
|
||||
share modes = no
|
||||
locking = no
|
||||
browseable = yes
|
||||
public = yes</PRE
|
||||
></P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>Now you are ready to run the setup program from the Microsoft Windows
|
||||
workstation as follows: <B
|
||||
CLASS="COMMAND"
|
||||
>\\"Server_Name"\MSOP95\msoffice\setup</B
|
||||
></P
|
||||
></LI
|
||||
></UL
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN198"
|
||||
>4.3. Microsoft Access database opening errors</A
|
||||
></H1
|
||||
><P
|
||||
>Here are some notes on running MS-Access on a Samba drive from <A
|
||||
HREF="stefank@esi.com.au"
|
||||
TARGET="_top"
|
||||
>Stefan Kjellberg</A
|
||||
></P
|
||||
><P
|
||||
><P
|
||||
></P
|
||||
><TABLE
|
||||
BORDER="0"
|
||||
><TBODY
|
||||
><TR
|
||||
><TD
|
||||
>Opening a database in 'exclusive' mode does NOT work. Samba ignores r/w/share modes on file open.</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>Make sure that you open the database as 'shared' and to 'lock modified records'</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>Of course locking must be enabled for the particular share (smb.conf)</TD
|
||||
></TR
|
||||
></TBODY
|
||||
></TABLE
|
||||
><P
|
||||
></P
|
||||
></P
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="NAVFOOTER"
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"><TABLE
|
||||
SUMMARY="Footer navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="faq-config.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="samba-faq.html"
|
||||
ACCESSKEY="H"
|
||||
>Home</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="faq-errors.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
>Configuration problems</TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
> </TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
>Common errors</TD
|
||||
></TR
|
||||
></TABLE
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
@ -1,182 +0,0 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>Configuration problems</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
||||
REL="HOME"
|
||||
TITLE="Samba FAQ"
|
||||
HREF="samba-faq.html"><LINK
|
||||
REL="PREVIOUS"
|
||||
TITLE="Compiling and installing Samba on a Unix host"
|
||||
HREF="faq-install.html"><LINK
|
||||
REL="NEXT"
|
||||
TITLE="Specific client application problems"
|
||||
HREF="faq-clientapp.html"></HEAD
|
||||
><BODY
|
||||
CLASS="CHAPTER"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><DIV
|
||||
CLASS="NAVHEADER"
|
||||
><TABLE
|
||||
SUMMARY="Header navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TH
|
||||
COLSPAN="3"
|
||||
ALIGN="center"
|
||||
>Samba FAQ</TH
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="left"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="faq-install.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="80%"
|
||||
ALIGN="center"
|
||||
VALIGN="bottom"
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="right"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="faq-clientapp.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
></TABLE
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"></DIV
|
||||
><DIV
|
||||
CLASS="CHAPTER"
|
||||
><H1
|
||||
><A
|
||||
NAME="FAQ-CONFIG"
|
||||
></A
|
||||
>Chapter 3. Configuration problems</H1
|
||||
><DIV
|
||||
CLASS="TOC"
|
||||
><DL
|
||||
><DT
|
||||
><B
|
||||
>Table of Contents</B
|
||||
></DT
|
||||
><DT
|
||||
>3.1. <A
|
||||
HREF="faq-config.html#AEN169"
|
||||
>I have set 'force user' and samba still makes 'root' the owner of all the files I touch!</A
|
||||
></DT
|
||||
><DT
|
||||
>3.2. <A
|
||||
HREF="faq-config.html#AEN172"
|
||||
>I have just installed samba and I'm trying to log in from Windows, but samba refuses all logins!</A
|
||||
></DT
|
||||
></DL
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN169"
|
||||
>3.1. I have set 'force user' and samba still makes 'root' the owner of all the files I touch!</A
|
||||
></H1
|
||||
><P
|
||||
>When you have a user in 'admin users', samba will always do file operations for
|
||||
this user as 'root', even if 'force user' has been set.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN172"
|
||||
>3.2. I have just installed samba and I'm trying to log in from Windows, but samba refuses all logins!</A
|
||||
></H1
|
||||
><P
|
||||
>Newer windows clients(NT4, 2000, XP) send encrypted passwords. Samba can't compare these
|
||||
passwords to the unix password database, so it needs it's own user database. You can
|
||||
add users to this database using "smbpasswd -a user-name".</P
|
||||
><P
|
||||
>See also the "User database" chapter of the samba HOWTO Collection.</P
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="NAVFOOTER"
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"><TABLE
|
||||
SUMMARY="Footer navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="faq-install.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="samba-faq.html"
|
||||
ACCESSKEY="H"
|
||||
>Home</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="faq-clientapp.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
>Compiling and installing Samba on a Unix host</TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
> </TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
>Specific client application problems</TD
|
||||
></TR
|
||||
></TABLE
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
@ -1,373 +0,0 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>Common errors</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
||||
REL="HOME"
|
||||
TITLE="Samba FAQ"
|
||||
HREF="samba-faq.html"><LINK
|
||||
REL="PREVIOUS"
|
||||
TITLE="Specific client application problems"
|
||||
HREF="faq-clientapp.html"><LINK
|
||||
REL="NEXT"
|
||||
TITLE="Features"
|
||||
HREF="faq-features.html"></HEAD
|
||||
><BODY
|
||||
CLASS="CHAPTER"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><DIV
|
||||
CLASS="NAVHEADER"
|
||||
><TABLE
|
||||
SUMMARY="Header navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TH
|
||||
COLSPAN="3"
|
||||
ALIGN="center"
|
||||
>Samba FAQ</TH
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="left"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="faq-clientapp.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="80%"
|
||||
ALIGN="center"
|
||||
VALIGN="bottom"
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="right"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="faq-features.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
></TABLE
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"></DIV
|
||||
><DIV
|
||||
CLASS="CHAPTER"
|
||||
><H1
|
||||
><A
|
||||
NAME="FAQ-ERRORS"
|
||||
></A
|
||||
>Chapter 5. Common errors</H1
|
||||
><DIV
|
||||
CLASS="TOC"
|
||||
><DL
|
||||
><DT
|
||||
><B
|
||||
>Table of Contents</B
|
||||
></DT
|
||||
><DT
|
||||
>5.1. <A
|
||||
HREF="faq-errors.html#AEN209"
|
||||
>Not listening for calling name</A
|
||||
></DT
|
||||
><DT
|
||||
>5.2. <A
|
||||
HREF="faq-errors.html#AEN216"
|
||||
>System Error 1240</A
|
||||
></DT
|
||||
><DT
|
||||
>5.3. <A
|
||||
HREF="faq-errors.html#AEN223"
|
||||
>smbclient ignores -N !</A
|
||||
></DT
|
||||
><DT
|
||||
>5.4. <A
|
||||
HREF="faq-errors.html#AEN232"
|
||||
>The data on the CD-Drive I've shared seems to be corrupted!</A
|
||||
></DT
|
||||
><DT
|
||||
>5.5. <A
|
||||
HREF="faq-errors.html#AEN236"
|
||||
>Why can users access home directories of other users?</A
|
||||
></DT
|
||||
><DT
|
||||
>5.6. <A
|
||||
HREF="faq-errors.html#AEN249"
|
||||
>Until a few minutes after samba has started, clients get the error "Domain Controller Unavailable"</A
|
||||
></DT
|
||||
><DT
|
||||
>5.7. <A
|
||||
HREF="faq-errors.html#AEN252"
|
||||
>I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs</A
|
||||
></DT
|
||||
></DL
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN209"
|
||||
>5.1. Not listening for calling name</A
|
||||
></H1
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
>Session request failed (131,129) with myname=HOBBES destname=CALVIN
|
||||
Not listening for calling name</PRE
|
||||
></P
|
||||
><P
|
||||
>If you get this when talking to a Samba box then it means that your
|
||||
global "hosts allow" or "hosts deny" settings are causing the Samba
|
||||
server to refuse the connection. </P
|
||||
><P
|
||||
>Look carefully at your "hosts allow" and "hosts deny" lines in the
|
||||
global section of smb.conf. </P
|
||||
><P
|
||||
>It can also be a problem with reverse DNS lookups not functioning
|
||||
correctly, leading to the remote host identity not being able to
|
||||
be confirmed, but that is less likely.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN216"
|
||||
>5.2. System Error 1240</A
|
||||
></H1
|
||||
><P
|
||||
>System error 1240 means that the client is refusing to talk
|
||||
to a non-encrypting server. Microsoft changed WinNT in service
|
||||
pack 3 to refuse to connect to servers that do not support
|
||||
SMB password encryption.</P
|
||||
><P
|
||||
>There are two main solutions:
|
||||
<P
|
||||
></P
|
||||
><TABLE
|
||||
BORDER="0"
|
||||
><TBODY
|
||||
><TR
|
||||
><TD
|
||||
>enable SMB password encryption in Samba. See the encryption part of
|
||||
the samba HOWTO Collection</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>disable this new behaviour in NT. See the section about
|
||||
Windows NT in the chapter "Portability" of the samba HOWTO collection</TD
|
||||
></TR
|
||||
></TBODY
|
||||
></TABLE
|
||||
><P
|
||||
></P
|
||||
></P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN223"
|
||||
>5.3. smbclient ignores -N !</A
|
||||
></H1
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="QUOTE"
|
||||
>"When getting the list of shares available on a host using the command
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>smbclient -N -L</B
|
||||
>
|
||||
the program always prompts for the password if the server is a Samba server.
|
||||
It also ignores the "-N" argument when querying some (but not all) of our
|
||||
NT servers."</SPAN
|
||||
></P
|
||||
><P
|
||||
>No, it does not ignore -N, it is just that your server rejected the
|
||||
null password in the connection, so smbclient prompts for a password
|
||||
to try again.</P
|
||||
><P
|
||||
>To get the behaviour that you probably want use <B
|
||||
CLASS="COMMAND"
|
||||
>smbclient -L host -U%</B
|
||||
></P
|
||||
><P
|
||||
>This will set both the username and password to null, which is
|
||||
an anonymous login for SMB. Using -N would only set the password
|
||||
to null, and this is not accepted as an anonymous login for most
|
||||
SMB servers.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN232"
|
||||
>5.4. The data on the CD-Drive I've shared seems to be corrupted!</A
|
||||
></H1
|
||||
><P
|
||||
>Some OSes (notably Linux) default to auto detection of file type on
|
||||
cdroms and do cr/lf translation. This is a very bad idea when use with
|
||||
Samba. It causes all sorts of stuff ups.</P
|
||||
><P
|
||||
>To overcome this problem use conv=binary when mounting the cdrom
|
||||
before exporting it with Samba.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN236"
|
||||
>5.5. Why can users access home directories of other users?</A
|
||||
></H1
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="QUOTE"
|
||||
>"We are unable to keep individual users from mapping to any other user's
|
||||
home directory once they have supplied a valid password! They only need
|
||||
to enter their own password. I have not found *any* method that I can
|
||||
use to configure samba to enforce that only a user may map their own
|
||||
home directory."</SPAN
|
||||
></P
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="QUOTE"
|
||||
>"User xyzzy can map his home directory. Once mapped user xyzzy can also map
|
||||
*anyone* elses home directory!"</SPAN
|
||||
></P
|
||||
><P
|
||||
>This is not a security flaw, it is by design. Samba allows
|
||||
users to have *exactly* the same access to the UNIX filesystem
|
||||
as they would if they were logged onto the UNIX box, except
|
||||
that it only allows such views onto the file system as are
|
||||
allowed by the defined shares.</P
|
||||
><P
|
||||
>This means that if your UNIX home directories are set up
|
||||
such that one user can happily cd into another users
|
||||
directory and do an ls, the UNIX security solution is to
|
||||
change the UNIX file permissions on the users home directories
|
||||
such that the cd and ls would be denied.</P
|
||||
><P
|
||||
>Samba tries very hard not to second guess the UNIX administrators
|
||||
security policies, and trusts the UNIX admin to set
|
||||
the policies and permissions he or she desires.</P
|
||||
><P
|
||||
>Samba does allow the setup you require when you have set the
|
||||
"only user = yes" option on the share, is that you have not set the
|
||||
valid users list for the share.</P
|
||||
><P
|
||||
>Note that only user works in conjunction with the users= list,
|
||||
so to get the behavior you require, add the line :
|
||||
<PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
>users = %S</PRE
|
||||
>
|
||||
this is equivalent to:
|
||||
<PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
>valid users = %S</PRE
|
||||
>
|
||||
to the definition of the [homes] share, as recommended in
|
||||
the smb.conf man page.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN249"
|
||||
>5.6. Until a few minutes after samba has started, clients get the error "Domain Controller Unavailable"</A
|
||||
></H1
|
||||
><P
|
||||
>A domain controller has to announce on the network who it is. This usually takes a while.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN252"
|
||||
>5.7. I'm getting "open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Cannot assign requested" in the logs</A
|
||||
></H1
|
||||
><P
|
||||
>Your loopback device isn't working correctly. Make sure it's running.</P
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="NAVFOOTER"
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"><TABLE
|
||||
SUMMARY="Footer navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="faq-clientapp.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="samba-faq.html"
|
||||
ACCESSKEY="H"
|
||||
>Home</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="faq-features.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
>Specific client application problems</TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
> </TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
>Features</TD
|
||||
></TR
|
||||
></TABLE
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
@ -1,601 +0,0 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>Features</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
||||
REL="HOME"
|
||||
TITLE="Samba FAQ"
|
||||
HREF="samba-faq.html"><LINK
|
||||
REL="PREVIOUS"
|
||||
TITLE="Common errors"
|
||||
HREF="faq-errors.html"><LINK
|
||||
REL="NEXT"
|
||||
TITLE="Printing problems"
|
||||
HREF="faq-printing.html"></HEAD
|
||||
><BODY
|
||||
CLASS="CHAPTER"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><DIV
|
||||
CLASS="NAVHEADER"
|
||||
><TABLE
|
||||
SUMMARY="Header navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TH
|
||||
COLSPAN="3"
|
||||
ALIGN="center"
|
||||
>Samba FAQ</TH
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="left"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="faq-errors.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="80%"
|
||||
ALIGN="center"
|
||||
VALIGN="bottom"
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="right"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="faq-printing.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
></TABLE
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"></DIV
|
||||
><DIV
|
||||
CLASS="CHAPTER"
|
||||
><H1
|
||||
><A
|
||||
NAME="FAQ-FEATURES"
|
||||
></A
|
||||
>Chapter 6. Features</H1
|
||||
><DIV
|
||||
CLASS="TOC"
|
||||
><DL
|
||||
><DT
|
||||
><B
|
||||
>Table of Contents</B
|
||||
></DT
|
||||
><DT
|
||||
>6.1. <A
|
||||
HREF="faq-features.html#AEN257"
|
||||
>How can I prevent my samba server from being used to distribute the Nimda worm?</A
|
||||
></DT
|
||||
><DT
|
||||
>6.2. <A
|
||||
HREF="faq-features.html#AEN271"
|
||||
>How can I use samba as a fax server?</A
|
||||
></DT
|
||||
><DD
|
||||
><DL
|
||||
><DT
|
||||
>6.2.1. <A
|
||||
HREF="faq-features.html#AEN282"
|
||||
>Tools for printing faxes</A
|
||||
></DT
|
||||
><DT
|
||||
>6.2.2. <A
|
||||
HREF="faq-features.html#AEN291"
|
||||
>Making the fax-server</A
|
||||
></DT
|
||||
><DT
|
||||
>6.2.3. <A
|
||||
HREF="faq-features.html#AEN307"
|
||||
>Installing the client drivers</A
|
||||
></DT
|
||||
><DT
|
||||
>6.2.4. <A
|
||||
HREF="faq-features.html#AEN321"
|
||||
>Example smb.conf</A
|
||||
></DT
|
||||
></DL
|
||||
></DD
|
||||
><DT
|
||||
>6.3. <A
|
||||
HREF="faq-features.html#AEN325"
|
||||
>Samba doesn't work well together with DHCP!</A
|
||||
></DT
|
||||
><DT
|
||||
>6.4. <A
|
||||
HREF="faq-features.html#AEN338"
|
||||
>How can I assign NetBIOS names to clients with DHCP?</A
|
||||
></DT
|
||||
><DT
|
||||
>6.5. <A
|
||||
HREF="faq-features.html#AEN345"
|
||||
>How do I convert between unix and dos text formats?</A
|
||||
></DT
|
||||
><DT
|
||||
>6.6. <A
|
||||
HREF="faq-features.html#AEN350"
|
||||
>Does samba have wins replication support?</A
|
||||
></DT
|
||||
></DL
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN257"
|
||||
>6.1. How can I prevent my samba server from being used to distribute the Nimda worm?</A
|
||||
></H1
|
||||
><P
|
||||
>Author: HASEGAWA Yosuke (translated by <A
|
||||
HREF="monyo@samba.gr.jp"
|
||||
TARGET="_top"
|
||||
>TAKAHASHI Motonobu</A
|
||||
>)</P
|
||||
><P
|
||||
>Nimba Worm is infected through shared disks on a network, as well as through
|
||||
Microsoft IIS, Internet Explorer and mailer of Outlook series.</P
|
||||
><P
|
||||
>At this time, the worm copies itself by the name *.nws and *.eml on
|
||||
the shared disk, moreover, by the name of Riched20.dll in the folder
|
||||
where *.doc file is included.</P
|
||||
><P
|
||||
>To prevent infection through the shared disk offered by Samba, set
|
||||
up as follows:</P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
>[global]
|
||||
...
|
||||
# This can break Administration installations of Office2k.
|
||||
# in that case, don't veto the riched20.dll
|
||||
veto files = /*.eml/*.nws/riched20.dll/</PRE
|
||||
></P
|
||||
><P
|
||||
>By setting the "veto files" parameter, matched files on the Samba
|
||||
server are completely hidden from the clients and making it impossible
|
||||
to access them at all.</P
|
||||
><P
|
||||
>In addition to it, the following setting is also pointed out by the
|
||||
samba-jp:09448 thread: when the
|
||||
"readme.txt.{3050F4D8-98B5-11CF-BB82-00AA00BDCE0B}" file exists on
|
||||
a Samba server, it is visible only as "readme.txt" and dangerous
|
||||
code may be executed if this file is double-clicked.</P
|
||||
><P
|
||||
>Setting the following,
|
||||
<PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
> veto files = /*.{*}/</PRE
|
||||
>
|
||||
any files having CLSID in its file extension will be inaccessible from any
|
||||
clients.</P
|
||||
><P
|
||||
>This technical article is created based on the discussion of
|
||||
samba-jp:09448 and samba-jp:10900 threads.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN271"
|
||||
>6.2. How can I use samba as a fax server?</A
|
||||
></H1
|
||||
><P
|
||||
>Contributor: <A
|
||||
HREF="mailto:zuber@berlin.snafu.de"
|
||||
TARGET="_top"
|
||||
>Gerhard Zuber</A
|
||||
></P
|
||||
><P
|
||||
>Requirements:
|
||||
<P
|
||||
></P
|
||||
><TABLE
|
||||
BORDER="0"
|
||||
><TBODY
|
||||
><TR
|
||||
><TD
|
||||
>UNIX box (Linux preferred) with SAMBA and a faxmodem</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>ghostscript package</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>mgetty+sendfax package</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>pbm package (portable bitmap tools)</TD
|
||||
></TR
|
||||
></TBODY
|
||||
></TABLE
|
||||
><P
|
||||
></P
|
||||
></P
|
||||
><P
|
||||
>First, install and configure the required packages. Be sure to read the mgetty+sendfax
|
||||
manual carefully.</P
|
||||
><DIV
|
||||
CLASS="SECT2"
|
||||
><H2
|
||||
CLASS="SECT2"
|
||||
><A
|
||||
NAME="AEN282"
|
||||
>6.2.1. Tools for printing faxes</A
|
||||
></H2
|
||||
><P
|
||||
>Your incomed faxes are in:
|
||||
<TT
|
||||
CLASS="FILENAME"
|
||||
>/var/spool/fax/incoming</TT
|
||||
>. Print it with:</P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
>for i in *
|
||||
do
|
||||
g3cat $i | g3tolj | lpr -P hp
|
||||
done</PRE
|
||||
></P
|
||||
><P
|
||||
>g3cat is in the tools-section, g3tolj is in the contrib-section
|
||||
for printing to HP lasers.</P
|
||||
><P
|
||||
>If you want to produce files for displaying and printing with Windows, use
|
||||
some tools from the pbm-package like the following command: <B
|
||||
CLASS="COMMAND"
|
||||
>g3cat $i | g3topbm - | ppmtopcx - >$i.pcx</B
|
||||
>
|
||||
and view it with your favourite Windows tool (maybe paintbrush)</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT2"
|
||||
><H2
|
||||
CLASS="SECT2"
|
||||
><A
|
||||
NAME="AEN291"
|
||||
>6.2.2. Making the fax-server</A
|
||||
></H2
|
||||
><P
|
||||
>fetch the file <TT
|
||||
CLASS="FILENAME"
|
||||
>mgetty+sendfax/frontends/winword/faxfilter</TT
|
||||
> and place it in <TT
|
||||
CLASS="FILENAME"
|
||||
>/usr/local/etc/mgetty+sendfax/</TT
|
||||
>(replace /usr/local/ with whatever place you installed mgetty+sendfax)</P
|
||||
><P
|
||||
>prepare your faxspool file as mentioned in this file
|
||||
edit fax/faxspool.in and reinstall or change the final
|
||||
/usr/local/bin/faxspool too.</P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
>if [ "$user" = "root" -o "$user" = "fax" -o \
|
||||
"$user" = "lp" -o "$user" = "daemon" -o "$user" = "bin" ]</PRE
|
||||
></P
|
||||
><P
|
||||
>find the first line and change it to the second.</P
|
||||
><P
|
||||
>make sure you have pbmtext (from the pbm-package). This is
|
||||
needed for creating the small header line on each page.</P
|
||||
><P
|
||||
>Prepare your faxheader <TT
|
||||
CLASS="FILENAME"
|
||||
>/usr/local/etc/mgetty+sendfax/faxheader</TT
|
||||
></P
|
||||
><P
|
||||
>Edit your /etc/printcap file:
|
||||
<PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
># FAX
|
||||
lp3|fax:\
|
||||
:lp=/dev/null:\
|
||||
:sd=/usr/spool/lp3:\
|
||||
:if=/usr/local/etc/mgetty+sendfax/faxfilter:sh:sf:mx#0:\
|
||||
:lf=/usr/spool/lp3/fax-log:</PRE
|
||||
></P
|
||||
><P
|
||||
>Now, edit your <TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf</TT
|
||||
> so you have a smb based printer named "fax"</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT2"
|
||||
><H2
|
||||
CLASS="SECT2"
|
||||
><A
|
||||
NAME="AEN307"
|
||||
>6.2.3. Installing the client drivers</A
|
||||
></H2
|
||||
><P
|
||||
>Now you have a printer called "fax" which can be used via
|
||||
TCP/IP-printing (lpd-system) or via SAMBA (windows printing).</P
|
||||
><P
|
||||
>On every system you are able to produce postscript-files you
|
||||
are ready to fax.</P
|
||||
><P
|
||||
>On Windows 3.1 95 and NT:</P
|
||||
><P
|
||||
>Install a printer wich produces postscript output,
|
||||
e.g. apple laserwriter</P
|
||||
><P
|
||||
>Connect the "fax" to your printer.</P
|
||||
><P
|
||||
>Now write your first fax. Use your favourite wordprocessor,
|
||||
write, winword, notepad or whatever you want, and start
|
||||
with the headerpage.</P
|
||||
><P
|
||||
>Usually each fax has a header page. It carries your name,
|
||||
your address, your phone/fax-number.</P
|
||||
><P
|
||||
>It carries also the recipient, his address and his *** fax
|
||||
number ***. Now here is the trick:</P
|
||||
><P
|
||||
>Use the text:
|
||||
<PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
>Fax-Nr: 123456789</PRE
|
||||
>
|
||||
as the recipients fax-number. Make sure this text does not
|
||||
occur in regular text ! Make sure this text is not broken
|
||||
by formatting information, e.g. format it as a single entity.
|
||||
(Windows Write and Win95 Wordpad are functional, maybe newer
|
||||
versions of Winword are breaking formatting information).</P
|
||||
><P
|
||||
>The trick is that postscript output is human readable and
|
||||
the faxfilter program scans the text for this pattern and
|
||||
uses the found number as the fax-destination-number.</P
|
||||
><P
|
||||
>Now print your fax through the fax-printer and it will be
|
||||
queued for later transmission. Use faxrunq for sending the
|
||||
queue out.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT2"
|
||||
><H2
|
||||
CLASS="SECT2"
|
||||
><A
|
||||
NAME="AEN321"
|
||||
>6.2.4. Example smb.conf</A
|
||||
></H2
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
>[global]
|
||||
printcap name = /etc/printcap
|
||||
print command = /usr/bin/lpr -r -P %p %s
|
||||
lpq command = /usr/bin/lpq -P %p
|
||||
lprm command = /usr/bin/lprm -P %p %j
|
||||
|
||||
[fax]
|
||||
comment = FAX (mgetty+sendfax)
|
||||
path = /tmp
|
||||
printable = yes
|
||||
public = yes
|
||||
writable = no
|
||||
create mode = 0700
|
||||
browseable = yes
|
||||
guest ok = no</PRE
|
||||
></P
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN325"
|
||||
>6.3. Samba doesn't work well together with DHCP!</A
|
||||
></H1
|
||||
><P
|
||||
>We wish to help those folks who wish to use the ISC DHCP Server and provide
|
||||
sample configuration settings. Most operating systems today come ship with
|
||||
the ISC DHCP Server. ISC DHCP is available from:
|
||||
<A
|
||||
HREF="ftp://ftp.isc.org/isc/dhcp"
|
||||
TARGET="_top"
|
||||
>ftp://ftp.isc.org/isc/dhcp</A
|
||||
></P
|
||||
><P
|
||||
>Incorrect configuration of MS Windows clients (Windows9X, Windows ME, Windows
|
||||
NT/2000) will lead to problems with browsing and with general network
|
||||
operation. Windows 9X/ME users often report problems where the TCP/IP and related
|
||||
network settings will inadvertantly become reset at machine start-up resulting
|
||||
in loss of configuration settings. This results in increased maintenance
|
||||
overheads as well as serious user frustration.</P
|
||||
><P
|
||||
>In recent times users on one mailing list incorrectly attributed the cause of
|
||||
network operating problems to incorrect configuration of Samba.</P
|
||||
><P
|
||||
>One user insisted that the only way to provent Windows95 from periodically
|
||||
performing a full system reset and hardware detection process on start-up was
|
||||
to install the NetBEUI protocol in addition to TCP/IP. This assertion is not
|
||||
correct.</P
|
||||
><P
|
||||
>In the first place, there is NO need for NetBEUI. All Microsoft Windows clients
|
||||
natively run NetBIOS over TCP/IP, and that is the only protocol that is
|
||||
recognised by Samba. Installation of NetBEUI and/or NetBIOS over IPX will
|
||||
cause problems with browse list operation on most networks. Even Windows NT
|
||||
networks experience these problems when incorrectly configured Windows95
|
||||
systems share the same name space. It is important that only those protocols
|
||||
that are strictly needed for site specific reasons should EVER be installed.</P
|
||||
><P
|
||||
>Secondly, and totally against common opinion, DHCP is NOT an evil design but is
|
||||
an extension of the BOOTP protocol that has been in use in Unix environments
|
||||
for many years without any of the melt-down problems that some sensationalists
|
||||
would have us believe can be experienced with DHCP. In fact, DHCP in covered by
|
||||
rfc1541 and is a very safe method of keeping an MS Windows desktop environment
|
||||
under control and for ensuring stable network operation.</P
|
||||
><P
|
||||
>Please note that MS Windows systems as of MS Windows NT 3.1 and MS Windows 95
|
||||
store all network configuration settings a registry. There are a few reports
|
||||
from MS Windows network administrators that warrant mention here. It would appear
|
||||
that when one sets certain MS TCP/IP protocol settings (either directly or via
|
||||
DHCP) that these do get written to the registry. Even though a subsequent
|
||||
change of setting may occur the old value may persist in the registry. This
|
||||
has been known to create serious networking problems.</P
|
||||
><P
|
||||
>An example of this occurs when a manual TCP/IP environment is configured to
|
||||
include a NetBIOS Scope. In this event, when the administrator then changes the
|
||||
configuration of the MS TCP/IP protocol stack, without first deleting the
|
||||
current settings, by simply checking the box to configure the MS TCP/IP stack
|
||||
via DHCP then the NetBIOS Scope that is still persistent in the registry WILL be
|
||||
applied to the resulting DHCP offered settings UNLESS the DHCP server also sets
|
||||
a NetBIOS Scope. It may therefore be prudent to forcibly apply a NULL NetBIOS
|
||||
Scope from your DHCP server. The can be done in the dhcpd.conf file with the
|
||||
parameter:
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>option netbios-scope "";</B
|
||||
></P
|
||||
><P
|
||||
>While it is true that the Microsoft DHCP server that comes with Windows NT
|
||||
Server provides only a sub-set of rfc1533 functionality this is hardly an issue
|
||||
in those sites that already have a large investment and commitment to Unix
|
||||
systems and technologies. The current state of the art of the DHCP Server
|
||||
specification in covered in rfc2132.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN338"
|
||||
>6.4. How can I assign NetBIOS names to clients with DHCP?</A
|
||||
></H1
|
||||
><P
|
||||
>SMB network clients need to be configured so that all standard TCP/IP name to
|
||||
address resolution works correctly. Once this has been achieved the SMB
|
||||
environment provides additional tools and services that act as helper agents in
|
||||
the translation of SMB (NetBIOS) names to their appropriate IP Addresses. One
|
||||
such helper agent is the NetBIOS Name Server (NBNS) or as Microsoft called it
|
||||
in their Windows NT Server implementation WINS (Windows Internet Name Server).</P
|
||||
><P
|
||||
>A client needs to be configured so that it has a unique Machine (Computer)
|
||||
Name.</P
|
||||
><P
|
||||
>This can be done, but needs a few NT registry hacks and you need to be able to
|
||||
speak UNICODE, which is of course no problem for a True Wizzard(tm) :)
|
||||
Instructions on how to do this (including a small util for less capable
|
||||
Wizzards) can be found at</P
|
||||
><P
|
||||
><A
|
||||
HREF="http://www.unixtools.org/~nneul/sw/nt/dhcp-netbios-hostname.html"
|
||||
TARGET="_top"
|
||||
>http://www.unixtools.org/~nneul/sw/nt/dhcp-netbios-hostname.html</A
|
||||
></P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN345"
|
||||
>6.5. How do I convert between unix and dos text formats?</A
|
||||
></H1
|
||||
><P
|
||||
>Jim barry has written an <A
|
||||
HREF="ftp://samba.org/pub/samba/contributed/fixcrlf.zip"
|
||||
TARGET="_top"
|
||||
>excellent drag-and-drop cr/lf converter for
|
||||
windows</A
|
||||
>. Just drag your file onto the icon and it converts the file.</P
|
||||
><P
|
||||
>The utilities unix2dos and dos2unix(in the mtools package) should do
|
||||
the job under unix.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN350"
|
||||
>6.6. Does samba have wins replication support?</A
|
||||
></H1
|
||||
><P
|
||||
>At the time of writing there is currently being worked on a wins replication implementation(wrepld).</P
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="NAVFOOTER"
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"><TABLE
|
||||
SUMMARY="Footer navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="faq-errors.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="samba-faq.html"
|
||||
ACCESSKEY="H"
|
||||
>Home</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="faq-printing.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
>Common errors</TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
> </TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
>Printing problems</TD
|
||||
></TR
|
||||
></TABLE
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
@ -1,484 +0,0 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>General Information</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
||||
REL="HOME"
|
||||
TITLE="Samba FAQ"
|
||||
HREF="samba-faq.html"><LINK
|
||||
REL="PREVIOUS"
|
||||
TITLE="Samba FAQ"
|
||||
HREF="samba-faq.html"><LINK
|
||||
REL="NEXT"
|
||||
TITLE="Compiling and installing Samba on a Unix host"
|
||||
HREF="faq-install.html"></HEAD
|
||||
><BODY
|
||||
CLASS="CHAPTER"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><DIV
|
||||
CLASS="NAVHEADER"
|
||||
><TABLE
|
||||
SUMMARY="Header navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TH
|
||||
COLSPAN="3"
|
||||
ALIGN="center"
|
||||
>Samba FAQ</TH
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="left"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="samba-faq.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="80%"
|
||||
ALIGN="center"
|
||||
VALIGN="bottom"
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="right"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="faq-install.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
></TABLE
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"></DIV
|
||||
><DIV
|
||||
CLASS="CHAPTER"
|
||||
><H1
|
||||
><A
|
||||
NAME="FAQ-GENERAL"
|
||||
></A
|
||||
>Chapter 1. General Information</H1
|
||||
><DIV
|
||||
CLASS="TOC"
|
||||
><DL
|
||||
><DT
|
||||
><B
|
||||
>Table of Contents</B
|
||||
></DT
|
||||
><DT
|
||||
>1.1. <A
|
||||
HREF="faq-general.html#AEN12"
|
||||
>Where can I get it?</A
|
||||
></DT
|
||||
><DT
|
||||
>1.2. <A
|
||||
HREF="faq-general.html#AEN16"
|
||||
>What do the version numbers mean?</A
|
||||
></DT
|
||||
><DT
|
||||
>1.3. <A
|
||||
HREF="faq-general.html#AEN28"
|
||||
>What platforms are supported?</A
|
||||
></DT
|
||||
><DT
|
||||
>1.4. <A
|
||||
HREF="faq-general.html#AEN71"
|
||||
>How do I subscribe to the Samba Mailing Lists?</A
|
||||
></DT
|
||||
><DT
|
||||
>1.5. <A
|
||||
HREF="faq-general.html#AEN75"
|
||||
>Pizza supply details</A
|
||||
></DT
|
||||
></DL
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN12"
|
||||
>1.1. Where can I get it?</A
|
||||
></H1
|
||||
><P
|
||||
>The Samba suite is available at the <A
|
||||
HREF="http://samba.org/"
|
||||
TARGET="_top"
|
||||
>samba website</A
|
||||
>.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN16"
|
||||
>1.2. What do the version numbers mean?</A
|
||||
></H1
|
||||
><P
|
||||
>It is not recommended that you run a version of Samba with the word
|
||||
"alpha" in its name unless you know what you are doing and are willing
|
||||
to do some debugging. Many, many people just get the latest
|
||||
recommended stable release version and are happy. If you are brave, by
|
||||
all means take the plunge and help with the testing and development -
|
||||
but don't install it on your departmental server. Samba is typically
|
||||
very stable and safe, and this is mostly due to the policy of many
|
||||
public releases.</P
|
||||
><P
|
||||
>How the scheme works:
|
||||
<P
|
||||
></P
|
||||
><TABLE
|
||||
BORDER="0"
|
||||
><TBODY
|
||||
><TR
|
||||
><TD
|
||||
>When major changes are made the version number is increased. For
|
||||
example, the transition from 1.9.15 to 1.9.16. However, this version
|
||||
number will not appear immediately and people should continue to use
|
||||
1.9.15 for production systems (see next point.)</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>Just after major changes are made the software is considered
|
||||
unstable, and a series of alpha releases are distributed, for example
|
||||
1.9.16alpha1. These are for testing by those who know what they are
|
||||
doing. The "alpha" in the filename will hopefully scare off those who
|
||||
are just looking for the latest version to install.</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>When Andrew thinks that the alphas have stabilised to the point
|
||||
where he would recommend new users install it, he renames it to the
|
||||
same version number without the alpha, for example 1.9.16.</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>Inevitably bugs are found in the "stable" releases and minor patch
|
||||
levels are released which give us the pXX series, for example 1.9.16p2.</TD
|
||||
></TR
|
||||
></TBODY
|
||||
></TABLE
|
||||
><P
|
||||
></P
|
||||
></P
|
||||
><P
|
||||
>So the progression goes:
|
||||
|
||||
<PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
>1.9.15p7 (production)
|
||||
1.9.15p8 (production)
|
||||
1.9.16alpha1 (test sites only)
|
||||
:
|
||||
1.9.16alpha20 (test sites only)
|
||||
1.9.16 (production)
|
||||
1.9.16p1 (production)</PRE
|
||||
></P
|
||||
><P
|
||||
>The above system means that whenever someone looks at the samba ftp
|
||||
site they will be able to grab the highest numbered release without an
|
||||
alpha in the name and be sure of getting the current recommended
|
||||
version.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN28"
|
||||
>1.3. What platforms are supported?</A
|
||||
></H1
|
||||
><P
|
||||
>Many different platforms have run Samba successfully. The platforms
|
||||
most widely used and thus best tested are Linux and SunOS.</P
|
||||
><P
|
||||
>At time of writing, there is support (or has been support for in earlier
|
||||
versions):</P
|
||||
><P
|
||||
></P
|
||||
><TABLE
|
||||
BORDER="0"
|
||||
><TBODY
|
||||
><TR
|
||||
><TD
|
||||
>A/UX 3.0</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>AIX</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>Altos Series 386/1000</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>Amiga</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>Apollo Domain/OS sr10.3</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>BSDI </TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>B.O.S. (Bull Operating System)</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>Cray, Unicos 8.0</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>Convex</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>DGUX. </TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>DNIX.</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>FreeBSD</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>HP-UX</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>Intergraph. </TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>Linux with/without shadow passwords and quota</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>LYNX 2.3.0</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>MachTen (a unix like system for Macintoshes)</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>Motorola 88xxx/9xx range of machines</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>NetBSD</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>NEXTSTEP Release 2.X, 3.0 and greater (including OPENSTEP for Mach).</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>OS/2 using EMX 0.9b</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>OSF1</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>QNX 4.22</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>RiscIX. </TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>RISCOs 5.0B</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>SEQUENT. </TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>SCO (including: 3.2v2, European dist., OpenServer 5)</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>SGI.</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>SMP_DC.OSx v1.1-94c079 on Pyramid S series</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>SONY NEWS, NEWS-OS (4.2.x and 6.1.x)</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>SUNOS 4</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>SUNOS 5.2, 5.3, and 5.4 (Solaris 2.2, 2.3, and '2.4 and later')</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>Sunsoft ISC SVR3V4</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>SVR4</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>System V with some berkely extensions (Motorola 88k R32V3.2).</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>ULTRIX.</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>UNIXWARE</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>UXP/DS</TD
|
||||
></TR
|
||||
></TBODY
|
||||
></TABLE
|
||||
><P
|
||||
></P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN71"
|
||||
>1.4. How do I subscribe to the Samba Mailing Lists?</A
|
||||
></H1
|
||||
><P
|
||||
>Look at <A
|
||||
HREF="http://samba.org/samba/archives.html"
|
||||
TARGET="_top"
|
||||
>the samba mailing list page</A
|
||||
></P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN75"
|
||||
>1.5. Pizza supply details</A
|
||||
></H1
|
||||
><P
|
||||
>Those who have registered in the Samba survey as "Pizza Factory" will
|
||||
already know this, but the rest may need some help. Andrew doesn't ask
|
||||
for payment, but he does appreciate it when people give him
|
||||
pizza. This calls for a little organisation when the pizza donor is
|
||||
twenty thousand kilometres away, but it has been done.</P
|
||||
><P
|
||||
>Method 1: Ring up your local branch of an international pizza chain
|
||||
and see if they honour their vouchers internationally. Pizza Hut do,
|
||||
which is how the entire Canberra Linux Users Group got to eat pizza
|
||||
one night, courtesy of someone in the US.</P
|
||||
><P
|
||||
>Method 2: Ring up a local pizza shop in Canberra and quote a credit
|
||||
card number for a certain amount, and tell them that Andrew will be
|
||||
collecting it (don't forget to tell him.) One kind soul from Germany
|
||||
did this.</P
|
||||
><P
|
||||
>Method 3: Purchase a pizza voucher from your local pizza shop that has
|
||||
no international affiliations and send it to Andrew. It is completely
|
||||
useless but he can hang it on the wall next to the one he already has
|
||||
from Germany :-)</P
|
||||
><P
|
||||
>Method 4: Air freight him a pizza with your favourite regional
|
||||
flavours. It will probably get stuck in customs or torn apart by
|
||||
hungry sniffer dogs but it will have been a noble gesture.</P
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="NAVFOOTER"
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"><TABLE
|
||||
SUMMARY="Footer navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="samba-faq.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="samba-faq.html"
|
||||
ACCESSKEY="H"
|
||||
>Home</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="faq-install.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
>Samba FAQ</TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
> </TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
>Compiling and installing Samba on a Unix host</TD
|
||||
></TR
|
||||
></TABLE
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
@ -1,582 +0,0 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>Compiling and installing Samba on a Unix host</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
||||
REL="HOME"
|
||||
TITLE="Samba FAQ"
|
||||
HREF="samba-faq.html"><LINK
|
||||
REL="PREVIOUS"
|
||||
TITLE="General Information"
|
||||
HREF="faq-general.html"><LINK
|
||||
REL="NEXT"
|
||||
TITLE="Configuration problems"
|
||||
HREF="faq-config.html"></HEAD
|
||||
><BODY
|
||||
CLASS="CHAPTER"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><DIV
|
||||
CLASS="NAVHEADER"
|
||||
><TABLE
|
||||
SUMMARY="Header navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TH
|
||||
COLSPAN="3"
|
||||
ALIGN="center"
|
||||
>Samba FAQ</TH
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="left"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="faq-general.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="80%"
|
||||
ALIGN="center"
|
||||
VALIGN="bottom"
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="right"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="faq-config.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
></TABLE
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"></DIV
|
||||
><DIV
|
||||
CLASS="CHAPTER"
|
||||
><H1
|
||||
><A
|
||||
NAME="FAQ-INSTALL"
|
||||
></A
|
||||
>Chapter 2. Compiling and installing Samba on a Unix host</H1
|
||||
><DIV
|
||||
CLASS="TOC"
|
||||
><DL
|
||||
><DT
|
||||
><B
|
||||
>Table of Contents</B
|
||||
></DT
|
||||
><DT
|
||||
>2.1. <A
|
||||
HREF="faq-install.html#AEN84"
|
||||
>I can't see the Samba server in any browse lists!</A
|
||||
></DT
|
||||
><DT
|
||||
>2.2. <A
|
||||
HREF="faq-install.html#AEN89"
|
||||
>Some files that I KNOW are on the server don't show up when I view the files from my client!</A
|
||||
></DT
|
||||
><DT
|
||||
>2.3. <A
|
||||
HREF="faq-install.html#AEN92"
|
||||
>Some files on the server show up with really wierd filenames when I view the files from my client!</A
|
||||
></DT
|
||||
><DT
|
||||
>2.4. <A
|
||||
HREF="faq-install.html#AEN96"
|
||||
>My client reports "cannot locate specified computer" or similar</A
|
||||
></DT
|
||||
><DT
|
||||
>2.5. <A
|
||||
HREF="faq-install.html#AEN103"
|
||||
>My client reports "cannot locate specified share name" or similar</A
|
||||
></DT
|
||||
><DT
|
||||
>2.6. <A
|
||||
HREF="faq-install.html#AEN112"
|
||||
>Printing doesn't work</A
|
||||
></DT
|
||||
><DT
|
||||
>2.7. <A
|
||||
HREF="faq-install.html#AEN120"
|
||||
>My client reports "This server is not configured to list shared resources"</A
|
||||
></DT
|
||||
><DT
|
||||
>2.8. <A
|
||||
HREF="faq-install.html#AEN124"
|
||||
>Log message "you appear to have a trapdoor uid system"</A
|
||||
></DT
|
||||
><DT
|
||||
>2.9. <A
|
||||
HREF="faq-install.html#AEN132"
|
||||
>Why are my file's timestamps off by an hour, or by a few hours?</A
|
||||
></DT
|
||||
><DT
|
||||
>2.10. <A
|
||||
HREF="faq-install.html#AEN155"
|
||||
>How do I set the printer driver name correctly?</A
|
||||
></DT
|
||||
></DL
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN84"
|
||||
>2.1. I can't see the Samba server in any browse lists!</A
|
||||
></H1
|
||||
><P
|
||||
>See Browsing.html in the docs directory of the samba source
|
||||
for more information on browsing.</P
|
||||
><P
|
||||
>If your GUI client does not permit you to select non-browsable
|
||||
servers, you may need to do so on the command line. For example, under
|
||||
Lan Manager you might connect to the above service as disk drive M:
|
||||
thusly:
|
||||
<PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
> net use M: \\mary\fred</PRE
|
||||
>
|
||||
The details of how to do this and the specific syntax varies from
|
||||
client to client - check your client's documentation.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN89"
|
||||
>2.2. Some files that I KNOW are on the server don't show up when I view the files from my client!</A
|
||||
></H1
|
||||
><P
|
||||
>See the next question.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN92"
|
||||
>2.3. Some files on the server show up with really wierd filenames when I view the files from my client!</A
|
||||
></H1
|
||||
><P
|
||||
>If you check what files are not showing up, you will note that they
|
||||
are files which contain upper case letters or which are otherwise not
|
||||
DOS-compatible (ie, they are not legal DOS filenames for some reason).</P
|
||||
><P
|
||||
>The Samba server can be configured either to ignore such files
|
||||
completely, or to present them to the client in "mangled" form. If you
|
||||
are not seeing the files at all, the Samba server has most likely been
|
||||
configured to ignore them. Consult the man page smb.conf(5) for
|
||||
details of how to change this - the parameter you need to set is
|
||||
"mangled names = yes".</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN96"
|
||||
>2.4. My client reports "cannot locate specified computer" or similar</A
|
||||
></H1
|
||||
><P
|
||||
>This indicates one of three things: You supplied an incorrect server
|
||||
name, the underlying TCP/IP layer is not working correctly, or the
|
||||
name you specified cannot be resolved.</P
|
||||
><P
|
||||
>After carefully checking that the name you typed is the name you
|
||||
should have typed, try doing things like pinging a host or telnetting
|
||||
to somewhere on your network to see if TCP/IP is functioning OK. If it
|
||||
is, the problem is most likely name resolution.</P
|
||||
><P
|
||||
>If your client has a facility to do so, hardcode a mapping between the
|
||||
hosts IP and the name you want to use. For example, with Lan Manager
|
||||
or Windows for Workgroups you would put a suitable entry in the file
|
||||
LMHOSTS. If this works, the problem is in the communication between
|
||||
your client and the netbios name server. If it does not work, then
|
||||
there is something fundamental wrong with your naming and the solution
|
||||
is beyond the scope of this document.</P
|
||||
><P
|
||||
>If you do not have any server on your subnet supplying netbios name
|
||||
resolution, hardcoded mappings are your only option. If you DO have a
|
||||
netbios name server running (such as the Samba suite's nmbd program),
|
||||
the problem probably lies in the way it is set up. Refer to Section
|
||||
Two of this FAQ for more ideas.</P
|
||||
><P
|
||||
>By the way, remember to REMOVE the hardcoded mapping before further
|
||||
tests :-)</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN103"
|
||||
>2.5. My client reports "cannot locate specified share name" or similar</A
|
||||
></H1
|
||||
><P
|
||||
>This message indicates that your client CAN locate the specified
|
||||
server, which is a good start, but that it cannot find a service of
|
||||
the name you gave.</P
|
||||
><P
|
||||
>The first step is to check the exact name of the service you are
|
||||
trying to connect to (consult your system administrator). Assuming it
|
||||
exists and you specified it correctly (read your client's docs on how
|
||||
to specify a service name correctly), read on:</P
|
||||
><P
|
||||
></P
|
||||
><TABLE
|
||||
BORDER="0"
|
||||
><TBODY
|
||||
><TR
|
||||
><TD
|
||||
>Many clients cannot accept or use service names longer than eight characters.</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>Many clients cannot accept or use service names containing spaces.</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>Some servers (not Samba though) are case sensitive with service names.</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>Some clients force service names into upper case.</TD
|
||||
></TR
|
||||
></TBODY
|
||||
></TABLE
|
||||
><P
|
||||
></P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN112"
|
||||
>2.6. Printing doesn't work</A
|
||||
></H1
|
||||
><P
|
||||
>Make sure that the specified print command for the service you are
|
||||
connecting to is correct and that it has a fully-qualified path (eg.,
|
||||
use "/usr/bin/lpr" rather than just "lpr").</P
|
||||
><P
|
||||
>Make sure that the spool directory specified for the service is
|
||||
writable by the user connected to the service. In particular the user
|
||||
"nobody" often has problems with printing, even if it worked with an
|
||||
earlier version of Samba. Try creating another guest user other than
|
||||
"nobody".</P
|
||||
><P
|
||||
>Make sure that the user specified in the service is permitted to use
|
||||
the printer.</P
|
||||
><P
|
||||
>Check the debug log produced by smbd. Search for the printer name and
|
||||
see if the log turns up any clues. Note that error messages to do with
|
||||
a service ipc$ are meaningless - they relate to the way the client
|
||||
attempts to retrieve status information when using the LANMAN1
|
||||
protocol.</P
|
||||
><P
|
||||
>If using WfWg then you need to set the default protocol to TCP/IP, not
|
||||
Netbeui. This is a WfWg bug.</P
|
||||
><P
|
||||
>If using the Lanman1 protocol (the default) then try switching to
|
||||
coreplus. Also not that print status error messages don't mean
|
||||
printing won't work. The print status is received by a different
|
||||
mechanism.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN120"
|
||||
>2.7. My client reports "This server is not configured to list shared resources"</A
|
||||
></H1
|
||||
><P
|
||||
>Your guest account is probably invalid for some reason. Samba uses the
|
||||
guest account for browsing in smbd. Check that your guest account is
|
||||
valid.</P
|
||||
><P
|
||||
>See also 'guest account' in smb.conf man page.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN124"
|
||||
>2.8. Log message "you appear to have a trapdoor uid system"</A
|
||||
></H1
|
||||
><P
|
||||
>This can have several causes. It might be because you are using a uid
|
||||
or gid of 65535 or -1. This is a VERY bad idea, and is a big security
|
||||
hole. Check carefully in your /etc/passwd file and make sure that no
|
||||
user has uid 65535 or -1. Especially check the "nobody" user, as many
|
||||
broken systems are shipped with nobody setup with a uid of 65535.</P
|
||||
><P
|
||||
>It might also mean that your OS has a trapdoor uid/gid system :-)</P
|
||||
><P
|
||||
>This means that once a process changes effective uid from root to
|
||||
another user it can't go back to root. Unfortunately Samba relies on
|
||||
being able to change effective uid from root to non-root and back
|
||||
again to implement its security policy. If your OS has a trapdoor uid
|
||||
system this won't work, and several things in Samba may break. Less
|
||||
things will break if you use user or server level security instead of
|
||||
the default share level security, but you may still strike
|
||||
problems.</P
|
||||
><P
|
||||
>The problems don't give rise to any security holes, so don't panic,
|
||||
but it does mean some of Samba's capabilities will be unavailable.
|
||||
In particular you will not be able to connect to the Samba server as
|
||||
two different uids at once. This may happen if you try to print as a
|
||||
"guest" while accessing a share as a normal user. It may also affect
|
||||
your ability to list the available shares as this is normally done as
|
||||
the guest user.</P
|
||||
><P
|
||||
>Complain to your OS vendor and ask them to fix their system.</P
|
||||
><P
|
||||
>Note: the reason why 65535 is a VERY bad choice of uid and gid is that
|
||||
it casts to -1 as a uid, and the setreuid() system call ignores (with
|
||||
no error) uid changes to -1. This means any daemon attempting to run
|
||||
as uid 65535 will actually run as root. This is not good!</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN132"
|
||||
>2.9. Why are my file's timestamps off by an hour, or by a few hours?</A
|
||||
></H1
|
||||
><P
|
||||
>This is from Paul Eggert eggert@twinsun.com.</P
|
||||
><P
|
||||
>Most likely it's a problem with your time zone settings.</P
|
||||
><P
|
||||
>Internally, Samba maintains time in traditional Unix format,
|
||||
namely, the number of seconds since 1970-01-01 00:00:00 Universal Time
|
||||
(or ``GMT''), not counting leap seconds.</P
|
||||
><P
|
||||
>On the server side, Samba uses the Unix TZ variable to convert
|
||||
internal timestamps to and from local time. So on the server side, there are
|
||||
two things to get right.
|
||||
<P
|
||||
></P
|
||||
><TABLE
|
||||
BORDER="0"
|
||||
><TBODY
|
||||
><TR
|
||||
><TD
|
||||
>The Unix system clock must have the correct Universal time. Use the shell command "sh -c 'TZ=UTC0 date'" to check this.</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>The TZ environment variable must be set on the server before Samba is invoked. The details of this depend on the server OS, but typically you must edit a file whose name is /etc/TIMEZONE or /etc/default/init, or run the command `zic -l'.</TD
|
||||
></TR
|
||||
></TBODY
|
||||
></TABLE
|
||||
><P
|
||||
></P
|
||||
></P
|
||||
><P
|
||||
>TZ must have the correct value.</P
|
||||
><P
|
||||
>If possible, use geographical time zone settings
|
||||
(e.g. TZ='America/Los_Angeles' or perhaps
|
||||
TZ=':US/Pacific'). These are supported by most
|
||||
popular Unix OSes, are easier to get right, and are
|
||||
more accurate for historical timestamps. If your
|
||||
operating system has out-of-date tables, you should be
|
||||
able to update them from the public domain time zone
|
||||
tables at <A
|
||||
HREF="ftp://elsie.nci.nih.gov/pub/"
|
||||
TARGET="_top"
|
||||
>ftp://elsie.nci.nih.gov/pub/</A
|
||||
>.</P
|
||||
><P
|
||||
>If your system does not support geographical timezone
|
||||
settings, you must use a Posix-style TZ strings, e.g.
|
||||
TZ='PST8PDT,M4.1.0/2,M10.5.0/2' for US Pacific time.
|
||||
Posix TZ strings can take the following form (with optional
|
||||
items in brackets):
|
||||
<PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
> StdOffset[Dst[Offset],Date/Time,Date/Time]</PRE
|
||||
>
|
||||
where:</P
|
||||
><P
|
||||
><P
|
||||
></P
|
||||
><TABLE
|
||||
BORDER="0"
|
||||
><TBODY
|
||||
><TR
|
||||
><TD
|
||||
>`Std' is the standard time designation (e.g. `PST').</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>`Offset' is the number of hours behind UTC (e.g. `8').
|
||||
Prepend a `-' if you are ahead of UTC, and
|
||||
append `:30' if you are at a half-hour offset.
|
||||
Omit all the remaining items if you do not use
|
||||
daylight-saving time.</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>`Dst' is the daylight-saving time designation
|
||||
(e.g. `PDT').</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>The optional second `Offset' is the number of
|
||||
hours that daylight-saving time is behind UTC.
|
||||
The default is 1 hour ahead of standard time.</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>`Date/Time,Date/Time' specify when daylight-saving
|
||||
time starts and ends. The format for a date is
|
||||
`Mm.n.d', which specifies the dth day (0 is Sunday)
|
||||
of the nth week of the mth month, where week 5 means
|
||||
the last such day in the month. The format for a
|
||||
time is [h]h[:mm[:ss]], using a 24-hour clock.</TD
|
||||
></TR
|
||||
></TBODY
|
||||
></TABLE
|
||||
><P
|
||||
></P
|
||||
></P
|
||||
><P
|
||||
>Other Posix string formats are allowed but you don't want
|
||||
to know about them.</P
|
||||
><P
|
||||
>On the client side, you must make sure that your client's clock and
|
||||
time zone is also set appropriately. [[I don't know how to do this.]]
|
||||
Samba traditionally has had many problems dealing with time zones, due
|
||||
to the bizarre ways that Microsoft network protocols handle time
|
||||
zones. </P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN155"
|
||||
>2.10. How do I set the printer driver name correctly?</A
|
||||
></H1
|
||||
><P
|
||||
>Question:
|
||||
<SPAN
|
||||
CLASS="QUOTE"
|
||||
>" On NT, I opened "Printer Manager" and "Connect to Printer".
|
||||
Enter ["\\ptdi270\ps1"] in the box of printer. I got the
|
||||
following error message
|
||||
"</SPAN
|
||||
></P
|
||||
><P
|
||||
> <PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
> You do not have sufficient access to your machine
|
||||
to connect to the selected printer, since a driver
|
||||
needs to be installed locally.
|
||||
</PRE
|
||||
>
|
||||
</P
|
||||
><P
|
||||
>Answer:</P
|
||||
><P
|
||||
>In the more recent versions of Samba you can now set the "printer
|
||||
driver" in smb.conf. This tells the client what driver to use. For
|
||||
example:</P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
> printer driver = HP LaserJet 4L</PRE
|
||||
></P
|
||||
><P
|
||||
>With this, NT knows to use the right driver. You have to get this string
|
||||
exactly right.</P
|
||||
><P
|
||||
>To find the exact string to use, you need to get to the dialog box in
|
||||
your client where you select which printer driver to install. The
|
||||
correct strings for all the different printers are shown in a listbox
|
||||
in that dialog box.</P
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="NAVFOOTER"
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"><TABLE
|
||||
SUMMARY="Footer navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="faq-general.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="samba-faq.html"
|
||||
ACCESSKEY="H"
|
||||
>Home</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="faq-config.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
>General Information</TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
> </TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
>Configuration problems</TD
|
||||
></TR
|
||||
></TABLE
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
@ -1,181 +0,0 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>Printing problems</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
||||
REL="HOME"
|
||||
TITLE="Samba FAQ"
|
||||
HREF="samba-faq.html"><LINK
|
||||
REL="PREVIOUS"
|
||||
TITLE="Features"
|
||||
HREF="faq-features.html"></HEAD
|
||||
><BODY
|
||||
CLASS="CHAPTER"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><DIV
|
||||
CLASS="NAVHEADER"
|
||||
><TABLE
|
||||
SUMMARY="Header navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TH
|
||||
COLSPAN="3"
|
||||
ALIGN="center"
|
||||
>Samba FAQ</TH
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="left"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="faq-features.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="80%"
|
||||
ALIGN="center"
|
||||
VALIGN="bottom"
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="right"
|
||||
VALIGN="bottom"
|
||||
> </TD
|
||||
></TR
|
||||
></TABLE
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"></DIV
|
||||
><DIV
|
||||
CLASS="CHAPTER"
|
||||
><H1
|
||||
><A
|
||||
NAME="FAQ-PRINTING"
|
||||
></A
|
||||
>Chapter 7. Printing problems</H1
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN359"
|
||||
>7.1. setdriver or cupsaddsmb failes</A
|
||||
></H1
|
||||
><P
|
||||
>setdriver expects the following setup:
|
||||
|
||||
<P
|
||||
></P
|
||||
><TABLE
|
||||
BORDER="0"
|
||||
><TBODY
|
||||
><TR
|
||||
><TD
|
||||
>you are a printer admin, or root. this is the smb.conf printer admin group, not the Printer Operators group in NT. I've not tried the latter, but I don't believe it will work based on the current code.</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>printer admins has to be defined in [global]</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>upload the driver files to \\server\print$\w32x86 and win40 as appropriate. DON'T put them in the 0 or 2 subdirectories.</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>Make sure that the user you're connecting as is able to write to the print$ directories</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>Use adddriver (with appropriate parameters) to create the driver. note, this will not just update samba's notion of drivers, it will also move the files from the w32x86 and win40 directories to an appropriate subdirectory (based on driver version, I think, but not important enough for me to find out)</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>Use setdriver to associate the driver with a printer</TD
|
||||
></TR
|
||||
></TBODY
|
||||
></TABLE
|
||||
><P
|
||||
></P
|
||||
></P
|
||||
><P
|
||||
>The setdriver call will fail if the printer doesn't already exist in
|
||||
samba's view of the world. Either create the printer in cups and
|
||||
restart samba, or create an add printer command (see smb.conf doco)
|
||||
and use RPC calls to create a printer. NB the add printer command MUST
|
||||
return a single line of text indicating which port the printer was
|
||||
added on. If it doesn't, Samba won't reload the printer
|
||||
definitions. Although samba doesn't really support the notion of
|
||||
ports, suitable add printer command and enumport command settings can
|
||||
allow you pretty good remote control of the samba printer setup.</P
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="NAVFOOTER"
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"><TABLE
|
||||
SUMMARY="Footer navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="faq-features.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="samba-faq.html"
|
||||
ACCESSKEY="H"
|
||||
>Home</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
> </TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
>Features</TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
> </TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
> </TD
|
||||
></TR
|
||||
></TABLE
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
@ -1,431 +1,113 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>Reporting Bugs</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
||||
REL="HOME"
|
||||
TITLE="SAMBA Project Documentation"
|
||||
HREF="samba-howto-collection.html"><LINK
|
||||
REL="UP"
|
||||
TITLE="Appendixes"
|
||||
HREF="appendixes.html"><LINK
|
||||
REL="PREVIOUS"
|
||||
TITLE="Analysing and solving samba problems"
|
||||
HREF="problems.html"></HEAD
|
||||
><BODY
|
||||
CLASS="CHAPTER"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><DIV
|
||||
CLASS="NAVHEADER"
|
||||
><TABLE
|
||||
SUMMARY="Header navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TH
|
||||
COLSPAN="3"
|
||||
ALIGN="center"
|
||||
>SAMBA Project Documentation</TH
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="left"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="problems.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="80%"
|
||||
ALIGN="center"
|
||||
VALIGN="bottom"
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="right"
|
||||
VALIGN="bottom"
|
||||
> </TD
|
||||
></TR
|
||||
></TABLE
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"></DIV
|
||||
><DIV
|
||||
CLASS="CHAPTER"
|
||||
><H1
|
||||
><A
|
||||
NAME="BUGREPORT"
|
||||
></A
|
||||
>Chapter 35. Reporting Bugs</H1
|
||||
><DIV
|
||||
CLASS="TOC"
|
||||
><DL
|
||||
><DT
|
||||
><B
|
||||
>Table of Contents</B
|
||||
></DT
|
||||
><DT
|
||||
>35.1. <A
|
||||
HREF="bugreport.html#AEN5125"
|
||||
>Introduction</A
|
||||
></DT
|
||||
><DT
|
||||
>35.2. <A
|
||||
HREF="bugreport.html#AEN5135"
|
||||
>General info</A
|
||||
></DT
|
||||
><DT
|
||||
>35.3. <A
|
||||
HREF="bugreport.html#AEN5141"
|
||||
>Debug levels</A
|
||||
></DT
|
||||
><DT
|
||||
>35.4. <A
|
||||
HREF="bugreport.html#AEN5162"
|
||||
>Internal errors</A
|
||||
></DT
|
||||
><DT
|
||||
>35.5. <A
|
||||
HREF="bugreport.html#AEN5176"
|
||||
>Attaching to a running process</A
|
||||
></DT
|
||||
><DT
|
||||
>35.6. <A
|
||||
HREF="bugreport.html#AEN5184"
|
||||
>Patches</A
|
||||
></DT
|
||||
></DL
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN5125"
|
||||
>35.1. Introduction</A
|
||||
></H1
|
||||
><P
|
||||
>The email address for bug reports for stable releases is <A
|
||||
HREF="mailto:samba@samba.org"
|
||||
TARGET="_top"
|
||||
>samba@samba.org</A
|
||||
>.
|
||||
Bug reports for alpha releases should go to <A
|
||||
HREF="mailto:samba-technical@samba.org"
|
||||
TARGET="_top"
|
||||
>samba-technical@samba.org</A
|
||||
>.</P
|
||||
><P
|
||||
>Please take the time to read this file before you submit a bug
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 29. Reporting Bugs</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="troubleshooting.html" title="Part IV. Troubleshooting"><link rel="previous" href="problems.html" title="Chapter 28. Analysing and solving samba problems"><link rel="next" href="Appendixes.html" title="Part V. Appendixes"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 29. Reporting Bugs</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="problems.html">Prev</a> </td><th width="60%" align="center">Part IV. Troubleshooting</th><td width="20%" align="right"> <a accesskey="n" href="Appendixes.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="bugreport"></a>Chapter 29. Reporting Bugs</h2></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author"></h3><div class="affiliation"><span class="orgname">Samba Team<br></span></div></div></div><div><p class="pubdate"> 27 June 1997 </p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="bugreport.html#id2903912">Introduction</a></dt><dt><a href="bugreport.html#id2903826">General info</a></dt><dt><a href="bugreport.html#id2904609">Debug levels</a></dt><dt><a href="bugreport.html#id2904745">Internal errors</a></dt><dt><a href="bugreport.html#id2904838">Attaching to a running process</a></dt><dt><a href="bugreport.html#id2904885">Patches</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2903912"></a>Introduction</h2></div></div><p>Please report bugs using <a href="https://bugzilla.samba.org/" target="_top">bugzilla</a>.</p><p>
|
||||
Please take the time to read this file before you submit a bug
|
||||
report. Also, please see if it has changed between releases, as we
|
||||
may be changing the bug reporting mechanism at some time.</P
|
||||
><P
|
||||
>Please also do as much as you can yourself to help track down the
|
||||
may be changing the bug reporting mechanism at some time.
|
||||
</p><p>
|
||||
Please also do as much as you can yourself to help track down the
|
||||
bug. Samba is maintained by a dedicated group of people who volunteer
|
||||
their time, skills and efforts. We receive far more mail about it than
|
||||
we can possibly answer, so you have a much higher chance of an answer
|
||||
and a fix if you send us a "developer friendly" bug report that lets
|
||||
us fix it fast. </P
|
||||
><P
|
||||
>Do not assume that if you post the bug to the comp.protocols.smb
|
||||
and a fix if you send us a "developer friendly" bug report that lets
|
||||
us fix it fast.
|
||||
</p><p>
|
||||
Do not assume that if you post the bug to the comp.protocols.smb
|
||||
newsgroup or the mailing list that we will read it. If you suspect that your
|
||||
problem is not a bug but a configuration problem then it is better to send
|
||||
it to the Samba mailing list, as there are (at last count) 5000 other users on
|
||||
that list that may be able to help you.</P
|
||||
><P
|
||||
>You may also like to look though the recent mailing list archives,
|
||||
that list that may be able to help you.
|
||||
</p><p>
|
||||
You may also like to look though the recent mailing list archives,
|
||||
which are conveniently accessible on the Samba web pages
|
||||
at <A
|
||||
HREF="http://samba.org/samba/"
|
||||
TARGET="_top"
|
||||
>http://samba.org/samba/</A
|
||||
>.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN5135"
|
||||
>35.2. General info</A
|
||||
></H1
|
||||
><P
|
||||
>Before submitting a bug report check your config for silly
|
||||
at <a href="http://samba.org/samba/" target="_top">http://samba.org/samba/</a>.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2903826"></a>General info</h2></div></div><p>
|
||||
Before submitting a bug report check your config for silly
|
||||
errors. Look in your log files for obvious messages that tell you that
|
||||
you've misconfigured something and run testparm to test your config
|
||||
file for correct syntax.</P
|
||||
><P
|
||||
>Have you run through the <A
|
||||
HREF="diagnosis.html"
|
||||
>diagnosis</A
|
||||
>?
|
||||
This is very important.</P
|
||||
><P
|
||||
>If you include part of a log file with your bug report then be sure to
|
||||
file for correct syntax.
|
||||
</p><p>
|
||||
Have you run through the <a href="diagnosis.html" title="Chapter 27. The samba checklist">diagnosis</a>?
|
||||
This is very important.
|
||||
</p><p>
|
||||
If you include part of a log file with your bug report then be sure to
|
||||
annotate it with exactly what you were doing on the client at the
|
||||
time, and exactly what the results were.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN5141"
|
||||
>35.3. Debug levels</A
|
||||
></H1
|
||||
><P
|
||||
>If the bug has anything to do with Samba behaving incorrectly as a
|
||||
time, and exactly what the results were.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2904609"></a>Debug levels</h2></div></div><p>
|
||||
If the bug has anything to do with Samba behaving incorrectly as a
|
||||
server (like refusing to open a file) then the log files will probably
|
||||
be very useful. Depending on the problem a log level of between 3 and
|
||||
10 showing the problem may be appropriate. A higher level givesmore
|
||||
detail, but may use too much disk space.</P
|
||||
><P
|
||||
>To set the debug level use <B
|
||||
CLASS="COMMAND"
|
||||
>log level =</B
|
||||
> in your
|
||||
<TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf</TT
|
||||
>. You may also find it useful to set the log
|
||||
detail, but may use too much disk space.
|
||||
</p><p>
|
||||
To set the debug level use <b>log level =</b> in your
|
||||
<tt>smb.conf</tt>. You may also find it useful to set the log
|
||||
level higher for just one machine and keep separate logs for each machine.
|
||||
To do this use:</P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
>log level = 10
|
||||
To do this use:
|
||||
</p><pre class="programlisting">
|
||||
log level = 10
|
||||
log file = /usr/local/samba/lib/log.%m
|
||||
include = /usr/local/samba/lib/smb.conf.%m</PRE
|
||||
></P
|
||||
><P
|
||||
>then create a file
|
||||
<TT
|
||||
CLASS="FILENAME"
|
||||
>/usr/local/samba/lib/smb.conf.<VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>machine</VAR
|
||||
></TT
|
||||
> where
|
||||
<VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>machine</VAR
|
||||
> is the name of the client you wish to debug. In that file
|
||||
put any <TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf</TT
|
||||
> commands you want, for example
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>log level=</B
|
||||
> may be useful. This also allows you to
|
||||
include = /usr/local/samba/lib/smb.conf.%m
|
||||
</pre><p>
|
||||
then create a file
|
||||
<tt>/usr/local/samba/lib/smb.conf.<i><tt>machine</tt></i></tt> where
|
||||
<i><tt>machine</tt></i> is the name of the client you wish to debug. In that file
|
||||
put any <tt>smb.conf</tt> commands you want, for example
|
||||
<b>log level=</b> may be useful. This also allows you to
|
||||
experiment with different security systems, protocol levels etc on just
|
||||
one machine.</P
|
||||
><P
|
||||
>The <TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf</TT
|
||||
> entry <B
|
||||
CLASS="COMMAND"
|
||||
>log level =</B
|
||||
>
|
||||
is synonymous with the entry <B
|
||||
CLASS="COMMAND"
|
||||
>debuglevel =</B
|
||||
> that has been
|
||||
one machine.
|
||||
</p><p>
|
||||
The <tt>smb.conf</tt> entry <b>log level =</b>
|
||||
is synonymous with the entry <b>debuglevel =</b> that has been
|
||||
used in older versions of Samba and is being retained for backwards
|
||||
compatibility of <TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf</TT
|
||||
> files.</P
|
||||
><P
|
||||
>As the <B
|
||||
CLASS="COMMAND"
|
||||
>log level =</B
|
||||
> value is increased you will record
|
||||
compatibility of <tt>smb.conf</tt> files.
|
||||
</p><p>
|
||||
As the <b>log level =</b> value is increased you will record
|
||||
a significantly increasing level of debugging information. For most
|
||||
debugging operations you may not need a setting higher than 3. Nearly
|
||||
all bugs can be tracked at a setting of 10, but be prepared for a VERY
|
||||
large volume of log data.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN5162"
|
||||
>35.4. Internal errors</A
|
||||
></H1
|
||||
><P
|
||||
>If you get a "INTERNAL ERROR" message in your log files it means that
|
||||
large volume of log data.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2904745"></a>Internal errors</h2></div></div><p>
|
||||
If you get a "INTERNAL ERROR" message in your log files it means that
|
||||
Samba got an unexpected signal while running. It is probably a
|
||||
segmentation fault and almost certainly means a bug in Samba (unless
|
||||
you have faulty hardware or system software).</P
|
||||
><P
|
||||
>If the message came from smbd then it will probably be accompanied by
|
||||
you have faulty hardware or system software).
|
||||
</p><p>
|
||||
If the message came from smbd then it will probably be accompanied by
|
||||
a message which details the last SMB message received by smbd. This
|
||||
info is often very useful in tracking down the problem so please
|
||||
include it in your bug report.</P
|
||||
><P
|
||||
>You should also detail how to reproduce the problem, if
|
||||
possible. Please make this reasonably detailed.</P
|
||||
><P
|
||||
>You may also find that a core file appeared in a <TT
|
||||
CLASS="FILENAME"
|
||||
>corefiles</TT
|
||||
>
|
||||
include it in your bug report.
|
||||
</p><p>
|
||||
You should also detail how to reproduce the problem, if
|
||||
possible. Please make this reasonably detailed.
|
||||
</p><p>
|
||||
You may also find that a core file appeared in a <tt>corefiles</tt>
|
||||
subdirectory of the directory where you keep your samba log
|
||||
files. This file is the most useful tool for tracking down the bug. To
|
||||
use it you do this:</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>gdb smbd core</B
|
||||
></P
|
||||
><P
|
||||
>adding appropriate paths to smbd and core so gdb can find them. If you
|
||||
don't have gdb then try <KBD
|
||||
CLASS="USERINPUT"
|
||||
>dbx</KBD
|
||||
>. Then within the debugger use the
|
||||
command <KBD
|
||||
CLASS="USERINPUT"
|
||||
>where</KBD
|
||||
> to give a stack trace of where the problem
|
||||
occurred. Include this in your mail.</P
|
||||
><P
|
||||
>If you known any assembly language then do a <KBD
|
||||
CLASS="USERINPUT"
|
||||
>disass</KBD
|
||||
> of the routine
|
||||
use it you do this:
|
||||
</p><p><b>gdb smbd core</b></p><p>
|
||||
adding appropriate paths to smbd and core so gdb can find them. If you
|
||||
don't have gdb then try <b><tt>dbx</tt></b>. Then within the debugger use the
|
||||
command <b><tt>where</tt></b> to give a stack trace of where the problem
|
||||
occurred. Include this in your mail.
|
||||
</p><p>
|
||||
If you know any assembly language then do a <b><tt>disass</tt></b> of the routine
|
||||
where the problem occurred (if its in a library routine then
|
||||
disassemble the routine that called it) and try to work out exactly
|
||||
where the problem is by looking at the surrounding code. Even if you
|
||||
don't know assembly then incuding this info in the bug report can be
|
||||
useful. </P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN5176"
|
||||
>35.5. Attaching to a running process</A
|
||||
></H1
|
||||
><P
|
||||
>Unfortunately some unixes (in particular some recent linux kernels)
|
||||
useful.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2904838"></a>Attaching to a running process</h2></div></div><p>
|
||||
Unfortunately some unixes (in particular some recent linux kernels)
|
||||
refuse to dump a core file if the task has changed uid (which smbd
|
||||
does often). To debug with this sort of system you could try to attach
|
||||
to the running process using <KBD
|
||||
CLASS="USERINPUT"
|
||||
>gdb smbd <VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>PID</VAR
|
||||
></KBD
|
||||
> where you get <VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>PID</VAR
|
||||
> from
|
||||
<SPAN
|
||||
CLASS="APPLICATION"
|
||||
>smbstatus</SPAN
|
||||
>. Then use <KBD
|
||||
CLASS="USERINPUT"
|
||||
>c</KBD
|
||||
> to continue and try to cause the core dump
|
||||
to the running process using <b><tt>gdb smbd <i><tt>PID</tt></i></tt></b> where you get <i><tt>PID</tt></i> from
|
||||
smbstatus. Then use <b><tt>c</tt></b> to continue and try to cause the core dump
|
||||
using the client. The debugger should catch the fault and tell you
|
||||
where it occurred.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN5184"
|
||||
>35.6. Patches</A
|
||||
></H1
|
||||
><P
|
||||
>The best sort of bug report is one that includes a fix! If you send us
|
||||
patches please use <KBD
|
||||
CLASS="USERINPUT"
|
||||
>diff -u</KBD
|
||||
> format if your version of
|
||||
diff supports it, otherwise use <KBD
|
||||
CLASS="USERINPUT"
|
||||
>diff -c4</KBD
|
||||
>. Make sure
|
||||
your do the diff against a clean version of the source and let me know
|
||||
exactly what version you used. </P
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="NAVFOOTER"
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"><TABLE
|
||||
SUMMARY="Footer navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="problems.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="samba-howto-collection.html"
|
||||
ACCESSKEY="H"
|
||||
>Home</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
> </TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
>Analysing and solving samba problems</TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="appendixes.html"
|
||||
ACCESSKEY="U"
|
||||
>Up</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
> </TD
|
||||
></TR
|
||||
></TABLE
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
where it occurred.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2904885"></a>Patches</h2></div></div><p>
|
||||
The best sort of bug report is one that includes a fix! If you send us
|
||||
patches please use <b><tt>diff -u</tt></b> format if your version of
|
||||
diff supports it, otherwise use <b><tt>diff -c4</tt></b>. Make sure
|
||||
you do the diff against a clean version of the source and let me know
|
||||
exactly what version you used.
|
||||
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="problems.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="Appendixes.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 28. Analysing and solving samba problems </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Part V. Appendixes</td></tr></table></div></body></html>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -1,446 +1,79 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>Samba as a NT4 or Win2k domain member</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
||||
REL="HOME"
|
||||
TITLE="SAMBA Project Documentation"
|
||||
HREF="samba-howto-collection.html"><LINK
|
||||
REL="UP"
|
||||
TITLE="Type of installation"
|
||||
HREF="type.html"><LINK
|
||||
REL="PREVIOUS"
|
||||
TITLE="Samba as a ADS domain member"
|
||||
HREF="ads.html"><LINK
|
||||
REL="NEXT"
|
||||
TITLE="Advanced Configuration"
|
||||
HREF="optional.html"></HEAD
|
||||
><BODY
|
||||
CLASS="CHAPTER"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><DIV
|
||||
CLASS="NAVHEADER"
|
||||
><TABLE
|
||||
SUMMARY="Header navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TH
|
||||
COLSPAN="3"
|
||||
ALIGN="center"
|
||||
>SAMBA Project Documentation</TH
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="left"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="ads.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="80%"
|
||||
ALIGN="center"
|
||||
VALIGN="bottom"
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="right"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="optional.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
></TABLE
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"></DIV
|
||||
><DIV
|
||||
CLASS="CHAPTER"
|
||||
><H1
|
||||
><A
|
||||
NAME="DOMAIN-MEMBER"
|
||||
></A
|
||||
>Chapter 10. Samba as a NT4 or Win2k domain member</H1
|
||||
><DIV
|
||||
CLASS="TOC"
|
||||
><DL
|
||||
><DT
|
||||
><B
|
||||
>Table of Contents</B
|
||||
></DT
|
||||
><DT
|
||||
>10.1. <A
|
||||
HREF="domain-member.html#AEN1447"
|
||||
>Joining an NT Domain with Samba 3.0</A
|
||||
></DT
|
||||
><DT
|
||||
>10.2. <A
|
||||
HREF="domain-member.html#AEN1501"
|
||||
>Why is this better than security = server?</A
|
||||
></DT
|
||||
></DL
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN1447"
|
||||
>10.1. Joining an NT Domain with Samba 3.0</A
|
||||
></H1
|
||||
><P
|
||||
>Assume you have a Samba 3.0 server with a NetBIOS name of
|
||||
<CODE
|
||||
CLASS="CONSTANT"
|
||||
>SERV1</CODE
|
||||
> and are joining an or Win2k NT domain called
|
||||
<CODE
|
||||
CLASS="CONSTANT"
|
||||
>DOM</CODE
|
||||
>, which has a PDC with a NetBIOS name
|
||||
of <CODE
|
||||
CLASS="CONSTANT"
|
||||
>DOMPDC</CODE
|
||||
> and two backup domain controllers
|
||||
with NetBIOS names <CODE
|
||||
CLASS="CONSTANT"
|
||||
>DOMBDC1</CODE
|
||||
> and <CODE
|
||||
CLASS="CONSTANT"
|
||||
>DOMBDC2
|
||||
</CODE
|
||||
>.</P
|
||||
><P
|
||||
>Firstly, you must edit your <TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf</TT
|
||||
> file to tell Samba it should
|
||||
now use domain security.</P
|
||||
><P
|
||||
>Change (or add) your <A
|
||||
HREF="smb.conf.5.html#SECURITY"
|
||||
TARGET="_top"
|
||||
> <VAR
|
||||
CLASS="PARAMETER"
|
||||
>security =</VAR
|
||||
></A
|
||||
> line in the [global] section
|
||||
of your <TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf</TT
|
||||
> to read:</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>security = domain</B
|
||||
></P
|
||||
><P
|
||||
>Next change the <A
|
||||
HREF="smb.conf.5.html#WORKGROUP"
|
||||
TARGET="_top"
|
||||
><VAR
|
||||
CLASS="PARAMETER"
|
||||
> workgroup =</VAR
|
||||
></A
|
||||
> line in the [global] section to read: </P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>workgroup = DOM</B
|
||||
></P
|
||||
><P
|
||||
>as this is the name of the domain we are joining. </P
|
||||
><P
|
||||
>You must also have the parameter <A
|
||||
HREF="smb.conf.5.html#ENCRYPTPASSWORDS"
|
||||
TARGET="_top"
|
||||
> <VAR
|
||||
CLASS="PARAMETER"
|
||||
>encrypt passwords</VAR
|
||||
></A
|
||||
> set to <CODE
|
||||
CLASS="CONSTANT"
|
||||
>yes
|
||||
</CODE
|
||||
> in order for your users to authenticate to the NT PDC.</P
|
||||
><P
|
||||
>Finally, add (or modify) a <A
|
||||
HREF="smb.conf.5.html#PASSWORDSERVER"
|
||||
TARGET="_top"
|
||||
> <VAR
|
||||
CLASS="PARAMETER"
|
||||
>password server =</VAR
|
||||
></A
|
||||
> line in the [global]
|
||||
section to read: </P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>password server = DOMPDC DOMBDC1 DOMBDC2</B
|
||||
></P
|
||||
><P
|
||||
>These are the primary and backup domain controllers Samba
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 8. Samba as a NT4 or Win2k domain member</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="type.html" title="Part II. Server Configuration Basics"><link rel="previous" href="ADS.html" title="Chapter 7. Samba as a ADS domain member"><link rel="next" href="optional.html" title="Part III. Advanced Configuration"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 8. Samba as a NT4 or Win2k domain member</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ADS.html">Prev</a> </td><th width="60%" align="center">Part II. Server Configuration Basics</th><td width="20%" align="right"> <a accesskey="n" href="optional.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="domain-member"></a>Chapter 8. Samba as a NT4 or Win2k domain member</h2></div><div><div class="author"><h3 class="author">Jeremy Allison</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jra@samba.org">jra@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">Gerald (Jerry) Carter</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jerry@samba.org">jerry@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">16 Apr 2001</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="domain-member.html#id2879309">Joining an NT Domain with Samba 3.0</a></dt><dt><a href="domain-member.html#id2880214">Why is this better than security = server?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2879309"></a>Joining an NT Domain with Samba 3.0</h2></div></div><p><span class="emphasis"><em>Assumptions:</em></span>
|
||||
</p><pre class="programlisting">
|
||||
NetBIOS name: SERV1
|
||||
Win2K/NT domain name: DOM
|
||||
Domain's PDC NetBIOS name: DOMPDC
|
||||
Domain's BDC NetBIOS names: DOMBDC1 and DOMBDC2
|
||||
</pre><p>
|
||||
</p><p>First, you must edit your <tt>smb.conf</tt> file to tell Samba it should
|
||||
now use domain security.</p><p>Change (or add) your <a href="smb.conf.5.html#SECURITY" target="_top">
|
||||
<i><tt>security =</tt></i></a> line in the [global] section
|
||||
of your <tt>smb.conf</tt> to read:</p><p><b>security = domain</b></p><p>Next change the <a href="smb.conf.5.html#WORKGROUP" target="_top"><i><tt>
|
||||
workgroup =</tt></i></a> line in the [global] section to read: </p><p><b>workgroup = DOM</b></p><p>as this is the name of the domain we are joining. </p><p>You must also have the parameter <a href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">
|
||||
<i><tt>encrypt passwords</tt></i></a> set to <tt>yes
|
||||
</tt> in order for your users to authenticate to the NT PDC.</p><p>Finally, add (or modify) a <a href="smb.conf.5.html#PASSWORDSERVER" target="_top">
|
||||
<i><tt>password server =</tt></i></a> line in the [global]
|
||||
section to read: </p><p><b>password server = DOMPDC DOMBDC1 DOMBDC2</b></p><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
|
||||
><P
|
||||
>Alternatively, if you want smbd to automatically determine
|
||||
among domain controllers.</p><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
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>password server = *</B
|
||||
></P
|
||||
><P
|
||||
>This method, allows Samba to use exactly the same
|
||||
set this line to be :</p><p><b>password server = *</b></p><p>This method, 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
|
||||
><P
|
||||
>In order to actually join the domain, you must run this
|
||||
command:</P
|
||||
><P
|
||||
><SAMP
|
||||
CLASS="PROMPT"
|
||||
>root# </SAMP
|
||||
><KBD
|
||||
CLASS="USERINPUT"
|
||||
>net rpc join -S DOMPDC
|
||||
-U<VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>Administrator%password</VAR
|
||||
></KBD
|
||||
></P
|
||||
><P
|
||||
>as we are joining the domain DOM and the PDC for that domain
|
||||
find domain controllers to authenticate against.</p><p>In order to actually join the domain, you must run this
|
||||
command:</p><p><tt>root# </tt><b><tt>net join -S DOMPDC
|
||||
-U<i><tt>Administrator%password</tt></i></tt></b></p><p>
|
||||
If the <b><tt>-S DOMPDC</tt></b> argument is not given then
|
||||
the domain name will be obtained from smb.conf.
|
||||
</p><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. The <VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>Administrator%password</VAR
|
||||
> is
|
||||
is DOMPDC. The <i><tt>Administrator%password</tt></i> is
|
||||
the login name and password for an account which has the necessary
|
||||
privilege to add machines to the domain. If this is successful
|
||||
you will see the message:</P
|
||||
><P
|
||||
><SAMP
|
||||
CLASS="COMPUTEROUTPUT"
|
||||
>Joined domain DOM.</SAMP
|
||||
>
|
||||
or <SAMP
|
||||
CLASS="COMPUTEROUTPUT"
|
||||
>Joined 'SERV1' to realm 'MYREALM'</SAMP
|
||||
>
|
||||
</P
|
||||
><P
|
||||
>in your terminal window. See the <A
|
||||
HREF="net.8.html"
|
||||
TARGET="_top"
|
||||
> net(8)</A
|
||||
> man page for more details.</P
|
||||
><P
|
||||
>This process joins the server to thedomain
|
||||
you will see the message:</p><p><tt>Joined domain DOM.</tt>
|
||||
or <tt>Joined 'SERV1' to realm 'MYREALM'</tt>
|
||||
</p><p>in your terminal window. See the <a href="net.8.html" target="_top">
|
||||
net(8)</a> man page for more details.</p><p>This process joins the server to the domain
|
||||
without having to create the machine trust account on the PDC
|
||||
beforehand.</P
|
||||
><P
|
||||
>This command goes through the machine account password
|
||||
beforehand.</p><p>This command goes through the machine account password
|
||||
change protocol, then writes the new (random) machine account
|
||||
password for this Samba server into a file in the same directory
|
||||
in which an smbpasswd file would be stored - normally :</P
|
||||
><P
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>/usr/local/samba/private/secrets.tdb</TT
|
||||
></P
|
||||
><P
|
||||
>This file is created and owned by root and is not
|
||||
in which an smbpasswd file would be stored - normally :</p><p><tt>/usr/local/samba/private/secrets.tdb</tt></p><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
|
||||
><P
|
||||
>Finally, restart your Samba daemons and get ready for
|
||||
clients to begin using domain security!</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN1501"
|
||||
>10.2. Why is this better than security = server?</A
|
||||
></H1
|
||||
><P
|
||||
>Currently, domain security in Samba doesn't free you from
|
||||
as a shadow password file.</p><p>Finally, restart your Samba daemons and get ready for
|
||||
clients to begin using domain security!</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2880214"></a>Why is this better than security = server?</h2></div></div><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
|
||||
CLASS="CONSTANT"
|
||||
>DOM\fred
|
||||
</CODE
|
||||
> attaches to your domain security Samba server, there needs
|
||||
to your server. This means that if domain user <tt>DOM\fred
|
||||
</tt> attaches to your domain security Samba server, there needs
|
||||
to be a local Unix user fred to represent that user in the Unix
|
||||
filesystem. This is very similar to the older Samba security mode
|
||||
<A
|
||||
HREF="smb.conf.5.html#SECURITYEQUALSSERVER"
|
||||
TARGET="_top"
|
||||
>security = server</A
|
||||
>,
|
||||
<a href="smb.conf.5.html#SECURITYEQUALSSERVER" target="_top">security = server</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
|
||||
><P
|
||||
>Please refer to the <A
|
||||
HREF="winbind.html"
|
||||
TARGET="_top"
|
||||
>Winbind
|
||||
paper</A
|
||||
> for information on a system to automatically
|
||||
</p><p>Please refer to the <a href="winbind.html" target="_top">Winbind
|
||||
paper</a> for information on a system to automatically
|
||||
assign UNIX uids and gids to Windows NT Domain users and groups.
|
||||
This code is available in development branches only at the moment,
|
||||
but will be moved to release branches soon.</P
|
||||
><P
|
||||
>The advantage to domain-level security is that the
|
||||
</p><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
|
||||
><P
|
||||
>In addition, with <B
|
||||
CLASS="COMMAND"
|
||||
>security = server</B
|
||||
> every Samba
|
||||
domain PDC to an account domain PDC).</p><p>In addition, with <b>security = server</b> 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 connections. With <B
|
||||
CLASS="COMMAND"
|
||||
>security = domain</B
|
||||
>,
|
||||
out of available connections. With <b>security = domain</b>,
|
||||
however, the Samba 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
|
||||
><P
|
||||
>And finally, acting in the same manner as an NT server
|
||||
thus conserving PDC connection resources.</p><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. </P
|
||||
><DIV
|
||||
CLASS="NOTE"
|
||||
><P
|
||||
></P
|
||||
><TABLE
|
||||
CLASS="NOTE"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="25"
|
||||
ALIGN="CENTER"
|
||||
VALIGN="TOP"
|
||||
><IMG
|
||||
SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
|
||||
HSPACE="5"
|
||||
ALT="Note"></TD
|
||||
><TD
|
||||
ALIGN="LEFT"
|
||||
VALIGN="TOP"
|
||||
><P
|
||||
> Much of the text of this document
|
||||
was first published in the Web magazine <A
|
||||
HREF="http://www.linuxworld.com"
|
||||
TARGET="_top"
|
||||
>
|
||||
LinuxWorld</A
|
||||
> as the article <A
|
||||
HREF="http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html"
|
||||
TARGET="_top"
|
||||
>Doing
|
||||
the NIS/NT Samba</A
|
||||
>.</P
|
||||
></TD
|
||||
></TR
|
||||
></TABLE
|
||||
></DIV
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="NAVFOOTER"
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"><TABLE
|
||||
SUMMARY="Footer navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="ads.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="samba-howto-collection.html"
|
||||
ACCESSKEY="H"
|
||||
>Home</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="optional.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
>Samba as a ADS domain member</TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="type.html"
|
||||
ACCESSKEY="U"
|
||||
>Up</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
>Advanced Configuration</TD
|
||||
></TR
|
||||
></TABLE
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
as the user SID, the list of NT groups the user belongs to, etc. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p> Much of the text of this document
|
||||
was first published in the Web magazine <a href="http://www.linuxworld.com" target="_top">
|
||||
LinuxWorld</a> as the article <a href="http://www.linuxworld.com/linuxworld/lw-1998-10/lw-10-samba.html" target="_top">Doing
|
||||
the NIS/NT Samba</a>.</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ADS.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="type.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="optional.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 7. Samba as a ADS domain member </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Part III. Advanced Configuration</td></tr></table></div></body></html>
|
||||
|
||||
@ -1,142 +1,12 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>editreg</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="EDITREG.1"
|
||||
></A
|
||||
>editreg</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>editreg -- A utility to report and change SIDs in registry files
|
||||
</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>editreg</B
|
||||
> [-v] [-c file] {file}</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN14"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
>This tool is part of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
> suite.</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>editreg</B
|
||||
> is a utility that
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>editreg</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="editreg.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>editreg — A utility to report and change SIDs in registry files
|
||||
</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>editreg</tt> [-v] [-c file] {file}</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>editreg</b> is a utility that
|
||||
can visualize windows registry files (currently only NT4) and apply
|
||||
so-called commandfiles to them.
|
||||
</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN22"
|
||||
></A
|
||||
><H2
|
||||
>OPTIONS</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>registry_file</DT
|
||||
><DD
|
||||
><P
|
||||
>Registry file to view or edit. </P
|
||||
></DD
|
||||
><DT
|
||||
>-v,--verbose</DT
|
||||
><DD
|
||||
><P
|
||||
>Increases verbosity of messages.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-c commandfile</DT
|
||||
><DD
|
||||
><P
|
||||
>Read commands to execute on <TT
|
||||
CLASS="FILENAME"
|
||||
>registry_file</TT
|
||||
> from <TT
|
||||
CLASS="FILENAME"
|
||||
>commandfile</TT
|
||||
>. Currently not yet supported!
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-h|--help</DT
|
||||
><DD
|
||||
><P
|
||||
>Print a summary of command line options.</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN43"
|
||||
></A
|
||||
><H2
|
||||
>VERSION</H2
|
||||
><P
|
||||
>This man page is correct for version 3.0 of the Samba
|
||||
suite.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN46"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>The original Samba software and related utilities
|
||||
</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">registry_file</span></dt><dd><p>Registry file to view or edit. </p></dd><dt><span class="term">-v,--verbose</span></dt><dd><p>Increases verbosity of messages.
|
||||
</p></dd><dt><span class="term">-c commandfile</span></dt><dd><p>Read commands to execute on <tt>registry_file</tt> from <tt>commandfile</tt>. Currently not yet supported!
|
||||
</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
|
||||
</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the Samba
|
||||
suite.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.</P
|
||||
><P
|
||||
>The editreg man page was written by Jelmer Vernooij. </P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
to the way the Linux kernel is developed.</p><p>The editreg man page was written by Jelmer Vernooij. </p></div></div></body></html>
|
||||
|
||||
@ -1,295 +1,61 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>findsmb</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="FINDSMB.1"
|
||||
></A
|
||||
>findsmb</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>findsmb -- list info about machines that respond to SMB
|
||||
name queries on a subnet</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>findsmb</B
|
||||
> [subnet broadcast address]</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN12"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
>This perl script is part of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
>
|
||||
suite.</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>findsmb</B
|
||||
> is a perl script that
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>findsmb</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="findsmb.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>findsmb — list info about machines that respond to SMB
|
||||
name queries on a subnet</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>findsmb</tt> [subnet broadcast address]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This perl script is part of the <a href="Samba.7.html">Samba(7)</a>
|
||||
suite.</p><p><b>findsmb</b> is a perl script that
|
||||
prints out several pieces of information about machines
|
||||
on a subnet that respond to SMB name query requests.
|
||||
It uses <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>nmblookup</SPAN
|
||||
>(1)</SPAN
|
||||
>
|
||||
and <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbclient</SPAN
|
||||
>(1)</SPAN
|
||||
>
|
||||
It uses <a href="nmblookup.1.html">nmblookup(1)</a>
|
||||
and <a href="smbclient.1.html">smbclient(1)</a>
|
||||
to obtain this information.
|
||||
</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN26"
|
||||
></A
|
||||
><H2
|
||||
>OPTIONS</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>-r</DT
|
||||
><DD
|
||||
><P
|
||||
>Controls whether <B
|
||||
CLASS="COMMAND"
|
||||
>findsmb</B
|
||||
> takes
|
||||
</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-r</span></dt><dd><p>Controls whether <b>findsmb</b> takes
|
||||
bugs in Windows95 into account when trying to find a Netbios name
|
||||
registered of the remote machine. This option is disabled by default
|
||||
because it is specific to Windows 95 and Windows 95 machines only.
|
||||
If set, <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>nmblookup</SPAN
|
||||
>(1)</SPAN
|
||||
>
|
||||
will be called with <CODE
|
||||
CLASS="CONSTANT"
|
||||
>-B</CODE
|
||||
> option.</P
|
||||
></DD
|
||||
><DT
|
||||
>subnet broadcast address</DT
|
||||
><DD
|
||||
><P
|
||||
>Without this option, <B
|
||||
CLASS="COMMAND"
|
||||
>findsmb
|
||||
</B
|
||||
> will probe the subnet of the machine where
|
||||
<SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>findsmb</SPAN
|
||||
>(1)</SPAN
|
||||
>
|
||||
If set, <a href="nmblookup.1.html">nmblookup(1)</a>
|
||||
will be called with <tt>-B</tt> option.</p></dd><dt><span class="term">subnet broadcast address</span></dt><dd><p>Without this option, <b>findsmb
|
||||
</b> will probe the subnet of the machine where
|
||||
<a href="findsmb.1.html">findsmb(1)</a>
|
||||
is run. This value is passed to
|
||||
<SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>nmblookup</SPAN
|
||||
>(1)</SPAN
|
||||
>
|
||||
as part of the <CODE
|
||||
CLASS="CONSTANT"
|
||||
>-B</CODE
|
||||
> option.</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN50"
|
||||
></A
|
||||
><H2
|
||||
>EXAMPLES</H2
|
||||
><P
|
||||
>The output of <B
|
||||
CLASS="COMMAND"
|
||||
>findsmb</B
|
||||
> lists the following
|
||||
<a href="nmblookup.1.html">nmblookup(1)</a>
|
||||
as part of the <tt>-B</tt> option.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>EXAMPLES</h2><p>The output of <b>findsmb</b> lists the following
|
||||
information for all machines that respond to the initial
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>nmblookup</B
|
||||
> for any name: IP address, NetBIOS name,
|
||||
Workgroup name, operating system, and SMB server version.</P
|
||||
><P
|
||||
>There will be a '+' in front of the workgroup name for
|
||||
<b>nmblookup</b> for any name: IP address, NetBIOS name,
|
||||
Workgroup name, operating system, and SMB server version.</p><p>There will be a '+' in front of the workgroup name for
|
||||
machines that are local master browsers for that workgroup. There
|
||||
will be an '*' in front of the workgroup name for
|
||||
machines that are the domain master browser for that workgroup.
|
||||
Machines that are running Windows, Windows 95 or Windows 98 will
|
||||
not show any information about the operating system or server
|
||||
version.</P
|
||||
><P
|
||||
>The command with <CODE
|
||||
CLASS="CONSTANT"
|
||||
>-r</CODE
|
||||
> option
|
||||
must be run on a system without <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>nmbd</SPAN
|
||||
>(8)</SPAN
|
||||
> running.
|
||||
version.</p><p>The command with <tt>-r</tt> option
|
||||
must be run on a system without <a href="nmbd.8.html">nmbd(8)</a> running.
|
||||
|
||||
If <B
|
||||
CLASS="COMMAND"
|
||||
>nmbd</B
|
||||
> is running on the system, you will
|
||||
If <b>nmbd</b> is running on the system, you will
|
||||
only get the IP address and the DNS name of the machine. To
|
||||
get proper responses from Windows 95 and Windows 98 machines,
|
||||
the command must be run as root and with <CODE
|
||||
CLASS="CONSTANT"
|
||||
>-r</CODE
|
||||
>
|
||||
option on a machine without <B
|
||||
CLASS="COMMAND"
|
||||
>nmbd</B
|
||||
> running.</P
|
||||
><P
|
||||
>For example, running <B
|
||||
CLASS="COMMAND"
|
||||
>findsmb</B
|
||||
>
|
||||
without <CODE
|
||||
CLASS="CONSTANT"
|
||||
>-r</CODE
|
||||
> option set would yield output similar
|
||||
to the following</P
|
||||
><PRE
|
||||
CLASS="SCREEN"
|
||||
> IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION
|
||||
---------------------------------------------------------------------
|
||||
192.168.35.10 MINESET-TEST1 [DMVENGR]
|
||||
192.168.35.55 LINUXBOX *[MYGROUP] [Unix] [Samba 2.0.6]
|
||||
5 192.168.35.56 HERBNT2 [HERB-NT]
|
||||
192.168.35.63 GANDALF [MVENGR] [Unix] [Samba 2.0.5a for IRIX]
|
||||
192.168.35.65 SAUNA [WORKGROUP] [Unix] [Samba 1.9.18p10]
|
||||
192.168.35.71 FROGSTAR [ENGR] [Unix] [Samba 2.0.0 for IRIX]
|
||||
192.168.35.78 HERBDHCP1 +[HERB]
|
||||
10 192.168.35.88 SCNT2 +[MVENGR] [Windows NT 4.0] [NT LAN Manager 4.0]
|
||||
192.168.35.93 FROGSTAR-PC [MVENGR] [Windows 5.0] [Windows 2000 LAN Manager]
|
||||
192.168.35.97 HERBNT1 *[HERB-NT] [Windows NT 4.0] [NT LAN Manager 4.0]</PRE
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN68"
|
||||
></A
|
||||
><H2
|
||||
>VERSION</H2
|
||||
><P
|
||||
>This man page is correct for version 3.0 of
|
||||
the Samba suite.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN71"
|
||||
></A
|
||||
><H2
|
||||
>SEE ALSO</H2
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>nmbd</SPAN
|
||||
>(8)</SPAN
|
||||
>,
|
||||
<SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbclient</SPAN
|
||||
>(1)</SPAN
|
||||
>, and <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>nmblookup</SPAN
|
||||
>(1)</SPAN
|
||||
>
|
||||
</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN83"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>The original Samba software and related utilities
|
||||
the command must be run as root and with <tt>-r</tt>
|
||||
option on a machine without <b>nmbd</b> running.</p><p>For example, running <b>findsmb</b>
|
||||
without <tt>-r</tt> option set would yield output similar
|
||||
to the following</p><pre class="screen">
|
||||
IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION
|
||||
---------------------------------------------------------------------
|
||||
192.168.35.10 MINESET-TEST1 [DMVENGR]
|
||||
192.168.35.55 LINUXBOX *[MYGROUP] [Unix] [Samba 2.0.6]
|
||||
192.168.35.56 HERBNT2 [HERB-NT]
|
||||
192.168.35.63 GANDALF [MVENGR] [Unix] [Samba 2.0.5a for IRIX]
|
||||
192.168.35.65 SAUNA [WORKGROUP] [Unix] [Samba 1.9.18p10]
|
||||
192.168.35.71 FROGSTAR [ENGR] [Unix] [Samba 2.0.0 for IRIX]
|
||||
192.168.35.78 HERBDHCP1 +[HERB]
|
||||
192.168.35.88 SCNT2 +[MVENGR] [Windows NT 4.0] [NT LAN Manager 4.0]
|
||||
192.168.35.93 FROGSTAR-PC [MVENGR] [Windows 5.0] [Windows 2000 LAN Manager]
|
||||
192.168.35.97 HERBNT1 *[HERB-NT] [Windows NT 4.0] [NT LAN Manager 4.0]
|
||||
</pre></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of
|
||||
the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="nmbd.8.html">nmbd(8)</a>,
|
||||
<a href="smbclient.1.html">smbclient(1)</a>, and <a href="nmblookup.1.html">nmblookup(1)</a>
|
||||
</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.</P
|
||||
><P
|
||||
>The original Samba man pages were written by Karl Auer.
|
||||
to the way the Linux kernel is developed.</p><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/"
|
||||
TARGET="_top"
|
||||
>ftp://ftp.icce.rug.nl/pub/unix/</A
|
||||
>)
|
||||
excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">ftp://ftp.icce.rug.nl/pub/unix/</a>)
|
||||
and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook
|
||||
XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
|
||||
|
||||
@ -1,236 +1,53 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>Configuring Group Mapping</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
||||
REL="HOME"
|
||||
TITLE="SAMBA Project Documentation"
|
||||
HREF="samba-howto-collection.html"><LINK
|
||||
REL="UP"
|
||||
TITLE="Advanced Configuration"
|
||||
HREF="optional.html"><LINK
|
||||
REL="PREVIOUS"
|
||||
TITLE="UNIX Permission Bits and Windows NT Access Control Lists"
|
||||
HREF="unix-permissions.html"><LINK
|
||||
REL="NEXT"
|
||||
TITLE="Printing Support"
|
||||
HREF="printing.html"></HEAD
|
||||
><BODY
|
||||
CLASS="CHAPTER"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><DIV
|
||||
CLASS="NAVHEADER"
|
||||
><TABLE
|
||||
SUMMARY="Header navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TH
|
||||
COLSPAN="3"
|
||||
ALIGN="center"
|
||||
>SAMBA Project Documentation</TH
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="left"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="unix-permissions.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="80%"
|
||||
ALIGN="center"
|
||||
VALIGN="bottom"
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="right"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="printing.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
></TABLE
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"></DIV
|
||||
><DIV
|
||||
CLASS="CHAPTER"
|
||||
><H1
|
||||
><A
|
||||
NAME="GROUPMAPPING"
|
||||
></A
|
||||
>Chapter 12. Configuring Group Mapping</H1
|
||||
><P
|
||||
>
|
||||
Starting with Samba 3.0 alpha 2, a new group mapping function is available. The
|
||||
current method (likely to change) to manage the groups is a new command called
|
||||
<SPAN
|
||||
CLASS="APPLICATION"
|
||||
>smbgroupedit</SPAN
|
||||
>.</P
|
||||
><P
|
||||
>The first immediate reason to use the group mapping on a PDC, is that
|
||||
the <B
|
||||
CLASS="COMMAND"
|
||||
>domain admin group</B
|
||||
> of <TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf</TT
|
||||
> is
|
||||
now gone. This parameter was used to give the listed users local admin rights
|
||||
on their workstations. It was some magic stuff that simply worked but didn't
|
||||
scale very well for complex setups.</P
|
||||
><P
|
||||
>Let me explain how it works on NT/W2K, to have this magic fade away.
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 12. Configuring Group Mapping</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="previous" href="unix-permissions.html" title="Chapter 11. UNIX Permission Bits and Windows NT Access Control Lists"><link rel="next" href="printing.html" title="Chapter 13. Printing Support"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 12. Configuring Group Mapping</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="unix-permissions.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="printing.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="groupmapping"></a>Chapter 12. Configuring Group Mapping</h2></div><div><div class="author"><h3 class="author">Jean François Micouleau</h3></div></div><div><div class="author"><h3 class="author">Gerald (Jerry) Carter</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jerry@samba.org">jerry@samba.org</a>></tt></p></div></div></div></div></div><p>
|
||||
Starting with Samba 3.0 alpha 2, new group mapping functionality
|
||||
is available to create associations between Windows SIDs and UNIX
|
||||
groups. The <i><tt>groupmap</tt></i> subcommand included with
|
||||
the <b>net</b> tool can be used to manage these associations.
|
||||
</p><p>
|
||||
The first immediate reason to use the group mapping on a Samba PDC, is that
|
||||
the <i><tt>domain admin group</tt></i> <tt>smb.conf</tt> has been removed.
|
||||
This parameter was used to give the listed users membership in the "Domain Admins"
|
||||
Windows group which gave local admin rights on their workstations (in
|
||||
default configurations).
|
||||
</p><p>
|
||||
When installing NT/W2K on a computer, the installer program creates some users
|
||||
and groups. Notably the 'Administrators' group, and gives to that group some
|
||||
privileges like the ability to change the date and time or to kill any process
|
||||
(or close too) running on the local machine. The 'Administrator' user is a
|
||||
member of the 'Administrators' group, and thus 'inherit' the 'Administrators'
|
||||
group privileges. If a 'joe' user is created and become a member of the
|
||||
'Administrator' group, 'joe' has exactly the same rights as 'Administrator'.</P
|
||||
><P
|
||||
>When a NT/W2K machine is joined to a domain, during that phase, the "Domain
|
||||
Administrators' group of the PDC is added to the 'Administrators' group of the
|
||||
workstation. Every members of the 'Domain Administrators' group 'inherit' the
|
||||
rights of the 'Administrators' group when logging on the workstation.</P
|
||||
><P
|
||||
>You are now wondering how to make some of your samba PDC users members of the
|
||||
'Domain Administrators' ? That's really easy.</P
|
||||
><P
|
||||
></P
|
||||
><OL
|
||||
TYPE="1"
|
||||
><LI
|
||||
><P
|
||||
>create a unix group (usually in <TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/group</TT
|
||||
>), let's call it domadm</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>add to this group the users that must be Administrators. For example if you want joe,john and mary, your entry in <TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/group</TT
|
||||
> will look like:</P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
>domadm:x:502:joe,john,mary</PRE
|
||||
></P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>Map this domadm group to the <B
|
||||
CLASS="COMMAND"
|
||||
>domain admins</B
|
||||
> group by running the command:</P
|
||||
><P
|
||||
><KBD
|
||||
CLASS="USERINPUT"
|
||||
>smbgroupedit -c "Domain Admins" -u domadm</KBD
|
||||
></P
|
||||
></LI
|
||||
></OL
|
||||
><P
|
||||
>You're set, joe, john and mary are domain administrators !</P
|
||||
><P
|
||||
>Like the Domain Admins group, you can map any arbitrary Unix group to any NT
|
||||
group. You can also make any Unix group a domain group. For example, on a domain
|
||||
member machine (an NT/W2K or a samba server running winbind), you would like to
|
||||
give access to a certain directory to some users who are member of a group on
|
||||
your samba PDC. Flag that group as a domain group by running:</P
|
||||
><P
|
||||
><KBD
|
||||
CLASS="USERINPUT"
|
||||
>smbgroupedit -a unixgroup -td</KBD
|
||||
></P
|
||||
><P
|
||||
>You can list the various groups in the mapping database like this</P
|
||||
><P
|
||||
><KBD
|
||||
CLASS="USERINPUT"
|
||||
>smbgroupedit -v</KBD
|
||||
></P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="NAVFOOTER"
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"><TABLE
|
||||
SUMMARY="Footer navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="unix-permissions.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="samba-howto-collection.html"
|
||||
ACCESSKEY="H"
|
||||
>Home</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="printing.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
>UNIX Permission Bits and Windows NT Access Control Lists</TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="optional.html"
|
||||
ACCESSKEY="U"
|
||||
>Up</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
>Printing Support</TD
|
||||
></TR
|
||||
></TABLE
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
'Administrator' group, 'joe' has exactly the same rights as 'Administrator'.
|
||||
</p><p>
|
||||
When a NT/W2K machine is joined to a domain, the "Domain Adminis" group of the
|
||||
PDC is added to the local 'Administrators' group of the workstation. Every
|
||||
member of the 'Domain Administrators' group 'inherit' the
|
||||
rights of the local 'Administrators' group when logging on the workstation.
|
||||
</p><p>
|
||||
The following steps describe how to make samba PDC users members of the
|
||||
'Domain Admins' group?
|
||||
</p><div class="orderedlist"><ol type="1"><li><p>create a unix group (usually in <tt>/etc/group</tt>),
|
||||
let's call it domadm</p></li><li><p>add to this group the users that must be Administrators. For example
|
||||
if you want joe,john and mary, your entry in <tt>/etc/group</tt> will
|
||||
look like:</p><pre class="programlisting">
|
||||
domadm:x:502:joe,john,mary
|
||||
</pre></li><li><p>Map this domadm group to the "Domain Admins" group
|
||||
by running the command:</p><p><tt>root# </tt><b><tt>net groupmap add ntgroup="Domain Admins" unixgroup=domadm</tt></b></p><p>The quotes around "Domain Admins" are necessary due to the space in the group name. Also make
|
||||
sure to leave no whitespace surrounding the equal character (=).</p></li></ol></div><p>Now joe, john and mary are domain administrators!</p><p>
|
||||
It is possible to map any arbitrary UNIX group to any Windows NT
|
||||
group as well as making any UNIX group a Windows domain group.
|
||||
For example, if you wanted to include a UNIX group (e.g. acct) in a ACL on a
|
||||
local file or printer on a domain member machine, you would flag
|
||||
that group as a domain group by running the following on the Samba PDC:
|
||||
</p><p><tt>root# </tt><b><tt>net groupmap add rid=1000 ntgroup="Accounting" unixgroup=acct</tt></b></p><p>Be aware that the rid parmeter is a unsigned 32 bit integer that should
|
||||
normally start at 1000. However, this rid must not overlap with any RID assigned
|
||||
to a user. Verifying this is done differently depending on on the passdb backend
|
||||
you are using. Future versions of the tools may perform the verification automatically,
|
||||
but for now the burden in on you.</p><p>You can list the various groups in the mapping database by executing
|
||||
<b>net groupmap list</b>. Here is an example:</p><pre class="programlisting"><tt>root# </tt>net groupmap list
|
||||
System Administrators (S-1-5-21-2547222302-1596225915-2414751004-1002) -> sysadmin
|
||||
Domain Admins (S-1-5-21-2547222302-1596225915-2414751004-512) -> domadmin
|
||||
Domain Users (S-1-5-21-2547222302-1596225915-2414751004-513) -> domuser
|
||||
Domain Guests (S-1-5-21-2547222302-1596225915-2414751004-514) -> domguest
|
||||
</pre><p>For complete details on <b>net groupmap</b>, refer to the
|
||||
net(8) man page.</p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="unix-permissions.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="printing.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 11. UNIX Permission Bits and Windows NT Access Control Lists </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 13. Printing Support</td></tr></table></div></body></html>
|
||||
|
||||
@ -1,629 +1,75 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>How to Install and Test SAMBA</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
||||
REL="HOME"
|
||||
TITLE="SAMBA Project Documentation"
|
||||
HREF="samba-howto-collection.html"><LINK
|
||||
REL="UP"
|
||||
TITLE="General installation"
|
||||
HREF="introduction.html"><LINK
|
||||
REL="PREVIOUS"
|
||||
TITLE="Introduction to Samba"
|
||||
HREF="introsmb.html"><LINK
|
||||
REL="NEXT"
|
||||
TITLE="Quick Cross Subnet Browsing / Cross Workgroup Browsing guide"
|
||||
HREF="browsing-quick.html"></HEAD
|
||||
><BODY
|
||||
CLASS="CHAPTER"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><DIV
|
||||
CLASS="NAVHEADER"
|
||||
><TABLE
|
||||
SUMMARY="Header navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TH
|
||||
COLSPAN="3"
|
||||
ALIGN="center"
|
||||
>SAMBA Project Documentation</TH
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="left"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="introsmb.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="80%"
|
||||
ALIGN="center"
|
||||
VALIGN="bottom"
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="right"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="browsing-quick.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
></TABLE
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"></DIV
|
||||
><DIV
|
||||
CLASS="CHAPTER"
|
||||
><H1
|
||||
><A
|
||||
NAME="INSTALL"
|
||||
></A
|
||||
>Chapter 2. How to Install and Test SAMBA</H1
|
||||
><DIV
|
||||
CLASS="TOC"
|
||||
><DL
|
||||
><DT
|
||||
><B
|
||||
>Table of Contents</B
|
||||
></DT
|
||||
><DT
|
||||
>2.1. <A
|
||||
HREF="install.html#AEN187"
|
||||
>Obtaining and installing samba</A
|
||||
></DT
|
||||
><DT
|
||||
>2.2. <A
|
||||
HREF="install.html#AEN193"
|
||||
>Configuring samba</A
|
||||
></DT
|
||||
><DD
|
||||
><DL
|
||||
><DT
|
||||
>2.2.1. <A
|
||||
HREF="install.html#AEN198"
|
||||
>Editing the <TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf</TT
|
||||
> file</A
|
||||
></DT
|
||||
><DT
|
||||
>2.2.2. <A
|
||||
HREF="install.html#AEN223"
|
||||
>SWAT</A
|
||||
></DT
|
||||
></DL
|
||||
></DD
|
||||
><DT
|
||||
>2.3. <A
|
||||
HREF="install.html#AEN229"
|
||||
>Try listing the shares available on your
|
||||
server</A
|
||||
></DT
|
||||
><DT
|
||||
>2.4. <A
|
||||
HREF="install.html#AEN238"
|
||||
>Try connecting with the unix client</A
|
||||
></DT
|
||||
><DT
|
||||
>2.5. <A
|
||||
HREF="install.html#AEN259"
|
||||
>Try connecting from a DOS, WfWg, Win9x, WinNT,
|
||||
Win2k, OS/2, etc... client</A
|
||||
></DT
|
||||
><DT
|
||||
>2.6. <A
|
||||
HREF="install.html#AEN272"
|
||||
>What If Things Don't Work?</A
|
||||
></DT
|
||||
><DD
|
||||
><DL
|
||||
><DT
|
||||
>2.6.1. <A
|
||||
HREF="install.html#AEN277"
|
||||
>Scope IDs</A
|
||||
></DT
|
||||
><DT
|
||||
>2.6.2. <A
|
||||
HREF="install.html#AEN280"
|
||||
>Locking</A
|
||||
></DT
|
||||
></DL
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN187"
|
||||
>2.1. Obtaining and installing samba</A
|
||||
></H1
|
||||
><P
|
||||
>Binary packages of samba are included in almost any Linux or
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 2. How to Install and Test SAMBA</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="introduction.html" title="Part I. General Installation"><link rel="previous" href="IntroSMB.html" title="Chapter 1. Introduction to Samba"><link rel="next" href="type.html" title="Part II. Server Configuration Basics"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 2. How to Install and Test SAMBA</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="IntroSMB.html">Prev</a> </td><th width="60%" align="center">Part I. General Installation</th><td width="20%" align="right"> <a accesskey="n" href="type.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="install"></a>Chapter 2. How to Install and Test SAMBA</h2></div><div><div class="author"><h3 class="author">Andrew Tridgell</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:tridge@samba.org">tridge@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">Karl Auer</h3></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="install.html#id2812103">Obtaining and installing samba</a></dt><dt><a href="install.html#id2812254">Configuring samba</a></dt><dd><dl><dt><a href="install.html#id2812000">Editing the smb.conf file</a></dt><dt><a href="install.html#id2875811">SWAT</a></dt></dl></dd><dt><a href="install.html#id2875850">Try listing the shares available on your
|
||||
server</a></dt><dt><a href="install.html#id2875900">Try connecting with the unix client</a></dt><dt><a href="install.html#id2876004">Try connecting from a DOS, WfWg, Win9x, WinNT,
|
||||
Win2k, OS/2, etc... client</a></dt><dt><a href="install.html#id2876065">What If Things Don't Work?</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2812103"></a>Obtaining and installing samba</h2></div></div><p>Binary packages of samba are included in almost any Linux or
|
||||
Unix distribution. There are also some packages available at
|
||||
<A
|
||||
HREF="http://samba.org/"
|
||||
TARGET="_top"
|
||||
>the samba homepage</A
|
||||
>.
|
||||
</P
|
||||
><P
|
||||
>If you need to compile samba from source, check the
|
||||
<A
|
||||
HREF="compiling.html"
|
||||
>appropriate appendix chapter</A
|
||||
>.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN193"
|
||||
>2.2. Configuring samba</A
|
||||
></H1
|
||||
><P
|
||||
>Samba's configuration is stored in the smb.conf file,
|
||||
that usually resides in <TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/samba/smb.conf</TT
|
||||
>
|
||||
or <TT
|
||||
CLASS="FILENAME"
|
||||
>/usr/local/samba/lib/smb.conf</TT
|
||||
>. You can either
|
||||
<a href="http://samba.org/" target="_top">the samba homepage</a>.
|
||||
</p><p>If you need to compile samba from source, check the
|
||||
<a href="compiling.html" title="Chapter 30. How to compile SAMBA">appropriate appendix chapter</a>.</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2812254"></a>Configuring samba</h2></div></div><p>Samba's configuration is stored in the smb.conf file,
|
||||
that usually resides in <tt>/etc/samba/smb.conf</tt>
|
||||
or <tt>/usr/local/samba/lib/smb.conf</tt>. You can either
|
||||
edit this file yourself or do it using one of the many graphical
|
||||
tools that are available, such as the web-based interface swat, that
|
||||
is included with samba.</P
|
||||
><DIV
|
||||
CLASS="SECT2"
|
||||
><H2
|
||||
CLASS="SECT2"
|
||||
><A
|
||||
NAME="AEN198"
|
||||
>2.2.1. Editing the <TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf</TT
|
||||
> file</A
|
||||
></H2
|
||||
><P
|
||||
>There are sample configuration files in the examples
|
||||
is included with samba.</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2812000"></a>Editing the <tt>smb.conf</tt> file</h3></div></div><p>There are sample configuration files in the examples
|
||||
subdirectory in the distribution. I suggest you read them
|
||||
carefully so you can see how the options go together in
|
||||
practice. See the man page for all the options.</P
|
||||
><P
|
||||
>The simplest useful configuration file would be
|
||||
something like this:</P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
>[global]
|
||||
practice. See the man page for all the options.</p><p>The simplest useful configuration file would be
|
||||
something like this:</p><pre class="programlisting">
|
||||
[global]
|
||||
workgroup = MYGROUP
|
||||
|
||||
[homes]
|
||||
guest ok = no
|
||||
read only = no
|
||||
</PRE
|
||||
></P
|
||||
><P
|
||||
>which would allow connections by anyone with an
|
||||
</pre><p>which would allow connections by anyone with an
|
||||
account on the server, using either their login name or
|
||||
"<B
|
||||
CLASS="COMMAND"
|
||||
>homes</B
|
||||
>" as the service name. (Note that I also set the
|
||||
workgroup that Samba is part of. See BROWSING.txt for details)</P
|
||||
><P
|
||||
>Make sure you put the <TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf</TT
|
||||
> file in the same place
|
||||
you specified in the<TT
|
||||
CLASS="FILENAME"
|
||||
>Makefile</TT
|
||||
> (the default is to
|
||||
look for it in <TT
|
||||
CLASS="FILENAME"
|
||||
>/usr/local/samba/lib/</TT
|
||||
>).</P
|
||||
><P
|
||||
>For more information about security settings for the
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>[homes]</B
|
||||
> share please refer to the chapter
|
||||
<A
|
||||
HREF="securing-samba.html"
|
||||
>Securing Samba</A
|
||||
>.</P
|
||||
><DIV
|
||||
CLASS="SECT3"
|
||||
><H3
|
||||
CLASS="SECT3"
|
||||
><A
|
||||
NAME="AEN214"
|
||||
>2.2.1.1. Test your config file with
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>testparm</B
|
||||
></A
|
||||
></H3
|
||||
><P
|
||||
>It's important that you test the validity of your
|
||||
<TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf</TT
|
||||
> file using the <SPAN
|
||||
CLASS="APPLICATION"
|
||||
>testparm</SPAN
|
||||
> program.
|
||||
"<b>homes</b>" as the service name. (Note that I also set the
|
||||
workgroup that Samba is part of. See BROWSING.txt for details)</p><p>Make sure you put the <tt>smb.conf</tt> file in the same place
|
||||
you specified in the<tt>Makefile</tt> (the default is to
|
||||
look for it in <tt>/usr/local/samba/lib/</tt>).</p><p>For more information about security settings for the
|
||||
<b>[homes]</b> share please refer to the chapter
|
||||
<a href="securing-samba.html" title="Chapter 24. Securing Samba">Securing Samba</a>.</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2875758"></a>Test your config file with
|
||||
<b>testparm</b></h4></div></div><p>It's important that you test the validity of your
|
||||
<tt>smb.conf</tt> file using the testparm program.
|
||||
If testparm runs OK then it will list the loaded services. If
|
||||
not it will give an error message.</P
|
||||
><P
|
||||
>Make sure it runs OK and that the services look
|
||||
reasonable before proceeding. </P
|
||||
><P
|
||||
>Always run testparm again when you change
|
||||
<TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf</TT
|
||||
>!</P
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT2"
|
||||
><H2
|
||||
CLASS="SECT2"
|
||||
><A
|
||||
NAME="AEN223"
|
||||
>2.2.2. SWAT</A
|
||||
></H2
|
||||
><P
|
||||
> SWAT is a web-based interface that helps you configure samba.
|
||||
not it will give an error message.</p><p>Make sure it runs OK and that the services look
|
||||
reasonable before proceeding. </p><p>Always run testparm again when you change
|
||||
<tt>smb.conf</tt>!</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2875811"></a>SWAT</h3></div></div><p>
|
||||
SWAT is a web-based interface that helps you configure samba.
|
||||
SWAT might not be available in the samba package on your platform,
|
||||
but in a seperate package. Please read the swat manpage
|
||||
but in a separate package. Please read the swat manpage
|
||||
on compiling, installing and configuring swat from source.
|
||||
</P
|
||||
><P
|
||||
>To launch SWAT just run your favorite web browser and
|
||||
point it at "http://localhost:901/". Replace <VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>localhost</VAR
|
||||
> with the name of the computer you are running samba on if you
|
||||
are running samba on a different computer then your browser.</P
|
||||
><P
|
||||
>Note that you can attach to SWAT from any IP connected
|
||||
</p><p>To launch SWAT just run your favorite web browser and
|
||||
point it at "http://localhost:901/". Replace <i><tt>localhost</tt></i> with the name of the computer you are running samba on if you
|
||||
are running samba on a different computer than your browser.</p><p>Note that you can attach to SWAT 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. </P
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN229"
|
||||
>2.3. Try listing the shares available on your
|
||||
server</A
|
||||
></H1
|
||||
><P
|
||||
><SAMP
|
||||
CLASS="PROMPT"
|
||||
>$ </SAMP
|
||||
><KBD
|
||||
CLASS="USERINPUT"
|
||||
>smbclient -L
|
||||
<VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>yourhostname</VAR
|
||||
></KBD
|
||||
></P
|
||||
><P
|
||||
>You should get back a list of shares available on
|
||||
in the clear over the wire. </p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2875850"></a>Try listing the shares available on your
|
||||
server</h2></div></div><p><tt>$ </tt><b><tt>smbclient -L
|
||||
<i><tt>yourhostname</tt></i></tt></b></p><p>You should get back a list of shares available on
|
||||
your server. If you don't then something is incorrectly setup.
|
||||
Note that this method can also be used to see what shares
|
||||
are available on other LanManager clients (such as WfWg).</P
|
||||
><P
|
||||
>If you choose user level security then you may find
|
||||
are available on other LanManager clients (such as WfWg).</p><p>If you choose user level security then you may find
|
||||
that Samba requests a password before it will list the shares.
|
||||
See the <B
|
||||
CLASS="COMMAND"
|
||||
>smbclient</B
|
||||
> man page for details. (you
|
||||
See the <b>smbclient</b> man page for details. (you
|
||||
can force it to list the shares without a password by
|
||||
adding the option -U% to the command line. This will not work
|
||||
with non-Samba servers)</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN238"
|
||||
>2.4. Try connecting with the unix client</A
|
||||
></H1
|
||||
><P
|
||||
><SAMP
|
||||
CLASS="PROMPT"
|
||||
>$ </SAMP
|
||||
><KBD
|
||||
CLASS="USERINPUT"
|
||||
>smbclient <VAR
|
||||
CLASS="REPLACEABLE"
|
||||
> //yourhostname/aservice</VAR
|
||||
></KBD
|
||||
></P
|
||||
><P
|
||||
>Typically the <VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>yourhostname</VAR
|
||||
>
|
||||
would be the name of the host where you installed <SPAN
|
||||
CLASS="APPLICATION"
|
||||
>smbd</SPAN
|
||||
>.
|
||||
The <VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>aservice</VAR
|
||||
> is
|
||||
any service you have defined in the <TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf</TT
|
||||
>
|
||||
file. Try your user name if you just have a <B
|
||||
CLASS="COMMAND"
|
||||
>[homes]</B
|
||||
>
|
||||
with non-Samba servers)</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2875900"></a>Try connecting with the unix client</h2></div></div><p><tt>$ </tt><b><tt>smbclient <i><tt>
|
||||
//yourhostname/aservice</tt></i></tt></b></p><p>Typically the <i><tt>yourhostname</tt></i>
|
||||
would be the name of the host where you installed smbd.
|
||||
The <i><tt>aservice</tt></i> is
|
||||
any service you have defined in the <tt>smb.conf</tt>
|
||||
file. Try your user name if you just have a <b>[homes]</b>
|
||||
section
|
||||
in <TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf</TT
|
||||
>.</P
|
||||
><P
|
||||
>For example if your unix host is <VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>bambi</VAR
|
||||
>
|
||||
and your login name is <VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>fred</VAR
|
||||
> you would type:</P
|
||||
><P
|
||||
><SAMP
|
||||
CLASS="PROMPT"
|
||||
>$ </SAMP
|
||||
><KBD
|
||||
CLASS="USERINPUT"
|
||||
>smbclient //<VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>bambi</VAR
|
||||
>/<VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>fred</VAR
|
||||
>
|
||||
</KBD
|
||||
></P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN259"
|
||||
>2.5. Try connecting from a DOS, WfWg, Win9x, WinNT,
|
||||
Win2k, OS/2, etc... client</A
|
||||
></H1
|
||||
><P
|
||||
>Try mounting disks. eg:</P
|
||||
><P
|
||||
><SAMP
|
||||
CLASS="PROMPT"
|
||||
>C:\WINDOWS\> </SAMP
|
||||
><KBD
|
||||
CLASS="USERINPUT"
|
||||
>net use d: \\servername\service
|
||||
</KBD
|
||||
></P
|
||||
><P
|
||||
>Try printing. eg:</P
|
||||
><P
|
||||
><SAMP
|
||||
CLASS="PROMPT"
|
||||
>C:\WINDOWS\> </SAMP
|
||||
><KBD
|
||||
CLASS="USERINPUT"
|
||||
>net use lpt1:
|
||||
\\servername\spoolservice</KBD
|
||||
></P
|
||||
><P
|
||||
><SAMP
|
||||
CLASS="PROMPT"
|
||||
>C:\WINDOWS\> </SAMP
|
||||
><KBD
|
||||
CLASS="USERINPUT"
|
||||
>print filename
|
||||
</KBD
|
||||
></P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN272"
|
||||
>2.6. What If Things Don't Work?</A
|
||||
></H1
|
||||
><P
|
||||
>Then you might read the file chapter
|
||||
<A
|
||||
HREF="diagnosis.html"
|
||||
>Diagnosis</A
|
||||
> and the
|
||||
in <tt>smb.conf</tt>.</p><p>For example if your unix host is <i><tt>bambi</tt></i>
|
||||
and your login name is <i><tt>fred</tt></i> you would type:</p><p><tt>$ </tt><b><tt>smbclient //<i><tt>bambi</tt></i>/<i><tt>fred</tt></i>
|
||||
</tt></b></p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2876004"></a>Try connecting from a DOS, WfWg, Win9x, WinNT,
|
||||
Win2k, OS/2, etc... client</h2></div></div><p>Try mounting disks. eg:</p><p><tt>C:\WINDOWS\> </tt><b><tt>net use d: \\servername\service
|
||||
</tt></b></p><p>Try printing. eg:</p><p><tt>C:\WINDOWS\> </tt><b><tt>net use lpt1:
|
||||
\\servername\spoolservice</tt></b></p><p><tt>C:\WINDOWS\> </tt><b><tt>print filename
|
||||
</tt></b></p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2876065"></a>What If Things Don't Work?</h2></div></div><p>Then you might read the file chapter
|
||||
<a href="diagnosis.html" title="Chapter 27. The samba checklist">Diagnosis</a> and the
|
||||
FAQ. If you are still stuck then try to follow
|
||||
the <A
|
||||
HREF="problems.html"
|
||||
>Analysing and Solving Problems chapter</A
|
||||
>
|
||||
the <a href="problems.html" title="Chapter 28. Analysing and solving samba problems">Analysing and Solving Problems chapter</a>
|
||||
Samba has been successfully installed at thousands of sites worldwide,
|
||||
so maybe someone else has hit your problem and has overcome it. </P
|
||||
><DIV
|
||||
CLASS="SECT2"
|
||||
><H2
|
||||
CLASS="SECT2"
|
||||
><A
|
||||
NAME="AEN277"
|
||||
>2.6.1. Scope IDs</A
|
||||
></H2
|
||||
><P
|
||||
>By default Samba uses a blank scope ID. This means
|
||||
all your windows boxes must also have a blank scope ID.
|
||||
If you really want to use a non-blank scope ID then you will
|
||||
need to use the 'netbios scope' smb.conf option.
|
||||
All your PCs will need to have the same setting for
|
||||
this to work. I do not recommend scope IDs.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT2"
|
||||
><H2
|
||||
CLASS="SECT2"
|
||||
><A
|
||||
NAME="AEN280"
|
||||
>2.6.2. Locking</A
|
||||
></H2
|
||||
><P
|
||||
>One area which sometimes causes trouble is locking.</P
|
||||
><P
|
||||
>There are two types of locking which need to be
|
||||
performed by a SMB server. The first is "record locking"
|
||||
which allows a client to lock a range of bytes in a open file.
|
||||
The second is the "deny modes" that are specified when a file
|
||||
is open.</P
|
||||
><P
|
||||
>Record locking semantics under Unix is very
|
||||
different from record locking under Windows. Versions
|
||||
of Samba before 2.2 have tried to use the native
|
||||
fcntl() unix system call to implement proper record
|
||||
locking between different Samba clients. This can not
|
||||
be fully correct due to several reasons. The simplest
|
||||
is the fact that a Windows client is allowed to lock a
|
||||
byte range up to 2^32 or 2^64, depending on the client
|
||||
OS. The unix locking only supports byte ranges up to
|
||||
2^31. So it is not possible to correctly satisfy a
|
||||
lock request above 2^31. There are many more
|
||||
differences, too many to be listed here.</P
|
||||
><P
|
||||
>Samba 2.2 and above implements record locking
|
||||
completely independent of the underlying unix
|
||||
system. If a byte range lock that the client requests
|
||||
happens to fall into the range 0-2^31, Samba hands
|
||||
this request down to the Unix system. All other locks
|
||||
can not be seen by unix anyway.</P
|
||||
><P
|
||||
>Strictly a SMB server should check for locks before
|
||||
every read and write call on a file. Unfortunately with the
|
||||
way fcntl() works this can be slow and may overstress the
|
||||
rpc.lockd. It is also almost always unnecessary as clients
|
||||
are supposed to independently make locking calls before reads
|
||||
and writes anyway if locking is important to them. By default
|
||||
Samba only makes locking calls when explicitly asked
|
||||
to by a client, but if you set "strict locking = yes" then it will
|
||||
make lock checking calls on every read and write. </P
|
||||
><P
|
||||
>You can also disable by range locking completely
|
||||
using "locking = no". This is useful for those shares that
|
||||
don't support locking or don't need it (such as cdroms). In
|
||||
this case Samba fakes the return codes of locking calls to
|
||||
tell clients that everything is OK.</P
|
||||
><P
|
||||
>The second class of locking is the "deny modes". These
|
||||
are set by an application when it opens a file to determine
|
||||
what types of access should be allowed simultaneously with
|
||||
its open. A client may ask for DENY_NONE, DENY_READ, DENY_WRITE
|
||||
or DENY_ALL. There are also special compatibility modes called
|
||||
DENY_FCB and DENY_DOS.</P
|
||||
></DIV
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="NAVFOOTER"
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"><TABLE
|
||||
SUMMARY="Footer navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="introsmb.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="samba-howto-collection.html"
|
||||
ACCESSKEY="H"
|
||||
>Home</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="browsing-quick.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
>Introduction to Samba</TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="introduction.html"
|
||||
ACCESSKEY="U"
|
||||
>Up</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</TD
|
||||
></TR
|
||||
></TABLE
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
so maybe someone else has hit your problem and has overcome it. </p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="IntroSMB.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="introduction.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="type.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 1. Introduction to Samba </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Part II. Server Configuration Basics</td></tr></table></div></body></html>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -1,152 +1,6 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>General installation</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
||||
REL="HOME"
|
||||
TITLE="SAMBA Project Documentation"
|
||||
HREF="samba-howto-collection.html"><LINK
|
||||
REL="PREVIOUS"
|
||||
TITLE="SAMBA Project Documentation"
|
||||
HREF="samba-howto-collection.html"><LINK
|
||||
REL="NEXT"
|
||||
TITLE="Introduction to Samba"
|
||||
HREF="introsmb.html"></HEAD
|
||||
><BODY
|
||||
CLASS="PART"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><DIV
|
||||
CLASS="NAVHEADER"
|
||||
><TABLE
|
||||
SUMMARY="Header navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TH
|
||||
COLSPAN="3"
|
||||
ALIGN="center"
|
||||
>SAMBA Project Documentation</TH
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="left"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="samba-howto-collection.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="80%"
|
||||
ALIGN="center"
|
||||
VALIGN="bottom"
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="right"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="introsmb.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
></TABLE
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"></DIV
|
||||
><DIV
|
||||
CLASS="PART"
|
||||
><A
|
||||
NAME="INTRODUCTION"
|
||||
></A
|
||||
><DIV
|
||||
CLASS="TITLEPAGE"
|
||||
><H1
|
||||
CLASS="TITLE"
|
||||
>I. General installation</H1
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="PARTINTRO"
|
||||
><A
|
||||
NAME="AEN44"
|
||||
></A
|
||||
><H1
|
||||
>Introduction</H1
|
||||
><P
|
||||
>This part contains general info on how to install samba
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part I. General Installation</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="index.html" title="SAMBA Project Documentation"><link rel="previous" href="index.html" title="SAMBA Project Documentation"><link rel="next" href="IntroSMB.html" title="Chapter 1. Introduction to Samba"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part I. General Installation</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="index.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="IntroSMB.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><h1 class="title"><a name="introduction"></a>General Installation</h1></div></div><div class="partintro" lang="en"><div><div><h1 class="title"><a name="id2861627"></a>Preparing Samba for Configuration</h1></div></div><p>This section of the Samba-HOWTO-Collection contains general info on how to install samba
|
||||
and how to configure the parts of samba you will most likely need.
|
||||
PLEASE read this.</P
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="NAVFOOTER"
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"><TABLE
|
||||
SUMMARY="Footer navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="samba-howto-collection.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="samba-howto-collection.html"
|
||||
ACCESSKEY="H"
|
||||
>Home</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="introsmb.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
>SAMBA Project Documentation</TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
> </TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
>Introduction to Samba</TD
|
||||
></TR
|
||||
></TABLE
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
PLEASE read this.</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt>1. <a href="IntroSMB.html">Introduction to Samba</a></dt><dd><dl><dt><a href="IntroSMB.html#id2810945">Background</a></dt><dt><a href="IntroSMB.html#id2811002">Terminology</a></dt><dt><a href="IntroSMB.html#id2811109">Related Projects</a></dt><dt><a href="IntroSMB.html#id2810650">SMB Methodology</a></dt><dt><a href="IntroSMB.html#id2807791">Additional Resources</a></dt><dt><a href="IntroSMB.html#id2810803">Epilogue</a></dt><dt><a href="IntroSMB.html#id2810879">Miscellaneous</a></dt></dl></dd><dt>2. <a href="install.html">How to Install and Test SAMBA</a></dt><dd><dl><dt><a href="install.html#id2812103">Obtaining and installing samba</a></dt><dt><a href="install.html#id2812254">Configuring samba</a></dt><dd><dl><dt><a href="install.html#id2812000">Editing the smb.conf file</a></dt><dt><a href="install.html#id2875811">SWAT</a></dt></dl></dd><dt><a href="install.html#id2875850">Try listing the shares available on your
|
||||
server</a></dt><dt><a href="install.html#id2875900">Try connecting with the unix client</a></dt><dt><a href="install.html#id2876004">Try connecting from a DOS, WfWg, Win9x, WinNT,
|
||||
Win2k, OS/2, etc... client</a></dt><dt><a href="install.html#id2876065">What If Things Don't Work?</a></dt></dl></dd></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="index.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="index.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="IntroSMB.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">SAMBA Project Documentation </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 1. Introduction to Samba</td></tr></table></div></body></html>
|
||||
|
||||
@ -1,212 +1,37 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>lmhosts</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="LMHOSTS.5"
|
||||
></A
|
||||
>lmhosts</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>lmhosts -- The Samba NetBIOS hosts file</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>lmhosts</TT
|
||||
> is the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
> NetBIOS name to IP address mapping file.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN14"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
>This file is part of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
> suite.</P
|
||||
><P
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>lmhosts</TT
|
||||
> is the <SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>Samba
|
||||
</I
|
||||
></SPAN
|
||||
> NetBIOS name to IP address mapping file. It
|
||||
is very similar to the <TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/hosts</TT
|
||||
> file
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>lmhosts</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="lmhosts.5"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>lmhosts — The Samba NetBIOS hosts file</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><p><tt>lmhosts</tt> is the <a href="Samba.7.html">Samba(7)</a> NetBIOS name to IP address mapping file.</p></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This file is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><tt>lmhosts</tt> is the <span class="emphasis"><em>Samba
|
||||
</em></span> NetBIOS name to IP address mapping file. It
|
||||
is very similar to the <tt>/etc/hosts</tt> file
|
||||
format, except that the hostname component must correspond
|
||||
to the NetBIOS naming format.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN24"
|
||||
></A
|
||||
><H2
|
||||
>FILE FORMAT</H2
|
||||
><P
|
||||
>It is an ASCII file containing one line for NetBIOS name.
|
||||
to the NetBIOS naming format.</p></div><div class="refsect1" lang="en"><h2>FILE FORMAT</h2><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
|
||||
><P
|
||||
></P
|
||||
><UL
|
||||
><LI
|
||||
><P
|
||||
>IP Address - in dotted decimal format.</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>NetBIOS Name - This name format is a
|
||||
in the lmhosts file contains the following information:</p><div class="itemizedlist"><ul type="disc"><li><p>IP Address - in dotted decimal format.</p></li><li><p>NetBIOS Name - This name format is a
|
||||
maximum fifteen character host name, with an optional
|
||||
trailing '#' character followed by the NetBIOS name type
|
||||
as two hexadecimal digits.</P
|
||||
><P
|
||||
>If the trailing '#' is omitted then the given IP
|
||||
as two hexadecimal digits.</p><p>If the trailing '#' 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
|
||||
></LI
|
||||
></UL
|
||||
><P
|
||||
>An example follows:</P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
>#
|
||||
name, whatever the NetBIOS name type in the lookup.</p></li></ul></div><p>An example follows:</p><pre class="programlisting">
|
||||
#
|
||||
# Sample Samba lmhosts file.
|
||||
#
|
||||
192.9.200.1 TESTPC
|
||||
192.9.200.20 NTSERVER#20
|
||||
192.9.200.21 SAMBASERVER
|
||||
</PRE
|
||||
><P
|
||||
>Contains three IP to NetBIOS name mappings. The first
|
||||
and third will be returned for any queries for the names "TESTPC"
|
||||
and "SAMBASERVER" respectively, whatever the type component of
|
||||
the NetBIOS name requested.</P
|
||||
><P
|
||||
>The second mapping will be returned only when the "0x20" name
|
||||
type for a name "NTSERVER" is queried. Any other name type will not
|
||||
be resolved.</P
|
||||
><P
|
||||
>The default location of the <TT
|
||||
CLASS="FILENAME"
|
||||
>lmhosts</TT
|
||||
> file
|
||||
is in the same directory as the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> file.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN42"
|
||||
></A
|
||||
><H2
|
||||
>VERSION</H2
|
||||
><P
|
||||
>This man page is correct for version 3.0 of the Samba suite.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN45"
|
||||
></A
|
||||
><H2
|
||||
>SEE ALSO</H2
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbclient</SPAN
|
||||
>(1)</SPAN
|
||||
>, <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
>, and <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbpasswd</SPAN
|
||||
>(8)</SPAN
|
||||
>
|
||||
</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN57"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>The original Samba software and related utilities
|
||||
</pre><p>Contains three IP to NetBIOS name mappings. The first
|
||||
and third will be returned for any queries for the names "TESTPC"
|
||||
and "SAMBASERVER" respectively, whatever the type component of
|
||||
the NetBIOS name requested.</p><p>The second mapping will be returned only when the "0x20" name
|
||||
type for a name "NTSERVER" is queried. Any other name type will not
|
||||
be resolved.</p><p>The default location of the <tt>lmhosts</tt> file
|
||||
is in the same directory as the <a href="smb.conf.5.html">smb.conf(5)</a> file.</p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="smbclient.1.html">smbclient(1)</a>, <a href="smb.conf.5.html">smb.conf(5)</a>, and <a href="smbpasswd.8.html">smbpasswd(8)</a>
|
||||
</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.</P
|
||||
><P
|
||||
>The original Samba man pages were written by Karl Auer.
|
||||
to the way the Linux kernel is developed.</p><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/"
|
||||
TARGET="_top"
|
||||
> ftp://ftp.icce.rug.nl/pub/unix/</A
|
||||
>) and updated for the Samba 2.0
|
||||
<a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
|
||||
ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook
|
||||
XML 4.2 was done by Alexander Bokovoy.</P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
XML 4.2 was done by Alexander Bokovoy.</p></div></div></body></html>
|
||||
|
||||
@ -1,147 +1,29 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>Hosting a Microsoft Distributed File System tree on Samba</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
||||
REL="HOME"
|
||||
TITLE="SAMBA Project Documentation"
|
||||
HREF="samba-howto-collection.html"><LINK
|
||||
REL="UP"
|
||||
TITLE="Advanced Configuration"
|
||||
HREF="optional.html"><LINK
|
||||
REL="PREVIOUS"
|
||||
TITLE="Stackable VFS modules"
|
||||
HREF="vfs.html"><LINK
|
||||
REL="NEXT"
|
||||
TITLE="Integrating MS Windows networks with Samba"
|
||||
HREF="integrate-ms-networks.html"></HEAD
|
||||
><BODY
|
||||
CLASS="CHAPTER"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><DIV
|
||||
CLASS="NAVHEADER"
|
||||
><TABLE
|
||||
SUMMARY="Header navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TH
|
||||
COLSPAN="3"
|
||||
ALIGN="center"
|
||||
>SAMBA Project Documentation</TH
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="left"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="vfs.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="80%"
|
||||
ALIGN="center"
|
||||
VALIGN="bottom"
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="right"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="integrate-ms-networks.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
></TABLE
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"></DIV
|
||||
><DIV
|
||||
CLASS="CHAPTER"
|
||||
><H1
|
||||
><A
|
||||
NAME="MSDFS"
|
||||
></A
|
||||
>Chapter 22. Hosting a Microsoft Distributed File System tree on Samba</H1
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN3695"
|
||||
>22.1. Instructions</A
|
||||
></H1
|
||||
><P
|
||||
>The Distributed File System (or Dfs) provides a means of
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 22. Hosting a Microsoft Distributed File System tree on Samba</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="previous" href="VFS.html" title="Chapter 21. Stackable VFS modules"><link rel="next" href="integrate-ms-networks.html" title="Chapter 23. Integrating MS Windows networks with Samba"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 22. Hosting a Microsoft Distributed File System tree on Samba</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="VFS.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="integrate-ms-networks.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="msdfs"></a>Chapter 22. Hosting a Microsoft Distributed File System tree on Samba</h2></div><div><div class="author"><h3 class="author">Shirish Kalele</h3><div class="affiliation"><span class="orgname">Samba Team & Veritas Software<br></span><div class="address"><p><br>
|
||||
<tt><<a href="mailto:samba@samba.org">samba@samba.org</a>></tt><br>
|
||||
</p></div></div></div></div><div><p class="pubdate">12 Jul 2000</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="msdfs.html#id2899111">Instructions</a></dt><dd><dl><dt><a href="msdfs.html#id2899858">Notes</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2899111"></a>Instructions</h2></div></div><p>The Distributed File System (or Dfs) provides a means of
|
||||
separating the logical view of files and directories that users
|
||||
see from the actual physical locations of these resources on the
|
||||
network. It allows for higher availability, smoother storage expansion,
|
||||
load balancing etc. For more information about Dfs, refer to <A
|
||||
HREF="http://www.microsoft.com/NTServer/nts/downloads/winfeatures/NTSDistrFile/AdminGuide.asp"
|
||||
TARGET="_top"
|
||||
> Microsoft documentation</A
|
||||
>. </P
|
||||
><P
|
||||
>This document explains how to host a Dfs tree on a Unix
|
||||
machine (for Dfs-aware clients to browse) using Samba.</P
|
||||
><P
|
||||
>To enable SMB-based DFS for Samba, configure it with the
|
||||
<VAR
|
||||
CLASS="PARAMETER"
|
||||
>--with-msdfs</VAR
|
||||
> option. Once built, a
|
||||
load balancing etc. For more information about Dfs, refer to <a href="http://www.microsoft.com/NTServer/nts/downloads/winfeatures/NTSDistrFile/AdminGuide.asp" target="_top">
|
||||
Microsoft documentation</a>. </p><p>This document explains how to host a Dfs tree on a Unix
|
||||
machine (for Dfs-aware clients to browse) using Samba.</p><p>To enable SMB-based DFS for Samba, configure it with the
|
||||
<i><tt>--with-msdfs</tt></i> option. Once built, a
|
||||
Samba server can be made a Dfs server by setting the global
|
||||
boolean <A
|
||||
HREF="smb.conf.5.html#HOSTMSDFS"
|
||||
TARGET="_top"
|
||||
><VAR
|
||||
CLASS="PARAMETER"
|
||||
> host msdfs</VAR
|
||||
></A
|
||||
> parameter in the <TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf
|
||||
</TT
|
||||
> file. You designate a share as a Dfs root using the share
|
||||
level boolean <A
|
||||
HREF="smb.conf.5.html#MSDFSROOT"
|
||||
TARGET="_top"
|
||||
><VAR
|
||||
CLASS="PARAMETER"
|
||||
> msdfs root</VAR
|
||||
></A
|
||||
> parameter. A Dfs root directory on
|
||||
boolean <a href="smb.conf.5.html#HOSTMSDFS" target="_top"><i><tt>
|
||||
host msdfs</tt></i></a> parameter in the <tt>smb.conf
|
||||
</tt> file. You designate a share as a Dfs root using the share
|
||||
level boolean <a href="smb.conf.5.html#MSDFSROOT" target="_top"><i><tt>
|
||||
msdfs root</tt></i></a> parameter. A Dfs root directory on
|
||||
Samba hosts Dfs links in the form of symbolic links that point
|
||||
to other servers. For example, a symbolic link
|
||||
<TT
|
||||
CLASS="FILENAME"
|
||||
>junction->msdfs:storage1\share1</TT
|
||||
> in
|
||||
<tt>junction->msdfs:storage1\share1</tt> in
|
||||
the share directory acts as the Dfs junction. When Dfs-aware
|
||||
clients attempt to access the junction link, they are redirected
|
||||
to the storage location (in this case, \\storage1\share1).</P
|
||||
><P
|
||||
>Dfs trees on Samba work with all Dfs-aware clients ranging
|
||||
from Windows 95 to 2000.</P
|
||||
><P
|
||||
>Here's an example of setting up a Dfs tree on a Samba
|
||||
server.</P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
># The smb.conf file:
|
||||
to the storage location (in this case, \\storage1\share1).</p><p>Dfs trees on Samba work with all Dfs-aware clients ranging
|
||||
from Windows 95 to 2000.</p><p>Here's an example of setting up a Dfs tree on a Samba
|
||||
server.</p><pre class="programlisting">
|
||||
# The smb.conf file:
|
||||
[global]
|
||||
netbios name = SAMBA
|
||||
host msdfs = yes
|
||||
@ -149,160 +31,21 @@ CLASS="PROGRAMLISTING"
|
||||
[dfs]
|
||||
path = /export/dfsroot
|
||||
msdfs root = yes
|
||||
</PRE
|
||||
></P
|
||||
><P
|
||||
>In the /export/dfsroot directory we set up our dfs links to
|
||||
other servers on the network.</P
|
||||
><P
|
||||
><SAMP
|
||||
CLASS="PROMPT"
|
||||
>root# </SAMP
|
||||
><KBD
|
||||
CLASS="USERINPUT"
|
||||
>cd /export/dfsroot</KBD
|
||||
></P
|
||||
><P
|
||||
><SAMP
|
||||
CLASS="PROMPT"
|
||||
>root# </SAMP
|
||||
><KBD
|
||||
CLASS="USERINPUT"
|
||||
>chown root /export/dfsroot</KBD
|
||||
></P
|
||||
><P
|
||||
><SAMP
|
||||
CLASS="PROMPT"
|
||||
>root# </SAMP
|
||||
><KBD
|
||||
CLASS="USERINPUT"
|
||||
>chmod 755 /export/dfsroot</KBD
|
||||
></P
|
||||
><P
|
||||
><SAMP
|
||||
CLASS="PROMPT"
|
||||
>root# </SAMP
|
||||
><KBD
|
||||
CLASS="USERINPUT"
|
||||
>ln -s msdfs:storageA\\shareA linka</KBD
|
||||
></P
|
||||
><P
|
||||
><SAMP
|
||||
CLASS="PROMPT"
|
||||
>root# </SAMP
|
||||
><KBD
|
||||
CLASS="USERINPUT"
|
||||
>ln -s msdfs:serverB\\share,serverC\\share linkb</KBD
|
||||
></P
|
||||
><P
|
||||
>You should set up the permissions and ownership of
|
||||
</pre><p>In the /export/dfsroot directory we set up our dfs links to
|
||||
other servers on the network.</p><p><tt>root# </tt><b><tt>cd /export/dfsroot</tt></b></p><p><tt>root# </tt><b><tt>chown root /export/dfsroot</tt></b></p><p><tt>root# </tt><b><tt>chmod 755 /export/dfsroot</tt></b></p><p><tt>root# </tt><b><tt>ln -s msdfs:storageA\\shareA linka</tt></b></p><p><tt>root# </tt><b><tt>ln -s msdfs:serverB\\share,serverC\\share linkb</tt></b></p><p>You should set up the permissions and ownership of
|
||||
the directory acting as the Dfs root such that only designated
|
||||
users can create, delete or modify the msdfs links. Also note
|
||||
that symlink names should be all lowercase. This limitation exists
|
||||
to have Samba avoid trying all the case combinations to get at
|
||||
the link name. Finally set up the symbolic links to point to the
|
||||
network shares you want, and start Samba.</P
|
||||
><P
|
||||
>Users on Dfs-aware clients can now browse the Dfs tree
|
||||
network shares you want, and start Samba.</p><p>Users on Dfs-aware clients can now browse the Dfs tree
|
||||
on the Samba server at \\samba\dfs. Accessing
|
||||
links linka or linkb (which appear as directories to the client)
|
||||
takes users directly to the appropriate shares on the network.</P
|
||||
><DIV
|
||||
CLASS="SECT2"
|
||||
><H2
|
||||
CLASS="SECT2"
|
||||
><A
|
||||
NAME="AEN3730"
|
||||
>22.1.1. Notes</A
|
||||
></H2
|
||||
><P
|
||||
></P
|
||||
><UL
|
||||
><LI
|
||||
><P
|
||||
>Windows clients need to be rebooted
|
||||
takes users directly to the appropriate shares on the network.</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2899858"></a>Notes</h3></div></div><div class="itemizedlist"><ul type="disc"><li><p>Windows clients need to be rebooted
|
||||
if a previously mounted non-dfs share is made a dfs
|
||||
root or vice versa. A better way is to introduce a
|
||||
new share and make it the dfs root.</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>Currently there's a restriction that msdfs
|
||||
symlink names should all be lowercase.</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>For security purposes, the directory
|
||||
new share and make it the dfs root.</p></li><li><p>Currently there's a restriction that msdfs
|
||||
symlink names should all be lowercase.</p></li><li><p>For security purposes, the directory
|
||||
acting as the root of the Dfs tree should have ownership
|
||||
and permissions set so that only designated users can
|
||||
modify the symbolic links in the directory.</P
|
||||
></LI
|
||||
></UL
|
||||
></DIV
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="NAVFOOTER"
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"><TABLE
|
||||
SUMMARY="Footer navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="vfs.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="samba-howto-collection.html"
|
||||
ACCESSKEY="H"
|
||||
>Home</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="integrate-ms-networks.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
>Stackable VFS modules</TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="optional.html"
|
||||
ACCESSKEY="U"
|
||||
>Up</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
>Integrating MS Windows networks with Samba</TD
|
||||
></TR
|
||||
></TABLE
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
modify the symbolic links in the directory.</p></li></ul></div></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="VFS.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="integrate-ms-networks.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 21. Stackable VFS modules </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 23. Integrating MS Windows networks with Samba</td></tr></table></div></body></html>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -1,712 +1,153 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>nmbd</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="NMBD.8"
|
||||
></A
|
||||
>nmbd</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>nmbd -- NetBIOS name server to provide NetBIOS
|
||||
over IP naming services to clients</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>nmbd</B
|
||||
> [-D] [-F] [-S] [-a] [-i] [-o] [-h] [-V] [-d <debug level>] [-H <lmhosts file>] [-l <log directory>] [-n <primary netbios name>] [-p <port number>] [-s <configuration file>]</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN25"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
>This program is part of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
> suite.</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>nmbd</B
|
||||
> is a server that understands
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>nmbd</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="nmbd.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>nmbd — NetBIOS name server to provide NetBIOS
|
||||
over IP naming services to clients</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>nmbd</tt> [-D] [-F] [-S] [-a] [-i] [-o] [-h] [-V] [-d <debug level>] [-H <lmhosts file>] [-l <log directory>] [-n <primary netbios name>] [-p <port number>] [-s <configuration file>]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This program is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>nmbd</b> is a server that understands
|
||||
and can reply to NetBIOS over IP name service requests, like
|
||||
those produced by SMB/CIFS clients such as Windows 95/98/ME,
|
||||
Windows NT, Windows 2000, Windows XP and LanManager clients. It also
|
||||
participates in the browsing protocols which make up the
|
||||
Windows "Network Neighborhood" view.</P
|
||||
><P
|
||||
>SMB/CIFS clients, when they start up, may wish to
|
||||
Windows "Network Neighborhood" view.</p><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
|
||||
><P
|
||||
>Amongst other services, <B
|
||||
CLASS="COMMAND"
|
||||
>nmbd</B
|
||||
> will
|
||||
IP number a specified host is using.</p><p>Amongst other services, <b>nmbd</b> 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
|
||||
is running on. Its "own NetBIOS name" is by
|
||||
default the primary DNS name of the host it is running on,
|
||||
but this can be overridden with the <SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>-n</I
|
||||
></SPAN
|
||||
>
|
||||
option (see OPTIONS below). Thus <B
|
||||
CLASS="COMMAND"
|
||||
>nmbd</B
|
||||
> will
|
||||
but this can be overridden with the <span class="emphasis"><em>-n</em></span>
|
||||
option (see OPTIONS below). Thus <b>nmbd</b> will
|
||||
reply to broadcast queries for its own name(s). Additional
|
||||
names for <B
|
||||
CLASS="COMMAND"
|
||||
>nmbd</B
|
||||
> to respond on can be set
|
||||
via parameters in the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> configuration file.</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>nmbd</B
|
||||
> can also be used as a WINS
|
||||
names for <b>nmbd</b> to respond on can be set
|
||||
via parameters in the <a href="smb.conf.5.html">smb.conf(5)</a> configuration file.</p><p><b>nmbd</b> 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
|
||||
><P
|
||||
>In addition, <B
|
||||
CLASS="COMMAND"
|
||||
>nmbd</B
|
||||
> can act as a WINS
|
||||
replying to queries from clients for these names.</p><p>In addition, <b>nmbd</b> can act as a WINS
|
||||
proxy, relaying broadcast queries from clients that do
|
||||
not understand how to talk the WINS protocol to a WINS
|
||||
server.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN46"
|
||||
></A
|
||||
><H2
|
||||
>OPTIONS</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>-D</DT
|
||||
><DD
|
||||
><P
|
||||
>If specified, this parameter causes
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>nmbd</B
|
||||
> to operate as a daemon. That is,
|
||||
server.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-D</span></dt><dd><p>If specified, this parameter causes
|
||||
<b>nmbd</b> to operate as a daemon. That is,
|
||||
it detaches itself and runs in the background, fielding
|
||||
requests on the appropriate port. By default, <B
|
||||
CLASS="COMMAND"
|
||||
>nmbd</B
|
||||
>
|
||||
requests on the appropriate port. By default, <b>nmbd</b>
|
||||
will operate as a daemon if launched from a command shell.
|
||||
nmbd can also be operated from the <B
|
||||
CLASS="COMMAND"
|
||||
>inetd</B
|
||||
>
|
||||
nmbd can also be operated from the <b>inetd</b>
|
||||
meta-daemon, although this is not recommended.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-F</DT
|
||||
><DD
|
||||
><P
|
||||
>If specified, this parameter causes
|
||||
the main <B
|
||||
CLASS="COMMAND"
|
||||
>nmbd</B
|
||||
> process to not daemonize,
|
||||
</p></dd><dt><span class="term">-F</span></dt><dd><p>If specified, this parameter causes
|
||||
the main <b>nmbd</b> process to not daemonize,
|
||||
i.e. double-fork and disassociate with the terminal.
|
||||
Child processes are still created as normal to service
|
||||
each connection request, but the main process does not
|
||||
exit. This operation mode is suitable for running
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>nmbd</B
|
||||
> under process supervisors such
|
||||
as <B
|
||||
CLASS="COMMAND"
|
||||
>supervise</B
|
||||
> and <B
|
||||
CLASS="COMMAND"
|
||||
>svscan</B
|
||||
>
|
||||
from Daniel J. Bernstein's <B
|
||||
CLASS="COMMAND"
|
||||
>daemontools</B
|
||||
>
|
||||
<b>nmbd</b> under process supervisors such
|
||||
as <b>supervise</b> and <b>svscan</b>
|
||||
from Daniel J. Bernstein's <b>daemontools</b>
|
||||
package, or the AIX process monitor.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-S</DT
|
||||
><DD
|
||||
><P
|
||||
>If specified, this parameter causes
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>nmbd</B
|
||||
> to log to standard output rather
|
||||
than a file.</P
|
||||
></DD
|
||||
><DT
|
||||
>-i</DT
|
||||
><DD
|
||||
><P
|
||||
>If this parameter is specified it causes the
|
||||
server to run "interactively", not as a daemon, even if the
|
||||
</p></dd><dt><span class="term">-S</span></dt><dd><p>If specified, this parameter causes
|
||||
<b>nmbd</b> to log to standard output rather
|
||||
than a file.</p></dd><dt><span class="term">-i</span></dt><dd><p>If this parameter is specified it causes the
|
||||
server to run "interactively", not as a daemon, even if the
|
||||
server is executed on the command line of a shell. Setting this
|
||||
parameter negates the implicit daemon mode when run from the
|
||||
command line. <B
|
||||
CLASS="COMMAND"
|
||||
>nmbd</B
|
||||
> also logs to standard
|
||||
output, as if the <CODE
|
||||
CLASS="CONSTANT"
|
||||
>-S</CODE
|
||||
> parameter had been
|
||||
given. </P
|
||||
></DD
|
||||
><DT
|
||||
>-h|--help</DT
|
||||
><DD
|
||||
><P
|
||||
>Print a summary of command line options.</P
|
||||
></DD
|
||||
><DT
|
||||
>-H <filename></DT
|
||||
><DD
|
||||
><P
|
||||
>NetBIOS lmhosts file. The lmhosts
|
||||
command line. <b>nmbd</b> also logs to standard
|
||||
output, as if the <tt>-S</tt> parameter had been
|
||||
given. </p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
|
||||
</p></dd><dt><span class="term">-H <filename></span></dt><dd><p>NetBIOS lmhosts file. 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"
|
||||
TARGET="_top"
|
||||
><VAR
|
||||
CLASS="PARAMETER"
|
||||
>name resolve
|
||||
order</VAR
|
||||
></A
|
||||
> described in <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> to resolve any
|
||||
resolution mechanism <a href="smb.conf.5.html#nameresolveorder" target="_top"><i><tt>name resolve
|
||||
order</tt></i></a> described in <a href="smb.conf.5.html">smb.conf(5)</a> to resolve any
|
||||
NetBIOS name queries needed by the server. Note
|
||||
that the contents of this file are <SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>NOT</I
|
||||
></SPAN
|
||||
>
|
||||
used by <B
|
||||
CLASS="COMMAND"
|
||||
>nmbd</B
|
||||
> to answer any name queries.
|
||||
that the contents of this file are <span class="emphasis"><em>NOT</em></span>
|
||||
used by <b>nmbd</b> to answer any name queries.
|
||||
Adding a line to this file affects name NetBIOS resolution
|
||||
from this host <SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>ONLY</I
|
||||
></SPAN
|
||||
>.</P
|
||||
><P
|
||||
>The default path to this file is compiled into
|
||||
from this host <span class="emphasis"><em>ONLY</em></span>.</p><p>The default path to this file is compiled into
|
||||
Samba as part of the build process. Common defaults
|
||||
are <TT
|
||||
CLASS="FILENAME"
|
||||
>/usr/local/samba/lib/lmhosts</TT
|
||||
>,
|
||||
<TT
|
||||
CLASS="FILENAME"
|
||||
>/usr/samba/lib/lmhosts</TT
|
||||
> or
|
||||
<TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/samba/lmhosts</TT
|
||||
>. See the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>lmhosts</SPAN
|
||||
>(5)</SPAN
|
||||
> man page for details on the contents of this file.</P
|
||||
></DD
|
||||
><DT
|
||||
>-V</DT
|
||||
><DD
|
||||
><P
|
||||
>Prints the version number for
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
>.</P
|
||||
></DD
|
||||
><DT
|
||||
>-s <configuration file></DT
|
||||
><DD
|
||||
><P
|
||||
>The file specified contains the
|
||||
are <tt>/usr/local/samba/lib/lmhosts</tt>,
|
||||
<tt>/usr/samba/lib/lmhosts</tt> or
|
||||
<tt>/etc/samba/lmhosts</tt>. See the <a href="lmhosts.5.html">lmhosts(5)</a> man page for details on the contents of this file.</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for
|
||||
<b>smbd</b>.</p></dd><dt><span class="term">-s <configuration file></span></dt><dd><p>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 <A
|
||||
HREF="smb.conf.5.html"
|
||||
TARGET="_top"
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf(5)</TT
|
||||
></A
|
||||
> for more information.
|
||||
to provide. See <a href="smb.conf.5.html" target="_top"><tt>
|
||||
smb.conf(5)</tt></a> for more information.
|
||||
The default configuration file name is determined at
|
||||
compile time.</P
|
||||
></DD
|
||||
><DT
|
||||
>-d|--debug=debuglevel</DT
|
||||
><DD
|
||||
><P
|
||||
><VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>debuglevel</VAR
|
||||
> is an integer
|
||||
compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
|
||||
from 0 to 10. The default value if this parameter is
|
||||
not specified is zero.</P
|
||||
><P
|
||||
>The higher this value, the more detail will be
|
||||
not specified is zero.</p><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
|
||||
><P
|
||||
>Levels above 1 will generate considerable
|
||||
information about operations carried out.</p><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
|
||||
><P
|
||||
>Note that specifying this parameter here will
|
||||
override the <A
|
||||
HREF="smb.conf.5.html#loglevel"
|
||||
TARGET="_top"
|
||||
>log
|
||||
level</A
|
||||
> parameter in the <A
|
||||
HREF="smb.conf.5.html"
|
||||
TARGET="_top"
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf(5)</TT
|
||||
></A
|
||||
> file.</P
|
||||
></DD
|
||||
><DT
|
||||
>-l|--logfile=logbasename</DT
|
||||
><DD
|
||||
><P
|
||||
>File name for log/debug files. The extension
|
||||
<CODE
|
||||
CLASS="CONSTANT"
|
||||
>".client"</CODE
|
||||
> will be appended. The log file is
|
||||
never removed by the client.</P
|
||||
></DD
|
||||
><DT
|
||||
>-p <UDP port number></DT
|
||||
><DD
|
||||
><P
|
||||
>UDP port number is a positive integer value.
|
||||
data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
|
||||
override the <a href="smb.conf.5.html#loglevel" target="_top">log
|
||||
level</a> parameter in the <a href="smb.conf.5.html" target="_top">
|
||||
<tt>smb.conf(5)</tt></a> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
|
||||
<tt>".client"</tt> will be appended. The log file is
|
||||
never removed by the client.
|
||||
</p></dd><dt><span class="term">-p <UDP port number></span></dt><dd><p>UDP port number is a positive integer value.
|
||||
This option changes the default UDP port number (normally 137)
|
||||
that <B
|
||||
CLASS="COMMAND"
|
||||
>nmbd</B
|
||||
> responds to name queries on. Don't
|
||||
that <b>nmbd</b> responds to name queries on. Don't
|
||||
use this option unless you are an expert, in which case you
|
||||
won't need help!</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN131"
|
||||
></A
|
||||
><H2
|
||||
>FILES</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/inetd.conf</TT
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>If the server is to be run by the
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>inetd</B
|
||||
> meta-daemon, this file
|
||||
won't need help!</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><tt>/etc/inetd.conf</tt></span></dt><dd><p>If the server is to be run by the
|
||||
<b>inetd</b> meta-daemon, this file
|
||||
must contain suitable startup information for the
|
||||
meta-daemon. See the <A
|
||||
HREF="install.html"
|
||||
TARGET="_top"
|
||||
>install</A
|
||||
> document
|
||||
meta-daemon. See the <a href="install.html" target="_top">install</a> document
|
||||
for details.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/rc</TT
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>or whatever initialization script your
|
||||
system uses).</P
|
||||
><P
|
||||
>If running the server as a daemon at startup,
|
||||
</p></dd><dt><span class="term"><tt>/etc/rc</tt></span></dt><dd><p>or whatever initialization script your
|
||||
system uses).</p><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 <A
|
||||
HREF="install.html"
|
||||
TARGET="_top"
|
||||
>"How to Install and Test SAMBA"</A
|
||||
> document
|
||||
for details.</P
|
||||
></DD
|
||||
><DT
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/services</TT
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>If running the server via the
|
||||
meta-daemon <B
|
||||
CLASS="COMMAND"
|
||||
>inetd</B
|
||||
>, this file
|
||||
sequence for the server. See the <a href="install.html" target="_top">"How to Install and Test SAMBA"</a> document
|
||||
for details.</p></dd><dt><span class="term"><tt>/etc/services</tt></span></dt><dd><p>If running the server via the
|
||||
meta-daemon <b>inetd</b>, 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 <A
|
||||
HREF="install.html"
|
||||
TARGET="_top"
|
||||
>"How to Install and Test SAMBA"</A
|
||||
>
|
||||
document for details.</P
|
||||
></DD
|
||||
><DT
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>/usr/local/samba/lib/smb.conf</TT
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>This is the default location of
|
||||
the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> server
|
||||
See the <a href="install.html" target="_top">"How to Install and Test SAMBA"</a>
|
||||
document for details.</p></dd><dt><span class="term"><tt>/usr/local/samba/lib/smb.conf</tt></span></dt><dd><p>This is the default location of
|
||||
the <a href="smb.conf.5.html">smb.conf(5)</a> server
|
||||
configuration file. Other common places that systems
|
||||
install this file are <TT
|
||||
CLASS="FILENAME"
|
||||
>/usr/samba/lib/smb.conf</TT
|
||||
>
|
||||
and <TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/samba/smb.conf</TT
|
||||
>.</P
|
||||
><P
|
||||
>When run as a WINS server (see the
|
||||
<A
|
||||
HREF="smb.conf.5.html#WINSSUPPORT"
|
||||
TARGET="_top"
|
||||
><CODE
|
||||
CLASS="CONSTANT"
|
||||
>wins support</CODE
|
||||
></A
|
||||
>
|
||||
parameter in the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> man page),
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>nmbd</B
|
||||
>
|
||||
will store the WINS database in the file <TT
|
||||
CLASS="FILENAME"
|
||||
>wins.dat</TT
|
||||
>
|
||||
in the <TT
|
||||
CLASS="FILENAME"
|
||||
>var/locks</TT
|
||||
> directory configured under
|
||||
wherever Samba was configured to install itself.</P
|
||||
><P
|
||||
>If <B
|
||||
CLASS="COMMAND"
|
||||
>nmbd</B
|
||||
> is acting as a <SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
> browse master</I
|
||||
></SPAN
|
||||
> (see the <A
|
||||
HREF="smb.conf.5.html#LOCALMASTER"
|
||||
TARGET="_top"
|
||||
><CODE
|
||||
CLASS="CONSTANT"
|
||||
>local master</CODE
|
||||
></A
|
||||
>
|
||||
parameter in the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> man page, <B
|
||||
CLASS="COMMAND"
|
||||
>nmbd</B
|
||||
>
|
||||
will store the browsing database in the file <TT
|
||||
CLASS="FILENAME"
|
||||
>browse.dat
|
||||
</TT
|
||||
> in the <TT
|
||||
CLASS="FILENAME"
|
||||
>var/locks</TT
|
||||
> directory
|
||||
install this file are <tt>/usr/samba/lib/smb.conf</tt>
|
||||
and <tt>/etc/samba/smb.conf</tt>.</p><p>When run as a WINS server (see the
|
||||
<a href="smb.conf.5.html#WINSSUPPORT" target="_top"><tt>wins support</tt></a>
|
||||
parameter in the <a href="smb.conf.5.html">smb.conf(5)</a> man page),
|
||||
<b>nmbd</b>
|
||||
will store the WINS database in the file <tt>wins.dat</tt>
|
||||
in the <tt>var/locks</tt> directory configured under
|
||||
wherever Samba was configured to install itself.</p><p>If <b>nmbd</b> is acting as a <span class="emphasis"><em>
|
||||
browse master</em></span> (see the <a href="smb.conf.5.html#LOCALMASTER" target="_top"><tt>local master</tt></a>
|
||||
parameter in the <a href="smb.conf.5.html">smb.conf(5)</a> man page, <b>nmbd</b>
|
||||
will store the browsing database in the file <tt>browse.dat
|
||||
</tt> in the <tt>var/locks</tt> directory
|
||||
configured under wherever Samba was configured to install itself.
|
||||
</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN185"
|
||||
></A
|
||||
><H2
|
||||
>SIGNALS</H2
|
||||
><P
|
||||
>To shut down an <B
|
||||
CLASS="COMMAND"
|
||||
>nmbd</B
|
||||
> process it is recommended
|
||||
that SIGKILL (-9) <SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>NOT</I
|
||||
></SPAN
|
||||
> be used, except as a last
|
||||
</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>SIGNALS</h2><p>To shut down an <b>nmbd</b> process it is recommended
|
||||
that SIGKILL (-9) <span class="emphasis"><em>NOT</em></span> be used, except as a last
|
||||
resort, as this may leave the name database in an inconsistent state.
|
||||
The correct way to terminate <B
|
||||
CLASS="COMMAND"
|
||||
>nmbd</B
|
||||
> is to send it
|
||||
a SIGTERM (-15) signal and wait for it to die on its own.</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>nmbd</B
|
||||
> will accept SIGHUP, which will cause
|
||||
it to dump out its namelists into the file <TT
|
||||
CLASS="FILENAME"
|
||||
>namelist.debug
|
||||
</TT
|
||||
> in the <TT
|
||||
CLASS="FILENAME"
|
||||
>/usr/local/samba/var/locks</TT
|
||||
>
|
||||
directory (or the <TT
|
||||
CLASS="FILENAME"
|
||||
>var/locks</TT
|
||||
> directory configured
|
||||
The correct way to terminate <b>nmbd</b> is to send it
|
||||
a SIGTERM (-15) signal and wait for it to die on its own.</p><p><b>nmbd</b> will accept SIGHUP, which will cause
|
||||
it to dump out its namelists into the file <tt>namelist.debug
|
||||
</tt> in the <tt>/usr/local/samba/var/locks</tt>
|
||||
directory (or the <tt>var/locks</tt> directory configured
|
||||
under wherever Samba was configured to install itself). This will also
|
||||
cause <B
|
||||
CLASS="COMMAND"
|
||||
>nmbd</B
|
||||
> to dump out its server database in
|
||||
the <TT
|
||||
CLASS="FILENAME"
|
||||
>log.nmb</TT
|
||||
> file.</P
|
||||
><P
|
||||
>The debug log level of nmbd may be raised or lowered
|
||||
using <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbcontrol</SPAN
|
||||
>(1)</SPAN
|
||||
> (SIGUSR[1|2] signals
|
||||
cause <b>nmbd</b> to dump out its server database in
|
||||
the <tt>log.nmb</tt> file.</p><p>The debug log level of nmbd may be raised or lowered
|
||||
using <a href="smbcontrol.1.html">smbcontrol(1)</a> (SIGUSR[1|2] signals
|
||||
are no longer used since Samba 2.2). This is to allow
|
||||
transient problems to be diagnosed, whilst still running
|
||||
at a normally low log level.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN202"
|
||||
></A
|
||||
><H2
|
||||
>VERSION</H2
|
||||
><P
|
||||
>This man page is correct for version 3.0 of
|
||||
the Samba suite.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN205"
|
||||
></A
|
||||
><H2
|
||||
>SEE ALSO</H2
|
||||
><P
|
||||
> <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>inetd</SPAN
|
||||
>(8)</SPAN
|
||||
>, <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbd</SPAN
|
||||
>(8)</SPAN
|
||||
>, <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
>, <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbclient</SPAN
|
||||
>(1)</SPAN
|
||||
>, <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>testparm</SPAN
|
||||
>(1)</SPAN
|
||||
>, <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>testprns</SPAN
|
||||
>(1)</SPAN
|
||||
>, and the Internet
|
||||
RFC's <TT
|
||||
CLASS="FILENAME"
|
||||
>rfc1001.txt</TT
|
||||
>, <TT
|
||||
CLASS="FILENAME"
|
||||
>rfc1002.txt</TT
|
||||
>.
|
||||
at a normally low log level.</p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of
|
||||
the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p>
|
||||
<a href="inetd.8.html">inetd(8)</a>, <a href="smbd.8.html">smbd(8)</a>, <a href="smb.conf.5.html">smb.conf(5)</a>, <a href="smbclient.1.html">smbclient(1)</a>, <a href="testparm.1.html">testparm(1)</a>, <a href="testprns.1.html">testprns(1)</a>, and the Internet
|
||||
RFC's <tt>rfc1001.txt</tt>, <tt>rfc1002.txt</tt>.
|
||||
In addition the CIFS (formerly SMB) specification is available
|
||||
as a link from the Web page <A
|
||||
HREF="http://samba.org/cifs/"
|
||||
TARGET="_top"
|
||||
>
|
||||
http://samba.org/cifs/</A
|
||||
>.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN229"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>The original Samba software and related utilities
|
||||
as a link from the Web page <a href="http://samba.org/cifs/" target="_top">
|
||||
http://samba.org/cifs/</a>.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.</P
|
||||
><P
|
||||
>The original Samba man pages were written by Karl Auer.
|
||||
to the way the Linux kernel is developed.</p><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/"
|
||||
TARGET="_top"
|
||||
> ftp://ftp.icce.rug.nl/pub/unix/</A
|
||||
>) and updated for the Samba 2.0
|
||||
excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
|
||||
ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook
|
||||
XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
|
||||
|
||||
@ -1,494 +1,107 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>nmblookup</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="NMBLOOKUP"
|
||||
></A
|
||||
>nmblookup</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>nmblookup -- NetBIOS over TCP/IP client used to lookup NetBIOS
|
||||
names</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>nmblookup</B
|
||||
> [-M] [-R] [-S] [-r] [-A] [-h] [-B <broadcast address>] [-U <unicast address>] [-d <debug level>] [-s <smb config file>] [-i <NetBIOS scope>] [-T] [-f] {name}</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN25"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
>This tool is part of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
> suite.</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>nmblookup</B
|
||||
> is used to query NetBIOS names
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>nmblookup</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="nmblookup"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>nmblookup — NetBIOS over TCP/IP client used to lookup NetBIOS
|
||||
names</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>nmblookup</tt> [-M] [-R] [-S] [-r] [-A] [-h] [-B <broadcast address>] [-U <unicast address>] [-d <debug level>] [-s <smb config file>] [-i <NetBIOS scope>] [-T] [-f] {name}</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>nmblookup</b> 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
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN33"
|
||||
></A
|
||||
><H2
|
||||
>OPTIONS</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>-M</DT
|
||||
><DD
|
||||
><P
|
||||
>Searches for a master browser by looking
|
||||
up the NetBIOS name <VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>name</VAR
|
||||
> with a
|
||||
type of <CODE
|
||||
CLASS="CONSTANT"
|
||||
>0x1d</CODE
|
||||
>. If <VAR
|
||||
CLASS="REPLACEABLE"
|
||||
> name</VAR
|
||||
> is "-" then it does a lookup on the special name
|
||||
<CODE
|
||||
CLASS="CONSTANT"
|
||||
>__MSBROWSE__</CODE
|
||||
>.</P
|
||||
></DD
|
||||
><DT
|
||||
>-R</DT
|
||||
><DD
|
||||
><P
|
||||
>Set the recursion desired bit in the packet
|
||||
are done over UDP.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-M</span></dt><dd><p>Searches for a master browser by looking
|
||||
up the NetBIOS name <i><tt>name</tt></i> with a
|
||||
type of <tt>0x1d</tt>. If <i><tt>
|
||||
name</tt></i> is "-" then it does a lookup on the special name
|
||||
<tt>__MSBROWSE__</tt>. Please note that in order to
|
||||
use the name "-", you need to make sure "-" isn't parsed as an
|
||||
argument, e.g. use :
|
||||
<b><tt>nmblookup -M -- -</tt></b>.</p></dd><dt><span class="term">-R</span></dt><dd><p>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
|
||||
></DD
|
||||
><DT
|
||||
>-S</DT
|
||||
><DD
|
||||
><P
|
||||
>Once the name query has returned an IP
|
||||
</p></dd><dt><span class="term">-S</span></dt><dd><p>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
|
||||
></DD
|
||||
><DT
|
||||
>-r</DT
|
||||
><DD
|
||||
><P
|
||||
>Try and bind to UDP port 137 to send and receive UDP
|
||||
</p></dd><dt><span class="term">-r</span></dt><dd><p>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 privilege is needed to bind to this port, and
|
||||
in addition, if the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>nmbd</SPAN
|
||||
>(8)</SPAN
|
||||
> daemon is running on this machine it also binds to this port.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-A</DT
|
||||
><DD
|
||||
><P
|
||||
>Interpret <VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>name</VAR
|
||||
> as
|
||||
an IP Address and do a node status query on this address.</P
|
||||
></DD
|
||||
><DT
|
||||
>-n <primary NetBIOS name></DT
|
||||
><DD
|
||||
><P
|
||||
>This option allows you to override
|
||||
in addition, if the <a href="nmbd.8.html">nmbd(8)</a> daemon is running on this machine it also binds to this port.
|
||||
</p></dd><dt><span class="term">-A</span></dt><dd><p>Interpret <i><tt>name</tt></i> as
|
||||
an IP Address and do a node status query on this address.</p></dd><dt><span class="term">-n <primary NetBIOS name></span></dt><dd><p>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"
|
||||
TARGET="_top"
|
||||
><VAR
|
||||
CLASS="PARAMETER"
|
||||
>NetBIOS
|
||||
name</VAR
|
||||
></A
|
||||
> parameter in the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> file. However, a command
|
||||
to setting the <a href="smb.conf.5.html#netbiosname" target="_top"><i><tt>NetBIOS
|
||||
name</tt></i></a> parameter in the <a href="smb.conf.5.html">smb.conf(5)</a> file. However, a command
|
||||
line setting will take precedence over settings in
|
||||
<SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
>.</P
|
||||
></DD
|
||||
><DT
|
||||
>-i <scope></DT
|
||||
><DD
|
||||
><P
|
||||
>This specifies a NetBIOS scope that
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>nmblookup</B
|
||||
> will use to communicate with when
|
||||
<a href="smb.conf.5.html">smb.conf(5)</a>.</p></dd><dt><span class="term">-i <scope></span></dt><dd><p>This specifies a NetBIOS scope that
|
||||
<b>nmblookup</b> 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
|
||||
<SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>very</I
|
||||
></SPAN
|
||||
> rarely used, only set this parameter
|
||||
<span class="emphasis"><em>very</em></span> rarely used, only set this parameter
|
||||
if you are the system administrator in charge of all the
|
||||
NetBIOS systems you communicate with.</P
|
||||
></DD
|
||||
><DT
|
||||
>-W|--workgroup=domain</DT
|
||||
><DD
|
||||
><P
|
||||
>Set the SMB domain of the username. This
|
||||
NetBIOS systems you communicate with.</p></dd><dt><span class="term">-W|--workgroup=domain</span></dt><dd><p>Set the SMB domain of the username. This
|
||||
overrides the default domain which is the domain defined in
|
||||
smb.conf. If the domain specified is the same as the servers
|
||||
NetBIOS name, it causes the client to log on using the servers local
|
||||
SAM (as opposed to the Domain SAM). </P
|
||||
></DD
|
||||
><DT
|
||||
>-O socket options</DT
|
||||
><DD
|
||||
><P
|
||||
>TCP socket options to set on the client
|
||||
SAM (as opposed to the Domain SAM). </p></dd><dt><span class="term">-O socket options</span></dt><dd><p>TCP socket options to set on the client
|
||||
socket. See the socket options parameter in
|
||||
the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> manual page for the list of valid
|
||||
options. </P
|
||||
></DD
|
||||
><DT
|
||||
>-h|--help</DT
|
||||
><DD
|
||||
><P
|
||||
>Print a summary of command line options.</P
|
||||
></DD
|
||||
><DT
|
||||
>-B <broadcast address></DT
|
||||
><DD
|
||||
><P
|
||||
>Send the query to the given broadcast address. Without
|
||||
the <a href="smb.conf.5.html">smb.conf(5)</a> manual page for the list of valid
|
||||
options. </p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
|
||||
</p></dd><dt><span class="term">-B <broadcast address></span></dt><dd><p>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"
|
||||
TARGET="_top"
|
||||
><VAR
|
||||
CLASS="PARAMETER"
|
||||
>interfaces</VAR
|
||||
>
|
||||
</A
|
||||
> parameter of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> file.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-U <unicast address></DT
|
||||
><DD
|
||||
><P
|
||||
>Do a unicast query to the specified address or
|
||||
host <VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>unicast address</VAR
|
||||
>. This option
|
||||
(along with the <VAR
|
||||
CLASS="PARAMETER"
|
||||
>-R</VAR
|
||||
> option) is needed to
|
||||
query a WINS server.</P
|
||||
></DD
|
||||
><DT
|
||||
>-V</DT
|
||||
><DD
|
||||
><P
|
||||
>Prints the version number for
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
>.</P
|
||||
></DD
|
||||
><DT
|
||||
>-s <configuration file></DT
|
||||
><DD
|
||||
><P
|
||||
>The file specified contains the
|
||||
either auto-detected or defined in the <a href="smb.conf.5.html#INTERFACES" target="_top"><i><tt>interfaces</tt></i>
|
||||
</a> parameter of the <a href="smb.conf.5.html">smb.conf(5)</a> file.
|
||||
</p></dd><dt><span class="term">-U <unicast address></span></dt><dd><p>Do a unicast query to the specified address or
|
||||
host <i><tt>unicast address</tt></i>. This option
|
||||
(along with the <i><tt>-R</tt></i> option) is needed to
|
||||
query a WINS server.</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for
|
||||
<b>smbd</b>.</p></dd><dt><span class="term">-s <configuration file></span></dt><dd><p>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 <A
|
||||
HREF="smb.conf.5.html"
|
||||
TARGET="_top"
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf(5)</TT
|
||||
></A
|
||||
> for more information.
|
||||
to provide. See <a href="smb.conf.5.html" target="_top"><tt>
|
||||
smb.conf(5)</tt></a> for more information.
|
||||
The default configuration file name is determined at
|
||||
compile time.</P
|
||||
></DD
|
||||
><DT
|
||||
>-d|--debug=debuglevel</DT
|
||||
><DD
|
||||
><P
|
||||
><VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>debuglevel</VAR
|
||||
> is an integer
|
||||
compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
|
||||
from 0 to 10. The default value if this parameter is
|
||||
not specified is zero.</P
|
||||
><P
|
||||
>The higher this value, the more detail will be
|
||||
not specified is zero.</p><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
|
||||
><P
|
||||
>Levels above 1 will generate considerable
|
||||
information about operations carried out.</p><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
|
||||
><P
|
||||
>Note that specifying this parameter here will
|
||||
override the <A
|
||||
HREF="smb.conf.5.html#loglevel"
|
||||
TARGET="_top"
|
||||
>log
|
||||
level</A
|
||||
> parameter in the <A
|
||||
HREF="smb.conf.5.html"
|
||||
TARGET="_top"
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf(5)</TT
|
||||
></A
|
||||
> file.</P
|
||||
></DD
|
||||
><DT
|
||||
>-l|--logfile=logbasename</DT
|
||||
><DD
|
||||
><P
|
||||
>File name for log/debug files. The extension
|
||||
<CODE
|
||||
CLASS="CONSTANT"
|
||||
>".client"</CODE
|
||||
> will be appended. The log file is
|
||||
never removed by the client.</P
|
||||
></DD
|
||||
><DT
|
||||
>-T</DT
|
||||
><DD
|
||||
><P
|
||||
>This causes any IP addresses found in the
|
||||
data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
|
||||
override the <a href="smb.conf.5.html#loglevel" target="_top">log
|
||||
level</a> parameter in the <a href="smb.conf.5.html" target="_top">
|
||||
<tt>smb.conf(5)</tt></a> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
|
||||
<tt>".client"</tt> will be appended. The log file is
|
||||
never removed by the client.
|
||||
</p></dd><dt><span class="term">-T</span></dt><dd><p>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</P
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>IP address .... NetBIOS name</I
|
||||
></SPAN
|
||||
></P
|
||||
><P
|
||||
> pair that is the normal output.</P
|
||||
></DD
|
||||
><DT
|
||||
>-f</DT
|
||||
><DD
|
||||
><P
|
||||
> Show which flags apply to the name that has been looked up. Possible
|
||||
DNS name, and printed out before each</p><p><span class="emphasis"><em>IP address .... NetBIOS name</em></span></p><p> pair that is the normal output.</p></dd><dt><span class="term">-f</span></dt><dd><p>
|
||||
Show which flags apply to the name that has been looked up. Possible
|
||||
answers are zero or more of: Response, Authoritative,
|
||||
Truncated, Recursion_Desired, Recursion_Available, Broadcast.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>name</DT
|
||||
><DD
|
||||
><P
|
||||
>This is the NetBIOS name being queried. Depending
|
||||
</p></dd><dt><span class="term">name</span></dt><dd><p>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 '#<type>' to the name. This name may also be
|
||||
by appending '#<type>' to the name. This name may also be
|
||||
'*', which will return all registered names within a broadcast
|
||||
area.</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN154"
|
||||
></A
|
||||
><H2
|
||||
>EXAMPLES</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>nmblookup</B
|
||||
> can be used to query
|
||||
a WINS server (in the same way <B
|
||||
CLASS="COMMAND"
|
||||
>nslookup</B
|
||||
> is
|
||||
used to query DNS servers). To query a WINS server, <B
|
||||
CLASS="COMMAND"
|
||||
>nmblookup</B
|
||||
>
|
||||
must be called like this:</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>nmblookup -U server -R 'name'</B
|
||||
></P
|
||||
><P
|
||||
>For example, running :</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>nmblookup -U samba.org -R 'IRIX#1B'</B
|
||||
></P
|
||||
><P
|
||||
>would query the WINS server samba.org for the domain
|
||||
master browser (1B name type) for the IRIX workgroup.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN166"
|
||||
></A
|
||||
><H2
|
||||
>VERSION</H2
|
||||
><P
|
||||
>This man page is correct for version 3.0 of
|
||||
the Samba suite.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN169"
|
||||
></A
|
||||
><H2
|
||||
>SEE ALSO</H2
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>nmbd</SPAN
|
||||
>(8)</SPAN
|
||||
>, <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>samba</SPAN
|
||||
>(7)</SPAN
|
||||
>, and <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
>.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN181"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>The original Samba software and related utilities
|
||||
area.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>EXAMPLES</h2><p><b>nmblookup</b> can be used to query
|
||||
a WINS server (in the same way <b>nslookup</b> is
|
||||
used to query DNS servers). To query a WINS server, <b>nmblookup</b>
|
||||
must be called like this:</p><p><b>nmblookup -U server -R 'name'</b></p><p>For example, running :</p><p><b>nmblookup -U samba.org -R 'IRIX#1B'</b></p><p>would query the WINS server samba.org for the domain
|
||||
master browser (1B name type) for the IRIX workgroup.</p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of
|
||||
the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="nmbd.8.html">nmbd(8)</a>, <a href="samba.7.html">samba(7)</a>, and <a href="smb.conf.5.html">smb.conf(5)</a>.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.</P
|
||||
><P
|
||||
>The original Samba man pages were written by Karl Auer.
|
||||
to the way the Linux kernel is developed.</p><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/"
|
||||
TARGET="_top"
|
||||
> ftp://ftp.icce.rug.nl/pub/unix/</A
|
||||
>) and updated for the Samba 2.0
|
||||
excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
|
||||
ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook
|
||||
XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
|
||||
|
||||
@ -1,261 +1,45 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>ntlm_auth</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="NTLM-AUTH.1"
|
||||
></A
|
||||
>ntlm_auth</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>ntlm_auth -- tool to allow external access to Winbind's NTLM authentication function</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>ntlm_auth</B
|
||||
> [-d debuglevel] [-l logfile] [-s <smb config file>]</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN14"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
>This tool is part of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
> suite.</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>ntlm_auth</B
|
||||
> is a helper utility that authenticates
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ntlm_auth</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="ntlm-auth.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ntlm_auth — tool to allow external access to Winbind's NTLM authentication function</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>ntlm_auth</tt> [-d debuglevel] [-l logfile] [-s <smb config file>]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>ntlm_auth</b> is a helper utility that authenticates
|
||||
users using NT/LM authentication. It returns 0 if the users is authenticated
|
||||
successfully and 1 if access was denied. ntlm_auth uses winbind to access
|
||||
the user and authentication data for a domain. This utility
|
||||
is only to be used by other programs (currently squid).
|
||||
</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN22"
|
||||
></A
|
||||
><H2
|
||||
>OPTIONS</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>--helper-protocol=PROTO</DT
|
||||
><DD
|
||||
><P
|
||||
> Operate as a stdio-based helper
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>--username=USERNAME</DT
|
||||
><DD
|
||||
><P
|
||||
> Specify username of user to authenticate
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>--domain=DOMAIN</DT
|
||||
><DD
|
||||
><P
|
||||
> Specify domain of user to authenticate
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>--workstation=WORKSTATION</DT
|
||||
><DD
|
||||
><P
|
||||
> Specify the workstation the user authenticated from
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>--challenge=STRING</DT
|
||||
><DD
|
||||
><P
|
||||
>challenge (HEX encoded)</P
|
||||
></DD
|
||||
><DT
|
||||
>--lm-response=RESPONSE</DT
|
||||
><DD
|
||||
><P
|
||||
>LM Response to the challenge (HEX encoded)</P
|
||||
></DD
|
||||
><DT
|
||||
>--nt-response=RESPONSE</DT
|
||||
><DD
|
||||
><P
|
||||
>NT or NTLMv2 Response to the challenge (HEX encoded)</P
|
||||
></DD
|
||||
><DT
|
||||
>--password=PASSWORD</DT
|
||||
><DD
|
||||
><P
|
||||
>User's plaintext password</P
|
||||
></DD
|
||||
><DT
|
||||
>--request-lm-key</DT
|
||||
><DD
|
||||
><P
|
||||
>Retreive LM session key</P
|
||||
></DD
|
||||
><DT
|
||||
>--request-nt-key</DT
|
||||
><DD
|
||||
><P
|
||||
>Request NT key</P
|
||||
></DD
|
||||
><DT
|
||||
>-V</DT
|
||||
><DD
|
||||
><P
|
||||
>Prints the version number for
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
>.</P
|
||||
></DD
|
||||
><DT
|
||||
>-s <configuration file></DT
|
||||
><DD
|
||||
><P
|
||||
>The file specified contains the
|
||||
</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">--helper-protocol=PROTO</span></dt><dd><p>
|
||||
Operate as a stdio-based helper
|
||||
</p></dd><dt><span class="term">--username=USERNAME</span></dt><dd><p>
|
||||
Specify username of user to authenticate
|
||||
</p></dd><dt><span class="term">--domain=DOMAIN</span></dt><dd><p>
|
||||
Specify domain of user to authenticate
|
||||
</p></dd><dt><span class="term">--workstation=WORKSTATION</span></dt><dd><p>
|
||||
Specify the workstation the user authenticated from
|
||||
</p></dd><dt><span class="term">--challenge=STRING</span></dt><dd><p>challenge (HEX encoded)</p></dd><dt><span class="term">--lm-response=RESPONSE</span></dt><dd><p>LM Response to the challenge (HEX encoded)</p></dd><dt><span class="term">--nt-response=RESPONSE</span></dt><dd><p>NT or NTLMv2 Response to the challenge (HEX encoded)</p></dd><dt><span class="term">--password=PASSWORD</span></dt><dd><p>User's plaintext password</p></dd><dt><span class="term">--request-lm-key</span></dt><dd><p>Retreive LM session key</p></dd><dt><span class="term">--request-nt-key</span></dt><dd><p>Request NT key</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for
|
||||
<b>smbd</b>.</p></dd><dt><span class="term">-s <configuration file></span></dt><dd><p>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 <A
|
||||
HREF="smb.conf.5.html"
|
||||
TARGET="_top"
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf(5)</TT
|
||||
></A
|
||||
> for more information.
|
||||
to provide. See <a href="smb.conf.5.html" target="_top"><tt>
|
||||
smb.conf(5)</tt></a> for more information.
|
||||
The default configuration file name is determined at
|
||||
compile time.</P
|
||||
></DD
|
||||
><DT
|
||||
>-d|--debug=debuglevel</DT
|
||||
><DD
|
||||
><P
|
||||
><VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>debuglevel</VAR
|
||||
> is an integer
|
||||
compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
|
||||
from 0 to 10. The default value if this parameter is
|
||||
not specified is zero.</P
|
||||
><P
|
||||
>The higher this value, the more detail will be
|
||||
not specified is zero.</p><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
|
||||
><P
|
||||
>Levels above 1 will generate considerable
|
||||
information about operations carried out.</p><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
|
||||
><P
|
||||
>Note that specifying this parameter here will
|
||||
override the <A
|
||||
HREF="smb.conf.5.html#loglevel"
|
||||
TARGET="_top"
|
||||
>log
|
||||
level</A
|
||||
> parameter in the <A
|
||||
HREF="smb.conf.5.html"
|
||||
TARGET="_top"
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf(5)</TT
|
||||
></A
|
||||
> file.</P
|
||||
></DD
|
||||
><DT
|
||||
>-l|--logfile=logbasename</DT
|
||||
><DD
|
||||
><P
|
||||
>File name for log/debug files. The extension
|
||||
<CODE
|
||||
CLASS="CONSTANT"
|
||||
>".client"</CODE
|
||||
> will be appended. The log file is
|
||||
never removed by the client.</P
|
||||
></DD
|
||||
><DT
|
||||
>-h|--help</DT
|
||||
><DD
|
||||
><P
|
||||
>Print a summary of command line options.</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN96"
|
||||
></A
|
||||
><H2
|
||||
>VERSION</H2
|
||||
><P
|
||||
>This man page is correct for version 3.0 of the Samba
|
||||
suite.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN99"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>The original Samba software and related utilities
|
||||
data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
|
||||
override the <a href="smb.conf.5.html#loglevel" target="_top">log
|
||||
level</a> parameter in the <a href="smb.conf.5.html" target="_top">
|
||||
<tt>smb.conf(5)</tt></a> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
|
||||
<tt>".client"</tt> will be appended. The log file is
|
||||
never removed by the client.
|
||||
</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
|
||||
</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the Samba
|
||||
suite.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.</P
|
||||
><P
|
||||
>The ntlm_auth manpage was written by Jelmer Vernooij.</P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
to the way the Linux kernel is developed.</p><p>The ntlm_auth manpage was written by Jelmer Vernooij.</p></div></div></body></html>
|
||||
|
||||
File diff suppressed because one or more lines are too long
@ -1,201 +1,37 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>PAM Configuration for Centrally Managed Authentication</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
||||
REL="HOME"
|
||||
TITLE="SAMBA Project Documentation"
|
||||
HREF="samba-howto-collection.html"><LINK
|
||||
REL="UP"
|
||||
TITLE="Advanced Configuration"
|
||||
HREF="optional.html"><LINK
|
||||
REL="PREVIOUS"
|
||||
TITLE="Interdomain Trust Relationships"
|
||||
HREF="interdomaintrusts.html"><LINK
|
||||
REL="NEXT"
|
||||
TITLE="Stackable VFS modules"
|
||||
HREF="vfs.html"></HEAD
|
||||
><BODY
|
||||
CLASS="CHAPTER"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><DIV
|
||||
CLASS="NAVHEADER"
|
||||
><TABLE
|
||||
SUMMARY="Header navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TH
|
||||
COLSPAN="3"
|
||||
ALIGN="center"
|
||||
>SAMBA Project Documentation</TH
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="left"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="interdomaintrusts.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="80%"
|
||||
ALIGN="center"
|
||||
VALIGN="bottom"
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="right"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="vfs.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
></TABLE
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"></DIV
|
||||
><DIV
|
||||
CLASS="CHAPTER"
|
||||
><H1
|
||||
><A
|
||||
NAME="PAM"
|
||||
></A
|
||||
>Chapter 20. PAM Configuration for Centrally Managed Authentication</H1
|
||||
><DIV
|
||||
CLASS="TOC"
|
||||
><DL
|
||||
><DT
|
||||
><B
|
||||
>Table of Contents</B
|
||||
></DT
|
||||
><DT
|
||||
>20.1. <A
|
||||
HREF="pam.html#AEN3507"
|
||||
>Samba and PAM</A
|
||||
></DT
|
||||
><DT
|
||||
>20.2. <A
|
||||
HREF="pam.html#AEN3558"
|
||||
>Distributed Authentication</A
|
||||
></DT
|
||||
><DT
|
||||
>20.3. <A
|
||||
HREF="pam.html#AEN3563"
|
||||
>PAM Configuration in smb.conf</A
|
||||
></DT
|
||||
></DL
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN3507"
|
||||
>20.1. Samba and PAM</A
|
||||
></H1
|
||||
><P
|
||||
>A number of Unix systems (eg: Sun Solaris), as well as the
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 20. PAM Configuration for Centrally Managed Authentication</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="previous" href="InterdomainTrusts.html" title="Chapter 19. Interdomain Trust Relationships"><link rel="next" href="VFS.html" title="Chapter 21. Stackable VFS modules"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 20. PAM Configuration for Centrally Managed Authentication</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="InterdomainTrusts.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="VFS.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="pam"></a>Chapter 20. PAM Configuration for Centrally Managed Authentication</h2></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate"> (Jun 21 2001) </p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="pam.html#id2897853">Samba and PAM</a></dt><dd><dl><dt><a href="pam.html#id2898634">PAM Configuration in smb.conf</a></dt><dt><a href="pam.html#id2898691">Password Synchronisation using pam_smbpass.so</a></dt></dl></dd><dt><a href="pam.html#id2898943">Distributed Authentication</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2897853"></a>Samba and PAM</h2></div></div><p>
|
||||
A number of Unix systems (eg: Sun Solaris), as well as the
|
||||
xxxxBSD family and Linux, now utilize the Pluggable Authentication
|
||||
Modules (PAM) facility to provide all authentication,
|
||||
authorization and resource control services. Prior to the
|
||||
introduction of PAM, a decision to use an alternative to
|
||||
the system password database (<TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/passwd</TT
|
||||
>)
|
||||
the system password database (<tt>/etc/passwd</tt>)
|
||||
would require the provision of alternatives for all programs that provide
|
||||
security services. Such a choice would involve provision of
|
||||
alternatives to such programs as: <B
|
||||
CLASS="COMMAND"
|
||||
>login</B
|
||||
>,
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>passwd</B
|
||||
>, <B
|
||||
CLASS="COMMAND"
|
||||
>chown</B
|
||||
>, etc.</P
|
||||
><P
|
||||
>PAM provides a mechanism that disconnects these security programs
|
||||
alternatives to such programs as: <b>login</b>,
|
||||
<b>passwd</b>, <b>chown</b>, etc.
|
||||
</p><p>
|
||||
PAM provides a mechanism that disconnects these security programs
|
||||
from the underlying authentication/authorization infrastructure.
|
||||
PAM is configured either through one file <TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/pam.conf</TT
|
||||
> (Solaris),
|
||||
or by editing individual files that are located in <TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/pam.d</TT
|
||||
>.</P
|
||||
><DIV
|
||||
CLASS="NOTE"
|
||||
><P
|
||||
></P
|
||||
><TABLE
|
||||
CLASS="NOTE"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="25"
|
||||
ALIGN="CENTER"
|
||||
VALIGN="TOP"
|
||||
><IMG
|
||||
SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
|
||||
HSPACE="5"
|
||||
ALT="Note"></TD
|
||||
><TD
|
||||
ALIGN="LEFT"
|
||||
VALIGN="TOP"
|
||||
><P
|
||||
> If the PAM authentication module (loadable link library file) is located in the
|
||||
PAM is configured either through one file <tt>/etc/pam.conf</tt> (Solaris),
|
||||
or by editing individual files that are located in <tt>/etc/pam.d</tt>.
|
||||
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
|
||||
If the PAM authentication module (loadable link library file) is located in the
|
||||
default location then it is not necessary to specify the path. In the case of
|
||||
Linux, the default location is <TT
|
||||
CLASS="FILENAME"
|
||||
>/lib/security</TT
|
||||
>. If the module
|
||||
is located other than default then the path may be specified as:
|
||||
Linux, the default location is <tt>/lib/security</tt>. If the module
|
||||
is located outside the default then the path must be specified as:
|
||||
|
||||
<PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
> auth required /other_path/pam_strange_module.so
|
||||
</PRE
|
||||
>
|
||||
</P
|
||||
></TD
|
||||
></TR
|
||||
></TABLE
|
||||
></DIV
|
||||
><P
|
||||
>The following is an example <TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/pam.d/login</TT
|
||||
> configuration file.
|
||||
</p><pre class="programlisting">
|
||||
auth required /other_path/pam_strange_module.so
|
||||
</pre><p>
|
||||
</p></div><p>
|
||||
The following is an example <tt>/etc/pam.d/login</tt> configuration file.
|
||||
This example had all options been uncommented is probably not usable
|
||||
as it stacks many conditions before allowing successful completion
|
||||
of the login process. Essentially all conditions can be disabled
|
||||
by commenting them out except the calls to <TT
|
||||
CLASS="FILENAME"
|
||||
>pam_pwdb.so</TT
|
||||
>.</P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
> #%PAM-1.0
|
||||
by commenting them out except the calls to <tt>pam_pwdb.so</tt>.
|
||||
</p><pre class="programlisting">
|
||||
#%PAM-1.0
|
||||
# The PAM configuration file for the `login' service
|
||||
#
|
||||
auth required pam_securetty.so
|
||||
@ -208,22 +44,13 @@ CLASS="PROGRAMLISTING"
|
||||
session required pam_pwdb.so
|
||||
# session optional pam_lastlog.so
|
||||
# password required pam_cracklib.so retry=3
|
||||
password required pam_pwdb.so shadow md5</PRE
|
||||
></P
|
||||
><P
|
||||
>PAM allows use of replacable modules. Those available on a
|
||||
sample system include:</P
|
||||
><P
|
||||
><SAMP
|
||||
CLASS="PROMPT"
|
||||
>$</SAMP
|
||||
><KBD
|
||||
CLASS="USERINPUT"
|
||||
>/bin/ls /lib/security</KBD
|
||||
>
|
||||
<PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
> pam_access.so pam_ftp.so pam_limits.so
|
||||
password required pam_pwdb.so shadow md5
|
||||
</pre><p>
|
||||
PAM allows use of replacable modules. Those available on a
|
||||
sample system include:
|
||||
</p><p><tt>$</tt><b><tt>/bin/ls /lib/security</tt></b>
|
||||
</p><pre class="programlisting">
|
||||
pam_access.so pam_ftp.so pam_limits.so
|
||||
pam_ncp_auth.so pam_rhosts_auth.so pam_stress.so
|
||||
pam_cracklib.so pam_group.so pam_listfile.so
|
||||
pam_nologin.so pam_rootok.so pam_tally.so
|
||||
@ -234,283 +61,220 @@ CLASS="PROGRAMLISTING"
|
||||
pam_env.so pam_ldap.so pam_motd.so
|
||||
pam_radius.so pam_smbpass.so pam_unix_acct.so
|
||||
pam_wheel.so pam_unix_auth.so pam_unix_passwd.so
|
||||
pam_userdb.so pam_warn.so pam_unix_session.so</PRE
|
||||
></P
|
||||
><P
|
||||
>The following example for the login program replaces the use of
|
||||
the <TT
|
||||
CLASS="FILENAME"
|
||||
>pam_pwdb.so</TT
|
||||
> module which uses the system
|
||||
password database (<TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/passwd</TT
|
||||
>,
|
||||
<TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/shadow</TT
|
||||
>, <TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/group</TT
|
||||
>) with
|
||||
the module <TT
|
||||
CLASS="FILENAME"
|
||||
>pam_smbpass.so</TT
|
||||
> which uses the Samba
|
||||
pam_userdb.so pam_warn.so pam_unix_session.so
|
||||
</pre><p>
|
||||
The following example for the login program replaces the use of
|
||||
the <tt>pam_pwdb.so</tt> module which uses the system
|
||||
password database (<tt>/etc/passwd</tt>,
|
||||
<tt>/etc/shadow</tt>, <tt>/etc/group</tt>) with
|
||||
the module <tt>pam_smbpass.so</tt> which uses the Samba
|
||||
database which contains the Microsoft MD4 encrypted password
|
||||
hashes. This database is stored in either
|
||||
<TT
|
||||
CLASS="FILENAME"
|
||||
>/usr/local/samba/private/smbpasswd</TT
|
||||
>,
|
||||
<TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/samba/smbpasswd</TT
|
||||
>, or in
|
||||
<TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/samba.d/smbpasswd</TT
|
||||
>, depending on the
|
||||
<tt>/usr/local/samba/private/smbpasswd</tt>,
|
||||
<tt>/etc/samba/smbpasswd</tt>, or in
|
||||
<tt>/etc/samba.d/smbpasswd</tt>, depending on the
|
||||
Samba implementation for your Unix/Linux system. The
|
||||
<TT
|
||||
CLASS="FILENAME"
|
||||
>pam_smbpass.so</TT
|
||||
> module is provided by
|
||||
<tt>pam_smbpass.so</tt> module is provided by
|
||||
Samba version 2.2.1 or later. It can be compiled by specifying the
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>--with-pam_smbpass</B
|
||||
> options when running Samba's
|
||||
<TT
|
||||
CLASS="FILENAME"
|
||||
>configure</TT
|
||||
> script. For more information
|
||||
on the <TT
|
||||
CLASS="FILENAME"
|
||||
>pam_smbpass</TT
|
||||
> module, see the documentation
|
||||
in the <TT
|
||||
CLASS="FILENAME"
|
||||
>source/pam_smbpass</TT
|
||||
> directory of the Samba
|
||||
source distribution.</P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
> #%PAM-1.0
|
||||
<b>--with-pam_smbpass</b> options when running Samba's
|
||||
<tt>configure</tt> script. For more information
|
||||
on the <tt>pam_smbpass</tt> module, see the documentation
|
||||
in the <tt>source/pam_smbpass</tt> directory of the Samba
|
||||
source distribution.
|
||||
</p><pre class="programlisting">
|
||||
#%PAM-1.0
|
||||
# The PAM configuration file for the `login' service
|
||||
#
|
||||
auth required pam_smbpass.so nodelay
|
||||
account required pam_smbpass.so nodelay
|
||||
session required pam_smbpass.so nodelay
|
||||
password required pam_smbpass.so nodelay</PRE
|
||||
></P
|
||||
><P
|
||||
>The following is the PAM configuration file for a particular
|
||||
Linux system. The default condition uses <TT
|
||||
CLASS="FILENAME"
|
||||
>pam_pwdb.so</TT
|
||||
>.</P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
> #%PAM-1.0
|
||||
password required pam_smbpass.so nodelay
|
||||
</pre><p>
|
||||
The following is the PAM configuration file for a particular
|
||||
Linux system. The default condition uses <tt>pam_pwdb.so</tt>.
|
||||
</p><pre class="programlisting">
|
||||
#%PAM-1.0
|
||||
# The PAM configuration file for the `samba' service
|
||||
#
|
||||
auth required pam_pwdb.so nullok nodelay shadow audit
|
||||
account required pam_pwdb.so audit nodelay
|
||||
session required pam_pwdb.so nodelay
|
||||
password required pam_pwdb.so shadow md5</PRE
|
||||
></P
|
||||
><P
|
||||
>In the following example the decision has been made to use the
|
||||
password required pam_pwdb.so shadow md5
|
||||
</pre><p>
|
||||
In the following example the decision has been made to use the
|
||||
smbpasswd database even for basic samba authentication. Such a
|
||||
decision could also be made for the passwd program and would
|
||||
thus allow the smbpasswd passwords to be changed using the passwd
|
||||
program.</P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
> #%PAM-1.0
|
||||
program.
|
||||
</p><pre class="programlisting">
|
||||
#%PAM-1.0
|
||||
# The PAM configuration file for the `samba' service
|
||||
#
|
||||
auth required pam_smbpass.so nodelay
|
||||
account required pam_pwdb.so audit nodelay
|
||||
session required pam_pwdb.so nodelay
|
||||
password required pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf</PRE
|
||||
></P
|
||||
><DIV
|
||||
CLASS="NOTE"
|
||||
><P
|
||||
></P
|
||||
><TABLE
|
||||
CLASS="NOTE"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="25"
|
||||
ALIGN="CENTER"
|
||||
VALIGN="TOP"
|
||||
><IMG
|
||||
SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
|
||||
HSPACE="5"
|
||||
ALT="Note"></TD
|
||||
><TD
|
||||
ALIGN="LEFT"
|
||||
VALIGN="TOP"
|
||||
><P
|
||||
>PAM allows stacking of authentication mechanisms. It is
|
||||
password required pam_smbpass.so nodelay smbconf=/etc/samba.d/smb.conf
|
||||
</pre><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>PAM allows stacking of authentication mechanisms. It is
|
||||
also possible to pass information obtained within one PAM module through
|
||||
to the next module in the PAM stack. Please refer to the documentation for
|
||||
your particular system implementation for details regarding the specific
|
||||
capabilities of PAM in this environment. Some Linux implmentations also
|
||||
provide the <TT
|
||||
CLASS="FILENAME"
|
||||
>pam_stack.so</TT
|
||||
> module that allows all
|
||||
provide the <tt>pam_stack.so</tt> module that allows all
|
||||
authentication to be configured in a single central file. The
|
||||
<TT
|
||||
CLASS="FILENAME"
|
||||
>pam_stack.so</TT
|
||||
> method has some very devoted followers
|
||||
<tt>pam_stack.so</tt> method has some very devoted followers
|
||||
on the basis that it allows for easier administration. As with all issues in
|
||||
life though, every decision makes trade-offs, so you may want examine the
|
||||
PAM documentation for further helpful information.</P
|
||||
></TD
|
||||
></TR
|
||||
></TABLE
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN3558"
|
||||
>20.2. Distributed Authentication</A
|
||||
></H1
|
||||
><P
|
||||
>The astute administrator will realize from this that the
|
||||
combination of <TT
|
||||
CLASS="FILENAME"
|
||||
>pam_smbpass.so</TT
|
||||
>,
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>winbindd</B
|
||||
>, and a distributed
|
||||
PAM documentation for further helpful information.
|
||||
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2898634"></a>PAM Configuration in smb.conf</h3></div></div><p>
|
||||
There is an option in smb.conf called <a href="smb.conf.5.html#OBEYPAMRESTRICTIONS" target="_top">obey pam restrictions</a>.
|
||||
The following is from the on-line help for this option in SWAT;
|
||||
</p><p>
|
||||
When Samba is configured to enable PAM support (i.e.
|
||||
<tt>--with-pam</tt>), this parameter will
|
||||
control whether or not Samba should obey PAM's account
|
||||
and session management directives. The default behavior
|
||||
is to use PAM for clear text authentication only and to
|
||||
ignore any account or session management. Note that Samba always
|
||||
ignores PAM for authentication in the case of
|
||||
<a href="smb.conf.5.html#ENCRYPTPASSWORDS" target="_top">encrypt passwords = yes</a>.
|
||||
The reason is that PAM modules cannot support the challenge/response
|
||||
authentication mechanism needed in the presence of SMB
|
||||
password encryption.
|
||||
</p><p>Default: <b>obey pam restrictions = no</b></p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2898691"></a>Password Synchronisation using pam_smbpass.so</h3></div></div><p>
|
||||
pam_smbpass is a PAM module which can be used on conforming systems to
|
||||
keep the smbpasswd (Samba password) database in sync with the unix
|
||||
password file. PAM (Pluggable Authentication Modules) is an API supported
|
||||
under some Unices, such as Solaris, HPUX and Linux, that provides a
|
||||
generic interface to authentication mechanisms.
|
||||
</p><p>
|
||||
For more information on PAM, see http://ftp.kernel.org/pub/linux/libs/pam/
|
||||
</p><p>
|
||||
This module authenticates a local smbpasswd user database. If you require
|
||||
support for authenticating against a remote SMB server, or if you're
|
||||
concerned about the presence of suid root binaries on your system, it is
|
||||
recommended that you use pam_winbind instead.
|
||||
</p><pre class="programlisting">
|
||||
Options recognized by this module are as follows:
|
||||
|
||||
debug - log more debugging info
|
||||
audit - like debug, but also logs unknown usernames
|
||||
use_first_pass - don't prompt the user for passwords;
|
||||
take them from PAM_ items instead
|
||||
try_first_pass - try to get the password from a previous
|
||||
PAM module, fall back to prompting the user
|
||||
use_authtok - like try_first_pass, but *fail* if the new
|
||||
PAM_AUTHTOK has not been previously set.
|
||||
(intended for stacking password modules only)
|
||||
not_set_pass - don't make passwords used by this module
|
||||
available to other modules.
|
||||
nodelay - don't insert ~1 second delays on authentication
|
||||
failure.
|
||||
nullok - null passwords are allowed.
|
||||
nonull - null passwords are not allowed. Used to
|
||||
override the Samba configuration.
|
||||
migrate - only meaningful in an "auth" context;
|
||||
used to update smbpasswd file with a
|
||||
password used for successful authentication.
|
||||
smbconf=< file > - specify an alternate path to the smb.conf
|
||||
file.
|
||||
</pre><pre class="programlisting">
|
||||
Thanks go to the following people:
|
||||
|
||||
* Andrew Morgan < morgan@transmeta.com >, for providing the Linux-PAM
|
||||
framework, without which none of this would have happened
|
||||
|
||||
* Christian Gafton < gafton@redhat.com > and Andrew Morgan again, for the
|
||||
pam_pwdb module upon which pam_smbpass was originally based
|
||||
|
||||
* Luke Leighton < lkcl@switchboard.net > for being receptive to the idea,
|
||||
and for the occasional good-natured complaint about the project's status
|
||||
that keep me working on it :)
|
||||
|
||||
* and of course, all the other members of the Samba team
|
||||
<http://www.samba.org/samba/team.html>, for creating a great product
|
||||
and for giving this project a purpose
|
||||
|
||||
---------------------
|
||||
Stephen Langasek < vorlon@netexpress.net >
|
||||
</pre><p>
|
||||
The following are examples of the use of pam_smbpass.so in the format of Linux
|
||||
<tt>/etc/pam.d/</tt> files structure. Those wishing to implement this
|
||||
tool on other platforms will need to adapt this appropriately.
|
||||
</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2898803"></a>Password Synchonisation Configuration</h4></div></div><p>
|
||||
A sample PAM configuration that shows the use of pam_smbpass to make
|
||||
sure private/smbpasswd is kept in sync when /etc/passwd (/etc/shadow)
|
||||
is changed. Useful when an expired password might be changed by an
|
||||
application (such as ssh).
|
||||
</p><pre class="programlisting">
|
||||
#%PAM-1.0
|
||||
# password-sync
|
||||
#
|
||||
auth requisite pam_nologin.so
|
||||
auth required pam_unix.so
|
||||
account required pam_unix.so
|
||||
password requisite pam_cracklib.so retry=3
|
||||
password requisite pam_unix.so shadow md5 use_authtok try_first_pass
|
||||
password required pam_smbpass.so nullok use_authtok try_first_pass
|
||||
session required pam_unix.so
|
||||
</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2898838"></a>Password Migration Configuration</h4></div></div><p>
|
||||
A sample PAM configuration that shows the use of pam_smbpass to migrate
|
||||
from plaintext to encrypted passwords for Samba. Unlike other methods,
|
||||
this can be used for users who have never connected to Samba shares:
|
||||
password migration takes place when users ftp in, login using ssh, pop
|
||||
their mail, etc.
|
||||
</p><pre class="programlisting">
|
||||
#%PAM-1.0
|
||||
# password-migration
|
||||
#
|
||||
auth requisite pam_nologin.so
|
||||
# pam_smbpass is called IFF pam_unix succeeds.
|
||||
auth requisite pam_unix.so
|
||||
auth optional pam_smbpass.so migrate
|
||||
account required pam_unix.so
|
||||
password requisite pam_cracklib.so retry=3
|
||||
password requisite pam_unix.so shadow md5 use_authtok try_first_pass
|
||||
password optional pam_smbpass.so nullok use_authtok try_first_pass
|
||||
session required pam_unix.so
|
||||
</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2898875"></a>Mature Password Configuration</h4></div></div><p>
|
||||
A sample PAM configuration for a 'mature' smbpasswd installation.
|
||||
private/smbpasswd is fully populated, and we consider it an error if
|
||||
the smbpasswd doesn't exist or doesn't match the Unix password.
|
||||
</p><pre class="programlisting">
|
||||
#%PAM-1.0
|
||||
# password-mature
|
||||
#
|
||||
auth requisite pam_nologin.so
|
||||
auth required pam_unix.so
|
||||
account required pam_unix.so
|
||||
password requisite pam_cracklib.so retry=3
|
||||
password requisite pam_unix.so shadow md5 use_authtok try_first_pass
|
||||
password required pam_smbpass.so use_authtok use_first_pass
|
||||
session required pam_unix.so
|
||||
</pre></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2898908"></a>Kerberos Password Integration Configuration</h4></div></div><p>
|
||||
A sample PAM configuration that shows pam_smbpass used together with
|
||||
pam_krb5. This could be useful on a Samba PDC that is also a member of
|
||||
a Kerberos realm.
|
||||
</p><pre class="programlisting">
|
||||
#%PAM-1.0
|
||||
# kdc-pdc
|
||||
#
|
||||
auth requisite pam_nologin.so
|
||||
auth requisite pam_krb5.so
|
||||
auth optional pam_smbpass.so migrate
|
||||
account required pam_krb5.so
|
||||
password requisite pam_cracklib.so retry=3
|
||||
password optional pam_smbpass.so nullok use_authtok try_first_pass
|
||||
password required pam_krb5.so use_authtok try_first_pass
|
||||
session required pam_krb5.so
|
||||
</pre></div></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2898943"></a>Distributed Authentication</h2></div></div><p>
|
||||
The astute administrator will realize from this that the
|
||||
combination of <tt>pam_smbpass.so</tt>,
|
||||
<b>winbindd</b>, and a distributed
|
||||
passdb backend, such as ldap, will allow the establishment of a
|
||||
centrally managed, distributed
|
||||
user/password database that can also be used by all
|
||||
PAM (eg: Linux) aware programs and applications. This arrangement
|
||||
can have particularly potent advantages compared with the
|
||||
use of Microsoft Active Directory Service (ADS) in so far as
|
||||
reduction of wide area network authentication traffic.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN3563"
|
||||
>20.3. PAM Configuration in smb.conf</A
|
||||
></H1
|
||||
><P
|
||||
>There is an option in smb.conf called <A
|
||||
HREF="smb.conf.5.html#OBEYPAMRESTRICTIONS"
|
||||
TARGET="_top"
|
||||
>obey pam restrictions</A
|
||||
>.
|
||||
The following is from the on-line help for this option in SWAT;</P
|
||||
><P
|
||||
>When Samba is configured to enable PAM support (i.e.
|
||||
<CODE
|
||||
CLASS="CONSTANT"
|
||||
>--with-pam</CODE
|
||||
>), this parameter will
|
||||
control whether or not Samba should obey PAM's account
|
||||
and session management directives. The default behavior
|
||||
is to use PAM for clear text authentication only and to
|
||||
ignore any account or session management. Note that Samba always
|
||||
ignores PAM for authentication in the case of
|
||||
<A
|
||||
HREF="smb.conf.5.html#ENCRYPTPASSWORDS"
|
||||
TARGET="_top"
|
||||
>encrypt passwords = yes</A
|
||||
>.
|
||||
The reason is that PAM modules cannot support the challenge/response
|
||||
authentication mechanism needed in the presence of SMB
|
||||
password encryption. </P
|
||||
><P
|
||||
>Default: <B
|
||||
CLASS="COMMAND"
|
||||
>obey pam restrictions = no</B
|
||||
></P
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="NAVFOOTER"
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"><TABLE
|
||||
SUMMARY="Footer navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="interdomaintrusts.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="samba-howto-collection.html"
|
||||
ACCESSKEY="H"
|
||||
>Home</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="vfs.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
>Interdomain Trust Relationships</TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="optional.html"
|
||||
ACCESSKEY="U"
|
||||
>Up</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
>Stackable VFS modules</TD
|
||||
></TR
|
||||
></TABLE
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
reduction of wide area network authentication traffic.
|
||||
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="InterdomainTrusts.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="VFS.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 19. Interdomain Trust Relationships </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 21. Stackable VFS modules</td></tr></table></div></body></html>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -1,588 +1,131 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>pdbedit</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="PDBEDIT.8"
|
||||
></A
|
||||
>pdbedit</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>pdbedit -- manage the SAM database</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>pdbedit</B
|
||||
> [-l] [-v] [-w] [-u username] [-f fullname] [-h homedir] [-D drive] [-S script] [-p profile] [-a] [-m] [-x] [-i passdb-backend] [-e passdb-backend] [-g] [-b passdb-backend] [-g] [-d debuglevel] [-s configfile] [-P account-policy] [-C value]</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN32"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
>This tool is part of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
> suite.</P
|
||||
><P
|
||||
>The pdbedit program is used to manage the users accounts
|
||||
stored in the sam database and can only be run by root.</P
|
||||
><P
|
||||
>The pdbedit tool uses the passdb modular interface and is
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>pdbedit</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="pdbedit.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>pdbedit — manage the SAM database</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>pdbedit</tt> [-l] [-v] [-w] [-u username] [-f fullname] [-h homedir] [-D drive] [-S script] [-p profile] [-a] [-m] [-x] [-i passdb-backend] [-e passdb-backend] [-g] [-b passdb-backend] [-g] [-d debuglevel] [-s configfile] [-P account-policy] [-C value]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p>The pdbedit program is used to manage the users accounts
|
||||
stored in the sam database and can only be run by root.</p><p>The pdbedit tool uses the passdb modular interface and is
|
||||
independent from the kind of users database used (currently there
|
||||
are smbpasswd, ldap, nis+ and tdb based and more can be added
|
||||
without changing the tool).</P
|
||||
><P
|
||||
>There are five main ways to use pdbedit: adding a user account,
|
||||
without changing the tool).</p><p>There are five main ways to use pdbedit: adding a user account,
|
||||
removing a user account, modifing a user account, listing user
|
||||
accounts, importing users accounts.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN41"
|
||||
></A
|
||||
><H2
|
||||
>OPTIONS</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>-l</DT
|
||||
><DD
|
||||
><P
|
||||
>This option lists all the user accounts
|
||||
accounts, importing users accounts.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-l</span></dt><dd><p>This option lists all the user accounts
|
||||
present in the users database.
|
||||
This option prints a list of user/uid pairs separated by
|
||||
the ':' character.</P
|
||||
><P
|
||||
>Example: <B
|
||||
CLASS="COMMAND"
|
||||
>pdbedit -l</B
|
||||
></P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="SCREEN"
|
||||
> sorce:500:Simo Sorce
|
||||
samba:45:Test User</PRE
|
||||
></P
|
||||
></DD
|
||||
><DT
|
||||
>-v</DT
|
||||
><DD
|
||||
><P
|
||||
>This option enables the verbose listing format.
|
||||
the ':' character.</p><p>Example: <b>pdbedit -l</b></p><pre class="screen">
|
||||
sorce:500:Simo Sorce
|
||||
samba:45:Test User
|
||||
</pre></dd><dt><span class="term">-v</span></dt><dd><p>This option enables the verbose listing format.
|
||||
It causes pdbedit to list the users in the database, printing
|
||||
out the account fields in a descriptive format.</P
|
||||
><P
|
||||
>Example: <B
|
||||
CLASS="COMMAND"
|
||||
>pdbedit -l -v</B
|
||||
></P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="SCREEN"
|
||||
> ---------------
|
||||
username: sorce
|
||||
user ID/Group: 500/500
|
||||
user RID/GRID: 2000/2001
|
||||
5 Full Name: Simo Sorce
|
||||
Home Directory: \\BERSERKER\sorce
|
||||
HomeDir Drive: H:
|
||||
Logon Script: \\BERSERKER\netlogon\sorce.bat
|
||||
Profile Path: \\BERSERKER\profile
|
||||
10 ---------------
|
||||
username: samba
|
||||
user ID/Group: 45/45
|
||||
user RID/GRID: 1090/1091
|
||||
Full Name: Test User
|
||||
15 Home Directory: \\BERSERKER\samba
|
||||
HomeDir Drive:
|
||||
Logon Script:
|
||||
Profile Path: \\BERSERKER\profile</PRE
|
||||
></P
|
||||
></DD
|
||||
><DT
|
||||
>-w</DT
|
||||
><DD
|
||||
><P
|
||||
>This option sets the "smbpasswd" listing format.
|
||||
out the account fields in a descriptive format.</p><p>Example: <b>pdbedit -l -v</b></p><pre class="screen">
|
||||
---------------
|
||||
username: sorce
|
||||
user ID/Group: 500/500
|
||||
user RID/GRID: 2000/2001
|
||||
Full Name: Simo Sorce
|
||||
Home Directory: \\BERSERKER\sorce
|
||||
HomeDir Drive: H:
|
||||
Logon Script: \\BERSERKER\netlogon\sorce.bat
|
||||
Profile Path: \\BERSERKER\profile
|
||||
---------------
|
||||
username: samba
|
||||
user ID/Group: 45/45
|
||||
user RID/GRID: 1090/1091
|
||||
Full Name: Test User
|
||||
Home Directory: \\BERSERKER\samba
|
||||
HomeDir Drive:
|
||||
Logon Script:
|
||||
Profile Path: \\BERSERKER\profile
|
||||
</pre></dd><dt><span class="term">-w</span></dt><dd><p>This option sets the "smbpasswd" listing format.
|
||||
It will make pdbedit list the users in the database, printing
|
||||
out the account fields in a format compatible with the
|
||||
<TT
|
||||
CLASS="FILENAME"
|
||||
>smbpasswd</TT
|
||||
> file format. (see the
|
||||
<SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbpasswd</SPAN
|
||||
>(5)</SPAN
|
||||
> for details)</P
|
||||
><P
|
||||
>Example: <B
|
||||
CLASS="COMMAND"
|
||||
>pdbedit -l -w</B
|
||||
></P
|
||||
><PRE
|
||||
CLASS="SCREEN"
|
||||
> sorce:500:508818B733CE64BEAAD3B435B51404EE:D2A2418EFC466A8A0F6B1DBB5C3DB80C:[UX ]:LCT-00000000:
|
||||
samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX ]:LCT-3BFA1E8D:</PRE
|
||||
></DD
|
||||
><DT
|
||||
>-u username</DT
|
||||
><DD
|
||||
><P
|
||||
>This option specifies the username to be
|
||||
<tt>smbpasswd</tt> file format. (see the
|
||||
<a href="smbpasswd.5.html">smbpasswd(5)</a> for details)</p><p>Example: <b>pdbedit -l -w</b></p><pre class="screen">
|
||||
sorce:500:508818B733CE64BEAAD3B435B51404EE:D2A2418EFC466A8A0F6B1DBB5C3DB80C:[UX ]:LCT-00000000:
|
||||
samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX ]:LCT-3BFA1E8D:
|
||||
</pre></dd><dt><span class="term">-u username</span></dt><dd><p>This option specifies the username to be
|
||||
used for the operation requested (listing, adding, removing).
|
||||
It is <SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>required</I
|
||||
></SPAN
|
||||
> in add, remove and modify
|
||||
operations and <SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>optional</I
|
||||
></SPAN
|
||||
> in list
|
||||
operations.</P
|
||||
></DD
|
||||
><DT
|
||||
>-f fullname</DT
|
||||
><DD
|
||||
><P
|
||||
>This option can be used while adding or
|
||||
It is <span class="emphasis"><em>required</em></span> in add, remove and modify
|
||||
operations and <span class="emphasis"><em>optional</em></span> in list
|
||||
operations.</p></dd><dt><span class="term">-f fullname</span></dt><dd><p>This option can be used while adding or
|
||||
modifing a user account. It will specify the user's full
|
||||
name. </P
|
||||
><P
|
||||
>Example: <B
|
||||
CLASS="COMMAND"
|
||||
>-f "Simo Sorce"</B
|
||||
></P
|
||||
></DD
|
||||
><DT
|
||||
>-h homedir</DT
|
||||
><DD
|
||||
><P
|
||||
>This option can be used while adding or
|
||||
name. </p><p>Example: <b>-f "Simo Sorce"</b></p></dd><dt><span class="term">-h homedir</span></dt><dd><p>This option can be used while adding or
|
||||
modifing a user account. It will specify the user's home
|
||||
directory network path.</P
|
||||
><P
|
||||
>Example: <B
|
||||
CLASS="COMMAND"
|
||||
>-h "\\\\BERSERKER\\sorce"</B
|
||||
>
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-D drive</DT
|
||||
><DD
|
||||
><P
|
||||
>This option can be used while adding or
|
||||
directory network path.</p><p>Example: <b>-h "\\\\BERSERKER\\sorce"</b>
|
||||
</p></dd><dt><span class="term">-D drive</span></dt><dd><p>This option can be used while adding or
|
||||
modifing a user account. It will specify the windows drive
|
||||
letter to be used to map the home directory.</P
|
||||
><P
|
||||
>Example: <B
|
||||
CLASS="COMMAND"
|
||||
>-d "H:"</B
|
||||
>
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-S script</DT
|
||||
><DD
|
||||
><P
|
||||
>This option can be used while adding or
|
||||
letter to be used to map the home directory.</p><p>Example: <b>-d "H:"</b>
|
||||
</p></dd><dt><span class="term">-S script</span></dt><dd><p>This option can be used while adding or
|
||||
modifing a user account. It will specify the user's logon
|
||||
script path.</P
|
||||
><P
|
||||
>Example: <B
|
||||
CLASS="COMMAND"
|
||||
>-s "\\\\BERSERKER\\netlogon\\sorce.bat"</B
|
||||
>
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-p profile</DT
|
||||
><DD
|
||||
><P
|
||||
>This option can be used while adding or
|
||||
script path.</p><p>Example: <b>-s "\\\\BERSERKER\\netlogon\\sorce.bat"</b>
|
||||
</p></dd><dt><span class="term">-p profile</span></dt><dd><p>This option can be used while adding or
|
||||
modifing a user account. It will specify the user's profile
|
||||
directory.</P
|
||||
><P
|
||||
>Example: <B
|
||||
CLASS="COMMAND"
|
||||
>-p "\\\\BERSERKER\\netlogon"</B
|
||||
>
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-a</DT
|
||||
><DD
|
||||
><P
|
||||
>This option is used to add a user into the
|
||||
directory.</p><p>Example: <b>-p "\\\\BERSERKER\\netlogon"</b>
|
||||
</p></dd><dt><span class="term">-a</span></dt><dd><p>This option is used to add a user into the
|
||||
database. This command needs a user name specified with
|
||||
the -u switch. When adding a new user, pdbedit will also
|
||||
ask for the password to be used.</P
|
||||
><P
|
||||
>Example: <B
|
||||
CLASS="COMMAND"
|
||||
>pdbedit -a -u sorce</B
|
||||
>
|
||||
<PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
>new password:
|
||||
retype new password</PRE
|
||||
></P
|
||||
></DD
|
||||
><DT
|
||||
>-m</DT
|
||||
><DD
|
||||
><P
|
||||
>This option may only be used in conjunction
|
||||
with the <VAR
|
||||
CLASS="PARAMETER"
|
||||
>-a</VAR
|
||||
> option. It will make
|
||||
ask for the password to be used.</p><p>Example: <b>pdbedit -a -u sorce</b>
|
||||
</p><pre class="programlisting">new password:
|
||||
retype new password
|
||||
</pre><p>
|
||||
</p></dd><dt><span class="term">-m</span></dt><dd><p>This option may only be used in conjunction
|
||||
with the <i><tt>-a</tt></i> option. It will make
|
||||
pdbedit to add a machine trust account instead of a user
|
||||
account (-u username will provide the machine name).</P
|
||||
><P
|
||||
>Example: <B
|
||||
CLASS="COMMAND"
|
||||
>pdbedit -a -m -u w2k-wks</B
|
||||
>
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-x</DT
|
||||
><DD
|
||||
><P
|
||||
>This option causes pdbedit to delete an account
|
||||
account (-u username will provide the machine name).</p><p>Example: <b>pdbedit -a -m -u w2k-wks</b>
|
||||
</p></dd><dt><span class="term">-x</span></dt><dd><p>This option causes pdbedit to delete an account
|
||||
from the database. It needs a username specified with the
|
||||
-u switch.</P
|
||||
><P
|
||||
>Example: <B
|
||||
CLASS="COMMAND"
|
||||
>pdbedit -x -u bob</B
|
||||
></P
|
||||
></DD
|
||||
><DT
|
||||
>-i passdb-backend</DT
|
||||
><DD
|
||||
><P
|
||||
>Use a different passdb backend to retrieve users
|
||||
-u switch.</p><p>Example: <b>pdbedit -x -u bob</b></p></dd><dt><span class="term">-i passdb-backend</span></dt><dd><p>Use a different passdb backend to retrieve users
|
||||
than the one specified in smb.conf. Can be used to import data into
|
||||
your local user database.</P
|
||||
><P
|
||||
>This option will ease migration from one passdb backend to
|
||||
another.</P
|
||||
><P
|
||||
>Example: <B
|
||||
CLASS="COMMAND"
|
||||
>pdbedit -i smbpasswd:/etc/smbpasswd.old
|
||||
</B
|
||||
></P
|
||||
></DD
|
||||
><DT
|
||||
>-e passdb-backend</DT
|
||||
><DD
|
||||
><P
|
||||
>Exports all currently available users to the
|
||||
specified password database backend.</P
|
||||
><P
|
||||
>This option will ease migration from one passdb backend to
|
||||
another and will ease backing up.</P
|
||||
><P
|
||||
>Example: <B
|
||||
CLASS="COMMAND"
|
||||
>pdbedit -e smbpasswd:/root/samba-users.backup</B
|
||||
></P
|
||||
></DD
|
||||
><DT
|
||||
>-g</DT
|
||||
><DD
|
||||
><P
|
||||
>If you specify <VAR
|
||||
CLASS="PARAMETER"
|
||||
>-g</VAR
|
||||
>,
|
||||
then <VAR
|
||||
CLASS="PARAMETER"
|
||||
>-i in-backend -e out-backend</VAR
|
||||
>
|
||||
applies to the group mapping instead of the user database.
|
||||
|
||||
</P
|
||||
><P
|
||||
>This option will ease migration from one passdb backend to
|
||||
another and will ease backing up.</P
|
||||
></DD
|
||||
><DT
|
||||
>-g</DT
|
||||
><DD
|
||||
><P
|
||||
>If you specify <VAR
|
||||
CLASS="PARAMETER"
|
||||
>-g</VAR
|
||||
>,
|
||||
then <VAR
|
||||
CLASS="PARAMETER"
|
||||
>-i in-backend -e out-backend</VAR
|
||||
>
|
||||
applies to the group mapping instead of the user database.
|
||||
|
||||
</P
|
||||
><P
|
||||
>This option will ease migration from one passdb backend to
|
||||
another and will ease backing up.</P
|
||||
></DD
|
||||
><DT
|
||||
>-b passdb-backend</DT
|
||||
><DD
|
||||
><P
|
||||
>Use a different default passdb backend. </P
|
||||
><P
|
||||
>Example: <B
|
||||
CLASS="COMMAND"
|
||||
>pdbedit -b xml:/root/pdb-backup.xml -l</B
|
||||
></P
|
||||
></DD
|
||||
><DT
|
||||
>-P account-policy</DT
|
||||
><DD
|
||||
><P
|
||||
>Display an account policy</P
|
||||
><P
|
||||
>Valid policies are: minimum password age, reset count minutes, disconnect time,
|
||||
your local user database.</p><p>This option will ease migration from one passdb backend to
|
||||
another.</p><p>Example: <b>pdbedit -i smbpasswd:/etc/smbpasswd.old
|
||||
</b></p></dd><dt><span class="term">-e passdb-backend</span></dt><dd><p>Exports all currently available users to the
|
||||
specified password database backend.</p><p>This option will ease migration from one passdb backend to
|
||||
another and will ease backing up.</p><p>Example: <b>pdbedit -e smbpasswd:/root/samba-users.backup</b></p></dd><dt><span class="term">-g</span></dt><dd><p>If you specify <i><tt>-g</tt></i>,
|
||||
then <i><tt>-i in-backend -e out-backend</tt></i>
|
||||
applies to the group mapping instead of the user database.</p><p>This option will ease migration from one passdb backend to
|
||||
another and will ease backing up.</p></dd><dt><span class="term">-g</span></dt><dd><p>If you specify <i><tt>-g</tt></i>,
|
||||
then <i><tt>-i in-backend -e out-backend</tt></i>
|
||||
applies to the group mapping instead of the user database.</p><p>This option will ease migration from one passdb backend to
|
||||
another and will ease backing up.</p></dd><dt><span class="term">-b passdb-backend</span></dt><dd><p>Use a different default passdb backend. </p><p>Example: <b>pdbedit -b xml:/root/pdb-backup.xml -l</b></p></dd><dt><span class="term">-P account-policy</span></dt><dd><p>Display an account policy</p><p>Valid policies are: minimum password age, reset count minutes, disconnect time,
|
||||
user must logon to change password, password history, lockout duration, min password length,
|
||||
maximum password age and bad lockout attempt.</P
|
||||
><P
|
||||
>Example: <B
|
||||
CLASS="COMMAND"
|
||||
>pdbedit -P "bad lockout attempt"</B
|
||||
></P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
>account policy value for bad lockout attempt is 0</PRE
|
||||
></P
|
||||
></DD
|
||||
><DT
|
||||
>-C account-policy-value</DT
|
||||
><DD
|
||||
><P
|
||||
>Sets an account policy to a specified value.
|
||||
maximum password age and bad lockout attempt.</p><p>Example: <b>pdbedit -P "bad lockout attempt"</b></p><pre class="programlisting">
|
||||
account policy value for bad lockout attempt is 0
|
||||
</pre></dd><dt><span class="term">-C account-policy-value</span></dt><dd><p>Sets an account policy to a specified value.
|
||||
This option may only be used in conjunction
|
||||
with the <VAR
|
||||
CLASS="PARAMETER"
|
||||
>-P</VAR
|
||||
> option.
|
||||
</P
|
||||
><P
|
||||
>Example: <B
|
||||
CLASS="COMMAND"
|
||||
>pdbedit -P "bad lockout attempt" -C 3</B
|
||||
></P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
>account policy value for bad lockout attempt was 0
|
||||
account policy value for bad lockout attempt is now 3</PRE
|
||||
></P
|
||||
></DD
|
||||
><DT
|
||||
>-h|--help</DT
|
||||
><DD
|
||||
><P
|
||||
>Print a summary of command line options.</P
|
||||
></DD
|
||||
><DT
|
||||
>-V</DT
|
||||
><DD
|
||||
><P
|
||||
>Prints the version number for
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
>.</P
|
||||
></DD
|
||||
><DT
|
||||
>-s <configuration file></DT
|
||||
><DD
|
||||
><P
|
||||
>The file specified contains the
|
||||
with the <i><tt>-P</tt></i> option.
|
||||
</p><p>Example: <b>pdbedit -P "bad lockout attempt" -C 3</b></p><pre class="programlisting">
|
||||
account policy value for bad lockout attempt was 0
|
||||
account policy value for bad lockout attempt is now 3
|
||||
</pre></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
|
||||
</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for
|
||||
<b>smbd</b>.</p></dd><dt><span class="term">-s <configuration file></span></dt><dd><p>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 <A
|
||||
HREF="smb.conf.5.html"
|
||||
TARGET="_top"
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf(5)</TT
|
||||
></A
|
||||
> for more information.
|
||||
to provide. See <a href="smb.conf.5.html" target="_top"><tt>
|
||||
smb.conf(5)</tt></a> for more information.
|
||||
The default configuration file name is determined at
|
||||
compile time.</P
|
||||
></DD
|
||||
><DT
|
||||
>-d|--debug=debuglevel</DT
|
||||
><DD
|
||||
><P
|
||||
><VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>debuglevel</VAR
|
||||
> is an integer
|
||||
compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
|
||||
from 0 to 10. The default value if this parameter is
|
||||
not specified is zero.</P
|
||||
><P
|
||||
>The higher this value, the more detail will be
|
||||
not specified is zero.</p><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
|
||||
><P
|
||||
>Levels above 1 will generate considerable
|
||||
information about operations carried out.</p><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
|
||||
><P
|
||||
>Note that specifying this parameter here will
|
||||
override the <A
|
||||
HREF="smb.conf.5.html#loglevel"
|
||||
TARGET="_top"
|
||||
>log
|
||||
level</A
|
||||
> parameter in the <A
|
||||
HREF="smb.conf.5.html"
|
||||
TARGET="_top"
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf(5)</TT
|
||||
></A
|
||||
> file.</P
|
||||
></DD
|
||||
><DT
|
||||
>-l|--logfile=logbasename</DT
|
||||
><DD
|
||||
><P
|
||||
>File name for log/debug files. The extension
|
||||
<CODE
|
||||
CLASS="CONSTANT"
|
||||
>".client"</CODE
|
||||
> will be appended. The log file is
|
||||
never removed by the client.</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN210"
|
||||
></A
|
||||
><H2
|
||||
>NOTES</H2
|
||||
><P
|
||||
>This command may be used only by root.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN213"
|
||||
></A
|
||||
><H2
|
||||
>VERSION</H2
|
||||
><P
|
||||
>This man page is correct for version 2.2 of
|
||||
the Samba suite.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN216"
|
||||
></A
|
||||
><H2
|
||||
>SEE ALSO</H2
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbpasswd</SPAN
|
||||
>(5)</SPAN
|
||||
>, <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>samba</SPAN
|
||||
>(7)</SPAN
|
||||
></P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN225"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>The original Samba software and related utilities
|
||||
data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
|
||||
override the <a href="smb.conf.5.html#loglevel" target="_top">log
|
||||
level</a> parameter in the <a href="smb.conf.5.html" target="_top">
|
||||
<tt>smb.conf(5)</tt></a> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
|
||||
<tt>".client"</tt> will be appended. The log file is
|
||||
never removed by the client.
|
||||
</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>NOTES</h2><p>This command may be used only by root.</p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 2.2 of
|
||||
the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="smbpasswd.5.html">smbpasswd(5)</a>, <a href="samba.7.html">samba(7)</a></p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.</P
|
||||
><P
|
||||
>The original Samba man pages were written by Karl Auer.
|
||||
to the way the Linux kernel is developed.</p><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/"
|
||||
TARGET="_top"
|
||||
> ftp://ftp.icce.rug.nl/pub/unix/</A
|
||||
>) and updated for the Samba 2.0
|
||||
excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
|
||||
ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook
|
||||
XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -1,139 +1,17 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>Analysing and solving samba problems</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
||||
REL="HOME"
|
||||
TITLE="SAMBA Project Documentation"
|
||||
HREF="samba-howto-collection.html"><LINK
|
||||
REL="UP"
|
||||
TITLE="Appendixes"
|
||||
HREF="appendixes.html"><LINK
|
||||
REL="PREVIOUS"
|
||||
TITLE="The samba checklist"
|
||||
HREF="diagnosis.html"><LINK
|
||||
REL="NEXT"
|
||||
TITLE="Reporting Bugs"
|
||||
HREF="bugreport.html"></HEAD
|
||||
><BODY
|
||||
CLASS="CHAPTER"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><DIV
|
||||
CLASS="NAVHEADER"
|
||||
><TABLE
|
||||
SUMMARY="Header navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TH
|
||||
COLSPAN="3"
|
||||
ALIGN="center"
|
||||
>SAMBA Project Documentation</TH
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="left"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="diagnosis.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="80%"
|
||||
ALIGN="center"
|
||||
VALIGN="bottom"
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="right"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="bugreport.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
></TABLE
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"></DIV
|
||||
><DIV
|
||||
CLASS="CHAPTER"
|
||||
><H1
|
||||
><A
|
||||
NAME="PROBLEMS"
|
||||
></A
|
||||
>Chapter 34. Analysing and solving samba problems</H1
|
||||
><DIV
|
||||
CLASS="TOC"
|
||||
><DL
|
||||
><DT
|
||||
><B
|
||||
>Table of Contents</B
|
||||
></DT
|
||||
><DT
|
||||
>34.1. <A
|
||||
HREF="problems.html#AEN5004"
|
||||
>Diagnostics tools</A
|
||||
></DT
|
||||
><DT
|
||||
>34.2. <A
|
||||
HREF="problems.html#AEN5019"
|
||||
>Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</A
|
||||
></DT
|
||||
><DT
|
||||
>34.3. <A
|
||||
HREF="problems.html#AEN5048"
|
||||
>Useful URL's</A
|
||||
></DT
|
||||
><DT
|
||||
>34.4. <A
|
||||
HREF="problems.html#AEN5072"
|
||||
>Getting help from the mailing lists</A
|
||||
></DT
|
||||
><DT
|
||||
>34.5. <A
|
||||
HREF="problems.html#AEN5102"
|
||||
>How to get off the mailinglists</A
|
||||
></DT
|
||||
></DL
|
||||
></DIV
|
||||
><P
|
||||
>There are many sources of information available in the form
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 28. Analysing and solving samba problems</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="troubleshooting.html" title="Part IV. Troubleshooting"><link rel="previous" href="diagnosis.html" title="Chapter 27. The samba checklist"><link rel="next" href="bugreport.html" title="Chapter 29. Reporting Bugs"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 28. Analysing and solving samba problems</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="diagnosis.html">Prev</a> </td><th width="60%" align="center">Part IV. Troubleshooting</th><td width="20%" align="right"> <a accesskey="n" href="bugreport.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="problems"></a>Chapter 28. Analysing and solving samba problems</h2></div><div><div class="author"><h3 class="author">Gerald (Jerry) Carter</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jerry@samba.org">jerry@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">David Bannon</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:dbannon@samba.org">dbannon@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">8 Apr 2003</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="problems.html#id2902374">Diagnostics tools</a></dt><dt><a href="problems.html#id2903991">Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</a></dt><dt><a href="problems.html#id2904132">Useful URL's</a></dt><dt><a href="problems.html#id2904239">Getting help from the mailing lists</a></dt><dt><a href="problems.html#id2904392">How to get off the mailinglists</a></dt></dl></div><p>
|
||||
There are many sources of information available in the form
|
||||
of mailing lists, RFC's and documentation. The docs that come
|
||||
with the samba distribution contain very good explanations of
|
||||
general SMB topics such as browsing.</P
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN5004"
|
||||
>34.1. Diagnostics tools</A
|
||||
></H1
|
||||
><P
|
||||
>One of the best diagnostic tools for debugging problems is Samba itself.
|
||||
general SMB topics such as browsing.</p><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2902374"></a>Diagnostics tools</h2></div></div><p>
|
||||
One of the best diagnostic tools for debugging problems is Samba itself.
|
||||
You can use the -d option for both smbd and nmbd to specify what
|
||||
'debug level' at which to run. See the man pages on smbd, nmbd and
|
||||
smb.conf for more information on debugging options. The debug
|
||||
level can range from 1 (the default) to 10 (100 for debugging passwords).</P
|
||||
><P
|
||||
>Another helpful method of debugging is to compile samba using the
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>gcc -g </B
|
||||
> flag. This will include debug
|
||||
level can range from 1 (the default) to 10 (100 for debugging passwords).
|
||||
</p><p>
|
||||
Another helpful method of debugging is to compile samba using the
|
||||
<b>gcc -g </b> flag. This will include debug
|
||||
information in the binaries and allow you to attach gdb to the
|
||||
running smbd / nmbd process. In order to attach gdb to an smbd
|
||||
process for an NT workstation, first get the workstation to make the
|
||||
@ -143,36 +21,16 @@ generate a 'LsaEnumTrustedDomains'. Thereafter, the workstation
|
||||
maintains an open connection, and therefore there will be an smbd
|
||||
process running (assuming that you haven't set a really short smbd
|
||||
idle timeout) So, in between pressing ctrl alt delete, and actually
|
||||
typing in your password, you can gdb attach and continue.</P
|
||||
><P
|
||||
>Some useful samba commands worth investigating:</P
|
||||
><P
|
||||
></P
|
||||
><UL
|
||||
><LI
|
||||
><P
|
||||
>testparam | more</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>smbclient -L //{netbios name of server}</P
|
||||
></LI
|
||||
></UL
|
||||
><P
|
||||
>An SMB enabled version of tcpdump is available from
|
||||
<A
|
||||
HREF="http://www.tcpdump.org/"
|
||||
TARGET="_top"
|
||||
>http://www.tcpdup.org/</A
|
||||
>.
|
||||
typing in your password, you can attach gdb and continue.
|
||||
</p><p>
|
||||
Some useful samba commands worth investigating:
|
||||
</p><div class="itemizedlist"><ul type="disc"><li><p>testparam | more</p></li><li><p>smbclient -L //{netbios name of server}</p></li></ul></div><p>
|
||||
An SMB enabled version of tcpdump is available from
|
||||
<a href="http://www.tcpdump.org/" target="_top">http://www.tcpdup.org/</a>.
|
||||
Ethereal, another good packet sniffer for Unix and Win32
|
||||
hosts, can be downloaded from <A
|
||||
HREF="http://www.ethereal.com/"
|
||||
TARGET="_top"
|
||||
>http://www.ethereal.com</A
|
||||
>.</P
|
||||
><P
|
||||
>For tracing things on the Microsoft Windows NT, Network Monitor
|
||||
hosts, can be downloaded from <a href="http://www.ethereal.com/" target="_top">http://www.ethereal.com</a>.
|
||||
</p><p>
|
||||
For tracing things on the Microsoft Windows NT, Network Monitor
|
||||
(aka. netmon) is available on the Microsoft Developer Network CD's,
|
||||
the Windows NT Server install CD and the SMS CD's. The version of
|
||||
netmon that ships with SMS allows for dumping packets between any two
|
||||
@ -180,381 +38,97 @@ computers (i.e. placing the network interface in promiscuous mode).
|
||||
The version on the NT Server install CD will only allow monitoring
|
||||
of network traffic directed to the local NT box and broadcasts on the
|
||||
local subnet. Be aware that Ethereal can read and write netmon
|
||||
formatted files.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN5019"
|
||||
>34.2. Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</A
|
||||
></H1
|
||||
><P
|
||||
>Installing netmon on an NT workstation requires a couple
|
||||
formatted files.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2903991"></a>Installing 'Network Monitor' on an NT Workstation or a Windows 9x box</h2></div></div><p>
|
||||
Installing netmon on an NT workstation requires a couple
|
||||
of steps. The following are for installing Netmon V4.00.349, which comes
|
||||
with Microsoft Windows NT Server 4.0, on Microsoft Windows NT
|
||||
Workstation 4.0. The process should be similar for other version of
|
||||
Workstation 4.0. The process should be similar for other versions of
|
||||
Windows NT / Netmon. You will need both the Microsoft Windows
|
||||
NT Server 4.0 Install CD and the Workstation 4.0 Install CD.</P
|
||||
><P
|
||||
>Initially you will need to install 'Network Monitor Tools and Agent'
|
||||
on the NT Server. To do this </P
|
||||
><P
|
||||
></P
|
||||
><UL
|
||||
><LI
|
||||
><P
|
||||
>Goto Start - Settings - Control Panel -
|
||||
Network - Services - Add </P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>Select the 'Network Monitor Tools and Agent' and
|
||||
click on 'OK'.</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>Click 'OK' on the Network Control Panel.
|
||||
</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>Insert the Windows NT Server 4.0 install CD
|
||||
when prompted.</P
|
||||
></LI
|
||||
></UL
|
||||
><P
|
||||
>At this point the Netmon files should exist in
|
||||
<TT
|
||||
CLASS="FILENAME"
|
||||
>%SYSTEMROOT%\System32\netmon\*.*</TT
|
||||
>.
|
||||
Two subdirectories exist as well, <TT
|
||||
CLASS="FILENAME"
|
||||
>parsers\</TT
|
||||
>
|
||||
NT Server 4.0 Install CD and the Workstation 4.0 Install CD.
|
||||
</p><p>
|
||||
Initially you will need to install 'Network Monitor Tools and Agent'
|
||||
on the NT Server. To do this
|
||||
</p><div class="itemizedlist"><ul type="disc"><li><p>Goto Start - Settings - Control Panel -
|
||||
Network - Services - Add </p></li><li><p>Select the 'Network Monitor Tools and Agent' and
|
||||
click on 'OK'.</p></li><li><p>Click 'OK' on the Network Control Panel.
|
||||
</p></li><li><p>Insert the Windows NT Server 4.0 install CD
|
||||
when prompted.</p></li></ul></div><p>
|
||||
At this point the Netmon files should exist in
|
||||
<tt>%SYSTEMROOT%\System32\netmon\*.*</tt>.
|
||||
Two subdirectories exist as well, <tt>parsers\</tt>
|
||||
which contains the necessary DLL's for parsing the netmon packet
|
||||
dump, and <TT
|
||||
CLASS="FILENAME"
|
||||
>captures\</TT
|
||||
>.</P
|
||||
><P
|
||||
>In order to install the Netmon tools on an NT Workstation, you will
|
||||
dump, and <tt>captures\</tt>.
|
||||
</p><p>
|
||||
In order to install the Netmon tools on an NT Workstation, you will
|
||||
first need to install the 'Network Monitor Agent' from the Workstation
|
||||
install CD.</P
|
||||
><P
|
||||
></P
|
||||
><UL
|
||||
><LI
|
||||
><P
|
||||
>Goto Start - Settings - Control Panel -
|
||||
Network - Services - Add</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>Select the 'Network Monitor Agent' and click
|
||||
on 'OK'.</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>Click 'OK' on the Network Control Panel.
|
||||
</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>Insert the Windows NT Workstation 4.0 install
|
||||
CD when prompted.</P
|
||||
></LI
|
||||
></UL
|
||||
><P
|
||||
>Now copy the files from the NT Server in %SYSTEMROOT%\System32\netmon\*.*
|
||||
install CD.
|
||||
</p><div class="itemizedlist"><ul type="disc"><li><p>Goto Start - Settings - Control Panel -
|
||||
Network - Services - Add</p></li><li><p>Select the 'Network Monitor Agent' and click
|
||||
on 'OK'.</p></li><li><p>Click 'OK' on the Network Control Panel.
|
||||
</p></li><li><p>Insert the Windows NT Workstation 4.0 install
|
||||
CD when prompted.</p></li></ul></div><p>
|
||||
Now copy the files from the NT Server in %SYSTEMROOT%\System32\netmon\*.*
|
||||
to %SYSTEMROOT%\System32\netmon\*.* on the Workstation and set
|
||||
permissions as you deem appropriate for your site. You will need
|
||||
administrative rights on the NT box to run netmon.</P
|
||||
><P
|
||||
>To install Netmon on a Windows 9x box install the network monitor agent
|
||||
administrative rights on the NT box to run netmon.
|
||||
</p><p>
|
||||
To install Netmon on a Windows 9x box install the network monitor agent
|
||||
from the Windows 9x CD (\admin\nettools\netmon). There is a readme
|
||||
file located with the netmon driver files on the CD if you need
|
||||
information on how to do this. Copy the files from a working
|
||||
Netmon installation.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN5048"
|
||||
>34.3. Useful URL's</A
|
||||
></H1
|
||||
><P
|
||||
></P
|
||||
><UL
|
||||
><LI
|
||||
><P
|
||||
>Home of Samba site <A
|
||||
HREF="http://samba.org"
|
||||
TARGET="_top"
|
||||
> http://samba.org</A
|
||||
>. We have a mirror near you !</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
> The <SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>Development</I
|
||||
></SPAN
|
||||
> document
|
||||
Netmon installation.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2904132"></a>Useful URL's</h2></div></div><div class="itemizedlist"><ul type="disc"><li><p>Home of Samba site <a href="http://samba.org" target="_top">
|
||||
http://samba.org</a>. We have a mirror near you !</p></li><li><p> The <span class="emphasis"><em>Development</em></span> document
|
||||
on the Samba mirrors might mention your problem. If so,
|
||||
it might mean that the developers are working on it.</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>See how Scott Merrill simulates a BDC behavior at
|
||||
<A
|
||||
HREF="http://www.skippy.net/linux/smb-howto.html"
|
||||
TARGET="_top"
|
||||
> http://www.skippy.net/linux/smb-howto.html</A
|
||||
>. </P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>Although 2.0.7 has almost had its day as a PDC, David Bannon will
|
||||
keep the 2.0.7 PDC pages at <A
|
||||
HREF="http://bioserve.latrobe.edu.au/samba"
|
||||
TARGET="_top"
|
||||
> http://bioserve.latrobe.edu.au/samba</A
|
||||
> going for a while yet.</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>Misc links to CIFS information
|
||||
<A
|
||||
HREF="http://samba.org/cifs/"
|
||||
TARGET="_top"
|
||||
>http://samba.org/cifs/</A
|
||||
></P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>NT Domains for Unix <A
|
||||
HREF="http://mailhost.cb1.com/~lkcl/ntdom/"
|
||||
TARGET="_top"
|
||||
> http://mailhost.cb1.com/~lkcl/ntdom/</A
|
||||
></P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>FTP site for older SMB specs:
|
||||
<A
|
||||
HREF="ftp://ftp.microsoft.com/developr/drg/CIFS/"
|
||||
TARGET="_top"
|
||||
> ftp://ftp.microsoft.com/developr/drg/CIFS/</A
|
||||
></P
|
||||
></LI
|
||||
></UL
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN5072"
|
||||
>34.4. Getting help from the mailing lists</A
|
||||
></H1
|
||||
><P
|
||||
>There are a number of Samba related mailing lists. Go to <A
|
||||
HREF="http://samba.org"
|
||||
TARGET="_top"
|
||||
>http://samba.org</A
|
||||
>, click on your nearest mirror
|
||||
and then click on <B
|
||||
CLASS="COMMAND"
|
||||
>Support</B
|
||||
> and then click on <B
|
||||
CLASS="COMMAND"
|
||||
>Samba related mailing lists</B
|
||||
>.</P
|
||||
><P
|
||||
>For questions relating to Samba TNG go to
|
||||
<A
|
||||
HREF="http://www.samba-tng.org/"
|
||||
TARGET="_top"
|
||||
>http://www.samba-tng.org/</A
|
||||
>
|
||||
it might mean that the developers are working on it.</p></li><li><p>See how Scott Merrill simulates a BDC behavior at
|
||||
<a href="http://www.skippy.net/linux/smb-howto.html" target="_top">
|
||||
http://www.skippy.net/linux/smb-howto.html</a>. </p></li><li><p>Although 2.0.7 has almost had its day as a PDC, David Bannon will
|
||||
keep the 2.0.7 PDC pages at <a href="http://bioserve.latrobe.edu.au/samba" target="_top">
|
||||
http://bioserve.latrobe.edu.au/samba</a> going for a while yet.</p></li><li><p>Misc links to CIFS information
|
||||
<a href="http://samba.org/cifs/" target="_top">http://samba.org/cifs/</a></p></li><li><p>NT Domains for Unix <a href="http://mailhost.cb1.com/~lkcl/ntdom/" target="_top">
|
||||
http://mailhost.cb1.com/~lkcl/ntdom/</a></p></li><li><p>FTP site for older SMB specs:
|
||||
<a href="ftp://ftp.microsoft.com/developr/drg/CIFS/" target="_top">
|
||||
ftp://ftp.microsoft.com/developr/drg/CIFS/</a></p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2904239"></a>Getting help from the mailing lists</h2></div></div><p>
|
||||
There are a number of Samba related mailing lists. Go to <a href="http://samba.org" target="_top">http://samba.org</a>, click on your nearest mirror
|
||||
and then click on <b>Support</b> and then click on <b>
|
||||
Samba related mailing lists</b>.
|
||||
</p><p>
|
||||
For questions relating to Samba TNG go to
|
||||
<a href="http://www.samba-tng.org/" target="_top">http://www.samba-tng.org/</a>
|
||||
It has been requested that you don't post questions about Samba-TNG to the
|
||||
main stream Samba lists.</P
|
||||
><P
|
||||
>If you post a message to one of the lists please observe the following guide lines :</P
|
||||
><P
|
||||
></P
|
||||
><UL
|
||||
><LI
|
||||
><P
|
||||
> Always remember that the developers are volunteers, they are
|
||||
main stream Samba lists.</p><p>
|
||||
If you post a message to one of the lists please observe the following guide lines :
|
||||
</p><div class="itemizedlist"><ul type="disc"><li><p> Always remember that the developers are volunteers, they are
|
||||
not paid and they never guarantee to produce a particular feature at
|
||||
a particular time. Any time lines are 'best guess' and nothing more.</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
> Always mention what version of samba you are using and what
|
||||
a particular time. Any time lines are 'best guess' and nothing more.
|
||||
</p></li><li><p> Always mention what version of samba you are using and what
|
||||
operating system its running under. You should probably list the
|
||||
relevant sections of your <TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf</TT
|
||||
> file, at least the options
|
||||
in [global] that affect PDC support.</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>In addition to the version, if you obtained Samba via
|
||||
CVS mention the date when you last checked it out.</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
> Try and make your question clear and brief, lots of long,
|
||||
relevant sections of your <tt>smb.conf</tt> file, at least the options
|
||||
in [global] that affect PDC support.</p></li><li><p>In addition to the version, if you obtained Samba via
|
||||
CVS mention the date when you last checked it out.</p></li><li><p> Try and make your question clear and brief, lots of long,
|
||||
convoluted questions get deleted before they are completely read !
|
||||
Don't post html encoded messages (if you can select colour or font
|
||||
size its html).</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
> If you run one of those nifty 'I'm on holidays' things when
|
||||
you are away, make sure its configured to not answer mailing lists.</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
> Don't cross post. Work out which is the best list to post to
|
||||
size its html).</p></li><li><p> If you run one of those nifty 'I'm on holidays' things when
|
||||
you are away, make sure its configured to not answer mailing lists.
|
||||
</p></li><li><p> Don't cross post. Work out which is the best list to post to
|
||||
and see what happens, i.e. don't post to both samba-ntdom and samba-technical.
|
||||
Many people active on the lists subscribe to more
|
||||
than one list and get annoyed to see the same message two or more times.
|
||||
Often someone will see a message and thinking it would be better dealt
|
||||
with on another, will forward it on for you.</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>You might include <SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>partial</I
|
||||
></SPAN
|
||||
>
|
||||
with on another, will forward it on for you.</p></li><li><p>You might include <span class="emphasis"><em>partial</em></span>
|
||||
log files written at a debug level set to as much as 20.
|
||||
Please don't send the entire log but enough to give the context of the
|
||||
error messages.</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>(Possibly) If you have a complete netmon trace ( from the opening of
|
||||
the pipe to the error ) you can send the *.CAP file as well.</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>Please think carefully before attaching a document to an email.
|
||||
error messages.</p></li><li><p>(Possibly) If you have a complete netmon trace ( from the opening of
|
||||
the pipe to the error ) you can send the *.CAP file as well.</p></li><li><p>Please think carefully before attaching a document to an email.
|
||||
Consider pasting the relevant parts into the body of the message. The samba
|
||||
mailing lists go to a huge number of people, do they all need a copy of your
|
||||
smb.conf in their attach directory?</P
|
||||
></LI
|
||||
></UL
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN5102"
|
||||
>34.5. How to get off the mailinglists</A
|
||||
></H1
|
||||
><P
|
||||
>To have your name removed from a samba mailing list, go to the
|
||||
same place you went to to get on it. Go to <A
|
||||
HREF="http://lists.samba.org/"
|
||||
TARGET="_top"
|
||||
>http://lists.samba.org</A
|
||||
>,
|
||||
click on your nearest mirror and then click on <B
|
||||
CLASS="COMMAND"
|
||||
>Support</B
|
||||
> and
|
||||
then click on <B
|
||||
CLASS="COMMAND"
|
||||
> Samba related mailing lists</B
|
||||
>. Or perhaps see
|
||||
<A
|
||||
HREF="http://lists.samba.org/mailman/roster/samba-ntdom"
|
||||
TARGET="_top"
|
||||
>here</A
|
||||
></P
|
||||
><P
|
||||
>Please don't post messages to the list asking to be removed, you will just
|
||||
be referred to the above address (unless that process failed in some way...)</P
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="NAVFOOTER"
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"><TABLE
|
||||
SUMMARY="Footer navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="diagnosis.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="samba-howto-collection.html"
|
||||
ACCESSKEY="H"
|
||||
>Home</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="bugreport.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
>The samba checklist</TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="appendixes.html"
|
||||
ACCESSKEY="U"
|
||||
>Up</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
>Reporting Bugs</TD
|
||||
></TR
|
||||
></TABLE
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
smb.conf in their attach directory?</p></li></ul></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2904392"></a>How to get off the mailinglists</h2></div></div><p>To have your name removed from a samba mailing list, go to the
|
||||
same place you went to to get on it. Go to <a href="http://lists.samba.org/" target="_top">http://lists.samba.org</a>,
|
||||
click on your nearest mirror and then click on <b>Support</b> and
|
||||
then click on <b> Samba related mailing lists</b>. Or perhaps see
|
||||
<a href="http://lists.samba.org/mailman/roster/samba-ntdom" target="_top">here</a>
|
||||
</p><p>
|
||||
Please don't post messages to the list asking to be removed, you will just
|
||||
be referred to the above address (unless that process failed in some way...)
|
||||
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="diagnosis.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="troubleshooting.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="bugreport.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 27. The samba checklist </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 29. Reporting Bugs</td></tr></table></div></body></html>
|
||||
|
||||
@ -1,139 +1,12 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>profiles</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="PROFILES.1"
|
||||
></A
|
||||
>profiles</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>profiles -- A utility to report and change SIDs in registry files
|
||||
</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>profiles</B
|
||||
> [-v] [-c SID] [-n SID] {file}</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN15"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
>This tool is part of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
> suite.</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>profiles</B
|
||||
> is a utility that
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>profiles</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="profiles.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>profiles — A utility to report and change SIDs in registry files
|
||||
</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>profiles</tt> [-v] [-c SID] [-n SID] {file}</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>profiles</b> is a utility that
|
||||
reports and changes SIDs in windows registry files. It currently only
|
||||
supports NT.
|
||||
</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN23"
|
||||
></A
|
||||
><H2
|
||||
>OPTIONS</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>file</DT
|
||||
><DD
|
||||
><P
|
||||
>Registry file to view or edit. </P
|
||||
></DD
|
||||
><DT
|
||||
>-v,--verbose</DT
|
||||
><DD
|
||||
><P
|
||||
>Increases verbosity of messages.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-c SID1 -n SID2</DT
|
||||
><DD
|
||||
><P
|
||||
>Change all occurences of SID1 in <TT
|
||||
CLASS="FILENAME"
|
||||
>file</TT
|
||||
> by SID2.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-h|--help</DT
|
||||
><DD
|
||||
><P
|
||||
>Print a summary of command line options.</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN43"
|
||||
></A
|
||||
><H2
|
||||
>VERSION</H2
|
||||
><P
|
||||
>This man page is correct for version 3.0 of the Samba
|
||||
suite.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN46"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>The original Samba software and related utilities
|
||||
</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">file</span></dt><dd><p>Registry file to view or edit. </p></dd><dt><span class="term">-v,--verbose</span></dt><dd><p>Increases verbosity of messages.
|
||||
</p></dd><dt><span class="term">-c SID1 -n SID2</span></dt><dd><p>Change all occurences of SID1 in <tt>file</tt> by SID2.
|
||||
</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
|
||||
</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the Samba
|
||||
suite.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.</P
|
||||
><P
|
||||
>The profiles man page was written by Jelmer Vernooij. </P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
to the way the Linux kernel is developed.</p><p>The profiles man page was written by Jelmer Vernooij. </p></div></div></body></html>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -1,178 +1,27 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>Samba Backup Domain Controller to Samba Domain Control</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
||||
REL="HOME"
|
||||
TITLE="SAMBA Project Documentation"
|
||||
HREF="samba-howto-collection.html"><LINK
|
||||
REL="UP"
|
||||
TITLE="Type of installation"
|
||||
HREF="type.html"><LINK
|
||||
REL="PREVIOUS"
|
||||
TITLE="Samba as an NT4 or Win2k Primary Domain Controller"
|
||||
HREF="samba-pdc.html"><LINK
|
||||
REL="NEXT"
|
||||
TITLE="Samba as a ADS domain member"
|
||||
HREF="ads.html"></HEAD
|
||||
><BODY
|
||||
CLASS="CHAPTER"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><DIV
|
||||
CLASS="NAVHEADER"
|
||||
><TABLE
|
||||
SUMMARY="Header navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TH
|
||||
COLSPAN="3"
|
||||
ALIGN="center"
|
||||
>SAMBA Project Documentation</TH
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="left"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="samba-pdc.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="80%"
|
||||
ALIGN="center"
|
||||
VALIGN="bottom"
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="right"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="ads.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
></TABLE
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"></DIV
|
||||
><DIV
|
||||
CLASS="CHAPTER"
|
||||
><H1
|
||||
><A
|
||||
NAME="SAMBA-BDC"
|
||||
></A
|
||||
>Chapter 8. Samba Backup Domain Controller to Samba Domain Control</H1
|
||||
><DIV
|
||||
CLASS="TOC"
|
||||
><DL
|
||||
><DT
|
||||
><B
|
||||
>Table of Contents</B
|
||||
></DT
|
||||
><DT
|
||||
>8.1. <A
|
||||
HREF="samba-bdc.html#AEN1293"
|
||||
>Prerequisite Reading</A
|
||||
></DT
|
||||
><DT
|
||||
>8.2. <A
|
||||
HREF="samba-bdc.html#AEN1297"
|
||||
>Background</A
|
||||
></DT
|
||||
><DT
|
||||
>8.3. <A
|
||||
HREF="samba-bdc.html#AEN1305"
|
||||
>What qualifies a Domain Controller on the network?</A
|
||||
></DT
|
||||
><DD
|
||||
><DL
|
||||
><DT
|
||||
>8.3.1. <A
|
||||
HREF="samba-bdc.html#AEN1308"
|
||||
>How does a Workstation find its domain controller?</A
|
||||
></DT
|
||||
><DT
|
||||
>8.3.2. <A
|
||||
HREF="samba-bdc.html#AEN1311"
|
||||
>When is the PDC needed?</A
|
||||
></DT
|
||||
></DL
|
||||
></DD
|
||||
><DT
|
||||
>8.4. <A
|
||||
HREF="samba-bdc.html#AEN1314"
|
||||
>Can Samba be a Backup Domain Controller to an NT PDC?</A
|
||||
></DT
|
||||
><DT
|
||||
>8.5. <A
|
||||
HREF="samba-bdc.html#AEN1319"
|
||||
>How do I set up a Samba BDC?</A
|
||||
></DT
|
||||
><DD
|
||||
><DL
|
||||
><DT
|
||||
>8.5.1. <A
|
||||
HREF="samba-bdc.html#AEN1336"
|
||||
>How do I replicate the smbpasswd file?</A
|
||||
></DT
|
||||
><DT
|
||||
>8.5.2. <A
|
||||
HREF="samba-bdc.html#AEN1340"
|
||||
>Can I do this all with LDAP?</A
|
||||
></DT
|
||||
></DL
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN1293"
|
||||
>8.1. Prerequisite Reading</A
|
||||
></H1
|
||||
><P
|
||||
>Before you continue reading in this chapter, please make sure
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 6.
|
||||
Samba Backup Domain Controller to Samba Domain Control
|
||||
</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="type.html" title="Part II. Server Configuration Basics"><link rel="previous" href="samba-pdc.html" title="Chapter 5.
|
||||
Samba as an NT4 or Win2k Primary Domain Controller
|
||||
"><link rel="next" href="ADS.html" title="Chapter 7. Samba as a ADS domain member"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 6.
|
||||
Samba Backup Domain Controller to Samba Domain Control
|
||||
</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="samba-pdc.html">Prev</a> </td><th width="60%" align="center">Part II. Server Configuration Basics</th><td width="20%" align="right"> <a accesskey="n" href="ADS.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="samba-bdc"></a>Chapter 6.
|
||||
Samba Backup Domain Controller to Samba Domain Control
|
||||
</h2></div><div><div class="author"><h3 class="author">Volker Lendecke</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:Volker.Lendecke@SerNet.DE">Volker.Lendecke@SerNet.DE</a>></tt></p></div></div></div></div><div><p class="pubdate"> (26 Apr 2001) </p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="samba-bdc.html#id2807541">Prerequisite Reading</a></dt><dt><a href="samba-bdc.html#id2877190">Background</a></dt><dt><a href="samba-bdc.html#id2879061">What qualifies a Domain Controller on the network?</a></dt><dd><dl><dt><a href="samba-bdc.html#id2879083">How does a Workstation find its domain controller?</a></dt><dt><a href="samba-bdc.html#id2879107">When is the PDC needed?</a></dt></dl></dd><dt><a href="samba-bdc.html#id2879127">Can Samba be a Backup Domain Controller to an NT PDC?</a></dt><dt><a href="samba-bdc.html#id2879160">How do I set up a Samba BDC?</a></dt><dd><dl><dt><a href="samba-bdc.html#id2879257">How do I replicate the smbpasswd file?</a></dt><dt><a href="samba-bdc.html#id2879286">Can I do this all with LDAP?</a></dt></dl></dd></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2807541"></a>Prerequisite Reading</h2></div></div><p>
|
||||
Before you continue reading in this chapter, please make sure
|
||||
that you are comfortable with configuring a Samba PDC
|
||||
as described in the <A
|
||||
HREF="Samba-PDC-HOWTO.html"
|
||||
TARGET="_top"
|
||||
>Samba-PDC-HOWTO</A
|
||||
>.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN1297"
|
||||
>8.2. Background</A
|
||||
></H1
|
||||
><P
|
||||
>What is a Domain Controller? It is a machine that is able to answer
|
||||
as described in the <a href="Samba-PDC-HOWTO.html" target="_top">Samba-PDC-HOWTO</a>.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2877190"></a>Background</h2></div></div><p>
|
||||
What is a Domain Controller? It is a machine that is able to answer
|
||||
logon requests from workstations in a Windows NT Domain. Whenever a
|
||||
user logs into a Windows NT Workstation, the workstation connects to a
|
||||
Domain Controller and asks him whether the username and password the
|
||||
user typed in is correct. The Domain Controller replies with a lot of
|
||||
information about the user, for example the place where the users
|
||||
profile is stored, the users full name of the user. All this
|
||||
information is stored in the NT user database, the so-called SAM.</P
|
||||
><P
|
||||
>There are two kinds of Domain Controller in a NT 4 compatible Domain:
|
||||
information is stored in the NT user database, the so-called SAM.
|
||||
</p><p>
|
||||
There are two kinds of Domain Controller in a NT 4 compatible Domain:
|
||||
A Primary Domain Controller (PDC) and one or more Backup Domain
|
||||
Controllers (BDC). The PDC contains the master copy of the
|
||||
SAM. Whenever the SAM has to change, for example when a user changes
|
||||
@ -181,51 +30,31 @@ Controller is a machine that maintains a read-only copy of the
|
||||
SAM. This way it is able to reply to logon requests and authenticate
|
||||
users in case the PDC is not available. During this time no changes to
|
||||
the SAM are possible. Whenever changes to the SAM are done on the PDC,
|
||||
all BDC receive the changes from the PDC.</P
|
||||
><P
|
||||
>Since version 2.2 Samba officially supports domain logons for all
|
||||
all BDC receive the changes from the PDC.
|
||||
</p><p>
|
||||
Since version 2.2 Samba officially supports domain logons for all
|
||||
current Windows Clients, including Windows 2000 and XP. This text
|
||||
assumes the domain to be named SAMBA. To be able to act as a PDC, some
|
||||
parameters in the [global]-section of the smb.conf have to be set:</P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
>workgroup = SAMBA
|
||||
domain master = yes
|
||||
domain logons = yes</PRE
|
||||
></P
|
||||
><P
|
||||
>Several other things like a [homes] and a [netlogon] share also may be
|
||||
parameters in the [global]-section of the smb.conf have to be set:
|
||||
</p><pre class="programlisting">
|
||||
workgroup = SAMBA
|
||||
domain master = yes
|
||||
domain logons = yes
|
||||
</pre><p>
|
||||
Several other things like a [homes] and a [netlogon] share also may be
|
||||
set along with settings for the profile path, the users home drive and
|
||||
others. This will not be covered in this document.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN1305"
|
||||
>8.3. What qualifies a Domain Controller on the network?</A
|
||||
></H1
|
||||
><P
|
||||
>Every machine that is a Domain Controller for the domain SAMBA has to
|
||||
others. This will not be covered in this document.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2879061"></a>What qualifies a Domain Controller on the network?</h2></div></div><p>
|
||||
Every machine that is a Domain Controller for the domain SAMBA has to
|
||||
register the NetBIOS group name SAMBA#1c with the WINS server and/or
|
||||
by broadcast on the local network. The PDC also registers the unique
|
||||
NetBIOS name SAMBA#1b with the WINS server. The name type #1b is
|
||||
normally reserved for the domain master browser, a role that has
|
||||
nothing to do with anything related to authentication, but the
|
||||
Microsoft Domain implementation requires the domain master browser to
|
||||
be on the same machine as the PDC.</P
|
||||
><DIV
|
||||
CLASS="SECT2"
|
||||
><H2
|
||||
CLASS="SECT2"
|
||||
><A
|
||||
NAME="AEN1308"
|
||||
>8.3.1. How does a Workstation find its domain controller?</A
|
||||
></H2
|
||||
><P
|
||||
>A NT workstation in the domain SAMBA that wants a local user to be
|
||||
be on the same machine as the PDC.
|
||||
</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2879083"></a>How does a Workstation find its domain controller?</h3></div></div><p>
|
||||
A NT workstation in the domain SAMBA that wants a local user to be
|
||||
authenticated has to find the domain controller for SAMBA. It does
|
||||
this by doing a NetBIOS name query for the group name SAMBA#1c. It
|
||||
assumes that each of the machines it gets back from the queries is a
|
||||
@ -233,214 +62,87 @@ domain controller and can answer logon requests. To not open security
|
||||
holes both the workstation and the selected (TODO: How is the DC
|
||||
chosen) domain controller authenticate each other. After that the
|
||||
workstation sends the user's credentials (his name and password) to
|
||||
the domain controller, asking for approval.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT2"
|
||||
><H2
|
||||
CLASS="SECT2"
|
||||
><A
|
||||
NAME="AEN1311"
|
||||
>8.3.2. When is the PDC needed?</A
|
||||
></H2
|
||||
><P
|
||||
>Whenever a user wants to change his password, this has to be done on
|
||||
the domain controller, asking for approval.
|
||||
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2879107"></a>When is the PDC needed?</h3></div></div><p>
|
||||
Whenever a user wants to change his password, this has to be done on
|
||||
the PDC. To find the PDC, the workstation does a NetBIOS name query
|
||||
for SAMBA#1b, assuming this machine maintains the master copy of the
|
||||
SAM. The workstation contacts the PDC, both mutually authenticate and
|
||||
the password change is done.</P
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN1314"
|
||||
>8.4. Can Samba be a Backup Domain Controller to an NT PDC?</A
|
||||
></H1
|
||||
><P
|
||||
>With version 2.2, no. The native NT SAM replication protocols have
|
||||
the password change is done.
|
||||
</p></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2879127"></a>Can Samba be a Backup Domain Controller to an NT PDC?</h2></div></div><p>
|
||||
With version 2.2, no. The native NT SAM replication protocols have
|
||||
not yet been fully implemented. The Samba Team is working on
|
||||
understanding and implementing the protocols, but this work has not
|
||||
been finished for version 2.2.</P
|
||||
><P
|
||||
>With version 3.0, the work on both the replication protocols and a
|
||||
been finished for version 2.2.
|
||||
</p><p>
|
||||
With version 3.0, the work on both the replication protocols and a
|
||||
suitable storage mechanism has progressed, and some form of NT4 BDC
|
||||
support is expected soon.</P
|
||||
><P
|
||||
>Can I get the benefits of a BDC with Samba? Yes. The main reason for
|
||||
support is expected soon.
|
||||
</p><p>
|
||||
Can I get the benefits of a BDC with Samba? Yes. The main reason for
|
||||
implementing a BDC is availability. If the PDC is a Samba machine,
|
||||
a second Samba machine can be set up to
|
||||
service logon requests whenever the PDC is down.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN1319"
|
||||
>8.5. How do I set up a Samba BDC?</A
|
||||
></H1
|
||||
><P
|
||||
>Several things have to be done:</P
|
||||
><P
|
||||
></P
|
||||
><UL
|
||||
><LI
|
||||
><P
|
||||
>The domain SID has to be the same on the PDC and the BDC. This used to
|
||||
service logon requests whenever the PDC is down.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2879160"></a>How do I set up a Samba BDC?</h2></div></div><p>
|
||||
Several things have to be done:
|
||||
</p><div class="itemizedlist"><ul type="disc"><li><p>
|
||||
The domain SID has to be the same on the PDC and the BDC. This used to
|
||||
be stored in the file private/MACHINE.SID. This file is not created
|
||||
anymore since Samba 2.2.5 or even earlier. Nowadays the domain SID is
|
||||
stored in the file private/secrets.tdb. Simply copying the secrets.tdb
|
||||
from the PDC to the BDC does not work, as the BDC would
|
||||
generate a new SID for itself and override the domain SID with this
|
||||
new BDC SID.</P
|
||||
><P
|
||||
>To retrieve the domain SID from the PDC or an existing BDC and store it in the
|
||||
secrets.tdb, execute 'net rpc getsid' on the BDC.</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>The Unix user database has to be synchronized from the PDC to the
|
||||
new BDC SID.</p><p>
|
||||
To retrieve the domain SID from the PDC or an existing BDC and store it in the
|
||||
secrets.tdb, execute 'net rpc getsid' on the BDC.
|
||||
</p></li><li><p>
|
||||
The Unix user database has to be synchronized from the PDC to the
|
||||
BDC. This means that both the /etc/passwd and /etc/group have to be
|
||||
replicated from the PDC to the BDC. This can be done manually
|
||||
whenever changes are made, or the PDC is set up as a NIS master
|
||||
server and the BDC as a NIS slave server. To set up the BDC as a
|
||||
mere NIS client would not be enough, as the BDC would not be able to
|
||||
access its user database in case of a PDC failure.</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>The Samba password database in the file private/smbpasswd has to be
|
||||
access its user database in case of a PDC failure.
|
||||
</p></li><li><p>
|
||||
The Samba password database in the file private/smbpasswd has to be
|
||||
replicated from the PDC to the BDC. This is a bit tricky, see the
|
||||
next section.</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>Any netlogon share has to be replicated from the PDC to the
|
||||
next section.
|
||||
</p></li><li><p>
|
||||
Any netlogon share has to be replicated from the PDC to the
|
||||
BDC. This can be done manually whenever login scripts are changed,
|
||||
or it can be done automatically together with the smbpasswd
|
||||
synchronization.</P
|
||||
></LI
|
||||
></UL
|
||||
><P
|
||||
>Finally, the BDC has to be found by the workstations. This can be done
|
||||
by setting</P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
>workgroup = samba
|
||||
domain master = no
|
||||
domain logons = yes</PRE
|
||||
></P
|
||||
><P
|
||||
>in the [global]-section of the smb.conf of the BDC. This makes the BDC
|
||||
synchronization.
|
||||
</p></li></ul></div><p>
|
||||
Finally, the BDC has to be found by the workstations. This can be done
|
||||
by setting
|
||||
</p><pre class="programlisting">
|
||||
workgroup = samba
|
||||
domain master = no
|
||||
domain logons = yes
|
||||
</pre><p>
|
||||
in the [global]-section of the smb.conf of the BDC. This makes the BDC
|
||||
only register the name SAMBA#1c with the WINS server. This is no
|
||||
problem as the name SAMBA#1c is a NetBIOS group name that is meant to
|
||||
be registered by more than one machine. The parameter 'domain master =
|
||||
no' forces the BDC not to register SAMBA#1b which as a unique NetBIOS
|
||||
name is reserved for the Primary Domain Controller.</P
|
||||
><DIV
|
||||
CLASS="SECT2"
|
||||
><H2
|
||||
CLASS="SECT2"
|
||||
><A
|
||||
NAME="AEN1336"
|
||||
>8.5.1. How do I replicate the smbpasswd file?</A
|
||||
></H2
|
||||
><P
|
||||
>Replication of the smbpasswd file is sensitive. It has to be done
|
||||
name is reserved for the Primary Domain Controller.
|
||||
</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2879257"></a>How do I replicate the smbpasswd file?</h3></div></div><p>
|
||||
Replication of the smbpasswd file is sensitive. It has to be done
|
||||
whenever changes to the SAM are made. Every user's password change is
|
||||
done in the smbpasswd file and has to be replicated to the BDC. So
|
||||
replicating the smbpasswd file very often is necessary.</P
|
||||
><P
|
||||
>As the smbpasswd file contains plain text password equivalents, it
|
||||
replicating the smbpasswd file very often is necessary.
|
||||
</p><p>
|
||||
As the smbpasswd file contains plain text password equivalents, it
|
||||
must not be sent unencrypted over the wire. The best way to set up
|
||||
smbpasswd replication from the PDC to the BDC is to use the utility
|
||||
rsync. rsync can use ssh as a transport. ssh itself can be set up to
|
||||
accept *only* rsync transfer without requiring the user to type a
|
||||
password.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT2"
|
||||
><H2
|
||||
CLASS="SECT2"
|
||||
><A
|
||||
NAME="AEN1340"
|
||||
>8.5.2. Can I do this all with LDAP?</A
|
||||
></H2
|
||||
><P
|
||||
>The simple answer is YES. Samba's pdb_ldap code supports
|
||||
password.
|
||||
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2879286"></a>Can I do this all with LDAP?</h3></div></div><p>The simple answer is YES. Samba's pdb_ldap code supports
|
||||
binding to a replica LDAP server, and will also follow referrals and
|
||||
rebind to the master if it ever needs to make a modification to the
|
||||
database. (Normally BDCs are read only, so this will not occur
|
||||
often).</P
|
||||
></DIV
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="NAVFOOTER"
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"><TABLE
|
||||
SUMMARY="Footer navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="samba-pdc.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="samba-howto-collection.html"
|
||||
ACCESSKEY="H"
|
||||
>Home</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="ads.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
>Samba as an NT4 or Win2k Primary Domain Controller</TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="type.html"
|
||||
ACCESSKEY="U"
|
||||
>Up</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
>Samba as a ADS domain member</TD
|
||||
></TR
|
||||
></TABLE
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
often).
|
||||
</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="samba-pdc.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="type.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ADS.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 5.
|
||||
Samba as an NT4 or Win2k Primary Domain Controller
|
||||
</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 7. Samba as a ADS domain member</td></tr></table></div></body></html>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -1,756 +1,116 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>samba</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="SAMBA.7"
|
||||
></A
|
||||
>samba</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>Samba -- A Windows SMB/CIFS fileserver for UNIX</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>Samba</B
|
||||
> </P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN11"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
>The Samba software suite is a collection of programs
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>samba</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="samba.7"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>Samba — A Windows SMB/CIFS fileserver for UNIX</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>Samba</tt> </p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><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). For a
|
||||
more thorough description, see <A
|
||||
HREF="http://www.ubiqx.org/cifs/"
|
||||
TARGET="_top"
|
||||
> http://www.ubiqx.org/cifs/</A
|
||||
>. Samba also implements the NetBIOS
|
||||
protocol in nmbd.</P
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbd</SPAN
|
||||
>(8)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>The <B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
> daemon provides the file and print services to
|
||||
more thorough description, see <a href="http://www.ubiqx.org/cifs/" target="_top">
|
||||
http://www.ubiqx.org/cifs/</a>. Samba also implements the NetBIOS
|
||||
protocol in nmbd.</p><div class="variablelist"><dl><dt><span class="term"><a href="smbd.8.html">smbd(8)</a></span></dt><dd><p>The <b>smbd</b> 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 <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
>
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>nmbd</SPAN
|
||||
>(8)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>The <B
|
||||
CLASS="COMMAND"
|
||||
>nmbd</B
|
||||
>
|
||||
for this daemon is described in <a href="smb.conf.5.html">smb.conf(5)</a>
|
||||
</p></dd><dt><span class="term"><a href="nmbd.8.html">nmbd(8)</a></span></dt><dd><p>The <b>nmbd</b>
|
||||
daemon provides NetBIOS nameservice and browsing
|
||||
support. The configuration file for this daemon
|
||||
is described in <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
></P
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbclient</SPAN
|
||||
>(1)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>The <B
|
||||
CLASS="COMMAND"
|
||||
>smbclient</B
|
||||
>
|
||||
is described in <a href="smb.conf.5.html">smb.conf(5)</a></p></dd><dt><span class="term"><a href="smbclient.1.html">smbclient(1)</a></span></dt><dd><p>The <b>smbclient</b>
|
||||
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
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>testparm</SPAN
|
||||
>(1)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>The <B
|
||||
CLASS="COMMAND"
|
||||
>testparm</B
|
||||
>
|
||||
utility is a simple syntax checker for Samba's <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> configuration file.</P
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>testprns</SPAN
|
||||
>(1)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>The <B
|
||||
CLASS="COMMAND"
|
||||
>testprns</B
|
||||
>
|
||||
any SMB server (such as a PC running Windows NT).</p></dd><dt><span class="term"><a href="testparm.1.html">testparm(1)</a></span></dt><dd><p>The <b>testparm</b>
|
||||
utility is a simple syntax checker for Samba's <a href="smb.conf.5.html">smb.conf(5)</a> configuration file.</p></dd><dt><span class="term"><a href="testprns.1.html">testprns(1)</a></span></dt><dd><p>The <b>testprns</b>
|
||||
utility supports testing printer names defined
|
||||
in your <TT
|
||||
CLASS="FILENAME"
|
||||
>printcap</TT
|
||||
> file used
|
||||
by Samba.</P
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbstatus</SPAN
|
||||
>(1)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>The <B
|
||||
CLASS="COMMAND"
|
||||
>smbstatus</B
|
||||
>
|
||||
in your <tt>printcap</tt> file used
|
||||
by Samba.</p></dd><dt><span class="term"><a href="smbstatus.1.html">smbstatus(1)</a></span></dt><dd><p>The <b>smbstatus</b>
|
||||
tool provides access to information about the
|
||||
current connections to <B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
>.</P
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>nmblookup</SPAN
|
||||
>(1)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>The <B
|
||||
CLASS="COMMAND"
|
||||
>nmblookup</B
|
||||
>
|
||||
current connections to <b>smbd</b>.</p></dd><dt><span class="term"><a href="nmblookup.1.html">nmblookup(1)</a></span></dt><dd><p>The <b>nmblookup</b>
|
||||
tools allows NetBIOS name queries to be made
|
||||
from a UNIX host.</P
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbgroupedit</SPAN
|
||||
>(8)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>The <B
|
||||
CLASS="COMMAND"
|
||||
>smbgroupedit</B
|
||||
>
|
||||
from a UNIX host.</p></dd><dt><span class="term"><a href="smbgroupedit.8.html">smbgroupedit(8)</a></span></dt><dd><p>The <b>smbgroupedit</b>
|
||||
tool allows for mapping unix groups to NT Builtin,
|
||||
Domain, or Local groups. Also it allows setting
|
||||
priviledges for that group, such as saAddUser, etc.</P
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbpasswd</SPAN
|
||||
>(8)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>The <B
|
||||
CLASS="COMMAND"
|
||||
>smbpasswd</B
|
||||
>
|
||||
priviledges for that group, such as saAddUser, etc.</p></dd><dt><span class="term"><a href="smbpasswd.8.html">smbpasswd(8)</a></span></dt><dd><p>The <b>smbpasswd</b>
|
||||
command is a tool for changing LanMan and Windows NT
|
||||
password hashes on Samba and Windows NT servers.</P
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbcacls</SPAN
|
||||
>(1)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>The <B
|
||||
CLASS="COMMAND"
|
||||
>smbcacls</B
|
||||
> command is
|
||||
a tool to set ACL's on remote CIFS servers. </P
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbsh</SPAN
|
||||
>(1)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>The <B
|
||||
CLASS="COMMAND"
|
||||
>smbsh</B
|
||||
> command is
|
||||
password hashes on Samba and Windows NT servers.</p></dd><dt><span class="term"><a href="smbcacls.1.html">smbcacls(1)</a></span></dt><dd><p>The <b>smbcacls</b> command is
|
||||
a tool to set ACL's on remote CIFS servers. </p></dd><dt><span class="term"><a href="smbsh.1.html">smbsh(1)</a></span></dt><dd><p>The <b>smbsh</b> command is
|
||||
a program that allows you to run a unix shell with
|
||||
with an overloaded VFS.</P
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbtree</SPAN
|
||||
>(1)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>The <B
|
||||
CLASS="COMMAND"
|
||||
>smbtree</B
|
||||
> command
|
||||
is a text-based network neighborhood tool.</P
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbtar</SPAN
|
||||
>(1)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>The <B
|
||||
CLASS="COMMAND"
|
||||
>smbtar</B
|
||||
> can make
|
||||
backups of data on CIFS/SMB servers.</P
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbspool</SPAN
|
||||
>(8)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbspool</B
|
||||
> is a
|
||||
with an overloaded VFS.</p></dd><dt><span class="term"><a href="smbtree.1.html">smbtree(1)</a></span></dt><dd><p>The <b>smbtree</b> command
|
||||
is a text-based network neighborhood tool.</p></dd><dt><span class="term"><a href="smbtar.1.html">smbtar(1)</a></span></dt><dd><p>The <b>smbtar</b> can make
|
||||
backups of data on CIFS/SMB servers.</p></dd><dt><span class="term"><a href="smbspool.8.html">smbspool(8)</a></span></dt><dd><p><b>smbspool</b> is a
|
||||
helper utility for printing on printers connected
|
||||
to CIFS servers. </P
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbcontrol</SPAN
|
||||
>(1)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbcontrol</B
|
||||
> is a utility
|
||||
to CIFS servers. </p></dd><dt><span class="term"><a href="smbcontrol.1.html">smbcontrol(1)</a></span></dt><dd><p><b>smbcontrol</b> is a utility
|
||||
that can change the behaviour of running samba daemons.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>rpcclient</SPAN
|
||||
>(1)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>rpcclient</B
|
||||
> is a utility
|
||||
</p></dd><dt><span class="term"><a href="rpcclient.1.html">rpcclient(1)</a></span></dt><dd><p><b>rpcclient</b> is a utility
|
||||
that can be used to execute RPC commands on remote
|
||||
CIFS servers.</P
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>pdbedit</SPAN
|
||||
>(8)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>The <B
|
||||
CLASS="COMMAND"
|
||||
>pdbedit</B
|
||||
> command
|
||||
CIFS servers.</p></dd><dt><span class="term"><a href="pdbedit.8.html">pdbedit(8)</a></span></dt><dd><p>The <b>pdbedit</b> command
|
||||
can be used to maintain the local user database on
|
||||
a samba server.</P
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>findsmb</SPAN
|
||||
>(1)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>The <B
|
||||
CLASS="COMMAND"
|
||||
>findsmb</B
|
||||
> command
|
||||
a samba server.</p></dd><dt><span class="term"><a href="findsmb.1.html">findsmb(1)</a></span></dt><dd><p>The <b>findsmb</b> command
|
||||
can be used to find SMB servers on the local network.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>net</SPAN
|
||||
>(8)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>The <B
|
||||
CLASS="COMMAND"
|
||||
>net</B
|
||||
> command
|
||||
</p></dd><dt><span class="term"><a href="net.8.html">net(8)</a></span></dt><dd><p>The <b>net</b> command
|
||||
is supposed to work similar to the DOS/Windows
|
||||
NET.EXE command.</P
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>swat</SPAN
|
||||
>(8)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>swat</B
|
||||
> is a web-based
|
||||
interface to configuring <TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf</TT
|
||||
>.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>winbindd</SPAN
|
||||
>(8)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>winbindd</B
|
||||
> is a daemon
|
||||
NET.EXE command.</p></dd><dt><span class="term"><a href="swat.8.html">swat(8)</a></span></dt><dd><p><b>swat</b> is a web-based
|
||||
interface to configuring <tt>smb.conf</tt>.
|
||||
</p></dd><dt><span class="term"><a href="winbindd.8.html">winbindd(8)</a></span></dt><dd><p><b>winbindd</b> is a daemon
|
||||
that is used for integrating authentication and
|
||||
the user database into unix.</P
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>wbinfo</SPAN
|
||||
>(1)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>wbinfo</B
|
||||
> is a utility
|
||||
the user database into unix.</p></dd><dt><span class="term"><a href="wbinfo.1.html">wbinfo(1)</a></span></dt><dd><p><b>wbinfo</b> is a utility
|
||||
that retrieves and stores information related to winbind.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>editreg</SPAN
|
||||
>(1)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>editreg</B
|
||||
> is a command-line
|
||||
</p></dd><dt><span class="term"><a href="editreg.1.html">editreg(1)</a></span></dt><dd><p><b>editreg</b> is a command-line
|
||||
utility that can edit windows registry files.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>profiles</SPAN
|
||||
>(1)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>profiles</B
|
||||
> is a command-line
|
||||
</p></dd><dt><span class="term"><a href="profiles.1.html">profiles(1)</a></span></dt><dd><p><b>profiles</b> is a command-line
|
||||
utility that can be used to replace all occurences of
|
||||
a certain SID with another SID.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>vfstest</SPAN
|
||||
>(1)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>vfstest</B
|
||||
> is a utility
|
||||
that can be used to test vfs modules.</P
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>ntlm_auth</SPAN
|
||||
>(1)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>ntlm_auth</B
|
||||
> is a helper-utility
|
||||
</p></dd><dt><span class="term"><a href="vfstest.1.html">vfstest(1)</a></span></dt><dd><p><b>vfstest</b> is a utility
|
||||
that can be used to test vfs modules.</p></dd><dt><span class="term"><a href="ntlm_auth.1.html">ntlm_auth(1)</a></span></dt><dd><p><b>ntlm_auth</b> is a helper-utility
|
||||
for external programs wanting to do NTLM-authentication.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbmount</SPAN
|
||||
>(8)</SPAN
|
||||
>, <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbumount</SPAN
|
||||
>(8)</SPAN
|
||||
>, <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbmount</SPAN
|
||||
>(8)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbmount</B
|
||||
>,<B
|
||||
CLASS="COMMAND"
|
||||
>smbmnt</B
|
||||
> and <B
|
||||
CLASS="COMMAND"
|
||||
>smbmnt</B
|
||||
> are commands that can be used to
|
||||
</p></dd><dt><span class="term"><a href="smbmount.8.html">smbmount(8)</a>, <a href="smbumount.8.html">smbumount(8)</a>, <a href="smbmount.8.html">smbmount(8)</a></span></dt><dd><p><b>smbmount</b>,<b>smbmnt</b> and <b>smbmnt</b> are commands that can be used to
|
||||
mount CIFS/SMB shares on Linux.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbcquotas</SPAN
|
||||
>(1)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbcquotas</B
|
||||
> is a tool that
|
||||
can set remote QUOTA's on server with NTFS 5. </P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN260"
|
||||
></A
|
||||
><H2
|
||||
>COMPONENTS</H2
|
||||
><P
|
||||
>The Samba suite is made up of several components. Each
|
||||
</p></dd><dt><span class="term"><a href="smbcquotas.1.html">smbcquotas(1)</a></span></dt><dd><p><b>smbcquotas</b> is a tool that
|
||||
can set remote QUOTA's on server with NTFS 5. </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>COMPONENTS</h2><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 and documents aren't clear enough then please visit
|
||||
<A
|
||||
HREF="http://devel.samba.org/"
|
||||
TARGET="_top"
|
||||
>http://devel.samba.org</A
|
||||
>
|
||||
for information on how to file a bug report or submit a patch.</P
|
||||
><P
|
||||
>If you require help, visit the Samba webpage at
|
||||
<A
|
||||
HREF="http://samba.org/"
|
||||
TARGET="_top"
|
||||
>http://www.samba.org/</A
|
||||
> and
|
||||
<a href="http://devel.samba.org/" target="_top">http://devel.samba.org</a>
|
||||
for information on how to file a bug report or submit a patch.</p><p>If you require help, visit the Samba webpage at
|
||||
<a href="http://samba.org/" target="_top">http://www.samba.org/</a> and
|
||||
explore the many option available to you.
|
||||
</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN266"
|
||||
></A
|
||||
><H2
|
||||
>AVAILABILITY</H2
|
||||
><P
|
||||
>The Samba software suite is licensed under the
|
||||
</p></div><div class="refsect1" lang="en"><h2>AVAILABILITY</h2><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
|
||||
><P
|
||||
>The latest version of the Samba suite can be
|
||||
please obey the terms of this license.</p><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
|
||||
><P
|
||||
>You may also find useful information about Samba
|
||||
on the newsgroup <A
|
||||
HREF="news:comp.protocols.smb"
|
||||
TARGET="_top"
|
||||
> comp.protocol.smb</A
|
||||
> and the Samba mailing
|
||||
mirror sites worldwide.</p><p>You may also find useful information about Samba
|
||||
on the newsgroup <a href="news:comp.protocols.smb" target="_top">
|
||||
comp.protocol.smb</a> and the Samba mailing
|
||||
list. Details on how to join the mailing list are given in
|
||||
the README file that comes with Samba.</P
|
||||
><P
|
||||
>If you have access to a WWW viewer (such as Mozilla
|
||||
the README file that comes with Samba.</p><p>If you have access to a WWW viewer (such as Mozilla
|
||||
or Konqueror) then you will also find lots of useful information,
|
||||
including back issues of the Samba mailing list, at
|
||||
<A
|
||||
HREF="http://lists.samba.org/"
|
||||
TARGET="_top"
|
||||
>http://lists.samba.org</A
|
||||
>.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN274"
|
||||
></A
|
||||
><H2
|
||||
>VERSION</H2
|
||||
><P
|
||||
>This man page is correct for version 3.0 of the
|
||||
Samba suite. </P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN277"
|
||||
></A
|
||||
><H2
|
||||
>CONTRIBUTIONS</H2
|
||||
><P
|
||||
>If you wish to contribute to the Samba project,
|
||||
<a href="http://lists.samba.org/" target="_top">http://lists.samba.org</a>.</p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the
|
||||
Samba suite. </p></div><div class="refsect1" lang="en"><h2>CONTRIBUTIONS</h2><p>If you wish to contribute to the Samba project,
|
||||
then I suggest you join the Samba mailing list at
|
||||
<A
|
||||
HREF="http://lists.samba.org/"
|
||||
TARGET="_top"
|
||||
>http://lists.samba.org</A
|
||||
>.
|
||||
</P
|
||||
><P
|
||||
>If you have patches to submit, visit
|
||||
<A
|
||||
HREF="http://devel.samba.org/"
|
||||
TARGET="_top"
|
||||
>http://devel.samba.org/</A
|
||||
>
|
||||
<a href="http://lists.samba.org/" target="_top">http://lists.samba.org</a>.
|
||||
</p><p>If you have patches to submit, visit
|
||||
<a href="http://devel.samba.org/" target="_top">http://devel.samba.org/</a>
|
||||
for information on how to do it properly. We prefer patches
|
||||
in <B
|
||||
CLASS="COMMAND"
|
||||
>diff -u</B
|
||||
> format.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN284"
|
||||
></A
|
||||
><H2
|
||||
>CONTRIBUTORS</H2
|
||||
><P
|
||||
>Contributors to the project are now too numerous
|
||||
in <b>diff -u</b> format.</p></div><div class="refsect1" lang="en"><h2>CONTRIBUTORS</h2><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"
|
||||
TARGET="_top"
|
||||
> ftp://samba.org/pub/samba/alpha/change-log</A
|
||||
>
|
||||
for the pre-CVS changes and at <A
|
||||
HREF="ftp://samba.org/pub/samba/alpha/cvs.log"
|
||||
TARGET="_top"
|
||||
> ftp://samba.org/pub/samba/alpha/cvs.log</A
|
||||
>
|
||||
users. To see a full list, look at <a href="ftp://samba.org/pub/samba/alpha/change-log" target="_top">
|
||||
ftp://samba.org/pub/samba/alpha/change-log</a>
|
||||
for the pre-CVS changes and at <a href="ftp://samba.org/pub/samba/alpha/cvs.log" target="_top">
|
||||
ftp://samba.org/pub/samba/alpha/cvs.log</a>
|
||||
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
|
||||
><P
|
||||
>In addition, several commercial organizations now help
|
||||
Samba. The project would have been unmanageable without it.</p><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"
|
||||
TARGET="_top"
|
||||
> http://samba.org/samba/samba-thanks.html</A
|
||||
>.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN291"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>The original Samba software and related utilities
|
||||
the Samba Web pages at <a href="http://samba.org/samba/samba-thanks.html" target="_top">
|
||||
http://samba.org/samba/samba-thanks.html</a>.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.</P
|
||||
><P
|
||||
>The original Samba man pages were written by Karl Auer.
|
||||
to the way the Linux kernel is developed.</p><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/"
|
||||
TARGET="_top"
|
||||
> ftp://ftp.icce.rug.nl/pub/unix/</A
|
||||
>) and updated for the Samba 2.0
|
||||
excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
|
||||
ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML
|
||||
4.2 for Samba 3.0 was done by Alexander Bokovoy.</P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
4.2 for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
|
||||
|
||||
@ -1,357 +1,116 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>Securing Samba</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
||||
REL="HOME"
|
||||
TITLE="SAMBA Project Documentation"
|
||||
HREF="samba-howto-collection.html"><LINK
|
||||
REL="UP"
|
||||
TITLE="Advanced Configuration"
|
||||
HREF="optional.html"><LINK
|
||||
REL="PREVIOUS"
|
||||
TITLE="Improved browsing in samba"
|
||||
HREF="improved-browsing.html"><LINK
|
||||
REL="NEXT"
|
||||
TITLE="Unicode/Charsets"
|
||||
HREF="unicode.html"></HEAD
|
||||
><BODY
|
||||
CLASS="CHAPTER"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><DIV
|
||||
CLASS="NAVHEADER"
|
||||
><TABLE
|
||||
SUMMARY="Header navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TH
|
||||
COLSPAN="3"
|
||||
ALIGN="center"
|
||||
>SAMBA Project Documentation</TH
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="left"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="improved-browsing.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="80%"
|
||||
ALIGN="center"
|
||||
VALIGN="bottom"
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="right"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="unicode.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
></TABLE
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"></DIV
|
||||
><DIV
|
||||
CLASS="CHAPTER"
|
||||
><H1
|
||||
><A
|
||||
NAME="SECURING-SAMBA"
|
||||
></A
|
||||
>Chapter 25. Securing Samba</H1
|
||||
><DIV
|
||||
CLASS="TOC"
|
||||
><DL
|
||||
><DT
|
||||
><B
|
||||
>Table of Contents</B
|
||||
></DT
|
||||
><DT
|
||||
>25.1. <A
|
||||
HREF="securing-samba.html#AEN4073"
|
||||
>Introduction</A
|
||||
></DT
|
||||
><DT
|
||||
>25.2. <A
|
||||
HREF="securing-samba.html#AEN4076"
|
||||
>Using host based protection</A
|
||||
></DT
|
||||
><DT
|
||||
>25.3. <A
|
||||
HREF="securing-samba.html#AEN4086"
|
||||
>Using interface protection</A
|
||||
></DT
|
||||
><DT
|
||||
>25.4. <A
|
||||
HREF="securing-samba.html#AEN4094"
|
||||
>Using a firewall</A
|
||||
></DT
|
||||
><DT
|
||||
>25.5. <A
|
||||
HREF="securing-samba.html#AEN4101"
|
||||
>Using a IPC$ share deny</A
|
||||
></DT
|
||||
><DT
|
||||
>25.6. <A
|
||||
HREF="securing-samba.html#AEN4110"
|
||||
>Upgrading Samba</A
|
||||
></DT
|
||||
></DL
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN4073"
|
||||
>25.1. Introduction</A
|
||||
></H1
|
||||
><P
|
||||
>This note was attached to the Samba 2.2.8 release notes as it contained an
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 24. Securing Samba</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="previous" href="integrate-ms-networks.html" title="Chapter 23. Integrating MS Windows networks with Samba"><link rel="next" href="unicode.html" title="Chapter 25. Unicode/Charsets"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 24. Securing Samba</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="integrate-ms-networks.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="unicode.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="securing-samba"></a>Chapter 24. Securing Samba</h2></div><div><div class="author"><h3 class="author">Andrew Tridgell</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:tridge@samba.org">tridge@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">John H. Terpstra</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jht@samba.org">jht@samba.org</a>></tt></p></div></div></div></div><div><p class="pubdate">17 March 2003</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="securing-samba.html#id2900501">Introduction</a></dt><dt><a href="securing-samba.html#id2900517">Using host based protection</a></dt><dt><a href="securing-samba.html#id2900967">Using interface protection</a></dt><dt><a href="securing-samba.html#id2901018">Using a firewall</a></dt><dt><a href="securing-samba.html#id2901061">Using a IPC$ share deny</a></dt><dt><a href="securing-samba.html#id2900617">NTLMv2 Security</a></dt><dt><a href="securing-samba.html#id2900653">Upgrading Samba</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2900501"></a>Introduction</h2></div></div><p>
|
||||
This note was attached to the Samba 2.2.8 release notes as it contained an
|
||||
important security fix. The information contained here applies to Samba
|
||||
installations in general.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN4076"
|
||||
>25.2. Using host based protection</A
|
||||
></H1
|
||||
><P
|
||||
>In many installations of Samba the greatest threat comes for outside
|
||||
installations in general.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2900517"></a>Using host based protection</h2></div></div><p>
|
||||
In many installations of Samba the greatest threat comes for outside
|
||||
your immediate network. By default Samba will accept connections from
|
||||
any host, which means that if you run an insecure version of Samba on
|
||||
a host that is directly connected to the Internet you can be
|
||||
especially vulnerable.</P
|
||||
><P
|
||||
>One of the simplest fixes in this case is to use the <B
|
||||
CLASS="COMMAND"
|
||||
>hosts allow</B
|
||||
> and
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>hosts deny</B
|
||||
> options in the Samba <TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf</TT
|
||||
> configuration file to only
|
||||
especially vulnerable.
|
||||
</p><p>
|
||||
One of the simplest fixes in this case is to use the <b>hosts allow</b> and
|
||||
<b>hosts deny</b> options in the Samba <tt>smb.conf</tt> configuration file to only
|
||||
allow access to your server from a specific range of hosts. An example
|
||||
might be:</P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
> hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24
|
||||
hosts deny = 0.0.0.0/0</PRE
|
||||
></P
|
||||
><P
|
||||
>The above will only allow SMB connections from 'localhost' (your own
|
||||
might be:
|
||||
</p><pre class="programlisting">
|
||||
hosts allow = 127.0.0.1 192.168.2.0/24 192.168.3.0/24
|
||||
hosts deny = 0.0.0.0/0
|
||||
</pre><p>
|
||||
The above will only allow SMB connections from 'localhost' (your own
|
||||
computer) and from the two private networks 192.168.2 and
|
||||
192.168.3. All other connections will be refused connections as soon
|
||||
192.168.3. All other connections will be refused as soon
|
||||
as the client sends its first packet. The refusal will be marked as a
|
||||
'not listening on called name' error.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN4086"
|
||||
>25.3. Using interface protection</A
|
||||
></H1
|
||||
><P
|
||||
>By default Samba will accept connections on any network interface that
|
||||
'not listening on called name' error.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2900967"></a>Using interface protection</h2></div></div><p>
|
||||
By default Samba will accept connections on any network interface that
|
||||
it finds on your system. That means if you have a ISDN line or a PPP
|
||||
connection to the Internet then Samba will accept connections on those
|
||||
links. This may not be what you want.</P
|
||||
><P
|
||||
>You can change this behaviour using options like the following:</P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
> interfaces = eth* lo
|
||||
bind interfaces only = yes</PRE
|
||||
></P
|
||||
><P
|
||||
>This tells Samba to only listen for connections on interfaces with a
|
||||
links. This may not be what you want.
|
||||
</p><p>
|
||||
You can change this behaviour using options like the following:
|
||||
</p><pre class="programlisting">
|
||||
interfaces = eth* lo
|
||||
bind interfaces only = yes
|
||||
</pre><p>
|
||||
This tells Samba to only listen for connections on interfaces with a
|
||||
name starting with 'eth' such as eth0, eth1, plus on the loopback
|
||||
interface called 'lo'. The name you will need to use depends on what
|
||||
OS you are using, in the above I used the common name for Ethernet
|
||||
adapters on Linux.</P
|
||||
><P
|
||||
>If you use the above and someone tries to make a SMB connection to
|
||||
adapters on Linux.
|
||||
</p><p>
|
||||
If you use the above and someone tries to make a SMB connection to
|
||||
your host over a PPP interface called 'ppp0' then they will get a TCP
|
||||
connection refused reply. In that case no Samba code is run at all as
|
||||
the operating system has been told not to pass connections from that
|
||||
interface to any process.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN4094"
|
||||
>25.4. Using a firewall</A
|
||||
></H1
|
||||
><P
|
||||
>Many people use a firewall to deny access to services that they don't
|
||||
interface to any samba process.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2901018"></a>Using a firewall</h2></div></div><p>
|
||||
Many people use a firewall to deny access to services that they don't
|
||||
want exposed outside their network. This can be a very good idea,
|
||||
although I would recommend using it in conjunction with the above
|
||||
methods so that you are protected even if your firewall is not active
|
||||
for some reason.</P
|
||||
><P
|
||||
>If you are setting up a firewall then you need to know what TCP and
|
||||
UDP ports to allow and block. Samba uses the following:</P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
>UDP/137 - used by nmbd
|
||||
UDP/138 - used by nmbd
|
||||
TCP/139 - used by smbd
|
||||
TCP/445 - used by smbd</PRE
|
||||
></P
|
||||
><P
|
||||
>The last one is important as many older firewall setups may not be
|
||||
for some reason.
|
||||
</p><p>
|
||||
If you are setting up a firewall then you need to know what TCP and
|
||||
UDP ports to allow and block. Samba uses the following:
|
||||
</p><pre class="programlisting">
|
||||
UDP/137 - used by nmbd
|
||||
UDP/138 - used by nmbd
|
||||
TCP/139 - used by smbd
|
||||
TCP/445 - used by smbd
|
||||
</pre><p>
|
||||
The last one is important as many older firewall setups may not be
|
||||
aware of it, given that this port was only added to the protocol in
|
||||
recent years. </P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN4101"
|
||||
>25.5. Using a IPC$ share deny</A
|
||||
></H1
|
||||
><P
|
||||
>If the above methods are not suitable, then you could also place a
|
||||
recent years.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2901061"></a>Using a IPC$ share deny</h2></div></div><p>
|
||||
If the above methods are not suitable, then you could also place a
|
||||
more specific deny on the IPC$ share that is used in the recently
|
||||
discovered security hole. This allows you to offer access to other
|
||||
shares while denying access to IPC$ from potentially untrustworthy
|
||||
hosts.</P
|
||||
><P
|
||||
>To do that you could use:</P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
> [ipc$]
|
||||
hosts allow = 192.168.115.0/24 127.0.0.1
|
||||
hosts deny = 0.0.0.0/0</PRE
|
||||
></P
|
||||
><P
|
||||
>this would tell Samba that IPC$ connections are not allowed from
|
||||
hosts.
|
||||
</p><p>
|
||||
To do that you could use:
|
||||
</p><pre class="programlisting">
|
||||
[ipc$]
|
||||
hosts allow = 192.168.115.0/24 127.0.0.1
|
||||
hosts deny = 0.0.0.0/0
|
||||
</pre><p>
|
||||
this would tell Samba that IPC$ connections are not allowed from
|
||||
anywhere but the two listed places (localhost and a local
|
||||
subnet). Connections to other shares would still be allowed. As the
|
||||
IPC$ share is the only share that is always accessible anonymously
|
||||
this provides some level of protection against attackers that do not
|
||||
know a username/password for your host.</P
|
||||
><P
|
||||
>If you use this method then clients will be given a 'access denied'
|
||||
know a username/password for your host.
|
||||
</p><p>
|
||||
If you use this method then clients will be given a 'access denied'
|
||||
reply when they try to access the IPC$ share. That means that those
|
||||
clients will not be able to browse shares, and may also be unable to
|
||||
access some other resources. </P
|
||||
><P
|
||||
>This is not recommended unless you cannot use one of the other
|
||||
methods listed above for some reason.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN4110"
|
||||
>25.6. Upgrading Samba</A
|
||||
></H1
|
||||
><P
|
||||
>Please check regularly on <A
|
||||
HREF="http://www.samba.org/"
|
||||
TARGET="_top"
|
||||
>http://www.samba.org/</A
|
||||
> for updates and
|
||||
access some other resources.
|
||||
</p><p>
|
||||
This is not recommended unless you cannot use one of the other
|
||||
methods listed above for some reason.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2900617"></a>NTLMv2 Security</h2></div></div><p>
|
||||
To configure NTLMv2 authentication the following registry keys are worth knowing about:
|
||||
</p><p>
|
||||
</p><pre class="programlisting">
|
||||
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
|
||||
"lmcompatibilitylevel"=dword:00000003
|
||||
|
||||
0x3 - Send NTLMv2 response only. Clients will use NTLMv2 authentication,
|
||||
use NTLMv2 session security if the server supports it. Domain
|
||||
controllers accept LM, NTLM and NTLMv2 authentication.
|
||||
|
||||
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0]
|
||||
"NtlmMinClientSec"=dword:00080000
|
||||
|
||||
0x80000 - NTLMv2 session security. If either NtlmMinClientSec or
|
||||
NtlmMinServerSec is set to 0x80000, the connection will fail if NTLMv2
|
||||
session security is not negotiated.
|
||||
</pre><p>
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2900653"></a>Upgrading Samba</h2></div></div><p>
|
||||
Please check regularly on <a href="http://www.samba.org/" target="_top">http://www.samba.org/</a> for updates and
|
||||
important announcements. Occasionally security releases are made and
|
||||
it is highly recommended to upgrade Samba when a security vulnerability
|
||||
is discovered.</P
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="NAVFOOTER"
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"><TABLE
|
||||
SUMMARY="Footer navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="improved-browsing.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="samba-howto-collection.html"
|
||||
ACCESSKEY="H"
|
||||
>Home</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="unicode.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
>Improved browsing in samba</TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="optional.html"
|
||||
ACCESSKEY="U"
|
||||
>Up</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
>Unicode/Charsets</TD
|
||||
></TR
|
||||
></TABLE
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
is discovered.
|
||||
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="integrate-ms-networks.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="unicode.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 23. Integrating MS Windows networks with Samba </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 25. Unicode/Charsets</td></tr></table></div></body></html>
|
||||
|
||||
@ -1,160 +1,42 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>Samba as Stand-Alone Server</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
||||
REL="HOME"
|
||||
TITLE="SAMBA Project Documentation"
|
||||
HREF="samba-howto-collection.html"><LINK
|
||||
REL="UP"
|
||||
TITLE="Type of installation"
|
||||
HREF="type.html"><LINK
|
||||
REL="PREVIOUS"
|
||||
TITLE="Nomenclature of Server Types"
|
||||
HREF="servertype.html"><LINK
|
||||
REL="NEXT"
|
||||
TITLE="Samba as an NT4 or Win2k Primary Domain Controller"
|
||||
HREF="samba-pdc.html"></HEAD
|
||||
><BODY
|
||||
CLASS="CHAPTER"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><DIV
|
||||
CLASS="NAVHEADER"
|
||||
><TABLE
|
||||
SUMMARY="Header navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TH
|
||||
COLSPAN="3"
|
||||
ALIGN="center"
|
||||
>SAMBA Project Documentation</TH
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="left"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="servertype.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="80%"
|
||||
ALIGN="center"
|
||||
VALIGN="bottom"
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="right"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="samba-pdc.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
></TABLE
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"></DIV
|
||||
><DIV
|
||||
CLASS="CHAPTER"
|
||||
><H1
|
||||
><A
|
||||
NAME="SECURITYLEVELS"
|
||||
></A
|
||||
>Chapter 6. Samba as Stand-Alone Server</H1
|
||||
><P
|
||||
>In this section the function and purpose of Samba's <SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>security</I
|
||||
></SPAN
|
||||
>
|
||||
modes are described.</P
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN896"
|
||||
>6.1. User and Share security level</A
|
||||
></H1
|
||||
><P
|
||||
>A SMB server tells the client at startup what "security level" it is
|
||||
running. There are two options "share level" and "user level". Which
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 4. Samba as Stand-Alone Server</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="type.html" title="Part II. Server Configuration Basics"><link rel="previous" href="ServerType.html" title="Chapter 3. Nomenclature of Server Types"><link rel="next" href="samba-pdc.html" title="Chapter 5.
|
||||
Samba as an NT4 or Win2k Primary Domain Controller
|
||||
"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 4. Samba as Stand-Alone Server</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="ServerType.html">Prev</a> </td><th width="60%" align="center">Part II. Server Configuration Basics</th><td width="20%" align="right"> <a accesskey="n" href="samba-pdc.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="securitylevels"></a>Chapter 4. Samba as Stand-Alone Server</h2></div><div><div class="author"><h3 class="author">Andrew Tridgell</h3><div class="affiliation"><span class="orgname">Samba Team<br></span><div class="address"><p><tt><<a href="mailto:tridge@samba.org">tridge@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="securitylevels.html#id2807692">User and Share security level</a></dt><dd><dl><dt><a href="securitylevels.html#id2807727">User Level Security</a></dt><dt><a href="securitylevels.html#id2810322">Share Level Security</a></dt><dt><a href="securitylevels.html#id2812328">Server Level Security</a></dt><dt><a href="securitylevels.html#id2876991">Domain Level Security</a></dt><dt><a href="securitylevels.html#id2877129">ADS Level Security</a></dt></dl></dd></dl></div><p>
|
||||
In this section the function and purpose of Samba's <span class="emphasis"><em>security</em></span>
|
||||
modes are described.
|
||||
</p><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2807692"></a>User and Share security level</h2></div></div><p>
|
||||
A SMB server tells the client at startup what "security level" it is
|
||||
running. There are two options "share level" and "user level". Which
|
||||
of these two the client receives affects the way the client then tries
|
||||
to authenticate itself. It does not directly affect (to any great
|
||||
extent) the way the Samba server does security. I know this is
|
||||
strange, but it fits in with the client/server approach of SMB. In SMB
|
||||
everything is initiated and controlled by the client, and the server
|
||||
can only tell the client what is available and whether an action is
|
||||
allowed. </P
|
||||
><DIV
|
||||
CLASS="SECT2"
|
||||
><H2
|
||||
CLASS="SECT2"
|
||||
><A
|
||||
NAME="AEN899"
|
||||
>6.1.1. User Level Security</A
|
||||
></H2
|
||||
><P
|
||||
>I'll describe user level security first, as its simpler. In user level
|
||||
security the client will send a "session setup" command directly after
|
||||
allowed.
|
||||
</p><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2807727"></a>User Level Security</h3></div></div><p>
|
||||
I'll describe user level security first, as its simpler. In user level
|
||||
security the client will send a "session setup" command directly after
|
||||
the protocol negotiation. This contains a username and password. The
|
||||
server can either accept or reject that username/password
|
||||
combination. Note that at this stage the server has no idea what
|
||||
share the client will eventually try to connect to, so it can't base
|
||||
the "accept/reject" on anything other than:</P
|
||||
><P
|
||||
></P
|
||||
><OL
|
||||
TYPE="1"
|
||||
><LI
|
||||
><P
|
||||
>the username/password</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>the machine that the client is coming from</P
|
||||
></LI
|
||||
></OL
|
||||
><P
|
||||
>If the server accepts the username/password then the client expects to
|
||||
be able to mount any share (using a "tree connection") without
|
||||
the "accept/reject" on anything other than:
|
||||
</p><div class="orderedlist"><ol type="1"><li><p>the username/password</p></li><li><p>the machine that the client is coming from</p></li></ol></div><p>
|
||||
If the server accepts the username/password then the client expects to
|
||||
be able to mount any share (using a "tree connection") without
|
||||
specifying a password. It expects that all access rights will be as
|
||||
the username/password specified in the "session setup". </P
|
||||
><P
|
||||
>It is also possible for a client to send multiple "session setup"
|
||||
requests. When the server responds it gives the client a "uid" to use
|
||||
the username/password specified in the "session setup".
|
||||
</p><p>
|
||||
It is also possible for a client to send multiple "session setup"
|
||||
requests. When the server responds it gives the client a "uid" to use
|
||||
as an authentication tag for that username/password. The client can
|
||||
maintain multiple authentication contexts in this way (WinDD is an
|
||||
example of an application that does this)</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT2"
|
||||
><H2
|
||||
CLASS="SECT2"
|
||||
><A
|
||||
NAME="AEN909"
|
||||
>6.1.2. Share Level Security</A
|
||||
></H2
|
||||
><P
|
||||
>Ok, now for share level security. In share level security the client
|
||||
example of an application that does this)
|
||||
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2810322"></a>Share Level Security</h3></div></div><p>
|
||||
Ok, now for share level security. In share level security the client
|
||||
authenticates itself separately for each share. It will send a
|
||||
password along with each "tree connection" (share mount). It does not
|
||||
password along with each "tree connection" (share mount). It does not
|
||||
explicitly send a username with this operation. The client is
|
||||
expecting a password to be associated with each share, independent of
|
||||
the user. This means that samba has to work out what username the
|
||||
@ -162,380 +44,169 @@ client probably wants to use. It is never explicitly sent the
|
||||
username. Some commercial SMB servers such as NT actually associate
|
||||
passwords directly with shares in share level security, but samba
|
||||
always uses the unix authentication scheme where it is a
|
||||
username/password that is authenticated, not a "share/password".</P
|
||||
><P
|
||||
>Many clients send a "session setup" even if the server is in share
|
||||
username/password that is authenticated, not a "share/password".
|
||||
</p><p>
|
||||
Many clients send a "session setup" even if the server is in share
|
||||
level security. They normally send a valid username but no
|
||||
password. Samba records this username in a list of "possible
|
||||
usernames". When the client then does a "tree connection" it also adds
|
||||
password. Samba records this username in a list of "possible
|
||||
usernames". When the client then does a "tree connection" it also adds
|
||||
to this list the name of the share they try to connect to (useful for
|
||||
home directories) and any users listed in the <B
|
||||
CLASS="COMMAND"
|
||||
>user =</B
|
||||
> <TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf</TT
|
||||
>
|
||||
line. The password is then checked in turn against these "possible
|
||||
usernames". If a match is found then the client is authenticated as
|
||||
that user.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT2"
|
||||
><H2
|
||||
CLASS="SECT2"
|
||||
><A
|
||||
NAME="AEN915"
|
||||
>6.1.3. Server Level Security</A
|
||||
></H2
|
||||
><P
|
||||
>Finally "server level" security. In server level security the samba
|
||||
home directories) and any users listed in the <b>user =</b> <tt>smb.conf</tt>
|
||||
line. The password is then checked in turn against these "possible
|
||||
usernames". If a match is found then the client is authenticated as
|
||||
that user.
|
||||
</p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2812328"></a>Server Level Security</h3></div></div><p>
|
||||
Finally "server level" security. In server level security the samba
|
||||
server reports to the client that it is in user level security. The
|
||||
client then does a "session setup" as described earlier. The samba
|
||||
client then does a "session setup" as described earlier. The samba
|
||||
server takes the username/password that the client sends and attempts
|
||||
to login to the "password server" by sending exactly the same
|
||||
to login to the "password server" by sending exactly the same
|
||||
username/password that it got from the client. If that server is in
|
||||
user level security and accepts the password then samba accepts the
|
||||
clients connection. This allows the samba server to use another SMB
|
||||
server as the "password server". </P
|
||||
><P
|
||||
>You should also note that at the very start of all this, where the
|
||||
server as the "password server".
|
||||
</p><p>
|
||||
You should also note that at the very start of all this, where the
|
||||
server tells the client what security level it is in, it also tells
|
||||
the client if it supports encryption. If it does then it supplies the
|
||||
client with a random "cryptkey". The client will then send all
|
||||
client with a random "cryptkey". The client will then send all
|
||||
passwords in encrypted form. You have to compile samba with encryption
|
||||
enabled to support this feature, and you have to maintain a separate
|
||||
smbpasswd file with SMB style encrypted passwords. It is
|
||||
cryptographically impossible to translate from unix style encryption
|
||||
to SMB style encryption, although there are some fairly simple management
|
||||
schemes by which the two could be kept in sync.</P
|
||||
><P
|
||||
>"security = server" means that Samba reports to clients that
|
||||
it is running in "user mode" but actually passes off all authentication
|
||||
requests to another "user mode" server. This requires an additional
|
||||
parameter "password server =" that points to the real authentication server.
|
||||
schemes by which the two could be kept in sync.
|
||||
</p><p>
|
||||
"security = server" means that Samba reports to clients that
|
||||
it is running in "user mode" but actually passes off all authentication
|
||||
requests to another "user mode" server. This requires an additional
|
||||
parameter "password server =" that points to the real authentication server.
|
||||
That real authentication server can be another Samba server or can be a
|
||||
Windows NT server, the later natively capable of encrypted password support.</P
|
||||
><DIV
|
||||
CLASS="SECT3"
|
||||
><H3
|
||||
CLASS="SECT3"
|
||||
><A
|
||||
NAME="AEN920"
|
||||
>6.1.3.1. Configuring Samba for Seemless Windows Network Integration</A
|
||||
></H3
|
||||
><P
|
||||
>MS Windows clients may use encrypted passwords as part of a challenege/response
|
||||
Windows NT server, the later natively capable of encrypted password support.
|
||||
</p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>
|
||||
<span class="emphasis"><em>Server</em></span> level security is incompatible with what is known
|
||||
as <span class="emphasis"><em>schannel</em></span> or "sign and seal" protocols. This means that
|
||||
if you want to use <span class="emphasis"><em>server</em></span> level security you must disable
|
||||
the use of "sign and seal" on all machines on your network.
|
||||
</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2876754"></a>Configuring Samba for Seemless Windows Network Integration</h4></div></div><p>
|
||||
MS Windows clients may use encrypted passwords as part of a challenege/response
|
||||
authentication model (a.k.a. NTLMv1) or alone, or clear text strings for simple
|
||||
password based authentication. It should be realized that with the SMB protocol
|
||||
the password is passed over the network either in plain text or encrypted, but
|
||||
not both in the same authentication requests.</P
|
||||
><P
|
||||
>When encrypted passwords are used a password that has been entered by the user
|
||||
is encrypted in two ways:</P
|
||||
><P
|
||||
></P
|
||||
><UL
|
||||
><LI
|
||||
><P
|
||||
>An MD4 hash of the UNICODE of the password
|
||||
not both in the same authentication request.
|
||||
</p><p>
|
||||
When encrypted passwords are used a password that has been entered by the user
|
||||
is encrypted in two ways:
|
||||
</p><div class="itemizedlist"><ul type="disc"><li><p>An MD4 hash of the UNICODE of the password
|
||||
string. This is known as the NT hash.
|
||||
</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>The password is converted to upper case,
|
||||
</p></li><li><p>The password is converted to upper case,
|
||||
and then padded or trucated to 14 bytes. This string is
|
||||
then appended with 5 bytes of NULL characters and split to
|
||||
form two 56 bit DES keys to encrypt a "magic" 8 byte value.
|
||||
form two 56 bit DES keys to encrypt a "magic" 8 byte value.
|
||||
The resulting 16 bytes for the LanMan hash.
|
||||
</P
|
||||
></LI
|
||||
></UL
|
||||
><P
|
||||
>MS Windows 95 pre-service pack 1, MS Windows NT versions 3.x and version 4.0
|
||||
</p></li></ul></div><p>
|
||||
MS Windows 95 pre-service pack 1, MS Windows NT versions 3.x and version 4.0
|
||||
pre-service pack 3 will use either mode of password authentication. All
|
||||
versions of MS Windows that follow these versions no longer support plain
|
||||
text passwords by default.</P
|
||||
><P
|
||||
>MS Windows clients have a habit of dropping network mappings that have been idle
|
||||
text passwords by default.
|
||||
</p><p>
|
||||
MS Windows clients have a habit of dropping network mappings that have been idle
|
||||
for 10 minutes or longer. When the user attempts to use the mapped drive
|
||||
connection that has been dropped, the client re-establishes the connection using
|
||||
a cached copy of the password.</P
|
||||
><P
|
||||
>When Microsoft changed the default password mode, support was dropped for caching
|
||||
a cached copy of the password.
|
||||
</p><p>
|
||||
When Microsoft changed the default password mode, support was dropped for caching
|
||||
of the plain text password. This means that when the registry parameter is changed
|
||||
to re-enable use of plain text passwords it appears to work, but when a dropped
|
||||
service connection mapping attempts to revalidate it will fail if the remote
|
||||
authentication server does not support encrypted passwords. This means that it
|
||||
is definitely not a good idea to re-enable plain text password support in such clients.</P
|
||||
><P
|
||||
>The following parameters can be used to work around the issue of Windows 9x client
|
||||
is definitely not a good idea to re-enable plain text password support in such clients.
|
||||
</p><p>
|
||||
The following parameters can be used to work around the issue of Windows 9x client
|
||||
upper casing usernames and password before transmitting them to the SMB server
|
||||
when using clear text authentication.</P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
> <A
|
||||
HREF="smb.conf.5.html#PASSWORDLEVEL"
|
||||
TARGET="_top"
|
||||
>passsword level</A
|
||||
> = <VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>integer</VAR
|
||||
>
|
||||
<A
|
||||
HREF="smb.conf.5.html#USERNAMELEVEL"
|
||||
TARGET="_top"
|
||||
>username level</A
|
||||
> = <VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>integer</VAR
|
||||
></PRE
|
||||
></P
|
||||
><P
|
||||
>By default Samba will lower case the username before attempting to lookup the user
|
||||
when using clear text authentication.
|
||||
</p><pre class="programlisting">
|
||||
<a href="smb.conf.5.html#PASSWORDLEVEL" target="_top">passsword level</a> = <i><tt>integer</tt></i>
|
||||
<a href="smb.conf.5.html#USERNAMELEVEL" target="_top">username level</a> = <i><tt>integer</tt></i>
|
||||
</pre><p>
|
||||
By default Samba will lower case the username before attempting to lookup the user
|
||||
in the database of local system accounts. Because UNIX usernames conventionally
|
||||
only contain lower case character, the <VAR
|
||||
CLASS="PARAMETER"
|
||||
>username level</VAR
|
||||
> parameter
|
||||
is rarely needed.</P
|
||||
><P
|
||||
>However, passwords on UNIX systems often make use of mixed case characters.
|
||||
only contain lower case character, the <i><tt>username level</tt></i> parameter
|
||||
is rarely needed.
|
||||
</p><p>
|
||||
However, passwords on UNIX systems often make use of mixed case characters.
|
||||
This means that in order for a user on a Windows 9x client to connect to a Samba
|
||||
server using clear text authentication, the <VAR
|
||||
CLASS="PARAMETER"
|
||||
>password level</VAR
|
||||
>
|
||||
must be set to the maximum number of upper case letter which <SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>could</I
|
||||
></SPAN
|
||||
>
|
||||
appear is a password. Note that is the server OS uses the traditional DES version
|
||||
of crypt(), then a <VAR
|
||||
CLASS="PARAMETER"
|
||||
>password level</VAR
|
||||
> of 8 will result in case
|
||||
server using clear text authentication, the <i><tt>password level</tt></i>
|
||||
must be set to the maximum number of upper case letter which <span class="emphasis"><em>could</em></span>
|
||||
appear is a password. Note that the server OS uses the traditional DES version
|
||||
of crypt(), a <i><tt>password level</tt></i> of 8 will result in case
|
||||
insensitive passwords as seen from Windows users. This will also result in longer
|
||||
login times as Samba hash to compute the permutations of the password string and
|
||||
try them one by one until a match is located (or all combinations fail).</P
|
||||
><P
|
||||
>The best option to adopt is to enable support for encrypted passwords
|
||||
login times as Samba has to compute the permutations of the password string and
|
||||
try them one by one until a match is located (or all combinations fail).
|
||||
</p><p>
|
||||
The best option to adopt is to enable support for encrypted passwords
|
||||
where ever Samba is used. There are three configuration possibilities
|
||||
for support of encrypted passwords:</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT3"
|
||||
><H3
|
||||
CLASS="SECT3"
|
||||
><A
|
||||
NAME="AEN946"
|
||||
>6.1.3.2. Use MS Windows NT as an authentication server</A
|
||||
></H3
|
||||
><P
|
||||
>This method involves the additions of the following parameters in the <TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf</TT
|
||||
> file:</P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
> encrypt passwords = Yes
|
||||
for support of encrypted passwords:
|
||||
</p></div><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2876930"></a>Use MS Windows NT as an authentication server</h4></div></div><p>
|
||||
This method involves the additions of the following parameters in the <tt>smb.conf</tt> file:
|
||||
</p><pre class="programlisting">
|
||||
encrypt passwords = Yes
|
||||
security = server
|
||||
password server = "NetBIOS_name_of_PDC"</PRE
|
||||
></P
|
||||
><P
|
||||
>There are two ways of identifying whether or not a username and
|
||||
password server = "NetBIOS_name_of_PDC"
|
||||
</pre><p>
|
||||
There are two ways of identifying whether or not a username and
|
||||
password pair was valid or not. One uses the reply information provided
|
||||
as part of the authentication messaging process, the other uses
|
||||
just and error code.</P
|
||||
><P
|
||||
>The down-side of this mode of configuration is the fact that
|
||||
just an error code.
|
||||
</p><p>
|
||||
The down-side of this mode of configuration is the fact that
|
||||
for security reasons Samba will send the password server a bogus
|
||||
username and a bogus password and if the remote server fails to
|
||||
reject the username and password pair then an alternative mode
|
||||
of identification of validation is used. Where a site uses password
|
||||
lock out after a certain number of failed authentication attempts
|
||||
this will result in user lockouts.</P
|
||||
><P
|
||||
>Use of this mode of authentication does require there to be
|
||||
this will result in user lockouts.
|
||||
</p><p>
|
||||
Use of this mode of authentication does require there to be
|
||||
a standard Unix account for the user, this account can be blocked
|
||||
to prevent logons by other than MS Windows clients.</P
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT2"
|
||||
><H2
|
||||
CLASS="SECT2"
|
||||
><A
|
||||
NAME="AEN955"
|
||||
>6.1.4. Domain Level Security</A
|
||||
></H2
|
||||
><P
|
||||
>When samba is operating in <SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>security = domain</I
|
||||
></SPAN
|
||||
> mode this means that
|
||||
to prevent logons by other than MS Windows clients.
|
||||
</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2876991"></a>Domain Level Security</h3></div></div><p>
|
||||
When samba is operating in <span class="emphasis"><em>security = domain</em></span> mode this means that
|
||||
the Samba server has a domain security trust account (a machine account) and will cause
|
||||
all authentication requests to be passed through to the domain controllers.</P
|
||||
><DIV
|
||||
CLASS="SECT3"
|
||||
><H3
|
||||
CLASS="SECT3"
|
||||
><A
|
||||
NAME="AEN959"
|
||||
>6.1.4.1. Samba as a member of an MS Windows NT security domain</A
|
||||
></H3
|
||||
><P
|
||||
>This method involves additon of the following paramters in the <TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf</TT
|
||||
> file:</P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
> encrypt passwords = Yes
|
||||
all authentication requests to be passed through to the domain controllers.
|
||||
</p><div class="sect3" lang="en"><div class="titlepage"><div><h4 class="title"><a name="id2877011"></a>Samba as a member of an MS Windows NT security domain</h4></div></div><p>
|
||||
This method involves addition of the following parameters in the <tt>smb.conf</tt> file:
|
||||
</p><pre class="programlisting">
|
||||
encrypt passwords = Yes
|
||||
security = domain
|
||||
workgroup = "name of NT domain"
|
||||
password server = *</PRE
|
||||
></P
|
||||
><P
|
||||
>The use of the "*" argument to <B
|
||||
CLASS="COMMAND"
|
||||
>password server</B
|
||||
> will cause samba to locate the
|
||||
workgroup = "name of NT domain"
|
||||
password server = *
|
||||
</pre><p>
|
||||
The use of the "*" argument to <b>password server</b> will cause samba to locate the
|
||||
domain controller in a way analogous to the way this is done within MS Windows NT.
|
||||
This is the default behaviour.</P
|
||||
><P
|
||||
>In order for this method to work the Samba server needs to join the
|
||||
MS Windows NT security domain. This is done as follows:</P
|
||||
><P
|
||||
></P
|
||||
><UL
|
||||
><LI
|
||||
><P
|
||||
>On the MS Windows NT domain controller using
|
||||
This is the default behaviour.
|
||||
</p><p>
|
||||
In order for this method to work the Samba server needs to join the
|
||||
MS Windows NT security domain. This is done as follows:
|
||||
</p><div class="itemizedlist"><ul type="disc"><li><p>On the MS Windows NT domain controller using
|
||||
the Server Manager add a machine account for the Samba server.
|
||||
</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>Next, on the Linux system execute:
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>smbpasswd -r PDC_NAME -j DOMAIN_NAME</B
|
||||
>
|
||||
</P
|
||||
></LI
|
||||
></UL
|
||||
><P
|
||||
>Use of this mode of authentication does require there to be a standard Unix account
|
||||
</p></li><li><p>Next, on the Linux system execute:
|
||||
<b>smbpasswd -r PDC_NAME -j DOMAIN_NAME</b> (samba 2.x)
|
||||
|
||||
<b>net join -U administrator%password</b> (samba-3)
|
||||
</p></li></ul></div><p>
|
||||
Use of this mode of authentication does require there to be a standard Unix account
|
||||
for the user in order to assign a uid once the account has been authenticated by
|
||||
the remote Windows DC. This account can be blocked to prevent logons by other than
|
||||
MS Windows clients by things such as setting an invalid shell in the
|
||||
<TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/passwd</TT
|
||||
> entry. </P
|
||||
><P
|
||||
>An alternative to assigning UIDs to Windows users on a Samba member server is
|
||||
presented in the <A
|
||||
HREF="winbind.html"
|
||||
TARGET="_top"
|
||||
>Winbind Overview</A
|
||||
> chapter
|
||||
in this HOWTO collection.</P
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT2"
|
||||
><H2
|
||||
CLASS="SECT2"
|
||||
><A
|
||||
NAME="AEN978"
|
||||
>6.1.5. ADS Level Security</A
|
||||
></H2
|
||||
><P
|
||||
>For information about the configuration option please refer to the entire section entitled
|
||||
<SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>Samba as an ADS Domain Member.</I
|
||||
></SPAN
|
||||
></P
|
||||
></DIV
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="NAVFOOTER"
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"><TABLE
|
||||
SUMMARY="Footer navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="servertype.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="samba-howto-collection.html"
|
||||
ACCESSKEY="H"
|
||||
>Home</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="samba-pdc.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
>Nomenclature of Server Types</TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="type.html"
|
||||
ACCESSKEY="U"
|
||||
>Up</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
>Samba as an NT4 or Win2k Primary Domain Controller</TD
|
||||
></TR
|
||||
></TABLE
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
the remote Windows DC. This account can be blocked to prevent logons by clients other than
|
||||
MS Windows through things such as setting an invalid shell in the
|
||||
<tt>/etc/passwd</tt> entry.
|
||||
</p><p>
|
||||
An alternative to assigning UIDs to Windows users on a Samba member server is
|
||||
presented in the <a href="winbind.html" title="Chapter 15. Unified Logons between Windows NT and UNIX using Winbind">Winbind Overview</a> chapter
|
||||
in this HOWTO collection.
|
||||
</p></div></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="id2877129"></a>ADS Level Security</h3></div></div><p>
|
||||
For information about the configuration option please refer to the entire section entitled
|
||||
<span class="emphasis"><em>Samba as an ADS Domain Member.</em></span>
|
||||
</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="ServerType.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="type.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="samba-pdc.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 3. Nomenclature of Server Types </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 5.
|
||||
Samba as an NT4 or Win2k Primary Domain Controller
|
||||
</td></tr></table></div></body></html>
|
||||
|
||||
File diff suppressed because one or more lines are too long
@ -1,510 +1,95 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>smbcacls</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="SMBCACLS.1"
|
||||
></A
|
||||
>smbcacls</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>smbcacls -- Set or get ACLs on an NT file or directory names</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbcacls</B
|
||||
> {//server/share} {filename} [-D acls] [-M acls] [-A acls] [-S acls] [-C name] [-G name] [-n] [-t] [-U username] [-h] [-d]</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN24"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
>This tool is part of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
> suite.</P
|
||||
><P
|
||||
>The <B
|
||||
CLASS="COMMAND"
|
||||
>smbcacls</B
|
||||
> program manipulates NT Access Control
|
||||
Lists (ACLs) on SMB file shares. </P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN32"
|
||||
></A
|
||||
><H2
|
||||
>OPTIONS</H2
|
||||
><P
|
||||
>The following options are available to the <B
|
||||
CLASS="COMMAND"
|
||||
>smbcacls</B
|
||||
> program.
|
||||
The format of ACLs is described in the section ACL FORMAT </P
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>-A acls</DT
|
||||
><DD
|
||||
><P
|
||||
>Add the ACLs specified to the ACL list. Existing
|
||||
access control entries are unchanged. </P
|
||||
></DD
|
||||
><DT
|
||||
>-M acls</DT
|
||||
><DD
|
||||
><P
|
||||
>Modify the mask value (permissions) for the ACLs
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbcacls</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbcacls.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbcacls — Set or get ACLs on an NT file or directory names</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>smbcacls</tt> {//server/share} {filename} [-D acls] [-M acls] [-A acls] [-S acls] [-C name] [-G name] [-n] [-t] [-U username] [-h] [-d]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p>The <b>smbcacls</b> program manipulates NT Access Control
|
||||
Lists (ACLs) on SMB file shares. </p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><p>The following options are available to the <b>smbcacls</b> program.
|
||||
The format of ACLs is described in the section ACL FORMAT </p><div class="variablelist"><dl><dt><span class="term">-A acls</span></dt><dd><p>Add the ACLs specified to the ACL list. Existing
|
||||
access control entries are unchanged. </p></dd><dt><span class="term">-M acls</span></dt><dd><p>Modify the mask value (permissions) for the ACLs
|
||||
specified on the command line. An error will be printed for each
|
||||
ACL specified that was not already present in the ACL list
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-D acls</DT
|
||||
><DD
|
||||
><P
|
||||
>Delete any ACLs specified on the command line.
|
||||
</p></dd><dt><span class="term">-D acls</span></dt><dd><p>Delete any ACLs specified on the command line.
|
||||
An error will be printed for each ACL specified that was not
|
||||
already present in the ACL list. </P
|
||||
></DD
|
||||
><DT
|
||||
>-S acls</DT
|
||||
><DD
|
||||
><P
|
||||
>This command sets the ACLs on the file with
|
||||
already present in the ACL list. </p></dd><dt><span class="term">-S acls</span></dt><dd><p>This command sets the ACLs on the file with
|
||||
only the ones specified on the command line. All other ACLs are
|
||||
erased. Note that the ACL specified must contain at least a revision,
|
||||
type, owner and group for the call to succeed. </P
|
||||
></DD
|
||||
><DT
|
||||
>-U username</DT
|
||||
><DD
|
||||
><P
|
||||
>Specifies a username used to connect to the
|
||||
specified service. The username may be of the form "username" in
|
||||
type, owner and group for the call to succeed. </p></dd><dt><span class="term">-U username</span></dt><dd><p>Specifies a username used to connect to the
|
||||
specified service. The username may be of the form "username" in
|
||||
which case the user is prompted to enter in a password and the
|
||||
workgroup specified in the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> file is
|
||||
used, or "username%password" or "DOMAIN\username%password" and the
|
||||
password and workgroup names are used as provided. </P
|
||||
></DD
|
||||
><DT
|
||||
>-C name</DT
|
||||
><DD
|
||||
><P
|
||||
>The owner of a file or directory can be changed
|
||||
to the name given using the <VAR
|
||||
CLASS="PARAMETER"
|
||||
>-C</VAR
|
||||
> option.
|
||||
workgroup specified in the <a href="smb.conf.5.html">smb.conf(5)</a> file is
|
||||
used, or "username%password" or "DOMAIN\username%password" and the
|
||||
password and workgroup names are used as provided. </p></dd><dt><span class="term">-C name</span></dt><dd><p>The owner of a file or directory can be changed
|
||||
to the name given using the <i><tt>-C</tt></i> option.
|
||||
The name can be a sid in the form S-1-x-y-z or a name resolved
|
||||
against the server specified in the first argument. </P
|
||||
><P
|
||||
>This command is a shortcut for -M OWNER:name.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-G name</DT
|
||||
><DD
|
||||
><P
|
||||
>The group owner of a file or directory can
|
||||
be changed to the name given using the <VAR
|
||||
CLASS="PARAMETER"
|
||||
>-G</VAR
|
||||
>
|
||||
against the server specified in the first argument. </p><p>This command is a shortcut for -M OWNER:name.
|
||||
</p></dd><dt><span class="term">-G name</span></dt><dd><p>The group owner of a file or directory can
|
||||
be changed to the name given using the <i><tt>-G</tt></i>
|
||||
option. The name can be a sid in the form S-1-x-y-z or a name
|
||||
resolved against the server specified n the first argument.
|
||||
</P
|
||||
><P
|
||||
>This command is a shortcut for -M GROUP:name.</P
|
||||
></DD
|
||||
><DT
|
||||
>-n</DT
|
||||
><DD
|
||||
><P
|
||||
>This option displays all ACL information in numeric
|
||||
</p><p>This command is a shortcut for -M GROUP:name.</p></dd><dt><span class="term">-n</span></dt><dd><p>This option displays all ACL information in numeric
|
||||
format. The default is to convert SIDs to names and ACE types
|
||||
and masks to a readable string format. </P
|
||||
></DD
|
||||
><DT
|
||||
>-t</DT
|
||||
><DD
|
||||
><P
|
||||
> Don't actually do anything, only validate the correctness of
|
||||
and masks to a readable string format. </p></dd><dt><span class="term">-t</span></dt><dd><p>
|
||||
Don't actually do anything, only validate the correctness of
|
||||
the arguments.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-h|--help</DT
|
||||
><DD
|
||||
><P
|
||||
>Print a summary of command line options.</P
|
||||
></DD
|
||||
><DT
|
||||
>-V</DT
|
||||
><DD
|
||||
><P
|
||||
>Prints the version number for
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
>.</P
|
||||
></DD
|
||||
><DT
|
||||
>-s <configuration file></DT
|
||||
><DD
|
||||
><P
|
||||
>The file specified contains the
|
||||
</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
|
||||
</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for
|
||||
<b>smbd</b>.</p></dd><dt><span class="term">-s <configuration file></span></dt><dd><p>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 <A
|
||||
HREF="smb.conf.5.html"
|
||||
TARGET="_top"
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf(5)</TT
|
||||
></A
|
||||
> for more information.
|
||||
to provide. See <a href="smb.conf.5.html" target="_top"><tt>
|
||||
smb.conf(5)</tt></a> for more information.
|
||||
The default configuration file name is determined at
|
||||
compile time.</P
|
||||
></DD
|
||||
><DT
|
||||
>-d|--debug=debuglevel</DT
|
||||
><DD
|
||||
><P
|
||||
><VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>debuglevel</VAR
|
||||
> is an integer
|
||||
compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
|
||||
from 0 to 10. The default value if this parameter is
|
||||
not specified is zero.</P
|
||||
><P
|
||||
>The higher this value, the more detail will be
|
||||
not specified is zero.</p><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
|
||||
><P
|
||||
>Levels above 1 will generate considerable
|
||||
information about operations carried out.</p><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
|
||||
><P
|
||||
>Note that specifying this parameter here will
|
||||
override the <A
|
||||
HREF="smb.conf.5.html#loglevel"
|
||||
TARGET="_top"
|
||||
>log
|
||||
level</A
|
||||
> parameter in the <A
|
||||
HREF="smb.conf.5.html"
|
||||
TARGET="_top"
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf(5)</TT
|
||||
></A
|
||||
> file.</P
|
||||
></DD
|
||||
><DT
|
||||
>-l|--logfile=logbasename</DT
|
||||
><DD
|
||||
><P
|
||||
>File name for log/debug files. The extension
|
||||
<CODE
|
||||
CLASS="CONSTANT"
|
||||
>".client"</CODE
|
||||
> will be appended. The log file is
|
||||
never removed by the client.</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN111"
|
||||
></A
|
||||
><H2
|
||||
>ACL FORMAT</H2
|
||||
><P
|
||||
>The format of an ACL is one or more ACL entries separated by
|
||||
either commas or newlines. An ACL entry is one of the following: </P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
>
|
||||
REVISION:<revision number>
|
||||
OWNER:<sid or name>
|
||||
GROUP:<sid or name>
|
||||
ACL:<sid or name>:<type>/<flags>/<mask></PRE
|
||||
></P
|
||||
><P
|
||||
>The revision of the ACL specifies the internal Windows
|
||||
data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
|
||||
override the <a href="smb.conf.5.html#loglevel" target="_top">log
|
||||
level</a> parameter in the <a href="smb.conf.5.html" target="_top">
|
||||
<tt>smb.conf(5)</tt></a> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
|
||||
<tt>".client"</tt> will be appended. The log file is
|
||||
never removed by the client.
|
||||
</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>ACL FORMAT</h2><p>The format of an ACL is one or more ACL entries separated by
|
||||
either commas or newlines. An ACL entry is one of the following: </p><pre class="programlisting">
|
||||
REVISION:<revision number>
|
||||
OWNER:<sid or name>
|
||||
GROUP:<sid or name>
|
||||
ACL:<sid or name>:<type>/<flags>/<mask>
|
||||
</pre><p>The revision of the ACL specifies the internal Windows
|
||||
NT ACL revision for the security descriptor.
|
||||
If not specified it defaults to 1. Using values other than 1 may
|
||||
cause strange behaviour. </P
|
||||
><P
|
||||
>The owner and group specify the owner and group sids for the
|
||||
cause strange behaviour. </p><p>The owner and group specify the owner and group sids for the
|
||||
object. If a SID in the format CWS-1-x-y-z is specified this is used,
|
||||
otherwise the name specified is resolved using the server on which
|
||||
the file or directory resides. </P
|
||||
><P
|
||||
>ACLs specify permissions granted to the SID. This SID again
|
||||
the file or directory resides. </p><p>ACLs specify permissions granted to the SID. This SID again
|
||||
can be specified in CWS-1-x-y-z format or as a name in which case
|
||||
it is resolved against the server on which the file or directory
|
||||
resides. The type, flags and mask values determine the type of
|
||||
access granted to the SID. </P
|
||||
><P
|
||||
>The type can be either 0 or 1 corresponding to ALLOWED or
|
||||
access granted to the SID. </p><p>The type can be either 0 or 1 corresponding to ALLOWED or
|
||||
DENIED access to the SID. The flags values are generally
|
||||
zero for file ACLs and either 9 or 2 for directory ACLs. Some
|
||||
common flags are: </P
|
||||
><P
|
||||
></P
|
||||
><UL
|
||||
><LI
|
||||
><P
|
||||
><CODE
|
||||
CLASS="CONSTANT"
|
||||
>#define SEC_ACE_FLAG_OBJECT_INHERIT 0x1</CODE
|
||||
></P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><CODE
|
||||
CLASS="CONSTANT"
|
||||
>#define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2</CODE
|
||||
></P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><CODE
|
||||
CLASS="CONSTANT"
|
||||
>#define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4</CODE
|
||||
></P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><CODE
|
||||
CLASS="CONSTANT"
|
||||
>#define SEC_ACE_FLAG_INHERIT_ONLY 0x8</CODE
|
||||
></P
|
||||
></LI
|
||||
></UL
|
||||
><P
|
||||
>At present flags can only be specified as decimal or
|
||||
hexadecimal values.</P
|
||||
><P
|
||||
>The mask is a value which expresses the access right
|
||||
common flags are: </p><div class="itemizedlist"><ul type="disc"><li><p><tt>#define SEC_ACE_FLAG_OBJECT_INHERIT 0x1</tt></p></li><li><p><tt>#define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2</tt></p></li><li><p><tt>#define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4</tt></p></li><li><p><tt>#define SEC_ACE_FLAG_INHERIT_ONLY 0x8</tt></p></li></ul></div><p>At present flags can only be specified as decimal or
|
||||
hexadecimal values.</p><p>The mask is a value which expresses the access right
|
||||
granted to the SID. It can be given as a decimal or hexadecimal value,
|
||||
or by using one of the following text strings which map to the NT
|
||||
file permissions of the same name. </P
|
||||
><P
|
||||
></P
|
||||
><UL
|
||||
><LI
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>R</I
|
||||
></SPAN
|
||||
> - Allow read access </P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>W</I
|
||||
></SPAN
|
||||
> - Allow write access</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>X</I
|
||||
></SPAN
|
||||
> - Execute permission on the object</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>D</I
|
||||
></SPAN
|
||||
> - Delete the object</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>P</I
|
||||
></SPAN
|
||||
> - Change permissions</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>O</I
|
||||
></SPAN
|
||||
> - Take ownership</P
|
||||
></LI
|
||||
></UL
|
||||
><P
|
||||
>The following combined permissions can be specified:</P
|
||||
><P
|
||||
></P
|
||||
><UL
|
||||
><LI
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>READ</I
|
||||
></SPAN
|
||||
> - Equivalent to 'RX'
|
||||
permissions</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>CHANGE</I
|
||||
></SPAN
|
||||
> - Equivalent to 'RXWD' permissions
|
||||
</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>FULL</I
|
||||
></SPAN
|
||||
> - Equivalent to 'RWXDPO'
|
||||
permissions</P
|
||||
></LI
|
||||
></UL
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN165"
|
||||
></A
|
||||
><H2
|
||||
>EXIT STATUS</H2
|
||||
><P
|
||||
>The <B
|
||||
CLASS="COMMAND"
|
||||
>smbcacls</B
|
||||
> program sets the exit status
|
||||
file permissions of the same name. </p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>R</em></span> - Allow read access </p></li><li><p><span class="emphasis"><em>W</em></span> - Allow write access</p></li><li><p><span class="emphasis"><em>X</em></span> - Execute permission on the object</p></li><li><p><span class="emphasis"><em>D</em></span> - Delete the object</p></li><li><p><span class="emphasis"><em>P</em></span> - Change permissions</p></li><li><p><span class="emphasis"><em>O</em></span> - Take ownership</p></li></ul></div><p>The following combined permissions can be specified:</p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>READ</em></span> - Equivalent to 'RX'
|
||||
permissions</p></li><li><p><span class="emphasis"><em>CHANGE</em></span> - Equivalent to 'RXWD' permissions
|
||||
</p></li><li><p><span class="emphasis"><em>FULL</em></span> - Equivalent to 'RWXDPO'
|
||||
permissions</p></li></ul></div></div><div class="refsect1" lang="en"><h2>EXIT STATUS</h2><p>The <b>smbcacls</b> program sets the exit status
|
||||
depending on the success or otherwise of the operations performed.
|
||||
The exit status may be one of the following values. </P
|
||||
><P
|
||||
>If the operation succeeded, smbcacls returns and exit
|
||||
status of 0. If <B
|
||||
CLASS="COMMAND"
|
||||
>smbcacls</B
|
||||
> couldn't connect to the specified server,
|
||||
The exit status may be one of the following values. </p><p>If the operation succeeded, smbcacls returns and exit
|
||||
status of 0. If <b>smbcacls</b> couldn't connect to the specified server,
|
||||
or there was an error getting or setting the ACLs, an exit status
|
||||
of 1 is returned. If there was an error parsing any command line
|
||||
arguments, an exit status of 2 is returned. </P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN171"
|
||||
></A
|
||||
><H2
|
||||
>VERSION</H2
|
||||
><P
|
||||
>This man page is correct for version 3.0 of the Samba suite.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN174"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>The original Samba software and related utilities
|
||||
arguments, an exit status of 2 is returned. </p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbcacls</B
|
||||
> was written by Andrew Tridgell
|
||||
and Tim Potter.</P
|
||||
><P
|
||||
>The conversion to DocBook for Samba 2.2 was done
|
||||
to the way the Linux kernel is developed.</p><p><b>smbcacls</b> was written by Andrew Tridgell
|
||||
and Tim Potter.</p><p>The conversion to DocBook for Samba 2.2 was done
|
||||
by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was done
|
||||
by Alexander Bokovoy.</P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
by Alexander Bokovoy.</p></div></div></body></html>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -1,468 +1,71 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>smbcontrol</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="SMBCONTROL.1"
|
||||
></A
|
||||
>smbcontrol</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>smbcontrol -- send messages to smbd, nmbd or winbindd processes</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbcontrol</B
|
||||
> [-i] [-s]</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbcontrol</B
|
||||
> [destination] [message-type] [parameter]</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN18"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
>This tool is part of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
> suite.</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbcontrol</B
|
||||
> is a very small program, which
|
||||
sends messages to a <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbd</SPAN
|
||||
>(8)</SPAN
|
||||
>, a <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>nmbd</SPAN
|
||||
>(8)</SPAN
|
||||
>, or a <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>winbindd</SPAN
|
||||
>(8)</SPAN
|
||||
> daemon running on the system.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN35"
|
||||
></A
|
||||
><H2
|
||||
>OPTIONS</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>-h|--help</DT
|
||||
><DD
|
||||
><P
|
||||
>Print a summary of command line options.</P
|
||||
></DD
|
||||
><DT
|
||||
>-s <configuration file></DT
|
||||
><DD
|
||||
><P
|
||||
>The file specified contains the
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbcontrol</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbcontrol.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbcontrol — send messages to smbd, nmbd or winbindd processes</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>smbcontrol</tt> [-i] [-s]</p></div><div class="cmdsynopsis"><p><tt>smbcontrol</tt> [destination] [message-type] [parameter]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>smbcontrol</b> is a very small program, which
|
||||
sends messages to a <a href="smbd.8.html">smbd(8)</a>, a <a href="nmbd.8.html">nmbd(8)</a>, or a <a href="winbindd.8.html">winbindd(8)</a> daemon running on the system.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
|
||||
</p></dd><dt><span class="term">-s <configuration file></span></dt><dd><p>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 <A
|
||||
HREF="smb.conf.5.html"
|
||||
TARGET="_top"
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf(5)</TT
|
||||
></A
|
||||
> for more information.
|
||||
to provide. See <a href="smb.conf.5.html" target="_top"><tt>
|
||||
smb.conf(5)</tt></a> for more information.
|
||||
The default configuration file name is determined at
|
||||
compile time.</P
|
||||
></DD
|
||||
><DT
|
||||
>-i</DT
|
||||
><DD
|
||||
><P
|
||||
>Run interactively. Individual commands
|
||||
compile time.</p></dd><dt><span class="term">-i</span></dt><dd><p>Run interactively. Individual commands
|
||||
of the form destination message-type parameters can be entered
|
||||
on STDIN. An empty command line or a "q" will quit the
|
||||
program.</P
|
||||
></DD
|
||||
><DT
|
||||
>destination</DT
|
||||
><DD
|
||||
><P
|
||||
>One of <VAR
|
||||
CLASS="PARAMETER"
|
||||
>nmbd</VAR
|
||||
>, <VAR
|
||||
CLASS="PARAMETER"
|
||||
>smbd</VAR
|
||||
> or a process ID.</P
|
||||
><P
|
||||
>The <VAR
|
||||
CLASS="PARAMETER"
|
||||
>smbd</VAR
|
||||
> destination causes the
|
||||
message to "broadcast" to all smbd daemons.</P
|
||||
><P
|
||||
>The <VAR
|
||||
CLASS="PARAMETER"
|
||||
>nmbd</VAR
|
||||
> destination causes the
|
||||
on STDIN. An empty command line or a "q" will quit the
|
||||
program.</p></dd><dt><span class="term">destination</span></dt><dd><p>One of <i><tt>nmbd</tt></i>, <i><tt>smbd</tt></i> or a process ID.</p><p>The <i><tt>smbd</tt></i> destination causes the
|
||||
message to "broadcast" to all smbd daemons.</p><p>The <i><tt>nmbd</tt></i> destination causes the
|
||||
message to be sent to the nmbd daemon specified in the
|
||||
<TT
|
||||
CLASS="FILENAME"
|
||||
>nmbd.pid</TT
|
||||
> file.</P
|
||||
><P
|
||||
>If a single process ID is given, the message is sent
|
||||
to only that process.</P
|
||||
></DD
|
||||
><DT
|
||||
>message-type</DT
|
||||
><DD
|
||||
><P
|
||||
>Type of message to send. See
|
||||
the section <CODE
|
||||
CLASS="CONSTANT"
|
||||
>MESSAGE-TYPES</CODE
|
||||
> for details.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>parameters</DT
|
||||
><DD
|
||||
><P
|
||||
>any parameters required for the message-type</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN73"
|
||||
></A
|
||||
><H2
|
||||
>MESSAGE-TYPES</H2
|
||||
><P
|
||||
>Available message types are:</P
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>close-share</DT
|
||||
><DD
|
||||
><P
|
||||
>Order smbd to close the client
|
||||
<tt>nmbd.pid</tt> file.</p><p>If a single process ID is given, the message is sent
|
||||
to only that process.</p></dd><dt><span class="term">message-type</span></dt><dd><p>Type of message to send. See
|
||||
the section <tt>MESSAGE-TYPES</tt> for details.
|
||||
</p></dd><dt><span class="term">parameters</span></dt><dd><p>any parameters required for the message-type</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>MESSAGE-TYPES</h2><p>Available message types are:</p><div class="variablelist"><dl><dt><span class="term">close-share</span></dt><dd><p>Order smbd to close the client
|
||||
connections to the named share. Note that this doesn't affect client
|
||||
connections to any other shares. This message-type takes an argument of the
|
||||
share name for which client connections will be closed, or the
|
||||
"*" character which will close all currently open shares.
|
||||
"*" character which will close all currently open shares.
|
||||
This may be useful if you made changes to the access controls on the share.
|
||||
This message can only be sent to <CODE
|
||||
CLASS="CONSTANT"
|
||||
>smbd</CODE
|
||||
>.</P
|
||||
></DD
|
||||
><DT
|
||||
>debug</DT
|
||||
><DD
|
||||
><P
|
||||
>Set debug level to the value specified by the
|
||||
parameter. This can be sent to any of the destinations.</P
|
||||
></DD
|
||||
><DT
|
||||
>force-election</DT
|
||||
><DD
|
||||
><P
|
||||
>This message causes the <B
|
||||
CLASS="COMMAND"
|
||||
>nmbd</B
|
||||
> daemon to
|
||||
force a new browse master election. </P
|
||||
></DD
|
||||
><DT
|
||||
>ping</DT
|
||||
><DD
|
||||
><P
|
||||
> Send specified number of "ping" messages and
|
||||
wait for the same number of reply "pong" messages. This can be sent to
|
||||
any of the destinations.</P
|
||||
></DD
|
||||
><DT
|
||||
>profile</DT
|
||||
><DD
|
||||
><P
|
||||
>Change profile settings of a daemon, based on the
|
||||
parameter. The parameter can be "on" to turn on profile stats
|
||||
collection, "off" to turn off profile stats collection, "count"
|
||||
This message can only be sent to <tt>smbd</tt>.</p></dd><dt><span class="term">debug</span></dt><dd><p>Set debug level to the value specified by the
|
||||
parameter. This can be sent to any of the destinations.</p></dd><dt><span class="term">force-election</span></dt><dd><p>This message causes the <b>nmbd</b> daemon to
|
||||
force a new browse master election. </p></dd><dt><span class="term">ping</span></dt><dd><p>
|
||||
Send specified number of "ping" messages and
|
||||
wait for the same number of reply "pong" messages. This can be sent to
|
||||
any of the destinations.</p></dd><dt><span class="term">profile</span></dt><dd><p>Change profile settings of a daemon, based on the
|
||||
parameter. The parameter can be "on" to turn on profile stats
|
||||
collection, "off" to turn off profile stats collection, "count"
|
||||
to enable only collection of count stats (time stats are
|
||||
disabled), and "flush" to zero the current profile stats. This can
|
||||
be sent to any smbd or nmbd destinations.</P
|
||||
></DD
|
||||
><DT
|
||||
>debuglevel</DT
|
||||
><DD
|
||||
><P
|
||||
> Request debuglevel of a certain daemon and write it to stdout. This
|
||||
can be sent to any of the destinations.</P
|
||||
></DD
|
||||
><DT
|
||||
>profilelevel</DT
|
||||
><DD
|
||||
><P
|
||||
> Request profilelevel of a certain daemon and write it to stdout.
|
||||
This can be sent to any smbd or nmbd destinations.</P
|
||||
></DD
|
||||
><DT
|
||||
>printnotify</DT
|
||||
><DD
|
||||
><P
|
||||
> Order smbd to send a printer notify message to any Windows NT clients
|
||||
disabled), and "flush" to zero the current profile stats. This can
|
||||
be sent to any smbd or nmbd destinations.</p></dd><dt><span class="term">debuglevel</span></dt><dd><p>
|
||||
Request debuglevel of a certain daemon and write it to stdout. This
|
||||
can be sent to any of the destinations.</p></dd><dt><span class="term">profilelevel</span></dt><dd><p>
|
||||
Request profilelevel of a certain daemon and write it to stdout.
|
||||
This can be sent to any smbd or nmbd destinations.</p></dd><dt><span class="term">printnotify</span></dt><dd><p>
|
||||
Order smbd to send a printer notify message to any Windows NT clients
|
||||
connected to a printer. This message-type takes the following arguments:
|
||||
</P
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>queuepause printername</DT
|
||||
><DD
|
||||
><P
|
||||
>Send a queue pause change notify
|
||||
message to the printer specified.</P
|
||||
></DD
|
||||
><DT
|
||||
>queueresume printername</DT
|
||||
><DD
|
||||
><P
|
||||
>Send a queue resume change notify
|
||||
message for the printer specified.</P
|
||||
></DD
|
||||
><DT
|
||||
>jobpause printername unixjobid</DT
|
||||
><DD
|
||||
><P
|
||||
>Send a job pause change notify
|
||||
</p><div class="variablelist"><dl><dt><span class="term">queuepause printername</span></dt><dd><p>Send a queue pause change notify
|
||||
message to the printer specified.</p></dd><dt><span class="term">queueresume printername</span></dt><dd><p>Send a queue resume change notify
|
||||
message for the printer specified.</p></dd><dt><span class="term">jobpause printername unixjobid</span></dt><dd><p>Send a job pause change notify
|
||||
message for the printer and unix jobid
|
||||
specified.</P
|
||||
></DD
|
||||
><DT
|
||||
>jobresume printername unixjobid</DT
|
||||
><DD
|
||||
><P
|
||||
>Send a job resume change notify
|
||||
specified.</p></dd><dt><span class="term">jobresume printername unixjobid</span></dt><dd><p>Send a job resume change notify
|
||||
message for the printer and unix jobid
|
||||
specified.</P
|
||||
></DD
|
||||
><DT
|
||||
>jobdelete printername unixjobid</DT
|
||||
><DD
|
||||
><P
|
||||
>Send a job delete change notify
|
||||
specified.</p></dd><dt><span class="term">jobdelete printername unixjobid</span></dt><dd><p>Send a job delete change notify
|
||||
message for the printer and unix jobid
|
||||
specified.</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
><P
|
||||
> Note that this message only sends notification that an
|
||||
specified.</p></dd></dl></div><p>
|
||||
Note that this message only sends notification that an
|
||||
event has occured. It doesn't actually cause the
|
||||
event to happen.
|
||||
</P
|
||||
><P
|
||||
>This message can only be sent to <CODE
|
||||
CLASS="CONSTANT"
|
||||
>smbd</CODE
|
||||
>. </P
|
||||
></DD
|
||||
><DT
|
||||
>samsync</DT
|
||||
><DD
|
||||
><P
|
||||
>Order smbd to synchronise sam database from PDC (being BDC). Can only be sent to <CODE
|
||||
CLASS="CONSTANT"
|
||||
>smbd</CODE
|
||||
>. </P
|
||||
><DIV
|
||||
CLASS="NOTE"
|
||||
><P
|
||||
></P
|
||||
><TABLE
|
||||
CLASS="NOTE"
|
||||
WIDTH="90%"
|
||||
BORDER="0"
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="25"
|
||||
ALIGN="CENTER"
|
||||
VALIGN="TOP"
|
||||
><IMG
|
||||
SRC="/usr/share/sgml/docbook/stylesheet/dsssl/modular/images/note.gif"
|
||||
HSPACE="5"
|
||||
ALT="Note"></TD
|
||||
><TD
|
||||
ALIGN="LEFT"
|
||||
VALIGN="TOP"
|
||||
><P
|
||||
>Not working at the moment</P
|
||||
></TD
|
||||
></TR
|
||||
></TABLE
|
||||
></DIV
|
||||
></DD
|
||||
><DT
|
||||
>samrepl</DT
|
||||
><DD
|
||||
><P
|
||||
>Send sam replication message, with specified serial. Can only be sent to <CODE
|
||||
CLASS="CONSTANT"
|
||||
>smbd</CODE
|
||||
>. Should not be used manually.</P
|
||||
></DD
|
||||
><DT
|
||||
>dmalloc-mark</DT
|
||||
><DD
|
||||
><P
|
||||
>Set a mark for dmalloc. Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support. </P
|
||||
></DD
|
||||
><DT
|
||||
>dmalloc-log-changed</DT
|
||||
><DD
|
||||
><P
|
||||
> Dump the pointers that have changed since the mark set by dmalloc-mark.
|
||||
Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support. </P
|
||||
></DD
|
||||
><DT
|
||||
>shutdown</DT
|
||||
><DD
|
||||
><P
|
||||
>Shut down specified daemon. Can be sent to both smbd and nmbd.</P
|
||||
></DD
|
||||
><DT
|
||||
>pool-usage</DT
|
||||
><DD
|
||||
><P
|
||||
>Print a human-readable description of all
|
||||
</p><p>This message can only be sent to <tt>smbd</tt>. </p></dd><dt><span class="term">samsync</span></dt><dd><p>Order smbd to synchronise sam database from PDC (being BDC). Can only be sent to <tt>smbd</tt>. </p><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3><p>Not working at the moment</p></div></dd><dt><span class="term">samrepl</span></dt><dd><p>Send sam replication message, with specified serial. Can only be sent to <tt>smbd</tt>. Should not be used manually.</p></dd><dt><span class="term">dmalloc-mark</span></dt><dd><p>Set a mark for dmalloc. Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support. </p></dd><dt><span class="term">dmalloc-log-changed</span></dt><dd><p>
|
||||
Dump the pointers that have changed since the mark set by dmalloc-mark.
|
||||
Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support. </p></dd><dt><span class="term">shutdown</span></dt><dd><p>Shut down specified daemon. Can be sent to both smbd and nmbd.</p></dd><dt><span class="term">pool-usage</span></dt><dd><p>Print a human-readable description of all
|
||||
talloc(pool) memory usage by the specified daemon/process. Available
|
||||
for both smbd and nmbd.</P
|
||||
></DD
|
||||
><DT
|
||||
>drvupgrade</DT
|
||||
><DD
|
||||
><P
|
||||
>Force clients of printers using specified driver
|
||||
for both smbd and nmbd.</p></dd><dt><span class="term">drvupgrade</span></dt><dd><p>Force clients of printers using specified driver
|
||||
to update their local version of the driver. Can only be
|
||||
sent to smbd.</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN167"
|
||||
></A
|
||||
><H2
|
||||
>VERSION</H2
|
||||
><P
|
||||
>This man page is correct for version 3.0 of
|
||||
the Samba suite.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN170"
|
||||
></A
|
||||
><H2
|
||||
>SEE ALSO</H2
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>nmbd</SPAN
|
||||
>(8)</SPAN
|
||||
> and <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbd</SPAN
|
||||
>(8)</SPAN
|
||||
>.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN179"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>The original Samba software and related utilities
|
||||
sent to smbd.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of
|
||||
the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="nmbd.8.html">nmbd(8)</a> and <a href="smbd.8.html">smbd(8)</a>.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.</P
|
||||
><P
|
||||
>The original Samba man pages were written by Karl Auer.
|
||||
to the way the Linux kernel is developed.</p><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/"
|
||||
TARGET="_top"
|
||||
> ftp://ftp.icce.rug.nl/pub/unix/</A
|
||||
>) and updated for the Samba 2.0
|
||||
excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
|
||||
ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for
|
||||
Samba 3.0 was done by Alexander Bokovoy.</P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
|
||||
|
||||
@ -1,391 +1,88 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>smbcquotas</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="SMBCQUOTAS.1"
|
||||
></A
|
||||
>smbcquotas</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>smbcquotas -- Set or get QUOTAs of NTFS 5 shares</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbcquotas</B
|
||||
> {//server/share} [-u user] [-L] [-F] [-S QUOTA_SET_COMMAND] [-n] [-t] [-v] [-d debuglevel] [-s configfile] [-l logfilebase] [-V] [-U username] [-N] [-k] [-A]</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN27"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
>This tool is part of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
> suite.</P
|
||||
><P
|
||||
>The <B
|
||||
CLASS="COMMAND"
|
||||
>smbcquotas</B
|
||||
> program manipulates NT Quotas on SMB file shares. </P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN35"
|
||||
></A
|
||||
><H2
|
||||
>OPTIONS</H2
|
||||
><P
|
||||
>The following options are available to the <B
|
||||
CLASS="COMMAND"
|
||||
>smbcquotas</B
|
||||
> program. </P
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>-u user</DT
|
||||
><DD
|
||||
><P
|
||||
> Specifies the user of whom the quotas are get or set.
|
||||
By default the current user's username will be used.</P
|
||||
></DD
|
||||
><DT
|
||||
>-L</DT
|
||||
><DD
|
||||
><P
|
||||
>Lists all quota records of the share.</P
|
||||
></DD
|
||||
><DT
|
||||
>-F</DT
|
||||
><DD
|
||||
><P
|
||||
>Show the share quota status and default limits.</P
|
||||
></DD
|
||||
><DT
|
||||
>-S QUOTA_SET_COMMAND</DT
|
||||
><DD
|
||||
><P
|
||||
>This command set/modify quotas for a user or on the share,
|
||||
depending on the QUOTA_SET_COMMAND parameter witch is described later</P
|
||||
></DD
|
||||
><DT
|
||||
>-n</DT
|
||||
><DD
|
||||
><P
|
||||
>This option displays all QUOTA information in numeric
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbcquotas</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbcquotas.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbcquotas — Set or get QUOTAs of NTFS 5 shares</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>smbcquotas</tt> {//server/share} [-u user] [-L] [-F] [-S QUOTA_SET_COMMAND] [-n] [-t] [-v] [-d debuglevel] [-s configfile] [-l logfilebase] [-V] [-U username] [-N] [-k] [-A]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p>The <b>smbcquotas</b> program manipulates NT Quotas on SMB file shares. </p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><p>The following options are available to the <b>smbcquotas</b> program. </p><div class="variablelist"><dl><dt><span class="term">-u user</span></dt><dd><p> Specifies the user of whom the quotas are get or set.
|
||||
By default the current user's username will be used.</p></dd><dt><span class="term">-L</span></dt><dd><p>Lists all quota records of the share.</p></dd><dt><span class="term">-F</span></dt><dd><p>Show the share quota status and default limits.</p></dd><dt><span class="term">-S QUOTA_SET_COMMAND</span></dt><dd><p>This command set/modify quotas for a user or on the share,
|
||||
depending on the QUOTA_SET_COMMAND parameter witch is described later</p></dd><dt><span class="term">-n</span></dt><dd><p>This option displays all QUOTA information in numeric
|
||||
format. The default is to convert SIDs to names and QUOTA limits
|
||||
to a readable string format. </P
|
||||
></DD
|
||||
><DT
|
||||
>-t</DT
|
||||
><DD
|
||||
><P
|
||||
> Don't actually do anything, only validate the correctness of
|
||||
to a readable string format. </p></dd><dt><span class="term">-t</span></dt><dd><p>
|
||||
Don't actually do anything, only validate the correctness of
|
||||
the arguments.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-v</DT
|
||||
><DD
|
||||
><P
|
||||
> Be verbose.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-h|--help</DT
|
||||
><DD
|
||||
><P
|
||||
>Print a summary of command line options.</P
|
||||
></DD
|
||||
><DT
|
||||
>-V</DT
|
||||
><DD
|
||||
><P
|
||||
>Prints the version number for
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
>.</P
|
||||
></DD
|
||||
><DT
|
||||
>-s <configuration file></DT
|
||||
><DD
|
||||
><P
|
||||
>The file specified contains the
|
||||
</p></dd><dt><span class="term">-v</span></dt><dd><p>
|
||||
Be verbose.
|
||||
</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
|
||||
</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for
|
||||
<b>smbd</b>.</p></dd><dt><span class="term">-s <configuration file></span></dt><dd><p>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 <A
|
||||
HREF="smb.conf.5.html"
|
||||
TARGET="_top"
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf(5)</TT
|
||||
></A
|
||||
> for more information.
|
||||
to provide. See <a href="smb.conf.5.html" target="_top"><tt>
|
||||
smb.conf(5)</tt></a> for more information.
|
||||
The default configuration file name is determined at
|
||||
compile time.</P
|
||||
></DD
|
||||
><DT
|
||||
>-d|--debug=debuglevel</DT
|
||||
><DD
|
||||
><P
|
||||
><VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>debuglevel</VAR
|
||||
> is an integer
|
||||
compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
|
||||
from 0 to 10. The default value if this parameter is
|
||||
not specified is zero.</P
|
||||
><P
|
||||
>The higher this value, the more detail will be
|
||||
not specified is zero.</p><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
|
||||
><P
|
||||
>Levels above 1 will generate considerable
|
||||
information about operations carried out.</p><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
|
||||
><P
|
||||
>Note that specifying this parameter here will
|
||||
override the <A
|
||||
HREF="smb.conf.5.html#loglevel"
|
||||
TARGET="_top"
|
||||
>log
|
||||
level</A
|
||||
> parameter in the <A
|
||||
HREF="smb.conf.5.html"
|
||||
TARGET="_top"
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf(5)</TT
|
||||
></A
|
||||
> file.</P
|
||||
></DD
|
||||
><DT
|
||||
>-l|--logfile=logbasename</DT
|
||||
><DD
|
||||
><P
|
||||
>File name for log/debug files. The extension
|
||||
<CODE
|
||||
CLASS="CONSTANT"
|
||||
>".client"</CODE
|
||||
> will be appended. The log file is
|
||||
never removed by the client.</P
|
||||
></DD
|
||||
><DT
|
||||
>-N</DT
|
||||
><DD
|
||||
><P
|
||||
>If specified, this parameter suppresses the normal
|
||||
data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
|
||||
override the <a href="smb.conf.5.html#loglevel" target="_top">log
|
||||
level</a> parameter in the <a href="smb.conf.5.html" target="_top">
|
||||
<tt>smb.conf(5)</tt></a> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
|
||||
<tt>".client"</tt> will be appended. The log file is
|
||||
never removed by the client.
|
||||
</p></dd><dt><span class="term">-N</span></dt><dd><p>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
|
||||
><P
|
||||
>Unless a password is specified on the command line or
|
||||
accessing a service that does not require a password. </p><p>Unless a password is specified on the command line or
|
||||
this parameter is specified, the client will request a
|
||||
password.</P
|
||||
></DD
|
||||
><DT
|
||||
>-k</DT
|
||||
><DD
|
||||
><P
|
||||
>Try to authenticate with kerberos. Only useful in
|
||||
an Active Directory environment.</P
|
||||
></DD
|
||||
><DT
|
||||
>-A|--authfile=filename</DT
|
||||
><DD
|
||||
><P
|
||||
>This option allows
|
||||
password.</p></dd><dt><span class="term">-k</span></dt><dd><p>
|
||||
Try to authenticate with kerberos. Only useful in
|
||||
an Active Directory environment.
|
||||
</p></dd><dt><span class="term">-A|--authfile=filename</span></dt><dd><p>This option allows
|
||||
you to specify a file from which to read the username and
|
||||
password used in the connection. The format of the file is</P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
>username = <value>
|
||||
password = <value>
|
||||
domain = <value></PRE
|
||||
></P
|
||||
><P
|
||||
>Make certain that the permissions on the file restrict
|
||||
access from unwanted users. </P
|
||||
></DD
|
||||
><DT
|
||||
>-U|--user=username[%password]</DT
|
||||
><DD
|
||||
><P
|
||||
>Sets the SMB username or username and password. </P
|
||||
><P
|
||||
>If %password is not specified, the user will be prompted. The
|
||||
client will first check the <VAR
|
||||
CLASS="ENVAR"
|
||||
>USER</VAR
|
||||
> environment variable, then the
|
||||
<VAR
|
||||
CLASS="ENVAR"
|
||||
>LOGNAME</VAR
|
||||
> variable and if either exists, the
|
||||
password used in the connection. The format of the file is
|
||||
</p><pre class="programlisting">
|
||||
username = <value>
|
||||
password = <value>
|
||||
domain = <value>
|
||||
</pre><p>Make certain that the permissions on the file restrict
|
||||
access from unwanted users. </p></dd><dt><span class="term">-U|--user=username[%password]</span></dt><dd><p>Sets the SMB username or username and password. </p><p>If %password is not specified, the user will be prompted. The
|
||||
client will first check the <tt>USER</tt> environment variable, then the
|
||||
<tt>LOGNAME</tt> variable and if either exists, the
|
||||
string is uppercased. If these environmental variables are not
|
||||
found, the username <CODE
|
||||
CLASS="CONSTANT"
|
||||
>GUEST</CODE
|
||||
> is used. </P
|
||||
><P
|
||||
>A third option is to use a credentials file which
|
||||
found, the username <tt>GUEST</tt> is used. </p><p>A third option is to use a credentials file which
|
||||
contains the plaintext of the username and password. This
|
||||
option is mainly provided for scripts where the admin does not
|
||||
wish to pass the credentials on the command line or via environment
|
||||
variables. If this method is used, make certain that the permissions
|
||||
on the file restrict access from unwanted users. See the
|
||||
<VAR
|
||||
CLASS="PARAMETER"
|
||||
>-A</VAR
|
||||
> for more details. </P
|
||||
><P
|
||||
>Be cautious about including passwords in scripts. Also, on
|
||||
<i><tt>-A</tt></i> for more details. </p><p>Be cautious about including passwords in scripts. Also, on
|
||||
many systems the command line of a running process may be seen
|
||||
via the <B
|
||||
CLASS="COMMAND"
|
||||
>ps</B
|
||||
> command. To be safe always allow
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>rpcclient</B
|
||||
> to prompt for a password and type
|
||||
it in directly. </P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN128"
|
||||
></A
|
||||
><H2
|
||||
>QUOTA_SET_COMAND</H2
|
||||
><P
|
||||
>The format of an ACL is one or more ACL entries separated by
|
||||
either commas or newlines. An ACL entry is one of the following: </P
|
||||
><P
|
||||
> for user setting quotas for the specified by -u or the current username:
|
||||
</P
|
||||
><P
|
||||
><KBD
|
||||
CLASS="USERINPUT"
|
||||
> UQLIM:<username><softlimit><hardlimit>
|
||||
</KBD
|
||||
></P
|
||||
><P
|
||||
> for setting the share quota defaults limits:
|
||||
</P
|
||||
><P
|
||||
><KBD
|
||||
CLASS="USERINPUT"
|
||||
> FSQLIM:<softlimit><hardlimit>
|
||||
</KBD
|
||||
></P
|
||||
><P
|
||||
> for changing the share quota settings:
|
||||
</P
|
||||
><P
|
||||
><KBD
|
||||
CLASS="USERINPUT"
|
||||
> FSQFLAGS:QUOTA_ENABLED/DENY_DISK/LOG_SOFTLIMIT/LOG_HARD_LIMIT
|
||||
</KBD
|
||||
></P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN140"
|
||||
></A
|
||||
><H2
|
||||
>EXIT STATUS</H2
|
||||
><P
|
||||
>The <B
|
||||
CLASS="COMMAND"
|
||||
>smbcquotas</B
|
||||
> program sets the exit status
|
||||
via the <b>ps</b> command. To be safe always allow
|
||||
<b>rpcclient</b> to prompt for a password and type
|
||||
it in directly. </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>QUOTA_SET_COMAND</h2><p>The format of an ACL is one or more ACL entries separated by
|
||||
either commas or newlines. An ACL entry is one of the following: </p><p>
|
||||
for user setting quotas for the specified by -u or the current username:
|
||||
</p><p><b><tt>
|
||||
UQLIM:<username><softlimit><hardlimit>
|
||||
</tt></b></p><p>
|
||||
for setting the share quota defaults limits:
|
||||
</p><p><b><tt>
|
||||
FSQLIM:<softlimit><hardlimit>
|
||||
</tt></b></p><p>
|
||||
for changing the share quota settings:
|
||||
</p><p><b><tt>
|
||||
FSQFLAGS:QUOTA_ENABLED/DENY_DISK/LOG_SOFTLIMIT/LOG_HARD_LIMIT
|
||||
</tt></b></p></div><div class="refsect1" lang="en"><h2>EXIT STATUS</h2><p>The <b>smbcquotas</b> program sets the exit status
|
||||
depending on the success or otherwise of the operations performed.
|
||||
The exit status may be one of the following values. </P
|
||||
><P
|
||||
>If the operation succeeded, smbcquotas returns an exit
|
||||
status of 0. If <B
|
||||
CLASS="COMMAND"
|
||||
>smbcquotas</B
|
||||
> couldn't connect to the specified server,
|
||||
The exit status may be one of the following values. </p><p>If the operation succeeded, smbcquotas returns an exit
|
||||
status of 0. If <b>smbcquotas</b> couldn't connect to the specified server,
|
||||
or when there was an error getting or setting the quota(s), an exit status
|
||||
of 1 is returned. If there was an error parsing any command line
|
||||
arguments, an exit status of 2 is returned. </P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN146"
|
||||
></A
|
||||
><H2
|
||||
>VERSION</H2
|
||||
><P
|
||||
>This man page is correct for version 3.0 of the Samba suite.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN149"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>The original Samba software and related utilities
|
||||
arguments, an exit status of 2 is returned. </p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbcacls</B
|
||||
> was written by Stefan Metzmacher.</P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
to the way the Linux kernel is developed.</p><p><b>smbcacls</b> was written by Stefan Metzmacher.</p></div></div></body></html>
|
||||
|
||||
@ -1,783 +1,183 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>smbd</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="SMBD.8"
|
||||
></A
|
||||
>smbd</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>smbd -- server to provide SMB/CIFS services to clients</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
> [-D] [-F] [-S] [-i] [-h] [-V] [-b] [-d <debug level>] [-l <log directory>] [-p <port number>] [-O <socket option>] [-s <configuration file>]</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN23"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
>This program is part of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
> suite.</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
> is the server daemon that
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbd</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbd.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbd — server to provide SMB/CIFS services to clients</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>smbd</tt> [-D] [-F] [-S] [-i] [-h] [-V] [-b] [-d <debug level>] [-l <log directory>] [-p <port number>] [-O <socket option>] [-s <configuration file>]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This program is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>smbd</b> 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/98/ME, Windows NT, Windows 2000,
|
||||
OS/2, DAVE for Macintosh, and smbfs for Linux.</P
|
||||
><P
|
||||
>An extensive description of the services that the
|
||||
OS/2, DAVE for Macintosh, and smbfs for Linux.</p><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 <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
>. This man page will not describe the
|
||||
services (see <a href="smb.conf.5.html">smb.conf(5)</a>. This man page will not describe the
|
||||
services, but will concentrate on the administrative aspects
|
||||
of running the server.</P
|
||||
><P
|
||||
>Please note that there are significant security
|
||||
implications to running this server, and the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> manual page should be regarded as mandatory reading before
|
||||
proceeding with installation.</P
|
||||
><P
|
||||
>A session is created whenever a client requests one.
|
||||
of running the server.</p><p>Please note that there are significant security
|
||||
implications to running this server, and the <a href="smb.conf.5.html">smb.conf(5)</a> manual page should be regarded as mandatory reading before
|
||||
proceeding with installation.</p><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
|
||||
><P
|
||||
>The configuration file, and any files that it includes,
|
||||
the copy of the server for that client terminates.</p><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 <B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
> killed and restarted.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN42"
|
||||
></A
|
||||
><H2
|
||||
>OPTIONS</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>-D</DT
|
||||
><DD
|
||||
><P
|
||||
>If specified, this parameter causes
|
||||
disconnect from the service, or <b>smbd</b> killed and restarted.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-D</span></dt><dd><p>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 <B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
> for
|
||||
daemon is the recommended way of running <b>smbd</b> for
|
||||
servers that provide more than casual use file and
|
||||
print services. This switch is assumed if <B
|
||||
CLASS="COMMAND"
|
||||
>smbd
|
||||
</B
|
||||
> is executed on the command line of a shell.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-F</DT
|
||||
><DD
|
||||
><P
|
||||
>If specified, this parameter causes
|
||||
the main <B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
> process to not daemonize,
|
||||
print services. This switch is assumed if <b>smbd
|
||||
</b> is executed on the command line of a shell.
|
||||
</p></dd><dt><span class="term">-F</span></dt><dd><p>If specified, this parameter causes
|
||||
the main <b>smbd</b> process to not daemonize,
|
||||
i.e. double-fork and disassociate with the terminal.
|
||||
Child processes are still created as normal to service
|
||||
each connection request, but the main process does not
|
||||
exit. This operation mode is suitable for running
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
> under process supervisors such
|
||||
as <B
|
||||
CLASS="COMMAND"
|
||||
>supervise</B
|
||||
> and <B
|
||||
CLASS="COMMAND"
|
||||
>svscan</B
|
||||
>
|
||||
from Daniel J. Bernstein's <B
|
||||
CLASS="COMMAND"
|
||||
>daemontools</B
|
||||
>
|
||||
<b>smbd</b> under process supervisors such
|
||||
as <b>supervise</b> and <b>svscan</b>
|
||||
from Daniel J. Bernstein's <b>daemontools</b>
|
||||
package, or the AIX process monitor.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-S</DT
|
||||
><DD
|
||||
><P
|
||||
>If specified, this parameter causes
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
> to log to standard output rather
|
||||
than a file.</P
|
||||
></DD
|
||||
><DT
|
||||
>-i</DT
|
||||
><DD
|
||||
><P
|
||||
>If this parameter is specified it causes the
|
||||
server to run "interactively", not as a daemon, even if the
|
||||
</p></dd><dt><span class="term">-S</span></dt><dd><p>If specified, this parameter causes
|
||||
<b>smbd</b> to log to standard output rather
|
||||
than a file.</p></dd><dt><span class="term">-i</span></dt><dd><p>If this parameter is specified it causes the
|
||||
server to run "interactively", not as a daemon, even if the
|
||||
server is executed on the command line of a shell. Setting this
|
||||
parameter negates the implicit deamon mode when run from the
|
||||
command line. <B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
> also logs to standard
|
||||
output, as if the <B
|
||||
CLASS="COMMAND"
|
||||
>-S</B
|
||||
> parameter had been
|
||||
command line. <b>smbd</b> also logs to standard
|
||||
output, as if the <b>-S</b> parameter had been
|
||||
given.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-V</DT
|
||||
><DD
|
||||
><P
|
||||
>Prints the version number for
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
>.</P
|
||||
></DD
|
||||
><DT
|
||||
>-s <configuration file></DT
|
||||
><DD
|
||||
><P
|
||||
>The file specified contains the
|
||||
</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for
|
||||
<b>smbd</b>.</p></dd><dt><span class="term">-s <configuration file></span></dt><dd><p>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 <A
|
||||
HREF="smb.conf.5.html"
|
||||
TARGET="_top"
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf(5)</TT
|
||||
></A
|
||||
> for more information.
|
||||
to provide. See <a href="smb.conf.5.html" target="_top"><tt>
|
||||
smb.conf(5)</tt></a> for more information.
|
||||
The default configuration file name is determined at
|
||||
compile time.</P
|
||||
></DD
|
||||
><DT
|
||||
>-d|--debug=debuglevel</DT
|
||||
><DD
|
||||
><P
|
||||
><VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>debuglevel</VAR
|
||||
> is an integer
|
||||
compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
|
||||
from 0 to 10. The default value if this parameter is
|
||||
not specified is zero.</P
|
||||
><P
|
||||
>The higher this value, the more detail will be
|
||||
not specified is zero.</p><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
|
||||
><P
|
||||
>Levels above 1 will generate considerable
|
||||
information about operations carried out.</p><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
|
||||
><P
|
||||
>Note that specifying this parameter here will
|
||||
override the <A
|
||||
HREF="smb.conf.5.html#loglevel"
|
||||
TARGET="_top"
|
||||
>log
|
||||
level</A
|
||||
> parameter in the <A
|
||||
HREF="smb.conf.5.html"
|
||||
TARGET="_top"
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf(5)</TT
|
||||
></A
|
||||
> file.</P
|
||||
></DD
|
||||
><DT
|
||||
>-l|--logfile=logbasename</DT
|
||||
><DD
|
||||
><P
|
||||
>File name for log/debug files. The extension
|
||||
<CODE
|
||||
CLASS="CONSTANT"
|
||||
>".client"</CODE
|
||||
> will be appended. The log file is
|
||||
never removed by the client.</P
|
||||
></DD
|
||||
><DT
|
||||
>-h|--help</DT
|
||||
><DD
|
||||
><P
|
||||
>Print a summary of command line options.</P
|
||||
></DD
|
||||
><DT
|
||||
>-b</DT
|
||||
><DD
|
||||
><P
|
||||
>Prints information about how
|
||||
Samba was built.</P
|
||||
></DD
|
||||
><DT
|
||||
>-l <log directory></DT
|
||||
><DD
|
||||
><P
|
||||
>If specified,
|
||||
<VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>log directory</VAR
|
||||
>
|
||||
specifies a log directory into which the "log.smbd" log
|
||||
data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
|
||||
override the <a href="smb.conf.5.html#loglevel" target="_top">log
|
||||
level</a> parameter in the <a href="smb.conf.5.html" target="_top">
|
||||
<tt>smb.conf(5)</tt></a> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
|
||||
<tt>".client"</tt> will be appended. The log file is
|
||||
never removed by the client.
|
||||
</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
|
||||
</p></dd><dt><span class="term">-b</span></dt><dd><p>Prints information about how
|
||||
Samba was built.</p></dd><dt><span class="term">-l <log directory></span></dt><dd><p>If specified,
|
||||
<i><tt>log directory</tt></i>
|
||||
specifies a log directory into which the "log.smbd" log
|
||||
file will be created for informational and debug
|
||||
messages from the running server. 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"
|
||||
TARGET="_top"
|
||||
><VAR
|
||||
CLASS="PARAMETER"
|
||||
>max log size</VAR
|
||||
></A
|
||||
>
|
||||
option in the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> file. <SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>Beware:</I
|
||||
></SPAN
|
||||
>
|
||||
If the directory specified does not exist, <B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
>
|
||||
its size may be controlled by the <a href="smb.conf.5.html#maxlogsize" target="_top"><i><tt>max log size</tt></i></a>
|
||||
option in the <a href="smb.conf.5.html">smb.conf(5)</a> file. <span class="emphasis"><em>Beware:</em></span>
|
||||
If the directory specified does not exist, <b>smbd</b>
|
||||
will log to the default debug log location defined at compile time.
|
||||
</P
|
||||
><P
|
||||
>The default log directory is specified at
|
||||
compile time.</P
|
||||
></DD
|
||||
><DT
|
||||
>-p <port number></DT
|
||||
><DD
|
||||
><P
|
||||
><VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>port number</VAR
|
||||
> is a positive integer
|
||||
</p><p>The default log directory is specified at
|
||||
compile time.</p></dd><dt><span class="term">-p <port number></span></dt><dd><p><i><tt>port number</tt></i> is a positive integer
|
||||
value. The default value if this parameter is not
|
||||
specified is 139.</P
|
||||
><P
|
||||
>This number is the port number that will be
|
||||
specified is 139.</p><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
|
||||
><P
|
||||
>In order for the server to be useful by most
|
||||
for help if you are in this situation.</p><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
|
||||
><P
|
||||
>This parameter is not normally specified except
|
||||
in the above situation.</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN127"
|
||||
></A
|
||||
><H2
|
||||
>FILES</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/inetd.conf</TT
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>If the server is to be run by the
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>inetd</B
|
||||
> meta-daemon, this file
|
||||
section 4.3.5.</p><p>This parameter is not normally specified except
|
||||
in the above situation.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><tt>/etc/inetd.conf</tt></span></dt><dd><p>If the server is to be run by the
|
||||
<b>inetd</b> meta-daemon, this file
|
||||
must contain suitable startup information for the
|
||||
meta-daemon. See the <A
|
||||
HREF="install.html"
|
||||
TARGET="_top"
|
||||
>"How to Install and Test SAMBA"</A
|
||||
>
|
||||
meta-daemon. See the <a href="install.html" target="_top">"How to Install and Test SAMBA"</a>
|
||||
document for details.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/rc</TT
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>or whatever initialization script your
|
||||
system uses).</P
|
||||
><P
|
||||
>If running the server as a daemon at startup,
|
||||
</p></dd><dt><span class="term"><tt>/etc/rc</tt></span></dt><dd><p>or whatever initialization script your
|
||||
system uses).</p><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 <A
|
||||
HREF="install.html"
|
||||
TARGET="_top"
|
||||
>"How to Install and Test SAMBA"</A
|
||||
>
|
||||
document for details.</P
|
||||
></DD
|
||||
><DT
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/services</TT
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>If running the server via the
|
||||
meta-daemon <B
|
||||
CLASS="COMMAND"
|
||||
>inetd</B
|
||||
>, this file
|
||||
sequence for the server. See the <a href="install.html" target="_top">"How to Install and Test SAMBA"</a>
|
||||
document for details.</p></dd><dt><span class="term"><tt>/etc/services</tt></span></dt><dd><p>If running the server via the
|
||||
meta-daemon <b>inetd</b>, 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 <A
|
||||
HREF="install.html"
|
||||
TARGET="_top"
|
||||
>"How to Install and Test SAMBA"</A
|
||||
>
|
||||
document for details.</P
|
||||
></DD
|
||||
><DT
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>/usr/local/samba/lib/smb.conf</TT
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>This is the default location of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> server configuration file. Other common places that systems
|
||||
install this file are <TT
|
||||
CLASS="FILENAME"
|
||||
>/usr/samba/lib/smb.conf</TT
|
||||
>
|
||||
and <TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/samba/smb.conf</TT
|
||||
>.</P
|
||||
><P
|
||||
>This file describes all the services the server
|
||||
is to make available to clients. See <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> for more information.</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN165"
|
||||
></A
|
||||
><H2
|
||||
>LIMITATIONS</H2
|
||||
><P
|
||||
>On some systems <B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
> cannot change uid back
|
||||
See the <a href="install.html" target="_top">"How to Install and Test SAMBA"</a>
|
||||
document for details.</p></dd><dt><span class="term"><tt>/usr/local/samba/lib/smb.conf</tt></span></dt><dd><p>This is the default location of the <a href="smb.conf.5.html">smb.conf(5)</a> server configuration file. Other common places that systems
|
||||
install this file are <tt>/usr/samba/lib/smb.conf</tt>
|
||||
and <tt>/etc/samba/smb.conf</tt>.</p><p>This file describes all the services the server
|
||||
is to make available to clients. See <a href="smb.conf.5.html">smb.conf(5)</a> for more information.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>LIMITATIONS</h2><p>On some systems <b>smbd</b> 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
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN169"
|
||||
></A
|
||||
><H2
|
||||
>ENVIRONMENT VARIABLES</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
><VAR
|
||||
CLASS="ENVAR"
|
||||
>PRINTER</VAR
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>If no printer name is specified to
|
||||
similar.</p></div><div class="refsect1" lang="en"><h2>ENVIRONMENT VARIABLES</h2><div class="variablelist"><dl><dt><span class="term"><tt>PRINTER</tt></span></dt><dd><p>If no printer name is specified to
|
||||
printable services, most systems will use the value of
|
||||
this variable (or <CODE
|
||||
CLASS="CONSTANT"
|
||||
>lp</CODE
|
||||
> if this variable is
|
||||
this variable (or <tt>lp</tt> if this variable is
|
||||
not defined) as the name of the printer to use. This
|
||||
is not specific to the server, however.</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN178"
|
||||
></A
|
||||
><H2
|
||||
>PAM INTERACTION</H2
|
||||
><P
|
||||
>Samba uses PAM for authentication (when presented with a plaintext
|
||||
is not specific to the server, however.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>PAM INTERACTION</h2><p>Samba uses PAM for authentication (when presented with a plaintext
|
||||
password), for account checking (is this account disabled?) and for
|
||||
session management. The degree too which samba supports PAM is restricted
|
||||
by the limitations of the SMB protocol and the <A
|
||||
HREF="smb.conf.5.html#OBEYPAMRESRICTIONS"
|
||||
TARGET="_top"
|
||||
><VAR
|
||||
CLASS="PARAMETER"
|
||||
>obey
|
||||
pam restricions</VAR
|
||||
></A
|
||||
> <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> paramater. When this is set, the following restrictions apply:
|
||||
</P
|
||||
><P
|
||||
></P
|
||||
><UL
|
||||
><LI
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>Account Validation</I
|
||||
></SPAN
|
||||
>: All accesses to a
|
||||
by the limitations of the SMB protocol and the <a href="smb.conf.5.html#OBEYPAMRESRICTIONS" target="_top"><i><tt>obey
|
||||
pam restricions</tt></i></a> <a href="smb.conf.5.html">smb.conf(5)</a> paramater. When this is set, the following restrictions apply:
|
||||
</p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>Account Validation</em></span>: All accesses to a
|
||||
samba server are checked
|
||||
against PAM to see if the account is vaild, not disabled and is permitted to
|
||||
login at this time. This also applies to encrypted logins.
|
||||
</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>Session Management</I
|
||||
></SPAN
|
||||
>: When not using share
|
||||
</p></li><li><p><span class="emphasis"><em>Session Management</em></span>: When not using share
|
||||
level secuirty, users must pass PAM's session checks before access
|
||||
is granted. Note however, that this is bypassed in share level secuirty.
|
||||
Note also that some older pam configuration files may need a line
|
||||
added for session support.
|
||||
</P
|
||||
></LI
|
||||
></UL
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN193"
|
||||
></A
|
||||
><H2
|
||||
>VERSION</H2
|
||||
><P
|
||||
>This man page is correct for version 3.0 of
|
||||
the Samba suite.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN196"
|
||||
></A
|
||||
><H2
|
||||
>DIAGNOSTICS</H2
|
||||
><P
|
||||
>Most diagnostics issued by the server are logged
|
||||
</p></li></ul></div></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of
|
||||
the Samba suite.</p></div><div class="refsect1" lang="en"><h2>DIAGNOSTICS</h2><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
|
||||
><P
|
||||
>The number and nature of diagnostics available depends
|
||||
at compile time, but may be overridden on the command line.</p><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
|
||||
><P
|
||||
>Most messages are reasonably self-explanatory. Unfortunately,
|
||||
the debug level to 3 and peruse the log files.</p><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
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN201"
|
||||
></A
|
||||
><H2
|
||||
>SIGNALS</H2
|
||||
><P
|
||||
>Sending the <B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
> a SIGHUP will cause it to
|
||||
reload its <TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf</TT
|
||||
> configuration
|
||||
file within a short period of time.</P
|
||||
><P
|
||||
>To shut down a user's <B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
> process it is recommended
|
||||
that <B
|
||||
CLASS="COMMAND"
|
||||
>SIGKILL (-9)</B
|
||||
> <SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>NOT</I
|
||||
></SPAN
|
||||
>
|
||||
diagnostics you are seeing.</p></div><div class="refsect1" lang="en"><h2>SIGNALS</h2><p>Sending the <b>smbd</b> a SIGHUP will cause it to
|
||||
reload its <tt>smb.conf</tt> configuration
|
||||
file within a short period of time.</p><p>To shut down a user's <b>smbd</b> process it is recommended
|
||||
that <b>SIGKILL (-9)</b> <span class="emphasis"><em>NOT</em></span>
|
||||
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 <B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
> is to send it a SIGTERM (-15) signal and wait for
|
||||
it to die on its own.</P
|
||||
><P
|
||||
>The debug log level of <B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
> may be raised
|
||||
or lowered using <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbcontrol</SPAN
|
||||
>(1)</SPAN
|
||||
> program (SIGUSR[1|2] signals are no longer
|
||||
an <b>smbd</b> is to send it a SIGTERM (-15) signal and wait for
|
||||
it to die on its own.</p><p>The debug log level of <b>smbd</b> may be raised
|
||||
or lowered using <a href="smbcontrol.1.html">smbcontrol(1)</a> program (SIGUSR[1|2] signals are no longer
|
||||
used since Samba 2.2). This is to allow transient problems to be diagnosed,
|
||||
whilst still running at a normally low log level.</P
|
||||
><P
|
||||
>Note that as the signal handlers send a debug write,
|
||||
they are not re-entrant in <B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
>. This you should wait until
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
> is in a state of waiting for an incoming SMB before
|
||||
whilst still running at a normally low log level.</p><p>Note that as the signal handlers send a debug write,
|
||||
they are not re-entrant in <b>smbd</b>. This you should wait until
|
||||
<b>smbd</b> 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
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN219"
|
||||
></A
|
||||
><H2
|
||||
>SEE ALSO</H2
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>hosts_access</SPAN
|
||||
>(5)</SPAN
|
||||
>, <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>inetd</SPAN
|
||||
>(8)</SPAN
|
||||
>, <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>nmbd</SPAN
|
||||
>(8)</SPAN
|
||||
>, <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
>, <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbclient</SPAN
|
||||
>(1)</SPAN
|
||||
>, <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>testparm</SPAN
|
||||
>(1)</SPAN
|
||||
>, <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>testprns</SPAN
|
||||
>(1)</SPAN
|
||||
>, and the
|
||||
Internet RFC's <TT
|
||||
CLASS="FILENAME"
|
||||
>rfc1001.txt</TT
|
||||
>, <TT
|
||||
CLASS="FILENAME"
|
||||
>rfc1002.txt</TT
|
||||
>.
|
||||
them after, however this would affect performance.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="hosts_access.5.html">hosts_access(5)</a>, <a href="inetd.8.html">inetd(8)</a>, <a href="nmbd.8.html">nmbd(8)</a>, <a href="smb.conf.5.html">smb.conf(5)</a>, <a href="smbclient.1.html">smbclient(1)</a>, <a href="testparm.1.html">testparm(1)</a>, <a href="testprns.1.html">testprns(1)</a>, and the
|
||||
Internet RFC's <tt>rfc1001.txt</tt>, <tt>rfc1002.txt</tt>.
|
||||
In addition the CIFS (formerly SMB) specification is available
|
||||
as a link from the Web page <A
|
||||
HREF="http://samba.org/cifs/"
|
||||
TARGET="_top"
|
||||
>
|
||||
http://samba.org/cifs/</A
|
||||
>.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN246"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>The original Samba software and related utilities
|
||||
as a link from the Web page <a href="http://samba.org/cifs/" target="_top">
|
||||
http://samba.org/cifs/</a>.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.</P
|
||||
><P
|
||||
>The original Samba man pages were written by Karl Auer.
|
||||
to the way the Linux kernel is developed.</p><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/"
|
||||
TARGET="_top"
|
||||
> ftp://ftp.icce.rug.nl/pub/unix/</A
|
||||
>) and updated for the Samba 2.0
|
||||
excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
|
||||
ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for
|
||||
Samba 3.0 was done by Alexander Bokovoy.</P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
|
||||
|
||||
@ -1,184 +1,24 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>smbmnt</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="SMBMNT.8"
|
||||
></A
|
||||
>smbmnt</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>smbmnt -- helper utility for mounting SMB filesystems</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbmnt</B
|
||||
> {mount-point} [-s <share>] [-r] [-u <uid>] [-g <gid>] [-f <mask>] [-d <mask>] [-o <options>] [-h]</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN20"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbmnt</B
|
||||
> is a helper application used
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbmnt</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbmnt.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbmnt — helper utility for mounting SMB filesystems</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>smbmnt</tt> {mount-point} [-s <share>] [-r] [-u <uid>] [-g <gid>] [-f <mask>] [-d <mask>] [-o <options>] [-h]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p><b>smbmnt</b> is a helper application used
|
||||
by the smbmount program to do the actual mounting of SMB shares.
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>smbmnt</B
|
||||
> can be installed setuid root if you want
|
||||
normal users to be able to mount their SMB shares.</P
|
||||
><P
|
||||
>A setuid smbmnt will only allow mounts on directories owned
|
||||
by the user, and that the user has write permission on.</P
|
||||
><P
|
||||
>The <B
|
||||
CLASS="COMMAND"
|
||||
>smbmnt</B
|
||||
> program is normally invoked
|
||||
by <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbmount</SPAN
|
||||
>(8)</SPAN
|
||||
>. It should not be invoked directly by users. </P
|
||||
><P
|
||||
>smbmount searches the normal PATH for smbmnt. You must ensure
|
||||
that the smbmnt version in your path matches the smbmount used.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN32"
|
||||
></A
|
||||
><H2
|
||||
>OPTIONS</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>-r</DT
|
||||
><DD
|
||||
><P
|
||||
>mount the filesystem read-only
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-u uid</DT
|
||||
><DD
|
||||
><P
|
||||
>specify the uid that the files will
|
||||
be owned by </P
|
||||
></DD
|
||||
><DT
|
||||
>-g gid</DT
|
||||
><DD
|
||||
><P
|
||||
>specify the gid that the files will be
|
||||
owned by </P
|
||||
></DD
|
||||
><DT
|
||||
>-f mask</DT
|
||||
><DD
|
||||
><P
|
||||
>specify the octal file mask applied
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-d mask</DT
|
||||
><DD
|
||||
><P
|
||||
>specify the octal directory mask
|
||||
applied </P
|
||||
></DD
|
||||
><DT
|
||||
>-o options</DT
|
||||
><DD
|
||||
><P
|
||||
> list of options that are passed as-is to smbfs, if this
|
||||
<b>smbmnt</b> can be installed setuid root if you want
|
||||
normal users to be able to mount their SMB shares.</p><p>A setuid smbmnt will only allow mounts on directories owned
|
||||
by the user, and that the user has write permission on.</p><p>The <b>smbmnt</b> program is normally invoked
|
||||
by <a href="smbmount.8.html">smbmount(8)</a>. It should not be invoked directly by users. </p><p>smbmount searches the normal PATH for smbmnt. You must ensure
|
||||
that the smbmnt version in your path matches the smbmount used.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-r</span></dt><dd><p>mount the filesystem read-only
|
||||
</p></dd><dt><span class="term">-u uid</span></dt><dd><p>specify the uid that the files will
|
||||
be owned by </p></dd><dt><span class="term">-g gid</span></dt><dd><p>specify the gid that the files will be
|
||||
owned by </p></dd><dt><span class="term">-f mask</span></dt><dd><p>specify the octal file mask applied
|
||||
</p></dd><dt><span class="term">-d mask</span></dt><dd><p>specify the octal directory mask
|
||||
applied </p></dd><dt><span class="term">-o options</span></dt><dd><p>
|
||||
list of options that are passed as-is to smbfs, if this
|
||||
command is run on a 2.4 or higher Linux kernel.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-h|--help</DT
|
||||
><DD
|
||||
><P
|
||||
>Print a summary of command line options.</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN63"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>Volker Lendecke, Andrew Tridgell, Michael H. Warfield
|
||||
and others.</P
|
||||
><P
|
||||
>The current maintainer of smbfs and the userspace
|
||||
tools <B
|
||||
CLASS="COMMAND"
|
||||
>smbmount</B
|
||||
>, <B
|
||||
CLASS="COMMAND"
|
||||
>smbumount</B
|
||||
>,
|
||||
and <B
|
||||
CLASS="COMMAND"
|
||||
>smbmnt</B
|
||||
> is <A
|
||||
HREF="mailto:urban@teststation.com"
|
||||
TARGET="_top"
|
||||
>Urban Widmark</A
|
||||
>.
|
||||
The <A
|
||||
HREF="mailto:samba@samba.org"
|
||||
TARGET="_top"
|
||||
>SAMBA Mailing list</A
|
||||
>
|
||||
</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
|
||||
</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>Volker Lendecke, Andrew Tridgell, Michael H. Warfield
|
||||
and others.</p><p>The current maintainer of smbfs and the userspace
|
||||
tools <b>smbmount</b>, <b>smbumount</b>,
|
||||
and <b>smbmnt</b> is <a href="mailto:urban@teststation.com" target="_top">Urban Widmark</a>.
|
||||
The <a href="mailto:samba@samba.org" target="_top">SAMBA Mailing list</a>
|
||||
is the preferred place to ask questions regarding these programs.
|
||||
</P
|
||||
><P
|
||||
>The conversion of this manpage for Samba 2.2 was performed
|
||||
</p><p>The conversion of this manpage for Samba 2.2 was performed
|
||||
by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0
|
||||
was done by Alexander Bokovoy.</P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
was done by Alexander Bokovoy.</p></div></div></body></html>
|
||||
|
||||
@ -1,329 +1,70 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>smbmount</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="SMBMOUNT.8"
|
||||
></A
|
||||
>smbmount</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>smbmount -- mount an smbfs filesystem</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbmount</B
|
||||
> {service} {mount-point} [-o options]</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN14"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbmount</B
|
||||
> mounts a Linux SMB filesystem. It
|
||||
is usually invoked as <B
|
||||
CLASS="COMMAND"
|
||||
>mount.smbfs</B
|
||||
> by
|
||||
the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>mount</SPAN
|
||||
>(8)</SPAN
|
||||
> command when using the
|
||||
"-t smbfs" option. This command only works in Linux, and the kernel must
|
||||
support the smbfs filesystem. </P
|
||||
><P
|
||||
>Options to <B
|
||||
CLASS="COMMAND"
|
||||
>smbmount</B
|
||||
> are specified as a comma-separated
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbmount</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbmount.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbmount — mount an smbfs filesystem</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>smbmount</tt> {service} {mount-point} [-o options]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p><b>smbmount</b> mounts a Linux SMB filesystem. It
|
||||
is usually invoked as <b>mount.smbfs</b> by
|
||||
the <a href="mount.8.html">mount(8)</a> command when using the
|
||||
"-t smbfs" option. This command only works in Linux, and the kernel must
|
||||
support the smbfs filesystem. </p><p>Options to <b>smbmount</b> are specified as a comma-separated
|
||||
list of key=value pairs. It is possible to send options other
|
||||
than those listed here, assuming that smbfs supports them. If
|
||||
you get mount failures, check your kernel log for errors on
|
||||
unknown options.</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbmount</B
|
||||
> is a daemon. After mounting it keeps running until
|
||||
unknown options.</p><p><b>smbmount</b> is a daemon. After mounting it keeps running until
|
||||
the mounted smbfs is umounted. It will log things that happen
|
||||
when in daemon mode using the "machine name" smbmount, so
|
||||
typically this output will end up in <TT
|
||||
CLASS="FILENAME"
|
||||
>log.smbmount</TT
|
||||
>. The <B
|
||||
CLASS="COMMAND"
|
||||
> smbmount</B
|
||||
> process may also be called mount.smbfs.</P
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>NOTE:</I
|
||||
></SPAN
|
||||
> <B
|
||||
CLASS="COMMAND"
|
||||
>smbmount</B
|
||||
>
|
||||
calls <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbmnt</SPAN
|
||||
>(8)</SPAN
|
||||
> to do the actual mount. You
|
||||
must make sure that <B
|
||||
CLASS="COMMAND"
|
||||
>smbmnt</B
|
||||
> is in the path so
|
||||
that it can be found. </P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN35"
|
||||
></A
|
||||
><H2
|
||||
>OPTIONS</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>username=<arg></DT
|
||||
><DD
|
||||
><P
|
||||
>specifies the username to connect as. If
|
||||
this is not given, then the environment variable <VAR
|
||||
CLASS="ENVAR"
|
||||
> USER</VAR
|
||||
> is used. This option can also take the
|
||||
form "user%password" or "user/workgroup" or
|
||||
"user/workgroup%password" to allow the password and workgroup
|
||||
to be specified as part of the username.</P
|
||||
></DD
|
||||
><DT
|
||||
>password=<arg></DT
|
||||
><DD
|
||||
><P
|
||||
>specifies the SMB password. If this
|
||||
when in daemon mode using the "machine name" smbmount, so
|
||||
typically this output will end up in <tt>log.smbmount</tt>. The <b>
|
||||
smbmount</b> process may also be called mount.smbfs.</p><p><span class="emphasis"><em>NOTE:</em></span> <b>smbmount</b>
|
||||
calls <a href="smbmnt.8.html">smbmnt(8)</a> to do the actual mount. You
|
||||
must make sure that <b>smbmnt</b> is in the path so
|
||||
that it can be found. </p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">username=<arg></span></dt><dd><p>specifies the username to connect as. If
|
||||
this is not given, then the environment variable <tt>
|
||||
USER</tt> is used. This option can also take the
|
||||
form "user%password" or "user/workgroup" or
|
||||
"user/workgroup%password" to allow the password and workgroup
|
||||
to be specified as part of the username.</p></dd><dt><span class="term">password=<arg></span></dt><dd><p>specifies the SMB password. If this
|
||||
option is not given then the environment variable
|
||||
<VAR
|
||||
CLASS="ENVAR"
|
||||
>PASSWD</VAR
|
||||
> is used. If it can find
|
||||
no password <B
|
||||
CLASS="COMMAND"
|
||||
>smbmount</B
|
||||
> will prompt
|
||||
<tt>PASSWD</tt> is used. If it can find
|
||||
no password <b>smbmount</b> will prompt
|
||||
for a passeword, unless the guest option is
|
||||
given. </P
|
||||
><P
|
||||
> Note that passwords which contain the argument delimiter
|
||||
given. </p><p>
|
||||
Note that passwords which contain the argument delimiter
|
||||
character (i.e. a comma ',') will failed to be parsed correctly
|
||||
on the command line. However, the same password defined
|
||||
in the PASSWD environment variable or a credentials file (see
|
||||
below) will be read correctly.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>credentials=<filename></DT
|
||||
><DD
|
||||
><P
|
||||
>specifies a file that contains a username and/or password.
|
||||
</p></dd><dt><span class="term">credentials=<filename></span></dt><dd><p>specifies a file that contains a username and/or password.
|
||||
The format of the file is:
|
||||
<PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
>username = <value>
|
||||
password = <value></PRE
|
||||
></P
|
||||
><P
|
||||
>This is preferred over having passwords in plaintext in a
|
||||
shared file, such as <TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/fstab</TT
|
||||
>. Be sure to protect any
|
||||
</p><pre class="programlisting">
|
||||
username = <value>
|
||||
password = <value>
|
||||
</pre><p>This is preferred over having passwords in plaintext in a
|
||||
shared file, such as <tt>/etc/fstab</tt>. Be sure to protect any
|
||||
credentials file properly.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>krb</DT
|
||||
><DD
|
||||
><P
|
||||
>Use kerberos (Active Directory). </P
|
||||
></DD
|
||||
><DT
|
||||
>netbiosname=<arg></DT
|
||||
><DD
|
||||
><P
|
||||
>sets the source NetBIOS name. It defaults
|
||||
to the local hostname. </P
|
||||
></DD
|
||||
><DT
|
||||
>uid=<arg></DT
|
||||
><DD
|
||||
><P
|
||||
>sets the uid that will own all files on
|
||||
</p></dd><dt><span class="term">krb</span></dt><dd><p>Use kerberos (Active Directory). </p></dd><dt><span class="term">netbiosname=<arg></span></dt><dd><p>sets the source NetBIOS name. It defaults
|
||||
to the local hostname. </p></dd><dt><span class="term">uid=<arg></span></dt><dd><p>sets the uid that will own all files on
|
||||
the mounted filesystem.
|
||||
It may be specified as either a username or a numeric uid.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>gid=<arg></DT
|
||||
><DD
|
||||
><P
|
||||
>sets the gid that will own all files on
|
||||
</p></dd><dt><span class="term">gid=<arg></span></dt><dd><p>sets the gid that will own all files on
|
||||
the mounted filesystem.
|
||||
It may be specified as either a groupname or a numeric
|
||||
gid. </P
|
||||
></DD
|
||||
><DT
|
||||
>port=<arg></DT
|
||||
><DD
|
||||
><P
|
||||
>sets the remote SMB port number. The default
|
||||
is 139. </P
|
||||
></DD
|
||||
><DT
|
||||
>fmask=<arg></DT
|
||||
><DD
|
||||
><P
|
||||
>sets the file mask. This determines the
|
||||
gid. </p></dd><dt><span class="term">port=<arg></span></dt><dd><p>sets the remote SMB port number. The default
|
||||
is 139. </p></dd><dt><span class="term">fmask=<arg></span></dt><dd><p>sets the file mask. This determines the
|
||||
permissions that remote files have in the local filesystem.
|
||||
The default is based on the current umask. </P
|
||||
></DD
|
||||
><DT
|
||||
>dmask=<arg></DT
|
||||
><DD
|
||||
><P
|
||||
>Sets the directory mask. This determines the
|
||||
The default is based on the current umask. </p></dd><dt><span class="term">dmask=<arg></span></dt><dd><p>Sets the directory mask. This determines the
|
||||
permissions that remote directories have in the local filesystem.
|
||||
The default is based on the current umask. </P
|
||||
></DD
|
||||
><DT
|
||||
>debug=<arg></DT
|
||||
><DD
|
||||
><P
|
||||
>Sets the debug level. This is useful for
|
||||
The default is based on the current umask. </p></dd><dt><span class="term">debug=<arg></span></dt><dd><p>Sets the debug level. This is useful for
|
||||
tracking down SMB connection problems. A suggested value to
|
||||
start with is 4. If set too high there will be a lot of
|
||||
output, possibly hiding the useful output.</P
|
||||
></DD
|
||||
><DT
|
||||
>ip=<arg></DT
|
||||
><DD
|
||||
><P
|
||||
>Sets the destination host or IP address.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>workgroup=<arg></DT
|
||||
><DD
|
||||
><P
|
||||
>Sets the workgroup on the destination </P
|
||||
></DD
|
||||
><DT
|
||||
>sockopt=<arg></DT
|
||||
><DD
|
||||
><P
|
||||
>Sets the TCP socket options. See the <A
|
||||
HREF="smb.conf.5.html#SOCKETOPTIONS"
|
||||
TARGET="_top"
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
></A
|
||||
> <VAR
|
||||
CLASS="PARAMETER"
|
||||
>socket options</VAR
|
||||
> option.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>scope=<arg></DT
|
||||
><DD
|
||||
><P
|
||||
>Sets the NetBIOS scope </P
|
||||
></DD
|
||||
><DT
|
||||
>guest</DT
|
||||
><DD
|
||||
><P
|
||||
>Don't prompt for a password </P
|
||||
></DD
|
||||
><DT
|
||||
>ro</DT
|
||||
><DD
|
||||
><P
|
||||
>mount read-only </P
|
||||
></DD
|
||||
><DT
|
||||
>rw</DT
|
||||
><DD
|
||||
><P
|
||||
>mount read-write </P
|
||||
></DD
|
||||
><DT
|
||||
>iocharset=<arg></DT
|
||||
><DD
|
||||
><P
|
||||
> sets the charset used by the Linux side for codepage
|
||||
output, possibly hiding the useful output.</p></dd><dt><span class="term">ip=<arg></span></dt><dd><p>Sets the destination host or IP address.
|
||||
</p></dd><dt><span class="term">workgroup=<arg></span></dt><dd><p>Sets the workgroup on the destination </p></dd><dt><span class="term">sockopt=<arg></span></dt><dd><p>Sets the TCP socket options. See the <a href="smb.conf.5.html#SOCKETOPTIONS" target="_top"><a href="smb.conf.5.html">smb.conf(5)</a></a> <i><tt>socket options</tt></i> option.
|
||||
</p></dd><dt><span class="term">scope=<arg></span></dt><dd><p>Sets the NetBIOS scope </p></dd><dt><span class="term">guest</span></dt><dd><p>Don't prompt for a password </p></dd><dt><span class="term">ro</span></dt><dd><p>mount read-only </p></dd><dt><span class="term">rw</span></dt><dd><p>mount read-write </p></dd><dt><span class="term">iocharset=<arg></span></dt><dd><p>
|
||||
sets the charset used by the Linux side for codepage
|
||||
to charset translations (NLS). Argument should be the
|
||||
name of a charset, like iso8859-1. (Note: only kernel
|
||||
2.4.0 or later)
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>codepage=<arg></DT
|
||||
><DD
|
||||
><P
|
||||
> sets the codepage the server uses. See the iocharset
|
||||
</p></dd><dt><span class="term">codepage=<arg></span></dt><dd><p>
|
||||
sets the codepage the server uses. See the iocharset
|
||||
option. Example value cp850. (Note: only kernel 2.4.0
|
||||
or later)
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>ttl=<arg></DT
|
||||
><DD
|
||||
><P
|
||||
> sets how long a directory listing is cached in milliseconds
|
||||
</p></dd><dt><span class="term">ttl=<arg></span></dt><dd><p>
|
||||
sets how long a directory listing is cached in milliseconds
|
||||
(also affects visibility of file size and date
|
||||
changes). A higher value means that changes on the
|
||||
server take longer to be noticed but it can give
|
||||
@ -332,139 +73,34 @@ CLASS="PARAMETER"
|
||||
like 10000ms (10 seconds) is probably more reasonable
|
||||
in many cases.
|
||||
(Note: only kernel 2.4.2 or later)
|
||||
</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN134"
|
||||
></A
|
||||
><H2
|
||||
>ENVIRONMENT VARIABLES</H2
|
||||
><P
|
||||
>The variable <VAR
|
||||
CLASS="ENVAR"
|
||||
>USER</VAR
|
||||
> may contain the username of the
|
||||
</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>ENVIRONMENT VARIABLES</h2><p>The variable <tt>USER</tt> may contain the username of the
|
||||
person using the client. This information is used only if the
|
||||
protocol level is high enough to support session-level
|
||||
passwords. The variable can be used to set both username and
|
||||
password by using the format username%password.</P
|
||||
><P
|
||||
>The variable <VAR
|
||||
CLASS="ENVAR"
|
||||
>PASSWD</VAR
|
||||
> may contain the password of the
|
||||
password by using the format username%password.</p><p>The variable <tt>PASSWD</tt> 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
|
||||
><P
|
||||
>The variable <VAR
|
||||
CLASS="ENVAR"
|
||||
>PASSWD_FILE</VAR
|
||||
> may contain the pathname
|
||||
passwords.</p><p>The variable <tt>PASSWD_FILE</tt> may contain the pathname
|
||||
of a file to read the password from. A single line of input is
|
||||
read and used as the password.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN142"
|
||||
></A
|
||||
><H2
|
||||
>BUGS</H2
|
||||
><P
|
||||
>Passwords and other options containing , can not be handled.
|
||||
read and used as the password.</p></div><div class="refsect1" lang="en"><h2>BUGS</h2><p>Passwords and other options containing , can not be handled.
|
||||
For passwords an alternative way of passing them is in a credentials
|
||||
file or in the PASSWD environment.</P
|
||||
><P
|
||||
>The credentials file does not handle usernames or passwords with
|
||||
leading space.</P
|
||||
><P
|
||||
>One smbfs bug is important enough to mention here, even if it
|
||||
is a bit misplaced:</P
|
||||
><P
|
||||
></P
|
||||
><UL
|
||||
><LI
|
||||
><P
|
||||
>Mounts sometimes stop working. This is usually
|
||||
file or in the PASSWD environment.</p><p>The credentials file does not handle usernames or passwords with
|
||||
leading space.</p><p>One smbfs bug is important enough to mention here, even if it
|
||||
is a bit misplaced:</p><div class="itemizedlist"><ul type="disc"><li><p>Mounts sometimes stop working. This is usually
|
||||
caused by smbmount terminating. Since smbfs needs smbmount to
|
||||
reconnect when the server disconnects, the mount will eventually go
|
||||
dead. An umount/mount normally fixes this. At least 2 ways to
|
||||
trigger this bug are known.</P
|
||||
></LI
|
||||
></UL
|
||||
><P
|
||||
>Note that the typical response to a bug report is suggestion
|
||||
trigger this bug are known.</p></li></ul></div><p>Note that the typical response to a bug report is suggestion
|
||||
to try the latest version first. So please try doing that first,
|
||||
and always include which versions you use of relevant software
|
||||
when reporting bugs (minimum: samba, kernel, distribution)</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN151"
|
||||
></A
|
||||
><H2
|
||||
>SEE ALSO</H2
|
||||
><P
|
||||
>Documentation/filesystems/smbfs.txt in the linux kernel
|
||||
source tree may contain additional options and information.</P
|
||||
><P
|
||||
>FreeBSD also has a smbfs, but it is not related to smbmount</P
|
||||
><P
|
||||
>For Solaris, HP-UX and others you may want to look at <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbsh</SPAN
|
||||
>(1)</SPAN
|
||||
> or at other solutions, such as
|
||||
Sharity or perhaps replacing the SMB server with a NFS server.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN159"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>Volker Lendecke, Andrew Tridgell, Michael H. Warfield
|
||||
and others.</P
|
||||
><P
|
||||
>The current maintainer of smbfs and the userspace
|
||||
tools <B
|
||||
CLASS="COMMAND"
|
||||
>smbmount</B
|
||||
>, <B
|
||||
CLASS="COMMAND"
|
||||
>smbumount</B
|
||||
>,
|
||||
and <B
|
||||
CLASS="COMMAND"
|
||||
>smbmnt</B
|
||||
> is <A
|
||||
HREF="mailto:urban@teststation.com"
|
||||
TARGET="_top"
|
||||
>Urban Widmark</A
|
||||
>.
|
||||
The <A
|
||||
HREF="mailto:samba@samba.org"
|
||||
TARGET="_top"
|
||||
>SAMBA Mailing list</A
|
||||
>
|
||||
when reporting bugs (minimum: samba, kernel, distribution)</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p>Documentation/filesystems/smbfs.txt in the linux kernel
|
||||
source tree may contain additional options and information.</p><p>FreeBSD also has a smbfs, but it is not related to smbmount</p><p>For Solaris, HP-UX and others you may want to look at <a href="smbsh.1.html">smbsh(1)</a> or at other solutions, such as
|
||||
Sharity or perhaps replacing the SMB server with a NFS server.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>Volker Lendecke, Andrew Tridgell, Michael H. Warfield
|
||||
and others.</p><p>The current maintainer of smbfs and the userspace
|
||||
tools <b>smbmount</b>, <b>smbumount</b>,
|
||||
and <b>smbmnt</b> is <a href="mailto:urban@teststation.com" target="_top">Urban Widmark</a>.
|
||||
The <a href="mailto:samba@samba.org" target="_top">SAMBA Mailing list</a>
|
||||
is the preferred place to ask questions regarding these programs.
|
||||
</P
|
||||
><P
|
||||
>The conversion of this manpage for Samba 2.2 was performed
|
||||
</p><p>The conversion of this manpage for Samba 2.2 was performed
|
||||
by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0
|
||||
was done by Alexander Bokovoy.</P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
was done by Alexander Bokovoy.</p></div></div></body></html>
|
||||
|
||||
@ -1,358 +1,89 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>smbpasswd</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="SMBPASSWD.5"
|
||||
></A
|
||||
>smbpasswd</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>smbpasswd -- The Samba encrypted password file</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>smbpasswd</TT
|
||||
></P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN11"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
>This tool is part of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
> suite.</P
|
||||
><P
|
||||
>smbpasswd is the Samba encrypted password file. It contains
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbpasswd</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbpasswd.5"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbpasswd — The Samba encrypted password file</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><p><tt>smbpasswd</tt></p></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p>smbpasswd is the Samba 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
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN18"
|
||||
></A
|
||||
><H2
|
||||
>FILE FORMAT</H2
|
||||
><P
|
||||
>The format of the smbpasswd file used by Samba 2.2
|
||||
is very similar to the familiar Unix <TT
|
||||
CLASS="FILENAME"
|
||||
>passwd(5)</TT
|
||||
>
|
||||
Samba and has had several different formats in the past. </p></div><div class="refsect1" lang="en"><h2>FILE FORMAT</h2><p>The format of the smbpasswd file used by Samba 2.2
|
||||
is very similar to the familiar Unix <tt>passwd(5)</tt>
|
||||
file. It is an ASCII file containing one line for each user. Each field
|
||||
ithin 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
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>name</DT
|
||||
><DD
|
||||
><P
|
||||
> This is the user name. It must be a name that
|
||||
already exists in the standard UNIX passwd file. </P
|
||||
></DD
|
||||
><DT
|
||||
>uid</DT
|
||||
><DD
|
||||
><P
|
||||
>This is the UNIX uid. It must match the uid
|
||||
following information for each user: </p><div class="variablelist"><dl><dt><span class="term">name</span></dt><dd><p> This is the user name. It must be a name that
|
||||
already exists in the standard UNIX passwd file. </p></dd><dt><span class="term">uid</span></dt><dd><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 smbpasswd file entry as being valid for a user.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>Lanman Password Hash</DT
|
||||
><DD
|
||||
><P
|
||||
>This is the LANMAN hash of the user's password,
|
||||
</p></dd><dt><span class="term">Lanman Password Hash</span></dt><dd><p>This is the LANMAN hash of the user's password,
|
||||
encoded as 32 hex digits. The LANMAN hash is created by DES
|
||||
encrypting a well known string with the user's password as the
|
||||
DES key. This is the same password used by Windows 95/98 machines.
|
||||
Note that this password hash is regarded as weak as it is
|
||||
vulnerable to dictionary attacks and if two users choose the
|
||||
same password this entry will be identical (i.e. the password
|
||||
is not "salted" as the UNIX password is). If the user has a
|
||||
null password this field will contain the characters "NO PASSWORD"
|
||||
is not "salted" as the UNIX password is). If the user has a
|
||||
null password this field will contain the characters "NO PASSWORD"
|
||||
as the start of the hex string. If the hex string is equal to
|
||||
32 'X' characters then the user's account is marked as
|
||||
<CODE
|
||||
CLASS="CONSTANT"
|
||||
>disabled</CODE
|
||||
> and the user will not be able to
|
||||
log onto the Samba server. </P
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>WARNING !!</I
|
||||
></SPAN
|
||||
> Note that, due to
|
||||
<tt>disabled</tt> and the user will not be able to
|
||||
log onto the Samba server. </p><p><span class="emphasis"><em>WARNING !!</em></span> 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 <SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>plain text
|
||||
equivalents</I
|
||||
></SPAN
|
||||
> and must <SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>NOT</I
|
||||
></SPAN
|
||||
> be made
|
||||
reason these hashes are known as <span class="emphasis"><em>plain text
|
||||
equivalents</em></span> and must <span class="emphasis"><em>NOT</em></span> be made
|
||||
available to anyone but the root user. To protect these passwords
|
||||
the smbpasswd file is placed in a directory with read and
|
||||
traverse access only to the root user and the smbpasswd file
|
||||
itself must be set to be read/write only by root, with no
|
||||
other access. </P
|
||||
></DD
|
||||
><DT
|
||||
>NT Password Hash</DT
|
||||
><DD
|
||||
><P
|
||||
>This is the Windows NT hash of the user's
|
||||
other access. </p></dd><dt><span class="term">NT Password Hash</span></dt><dd><p>This is the Windows NT hash of the user's
|
||||
password, encoded as 32 hex digits. The Windows NT hash is
|
||||
created by taking the user's password as represented in
|
||||
16-bit, little-endian UNICODE and then applying the MD4
|
||||
(internet rfc1321) hashing algorithm to it. </P
|
||||
><P
|
||||
>This password hash is considered more secure than
|
||||
(internet rfc1321) hashing algorithm to it. </p><p>This password hash is considered more secure than
|
||||
the LANMAN Password Hash 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 "salted" as the UNIX password is). </P
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>WARNING !!</I
|
||||
></SPAN
|
||||
>. Note that, due to
|
||||
not "salted" as the UNIX password is). </p><p><span class="emphasis"><em>WARNING !!</em></span>. 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 <SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>plain text
|
||||
equivalents</I
|
||||
></SPAN
|
||||
> and must <SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>NOT</I
|
||||
></SPAN
|
||||
> be made
|
||||
reason these hashes are known as <span class="emphasis"><em>plain text
|
||||
equivalents</em></span> and must <span class="emphasis"><em>NOT</em></span> be made
|
||||
available to anyone but the root user. To protect these passwords
|
||||
the smbpasswd file is placed in a directory with read and
|
||||
traverse access only to the root user and the smbpasswd file
|
||||
itself must be set to be read/write only by root, with no
|
||||
other access. </P
|
||||
></DD
|
||||
><DT
|
||||
>Account Flags</DT
|
||||
><DD
|
||||
><P
|
||||
>This section contains flags that describe
|
||||
other access. </p></dd><dt><span class="term">Account Flags</span></dt><dd><p>This section contains flags that describe
|
||||
the attributes of the users account. In the Samba 2.2 release
|
||||
this field is bracketed by '[' and ']' characters and is always
|
||||
13 characters in length (including the '[' and ']' characters).
|
||||
The contents of this field may be any of the following characters:
|
||||
</P
|
||||
><P
|
||||
></P
|
||||
><UL
|
||||
><LI
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>U</I
|
||||
></SPAN
|
||||
> - This means
|
||||
this is a "User" account, i.e. an ordinary user. Only User
|
||||
</p><div class="itemizedlist"><ul type="disc"><li><p><span class="emphasis"><em>U</em></span> - This means
|
||||
this is a "User" account, i.e. an ordinary user. Only User
|
||||
and Workstation Trust accounts are currently supported
|
||||
in the smbpasswd file. </P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>N</I
|
||||
></SPAN
|
||||
> - This means the
|
||||
in the smbpasswd file. </p></li><li><p><span class="emphasis"><em>N</em></span> - This means the
|
||||
account has no password (the passwords in the fields LANMAN
|
||||
Password Hash and NT Password Hash are ignored). Note that this
|
||||
will only allow users to log on with no password if the <VAR
|
||||
CLASS="PARAMETER"
|
||||
> null passwords</VAR
|
||||
> parameter is set in the <A
|
||||
HREF="smb.conf.5.html#NULLPASSWORDS"
|
||||
TARGET="_top"
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
></A
|
||||
> config file. </P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>D</I
|
||||
></SPAN
|
||||
> - This means the account
|
||||
is disabled and no SMB/CIFS logins will be allowed for this user. </P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>W</I
|
||||
></SPAN
|
||||
> - This means this account
|
||||
is a "Workstation Trust" account. This kind of account is used
|
||||
will only allow users to log on with no password if the <i><tt>
|
||||
null passwords</tt></i> parameter is set in the <a href="smb.conf.5.html#NULLPASSWORDS" target="_top"><a href="smb.conf.5.html">smb.conf(5)</a></a> config file. </p></li><li><p><span class="emphasis"><em>D</em></span> - This means the account
|
||||
is disabled and no SMB/CIFS logins will be allowed for this user. </p></li><li><p><span class="emphasis"><em>W</em></span> - This means this account
|
||||
is a "Workstation Trust" 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
|
||||
></LI
|
||||
></UL
|
||||
><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
|
||||
></DD
|
||||
><DT
|
||||
>Last Change Time</DT
|
||||
><DD
|
||||
><P
|
||||
>This field consists of the time the account was
|
||||
and Servers to join a Domain hosted by a Samba PDC. </p></li></ul></div><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></dd><dt><span class="term">Last Change Time</span></dt><dd><p>This field consists of the time the account was
|
||||
last modified. It consists of the characters 'LCT-' (standing for
|
||||
"Last Change Time") followed by a numeric encoding of the UNIX time
|
||||
"Last Change Time") followed by a numeric encoding of the UNIX time
|
||||
in seconds since the epoch (1970) that the last change was made.
|
||||
</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
><P
|
||||
>All other colon separated fields are ignored at this time.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN77"
|
||||
></A
|
||||
><H2
|
||||
>VERSION</H2
|
||||
><P
|
||||
>This man page is correct for version 3.0 of
|
||||
the Samba suite.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN80"
|
||||
></A
|
||||
><H2
|
||||
>SEE ALSO</H2
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbpasswd</SPAN
|
||||
>(8)</SPAN
|
||||
>, <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
>, and
|
||||
</p></dd></dl></div><p>All other colon separated fields are ignored at this time.</p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of
|
||||
the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="smbpasswd.8.html">smbpasswd(8)</a>, <a href="Samba.7.html">Samba(7)</a>, and
|
||||
the Internet RFC1321 for details on the MD4 algorithm.
|
||||
</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN89"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>The original Samba software and related utilities
|
||||
</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.</P
|
||||
><P
|
||||
>The original Samba man pages were written by Karl Auer.
|
||||
to the way the Linux kernel is developed.</p><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/"
|
||||
TARGET="_top"
|
||||
> ftp://ftp.icce.rug.nl/pub/unix/</A
|
||||
>) and updated for the Samba 2.0
|
||||
excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
|
||||
ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2
|
||||
for Samba 3.0 was done by Alexander Bokovoy.</P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
|
||||
|
||||
@ -1,640 +1,163 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>smbpasswd</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="SMBPASSWD.8"
|
||||
></A
|
||||
>smbpasswd</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>smbpasswd -- change a user's SMB password</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbpasswd</B
|
||||
> [-a] [-x] [-d] [-e] [-D debuglevel] [-n] [-r <remote machine>] [-R <name resolve order>] [-m] [-U username[%password]] [-h] [-s] [-w pass] [-i] [-L] [username]</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN27"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
>This tool is part of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
> suite.</P
|
||||
><P
|
||||
>The smbpasswd program has several different
|
||||
functions, depending on whether it is run by the <SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>root</I
|
||||
></SPAN
|
||||
> user
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbpasswd</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbpasswd.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbpasswd — change a user's SMB password</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>smbpasswd</tt> [-a] [-x] [-d] [-e] [-D debuglevel] [-n] [-r <remote machine>] [-R <name resolve order>] [-m] [-U username[%password]] [-h] [-s] [-w pass] [-i] [-L] [username]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p>The smbpasswd program has several different
|
||||
functions, depending on whether it is run by the <span class="emphasis"><em>root</em></span> 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
|
||||
><P
|
||||
>By default (when run with no arguments) it will attempt to
|
||||
SMB passwords. </p><p>By default (when run with no arguments) it will attempt to
|
||||
change the current user's SMB password on the local machine. This is
|
||||
similar to the way the <B
|
||||
CLASS="COMMAND"
|
||||
>passwd(1)</B
|
||||
> program works. <B
|
||||
CLASS="COMMAND"
|
||||
> smbpasswd</B
|
||||
> differs from how the passwd program works
|
||||
however in that it is not <SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>setuid root</I
|
||||
></SPAN
|
||||
> but works in
|
||||
similar to the way the <b>passwd(1)</b> program works. <b>
|
||||
smbpasswd</b> differs from how the passwd program works
|
||||
however in that it is not <span class="emphasis"><em>setuid root</em></span> but works in
|
||||
a client-server mode and communicates with a
|
||||
locally running <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbd</SPAN
|
||||
>(8)</SPAN
|
||||
>. As a consequence in order for this to
|
||||
locally running <a href="smbd.8.html">smbd(8)</a>. As a consequence in order for this to
|
||||
succeed the smbd daemon must be running on the local machine. On a
|
||||
UNIX machine the encrypted SMB passwords are usually stored in
|
||||
the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbpasswd</SPAN
|
||||
>(5)</SPAN
|
||||
> file. </P
|
||||
><P
|
||||
>When run by an ordinary user with no options, smbpasswd
|
||||
the <a href="smbpasswd.5.html">smbpasswd(5)</a> file. </p><p>When run by an ordinary user with no options, smbpasswd
|
||||
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 smbpasswd file) then just press
|
||||
the <Enter> key when asked for your old password. </P
|
||||
><P
|
||||
>smbpasswd can also be used by a normal user to change their
|
||||
the string "NO PASSWORD" in the smbpasswd file) then just press
|
||||
the <Enter> key when asked for your old password. </p><p>smbpasswd 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 (<VAR
|
||||
CLASS="PARAMETER"
|
||||
>-r</VAR
|
||||
>) and <VAR
|
||||
CLASS="PARAMETER"
|
||||
>-U</VAR
|
||||
> options
|
||||
below. </P
|
||||
><P
|
||||
>When run by root, smbpasswd allows new users to be added
|
||||
Controllers. See the (<i><tt>-r</tt></i>) and <i><tt>-U</tt></i> options
|
||||
below. </p><p>When run by root, smbpasswd allows new users to be added
|
||||
and deleted in the smbpasswd file, as well as allows changes to
|
||||
the attributes of the user in this file to be made. When run by root, <B
|
||||
CLASS="COMMAND"
|
||||
> smbpasswd</B
|
||||
> accesses the local smbpasswd file
|
||||
the attributes of the user in this file to be made. When run by root, <b>
|
||||
smbpasswd</b> accesses the local smbpasswd file
|
||||
directly, thus enabling changes to be made even if smbd is not
|
||||
running. </P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN51"
|
||||
></A
|
||||
><H2
|
||||
>OPTIONS</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>-a</DT
|
||||
><DD
|
||||
><P
|
||||
>This option specifies that the username
|
||||
running. </p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-a</span></dt><dd><p>This option specifies that the username
|
||||
following should be added to the local smbpasswd file, with the
|
||||
new password typed (type <Enter> for the old password). This
|
||||
new password typed (type <Enter> for the old password). This
|
||||
option is ignored if the username following already exists in
|
||||
the smbpasswd file and it is treated like a regular change
|
||||
password command. Note that the default passdb backends require
|
||||
the user to already exist in the system password file (usually
|
||||
<TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/passwd</TT
|
||||
>), else the request to add the
|
||||
user will fail. </P
|
||||
><P
|
||||
>This option is only available when running smbpasswd
|
||||
as root. </P
|
||||
></DD
|
||||
><DT
|
||||
>-x</DT
|
||||
><DD
|
||||
><P
|
||||
>This option specifies that the username
|
||||
<tt>/etc/passwd</tt>), else the request to add the
|
||||
user will fail. </p><p>This option is only available when running smbpasswd
|
||||
as root. </p></dd><dt><span class="term">-x</span></dt><dd><p>This option specifies that the username
|
||||
following should be deleted from the local smbpasswd file.
|
||||
</P
|
||||
><P
|
||||
>This option is only available when running smbpasswd as
|
||||
root.</P
|
||||
></DD
|
||||
><DT
|
||||
>-d</DT
|
||||
><DD
|
||||
><P
|
||||
>This option specifies that the username following
|
||||
should be <CODE
|
||||
CLASS="CONSTANT"
|
||||
>disabled</CODE
|
||||
> in the local smbpasswd
|
||||
file. This is done by writing a <CODE
|
||||
CLASS="CONSTANT"
|
||||
>'D'</CODE
|
||||
> flag
|
||||
</p><p>This option is only available when running smbpasswd as
|
||||
root.</p></dd><dt><span class="term">-d</span></dt><dd><p>This option specifies that the username following
|
||||
should be <tt>disabled</tt> in the local smbpasswd
|
||||
file. This is done by writing a <tt>'D'</tt> flag
|
||||
into the account control space in the smbpasswd file. Once this
|
||||
is done all attempts to authenticate via SMB using this username
|
||||
will fail. </P
|
||||
><P
|
||||
>If the smbpasswd file is in the 'old' format (pre-Samba 2.0
|
||||
will fail. </p><p>If the smbpasswd file is in the 'old' format (pre-Samba 2.0
|
||||
format) there is no space in the user's password entry to write
|
||||
this information and the command will FAIL. See <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbpasswd</SPAN
|
||||
>(5)</SPAN
|
||||
> for details on the 'old' and new password file formats.
|
||||
</P
|
||||
><P
|
||||
>This option is only available when running smbpasswd as
|
||||
root.</P
|
||||
></DD
|
||||
><DT
|
||||
>-e</DT
|
||||
><DD
|
||||
><P
|
||||
>This option specifies that the username following
|
||||
should be <CODE
|
||||
CLASS="CONSTANT"
|
||||
>enabled</CODE
|
||||
> in the local smbpasswd file,
|
||||
this information and the command will FAIL. See <a href="smbpasswd.5.html">smbpasswd(5)</a> for details on the 'old' and new password file formats.
|
||||
</p><p>This option is only available when running smbpasswd as
|
||||
root.</p></dd><dt><span class="term">-e</span></dt><dd><p>This option specifies that the username following
|
||||
should be <tt>enabled</tt> in the local smbpasswd 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
|
||||
><P
|
||||
>If the smbpasswd file is in the 'old' format, then <B
|
||||
CLASS="COMMAND"
|
||||
> smbpasswd</B
|
||||
> will FAIL to enable the account.
|
||||
See <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbpasswd</SPAN
|
||||
>(5)</SPAN
|
||||
> for
|
||||
details on the 'old' and new password file formats. </P
|
||||
><P
|
||||
>This option is only available when running smbpasswd as root.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-D debuglevel</DT
|
||||
><DD
|
||||
><P
|
||||
><VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>debuglevel</VAR
|
||||
> is an integer
|
||||
the user will be able to authenticate via SMB once again. </p><p>If the smbpasswd file is in the 'old' format, then <b>
|
||||
smbpasswd</b> will FAIL to enable the account.
|
||||
See <a href="smbpasswd.5.html">smbpasswd(5)</a> for
|
||||
details on the 'old' and new password file formats. </p><p>This option is only available when running smbpasswd as root.
|
||||
</p></dd><dt><span class="term">-D debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
|
||||
from 0 to 10. The default value if this parameter is not specified
|
||||
is zero. </P
|
||||
><P
|
||||
>The higher this value, the more detail will be logged to the
|
||||
is zero. </p><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
|
||||
><P
|
||||
>Levels above 1 will generate considerable amounts of log
|
||||
critical errors and serious warnings will be logged. </p><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
|
||||
></DD
|
||||
><DT
|
||||
>-n</DT
|
||||
><DD
|
||||
><P
|
||||
>This option specifies that the username following
|
||||
</p></dd><dt><span class="term">-n</span></dt><dd><p>This option specifies that the username following
|
||||
should have their password set to null (i.e. a blank password) in
|
||||
the local smbpasswd file. This is done by writing the string "NO
|
||||
PASSWORD" as the first part of the first password stored in the
|
||||
smbpasswd file. </P
|
||||
><P
|
||||
>Note that to allow users to logon to a Samba server once
|
||||
the password has been set to "NO PASSWORD" in the smbpasswd
|
||||
the local smbpasswd file. This is done by writing the string "NO
|
||||
PASSWORD" as the first part of the first password stored in the
|
||||
smbpasswd file. </p><p>Note that to allow users to logon to a Samba server once
|
||||
the password has been set to "NO PASSWORD" in the smbpasswd
|
||||
file the administrator must set the following parameter in the [global]
|
||||
section of the <TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf</TT
|
||||
> file : </P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>null passwords = yes</B
|
||||
></P
|
||||
><P
|
||||
>This option is only available when running smbpasswd as
|
||||
root.</P
|
||||
></DD
|
||||
><DT
|
||||
>-r remote machine name</DT
|
||||
><DD
|
||||
><P
|
||||
>This option allows a user to specify what machine
|
||||
section of the <tt>smb.conf</tt> file : </p><p><b>null passwords = yes</b></p><p>This option is only available when running smbpasswd as
|
||||
root.</p></dd><dt><span class="term">-r remote machine name</span></dt><dd><p>This option allows a user to specify what machine
|
||||
they wish to change their password on. Without this parameter
|
||||
smbpasswd defaults to the local host. The <VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>remote
|
||||
machine name</VAR
|
||||
> is the NetBIOS name of the SMB/CIFS
|
||||
smbpasswd defaults to the local host. The <i><tt>remote
|
||||
machine name</tt></i> is the NetBIOS name of the SMB/CIFS
|
||||
server to contact to attempt the password change. This name is
|
||||
resolved into an IP address using the standard name resolution
|
||||
mechanism in all programs of the Samba suite. See the <VAR
|
||||
CLASS="PARAMETER"
|
||||
>-R
|
||||
name resolve order</VAR
|
||||
> parameter for details on changing
|
||||
this resolving mechanism. </P
|
||||
><P
|
||||
>The username whose password is changed is that of the
|
||||
current UNIX logged on user. See the <VAR
|
||||
CLASS="PARAMETER"
|
||||
>-U username</VAR
|
||||
>
|
||||
mechanism in all programs of the Samba suite. See the <i><tt>-R
|
||||
name resolve order</tt></i> parameter for details on changing
|
||||
this resolving mechanism. </p><p>The username whose password is changed is that of the
|
||||
current UNIX logged on user. See the <i><tt>-U username</tt></i>
|
||||
parameter for details on changing the password for a different
|
||||
username. </P
|
||||
><P
|
||||
>Note that if changing a Windows NT Domain password the
|
||||
username. </p><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
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>Note</I
|
||||
></SPAN
|
||||
> that Windows 95/98 do not have
|
||||
change).</p><p><span class="emphasis"><em>Note</em></span> 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
|
||||
></DD
|
||||
><DT
|
||||
>-R name resolve order</DT
|
||||
><DD
|
||||
><P
|
||||
>This option allows the user of smbpasswd to determine
|
||||
specifying a Win95/98 machine as remote machine target. </p></dd><dt><span class="term">-R name resolve order</span></dt><dd><p>This option allows the user of smbpasswd to determine
|
||||
what name resolution services to use when looking up the NetBIOS
|
||||
name of the host being connected to. </P
|
||||
><P
|
||||
>The options are :"lmhosts", "host", "wins" and "bcast". They
|
||||
cause names to be resolved as follows: </P
|
||||
><P
|
||||
></P
|
||||
><UL
|
||||
><LI
|
||||
><P
|
||||
><CODE
|
||||
CLASS="CONSTANT"
|
||||
>lmhosts</CODE
|
||||
>: Lookup an IP
|
||||
name of the host being connected to. </p><p>The options are :"lmhosts", "host", "wins" and "bcast". They
|
||||
cause names to be resolved as follows: </p><div class="itemizedlist"><ul type="disc"><li><p><tt>lmhosts</tt>: Lookup an IP
|
||||
address in the Samba lmhosts file. If the line in lmhosts has
|
||||
no name type attached to the NetBIOS name (see the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>lmhosts</SPAN
|
||||
>(5)</SPAN
|
||||
> for details) then
|
||||
any name type matches for lookup.</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><CODE
|
||||
CLASS="CONSTANT"
|
||||
>host</CODE
|
||||
>: Do a standard host
|
||||
name to IP address resolution, using the system <TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/hosts
|
||||
</TT
|
||||
>, NIS, or DNS lookups. This method of name resolution
|
||||
no name type attached to the NetBIOS name (see the <a href="lmhosts.5.html">lmhosts(5)</a> for details) then
|
||||
any name type matches for lookup.</p></li><li><p><tt>host</tt>: Do a standard host
|
||||
name to IP address resolution, using the system <tt>/etc/hosts
|
||||
</tt>, 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 <TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/nsswitch.conf</TT
|
||||
>
|
||||
may be controlled by the <tt>/etc/nsswitch.conf</tt>
|
||||
file). Note that this method is only used if the NetBIOS name
|
||||
type being queried is the 0x20 (server) name type, otherwise
|
||||
it is ignored.</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><CODE
|
||||
CLASS="CONSTANT"
|
||||
>wins</CODE
|
||||
>: Query a name with
|
||||
the IP address listed in the <VAR
|
||||
CLASS="PARAMETER"
|
||||
>wins server</VAR
|
||||
>
|
||||
it is ignored.</p></li><li><p><tt>wins</tt>: Query a name with
|
||||
the IP address listed in the <i><tt>wins server</tt></i>
|
||||
parameter. If no WINS server has been specified this method
|
||||
will be ignored.</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><CODE
|
||||
CLASS="CONSTANT"
|
||||
>bcast</CODE
|
||||
>: Do a broadcast on
|
||||
will be ignored.</p></li><li><p><tt>bcast</tt>: Do a broadcast on
|
||||
each of the known local interfaces listed in the
|
||||
<VAR
|
||||
CLASS="PARAMETER"
|
||||
>interfaces</VAR
|
||||
> parameter. This is the least
|
||||
<i><tt>interfaces</tt></i> parameter. This is the least
|
||||
reliable of the name resolution methods as it depends on the
|
||||
target host being on a locally connected subnet.</P
|
||||
></LI
|
||||
></UL
|
||||
><P
|
||||
>The default order is <B
|
||||
CLASS="COMMAND"
|
||||
>lmhosts, host, wins, bcast</B
|
||||
>
|
||||
and without this parameter or any entry in the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> file the name resolution methods will
|
||||
be attempted in this order. </P
|
||||
></DD
|
||||
><DT
|
||||
>-m</DT
|
||||
><DD
|
||||
><P
|
||||
>This option tells smbpasswd that the account
|
||||
target host being on a locally connected subnet.</p></li></ul></div><p>The default order is <b>lmhosts, host, wins, bcast</b>
|
||||
and without this parameter or any entry in the <a href="smb.conf.5.html">smb.conf(5)</a> file the name resolution methods will
|
||||
be attempted in this order. </p></dd><dt><span class="term">-m</span></dt><dd><p>This option tells smbpasswd that the account
|
||||
being changed is a MACHINE account. Currently this is used
|
||||
when Samba is being used as an NT Primary Domain Controller.</P
|
||||
><P
|
||||
>This option is only available when running smbpasswd as root.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-U username</DT
|
||||
><DD
|
||||
><P
|
||||
>This option may only be used in conjunction
|
||||
with the <VAR
|
||||
CLASS="PARAMETER"
|
||||
>-r</VAR
|
||||
> option. When changing
|
||||
when Samba is being used as an NT Primary Domain Controller.</p><p>This option is only available when running smbpasswd as root.
|
||||
</p></dd><dt><span class="term">-U username</span></dt><dd><p>This option may only be used in conjunction
|
||||
with the <i><tt>-r</tt></i> 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
|
||||
></DD
|
||||
><DT
|
||||
>-h</DT
|
||||
><DD
|
||||
><P
|
||||
>This option prints the help string for <B
|
||||
CLASS="COMMAND"
|
||||
> smbpasswd</B
|
||||
>, selecting the correct one for running as root
|
||||
or as an ordinary user. </P
|
||||
></DD
|
||||
><DT
|
||||
>-s</DT
|
||||
><DD
|
||||
><P
|
||||
>This option causes smbpasswd to be silent (i.e.
|
||||
different systems to change these passwords. </p></dd><dt><span class="term">-h</span></dt><dd><p>This option prints the help string for <b>
|
||||
smbpasswd</b>, selecting the correct one for running as root
|
||||
or as an ordinary user. </p></dd><dt><span class="term">-s</span></dt><dd><p>This option causes smbpasswd to be silent (i.e.
|
||||
not issue prompts) and to read its old and new passwords from
|
||||
standard input, rather than from <TT
|
||||
CLASS="FILENAME"
|
||||
>/dev/tty</TT
|
||||
>
|
||||
(like the <B
|
||||
CLASS="COMMAND"
|
||||
>passwd(1)</B
|
||||
> program does). This option
|
||||
is to aid people writing scripts to drive smbpasswd</P
|
||||
></DD
|
||||
><DT
|
||||
>-w password</DT
|
||||
><DD
|
||||
><P
|
||||
>This parameter is only available if Samba
|
||||
standard input, rather than from <tt>/dev/tty</tt>
|
||||
(like the <b>passwd(1)</b> program does). This option
|
||||
is to aid people writing scripts to drive smbpasswd</p></dd><dt><span class="term">-w password</span></dt><dd><p>This parameter is only available if Samba
|
||||
has been configured to use the experimental
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>--with-ldapsam</B
|
||||
> option. The <VAR
|
||||
CLASS="PARAMETER"
|
||||
>-w</VAR
|
||||
>
|
||||
<b>--with-ldapsam</b> option. The <i><tt>-w</tt></i>
|
||||
switch is used to specify the password to be used with the
|
||||
<A
|
||||
HREF="smb.conf.5.html#LDAPADMINDN"
|
||||
TARGET="_top"
|
||||
><VAR
|
||||
CLASS="PARAMETER"
|
||||
>ldap admin
|
||||
dn</VAR
|
||||
></A
|
||||
>. Note that the password is stored in
|
||||
the <TT
|
||||
CLASS="FILENAME"
|
||||
>secrets.tdb</TT
|
||||
> and is keyed off
|
||||
of the admin's DN. This means that if the value of <VAR
|
||||
CLASS="PARAMETER"
|
||||
>ldap
|
||||
admin dn</VAR
|
||||
> ever changes, the password will need to be
|
||||
<a href="smb.conf.5.html#LDAPADMINDN" target="_top"><i><tt>ldap admin
|
||||
dn</tt></i></a>. Note that the password is stored in
|
||||
the <tt>secrets.tdb</tt> and is keyed off
|
||||
of the admin's DN. This means that if the value of <i><tt>ldap
|
||||
admin dn</tt></i> ever changes, the password will need to be
|
||||
manually updated as well.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-i</DT
|
||||
><DD
|
||||
><P
|
||||
>This option tells smbpasswd that the account
|
||||
</p></dd><dt><span class="term">-i</span></dt><dd><p>This option tells smbpasswd that the account
|
||||
being changed is an interdomain trust account. Currently this is used
|
||||
when Samba is being used as an NT Primary Domain Controller.
|
||||
The account contains the info about another trusted domain.</P
|
||||
><P
|
||||
>This option is only available when running smbpasswd as root.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-L</DT
|
||||
><DD
|
||||
><P
|
||||
>Run in local mode.</P
|
||||
></DD
|
||||
><DT
|
||||
>username</DT
|
||||
><DD
|
||||
><P
|
||||
>This specifies the username for all of the
|
||||
<SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>root only</I
|
||||
></SPAN
|
||||
> options to operate on. Only root
|
||||
The account contains the info about another trusted domain.</p><p>This option is only available when running smbpasswd as root.
|
||||
</p></dd><dt><span class="term">-L</span></dt><dd><p>Run in local mode.</p></dd><dt><span class="term">username</span></dt><dd><p>This specifies the username for all of the
|
||||
<span class="emphasis"><em>root only</em></span> options to operate on. Only root
|
||||
can specify this parameter as only root has the permission needed
|
||||
to modify attributes directly in the local smbpasswd file.
|
||||
</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN189"
|
||||
></A
|
||||
><H2
|
||||
>NOTES</H2
|
||||
><P
|
||||
>Since <B
|
||||
CLASS="COMMAND"
|
||||
>smbpasswd</B
|
||||
> works in client-server
|
||||
</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>NOTES</h2><p>Since <b>smbpasswd</b> works in client-server
|
||||
mode communicating with a local smbd for a non-root user then
|
||||
the smbd daemon must be running for this to work. A common problem
|
||||
is to add a restriction to the hosts that may access the <B
|
||||
CLASS="COMMAND"
|
||||
> smbd</B
|
||||
> running on the local machine by specifying either <VAR
|
||||
CLASS="PARAMETER"
|
||||
>allow
|
||||
hosts</VAR
|
||||
> or <VAR
|
||||
CLASS="PARAMETER"
|
||||
>deny hosts</VAR
|
||||
> entry in
|
||||
the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> file and neglecting to
|
||||
allow "localhost" access to the smbd. </P
|
||||
><P
|
||||
>In addition, the smbpasswd command is only useful if Samba
|
||||
has been set up to use encrypted passwords. See the document <A
|
||||
HREF="pwencrypt.html"
|
||||
TARGET="_top"
|
||||
> "LanMan and NT Password Encryption in Samba"</A
|
||||
> in the docs directory for details
|
||||
on how to do this. </P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN201"
|
||||
></A
|
||||
><H2
|
||||
>VERSION</H2
|
||||
><P
|
||||
>This man page is correct for version 3.0 of the Samba suite.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN204"
|
||||
></A
|
||||
><H2
|
||||
>SEE ALSO</H2
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbpasswd</SPAN
|
||||
>(5)</SPAN
|
||||
>, <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
>.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN213"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>The original Samba software and related utilities
|
||||
is to add a restriction to the hosts that may access the <b>
|
||||
smbd</b> running on the local machine by specifying either <i><tt>allow
|
||||
hosts</tt></i> or <i><tt>deny hosts</tt></i> entry in
|
||||
the <a href="smb.conf.5.html">smb.conf(5)</a> file and neglecting to
|
||||
allow "localhost" access to the smbd. </p><p>In addition, the smbpasswd command is only useful if Samba
|
||||
has been set up to use encrypted passwords. See the document <a href="pwencrypt.html" target="_top">
|
||||
"LanMan and NT Password Encryption in Samba"</a> in the docs directory for details
|
||||
on how to do this. </p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="smbpasswd.5.html">smbpasswd(5)</a>, <a href="Samba.7.html">Samba(7)</a>.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.</P
|
||||
><P
|
||||
>The original Samba man pages were written by Karl Auer.
|
||||
to the way the Linux kernel is developed.</p><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/"
|
||||
TARGET="_top"
|
||||
> ftp://ftp.icce.rug.nl/pub/unix/</A
|
||||
>) and updated for the Samba 2.0
|
||||
excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
|
||||
ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2
|
||||
for Samba 3.0 was done by Alexander Bokovoy.</P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
|
||||
|
||||
@ -1,479 +1,110 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>smbsh</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="SMBSH.1"
|
||||
></A
|
||||
>smbsh</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>smbsh -- Allows access to Windows NT filesystem
|
||||
using UNIX commands</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbsh</B
|
||||
> [-W workgroup] [-U username] [-P prefix] [-R <name resolve order>] [-d <debug level>] [-l logfile] [-L libdir]</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN18"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
>This tool is part of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
> suite.</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbsh</B
|
||||
> allows you to access an NT filesystem
|
||||
using UNIX commands such as <B
|
||||
CLASS="COMMAND"
|
||||
>ls</B
|
||||
>, <B
|
||||
CLASS="COMMAND"
|
||||
> egrep</B
|
||||
>, and <B
|
||||
CLASS="COMMAND"
|
||||
>rcp</B
|
||||
>. You must use a
|
||||
shell that is dynamically linked in order for <B
|
||||
CLASS="COMMAND"
|
||||
>smbsh</B
|
||||
>
|
||||
to work correctly.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN30"
|
||||
></A
|
||||
><H2
|
||||
>OPTIONS</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>-W WORKGROUP</DT
|
||||
><DD
|
||||
><P
|
||||
>Override the default workgroup specified in the
|
||||
workgroup parameter of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> file
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbsh</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbsh.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbsh — Allows access to Windows NT filesystem
|
||||
using UNIX commands</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>smbsh</tt> [-W workgroup] [-U username] [-P prefix] [-R <name resolve order>] [-d <debug level>] [-l logfile] [-L libdir]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>smbsh</b> allows you to access an NT filesystem
|
||||
using UNIX commands such as <b>ls</b>, <b>
|
||||
egrep</b>, and <b>rcp</b>. You must use a
|
||||
shell that is dynamically linked in order for <b>smbsh</b>
|
||||
to work correctly.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-W WORKGROUP</span></dt><dd><p>Override the default workgroup specified in the
|
||||
workgroup parameter of the <a href="smb.conf.5.html">smb.conf(5)</a> file
|
||||
for this session. This may be needed to connect to some
|
||||
servers. </P
|
||||
></DD
|
||||
><DT
|
||||
>-U username[%pass]</DT
|
||||
><DD
|
||||
><P
|
||||
>Sets the SMB username or username and password.
|
||||
servers. </p></dd><dt><span class="term">-U username[%pass]</span></dt><dd><p>Sets the SMB username or username and password.
|
||||
If this option is not specified, the user will be prompted for
|
||||
both the username and the password. If %pass is not specified,
|
||||
the user will be prompted for the password.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-P prefix</DT
|
||||
><DD
|
||||
><P
|
||||
>This option allows
|
||||
</p></dd><dt><span class="term">-P prefix</span></dt><dd><p>This option allows
|
||||
the user to set the directory prefix for SMB access. The
|
||||
default value if this option is not specified is
|
||||
<SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>smb</I
|
||||
></SPAN
|
||||
>.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-s <configuration file></DT
|
||||
><DD
|
||||
><P
|
||||
>The file specified contains the
|
||||
<span class="emphasis"><em>smb</em></span>.
|
||||
</p></dd><dt><span class="term">-s <configuration file></span></dt><dd><p>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 <A
|
||||
HREF="smb.conf.5.html"
|
||||
TARGET="_top"
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf(5)</TT
|
||||
></A
|
||||
> for more information.
|
||||
to provide. See <a href="smb.conf.5.html" target="_top"><tt>
|
||||
smb.conf(5)</tt></a> for more information.
|
||||
The default configuration file name is determined at
|
||||
compile time.</P
|
||||
></DD
|
||||
><DT
|
||||
>-d|--debug=debuglevel</DT
|
||||
><DD
|
||||
><P
|
||||
><VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>debuglevel</VAR
|
||||
> is an integer
|
||||
compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
|
||||
from 0 to 10. The default value if this parameter is
|
||||
not specified is zero.</P
|
||||
><P
|
||||
>The higher this value, the more detail will be
|
||||
not specified is zero.</p><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
|
||||
><P
|
||||
>Levels above 1 will generate considerable
|
||||
information about operations carried out.</p><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
|
||||
><P
|
||||
>Note that specifying this parameter here will
|
||||
override the <A
|
||||
HREF="smb.conf.5.html#loglevel"
|
||||
TARGET="_top"
|
||||
>log
|
||||
level</A
|
||||
> parameter in the <A
|
||||
HREF="smb.conf.5.html"
|
||||
TARGET="_top"
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf(5)</TT
|
||||
></A
|
||||
> file.</P
|
||||
></DD
|
||||
><DT
|
||||
>-R <name resolve order></DT
|
||||
><DD
|
||||
><P
|
||||
>This option is used to determine what naming
|
||||
data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
|
||||
override the <a href="smb.conf.5.html#loglevel" target="_top">log
|
||||
level</a> parameter in the <a href="smb.conf.5.html" target="_top">
|
||||
<tt>smb.conf(5)</tt></a> file.</p></dd><dt><span class="term">-R <name resolve order></span></dt><dd><p>This option is used to determine what naming
|
||||
services and in what order to resolve
|
||||
host names to IP addresses. The option takes a space-separated
|
||||
string of different name resolution options.</P
|
||||
><P
|
||||
>The options are: "lmhosts", "host", "wins" and "bcast".
|
||||
They cause names to be resolved as follows :</P
|
||||
><P
|
||||
></P
|
||||
><UL
|
||||
><LI
|
||||
><P
|
||||
><CODE
|
||||
CLASS="CONSTANT"
|
||||
>lmhosts</CODE
|
||||
>:
|
||||
string of different name resolution options.</p><p>The options are: "lmhosts", "host", "wins" and "bcast".
|
||||
They cause names to be resolved as follows :</p><div class="itemizedlist"><ul type="disc"><li><p><tt>lmhosts</tt>:
|
||||
Lookup an IP address in the Samba lmhosts file. If the
|
||||
line in lmhosts has no name type attached to the
|
||||
NetBIOS name
|
||||
(see the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>lmhosts</SPAN
|
||||
>(5)</SPAN
|
||||
> for details)
|
||||
then any name type matches for lookup.</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><CODE
|
||||
CLASS="CONSTANT"
|
||||
>host</CODE
|
||||
>:
|
||||
(see the <a href="lmhosts.5.html">lmhosts(5)</a> for details)
|
||||
then any name type matches for lookup.
|
||||
</p></li><li><p><tt>host</tt>:
|
||||
Do a standard host name to IP address resolution, using
|
||||
the system <TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/hosts</TT
|
||||
>, NIS, or DNS
|
||||
the system <tt>/etc/hosts</tt>, 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 <TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/nsswitch.conf</TT
|
||||
> file). Note that this method is only used
|
||||
may be controlled by the <tt>/etc/nsswitch.conf
|
||||
</tt> file). Note that this method is only used
|
||||
if the NetBIOS name type being queried is the 0x20
|
||||
(server) name type, otherwise it is ignored.</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><CODE
|
||||
CLASS="CONSTANT"
|
||||
>wins</CODE
|
||||
>:
|
||||
(server) name type, otherwise it is ignored.
|
||||
</p></li><li><p><tt>wins</tt>:
|
||||
Query a name with the IP address listed in the
|
||||
<VAR
|
||||
CLASS="PARAMETER"
|
||||
>wins server</VAR
|
||||
> parameter. If no
|
||||
<i><tt>wins server</tt></i> parameter. If no
|
||||
WINS server has been specified this method will be
|
||||
ignored.</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><CODE
|
||||
CLASS="CONSTANT"
|
||||
>bcast</CODE
|
||||
>:
|
||||
ignored.
|
||||
</p></li><li><p><tt>bcast</tt>:
|
||||
Do a broadcast on each of the known local interfaces
|
||||
listed in the <VAR
|
||||
CLASS="PARAMETER"
|
||||
>interfaces</VAR
|
||||
>
|
||||
listed in the <i><tt>interfaces</tt></i>
|
||||
parameter. This is the least reliable of the name
|
||||
resolution methods as it depends on the target host
|
||||
being on a locally connected subnet.</P
|
||||
></LI
|
||||
></UL
|
||||
><P
|
||||
>If this parameter is not set then the name resolve order
|
||||
defined in the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> file parameter
|
||||
(<VAR
|
||||
CLASS="PARAMETER"
|
||||
>name resolve order</VAR
|
||||
>) will be used. </P
|
||||
><P
|
||||
>The default order is lmhosts, host, wins, bcast. Without
|
||||
this parameter or any entry in the <VAR
|
||||
CLASS="PARAMETER"
|
||||
>name resolve order</VAR
|
||||
> parameter of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> file, the name resolution methods
|
||||
will be attempted in this order. </P
|
||||
></DD
|
||||
><DT
|
||||
>-L libdir</DT
|
||||
><DD
|
||||
><P
|
||||
>This parameter specifies the location of the
|
||||
shared libraries used by <B
|
||||
CLASS="COMMAND"
|
||||
>smbsh</B
|
||||
>. The default
|
||||
being on a locally connected subnet.
|
||||
</p></li></ul></div><p>If this parameter is not set then the name resolve order
|
||||
defined in the <a href="smb.conf.5.html">smb.conf(5)</a> file parameter
|
||||
(<i><tt>name resolve order</tt></i>) will be used. </p><p>The default order is lmhosts, host, wins, bcast. Without
|
||||
this parameter or any entry in the <i><tt>name resolve order
|
||||
</tt></i> parameter of the <a href="smb.conf.5.html">smb.conf(5)</a> file, the name resolution methods
|
||||
will be attempted in this order. </p></dd><dt><span class="term">-L libdir</span></dt><dd><p>This parameter specifies the location of the
|
||||
shared libraries used by <b>smbsh</b>. The default
|
||||
value is specified at compile time.
|
||||
</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN106"
|
||||
></A
|
||||
><H2
|
||||
>EXAMPLES</H2
|
||||
><P
|
||||
>To use the <B
|
||||
CLASS="COMMAND"
|
||||
>smbsh</B
|
||||
> command, execute <B
|
||||
CLASS="COMMAND"
|
||||
> smbsh</B
|
||||
> from the prompt and enter the username and password
|
||||
</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>EXAMPLES</h2><p>To use the <b>smbsh</b> command, execute <b>
|
||||
smbsh</b> from the prompt and enter the username and password
|
||||
that authenticates you to the machine running the Windows NT
|
||||
operating system.
|
||||
<PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
><SAMP
|
||||
CLASS="PROMPT"
|
||||
>system% </SAMP
|
||||
><KBD
|
||||
CLASS="USERINPUT"
|
||||
>smbsh</KBD
|
||||
>
|
||||
<SAMP
|
||||
CLASS="PROMPT"
|
||||
>Username: </SAMP
|
||||
><KBD
|
||||
CLASS="USERINPUT"
|
||||
>user</KBD
|
||||
>
|
||||
<SAMP
|
||||
CLASS="PROMPT"
|
||||
>Password: </SAMP
|
||||
><KBD
|
||||
CLASS="USERINPUT"
|
||||
>XXXXXXX</KBD
|
||||
></PRE
|
||||
></P
|
||||
><P
|
||||
>Any dynamically linked command you execute from
|
||||
this shell will access the <TT
|
||||
CLASS="FILENAME"
|
||||
>/smb</TT
|
||||
> directory
|
||||
using the smb protocol. For example, the command <B
|
||||
CLASS="COMMAND"
|
||||
>ls /smb
|
||||
</B
|
||||
> will show a list of workgroups. The command
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>ls /smb/MYGROUP </B
|
||||
> will show all the machines in
|
||||
</p><pre class="programlisting">
|
||||
<tt>system% </tt><b><tt>smbsh</tt></b>
|
||||
<tt>Username: </tt><b><tt>user</tt></b>
|
||||
<tt>Password: </tt><b><tt>XXXXXXX</tt></b>
|
||||
</pre><p>Any dynamically linked command you execute from
|
||||
this shell will access the <tt>/smb</tt> directory
|
||||
using the smb protocol. For example, the command <b>ls /smb
|
||||
</b> will show a list of workgroups. The command
|
||||
<b>ls /smb/MYGROUP </b> will show all the machines in
|
||||
the workgroup MYGROUP. The command
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>ls /smb/MYGROUP/<machine-name></B
|
||||
> will show the share
|
||||
names for that machine. You could then, for example, use the <B
|
||||
CLASS="COMMAND"
|
||||
> cd</B
|
||||
> command to change directories, <B
|
||||
CLASS="COMMAND"
|
||||
>vi</B
|
||||
> to
|
||||
edit files, and <B
|
||||
CLASS="COMMAND"
|
||||
>rcp</B
|
||||
> to copy files.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN126"
|
||||
></A
|
||||
><H2
|
||||
>VERSION</H2
|
||||
><P
|
||||
>This man page is correct for version 3.0 of the Samba suite.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN129"
|
||||
></A
|
||||
><H2
|
||||
>BUGS</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbsh</B
|
||||
> works by intercepting the standard
|
||||
libc calls with the dynamically loaded versions in <TT
|
||||
CLASS="FILENAME"
|
||||
> smbwrapper.o</TT
|
||||
>. Not all calls have been "wrapped", so
|
||||
some programs may not function correctly under <B
|
||||
CLASS="COMMAND"
|
||||
>smbsh
|
||||
</B
|
||||
>.</P
|
||||
><P
|
||||
>Programs which are not dynamically linked cannot make
|
||||
use of <B
|
||||
CLASS="COMMAND"
|
||||
>smbsh</B
|
||||
>'s functionality. Most versions
|
||||
of UNIX have a <B
|
||||
CLASS="COMMAND"
|
||||
>file</B
|
||||
> command that will
|
||||
describe how a program was linked.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN138"
|
||||
></A
|
||||
><H2
|
||||
>SEE ALSO</H2
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbd</SPAN
|
||||
>(8)</SPAN
|
||||
>, <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
></P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN147"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>The original Samba software and related utilities
|
||||
<b>ls /smb/MYGROUP/<machine-name></b> will show the share
|
||||
names for that machine. You could then, for example, use the <b>
|
||||
cd</b> command to change directories, <b>vi</b> to
|
||||
edit files, and <b>rcp</b> to copy files.</p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><h2>BUGS</h2><p><b>smbsh</b> works by intercepting the standard
|
||||
libc calls with the dynamically loaded versions in <tt>
|
||||
smbwrapper.o</tt>. Not all calls have been "wrapped", so
|
||||
some programs may not function correctly under <b>smbsh
|
||||
</b>.</p><p>Programs which are not dynamically linked cannot make
|
||||
use of <b>smbsh</b>'s functionality. Most versions
|
||||
of UNIX have a <b>file</b> command that will
|
||||
describe how a program was linked.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="smbd.8.html">smbd(8)</a>, <a href="smb.conf.5.html">smb.conf(5)</a></p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.</P
|
||||
><P
|
||||
>The original Samba man pages were written by Karl Auer.
|
||||
to the way the Linux kernel is developed.</p><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/"
|
||||
TARGET="_top"
|
||||
> ftp://ftp.icce.rug.nl/pub/unix/</A
|
||||
>) and updated for the Samba 2.0
|
||||
excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
|
||||
ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2
|
||||
for Samba 3.0 was done by Alexander Bokovoy.</P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
|
||||
|
||||
@ -1,226 +1,35 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>smbspool</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="SMBSPOOL.8"
|
||||
></A
|
||||
>smbspool</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>smbspool -- send a print file to an SMB printer</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbspool</B
|
||||
> {job} {user} {title} {copies} {options} [filename]</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN17"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
>This tool is part of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
> suite.</P
|
||||
><P
|
||||
>smbspool is a very small print spooling program that
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbspool</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbspool.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbspool — send a print file to an SMB printer</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>smbspool</tt> {job} {user} {title} {copies} {options} [filename]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p>smbspool is a very small print spooling program that
|
||||
sends a print file to an SMB printer. The command-line arguments
|
||||
are position-dependent for compatibility with the Common UNIX
|
||||
Printing System, but you can use smbspool with any printing system
|
||||
or from a program or script.</P
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>DEVICE URI</I
|
||||
></SPAN
|
||||
></P
|
||||
><P
|
||||
>smbspool specifies the destination using a Uniform Resource
|
||||
Identifier ("URI") with a method of "smb". This string can take
|
||||
a number of forms:</P
|
||||
><P
|
||||
></P
|
||||
><UL
|
||||
><LI
|
||||
><P
|
||||
>smb://server/printer</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>smb://workgroup/server/printer</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>smb://username:password@server/printer</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>smb://username:password@workgroup/server/printer</P
|
||||
></LI
|
||||
></UL
|
||||
><P
|
||||
>smbspool tries to get the URI from argv[0]. If argv[0]
|
||||
contains the name of the program then it looks in the <VAR
|
||||
CLASS="ENVAR"
|
||||
> DEVICE_URI</VAR
|
||||
> environment variable.</P
|
||||
><P
|
||||
>Programs using the <B
|
||||
CLASS="COMMAND"
|
||||
>exec(2)</B
|
||||
> functions can
|
||||
or from a program or script.</p><p><span class="emphasis"><em>DEVICE URI</em></span></p><p>smbspool specifies the destination using a Uniform Resource
|
||||
Identifier ("URI") with a method of "smb". This string can take
|
||||
a number of forms:</p><div class="itemizedlist"><ul type="disc"><li><p>smb://server/printer</p></li><li><p>smb://workgroup/server/printer</p></li><li><p>smb://username:password@server/printer</p></li><li><p>smb://username:password@workgroup/server/printer</p></li></ul></div><p>smbspool tries to get the URI from argv[0]. If argv[0]
|
||||
contains the name of the program then it looks in the <tt>
|
||||
DEVICE_URI</tt> environment variable.</p><p>Programs using the <b>exec(2)</b> functions can
|
||||
pass the URI in argv[0], while shell scripts must set the
|
||||
<VAR
|
||||
CLASS="ENVAR"
|
||||
>DEVICE_URI</VAR
|
||||
> environment variable prior to
|
||||
running smbspool.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN41"
|
||||
></A
|
||||
><H2
|
||||
>OPTIONS</H2
|
||||
><P
|
||||
></P
|
||||
><UL
|
||||
><LI
|
||||
><P
|
||||
>The job argument (argv[1]) contains the
|
||||
<tt>DEVICE_URI</tt> environment variable prior to
|
||||
running smbspool.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="itemizedlist"><ul type="disc"><li><p>The job argument (argv[1]) contains the
|
||||
job ID number and is presently not used by smbspool.
|
||||
</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>The user argument (argv[2]) contains the
|
||||
</p></li><li><p>The user argument (argv[2]) contains the
|
||||
print user's name and is presently not used by smbspool.
|
||||
</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>The title argument (argv[3]) contains the
|
||||
</p></li><li><p>The title argument (argv[3]) contains the
|
||||
job title string and is passed as the remote file name
|
||||
when sending the print job.</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>The copies argument (argv[4]) contains
|
||||
when sending the print job.</p></li><li><p>The copies argument (argv[4]) contains
|
||||
the number of copies to be printed of the named file. If
|
||||
no filename is provided then this argument is not used by
|
||||
smbspool.</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>The options argument (argv[5]) contains
|
||||
smbspool.</p></li><li><p>The options argument (argv[5]) contains
|
||||
the print options in a single string and is currently
|
||||
not used by smbspool.</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>The filename argument (argv[6]) contains the
|
||||
not used by smbspool.</p></li><li><p>The filename argument (argv[6]) contains the
|
||||
name of the file to print. If this argument is not specified
|
||||
then the print file is read from the standard input.</P
|
||||
></LI
|
||||
></UL
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN56"
|
||||
></A
|
||||
><H2
|
||||
>VERSION</H2
|
||||
><P
|
||||
>This man page is correct for version 3.0 of the Samba suite.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN59"
|
||||
></A
|
||||
><H2
|
||||
>SEE ALSO</H2
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbd</SPAN
|
||||
>(8)</SPAN
|
||||
> and <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
>.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN68"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbspool</B
|
||||
> was written by Michael Sweet
|
||||
at Easy Software Products.</P
|
||||
><P
|
||||
>The original Samba software and related utilities
|
||||
then the print file is read from the standard input.</p></li></ul></div></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="smbd.8.html">smbd(8)</a> and <a href="Samba.7.html">Samba(7)</a>.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p><b>smbspool</b> was written by Michael Sweet
|
||||
at Easy Software Products.</p><p>The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.</P
|
||||
><P
|
||||
>The original Samba man pages were written by Karl Auer.
|
||||
to the way the Linux kernel is developed.</p><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/"
|
||||
TARGET="_top"
|
||||
> ftp://ftp.icce.rug.nl/pub/unix/</A
|
||||
>) and updated for the Samba 2.0
|
||||
excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
|
||||
ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2
|
||||
for Samba 3.0 was done by Alexander Bokovoy.</P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
|
||||
|
||||
@ -1,286 +1,44 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>smbstatus</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="SMBSTATUS.1"
|
||||
></A
|
||||
>smbstatus</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>smbstatus -- report on current Samba connections</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbstatus</B
|
||||
> [-P] [-b] [-d <debug level>] [-v] [-L] [-B] [-p] [-S] [-s <configuration file>] [-u <username>]</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN21"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
>This tool is part of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
> suite.</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbstatus</B
|
||||
> is a very simple program to
|
||||
list the current Samba connections.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN29"
|
||||
></A
|
||||
><H2
|
||||
>OPTIONS</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>-P|--profile</DT
|
||||
><DD
|
||||
><P
|
||||
>If samba has been compiled with the
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbstatus</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbstatus.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbstatus — report on current Samba connections</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>smbstatus</tt> [-P] [-b] [-d <debug level>] [-v] [-L] [-B] [-p] [-S] [-s <configuration file>] [-u <username>]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>smbstatus</b> is a very simple program to
|
||||
list the current Samba connections.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-P|--profile</span></dt><dd><p>If samba has been compiled with the
|
||||
profiling option, print only the contents of the profiling
|
||||
shared memory area.</P
|
||||
></DD
|
||||
><DT
|
||||
>-b|--brief</DT
|
||||
><DD
|
||||
><P
|
||||
>gives brief output.</P
|
||||
></DD
|
||||
><DT
|
||||
>-V</DT
|
||||
><DD
|
||||
><P
|
||||
>Prints the version number for
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
>.</P
|
||||
></DD
|
||||
><DT
|
||||
>-s <configuration file></DT
|
||||
><DD
|
||||
><P
|
||||
>The file specified contains the
|
||||
shared memory area.</p></dd><dt><span class="term">-b|--brief</span></dt><dd><p>gives brief output.</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for
|
||||
<b>smbd</b>.</p></dd><dt><span class="term">-s <configuration file></span></dt><dd><p>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 <A
|
||||
HREF="smb.conf.5.html"
|
||||
TARGET="_top"
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf(5)</TT
|
||||
></A
|
||||
> for more information.
|
||||
to provide. See <a href="smb.conf.5.html" target="_top"><tt>
|
||||
smb.conf(5)</tt></a> for more information.
|
||||
The default configuration file name is determined at
|
||||
compile time.</P
|
||||
></DD
|
||||
><DT
|
||||
>-d|--debug=debuglevel</DT
|
||||
><DD
|
||||
><P
|
||||
><VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>debuglevel</VAR
|
||||
> is an integer
|
||||
compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
|
||||
from 0 to 10. The default value if this parameter is
|
||||
not specified is zero.</P
|
||||
><P
|
||||
>The higher this value, the more detail will be
|
||||
not specified is zero.</p><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
|
||||
><P
|
||||
>Levels above 1 will generate considerable
|
||||
information about operations carried out.</p><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
|
||||
><P
|
||||
>Note that specifying this parameter here will
|
||||
override the <A
|
||||
HREF="smb.conf.5.html#loglevel"
|
||||
TARGET="_top"
|
||||
>log
|
||||
level</A
|
||||
> parameter in the <A
|
||||
HREF="smb.conf.5.html"
|
||||
TARGET="_top"
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf(5)</TT
|
||||
></A
|
||||
> file.</P
|
||||
></DD
|
||||
><DT
|
||||
>-l|--logfile=logbasename</DT
|
||||
><DD
|
||||
><P
|
||||
>File name for log/debug files. The extension
|
||||
<CODE
|
||||
CLASS="CONSTANT"
|
||||
>".client"</CODE
|
||||
> will be appended. The log file is
|
||||
never removed by the client.</P
|
||||
></DD
|
||||
><DT
|
||||
>-v|--verbose</DT
|
||||
><DD
|
||||
><P
|
||||
>gives verbose output.</P
|
||||
></DD
|
||||
><DT
|
||||
>-L|--locks</DT
|
||||
><DD
|
||||
><P
|
||||
>causes smbstatus to only list locks.</P
|
||||
></DD
|
||||
><DT
|
||||
>-B|--byterange</DT
|
||||
><DD
|
||||
><P
|
||||
>causes smbstatus to include byte range locks.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-p|--processes</DT
|
||||
><DD
|
||||
><P
|
||||
>print a list of <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbd</SPAN
|
||||
>(8)</SPAN
|
||||
> processes and exit.
|
||||
Useful for scripting.</P
|
||||
></DD
|
||||
><DT
|
||||
>-S|--shares</DT
|
||||
><DD
|
||||
><P
|
||||
>causes smbstatus to only list shares.</P
|
||||
></DD
|
||||
><DT
|
||||
>-h|--help</DT
|
||||
><DD
|
||||
><P
|
||||
>Print a summary of command line options.</P
|
||||
></DD
|
||||
><DT
|
||||
>-u|--user=<username></DT
|
||||
><DD
|
||||
><P
|
||||
>selects information relevant to
|
||||
<VAR
|
||||
CLASS="PARAMETER"
|
||||
>username</VAR
|
||||
> only.</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN99"
|
||||
></A
|
||||
><H2
|
||||
>VERSION</H2
|
||||
><P
|
||||
>This man page is correct for version 3.0 of
|
||||
the Samba suite.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN102"
|
||||
></A
|
||||
><H2
|
||||
>SEE ALSO</H2
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbd</SPAN
|
||||
>(8)</SPAN
|
||||
> and <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
>.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN111"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>The original Samba software and related utilities
|
||||
data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
|
||||
override the <a href="smb.conf.5.html#loglevel" target="_top">log
|
||||
level</a> parameter in the <a href="smb.conf.5.html" target="_top">
|
||||
<tt>smb.conf(5)</tt></a> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
|
||||
<tt>".client"</tt> will be appended. The log file is
|
||||
never removed by the client.
|
||||
</p></dd><dt><span class="term">-v|--verbose</span></dt><dd><p>gives verbose output.</p></dd><dt><span class="term">-L|--locks</span></dt><dd><p>causes smbstatus to only list locks.</p></dd><dt><span class="term">-B|--byterange</span></dt><dd><p>causes smbstatus to include byte range locks.
|
||||
</p></dd><dt><span class="term">-p|--processes</span></dt><dd><p>print a list of <a href="smbd.8.html">smbd(8)</a> processes and exit.
|
||||
Useful for scripting.</p></dd><dt><span class="term">-S|--shares</span></dt><dd><p>causes smbstatus to only list shares.</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
|
||||
</p></dd><dt><span class="term">-u|--user=<username></span></dt><dd><p>selects information relevant to
|
||||
<i><tt>username</tt></i> only.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of
|
||||
the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="smbd.8.html">smbd(8)</a> and <a href="smb.conf.5.html">smb.conf(5)</a>.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.</P
|
||||
><P
|
||||
>The original Samba man pages were written by Karl Auer.
|
||||
to the way the Linux kernel is developed.</p><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/"
|
||||
TARGET="_top"
|
||||
> ftp://ftp.icce.rug.nl/pub/unix/</A
|
||||
>) and updated for the Samba 2.0
|
||||
excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
|
||||
ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2
|
||||
for Samba 3.0 was done by Alexander Bokovoy.</P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
|
||||
|
||||
@ -1,351 +1,39 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>smbtar</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="SMBTAR.1"
|
||||
></A
|
||||
>smbtar</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>smbtar -- shell script for backing up SMB/CIFS shares
|
||||
directly to UNIX tape drives</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbtar</B
|
||||
> [-r] [-i] [-a] [-v] {-s server} [-p password] [-x services] [-X] [-N filename] [-b blocksize] [-d directory] [-l loglevel] [-u user] [-t tape] {filenames}</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN26"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
>This tool is part of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
> suite.</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbtar</B
|
||||
> is a very small shell script on top
|
||||
of <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbclient</SPAN
|
||||
>(1)</SPAN
|
||||
> which dumps SMB shares directly to tape.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN37"
|
||||
></A
|
||||
><H2
|
||||
>OPTIONS</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>-s server</DT
|
||||
><DD
|
||||
><P
|
||||
>The SMB/CIFS server that the share resides
|
||||
upon.</P
|
||||
></DD
|
||||
><DT
|
||||
>-x service</DT
|
||||
><DD
|
||||
><P
|
||||
>The share name on the server to connect to.
|
||||
The default is "backup".</P
|
||||
></DD
|
||||
><DT
|
||||
>-X</DT
|
||||
><DD
|
||||
><P
|
||||
>Exclude mode. Exclude filenames... from tar
|
||||
create or restore. </P
|
||||
></DD
|
||||
><DT
|
||||
>-d directory</DT
|
||||
><DD
|
||||
><P
|
||||
>Change to initial <VAR
|
||||
CLASS="PARAMETER"
|
||||
>directory
|
||||
</VAR
|
||||
> before restoring / backing up files. </P
|
||||
></DD
|
||||
><DT
|
||||
>-v</DT
|
||||
><DD
|
||||
><P
|
||||
>Verbose mode.</P
|
||||
></DD
|
||||
><DT
|
||||
>-p password</DT
|
||||
><DD
|
||||
><P
|
||||
>The password to use to access a share.
|
||||
Default: none </P
|
||||
></DD
|
||||
><DT
|
||||
>-u user</DT
|
||||
><DD
|
||||
><P
|
||||
>The user id to connect as. Default:
|
||||
UNIX login name. </P
|
||||
></DD
|
||||
><DT
|
||||
>-a</DT
|
||||
><DD
|
||||
><P
|
||||
>Reset DOS archive bit mode to
|
||||
indicate file has been archived. </P
|
||||
></DD
|
||||
><DT
|
||||
>-t tape</DT
|
||||
><DD
|
||||
><P
|
||||
>Tape device. May be regular file or tape
|
||||
device. Default: <VAR
|
||||
CLASS="PARAMETER"
|
||||
>$TAPE</VAR
|
||||
> environmental
|
||||
variable; if not set, a file called <TT
|
||||
CLASS="FILENAME"
|
||||
>tar.out
|
||||
</TT
|
||||
>. </P
|
||||
></DD
|
||||
><DT
|
||||
>-b blocksize</DT
|
||||
><DD
|
||||
><P
|
||||
>Blocking factor. Defaults to 20. See
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>tar(1)</B
|
||||
> for a fuller explanation. </P
|
||||
></DD
|
||||
><DT
|
||||
>-N filename</DT
|
||||
><DD
|
||||
><P
|
||||
>Backup only files newer than filename. Could
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbtar</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbtar.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbtar — shell script for backing up SMB/CIFS shares
|
||||
directly to UNIX tape drives</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>smbtar</tt> [-r] [-i] [-a] [-v] {-s server} [-p password] [-x services] [-X] [-N filename] [-b blocksize] [-d directory] [-l loglevel] [-u user] [-t tape] {filenames}</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>smbtar</b> is a very small shell script on top
|
||||
of <a href="smbclient.1.html">smbclient(1)</a> which dumps SMB shares directly to tape.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-s server</span></dt><dd><p>The SMB/CIFS server that the share resides
|
||||
upon.</p></dd><dt><span class="term">-x service</span></dt><dd><p>The share name on the server to connect to.
|
||||
The default is "backup".</p></dd><dt><span class="term">-X</span></dt><dd><p>Exclude mode. Exclude filenames... from tar
|
||||
create or restore. </p></dd><dt><span class="term">-d directory</span></dt><dd><p>Change to initial <i><tt>directory
|
||||
</tt></i> before restoring / backing up files. </p></dd><dt><span class="term">-v</span></dt><dd><p>Verbose mode.</p></dd><dt><span class="term">-p password</span></dt><dd><p>The password to use to access a share.
|
||||
Default: none </p></dd><dt><span class="term">-u user</span></dt><dd><p>The user id to connect as. Default:
|
||||
UNIX login name. </p></dd><dt><span class="term">-a</span></dt><dd><p>Reset DOS archive bit mode to
|
||||
indicate file has been archived. </p></dd><dt><span class="term">-t tape</span></dt><dd><p>Tape device. May be regular file or tape
|
||||
device. Default: <i><tt>$TAPE</tt></i> environmental
|
||||
variable; if not set, a file called <tt>tar.out
|
||||
</tt>. </p></dd><dt><span class="term">-b blocksize</span></dt><dd><p>Blocking factor. Defaults to 20. See
|
||||
<b>tar(1)</b> for a fuller explanation. </p></dd><dt><span class="term">-N filename</span></dt><dd><p>Backup only files newer than filename. Could
|
||||
be used (for example) on a log file to implement incremental
|
||||
backups. </P
|
||||
></DD
|
||||
><DT
|
||||
>-i</DT
|
||||
><DD
|
||||
><P
|
||||
>Incremental mode; tar files are only backed
|
||||
backups. </p></dd><dt><span class="term">-i</span></dt><dd><p>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
|
||||
></DD
|
||||
><DT
|
||||
>-r</DT
|
||||
><DD
|
||||
><P
|
||||
>Restore. Files are restored to the share
|
||||
from the tar file. </P
|
||||
></DD
|
||||
><DT
|
||||
>-l log level</DT
|
||||
><DD
|
||||
><P
|
||||
>Log (debug) level. Corresponds to the
|
||||
<VAR
|
||||
CLASS="PARAMETER"
|
||||
>-d</VAR
|
||||
> flag of <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbclient</SPAN
|
||||
>(1)</SPAN
|
||||
>.</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN104"
|
||||
></A
|
||||
><H2
|
||||
>ENVIRONMENT VARIABLES</H2
|
||||
><P
|
||||
>The <VAR
|
||||
CLASS="PARAMETER"
|
||||
>$TAPE</VAR
|
||||
> variable specifies the
|
||||
after each file is read. </p></dd><dt><span class="term">-r</span></dt><dd><p>Restore. Files are restored to the share
|
||||
from the tar file. </p></dd><dt><span class="term">-l log level</span></dt><dd><p>Log (debug) level. Corresponds to the
|
||||
<i><tt>-d</tt></i> flag of <a href="smbclient.1.html">smbclient(1)</a>.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>ENVIRONMENT VARIABLES</h2><p>The <i><tt>$TAPE</tt></i> variable specifies the
|
||||
default tape device to write to. May be overridden
|
||||
with the -t option. </P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN108"
|
||||
></A
|
||||
><H2
|
||||
>BUGS</H2
|
||||
><P
|
||||
>The <B
|
||||
CLASS="COMMAND"
|
||||
>smbtar</B
|
||||
> script has different
|
||||
options from ordinary tar and from smbclient's tar command. </P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN112"
|
||||
></A
|
||||
><H2
|
||||
>CAVEATS</H2
|
||||
><P
|
||||
>Sites that are more careful about security may not like
|
||||
with the -t option. </p></div><div class="refsect1" lang="en"><h2>BUGS</h2><p>The <b>smbtar</b> script has different
|
||||
options from ordinary tar and from smbclient's tar command. </p></div><div class="refsect1" lang="en"><h2>CAVEATS</h2><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. smbtar works best
|
||||
with GNU tar and may not work well with other versions. </P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN115"
|
||||
></A
|
||||
><H2
|
||||
>DIAGNOSTICS</H2
|
||||
><P
|
||||
>See the <SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>DIAGNOSTICS</I
|
||||
></SPAN
|
||||
> section for the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbclient</SPAN
|
||||
>(1)</SPAN
|
||||
> command.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN122"
|
||||
></A
|
||||
><H2
|
||||
>VERSION</H2
|
||||
><P
|
||||
>This man page is correct for version 3.0 of
|
||||
the Samba suite.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN125"
|
||||
></A
|
||||
><H2
|
||||
>SEE ALSO</H2
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbd</SPAN
|
||||
>(8)</SPAN
|
||||
>, <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbclient</SPAN
|
||||
>(1)</SPAN
|
||||
>, <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
>.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN137"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>The original Samba software and related utilities
|
||||
with GNU tar and may not work well with other versions. </p></div><div class="refsect1" lang="en"><h2>DIAGNOSTICS</h2><p>See the <span class="emphasis"><em>DIAGNOSTICS</em></span> section for the <a href="smbclient.1.html">smbclient(1)</a> command.</p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of
|
||||
the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="smbd.8.html">smbd(8)</a>, <a href="smbclient.1.html">smbclient(1)</a>, <a href="smb.conf.5.html">smb.conf(5)</a>.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.</P
|
||||
><P
|
||||
><A
|
||||
HREF="mailto:poultenr@logica.co.uk"
|
||||
TARGET="_top"
|
||||
>Ricky Poulten</A
|
||||
>
|
||||
wrote the tar extension and this man page. The <B
|
||||
CLASS="COMMAND"
|
||||
>smbtar</B
|
||||
>
|
||||
script was heavily rewritten and improved by <A
|
||||
HREF="mailto:Martin.Kraemer@mch.sni.de"
|
||||
TARGET="_top"
|
||||
>Martin Kraemer</A
|
||||
>. Many
|
||||
to the way the Linux kernel is developed.</p><p><a href="mailto:poultenr@logica.co.uk" target="_top">Ricky Poulten</a>
|
||||
wrote the tar extension and this man page. The <b>smbtar</b>
|
||||
script was heavily rewritten and improved by <a href="mailto:Martin.Kraemer@mch.sni.de" target="_top">Martin Kraemer</a>. 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 <A
|
||||
HREF="ftp://ftp.icce.rug.nl/pub/unix/"
|
||||
TARGET="_top"
|
||||
> ftp://ftp.icce.rug.nl/pub/unix/</A
|
||||
>) and updated for the Samba 2.0
|
||||
excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
|
||||
ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for
|
||||
Samba 3.0 was done by Alexander Bokovoy.</P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
|
||||
|
||||
@ -1,304 +1,74 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>smbtree</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="SMBTREE.1"
|
||||
></A
|
||||
>smbtree</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>smbtree -- A text based smb network browser
|
||||
</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbtree</B
|
||||
> [-b] [-D] [-S]</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN14"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
>This tool is part of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
> suite.</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbtree</B
|
||||
> is a smb browser program
|
||||
in text mode. It is similar to the "Network Neighborhood" found
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbtree</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbtree.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbtree — A text based smb network browser
|
||||
</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>smbtree</tt> [-b] [-D] [-S]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>smbtree</b> is a smb browser program
|
||||
in text mode. It is similar to the "Network Neighborhood" found
|
||||
on Windows computers. It prints a tree with all
|
||||
the known domains, the servers in those domains and
|
||||
the shares on the servers.
|
||||
</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN22"
|
||||
></A
|
||||
><H2
|
||||
>OPTIONS</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>-b</DT
|
||||
><DD
|
||||
><P
|
||||
>Query network nodes by sending requests
|
||||
</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-b</span></dt><dd><p>Query network nodes by sending requests
|
||||
as broadcasts instead of querying the (domain) master browser.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-D</DT
|
||||
><DD
|
||||
><P
|
||||
>Only print a list of all
|
||||
</p></dd><dt><span class="term">-D</span></dt><dd><p>Only print a list of all
|
||||
the domains known on broadcast or by the
|
||||
master browser</P
|
||||
></DD
|
||||
><DT
|
||||
>-S</DT
|
||||
><DD
|
||||
><P
|
||||
>Only print a list of
|
||||
master browser</p></dd><dt><span class="term">-S</span></dt><dd><p>Only print a list of
|
||||
all the domains and servers responding on broadcast or
|
||||
known by the master browser.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-V</DT
|
||||
><DD
|
||||
><P
|
||||
>Prints the version number for
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
>.</P
|
||||
></DD
|
||||
><DT
|
||||
>-s <configuration file></DT
|
||||
><DD
|
||||
><P
|
||||
>The file specified contains the
|
||||
</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for
|
||||
<b>smbd</b>.</p></dd><dt><span class="term">-s <configuration file></span></dt><dd><p>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 <A
|
||||
HREF="smb.conf.5.html"
|
||||
TARGET="_top"
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf(5)</TT
|
||||
></A
|
||||
> for more information.
|
||||
to provide. See <a href="smb.conf.5.html" target="_top"><tt>
|
||||
smb.conf(5)</tt></a> for more information.
|
||||
The default configuration file name is determined at
|
||||
compile time.</P
|
||||
></DD
|
||||
><DT
|
||||
>-d|--debug=debuglevel</DT
|
||||
><DD
|
||||
><P
|
||||
><VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>debuglevel</VAR
|
||||
> is an integer
|
||||
compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
|
||||
from 0 to 10. The default value if this parameter is
|
||||
not specified is zero.</P
|
||||
><P
|
||||
>The higher this value, the more detail will be
|
||||
not specified is zero.</p><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
|
||||
><P
|
||||
>Levels above 1 will generate considerable
|
||||
information about operations carried out.</p><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
|
||||
><P
|
||||
>Note that specifying this parameter here will
|
||||
override the <A
|
||||
HREF="smb.conf.5.html#loglevel"
|
||||
TARGET="_top"
|
||||
>log
|
||||
level</A
|
||||
> parameter in the <A
|
||||
HREF="smb.conf.5.html"
|
||||
TARGET="_top"
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf(5)</TT
|
||||
></A
|
||||
> file.</P
|
||||
></DD
|
||||
><DT
|
||||
>-l|--logfile=logbasename</DT
|
||||
><DD
|
||||
><P
|
||||
>File name for log/debug files. The extension
|
||||
<CODE
|
||||
CLASS="CONSTANT"
|
||||
>".client"</CODE
|
||||
> will be appended. The log file is
|
||||
never removed by the client.</P
|
||||
></DD
|
||||
><DT
|
||||
>-N</DT
|
||||
><DD
|
||||
><P
|
||||
>If specified, this parameter suppresses the normal
|
||||
data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
|
||||
override the <a href="smb.conf.5.html#loglevel" target="_top">log
|
||||
level</a> parameter in the <a href="smb.conf.5.html" target="_top">
|
||||
<tt>smb.conf(5)</tt></a> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
|
||||
<tt>".client"</tt> will be appended. The log file is
|
||||
never removed by the client.
|
||||
</p></dd><dt><span class="term">-N</span></dt><dd><p>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
|
||||
><P
|
||||
>Unless a password is specified on the command line or
|
||||
accessing a service that does not require a password. </p><p>Unless a password is specified on the command line or
|
||||
this parameter is specified, the client will request a
|
||||
password.</P
|
||||
></DD
|
||||
><DT
|
||||
>-k</DT
|
||||
><DD
|
||||
><P
|
||||
>Try to authenticate with kerberos. Only useful in
|
||||
an Active Directory environment.</P
|
||||
></DD
|
||||
><DT
|
||||
>-A|--authfile=filename</DT
|
||||
><DD
|
||||
><P
|
||||
>This option allows
|
||||
password.</p></dd><dt><span class="term">-k</span></dt><dd><p>
|
||||
Try to authenticate with kerberos. Only useful in
|
||||
an Active Directory environment.
|
||||
</p></dd><dt><span class="term">-A|--authfile=filename</span></dt><dd><p>This option allows
|
||||
you to specify a file from which to read the username and
|
||||
password used in the connection. The format of the file is</P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
>username = <value>
|
||||
password = <value>
|
||||
domain = <value></PRE
|
||||
></P
|
||||
><P
|
||||
>Make certain that the permissions on the file restrict
|
||||
access from unwanted users. </P
|
||||
></DD
|
||||
><DT
|
||||
>-U|--user=username[%password]</DT
|
||||
><DD
|
||||
><P
|
||||
>Sets the SMB username or username and password. </P
|
||||
><P
|
||||
>If %password is not specified, the user will be prompted. The
|
||||
client will first check the <VAR
|
||||
CLASS="ENVAR"
|
||||
>USER</VAR
|
||||
> environment variable, then the
|
||||
<VAR
|
||||
CLASS="ENVAR"
|
||||
>LOGNAME</VAR
|
||||
> variable and if either exists, the
|
||||
password used in the connection. The format of the file is
|
||||
</p><pre class="programlisting">
|
||||
username = <value>
|
||||
password = <value>
|
||||
domain = <value>
|
||||
</pre><p>Make certain that the permissions on the file restrict
|
||||
access from unwanted users. </p></dd><dt><span class="term">-U|--user=username[%password]</span></dt><dd><p>Sets the SMB username or username and password. </p><p>If %password is not specified, the user will be prompted. The
|
||||
client will first check the <tt>USER</tt> environment variable, then the
|
||||
<tt>LOGNAME</tt> variable and if either exists, the
|
||||
string is uppercased. If these environmental variables are not
|
||||
found, the username <CODE
|
||||
CLASS="CONSTANT"
|
||||
>GUEST</CODE
|
||||
> is used. </P
|
||||
><P
|
||||
>A third option is to use a credentials file which
|
||||
found, the username <tt>GUEST</tt> is used. </p><p>A third option is to use a credentials file which
|
||||
contains the plaintext of the username and password. This
|
||||
option is mainly provided for scripts where the admin does not
|
||||
wish to pass the credentials on the command line or via environment
|
||||
variables. If this method is used, make certain that the permissions
|
||||
on the file restrict access from unwanted users. See the
|
||||
<VAR
|
||||
CLASS="PARAMETER"
|
||||
>-A</VAR
|
||||
> for more details. </P
|
||||
><P
|
||||
>Be cautious about including passwords in scripts. Also, on
|
||||
<i><tt>-A</tt></i> for more details. </p><p>Be cautious about including passwords in scripts. Also, on
|
||||
many systems the command line of a running process may be seen
|
||||
via the <B
|
||||
CLASS="COMMAND"
|
||||
>ps</B
|
||||
> command. To be safe always allow
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>rpcclient</B
|
||||
> to prompt for a password and type
|
||||
it in directly. </P
|
||||
></DD
|
||||
><DT
|
||||
>-h|--help</DT
|
||||
><DD
|
||||
><P
|
||||
>Print a summary of command line options.</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN97"
|
||||
></A
|
||||
><H2
|
||||
>VERSION</H2
|
||||
><P
|
||||
>This man page is correct for version 3.0 of the Samba
|
||||
suite.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN100"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>The original Samba software and related utilities
|
||||
via the <b>ps</b> command. To be safe always allow
|
||||
<b>rpcclient</b> to prompt for a password and type
|
||||
it in directly. </p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
|
||||
</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the Samba
|
||||
suite.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.</P
|
||||
><P
|
||||
>The smbtree man page was written by Jelmer Vernooij. </P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
to the way the Linux kernel is developed.</p><p>The smbtree man page was written by Jelmer Vernooij. </p></div></div></body></html>
|
||||
|
||||
@ -1,140 +1,16 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>smbumount</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="SMBUMOUNT.8"
|
||||
></A
|
||||
>smbumount</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>smbumount -- smbfs umount for normal users</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>smbumount</B
|
||||
> {mount-point}</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN12"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
>With this program, normal users can unmount smb-filesystems,
|
||||
provided that it is suid root. <B
|
||||
CLASS="COMMAND"
|
||||
>smbumount</B
|
||||
> has
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>smbumount</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="smbumount.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>smbumount — smbfs umount for normal users</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>smbumount</tt> {mount-point}</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>With this program, normal users can unmount smb-filesystems,
|
||||
provided that it is suid root. <b>smbumount</b> has
|
||||
been written to give normal Linux users more control over their
|
||||
resources. It is safe to install this program suid root, because only
|
||||
the user who has mounted a filesystem is allowed to unmount it again.
|
||||
For root it is not necessary to use smbumount. The normal umount
|
||||
program works perfectly well, but it would certainly be problematic
|
||||
to make umount setuid root.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN16"
|
||||
></A
|
||||
><H2
|
||||
>OPTIONS</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>mount-point</DT
|
||||
><DD
|
||||
><P
|
||||
>The directory to unmount.</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN23"
|
||||
></A
|
||||
><H2
|
||||
>SEE ALSO</H2
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbmount</SPAN
|
||||
>(8)</SPAN
|
||||
></P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN29"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>Volker Lendecke, Andrew Tridgell, Michael H. Warfield
|
||||
and others.</P
|
||||
><P
|
||||
>The current maintainer of smbfs and the userspace
|
||||
tools <B
|
||||
CLASS="COMMAND"
|
||||
>smbmount</B
|
||||
>, <B
|
||||
CLASS="COMMAND"
|
||||
>smbumount</B
|
||||
>,
|
||||
and <B
|
||||
CLASS="COMMAND"
|
||||
>smbmnt</B
|
||||
> is <A
|
||||
HREF="mailto:urban@teststation.com"
|
||||
TARGET="_top"
|
||||
>Urban Widmark</A
|
||||
>.
|
||||
The <A
|
||||
HREF="mailto:samba@samba.org"
|
||||
TARGET="_top"
|
||||
>SAMBA Mailing list</A
|
||||
>
|
||||
to make umount setuid root.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">mount-point</span></dt><dd><p>The directory to unmount.</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="smbmount.8.html">smbmount(8)</a></p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>Volker Lendecke, Andrew Tridgell, Michael H. Warfield
|
||||
and others.</p><p>The current maintainer of smbfs and the userspace
|
||||
tools <b>smbmount</b>, <b>smbumount</b>,
|
||||
and <b>smbmnt</b> is <a href="mailto:urban@teststation.com" target="_top">Urban Widmark</a>.
|
||||
The <a href="mailto:samba@samba.org" target="_top">SAMBA Mailing list</a>
|
||||
is the preferred place to ask questions regarding these programs.
|
||||
</P
|
||||
><P
|
||||
>The conversion of this manpage for Samba 2.2 was performed
|
||||
</p><p>The conversion of this manpage for Samba 2.2 was performed
|
||||
by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0
|
||||
was done by Alexander Bokovoy.</P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
was done by Alexander Bokovoy.</p></div></div></body></html>
|
||||
|
||||
@ -1,499 +1,108 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>Samba performance issues</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
||||
REL="HOME"
|
||||
TITLE="SAMBA Project Documentation"
|
||||
HREF="samba-howto-collection.html"><LINK
|
||||
REL="UP"
|
||||
TITLE="Appendixes"
|
||||
HREF="appendixes.html"><LINK
|
||||
REL="PREVIOUS"
|
||||
TITLE="SWAT - The Samba Web Admininistration Tool"
|
||||
HREF="swat.html"><LINK
|
||||
REL="NEXT"
|
||||
TITLE="The samba checklist"
|
||||
HREF="diagnosis.html"></HEAD
|
||||
><BODY
|
||||
CLASS="CHAPTER"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><DIV
|
||||
CLASS="NAVHEADER"
|
||||
><TABLE
|
||||
SUMMARY="Header navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TH
|
||||
COLSPAN="3"
|
||||
ALIGN="center"
|
||||
>SAMBA Project Documentation</TH
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="left"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="swat.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="80%"
|
||||
ALIGN="center"
|
||||
VALIGN="bottom"
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="right"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="diagnosis.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
></TABLE
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"></DIV
|
||||
><DIV
|
||||
CLASS="CHAPTER"
|
||||
><H1
|
||||
><A
|
||||
NAME="SPEED"
|
||||
></A
|
||||
>Chapter 32. Samba performance issues</H1
|
||||
><DIV
|
||||
CLASS="TOC"
|
||||
><DL
|
||||
><DT
|
||||
><B
|
||||
>Table of Contents</B
|
||||
></DT
|
||||
><DT
|
||||
>32.1. <A
|
||||
HREF="speed.html#AEN4687"
|
||||
>Comparisons</A
|
||||
></DT
|
||||
><DT
|
||||
>32.2. <A
|
||||
HREF="speed.html#AEN4693"
|
||||
>Socket options</A
|
||||
></DT
|
||||
><DT
|
||||
>32.3. <A
|
||||
HREF="speed.html#AEN4700"
|
||||
>Read size</A
|
||||
></DT
|
||||
><DT
|
||||
>32.4. <A
|
||||
HREF="speed.html#AEN4705"
|
||||
>Max xmit</A
|
||||
></DT
|
||||
><DT
|
||||
>32.5. <A
|
||||
HREF="speed.html#AEN4710"
|
||||
>Log level</A
|
||||
></DT
|
||||
><DT
|
||||
>32.6. <A
|
||||
HREF="speed.html#AEN4713"
|
||||
>Read raw</A
|
||||
></DT
|
||||
><DT
|
||||
>32.7. <A
|
||||
HREF="speed.html#AEN4718"
|
||||
>Write raw</A
|
||||
></DT
|
||||
><DT
|
||||
>32.8. <A
|
||||
HREF="speed.html#AEN4722"
|
||||
>Slow Clients</A
|
||||
></DT
|
||||
><DT
|
||||
>32.9. <A
|
||||
HREF="speed.html#AEN4726"
|
||||
>Slow Logins</A
|
||||
></DT
|
||||
><DT
|
||||
>32.10. <A
|
||||
HREF="speed.html#AEN4729"
|
||||
>Client tuning</A
|
||||
></DT
|
||||
></DL
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN4687"
|
||||
>32.1. Comparisons</A
|
||||
></H1
|
||||
><P
|
||||
>The Samba server uses TCP to talk to the client. Thus if you are
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 35. Samba performance issues</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="Appendixes.html" title="Part V. Appendixes"><link rel="previous" href="SWAT.html" title="Chapter 34. SWAT - The Samba Web Admininistration Tool"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 35. Samba performance issues</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="SWAT.html">Prev</a> </td><th width="60%" align="center">Part V. Appendixes</th><td width="20%" align="right"> </td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="speed"></a>Chapter 35. Samba performance issues</h2></div><div><div class="author"><h3 class="author">Paul Cochrane</h3><div class="affiliation"><span class="orgname">Dundee Limb Fitting Centre<br></span><div class="address"><p><tt><<a href="mailto:paulc@dth.scot.nhs.uk">paulc@dth.scot.nhs.uk</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="speed.html#id2908657">Comparisons</a></dt><dt><a href="speed.html#id2908548">Socket options</a></dt><dt><a href="speed.html#id2909437">Read size</a></dt><dt><a href="speed.html#id2909480">Max xmit</a></dt><dt><a href="speed.html#id2909533">Log level</a></dt><dt><a href="speed.html#id2909556">Read raw</a></dt><dt><a href="speed.html#id2909613">Write raw</a></dt><dt><a href="speed.html#id2909655">Slow Logins</a></dt><dt><a href="speed.html#id2909676">Client tuning</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2908657"></a>Comparisons</h2></div></div><p>
|
||||
The Samba server uses TCP to talk to the client. Thus if you are
|
||||
trying to see if it performs well you should really compare it to
|
||||
programs that use the same protocol. The most readily available
|
||||
programs for file transfer that use TCP are ftp or another TCP based
|
||||
SMB server.</P
|
||||
><P
|
||||
>If you want to test against something like a NT or WfWg server then
|
||||
SMB server.
|
||||
</p><p>
|
||||
If you want to test against something like a NT or WfWg server then
|
||||
you will have to disable all but TCP on either the client or
|
||||
server. Otherwise you may well be using a totally different protocol
|
||||
(such as Netbeui) and comparisons may not be valid.</P
|
||||
><P
|
||||
>Generally you should find that Samba performs similarly to ftp at raw
|
||||
(such as Netbeui) and comparisons may not be valid.
|
||||
</p><p>
|
||||
Generally you should find that Samba performs similarly to ftp at raw
|
||||
transfer speed. It should perform quite a bit faster than NFS,
|
||||
although this very much depends on your system.</P
|
||||
><P
|
||||
>Several people have done comparisons between Samba and Novell, NFS or
|
||||
although this very much depends on your system.
|
||||
</p><p>
|
||||
Several people have done comparisons between Samba and Novell, NFS or
|
||||
WinNT. In some cases Samba performed the best, in others the worst. I
|
||||
suspect the biggest factor is not Samba vs some other system but the
|
||||
hardware and drivers used on the various systems. Given similar
|
||||
hardware Samba should certainly be competitive in speed with other
|
||||
systems.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN4693"
|
||||
>32.2. Socket options</A
|
||||
></H1
|
||||
><P
|
||||
>There are a number of socket options that can greatly affect the
|
||||
performance of a TCP based server like Samba.</P
|
||||
><P
|
||||
>The socket options that Samba uses are settable both on the command
|
||||
line with the -O option, or in the smb.conf file.</P
|
||||
><P
|
||||
>The "socket options" section of the smb.conf manual page describes how
|
||||
to set these and gives recommendations.</P
|
||||
><P
|
||||
>Getting the socket options right can make a big difference to your
|
||||
systems.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2908548"></a>Socket options</h2></div></div><p>
|
||||
There are a number of socket options that can greatly affect the
|
||||
performance of a TCP based server like Samba.
|
||||
</p><p>
|
||||
The socket options that Samba uses are settable both on the command
|
||||
line with the -O option, or in the smb.conf file.
|
||||
</p><p>
|
||||
The <b>socket options</b> section of the <tt>smb.conf</tt> manual page describes how
|
||||
to set these and gives recommendations.
|
||||
</p><p>
|
||||
Getting the socket options right can make a big difference to your
|
||||
performance, but getting them wrong can degrade it by just as
|
||||
much. The correct settings are very dependent on your local network.</P
|
||||
><P
|
||||
>The socket option TCP_NODELAY is the one that seems to make the
|
||||
much. The correct settings are very dependent on your local network.
|
||||
</p><p>
|
||||
The socket option TCP_NODELAY is the one that seems to make the
|
||||
biggest single difference for most networks. Many people report that
|
||||
adding "socket options = TCP_NODELAY" doubles the read performance of
|
||||
a Samba drive. The best explanation I have seen for this is that the
|
||||
Microsoft TCP/IP stack is slow in sending tcp ACKs.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN4700"
|
||||
>32.3. Read size</A
|
||||
></H1
|
||||
><P
|
||||
>The option "read size" affects the overlap of disk reads/writes with
|
||||
network reads/writes. If the amount of data being transferred in
|
||||
several of the SMB commands (currently SMBwrite, SMBwriteX and
|
||||
adding <b>socket options = TCP_NODELAY</b> doubles the read
|
||||
performance of a Samba drive. The best explanation I have seen for this is
|
||||
that the Microsoft TCP/IP stack is slow in sending tcp ACKs.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2909437"></a>Read size</h2></div></div><p>
|
||||
The option <b>read size</b> affects the overlap of disk
|
||||
reads/writes with network reads/writes. If the amount of data being
|
||||
transferred in several of the SMB commands (currently SMBwrite, SMBwriteX and
|
||||
SMBreadbraw) is larger than this value then the server begins writing
|
||||
the data before it has received the whole packet from the network, or
|
||||
in the case of SMBreadbraw, it begins writing to the network before
|
||||
all the data has been read from disk.</P
|
||||
><P
|
||||
>This overlapping works best when the speeds of disk and network access
|
||||
all the data has been read from disk.
|
||||
</p><p>
|
||||
This overlapping works best when the speeds of disk and network access
|
||||
are similar, having very little effect when the speed of one is much
|
||||
greater than the other.</P
|
||||
><P
|
||||
>The default value is 16384, but very little experimentation has been
|
||||
greater than the other.
|
||||
</p><p>
|
||||
The default value is 16384, but very little experimentation has been
|
||||
done yet to determine the optimal value, and it is likely that the best
|
||||
value will vary greatly between systems anyway. A value over 65536 is
|
||||
pointless and will cause you to allocate memory unnecessarily.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN4705"
|
||||
>32.4. Max xmit</A
|
||||
></H1
|
||||
><P
|
||||
>At startup the client and server negotiate a "maximum transmit" size,
|
||||
pointless and will cause you to allocate memory unnecessarily.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2909480"></a>Max xmit</h2></div></div><p>
|
||||
At startup the client and server negotiate a <b>maximum transmit</b> size,
|
||||
which limits the size of nearly all SMB commands. You can set the
|
||||
maximum size that Samba will negotiate using the "max xmit = " option
|
||||
in smb.conf. Note that this is the maximum size of SMB request that
|
||||
maximum size that Samba will negotiate using the <b>max xmit = </b> option
|
||||
in <tt>smb.conf</tt>. Note that this is the maximum size of SMB requests that
|
||||
Samba will accept, but not the maximum size that the *client* will accept.
|
||||
The client maximum receive size is sent to Samba by the client and Samba
|
||||
honours this limit.</P
|
||||
><P
|
||||
>It defaults to 65536 bytes (the maximum), but it is possible that some
|
||||
honours this limit.
|
||||
</p><p>
|
||||
It defaults to 65536 bytes (the maximum), but it is possible that some
|
||||
clients may perform better with a smaller transmit unit. Trying values
|
||||
of less than 2048 is likely to cause severe problems.</P
|
||||
><P
|
||||
>In most cases the default is the best option.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN4710"
|
||||
>32.5. Log level</A
|
||||
></H1
|
||||
><P
|
||||
>If you set the log level (also known as "debug level") higher than 2
|
||||
of less than 2048 is likely to cause severe problems.
|
||||
</p><p>
|
||||
In most cases the default is the best option.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2909533"></a>Log level</h2></div></div><p>
|
||||
If you set the log level (also known as <b>debug level</b>) higher than 2
|
||||
then you may suffer a large drop in performance. This is because the
|
||||
server flushes the log file after each operation, which can be very
|
||||
expensive. </P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN4713"
|
||||
>32.6. Read raw</A
|
||||
></H1
|
||||
><P
|
||||
>The "read raw" operation is designed to be an optimised, low-latency
|
||||
expensive.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2909556"></a>Read raw</h2></div></div><p>
|
||||
The <b>read raw</b> operation is designed to be an optimised, low-latency
|
||||
file read operation. A server may choose to not support it,
|
||||
however. and Samba makes support for "read raw" optional, with it
|
||||
being enabled by default.</P
|
||||
><P
|
||||
>In some cases clients don't handle "read raw" very well and actually
|
||||
however. and Samba makes support for <b>read raw</b> optional, with it
|
||||
being enabled by default.
|
||||
</p><p>
|
||||
In some cases clients don't handle <b>read raw</b> very well and actually
|
||||
get lower performance using it than they get using the conventional
|
||||
read operations. </P
|
||||
><P
|
||||
>So you might like to try "read raw = no" and see what happens on your
|
||||
read operations.
|
||||
</p><p>
|
||||
So you might like to try <b>read raw = no</b> and see what happens on your
|
||||
network. It might lower, raise or not affect your performance. Only
|
||||
testing can really tell.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN4718"
|
||||
>32.7. Write raw</A
|
||||
></H1
|
||||
><P
|
||||
>The "write raw" operation is designed to be an optimised, low-latency
|
||||
testing can really tell.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2909613"></a>Write raw</h2></div></div><p>
|
||||
The <b>write raw</b> operation is designed to be an optimised, low-latency
|
||||
file write operation. A server may choose to not support it,
|
||||
however. and Samba makes support for "write raw" optional, with it
|
||||
being enabled by default.</P
|
||||
><P
|
||||
>Some machines may find "write raw" slower than normal write, in which
|
||||
case you may wish to change this option.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN4722"
|
||||
>32.8. Slow Clients</A
|
||||
></H1
|
||||
><P
|
||||
>One person has reported that setting the protocol to COREPLUS rather
|
||||
than LANMAN2 gave a dramatic speed improvement (from 10k/s to 150k/s).</P
|
||||
><P
|
||||
>I suspect that his PC's (386sx16 based) were asking for more data than
|
||||
they could chew. I suspect a similar speed could be had by setting
|
||||
"read raw = no" and "max xmit = 2048", instead of changing the
|
||||
protocol. Lowering the "read size" might also help.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN4726"
|
||||
>32.9. Slow Logins</A
|
||||
></H1
|
||||
><P
|
||||
>Slow logins are almost always due to the password checking time. Using
|
||||
the lowest practical "password level" will improve things a lot. You
|
||||
could also enable the "UFC crypt" option in the Makefile.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN4729"
|
||||
>32.10. Client tuning</A
|
||||
></H1
|
||||
><P
|
||||
>Often a speed problem can be traced to the client. The client (for
|
||||
however. and Samba makes support for <b>write raw</b> optional, with it
|
||||
being enabled by default.
|
||||
</p><p>
|
||||
Some machines may find <b>write raw</b> slower than normal write, in which
|
||||
case you may wish to change this option.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2909655"></a>Slow Logins</h2></div></div><p>
|
||||
Slow logins are almost always due to the password checking time. Using
|
||||
the lowest practical <b>password level</b> will improve things.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2909676"></a>Client tuning</h2></div></div><p>
|
||||
Often a speed problem can be traced to the client. The client (for
|
||||
example Windows for Workgroups) can often be tuned for better TCP
|
||||
performance.</P
|
||||
><P
|
||||
>See your client docs for details. In particular, I have heard rumours
|
||||
that the WfWg options TCPWINDOWSIZE and TCPSEGMENTSIZE can have a
|
||||
large impact on performance.</P
|
||||
><P
|
||||
>Also note that some people have found that setting DefaultRcvWindow in
|
||||
the [MSTCP] section of the SYSTEM.INI file under WfWg to 3072 gives a
|
||||
big improvement. I don't know why.</P
|
||||
><P
|
||||
>My own experience wth DefaultRcvWindow is that I get much better
|
||||
performance with a large value (16384 or larger). Other people have
|
||||
reported that anything over 3072 slows things down enourmously. One
|
||||
person even reported a speed drop of a factor of 30 when he went from
|
||||
3072 to 8192. I don't know why.</P
|
||||
><P
|
||||
>It probably depends a lot on your hardware, and the type of unix box
|
||||
you have at the other end of the link.</P
|
||||
><P
|
||||
>Paul Cochrane has done some testing on client side tuning and come
|
||||
to the following conclusions:</P
|
||||
><P
|
||||
>Install the W2setup.exe file from www.microsoft.com. This is an
|
||||
update for the winsock stack and utilities which improve performance.</P
|
||||
><P
|
||||
>Configure the win95 TCPIP registry settings to give better
|
||||
perfomance. I use a program called MTUSPEED.exe which I got off the
|
||||
net. There are various other utilities of this type freely available.
|
||||
The setting which give the best performance for me are:</P
|
||||
><P
|
||||
></P
|
||||
><OL
|
||||
TYPE="1"
|
||||
><LI
|
||||
><P
|
||||
>MaxMTU Remove</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>RWIN Remove</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>MTUAutoDiscover Disable</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>MTUBlackHoleDetect Disable</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>Time To Live Enabled</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>Time To Live - HOPS 32</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>NDI Cache Size 0</P
|
||||
></LI
|
||||
></OL
|
||||
><P
|
||||
>I tried virtually all of the items mentioned in the document and
|
||||
the only one which made a difference to me was the socket options. It
|
||||
turned out I was better off without any!!!!!</P
|
||||
><P
|
||||
>In terms of overall speed of transfer, between various win95 clients
|
||||
and a DX2-66 20MB server with a crappy NE2000 compatible and old IDE
|
||||
drive (Kernel 2.0.30). The transfer rate was reasonable for 10 baseT.</P
|
||||
><P
|
||||
><PRE
|
||||
CLASS="PROGRAMLISTING"
|
||||
>The figures are: Put Get
|
||||
P166 client 3Com card: 420-440kB/s 500-520kB/s
|
||||
P100 client 3Com card: 390-410kB/s 490-510kB/s
|
||||
DX4-75 client NE2000: 370-380kB/s 330-350kB/s</PRE
|
||||
></P
|
||||
><P
|
||||
>I based these test on transfer two files a 4.5MB text file and a 15MB
|
||||
textfile. The results arn't bad considering the hardware Samba is
|
||||
running on. It's a crap machine!!!!</P
|
||||
><P
|
||||
>The updates mentioned in 1 and 2 brought up the transfer rates from
|
||||
just over 100kB/s in some clients.</P
|
||||
><P
|
||||
>A new client is a P333 connected via a 100MB/s card and hub. The
|
||||
transfer rates from this were good: 450-500kB/s on put and 600+kB/s
|
||||
on get.</P
|
||||
><P
|
||||
>Looking at standard FTP throughput, Samba is a bit slower (100kB/s
|
||||
upwards). I suppose there is more going on in the samba protocol, but
|
||||
if it could get up to the rate of FTP the perfomance would be quite
|
||||
staggering.</P
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="NAVFOOTER"
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"><TABLE
|
||||
SUMMARY="Footer navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="swat.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="samba-howto-collection.html"
|
||||
ACCESSKEY="H"
|
||||
>Home</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="diagnosis.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
>SWAT - The Samba Web Admininistration Tool</TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="appendixes.html"
|
||||
ACCESSKEY="U"
|
||||
>Up</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
>The samba checklist</TD
|
||||
></TR
|
||||
></TABLE
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
performance. Check the sections on the various clients in
|
||||
<a href="Other-Clients.html" title="Chapter 33. Samba and other CIFS clients">Samba and Other Clients</a>.
|
||||
</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="SWAT.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="Appendixes.html">Up</a></td><td width="40%" align="right"> </td></tr><tr><td width="40%" align="left" valign="top">Chapter 34. SWAT - The Samba Web Admininistration Tool </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> </td></tr></table></div></body></html>
|
||||
|
||||
@ -1,518 +1,87 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>swat</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="SWAT.8"
|
||||
></A
|
||||
>swat</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>swat -- Samba Web Administration Tool</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>swat</B
|
||||
> [-s <smb config file>] [-a]</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN13"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
>This tool is part of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
> suite.</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>swat</B
|
||||
> allows a Samba administrator to
|
||||
configure the complex <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> file via a Web browser. In addition,
|
||||
a <B
|
||||
CLASS="COMMAND"
|
||||
>swat</B
|
||||
> configuration page has help links
|
||||
to all the configurable options in the <TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf</TT
|
||||
> file allowing an
|
||||
administrator to easily look up the effects of any change. </P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>swat</B
|
||||
> is run from <B
|
||||
CLASS="COMMAND"
|
||||
>inetd</B
|
||||
> </P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN29"
|
||||
></A
|
||||
><H2
|
||||
>OPTIONS</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>-s smb configuration file</DT
|
||||
><DD
|
||||
><P
|
||||
>The default configuration file path is
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>swat</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="swat.8"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>swat — Samba Web Administration Tool</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>swat</tt> [-s <smb config file>] [-a]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>swat</b> allows a Samba administrator to
|
||||
configure the complex <a href="smb.conf.5.html">smb.conf(5)</a> file via a Web browser. In addition,
|
||||
a <b>swat</b> configuration page has help links
|
||||
to all the configurable options in the <tt>smb.conf</tt> file allowing an
|
||||
administrator to easily look up the effects of any change. </p><p><b>swat</b> is run from <b>inetd</b> </p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-s smb configuration file</span></dt><dd><p>The default configuration file path is
|
||||
determined at compile time. The file specified contains
|
||||
the configuration details required by the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbd</SPAN
|
||||
>(8)</SPAN
|
||||
> server. This is the file
|
||||
that <B
|
||||
CLASS="COMMAND"
|
||||
>swat</B
|
||||
> will modify.
|
||||
the configuration details required by the <a href="smbd.8.html">smbd(8)</a> server. This is the file
|
||||
that <b>swat</b> 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 <TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf</TT
|
||||
> for more information.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-a</DT
|
||||
><DD
|
||||
><P
|
||||
>This option disables authentication and puts
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>swat</B
|
||||
> in demo mode. In that mode anyone will be able to modify
|
||||
the <TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf</TT
|
||||
> file. </P
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>WARNING: Do NOT enable this option on a production
|
||||
server. </I
|
||||
></SPAN
|
||||
></P
|
||||
></DD
|
||||
><DT
|
||||
>-V</DT
|
||||
><DD
|
||||
><P
|
||||
>Prints the version number for
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
>.</P
|
||||
></DD
|
||||
><DT
|
||||
>-s <configuration file></DT
|
||||
><DD
|
||||
><P
|
||||
>The file specified contains the
|
||||
See <tt>smb.conf</tt> for more information.
|
||||
</p></dd><dt><span class="term">-a</span></dt><dd><p>This option disables authentication and puts
|
||||
<b>swat</b> in demo mode. In that mode anyone will be able to modify
|
||||
the <tt>smb.conf</tt> file. </p><p><span class="emphasis"><em>WARNING: Do NOT enable this option on a production
|
||||
server. </em></span></p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for
|
||||
<b>smbd</b>.</p></dd><dt><span class="term">-s <configuration file></span></dt><dd><p>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 <A
|
||||
HREF="smb.conf.5.html"
|
||||
TARGET="_top"
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf(5)</TT
|
||||
></A
|
||||
> for more information.
|
||||
to provide. See <a href="smb.conf.5.html" target="_top"><tt>
|
||||
smb.conf(5)</tt></a> for more information.
|
||||
The default configuration file name is determined at
|
||||
compile time.</P
|
||||
></DD
|
||||
><DT
|
||||
>-d|--debug=debuglevel</DT
|
||||
><DD
|
||||
><P
|
||||
><VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>debuglevel</VAR
|
||||
> is an integer
|
||||
compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
|
||||
from 0 to 10. The default value if this parameter is
|
||||
not specified is zero.</P
|
||||
><P
|
||||
>The higher this value, the more detail will be
|
||||
not specified is zero.</p><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
|
||||
><P
|
||||
>Levels above 1 will generate considerable
|
||||
information about operations carried out.</p><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
|
||||
><P
|
||||
>Note that specifying this parameter here will
|
||||
override the <A
|
||||
HREF="smb.conf.5.html#loglevel"
|
||||
TARGET="_top"
|
||||
>log
|
||||
level</A
|
||||
> parameter in the <A
|
||||
HREF="smb.conf.5.html"
|
||||
TARGET="_top"
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf(5)</TT
|
||||
></A
|
||||
> file.</P
|
||||
></DD
|
||||
><DT
|
||||
>-l|--logfile=logbasename</DT
|
||||
><DD
|
||||
><P
|
||||
>File name for log/debug files. The extension
|
||||
<CODE
|
||||
CLASS="CONSTANT"
|
||||
>".client"</CODE
|
||||
> will be appended. The log file is
|
||||
never removed by the client.</P
|
||||
></DD
|
||||
><DT
|
||||
>-h|--help</DT
|
||||
><DD
|
||||
><P
|
||||
>Print a summary of command line options.</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN80"
|
||||
></A
|
||||
><H2
|
||||
>INSTALLATION</H2
|
||||
><P
|
||||
>Swat is included as binary package with most distributions. The
|
||||
data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
|
||||
override the <a href="smb.conf.5.html#loglevel" target="_top">log
|
||||
level</a> parameter in the <a href="smb.conf.5.html" target="_top">
|
||||
<tt>smb.conf(5)</tt></a> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
|
||||
<tt>".client"</tt> will be appended. The log file is
|
||||
never removed by the client.
|
||||
</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
|
||||
</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>INSTALLATION</h2><p>Swat is included as binary package with most distributions. The
|
||||
package manager in this case takes care of the installation and
|
||||
configuration. This section is only for those who have compiled
|
||||
swat from scratch.
|
||||
</P
|
||||
><P
|
||||
>After you compile SWAT you need to run <B
|
||||
CLASS="COMMAND"
|
||||
>make install
|
||||
</B
|
||||
> to install the <B
|
||||
CLASS="COMMAND"
|
||||
>swat</B
|
||||
> binary
|
||||
</p><p>After you compile SWAT you need to run <b>make install
|
||||
</b> to install the <b>swat</b> binary
|
||||
and the various help files and images. A default install would put
|
||||
these in: </P
|
||||
><P
|
||||
></P
|
||||
><UL
|
||||
><LI
|
||||
><P
|
||||
>/usr/local/samba/bin/swat</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>/usr/local/samba/swat/images/*</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
>/usr/local/samba/swat/help/*</P
|
||||
></LI
|
||||
></UL
|
||||
><DIV
|
||||
CLASS="REFSECT2"
|
||||
><A
|
||||
NAME="AEN93"
|
||||
></A
|
||||
><H3
|
||||
>Inetd Installation</H3
|
||||
><P
|
||||
>You need to edit your <TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/inetd.conf
|
||||
</TT
|
||||
> and <TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/services</TT
|
||||
>
|
||||
to enable SWAT to be launched via <B
|
||||
CLASS="COMMAND"
|
||||
>inetd</B
|
||||
>.</P
|
||||
><P
|
||||
>In <TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/services</TT
|
||||
> you need to
|
||||
add a line like this: </P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>swat 901/tcp</B
|
||||
></P
|
||||
><P
|
||||
>Note for NIS/YP and LDAP users - you may need to rebuild the
|
||||
NIS service maps rather than alter your local <TT
|
||||
CLASS="FILENAME"
|
||||
> /etc/services</TT
|
||||
> file. </P
|
||||
><P
|
||||
>the choice of port number isn't really important
|
||||
these in: </p><div class="itemizedlist"><ul type="disc"><li><p>/usr/local/samba/bin/swat</p></li><li><p>/usr/local/samba/swat/images/*</p></li><li><p>/usr/local/samba/swat/help/*</p></li></ul></div><div class="refsect2" lang="en"><h3>Inetd Installation</h3><p>You need to edit your <tt>/etc/inetd.conf
|
||||
</tt> and <tt>/etc/services</tt>
|
||||
to enable SWAT to be launched via <b>inetd</b>.</p><p>In <tt>/etc/services</tt> you need to
|
||||
add a line like this: </p><p><b>swat 901/tcp</b></p><p>Note for NIS/YP and LDAP users - you may need to rebuild the
|
||||
NIS service maps rather than alter your local <tt>
|
||||
/etc/services</tt> file. </p><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
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>inetd</B
|
||||
> daemon). </P
|
||||
><P
|
||||
>In <TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/inetd.conf</TT
|
||||
> you should
|
||||
add a line like this: </P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>swat stream tcp nowait.400 root
|
||||
/usr/local/samba/bin/swat swat</B
|
||||
></P
|
||||
><P
|
||||
>One you have edited <TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/services</TT
|
||||
>
|
||||
and <TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/inetd.conf</TT
|
||||
> you need to send a
|
||||
HUP signal to inetd. To do this use <B
|
||||
CLASS="COMMAND"
|
||||
>kill -1 PID
|
||||
</B
|
||||
> where PID is the process ID of the inetd daemon. </P
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN115"
|
||||
></A
|
||||
><H2
|
||||
>LAUNCHING</H2
|
||||
><P
|
||||
>To launch SWAT just run your favorite web browser and
|
||||
point it at "http://localhost:901/".</P
|
||||
><P
|
||||
>Note that you can attach to SWAT from any IP connected
|
||||
<b>inetd</b> daemon). </p><p>In <tt>/etc/inetd.conf</tt> you should
|
||||
add a line like this: </p><p><b>swat stream tcp nowait.400 root
|
||||
/usr/local/samba/bin/swat swat</b></p><p>One you have edited <tt>/etc/services</tt>
|
||||
and <tt>/etc/inetd.conf</tt> you need to send a
|
||||
HUP signal to inetd. To do this use <b>kill -1 PID
|
||||
</b> where PID is the process ID of the inetd daemon. </p></div></div><div class="refsect1" lang="en"><h2>LAUNCHING</h2><p>To launch SWAT just run your favorite web browser and
|
||||
point it at "http://localhost:901/".</p><p>Note that you can attach to SWAT 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. </P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN119"
|
||||
></A
|
||||
><H2
|
||||
>FILES</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/inetd.conf</TT
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>This file must contain suitable startup
|
||||
information for the meta-daemon.</P
|
||||
></DD
|
||||
><DT
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/services</TT
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>This file must contain a mapping of service name
|
||||
in the clear over the wire. </p></div><div class="refsect1" lang="en"><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><tt>/etc/inetd.conf</tt></span></dt><dd><p>This file must contain suitable startup
|
||||
information for the meta-daemon.</p></dd><dt><span class="term"><tt>/etc/services</tt></span></dt><dd><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
|
||||
></DD
|
||||
><DT
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>/usr/local/samba/lib/smb.conf</TT
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>This is the default location of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> server configuration file that swat edits. Other
|
||||
common places that systems install this file are <TT
|
||||
CLASS="FILENAME"
|
||||
> /usr/samba/lib/smb.conf</TT
|
||||
> and <TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/smb.conf
|
||||
</TT
|
||||
>. This file describes all the services the server
|
||||
is to make available to clients. </P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN142"
|
||||
></A
|
||||
><H2
|
||||
>WARNINGS</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>swat</B
|
||||
> will rewrite your <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> file. It will rearrange the entries and delete all
|
||||
comments, <VAR
|
||||
CLASS="PARAMETER"
|
||||
>include=</VAR
|
||||
> and <VAR
|
||||
CLASS="PARAMETER"
|
||||
>copy=
|
||||
</VAR
|
||||
> options. If you have a carefully crafted <TT
|
||||
CLASS="FILENAME"
|
||||
> smb.conf</TT
|
||||
> then back it up or don't use swat! </P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN152"
|
||||
></A
|
||||
><H2
|
||||
>VERSION</H2
|
||||
><P
|
||||
>This man page is correct for version 3.0 of the Samba suite.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN155"
|
||||
></A
|
||||
><H2
|
||||
>SEE ALSO</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>inetd(5)</B
|
||||
>, <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbd</SPAN
|
||||
>(8)</SPAN
|
||||
>, <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
></P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN165"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>The original Samba software and related utilities
|
||||
(e.g., tcp). </p></dd><dt><span class="term"><tt>/usr/local/samba/lib/smb.conf</tt></span></dt><dd><p>This is the default location of the <a href="smb.conf.5.html">smb.conf(5)</a> server configuration file that swat edits. Other
|
||||
common places that systems install this file are <tt>
|
||||
/usr/samba/lib/smb.conf</tt> and <tt>/etc/smb.conf
|
||||
</tt>. This file describes all the services the server
|
||||
is to make available to clients. </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>WARNINGS</h2><p><b>swat</b> will rewrite your <a href="smb.conf.5.html">smb.conf(5)</a> file. It will rearrange the entries and delete all
|
||||
comments, <i><tt>include=</tt></i> and <i><tt>copy=
|
||||
</tt></i> options. If you have a carefully crafted <tt>
|
||||
smb.conf</tt> then back it up or don't use swat! </p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><b>inetd(5)</b>, <a href="smbd.8.html">smbd(8)</a>, <a href="smb.conf.5.html">smb.conf(5)</a></p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.</P
|
||||
><P
|
||||
>The original Samba man pages were written by Karl Auer.
|
||||
to the way the Linux kernel is developed.</p><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/"
|
||||
TARGET="_top"
|
||||
> ftp://ftp.icce.rug.nl/pub/unix/</A
|
||||
>) and updated for the Samba 2.0
|
||||
excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
|
||||
ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for
|
||||
Samba 3.0 was done by Alexander Bokovoy.</P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
|
||||
|
||||
@ -1,340 +1,51 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>testparm</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="TESTPARM.1"
|
||||
></A
|
||||
>testparm</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>testparm -- check an smb.conf configuration file for
|
||||
internal correctness</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>testparm</B
|
||||
> [-s] [-h] [-v] [-L <servername>] [-t <encoding>] {config filename} [hostname hostIP]</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN18"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
>This tool is part of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
> suite.</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>testparm</B
|
||||
> is a very simple test program
|
||||
to check an <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbd</SPAN
|
||||
>(8)</SPAN
|
||||
> configuration file for
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>testparm</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="testparm.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>testparm — check an smb.conf configuration file for
|
||||
internal correctness</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>testparm</tt> [-s] [-h] [-v] [-L <servername>] [-t <encoding>] {config filename} [hostname hostIP]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>testparm</b> is a very simple test program
|
||||
to check an <a href="smbd.8.html">smbd(8)</a> configuration file for
|
||||
internal correctness. If this program reports no problems, you
|
||||
can use the configuration file with confidence that <B
|
||||
CLASS="COMMAND"
|
||||
>smbd
|
||||
</B
|
||||
> will successfully load the configuration file.</P
|
||||
><P
|
||||
>Note that this is <SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>NOT</I
|
||||
></SPAN
|
||||
> a guarantee that
|
||||
can use the configuration file with confidence that <b>smbd
|
||||
</b> will successfully load the configuration file.</p><p>Note that this is <span class="emphasis"><em>NOT</em></span> a guarantee that
|
||||
the services specified in the configuration file will be
|
||||
available or will operate as expected. </P
|
||||
><P
|
||||
>If the optional host name and host IP address are
|
||||
available or will operate as expected. </p><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
|
||||
><P
|
||||
>If <B
|
||||
CLASS="COMMAND"
|
||||
>testparm</B
|
||||
> finds an error in the <TT
|
||||
CLASS="FILENAME"
|
||||
> smb.conf</TT
|
||||
> file it returns an exit code of 1 to the calling
|
||||
has access to each service. </p><p>If <b>testparm</b> finds an error in the <tt>
|
||||
smb.conf</tt> 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 <B
|
||||
CLASS="COMMAND"
|
||||
>testparm</B
|
||||
>.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN37"
|
||||
></A
|
||||
><H2
|
||||
>OPTIONS</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>-s</DT
|
||||
><DD
|
||||
><P
|
||||
>Without this option, <B
|
||||
CLASS="COMMAND"
|
||||
>testparm</B
|
||||
>
|
||||
to test the output from <b>testparm</b>.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-s</span></dt><dd><p>Without this option, <b>testparm</b>
|
||||
will prompt for a carriage return after printing the service
|
||||
names and before dumping the service definitions.</P
|
||||
></DD
|
||||
><DT
|
||||
>-h|--help</DT
|
||||
><DD
|
||||
><P
|
||||
>Print a summary of command line options.</P
|
||||
></DD
|
||||
><DT
|
||||
>-V</DT
|
||||
><DD
|
||||
><P
|
||||
>Prints the version number for
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
>.</P
|
||||
></DD
|
||||
><DT
|
||||
>-L servername</DT
|
||||
><DD
|
||||
><P
|
||||
>Sets the value of the %L macro to <VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>servername</VAR
|
||||
>.
|
||||
names and before dumping the service definitions.</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
|
||||
</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for
|
||||
<b>smbd</b>.</p></dd><dt><span class="term">-L servername</span></dt><dd><p>Sets the value of the %L macro to <i><tt>servername</tt></i>.
|
||||
This is useful for testing include files specified with the
|
||||
%L macro. </P
|
||||
></DD
|
||||
><DT
|
||||
>-v</DT
|
||||
><DD
|
||||
><P
|
||||
>If this option is specified, testparm
|
||||
will also output all options that were not used in <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> and are thus set to their defaults.</P
|
||||
></DD
|
||||
><DT
|
||||
>-t encoding</DT
|
||||
><DD
|
||||
><P
|
||||
> Output data in specified encoding.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>configfilename</DT
|
||||
><DD
|
||||
><P
|
||||
>This is the name of the configuration file
|
||||
%L macro. </p></dd><dt><span class="term">-v</span></dt><dd><p>If this option is specified, testparm
|
||||
will also output all options that were not used in <a href="smb.conf.5.html">smb.conf(5)</a> and are thus set to their defaults.</p></dd><dt><span class="term">-t encoding</span></dt><dd><p>
|
||||
Output data in specified encoding.
|
||||
</p></dd><dt><span class="term">configfilename</span></dt><dd><p>This is the name of the configuration file
|
||||
to check. If this parameter is not present then the
|
||||
default <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> file will be checked.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>hostname</DT
|
||||
><DD
|
||||
><P
|
||||
>If this parameter and the following are
|
||||
specified, then <B
|
||||
CLASS="COMMAND"
|
||||
>testparm</B
|
||||
> will examine the <VAR
|
||||
CLASS="PARAMETER"
|
||||
>hosts
|
||||
allow</VAR
|
||||
> and <VAR
|
||||
CLASS="PARAMETER"
|
||||
>hosts deny</VAR
|
||||
>
|
||||
parameters in the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> file to
|
||||
default <a href="smb.conf.5.html">smb.conf(5)</a> file will be checked.
|
||||
</p></dd><dt><span class="term">hostname</span></dt><dd><p>If this parameter and the following are
|
||||
specified, then <b>testparm</b> will examine the <i><tt>hosts
|
||||
allow</tt></i> and <i><tt>hosts deny</tt></i>
|
||||
parameters in the <a href="smb.conf.5.html">smb.conf(5)</a> file to
|
||||
determine if the hostname with this IP address would be
|
||||
allowed access to the <B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
> server. If
|
||||
allowed access to the <b>smbd</b> server. If
|
||||
this parameter is supplied, the hostIP parameter must also
|
||||
be supplied.</P
|
||||
></DD
|
||||
><DT
|
||||
>hostIP</DT
|
||||
><DD
|
||||
><P
|
||||
>This is the IP address of the host specified
|
||||
be supplied.</p></dd><dt><span class="term">hostIP</span></dt><dd><p>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
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN92"
|
||||
></A
|
||||
><H2
|
||||
>FILES</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>This is usually the name of the configuration
|
||||
file used by <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbd</SPAN
|
||||
>(8)</SPAN
|
||||
>.
|
||||
</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN105"
|
||||
></A
|
||||
><H2
|
||||
>DIAGNOSTICS</H2
|
||||
><P
|
||||
>The program will issue a message saying whether the
|
||||
if the hostname parameter is supplied. </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><a href="smb.conf.5.html">smb.conf(5)</a></span></dt><dd><p>This is usually the name of the configuration
|
||||
file used by <a href="smbd.8.html">smbd(8)</a>.
|
||||
</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>DIAGNOSTICS</h2><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
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN108"
|
||||
></A
|
||||
><H2
|
||||
>VERSION</H2
|
||||
><P
|
||||
>This man page is correct for version 3.0 of
|
||||
the Samba suite.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN111"
|
||||
></A
|
||||
><H2
|
||||
>SEE ALSO</H2
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
>, <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbd</SPAN
|
||||
>(8)</SPAN
|
||||
></P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN120"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>The original Samba software and related utilities
|
||||
to stdout. </p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of
|
||||
the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="smb.conf.5.html">smb.conf(5)</a>, <a href="smbd.8.html">smbd(8)</a></p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.</P
|
||||
><P
|
||||
>The original Samba man pages were written by Karl Auer.
|
||||
to the way the Linux kernel is developed.</p><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/"
|
||||
TARGET="_top"
|
||||
> ftp://ftp.icce.rug.nl/pub/unix/</A
|
||||
>) and updated for the Samba 2.0
|
||||
excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
|
||||
ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2
|
||||
for Samba 3.0 was done by Alexander Bokovoy.</P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
|
||||
|
||||
@ -1,252 +1,38 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>testprns</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="TESTPRNS.1"
|
||||
></A
|
||||
>testprns</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>testprns -- check printer name for validity with smbd</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>testprns</B
|
||||
> {printername} [printcapname]</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN13"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
>This tool is part of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
> suite.</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>testprns</B
|
||||
> is a very simple test program
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>testprns</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="testprns.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>testprns — check printer name for validity with smbd</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>testprns</tt> {printername} [printcapname]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>testprns</b> is a very simple test program
|
||||
to determine whether a given printer name is valid for use in
|
||||
a service to be provided by <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbd</SPAN
|
||||
>(8)</SPAN
|
||||
>.</P
|
||||
><P
|
||||
>"Valid" in this context means "can be found in the
|
||||
printcap specified". This program is very stupid - so stupid in
|
||||
a service to be provided by <a href="smbd.8.html">smbd(8)</a>.</p><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
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN25"
|
||||
></A
|
||||
><H2
|
||||
>OPTIONS</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>printername</DT
|
||||
><DD
|
||||
><P
|
||||
>The printer name to validate.</P
|
||||
><P
|
||||
>Printer names are taken from the first field in each
|
||||
to use. </p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">printername</span></dt><dd><p>The printer name to validate.</p><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.
|
||||
of aliases separated by vertical bars ("|") are recognized.
|
||||
Note that no validation or checking of the printcap syntax is
|
||||
done beyond that required to extract the printer name. It may
|
||||
be that the print spooling system is more forgiving or less
|
||||
forgiving than <B
|
||||
CLASS="COMMAND"
|
||||
>testprns</B
|
||||
>. However, if
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>testprns</B
|
||||
> finds the printer then <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbd</SPAN
|
||||
>(8)</SPAN
|
||||
> should do so as well. </P
|
||||
></DD
|
||||
><DT
|
||||
>printcapname</DT
|
||||
><DD
|
||||
><P
|
||||
>This is the name of the printcap file within
|
||||
which to search for the given printer name. </P
|
||||
><P
|
||||
>If no printcap name is specified <B
|
||||
CLASS="COMMAND"
|
||||
>testprns
|
||||
</B
|
||||
> will attempt to scan the printcap file name
|
||||
specified at compile time. </P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN44"
|
||||
></A
|
||||
><H2
|
||||
>FILES</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>/etc/printcap</TT
|
||||
></DT
|
||||
><DD
|
||||
><P
|
||||
>This is usually the default printcap
|
||||
file to scan. See <TT
|
||||
CLASS="FILENAME"
|
||||
>printcap (5)</TT
|
||||
>.
|
||||
</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN53"
|
||||
></A
|
||||
><H2
|
||||
>DIAGNOSTICS</H2
|
||||
><P
|
||||
>If a printer is found to be valid, the message
|
||||
"Printer name <printername> is valid" will be
|
||||
displayed. </P
|
||||
><P
|
||||
>If a printer is found to be invalid, the message
|
||||
"Printer name <printername> is not valid" will be
|
||||
displayed. </P
|
||||
><P
|
||||
>All messages that would normally be logged during
|
||||
forgiving than <b>testprns</b>. However, if
|
||||
<b>testprns</b> finds the printer then <a href="smbd.8.html">smbd(8)</a> should do so as well. </p></dd><dt><span class="term">printcapname</span></dt><dd><p>This is the name of the printcap file within
|
||||
which to search for the given printer name. </p><p>If no printcap name is specified <b>testprns
|
||||
</b> will attempt to scan the printcap file name
|
||||
specified at compile time. </p></dd></dl></div></div><div class="refsect1" lang="en"><h2>FILES</h2><div class="variablelist"><dl><dt><span class="term"><tt>/etc/printcap</tt></span></dt><dd><p>This is usually the default printcap
|
||||
file to scan. See <tt>printcap (5)</tt>.
|
||||
</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>DIAGNOSTICS</h2><p>If a printer is found to be valid, the message
|
||||
"Printer name <printername> is valid" will be
|
||||
displayed. </p><p>If a printer is found to be invalid, the message
|
||||
"Printer name <printername> is not valid" will be
|
||||
displayed. </p><p>All messages that would normally be logged during
|
||||
operation of the Samba daemons are logged by this program to the
|
||||
file <TT
|
||||
CLASS="FILENAME"
|
||||
>test.log</TT
|
||||
> in the current directory. The
|
||||
file <tt>test.log</tt> 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
|
||||
><P
|
||||
>Other messages are self-explanatory. </P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN60"
|
||||
></A
|
||||
><H2
|
||||
>VERSION</H2
|
||||
><P
|
||||
>This man page is correct for version 3.0 of
|
||||
the Samba suite.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN63"
|
||||
></A
|
||||
><H2
|
||||
>SEE ALSO</H2
|
||||
><P
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>printcap(5)</TT
|
||||
>,
|
||||
<SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbd</SPAN
|
||||
>(8)</SPAN
|
||||
>, <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smbclient</SPAN
|
||||
>(1)</SPAN
|
||||
></P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN73"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>The original Samba software and related utilities
|
||||
for errors and warnings. </p><p>Other messages are self-explanatory. </p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of
|
||||
the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><tt>printcap(5)</tt>,
|
||||
<a href="smbd.8.html">smbd(8)</a>, <a href="smbclient.1.html">smbclient(1)</a></p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.</P
|
||||
><P
|
||||
>The original Samba man pages were written by Karl Auer.
|
||||
to the way the Linux kernel is developed.</p><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/"
|
||||
TARGET="_top"
|
||||
> ftp://ftp.icce.rug.nl/pub/unix/</A
|
||||
>) and updated for the Samba 2.0
|
||||
excellent piece of Open Source software, available at <a href="ftp://ftp.icce.rug.nl/pub/unix/" target="_top">
|
||||
ftp://ftp.icce.rug.nl/pub/unix/</a>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2
|
||||
for Samba 3.0 was done by Alexander Bokovoy.</P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
for Samba 3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
|
||||
|
||||
@ -1,151 +1,16 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>Type of installation</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
||||
REL="HOME"
|
||||
TITLE="SAMBA Project Documentation"
|
||||
HREF="samba-howto-collection.html"><LINK
|
||||
REL="PREVIOUS"
|
||||
TITLE="User information database"
|
||||
HREF="passdb.html"><LINK
|
||||
REL="NEXT"
|
||||
TITLE="Nomenclature of Server Types"
|
||||
HREF="servertype.html"></HEAD
|
||||
><BODY
|
||||
CLASS="PART"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><DIV
|
||||
CLASS="NAVHEADER"
|
||||
><TABLE
|
||||
SUMMARY="Header navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TH
|
||||
COLSPAN="3"
|
||||
ALIGN="center"
|
||||
>SAMBA Project Documentation</TH
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="left"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="passdb.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="80%"
|
||||
ALIGN="center"
|
||||
VALIGN="bottom"
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="right"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="servertype.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
></TABLE
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"></DIV
|
||||
><DIV
|
||||
CLASS="PART"
|
||||
><A
|
||||
NAME="TYPE"
|
||||
></A
|
||||
><DIV
|
||||
CLASS="TITLEPAGE"
|
||||
><H1
|
||||
CLASS="TITLE"
|
||||
>II. Type of installation</H1
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="PARTINTRO"
|
||||
><A
|
||||
NAME="AEN816"
|
||||
></A
|
||||
><H1
|
||||
>Introduction</H1
|
||||
><P
|
||||
>Samba can operate in various SMB networks. This part contains information on configuring samba
|
||||
for various environments.</P
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="NAVFOOTER"
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"><TABLE
|
||||
SUMMARY="Footer navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="passdb.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="samba-howto-collection.html"
|
||||
ACCESSKEY="H"
|
||||
>Home</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="servertype.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
>User information database</TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
> </TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
>Nomenclature of Server Types</TD
|
||||
></TR
|
||||
></TABLE
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Part II. Server Configuration Basics</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="index.html" title="SAMBA Project Documentation"><link rel="previous" href="install.html" title="Chapter 2. How to Install and Test SAMBA"><link rel="next" href="ServerType.html" title="Chapter 3. Nomenclature of Server Types"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Part II. Server Configuration Basics</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="install.html">Prev</a> </td><th width="60%" align="center"> </th><td width="20%" align="right"> <a accesskey="n" href="ServerType.html">Next</a></td></tr></table><hr></div><div class="part" lang="en"><div class="titlepage"><div><h1 class="title"><a name="type"></a>Server Configuration Basics</h1></div></div><div class="partintro" lang="en"><div><div><h1 class="title"><a name="id2812280"></a>First Steps in Server Configuration</h1></div></div><p>
|
||||
Samba can operate in various modes within SMB networks. This HOWTO section contains information on
|
||||
configuring samba to function as the type of server your network requires. Please read this
|
||||
section carefully.
|
||||
</p><div class="toc"><p><b>Table of Contents</b></p><dl><dt>3. <a href="ServerType.html">Nomenclature of Server Types</a></dt><dd><dl><dt><a href="ServerType.html#id2810455">Stand Alone Server</a></dt><dt><a href="ServerType.html#id2810516">Domain Member Server</a></dt><dt><a href="ServerType.html#id2810556">Domain Controller</a></dt><dd><dl><dt><a href="ServerType.html#id2810572">Domain Controller Types</a></dt></dl></dd></dl></dd><dt>4. <a href="securitylevels.html">Samba as Stand-Alone Server</a></dt><dd><dl><dt><a href="securitylevels.html#id2807692">User and Share security level</a></dt><dd><dl><dt><a href="securitylevels.html#id2807727">User Level Security</a></dt><dt><a href="securitylevels.html#id2810322">Share Level Security</a></dt><dt><a href="securitylevels.html#id2812328">Server Level Security</a></dt><dt><a href="securitylevels.html#id2876991">Domain Level Security</a></dt><dt><a href="securitylevels.html#id2877129">ADS Level Security</a></dt></dl></dd></dl></dd><dt>5. <a href="samba-pdc.html">
|
||||
Samba as an NT4 or Win2k Primary Domain Controller
|
||||
</a></dt><dd><dl><dt><a href="samba-pdc.html#id2807495">Prerequisite Reading</a></dt><dt><a href="samba-pdc.html#id2807518">
|
||||
Background
|
||||
</a></dt><dt><a href="samba-pdc.html#id2877458">Configuring the Samba Domain Controller</a></dt><dt><a href="samba-pdc.html#id2877759">Creating Machine Trust Accounts and Joining Clients to the Domain</a></dt><dd><dl><dt><a href="samba-pdc.html#id2878028">Manual Creation of Machine Trust Accounts</a></dt><dt><a href="samba-pdc.html#id2878262">"On-the-Fly" Creation of Machine Trust Accounts</a></dt><dt><a href="samba-pdc.html#id2878318">Joining the Client to the Domain</a></dt></dl></dd><dt><a href="samba-pdc.html#id2878425">Common Problems and Errors</a></dt><dd><dl><dt><a href="samba-pdc.html#id2878432">I cannot include a '$' in a machine name</a></dt><dt><a href="samba-pdc.html#id2878470">I get told "You already have a connection to the Domain...."
|
||||
or "Cannot join domain, the credentials supplied conflict with an
|
||||
existing set.." when creating a machine trust account.</a></dt><dt><a href="samba-pdc.html#id2878517">The system can not log you on (C000019B)....</a></dt><dt><a href="samba-pdc.html#id2878568">The machine trust account for this computer either does not
|
||||
exist or is not accessible.</a></dt><dt><a href="samba-pdc.html#id2878617">When I attempt to login to a Samba Domain from a NT4/W2K workstation,
|
||||
I get a message about my account being disabled.</a></dt></dl></dd><dt><a href="samba-pdc.html#id2878642">Domain Control for Windows 9x/ME</a></dt><dd><dl><dt><a href="samba-pdc.html#id2878805">Configuration Instructions: Network Logons</a></dt></dl></dd></dl></dd><dt>6. <a href="samba-bdc.html">
|
||||
Samba Backup Domain Controller to Samba Domain Control
|
||||
</a></dt><dd><dl><dt><a href="samba-bdc.html#id2807541">Prerequisite Reading</a></dt><dt><a href="samba-bdc.html#id2877190">Background</a></dt><dt><a href="samba-bdc.html#id2879061">What qualifies a Domain Controller on the network?</a></dt><dd><dl><dt><a href="samba-bdc.html#id2879083">How does a Workstation find its domain controller?</a></dt><dt><a href="samba-bdc.html#id2879107">When is the PDC needed?</a></dt></dl></dd><dt><a href="samba-bdc.html#id2879127">Can Samba be a Backup Domain Controller to an NT PDC?</a></dt><dt><a href="samba-bdc.html#id2879160">How do I set up a Samba BDC?</a></dt><dd><dl><dt><a href="samba-bdc.html#id2879257">How do I replicate the smbpasswd file?</a></dt><dt><a href="samba-bdc.html#id2879286">Can I do this all with LDAP?</a></dt></dl></dd></dl></dd><dt>7. <a href="ADS.html">Samba as a ADS domain member</a></dt><dd><dl><dt><a href="ADS.html#id2878917">Setup your smb.conf</a></dt><dt><a href="ADS.html#id2879467">Setup your /etc/krb5.conf</a></dt><dt><a href="ADS.html#ads-create-machine-account">Create the computer account</a></dt><dd><dl><dt><a href="ADS.html#id2879661">Possible errors</a></dt></dl></dd><dt><a href="ADS.html#ads-test-server">Test your server setup</a></dt><dt><a href="ADS.html#ads-test-smbclient">Testing with smbclient</a></dt><dt><a href="ADS.html#id2879814">Notes</a></dt></dl></dd><dt>8. <a href="domain-member.html">Samba as a NT4 or Win2k domain member</a></dt><dd><dl><dt><a href="domain-member.html#id2879309">Joining an NT Domain with Samba 3.0</a></dt><dt><a href="domain-member.html#id2880214">Why is this better than security = server?</a></dt></dl></dd></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="install.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="index.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="ServerType.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 2. How to Install and Test SAMBA </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 3. Nomenclature of Server Types</td></tr></table></div></body></html>
|
||||
|
||||
@ -1,370 +1,60 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>Unicode/Charsets</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
|
||||
REL="HOME"
|
||||
TITLE="SAMBA Project Documentation"
|
||||
HREF="samba-howto-collection.html"><LINK
|
||||
REL="UP"
|
||||
TITLE="Advanced Configuration"
|
||||
HREF="optional.html"><LINK
|
||||
REL="PREVIOUS"
|
||||
TITLE="Securing Samba"
|
||||
HREF="securing-samba.html"><LINK
|
||||
REL="NEXT"
|
||||
TITLE="Appendixes"
|
||||
HREF="appendixes.html"></HEAD
|
||||
><BODY
|
||||
CLASS="CHAPTER"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><DIV
|
||||
CLASS="NAVHEADER"
|
||||
><TABLE
|
||||
SUMMARY="Header navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TH
|
||||
COLSPAN="3"
|
||||
ALIGN="center"
|
||||
>SAMBA Project Documentation</TH
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="left"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="securing-samba.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="80%"
|
||||
ALIGN="center"
|
||||
VALIGN="bottom"
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="10%"
|
||||
ALIGN="right"
|
||||
VALIGN="bottom"
|
||||
><A
|
||||
HREF="appendixes.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
></TABLE
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"></DIV
|
||||
><DIV
|
||||
CLASS="CHAPTER"
|
||||
><H1
|
||||
><A
|
||||
NAME="UNICODE"
|
||||
></A
|
||||
>Chapter 26. Unicode/Charsets</H1
|
||||
><DIV
|
||||
CLASS="TOC"
|
||||
><DL
|
||||
><DT
|
||||
><B
|
||||
>Table of Contents</B
|
||||
></DT
|
||||
><DT
|
||||
>26.1. <A
|
||||
HREF="unicode.html#AEN4132"
|
||||
>What are charsets and unicode?</A
|
||||
></DT
|
||||
><DT
|
||||
>26.2. <A
|
||||
HREF="unicode.html#AEN4141"
|
||||
>Samba and charsets</A
|
||||
></DT
|
||||
><DT
|
||||
>26.3. <A
|
||||
HREF="unicode.html#AEN4160"
|
||||
>Conversion from old names</A
|
||||
></DT
|
||||
><DT
|
||||
>26.4. <A
|
||||
HREF="unicode.html#AEN4168"
|
||||
>Japanese charsets</A
|
||||
></DT
|
||||
></DL
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN4132"
|
||||
>26.1. What are charsets and unicode?</A
|
||||
></H1
|
||||
><P
|
||||
>Computers communicate in numbers. In texts, each number will be
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>Chapter 25. Unicode/Charsets</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"><link rel="home" href="index.html" title="SAMBA Project Documentation"><link rel="up" href="optional.html" title="Part III. Advanced Configuration"><link rel="previous" href="securing-samba.html" title="Chapter 24. Securing Samba"><link rel="next" href="locking.html" title="Chapter 26. File and Record Locking"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">Chapter 25. Unicode/Charsets</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="securing-samba.html">Prev</a> </td><th width="60%" align="center">Part III. Advanced Configuration</th><td width="20%" align="right"> <a accesskey="n" href="locking.html">Next</a></td></tr></table><hr></div><div class="chapter" lang="en"><div class="titlepage"><div><h2 class="title"><a name="unicode"></a>Chapter 25. Unicode/Charsets</h2></div><div><div class="author"><h3 class="author">Jelmer R. Vernooij</h3><div class="affiliation"><span class="orgname">The Samba Team<br></span><div class="address"><p><tt><<a href="mailto:jelmer@samba.org">jelmer@samba.org</a>></tt></p></div></div></div></div><div><div class="author"><h3 class="author">TAKAHASHI Motonobu</h3><div class="affiliation"><div class="address"><p><tt><<a href="mailto:monyo@home.monyo.com">monyo@home.monyo.com</a>></tt></p></div></div></div></div><div><p class="pubdate">25 March 2003</p></div></div><div class="toc"><p><b>Table of Contents</b></p><dl><dt><a href="unicode.html#id2901255">What are charsets and unicode?</a></dt><dt><a href="unicode.html#id2901324">Samba and charsets</a></dt><dt><a href="unicode.html#id2901414">Conversion from old names</a></dt><dt><a href="unicode.html#id2901459">Japanese charsets</a></dt></dl></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2901255"></a>What are charsets and unicode?</h2></div></div><p>
|
||||
Computers communicate in numbers. In texts, each number will be
|
||||
translated to a corresponding letter. The meaning that will be assigned
|
||||
to a certain number depends on the <SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>character set(charset)</I
|
||||
></SPAN
|
||||
> that is used.
|
||||
to a certain number depends on the <span class="emphasis"><em>character set(charset)
|
||||
</em></span> that is used.
|
||||
A charset can be seen as a table that is used to translate numbers to
|
||||
letters. Not all computers use the same charset (there are charsets
|
||||
with German umlauts, Japanese characters, etc). Usually a charset contains
|
||||
256 characters, which means that storing a character with it takes
|
||||
exactly one byte. </P
|
||||
><P
|
||||
>There are also charsets that support even more characters,
|
||||
exactly one byte. </p><p>
|
||||
There are also charsets that support even more characters,
|
||||
but those need twice(or even more) as much storage space. These
|
||||
charsets can contain <B
|
||||
CLASS="COMMAND"
|
||||
>256 * 256 = 65536</B
|
||||
> characters, which
|
||||
charsets can contain <b>256 * 256 = 65536</b> characters, which
|
||||
is more then all possible characters one could think of. They are called
|
||||
multibyte charsets (because they use more then one byte to
|
||||
store one character). </P
|
||||
><P
|
||||
>A standardised multibyte charset is unicode, info available at
|
||||
<A
|
||||
HREF="http://www.unicode.org/"
|
||||
TARGET="_top"
|
||||
>www.unicode.org</A
|
||||
>.
|
||||
Big advantage of using a multibyte charset is that you only need one; no
|
||||
store one character).
|
||||
</p><p>
|
||||
A standardised multibyte charset is unicode, info is available at
|
||||
<a href="http://www.unicode.org/" target="_top">www.unicode.org</a>.
|
||||
A big advantage of using a multibyte charset is that you only need one; no
|
||||
need to make sure two computers use the same charset when they are
|
||||
communicating.</P
|
||||
><P
|
||||
>Old windows clients used to use single-byte charsets, named
|
||||
communicating.
|
||||
</p><p>Old windows clients used to use single-byte charsets, named
|
||||
'codepages' by microsoft. However, there is no support for
|
||||
negotiating the charset to be used in the smb protocol. Thus, you
|
||||
have to make sure you are using the same charset when talking to an old client.
|
||||
Newer clients (Windows NT, 2K, XP) talk unicode over the wire.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN4141"
|
||||
>26.2. Samba and charsets</A
|
||||
></H1
|
||||
><P
|
||||
>As of samba 3.0, samba can (and will) talk unicode over the wire. Internally,
|
||||
samba knows of three kinds of character sets: </P
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>unix charset</DT
|
||||
><DD
|
||||
><P
|
||||
> This is the charset used internally by your operating system.
|
||||
The default is <CODE
|
||||
CLASS="CONSTANT"
|
||||
>ASCII</CODE
|
||||
>, which is fine for most
|
||||
Newer clients (Windows NT, 2K, XP) talk unicode over the wire.
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2901324"></a>Samba and charsets</h2></div></div><p>
|
||||
As of samba 3.0, samba can (and will) talk unicode over the wire. Internally,
|
||||
samba knows of three kinds of character sets:
|
||||
</p><div class="variablelist"><dl><dt><span class="term">unix charset</span></dt><dd><p>
|
||||
This is the charset used internally by your operating system.
|
||||
The default is <tt>ASCII</tt>, which is fine for most
|
||||
systems.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>display charset</DT
|
||||
><DD
|
||||
><P
|
||||
>This is the charset samba will use to print messages
|
||||
on your screen. It should generally be the same as the <B
|
||||
CLASS="COMMAND"
|
||||
>unix charset</B
|
||||
>.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>dos charset</DT
|
||||
><DD
|
||||
><P
|
||||
>This is the charset samba uses when communicating with
|
||||
</p></dd><dt><span class="term">display charset</span></dt><dd><p>This is the charset samba will use to print messages
|
||||
on your screen. It should generally be the same as the <b>unix charset</b>.
|
||||
</p></dd><dt><span class="term">dos charset</span></dt><dd><p>This is the charset samba uses when communicating with
|
||||
DOS and Windows 9x clients. It will talk unicode to all newer clients.
|
||||
The default depends on the charsets you have installed on your system.
|
||||
Run <B
|
||||
CLASS="COMMAND"
|
||||
>testparm -v | grep "dos charset"</B
|
||||
> to see
|
||||
Run <b>testparm -v | grep "dos charset"</b> to see
|
||||
what the default is on your system.
|
||||
</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN4160"
|
||||
>26.3. Conversion from old names</A
|
||||
></H1
|
||||
><P
|
||||
>Because previous samba versions did not do any charset conversion,
|
||||
</p></dd></dl></div></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2901414"></a>Conversion from old names</h2></div></div><p>Because previous samba versions did not do any charset conversion,
|
||||
characters in filenames are usually not correct in the unix charset but only
|
||||
for the local charset used by the DOS/Windows clients.</P
|
||||
><P
|
||||
>The following script from Steve Langasek converts all
|
||||
filenames from CP850 to the iso8859-15 charset.</P
|
||||
><P
|
||||
><SAMP
|
||||
CLASS="PROMPT"
|
||||
>#</SAMP
|
||||
><KBD
|
||||
CLASS="USERINPUT"
|
||||
>find <VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>/path/to/share</VAR
|
||||
> -type f -exec bash -c 'CP="{}"; ISO=`echo -n "$CP" | iconv -f cp850 \
|
||||
-t iso8859-15`; if [ "$CP" != "$ISO" ]; then mv "$CP" "$ISO"; fi' \;</KBD
|
||||
></P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="SECT1"
|
||||
><H1
|
||||
CLASS="SECT1"
|
||||
><A
|
||||
NAME="AEN4168"
|
||||
>26.4. Japanese charsets</A
|
||||
></H1
|
||||
><P
|
||||
>Samba doesn't work correctly with Japanese charsets yet. Here are points of attention when setting it up:</P
|
||||
><P
|
||||
></P
|
||||
><TABLE
|
||||
BORDER="0"
|
||||
><TBODY
|
||||
><TR
|
||||
><TD
|
||||
>You should set <B
|
||||
CLASS="COMMAND"
|
||||
>mangling method = hash</B
|
||||
></TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>There are various iconv() implementations around and not all of
|
||||
them work equally well. glibc2's iconv() has a critical problem in CP932.
|
||||
libiconv-1.8 works with CP932 but still has some problems and does not
|
||||
work with EUC-JP. </TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>You should set <B
|
||||
CLASS="COMMAND"
|
||||
>dos charset = CP932</B
|
||||
>, not Shift_JIS, SJIS...</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>Currently only <B
|
||||
CLASS="COMMAND"
|
||||
>unix charset = CP932</B
|
||||
> will work (but still has some problems...) because of iconv() issues. <B
|
||||
CLASS="COMMAND"
|
||||
>unix charset = EUC-JP</B
|
||||
> doesn't work well because of iconv() issues.</TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
>Currently Samba 3.0 does not support <B
|
||||
CLASS="COMMAND"
|
||||
>unix charset = UTF8-MAC/CAP/HEX/JIS*</B
|
||||
></TD
|
||||
></TR
|
||||
></TBODY
|
||||
></TABLE
|
||||
><P
|
||||
></P
|
||||
><P
|
||||
>More information (in Japanese) is available at: <A
|
||||
HREF="http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html"
|
||||
TARGET="_top"
|
||||
>http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html</A
|
||||
>.</P
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="NAVFOOTER"
|
||||
><HR
|
||||
ALIGN="LEFT"
|
||||
WIDTH="100%"><TABLE
|
||||
SUMMARY="Footer navigation table"
|
||||
WIDTH="100%"
|
||||
BORDER="0"
|
||||
CELLPADDING="0"
|
||||
CELLSPACING="0"
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="securing-samba.html"
|
||||
ACCESSKEY="P"
|
||||
>Prev</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="samba-howto-collection.html"
|
||||
ACCESSKEY="H"
|
||||
>Home</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="appendixes.html"
|
||||
ACCESSKEY="N"
|
||||
>Next</A
|
||||
></TD
|
||||
></TR
|
||||
><TR
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="left"
|
||||
VALIGN="top"
|
||||
>Securing Samba</TD
|
||||
><TD
|
||||
WIDTH="34%"
|
||||
ALIGN="center"
|
||||
VALIGN="top"
|
||||
><A
|
||||
HREF="optional.html"
|
||||
ACCESSKEY="U"
|
||||
>Up</A
|
||||
></TD
|
||||
><TD
|
||||
WIDTH="33%"
|
||||
ALIGN="right"
|
||||
VALIGN="top"
|
||||
>Appendixes</TD
|
||||
></TR
|
||||
></TABLE
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
for the local charset used by the DOS/Windows clients.</p><p>The following script from Steve Langasek converts all
|
||||
filenames from CP850 to the iso8859-15 charset.</p><p>
|
||||
<tt>#</tt><b><tt>find <i><tt>/path/to/share</tt></i> -type f -exec bash -c 'CP="{}"; ISO=`echo -n "$CP" | iconv -f cp850 \
|
||||
-t iso8859-15`; if [ "$CP" != "$ISO" ]; then mv "$CP" "$ISO"; fi' \;
|
||||
</tt></b>
|
||||
</p></div><div class="sect1" lang="en"><div class="titlepage"><div><h2 class="title" style="clear: both"><a name="id2901459"></a>Japanese charsets</h2></div></div><p>Samba doesn't work correctly with Japanese charsets yet. Here are
|
||||
points of attention when setting it up:</p><div class="itemizedlist"><ul type="disc"><li><p>You should set <b>mangling method =
|
||||
hash</b></p></li><li><p>There are various iconv() implementations around and not
|
||||
all of them work equally well. glibc2's iconv() has a critical problem
|
||||
in CP932. libiconv-1.8 works with CP932 but still has some problems and
|
||||
does not work with EUC-JP.</p></li><li><p>You should set <b>dos charset = CP932</b>, not
|
||||
Shift_JIS, SJIS...</p></li><li><p>Currently only <b>unix charset = CP932</b>
|
||||
will work (but still has some problems...) because of iconv() issues.
|
||||
<b>unix charset = EUC-JP</b> doesn't work well because of
|
||||
iconv() issues.</p></li><li><p>Currently Samba 3.0 does not support <b>unix charset
|
||||
= UTF8-MAC/CAP/HEX/JIS*</b></p></li></ul></div><p>More information (in Japanese) is available at: <a href="http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html" target="_top">http://www.atmarkit.co.jp/flinux/special/samba3/samba3a.html</a>.</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="securing-samba.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="optional.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="locking.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">Chapter 24. Securing Samba </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> Chapter 26. File and Record Locking</td></tr></table></div></body></html>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -1,537 +1,43 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>vfstest</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="VFSTEST.1"
|
||||
></A
|
||||
>vfstest</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>vfstest -- tool for testing samba VFS modules </DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>vfstest</B
|
||||
> [-d debuglevel] [-c command] [-l logfile] [-h]</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN15"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
>This tool is part of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
> suite.</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>vfstest</B
|
||||
> is a small command line
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>vfstest</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="vfstest.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>vfstest — tool for testing samba VFS modules </p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>vfstest</tt> [-d debuglevel] [-c command] [-l logfile] [-h]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p><b>vfstest</b> is a small command line
|
||||
utility that has the ability to test dso samba VFS modules. It gives the
|
||||
user the ability to call the various VFS functions manually and
|
||||
supports cascaded VFS modules.
|
||||
</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN23"
|
||||
></A
|
||||
><H2
|
||||
>OPTIONS</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>-c|--command=command</DT
|
||||
><DD
|
||||
><P
|
||||
>Execute the specified (colon-separated) commands.
|
||||
</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-c|--command=command</span></dt><dd><p>Execute the specified (colon-separated) commands.
|
||||
See below for the commands that are available.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-h|--help</DT
|
||||
><DD
|
||||
><P
|
||||
>Print a summary of command line options.</P
|
||||
></DD
|
||||
><DT
|
||||
>-l|--logfile=logbasename</DT
|
||||
><DD
|
||||
><P
|
||||
>File name for log/debug files. The extension
|
||||
<CODE
|
||||
CLASS="CONSTANT"
|
||||
>'.client'</CODE
|
||||
> will be appended. The log file is never removed
|
||||
</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
|
||||
</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
|
||||
<tt>'.client'</tt> will be appended. The log file is never removed
|
||||
by the client.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-V</DT
|
||||
><DD
|
||||
><P
|
||||
>Prints the version number for
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
>.</P
|
||||
></DD
|
||||
><DT
|
||||
>-s <configuration file></DT
|
||||
><DD
|
||||
><P
|
||||
>The file specified contains the
|
||||
</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for
|
||||
<b>smbd</b>.</p></dd><dt><span class="term">-s <configuration file></span></dt><dd><p>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 <A
|
||||
HREF="smb.conf.5.html"
|
||||
TARGET="_top"
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf(5)</TT
|
||||
></A
|
||||
> for more information.
|
||||
to provide. See <a href="smb.conf.5.html" target="_top"><tt>
|
||||
smb.conf(5)</tt></a> for more information.
|
||||
The default configuration file name is determined at
|
||||
compile time.</P
|
||||
></DD
|
||||
><DT
|
||||
>-d|--debug=debuglevel</DT
|
||||
><DD
|
||||
><P
|
||||
><VAR
|
||||
CLASS="REPLACEABLE"
|
||||
>debuglevel</VAR
|
||||
> is an integer
|
||||
compile time.</p></dd><dt><span class="term">-d|--debug=debuglevel</span></dt><dd><p><i><tt>debuglevel</tt></i> is an integer
|
||||
from 0 to 10. The default value if this parameter is
|
||||
not specified is zero.</P
|
||||
><P
|
||||
>The higher this value, the more detail will be
|
||||
not specified is zero.</p><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
|
||||
><P
|
||||
>Levels above 1 will generate considerable
|
||||
information about operations carried out.</p><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
|
||||
><P
|
||||
>Note that specifying this parameter here will
|
||||
override the <A
|
||||
HREF="smb.conf.5.html#loglevel"
|
||||
TARGET="_top"
|
||||
>log
|
||||
level</A
|
||||
> parameter in the <A
|
||||
HREF="smb.conf.5.html"
|
||||
TARGET="_top"
|
||||
><TT
|
||||
CLASS="FILENAME"
|
||||
>smb.conf(5)</TT
|
||||
></A
|
||||
> file.</P
|
||||
></DD
|
||||
><DT
|
||||
>-l|--logfile=logbasename</DT
|
||||
><DD
|
||||
><P
|
||||
>File name for log/debug files. The extension
|
||||
<CODE
|
||||
CLASS="CONSTANT"
|
||||
>".client"</CODE
|
||||
> will be appended. The log file is
|
||||
never removed by the client.</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN66"
|
||||
></A
|
||||
><H2
|
||||
>COMMANDS</H2
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>VFS COMMANDS</I
|
||||
></SPAN
|
||||
></P
|
||||
><P
|
||||
></P
|
||||
><UL
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>load <module.so></B
|
||||
> - Load specified VFS module </P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>populate <char> <size></B
|
||||
> - Populate a data buffer with the specified data
|
||||
</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>showdata [<offset> <len>]</B
|
||||
> - Show data currently in data buffer
|
||||
</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>connect</B
|
||||
> - VFS connect()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>disconnect</B
|
||||
> - VFS disconnect()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>disk_free</B
|
||||
> - VFS disk_free()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>opendir</B
|
||||
> - VFS opendir()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>readdir</B
|
||||
> - VFS readdir()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>mkdir</B
|
||||
> - VFS mkdir()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>rmdir</B
|
||||
> - VFS rmdir()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>closedir</B
|
||||
> - VFS closedir()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>open</B
|
||||
> - VFS open()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>close</B
|
||||
> - VFS close()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>read</B
|
||||
> - VFS read()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>write</B
|
||||
> - VFS write()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>lseek</B
|
||||
> - VFS lseek()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>rename</B
|
||||
> - VFS rename()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>fsync</B
|
||||
> - VFS fsync()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>stat</B
|
||||
> - VFS stat()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>fstat</B
|
||||
> - VFS fstat()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>lstat</B
|
||||
> - VFS lstat()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>unlink</B
|
||||
> - VFS unlink()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>chmod</B
|
||||
> - VFS chmod()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>fchmod</B
|
||||
> - VFS fchmod()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>chown</B
|
||||
> - VFS chown()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>fchown</B
|
||||
> - VFS fchown()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>chdir</B
|
||||
> - VFS chdir()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>getwd</B
|
||||
> - VFS getwd()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>utime</B
|
||||
> - VFS utime()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>ftruncate</B
|
||||
> - VFS ftruncate()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>lock</B
|
||||
> - VFS lock()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>symlink</B
|
||||
> - VFS symlink()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>readlink</B
|
||||
> - VFS readlink()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>link</B
|
||||
> - VFS link()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>mknod</B
|
||||
> - VFS mknod()</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>realpath</B
|
||||
> - VFS realpath()</P
|
||||
></LI
|
||||
></UL
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="emphasis"
|
||||
><I
|
||||
CLASS="EMPHASIS"
|
||||
>GENERAL COMMANDS</I
|
||||
></SPAN
|
||||
></P
|
||||
><P
|
||||
></P
|
||||
><UL
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>conf <smb.conf></B
|
||||
> - Load a different configuration file</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>help [<command>]</B
|
||||
> - Get list of commands or info about specified command</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>debuglevel <level></B
|
||||
> - Set debug level</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>freemem</B
|
||||
> - Free memory currently in use</P
|
||||
></LI
|
||||
><LI
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>exit</B
|
||||
> - Exit vfstest</P
|
||||
></LI
|
||||
></UL
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN197"
|
||||
></A
|
||||
><H2
|
||||
>VERSION</H2
|
||||
><P
|
||||
>This man page is correct for version 3.0 of the Samba
|
||||
suite.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN200"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>The original Samba software and related utilities
|
||||
data, most of which is extremely cryptic.</p><p>Note that specifying this parameter here will
|
||||
override the <a href="smb.conf.5.html#loglevel" target="_top">log
|
||||
level</a> parameter in the <a href="smb.conf.5.html" target="_top">
|
||||
<tt>smb.conf(5)</tt></a> file.</p></dd><dt><span class="term">-l|--logfile=logbasename</span></dt><dd><p>File name for log/debug files. The extension
|
||||
<tt>".client"</tt> will be appended. The log file is
|
||||
never removed by the client.
|
||||
</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>COMMANDS</h2><p><span class="emphasis"><em>VFS COMMANDS</em></span></p><div class="itemizedlist"><ul type="disc"><li><p><b>load <module.so></b> - Load specified VFS module </p></li><li><p><b>populate <char> <size></b> - Populate a data buffer with the specified data
|
||||
</p></li><li><p><b>showdata [<offset> <len>]</b> - Show data currently in data buffer
|
||||
</p></li><li><p><b>connect</b> - VFS connect()</p></li><li><p><b>disconnect</b> - VFS disconnect()</p></li><li><p><b>disk_free</b> - VFS disk_free()</p></li><li><p><b>opendir</b> - VFS opendir()</p></li><li><p><b>readdir</b> - VFS readdir()</p></li><li><p><b>mkdir</b> - VFS mkdir()</p></li><li><p><b>rmdir</b> - VFS rmdir()</p></li><li><p><b>closedir</b> - VFS closedir()</p></li><li><p><b>open</b> - VFS open()</p></li><li><p><b>close</b> - VFS close()</p></li><li><p><b>read</b> - VFS read()</p></li><li><p><b>write</b> - VFS write()</p></li><li><p><b>lseek</b> - VFS lseek()</p></li><li><p><b>rename</b> - VFS rename()</p></li><li><p><b>fsync</b> - VFS fsync()</p></li><li><p><b>stat</b> - VFS stat()</p></li><li><p><b>fstat</b> - VFS fstat()</p></li><li><p><b>lstat</b> - VFS lstat()</p></li><li><p><b>unlink</b> - VFS unlink()</p></li><li><p><b>chmod</b> - VFS chmod()</p></li><li><p><b>fchmod</b> - VFS fchmod()</p></li><li><p><b>chown</b> - VFS chown()</p></li><li><p><b>fchown</b> - VFS fchown()</p></li><li><p><b>chdir</b> - VFS chdir()</p></li><li><p><b>getwd</b> - VFS getwd()</p></li><li><p><b>utime</b> - VFS utime()</p></li><li><p><b>ftruncate</b> - VFS ftruncate()</p></li><li><p><b>lock</b> - VFS lock()</p></li><li><p><b>symlink</b> - VFS symlink()</p></li><li><p><b>readlink</b> - VFS readlink()</p></li><li><p><b>link</b> - VFS link()</p></li><li><p><b>mknod</b> - VFS mknod()</p></li><li><p><b>realpath</b> - VFS realpath()</p></li></ul></div><p><span class="emphasis"><em>GENERAL COMMANDS</em></span></p><div class="itemizedlist"><ul type="disc"><li><p><b>conf <smb.conf></b> - Load a different configuration file</p></li><li><p><b>help [<command>]</b> - Get list of commands or info about specified command</p></li><li><p><b>debuglevel <level></b> - Set debug level</p></li><li><p><b>freemem</b> - Free memory currently in use</p></li><li><p><b>exit</b> - Exit vfstest</p></li></ul></div></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of the Samba
|
||||
suite.</p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.</P
|
||||
><P
|
||||
>The vfstest man page was written by Jelmer Vernooij.</P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
to the way the Linux kernel is developed.</p><p>The vfstest man page was written by Jelmer Vernooij.</p></div></div></body></html>
|
||||
|
||||
@ -1,444 +1,71 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||||
<HTML
|
||||
><HEAD
|
||||
><TITLE
|
||||
>wbinfo</TITLE
|
||||
><META
|
||||
NAME="GENERATOR"
|
||||
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"></HEAD
|
||||
><BODY
|
||||
CLASS="REFENTRY"
|
||||
BGCOLOR="#FFFFFF"
|
||||
TEXT="#000000"
|
||||
LINK="#0000FF"
|
||||
VLINK="#840084"
|
||||
ALINK="#0000FF"
|
||||
><H1
|
||||
><A
|
||||
NAME="WBINFO.1"
|
||||
></A
|
||||
>wbinfo</H1
|
||||
><DIV
|
||||
CLASS="REFNAMEDIV"
|
||||
><A
|
||||
NAME="AEN5"
|
||||
></A
|
||||
><H2
|
||||
>Name</H2
|
||||
>wbinfo -- Query information from winbind daemon</DIV
|
||||
><DIV
|
||||
CLASS="REFSYNOPSISDIV"
|
||||
><A
|
||||
NAME="AEN8"
|
||||
></A
|
||||
><H2
|
||||
>Synopsis</H2
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>wbinfo</B
|
||||
> [-u] [-g] [-N netbios-name] [-I ip] [-n name] [-s sid] [-U uid] [-G gid] [-S sid] [-Y sid] [-t] [-m] [--sequence] [-r user] [-a user%password] [-A user%password] [--get-auth-user] [-p]</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN29"
|
||||
></A
|
||||
><H2
|
||||
>DESCRIPTION</H2
|
||||
><P
|
||||
>This tool is part of the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
> suite.</P
|
||||
><P
|
||||
>The <B
|
||||
CLASS="COMMAND"
|
||||
>wbinfo</B
|
||||
> program queries and returns information
|
||||
created and used by the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>winbindd</SPAN
|
||||
>(8)</SPAN
|
||||
> daemon. </P
|
||||
><P
|
||||
>The <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>winbindd</SPAN
|
||||
>(8)</SPAN
|
||||
> daemon must be configured
|
||||
and running for the <B
|
||||
CLASS="COMMAND"
|
||||
>wbinfo</B
|
||||
> program to be able
|
||||
to return information.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN45"
|
||||
></A
|
||||
><H2
|
||||
>OPTIONS</H2
|
||||
><P
|
||||
></P
|
||||
><DIV
|
||||
CLASS="VARIABLELIST"
|
||||
><DL
|
||||
><DT
|
||||
>-u</DT
|
||||
><DD
|
||||
><P
|
||||
>This option will list all users available
|
||||
in the Windows NT domain for which the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>winbindd</SPAN
|
||||
>(8)</SPAN
|
||||
> daemon is operating in. Users in all trusted domains
|
||||
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>wbinfo</title><link rel="stylesheet" href="samba.css" type="text/css"><meta name="generator" content="DocBook XSL Stylesheets V1.59.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry" lang="en"><a name="wbinfo.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>wbinfo — Query information from winbind daemon</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><tt>wbinfo</tt> [-u] [-g] [-N netbios-name] [-I ip] [-n name] [-s sid] [-U uid] [-G gid] [-S sid] [-Y sid] [-t] [-m] [--sequence] [-r user] [-a user%password] [-A user%password] [--get-auth-user] [-p]</p></div></div><div class="refsect1" lang="en"><h2>DESCRIPTION</h2><p>This tool is part of the <a href="Samba.7.html">Samba(7)</a> suite.</p><p>The <b>wbinfo</b> program queries and returns information
|
||||
created and used by the <a href="winbindd.8.html">winbindd(8)</a> daemon. </p><p>The <a href="winbindd.8.html">winbindd(8)</a> daemon must be configured
|
||||
and running for the <b>wbinfo</b> program to be able
|
||||
to return information.</p></div><div class="refsect1" lang="en"><h2>OPTIONS</h2><div class="variablelist"><dl><dt><span class="term">-u</span></dt><dd><p>This option will list all users available
|
||||
in the Windows NT domain for which the <a href="winbindd.8.html">winbindd(8)</a> daemon is operating in. Users in all trusted domains
|
||||
will also be listed. Note that this operation does not assign
|
||||
user ids to any users that have not already been seen by <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>winbindd</SPAN
|
||||
>(8)</SPAN
|
||||
>
|
||||
.</P
|
||||
></DD
|
||||
><DT
|
||||
>-g</DT
|
||||
><DD
|
||||
><P
|
||||
>This option will list all groups available
|
||||
in the Windows NT domain for which the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>Samba</SPAN
|
||||
>(7)</SPAN
|
||||
> daemon is operating in. Groups in all trusted domains
|
||||
user ids to any users that have not already been seen by <a href="winbindd.8.html">winbindd(8)</a>
|
||||
.</p></dd><dt><span class="term">-g</span></dt><dd><p>This option will list all groups available
|
||||
in the Windows NT domain for which the <a href="Samba.7.html">Samba(7)</a> daemon is operating in. Groups in all trusted domains
|
||||
will also be listed. Note that this operation does not assign
|
||||
group ids to any groups that have not already been
|
||||
seen by <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>winbindd</SPAN
|
||||
>(8)</SPAN
|
||||
>. </P
|
||||
></DD
|
||||
><DT
|
||||
>-N name</DT
|
||||
><DD
|
||||
><P
|
||||
>The <VAR
|
||||
CLASS="PARAMETER"
|
||||
>-N</VAR
|
||||
> option
|
||||
queries <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>winbindd</SPAN
|
||||
>(8)</SPAN
|
||||
> to query the WINS
|
||||
seen by <a href="winbindd.8.html">winbindd(8)</a>. </p></dd><dt><span class="term">-N name</span></dt><dd><p>The <i><tt>-N</tt></i> option
|
||||
queries <a href="winbindd.8.html">winbindd(8)</a> to query the WINS
|
||||
server for the IP address associated with the NetBIOS name
|
||||
specified by the <VAR
|
||||
CLASS="PARAMETER"
|
||||
>name</VAR
|
||||
> parameter.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-I ip</DT
|
||||
><DD
|
||||
><P
|
||||
>The <VAR
|
||||
CLASS="PARAMETER"
|
||||
>-I</VAR
|
||||
> option
|
||||
queries <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>winbindd</SPAN
|
||||
>(8)</SPAN
|
||||
> to send a node status
|
||||
specified by the <i><tt>name</tt></i> parameter.
|
||||
</p></dd><dt><span class="term">-I ip</span></dt><dd><p>The <i><tt>-I</tt></i> option
|
||||
queries <a href="winbindd.8.html">winbindd(8)</a> to send a node status
|
||||
request to get the NetBIOS name associated with the IP address
|
||||
specified by the <VAR
|
||||
CLASS="PARAMETER"
|
||||
>ip</VAR
|
||||
> parameter.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-n name</DT
|
||||
><DD
|
||||
><P
|
||||
>The <VAR
|
||||
CLASS="PARAMETER"
|
||||
>-n</VAR
|
||||
> option
|
||||
queries <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>winbindd</SPAN
|
||||
>(8)</SPAN
|
||||
> for the SID
|
||||
specified by the <i><tt>ip</tt></i> parameter.
|
||||
</p></dd><dt><span class="term">-n name</span></dt><dd><p>The <i><tt>-n</tt></i> option
|
||||
queries <a href="winbindd.8.html">winbindd(8)</a> for the SID
|
||||
associated with the name specified. Domain names can be specified
|
||||
before the user name by using the winbind separator character.
|
||||
For example CWDOM1/Administrator refers to the Administrator
|
||||
user in the domain CWDOM1. If no domain is specified then the
|
||||
domain used is the one specified in the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>smb.conf</SPAN
|
||||
>(5)</SPAN
|
||||
> <VAR
|
||||
CLASS="PARAMETER"
|
||||
>workgroup
|
||||
</VAR
|
||||
> parameter. </P
|
||||
></DD
|
||||
><DT
|
||||
>-s sid</DT
|
||||
><DD
|
||||
><P
|
||||
>Use <VAR
|
||||
CLASS="PARAMETER"
|
||||
>-s</VAR
|
||||
> to resolve
|
||||
a SID to a name. This is the inverse of the <VAR
|
||||
CLASS="PARAMETER"
|
||||
>-n
|
||||
</VAR
|
||||
> option above. SIDs must be specified as ASCII strings
|
||||
domain used is the one specified in the <a href="smb.conf.5.html">smb.conf(5)</a> <i><tt>workgroup
|
||||
</tt></i> parameter. </p></dd><dt><span class="term">-s sid</span></dt><dd><p>Use <i><tt>-s</tt></i> to resolve
|
||||
a SID to a name. This is the inverse of the <i><tt>-n
|
||||
</tt></i> option above. SIDs must be specified as ASCII strings
|
||||
in the traditional Microsoft format. For example,
|
||||
S-1-5-21-1455342024-3071081365-2475485837-500. </P
|
||||
></DD
|
||||
><DT
|
||||
>-U uid</DT
|
||||
><DD
|
||||
><P
|
||||
>Try to convert a UNIX user id to a Windows NT
|
||||
S-1-5-21-1455342024-3071081365-2475485837-500. </p></dd><dt><span class="term">-U uid</span></dt><dd><p>Try to convert a UNIX user id to a Windows NT
|
||||
SID. If the uid specified does not refer to one within
|
||||
the winbind uid range then the operation will fail. </P
|
||||
></DD
|
||||
><DT
|
||||
>-G gid</DT
|
||||
><DD
|
||||
><P
|
||||
>Try to convert a UNIX group id to a Windows
|
||||
the winbind uid range then the operation will fail. </p></dd><dt><span class="term">-G gid</span></dt><dd><p>Try to convert a UNIX group id to a Windows
|
||||
NT SID. If the gid specified does not refer to one within
|
||||
the winbind gid range then the operation will fail. </P
|
||||
></DD
|
||||
><DT
|
||||
>-S sid</DT
|
||||
><DD
|
||||
><P
|
||||
>Convert a SID to a UNIX user id. If the SID
|
||||
does not correspond to a UNIX user mapped by <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>winbindd</SPAN
|
||||
>(8)</SPAN
|
||||
> then the operation will fail. </P
|
||||
></DD
|
||||
><DT
|
||||
>-Y sid</DT
|
||||
><DD
|
||||
><P
|
||||
>Convert a SID to a UNIX group id. If the SID
|
||||
does not correspond to a UNIX group mapped by <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>winbindd</SPAN
|
||||
>(8)</SPAN
|
||||
> then
|
||||
the operation will fail. </P
|
||||
></DD
|
||||
><DT
|
||||
>-t</DT
|
||||
><DD
|
||||
><P
|
||||
>Verify that the workstation trust account
|
||||
the winbind gid range then the operation will fail. </p></dd><dt><span class="term">-S sid</span></dt><dd><p>Convert a SID to a UNIX user id. If the SID
|
||||
does not correspond to a UNIX user mapped by <a href="winbindd.8.html">winbindd(8)</a> then the operation will fail. </p></dd><dt><span class="term">-Y sid</span></dt><dd><p>Convert a SID to a UNIX group id. If the SID
|
||||
does not correspond to a UNIX group mapped by <a href="winbindd.8.html">winbindd(8)</a> then
|
||||
the operation will fail. </p></dd><dt><span class="term">-t</span></dt><dd><p>Verify that the workstation trust account
|
||||
created when the Samba server is added to the Windows NT
|
||||
domain is working. </P
|
||||
></DD
|
||||
><DT
|
||||
>-m</DT
|
||||
><DD
|
||||
><P
|
||||
>Produce a list of domains trusted by the
|
||||
Windows NT server <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>winbindd</SPAN
|
||||
>(8)</SPAN
|
||||
> contacts
|
||||
domain is working. </p></dd><dt><span class="term">-m</span></dt><dd><p>Produce a list of domains trusted by the
|
||||
Windows NT server <a href="winbindd.8.html">winbindd(8)</a> contacts
|
||||
when resolving names. This list does not include the Windows
|
||||
NT domain the server is a Primary Domain Controller for.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>--sequence</DT
|
||||
><DD
|
||||
><P
|
||||
>Show sequence numbers of
|
||||
all known domains</P
|
||||
></DD
|
||||
><DT
|
||||
>-r username</DT
|
||||
><DD
|
||||
><P
|
||||
>Try to obtain the list of UNIX group ids
|
||||
</p></dd><dt><span class="term">--sequence</span></dt><dd><p>Show sequence numbers of
|
||||
all known domains</p></dd><dt><span class="term">-r username</span></dt><dd><p>Try to obtain the list of UNIX group ids
|
||||
to which the user belongs. This only works for users
|
||||
defined on a Domain Controller.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-a username%password</DT
|
||||
><DD
|
||||
><P
|
||||
>Attempt to authenticate a user via winbindd.
|
||||
</p></dd><dt><span class="term">-a username%password</span></dt><dd><p>Attempt to authenticate a user via winbindd.
|
||||
This checks both authenticaion methods and reports its results.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-A username%password</DT
|
||||
><DD
|
||||
><P
|
||||
>Store username and password used by winbindd
|
||||
</p></dd><dt><span class="term">-A username%password</span></dt><dd><p>Store username and password used by winbindd
|
||||
during session setup to a domain controller. This enables
|
||||
winbindd to operate in a Windows 2000 domain with Restrict
|
||||
Anonymous turned on (a.k.a. Permissions compatiable with
|
||||
Windows 2000 servers only).
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>--get-auth-user</DT
|
||||
><DD
|
||||
><P
|
||||
>Print username and password used by winbindd
|
||||
</p></dd><dt><span class="term">--get-auth-user</span></dt><dd><p>Print username and password used by winbindd
|
||||
during session setup to a domain controller. Username
|
||||
and password can be set using '-A'. Only available for
|
||||
root.</P
|
||||
></DD
|
||||
><DT
|
||||
>-p</DT
|
||||
><DD
|
||||
><P
|
||||
>Check whether winbindd is still alive.
|
||||
root.</p></dd><dt><span class="term">-p</span></dt><dd><p>Check whether winbindd is still alive.
|
||||
Prints out either 'succeeded' or 'failed'.
|
||||
</P
|
||||
></DD
|
||||
><DT
|
||||
>-V</DT
|
||||
><DD
|
||||
><P
|
||||
>Prints the version number for
|
||||
<B
|
||||
CLASS="COMMAND"
|
||||
>smbd</B
|
||||
>.</P
|
||||
></DD
|
||||
><DT
|
||||
>-h|--help</DT
|
||||
><DD
|
||||
><P
|
||||
>Print a summary of command line options.</P
|
||||
></DD
|
||||
></DL
|
||||
></DIV
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN170"
|
||||
></A
|
||||
><H2
|
||||
>EXIT STATUS</H2
|
||||
><P
|
||||
>The wbinfo program returns 0 if the operation
|
||||
succeeded, or 1 if the operation failed. If the <SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>winbindd</SPAN
|
||||
>(8)</SPAN
|
||||
> daemon is not working <B
|
||||
CLASS="COMMAND"
|
||||
>wbinfo</B
|
||||
> will always return
|
||||
failure. </P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN177"
|
||||
></A
|
||||
><H2
|
||||
>VERSION</H2
|
||||
><P
|
||||
>This man page is correct for version 3.0 of
|
||||
the Samba suite.</P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN180"
|
||||
></A
|
||||
><H2
|
||||
>SEE ALSO</H2
|
||||
><P
|
||||
><SPAN
|
||||
CLASS="CITEREFENTRY"
|
||||
><SPAN
|
||||
CLASS="REFENTRYTITLE"
|
||||
>winbindd</SPAN
|
||||
>(8)</SPAN
|
||||
></P
|
||||
></DIV
|
||||
><DIV
|
||||
CLASS="REFSECT1"
|
||||
><A
|
||||
NAME="AEN186"
|
||||
></A
|
||||
><H2
|
||||
>AUTHOR</H2
|
||||
><P
|
||||
>The original Samba software and related utilities
|
||||
</p></dd><dt><span class="term">-V</span></dt><dd><p>Prints the version number for
|
||||
<b>smbd</b>.</p></dd><dt><span class="term">-h|--help</span></dt><dd><p>Print a summary of command line options.
|
||||
</p></dd></dl></div></div><div class="refsect1" lang="en"><h2>EXIT STATUS</h2><p>The wbinfo program returns 0 if the operation
|
||||
succeeded, or 1 if the operation failed. If the <a href="winbindd.8.html">winbindd(8)</a> daemon is not working <b>wbinfo</b> will always return
|
||||
failure. </p></div><div class="refsect1" lang="en"><h2>VERSION</h2><p>This man page is correct for version 3.0 of
|
||||
the Samba suite.</p></div><div class="refsect1" lang="en"><h2>SEE ALSO</h2><p><a href="winbindd.8.html">winbindd(8)</a></p></div><div class="refsect1" lang="en"><h2>AUTHOR</h2><p>The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.</P
|
||||
><P
|
||||
><B
|
||||
CLASS="COMMAND"
|
||||
>wbinfo</B
|
||||
> and <B
|
||||
CLASS="COMMAND"
|
||||
>winbindd</B
|
||||
>
|
||||
were written by Tim Potter.</P
|
||||
><P
|
||||
>The conversion to DocBook for Samba 2.2 was done
|
||||
to the way the Linux kernel is developed.</p><p><b>wbinfo</b> and <b>winbindd</b>
|
||||
were written by Tim Potter.</p><p>The conversion to DocBook for Samba 2.2 was done
|
||||
by Gerald Carter. The conversion to DocBook XML 4.2 for Samba
|
||||
3.0 was done by Alexander Bokovoy.</P
|
||||
></DIV
|
||||
></BODY
|
||||
></HTML
|
||||
>
|
||||
3.0 was done by Alexander Bokovoy.</p></div></div></body></html>
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -1,45 +1,71 @@
|
||||
.\" This manpage has been automatically generated by docbook2man
|
||||
.\" from a DocBook document. This tool can be found at:
|
||||
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
||||
.\" Please send any bug reports, improvements, comments, patches,
|
||||
.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
||||
.TH "EDITREG" "1" "19 april 2003" "" ""
|
||||
|
||||
.\"Generated by db2man.xsl. Don't modify this, modify the source.
|
||||
.de Sh \" Subsection
|
||||
.br
|
||||
.if t .Sp
|
||||
.ne 5
|
||||
.PP
|
||||
\fB\\$1\fR
|
||||
.PP
|
||||
..
|
||||
.de Sp \" Vertical space (when we can't use .PP)
|
||||
.if t .sp .5v
|
||||
.if n .sp
|
||||
..
|
||||
.de Ip \" List item
|
||||
.br
|
||||
.ie \\n(.$>=3 .ne \\$3
|
||||
.el .ne 3
|
||||
.IP "\\$1" \\$2
|
||||
..
|
||||
.TH "EDITREG" 1 "" "" ""
|
||||
.SH NAME
|
||||
editreg \- A utility to report and change SIDs in registry files
|
||||
.SH SYNOPSIS
|
||||
.SH "SYNOPSIS"
|
||||
|
||||
\fBeditreg\fR [ \fB-v\fR ] [ \fB-c file\fR ] \fBfile\fR
|
||||
.nf
|
||||
\fBeditreg\fR [-v] [-c file] {file}
|
||||
.fi
|
||||
|
||||
.SH "DESCRIPTION"
|
||||
|
||||
.PP
|
||||
This tool is part of the \fBSamba\fR(7) suite.
|
||||
This tool is part of the \fBSamba\fR(7) suite\&.
|
||||
|
||||
.PP
|
||||
\fBeditreg\fR is a utility that
|
||||
can visualize windows registry files (currently only NT4) and apply
|
||||
so-called commandfiles to them.
|
||||
\fBeditreg\fR is a utility that can visualize windows registry files (currently only NT4) and apply so-called commandfiles to them\&.
|
||||
|
||||
.SH "OPTIONS"
|
||||
|
||||
.TP
|
||||
\fBregistry_file\fR
|
||||
Registry file to view or edit.
|
||||
registry_file
|
||||
Registry file to view or edit\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-v,--verbose\fR
|
||||
Increases verbosity of messages.
|
||||
-v,--verbose
|
||||
Increases verbosity of messages\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-c commandfile\fR
|
||||
Read commands to execute on \fIregistry_file\fR from \fIcommandfile\fR. Currently not yet supported!
|
||||
-c commandfile
|
||||
Read commands to execute on \fIregistry_file\fR from \fIcommandfile\fR\&. Currently not yet supported!
|
||||
|
||||
|
||||
.TP
|
||||
\fB-h|--help\fR
|
||||
Print a summary of command line options.
|
||||
-h|--help
|
||||
Print a summary of command line options\&.
|
||||
|
||||
|
||||
.SH "VERSION"
|
||||
|
||||
.PP
|
||||
This man page is correct for version 3.0 of the Samba
|
||||
suite.
|
||||
This man page is correct for version 3\&.0 of the Samba suite\&.
|
||||
|
||||
.SH "AUTHOR"
|
||||
|
||||
.PP
|
||||
The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.
|
||||
The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
|
||||
|
||||
.PP
|
||||
The editreg man page was written by Jelmer Vernooij.
|
||||
The editreg man page was written by Jelmer Vernooij\&.
|
||||
|
||||
|
||||
@ -1,103 +1,95 @@
|
||||
.\" This manpage has been automatically generated by docbook2man
|
||||
.\" from a DocBook document. This tool can be found at:
|
||||
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
||||
.\" Please send any bug reports, improvements, comments, patches,
|
||||
.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
||||
.TH "FINDSMB" "1" "19 april 2003" "" ""
|
||||
|
||||
.\"Generated by db2man.xsl. Don't modify this, modify the source.
|
||||
.de Sh \" Subsection
|
||||
.br
|
||||
.if t .Sp
|
||||
.ne 5
|
||||
.PP
|
||||
\fB\\$1\fR
|
||||
.PP
|
||||
..
|
||||
.de Sp \" Vertical space (when we can't use .PP)
|
||||
.if t .sp .5v
|
||||
.if n .sp
|
||||
..
|
||||
.de Ip \" List item
|
||||
.br
|
||||
.ie \\n(.$>=3 .ne \\$3
|
||||
.el .ne 3
|
||||
.IP "\\$1" \\$2
|
||||
..
|
||||
.TH "FINDSMB" 1 "" "" ""
|
||||
.SH NAME
|
||||
findsmb \- list info about machines that respond to SMB name queries on a subnet
|
||||
.SH SYNOPSIS
|
||||
|
||||
\fBfindsmb\fR [ \fBsubnet broadcast address\fR ]
|
||||
|
||||
.SH "DESCRIPTION"
|
||||
.PP
|
||||
This perl script is part of the \fBSamba\fR(7)
|
||||
suite.
|
||||
.PP
|
||||
\fBfindsmb\fR is a perl script that
|
||||
prints out several pieces of information about machines
|
||||
on a subnet that respond to SMB name query requests.
|
||||
It uses \fBnmblookup\fR(1)
|
||||
and \fBsmbclient\fR(1)
|
||||
to obtain this information.
|
||||
.SH "OPTIONS"
|
||||
.TP
|
||||
\fB-r\fR
|
||||
Controls whether \fBfindsmb\fR takes
|
||||
bugs in Windows95 into account when trying to find a Netbios name
|
||||
registered of the remote machine. This option is disabled by default
|
||||
because it is specific to Windows 95 and Windows 95 machines only.
|
||||
If set, \fBnmblookup\fR(1)
|
||||
will be called with -B option.
|
||||
.TP
|
||||
\fBsubnet broadcast address\fR
|
||||
Without this option, \fBfindsmb
|
||||
\fR will probe the subnet of the machine where
|
||||
\fBfindsmb\fR(1)
|
||||
is run. This value is passed to
|
||||
\fBnmblookup\fR(1)
|
||||
as part of the -B option.
|
||||
.SH "EXAMPLES"
|
||||
.PP
|
||||
The output of \fBfindsmb\fR lists the following
|
||||
information for all machines that respond to the initial
|
||||
\fBnmblookup\fR for any name: IP address, NetBIOS name,
|
||||
Workgroup name, operating system, and SMB server version.
|
||||
.PP
|
||||
There will be a '+' in front of the workgroup name for
|
||||
machines that are local master browsers for that workgroup. There
|
||||
will be an '*' in front of the workgroup name for
|
||||
machines that are the domain master browser for that workgroup.
|
||||
Machines that are running Windows, Windows 95 or Windows 98 will
|
||||
not show any information about the operating system or server
|
||||
version.
|
||||
.PP
|
||||
The command with -r option
|
||||
must be run on a system without \fBnmbd\fR(8) running.
|
||||
If \fBnmbd\fR is running on the system, you will
|
||||
only get the IP address and the DNS name of the machine. To
|
||||
get proper responses from Windows 95 and Windows 98 machines,
|
||||
the command must be run as root and with -r
|
||||
option on a machine without \fBnmbd\fR running.
|
||||
.PP
|
||||
For example, running \fBfindsmb\fR
|
||||
without -r option set would yield output similar
|
||||
to the following
|
||||
findsmb \- list info about machines that respond to SMB name queries on a subnet
|
||||
.SH "SYNOPSIS"
|
||||
|
||||
.nf
|
||||
\fBfindsmb\fR [subnet broadcast address]
|
||||
.fi
|
||||
|
||||
.SH "DESCRIPTION"
|
||||
|
||||
.PP
|
||||
This perl script is part of the \fBSamba\fR(7) suite\&.
|
||||
|
||||
.PP
|
||||
\fBfindsmb\fR is a perl script that prints out several pieces of information about machines on a subnet that respond to SMB name query requests\&. It uses \fBnmblookup\fR(1) and \fBsmbclient\fR(1) to obtain this information\&.
|
||||
|
||||
.SH "OPTIONS"
|
||||
|
||||
.TP
|
||||
-r
|
||||
Controls whether \fBfindsmb\fR takes bugs in Windows95 into account when trying to find a Netbios name registered of the remote machine\&. This option is disabled by default because it is specific to Windows 95 and Windows 95 machines only\&. If set, \fBnmblookup\fR(1) will be called with \fB-B\fR option\&.
|
||||
|
||||
|
||||
.TP
|
||||
subnet broadcast address
|
||||
Without this option, \fBfindsmb \fR will probe the subnet of the machine where \fBfindsmb\fR(1) is run\&. This value is passed to \fBnmblookup\fR(1) as part of the \fB-B\fR option\&.
|
||||
|
||||
|
||||
.SH "EXAMPLES"
|
||||
|
||||
.PP
|
||||
The output of \fBfindsmb\fR lists the following information for all machines that respond to the initial\fBnmblookup\fR for any name: IP address, NetBIOS name, Workgroup name, operating system, and SMB server version\&.
|
||||
|
||||
.PP
|
||||
There will be a '+' in front of the workgroup name for machines that are local master browsers for that workgroup\&. There will be an '*' in front of the workgroup name for machines that are the domain master browser for that workgroup\&. Machines that are running Windows, Windows 95 or Windows 98 will not show any information about the operating system or server version\&.
|
||||
|
||||
.PP
|
||||
The command with \fB-r\fR option must be run on a system without \fBnmbd\fR(8)running\&. If \fBnmbd\fR is running on the system, you will only get the IP address and the DNS name of the machine\&. To get proper responses from Windows 95 and Windows 98 machines, the command must be run as root and with \fB-r\fR option on a machine without \fBnmbd\fR running\&.
|
||||
|
||||
.PP
|
||||
For example, running \fBfindsmb\fR without \fB-r\fR option set would yield output similar to the following
|
||||
.nf
|
||||
|
||||
IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION
|
||||
---------------------------------------------------------------------
|
||||
192.168.35.10 MINESET-TEST1 [DMVENGR]
|
||||
192.168.35.55 LINUXBOX *[MYGROUP] [Unix] [Samba 2.0.6]
|
||||
192.168.35.56 HERBNT2 [HERB-NT]
|
||||
192.168.35.63 GANDALF [MVENGR] [Unix] [Samba 2.0.5a for IRIX]
|
||||
192.168.35.65 SAUNA [WORKGROUP] [Unix] [Samba 1.9.18p10]
|
||||
192.168.35.71 FROGSTAR [ENGR] [Unix] [Samba 2.0.0 for IRIX]
|
||||
192.168.35.78 HERBDHCP1 +[HERB]
|
||||
192.168.35.88 SCNT2 +[MVENGR] [Windows NT 4.0] [NT LAN Manager 4.0]
|
||||
192.168.35.93 FROGSTAR-PC [MVENGR] [Windows 5.0] [Windows 2000 LAN Manager]
|
||||
192.168.35.97 HERBNT1 *[HERB-NT] [Windows NT 4.0] [NT LAN Manager 4.0]
|
||||
192\&.168\&.35\&.10 MINESET-TEST1 [DMVENGR]
|
||||
192\&.168\&.35\&.55 LINUXBOX *[MYGROUP] [Unix] [Samba 2\&.0\&.6]
|
||||
192\&.168\&.35\&.56 HERBNT2 [HERB-NT]
|
||||
192\&.168\&.35\&.63 GANDALF [MVENGR] [Unix] [Samba 2\&.0\&.5a for IRIX]
|
||||
192\&.168\&.35\&.65 SAUNA [WORKGROUP] [Unix] [Samba 1\&.9\&.18p10]
|
||||
192\&.168\&.35\&.71 FROGSTAR [ENGR] [Unix] [Samba 2\&.0\&.0 for IRIX]
|
||||
192\&.168\&.35\&.78 HERBDHCP1 +[HERB]
|
||||
192\&.168\&.35\&.88 SCNT2 +[MVENGR] [Windows NT 4\&.0] [NT LAN Manager 4\&.0]
|
||||
192\&.168\&.35\&.93 FROGSTAR-PC [MVENGR] [Windows 5\&.0] [Windows 2000 LAN Manager]
|
||||
192\&.168\&.35\&.97 HERBNT1 *[HERB-NT] [Windows NT 4\&.0] [NT LAN Manager 4\&.0]
|
||||
.fi
|
||||
|
||||
.SH "VERSION"
|
||||
|
||||
.PP
|
||||
This man page is correct for version 3.0 of
|
||||
the Samba suite.
|
||||
This man page is correct for version 3\&.0 of the Samba suite\&.
|
||||
|
||||
.SH "SEE ALSO"
|
||||
|
||||
.PP
|
||||
\fBnmbd\fR(8),
|
||||
\fBsmbclient\fR(1), and \fBnmblookup\fR(1)
|
||||
\fBnmbd\fR(8),\fBsmbclient\fR(1), and \fBnmblookup\fR(1)
|
||||
|
||||
.SH "AUTHOR"
|
||||
|
||||
.PP
|
||||
The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.
|
||||
The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
|
||||
|
||||
.PP
|
||||
The original Samba man pages were written by Karl Auer.
|
||||
The man page sources were converted to YODL format (another
|
||||
excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>)
|
||||
and updated for the Samba 2.0 release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook
|
||||
XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.
|
||||
The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
|
||||
|
||||
|
||||
@ -1,84 +1,92 @@
|
||||
.\" This manpage has been automatically generated by docbook2man
|
||||
.\" from a DocBook document. This tool can be found at:
|
||||
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
||||
.\" Please send any bug reports, improvements, comments, patches,
|
||||
.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
||||
.TH "LMHOSTS" "5" "19 april 2003" "" ""
|
||||
|
||||
.\"Generated by db2man.xsl. Don't modify this, modify the source.
|
||||
.de Sh \" Subsection
|
||||
.br
|
||||
.if t .Sp
|
||||
.ne 5
|
||||
.PP
|
||||
\fB\\$1\fR
|
||||
.PP
|
||||
..
|
||||
.de Sp \" Vertical space (when we can't use .PP)
|
||||
.if t .sp .5v
|
||||
.if n .sp
|
||||
..
|
||||
.de Ip \" List item
|
||||
.br
|
||||
.ie \\n(.$>=3 .ne \\$3
|
||||
.el .ne 3
|
||||
.IP "\\$1" \\$2
|
||||
..
|
||||
.TH "LMHOSTS" 5 "" "" ""
|
||||
.SH NAME
|
||||
lmhosts \- The Samba NetBIOS hosts file
|
||||
.SH SYNOPSIS
|
||||
.PP
|
||||
\fIlmhosts\fR is the \fBSamba\fR(7) NetBIOS name to IP address mapping file.
|
||||
.SH "DESCRIPTION"
|
||||
.PP
|
||||
This file is part of the \fBSamba\fR(7) suite.
|
||||
.PP
|
||||
\fIlmhosts\fR is the \fBSamba
|
||||
\fR NetBIOS name to IP address mapping file. It
|
||||
is very similar to the \fI/etc/hosts\fR file
|
||||
format, except that the hostname component must correspond
|
||||
to the NetBIOS naming format.
|
||||
.SH "FILE FORMAT"
|
||||
.PP
|
||||
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:
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
IP Address - in dotted decimal format.
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
NetBIOS Name - This name format is a
|
||||
maximum fifteen character host name, with an optional
|
||||
trailing '#' character followed by the NetBIOS name type
|
||||
as two hexadecimal digits.
|
||||
.SH "SYNOPSIS"
|
||||
|
||||
.PP
|
||||
\fIlmhosts\fR is the \fBSamba\fR(7) NetBIOS name to IP address mapping file\&.
|
||||
|
||||
.SH "DESCRIPTION"
|
||||
|
||||
.PP
|
||||
This file is part of the \fBSamba\fR(7) suite\&.
|
||||
|
||||
.PP
|
||||
\fIlmhosts\fR is the \fBSamba \fR NetBIOS name to IP address mapping file\&. It is very similar to the \fI/etc/hosts\fR file format, except that the hostname component must correspond to the NetBIOS naming format\&.
|
||||
|
||||
.SH "FILE FORMAT"
|
||||
|
||||
.PP
|
||||
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:
|
||||
|
||||
.TP 3
|
||||
\(bu
|
||||
IP Address - in dotted decimal format\&.
|
||||
|
||||
.TP
|
||||
\(bu
|
||||
NetBIOS Name - This name format is a maximum fifteen character host name, with an optional trailing '#' character followed by the NetBIOS name type as two hexadecimal digits\&.
|
||||
|
||||
|
||||
If the trailing '#' 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\&.
|
||||
|
||||
.LP
|
||||
|
||||
If the trailing '#' 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.
|
||||
.PP
|
||||
An example follows:
|
||||
|
||||
.nf
|
||||
|
||||
#
|
||||
# Sample Samba lmhosts file.
|
||||
# Sample Samba lmhosts file\&.
|
||||
#
|
||||
192.9.200.1 TESTPC
|
||||
192.9.200.20 NTSERVER#20
|
||||
192.9.200.21 SAMBASERVER
|
||||
|
||||
.fi
|
||||
192\&.9\&.200\&.1 TESTPC
|
||||
192\&.9\&.200\&.20 NTSERVER#20
|
||||
192\&.9\&.200\&.21 SAMBASERVER
|
||||
.fi
|
||||
|
||||
.PP
|
||||
Contains three IP to NetBIOS name mappings. The first
|
||||
and third will be returned for any queries for the names "TESTPC"
|
||||
and "SAMBASERVER" respectively, whatever the type component of
|
||||
the NetBIOS name requested.
|
||||
Contains three IP to NetBIOS name mappings\&. The first and third will be returned for any queries for the names "TESTPC" and "SAMBASERVER" respectively, whatever the type component of the NetBIOS name requested\&.
|
||||
|
||||
.PP
|
||||
The second mapping will be returned only when the "0x20" name
|
||||
type for a name "NTSERVER" is queried. Any other name type will not
|
||||
be resolved.
|
||||
The second mapping will be returned only when the "0x20" name type for a name "NTSERVER" is queried\&. Any other name type will not be resolved\&.
|
||||
|
||||
.PP
|
||||
The default location of the \fIlmhosts\fR file
|
||||
is in the same directory as the \fBsmb.conf\fR(5) file.
|
||||
The default location of the \fIlmhosts\fR file is in the same directory as the \fBsmb.conf\fR(5) file\&.
|
||||
|
||||
.SH "VERSION"
|
||||
|
||||
.PP
|
||||
This man page is correct for version 3.0 of the Samba suite.
|
||||
This man page is correct for version 3\&.0 of the Samba suite\&.
|
||||
|
||||
.SH "SEE ALSO"
|
||||
|
||||
.PP
|
||||
\fBsmbclient\fR(1), \fBsmb.conf\fR(5), and \fBsmbpasswd\fR(8)
|
||||
\fBsmbclient\fR(1), \fBsmb.conf\fR(5), and \fBsmbpasswd\fR(8)
|
||||
|
||||
.SH "AUTHOR"
|
||||
|
||||
.PP
|
||||
The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.
|
||||
The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
|
||||
|
||||
.PP
|
||||
The original Samba man pages were written by Karl Auer.
|
||||
The man page sources were converted to YODL format (another
|
||||
excellent piece of Open Source software, available at
|
||||
ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook
|
||||
XML 4.2 was done by Alexander Bokovoy.
|
||||
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 atftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 was done by Alexander Bokovoy\&.
|
||||
|
||||
|
||||
@ -1,441 +1,549 @@
|
||||
.\" This manpage has been automatically generated by docbook2man
|
||||
.\" from a DocBook document. This tool can be found at:
|
||||
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
||||
.\" Please send any bug reports, improvements, comments, patches,
|
||||
.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
||||
.TH "NET" "8" "19 april 2003" "" ""
|
||||
|
||||
.\"Generated by db2man.xsl. Don't modify this, modify the source.
|
||||
.de Sh \" Subsection
|
||||
.br
|
||||
.if t .Sp
|
||||
.ne 5
|
||||
.PP
|
||||
\fB\\$1\fR
|
||||
.PP
|
||||
..
|
||||
.de Sp \" Vertical space (when we can't use .PP)
|
||||
.if t .sp .5v
|
||||
.if n .sp
|
||||
..
|
||||
.de Ip \" List item
|
||||
.br
|
||||
.ie \\n(.$>=3 .ne \\$3
|
||||
.el .ne 3
|
||||
.IP "\\$1" \\$2
|
||||
..
|
||||
.TH "NET" 8 "" "" ""
|
||||
.SH NAME
|
||||
net \- Tool for administration of Samba and remote CIFS servers.
|
||||
.SH SYNOPSIS
|
||||
.SH "SYNOPSIS"
|
||||
|
||||
\fBnet\fR \fB<ads|rap|rpc>\fR [ \fB-h\fR ] [ \fB-w workgroup\fR ] [ \fB-W myworkgroup\fR ] [ \fB-U user\fR ] [ \fB-I ip-address\fR ] [ \fB-p port\fR ] [ \fB-n myname\fR ] [ \fB-s conffile\fR ] [ \fB-S server\fR ] [ \fB-l\fR ] [ \fB-P\fR ] [ \fB-D debuglevel\fR ]
|
||||
.nf
|
||||
\fBnet\fR {<ads|rap|rpc>} [-h] [-w workgroup] [-W myworkgroup] [-U user] [-I ip-address]
|
||||
[-p port] [-n myname] [-s conffile] [-S server] [-l] [-P] [-D debuglevel]
|
||||
|
||||
.fi
|
||||
|
||||
.SH "DESCRIPTION"
|
||||
|
||||
.PP
|
||||
This tool is part of the \fBSamba\fR(7) suite.
|
||||
This tool is part of the \fBSamba\fR(7) suite\&.
|
||||
|
||||
.PP
|
||||
The samba net utility is meant to work just like the net utility
|
||||
available for windows and DOS. The first argument should be used
|
||||
to specify the protocol to use when executing a certain command.
|
||||
ADS is used for ActiveDirectory, RAP is using for old (Win9x/NT3)
|
||||
clients and RPC can be used for NT4 and Windows 2000. If this
|
||||
argument is omitted, net will try to determine it automatically.
|
||||
Not all commands are available on all protocols.
|
||||
The samba net utility is meant to work just like the net utility available for windows and DOS\&. The first argument should be used to specify the protocol to use when executing a certain command\&. ADS is used for ActiveDirectory, RAP is using for old (Win9x/NT3) clients and RPC can be used for NT4 and Windows 2000\&. If this argument is omitted, net will try to determine it automatically\&. Not all commands are available on all protocols\&.
|
||||
|
||||
.SH "OPTIONS"
|
||||
|
||||
.TP
|
||||
\fB-h|--help\fR
|
||||
Print a summary of command line options.
|
||||
-h|--help
|
||||
Print a summary of command line options\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-w target-workgroup\fR
|
||||
Sets target workgroup or domain. You have to specify
|
||||
either this option or the IP address or the name of a server.
|
||||
-w target-workgroup
|
||||
Sets target workgroup or domain\&. You have to specify either this option or the IP address or the name of a server\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-W workgroup\fR
|
||||
-W workgroup
|
||||
Sets client workgroup or domain
|
||||
|
||||
|
||||
.TP
|
||||
\fB-U user\fR
|
||||
-U user
|
||||
User name to use
|
||||
.TP
|
||||
\fB-I ip-address\fR
|
||||
IP address of target server to use. You have to
|
||||
specify either this option or a target workgroup or
|
||||
a target server.
|
||||
.TP
|
||||
\fB-p port\fR
|
||||
Port on the target server to connect to (usually 139 or 445).
|
||||
Defaults to trying 445 first, then 139.
|
||||
.TP
|
||||
\fB-n <primary NetBIOS name>\fR
|
||||
This option allows you to override
|
||||
the NetBIOS name that Samba uses for itself. This is identical
|
||||
to setting the \fINetBIOS
|
||||
name\fR parameter in the \fBsmb.conf\fR(5) file. However, a command
|
||||
line setting will take precedence over settings in
|
||||
\fBsmb.conf\fR(5).
|
||||
.TP
|
||||
\fB-s <configuration file>\fR
|
||||
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 \fIsmb.conf(5)\fR for more information.
|
||||
The default configuration file name is determined at
|
||||
compile time.
|
||||
.TP
|
||||
\fB-S server\fR
|
||||
Name of target server. You should specify either
|
||||
this option or a target workgroup or a target IP address.
|
||||
.TP
|
||||
\fB-l\fR
|
||||
When listing data, give more information on each item.
|
||||
.TP
|
||||
\fB-P\fR
|
||||
Make queries to the external server using the machine account of the local server.
|
||||
.TP
|
||||
\fB-d|--debug=debuglevel\fR
|
||||
\fIdebuglevel\fR is an integer
|
||||
from 0 to 10. The default value if this parameter is
|
||||
not specified is zero.
|
||||
|
||||
The higher this value, the more detail will be
|
||||
logged to the log files about the activities of the
|
||||
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.
|
||||
|
||||
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.
|
||||
.TP
|
||||
-I ip-address
|
||||
IP address of target server to use\&. You have to specify either this option or a target workgroup or a target server\&.
|
||||
|
||||
|
||||
.TP
|
||||
-p port
|
||||
Port on the target server to connect to (usually 139 or 445)\&. Defaults to trying 445 first, then 139\&.
|
||||
|
||||
|
||||
.TP
|
||||
-n <primary NetBIOS name>
|
||||
This option allows you to override the NetBIOS name that Samba uses for itself\&. This is identical to setting the \fINetBIOS name\fR parameter in the \fBsmb.conf\fR(5) file\&. However, a command line setting will take precedence over settings in \fBsmb.conf\fR(5)\&.
|
||||
|
||||
|
||||
.TP
|
||||
-s <configuration file>
|
||||
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 \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
|
||||
|
||||
|
||||
.TP
|
||||
-S server
|
||||
Name of target server\&. You should specify either this option or a target workgroup or a target IP address\&.
|
||||
|
||||
|
||||
.TP
|
||||
-l
|
||||
When listing data, give more information on each item\&.
|
||||
|
||||
|
||||
.TP
|
||||
-P
|
||||
Make queries to the external server using the machine account of the local server\&.
|
||||
|
||||
|
||||
.TP
|
||||
-d|--debug=debuglevel
|
||||
\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
|
||||
|
||||
|
||||
The higher this value, the more detail will be logged to the log files about the activities of the 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\&.
|
||||
|
||||
|
||||
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\&.
|
||||
|
||||
|
||||
Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&.
|
||||
|
||||
|
||||
Note that specifying this parameter here will
|
||||
override the log
|
||||
level file.
|
||||
.SH "COMMANDS"
|
||||
|
||||
.SS "TIME"
|
||||
|
||||
.PP
|
||||
The \fBNET TIME\fR command allows you to view the time on a remote server
|
||||
or synchronise the time on the local server with the time on the remote server.
|
||||
.SS "TIME"
|
||||
The \fBNET TIME\fR command allows you to view the time on a remote server or synchronise the time on the local server with the time on the remote server\&.
|
||||
|
||||
.PP
|
||||
Without any options, the \fBNET TIME\fR command
|
||||
displays the time on the remote server.
|
||||
.SS "TIME SYSTEM"
|
||||
Without any options, the \fBNET TIME\fR command displays the time on the remote server\&.
|
||||
|
||||
.PP
|
||||
Displays the time on the remote server in a format ready for \fB/bin/date\fR
|
||||
.SS "TIME SET"
|
||||
|
||||
.PP
|
||||
Tries to set the date and time of the local server to that on
|
||||
the remote server using \fB/bin/date\fR.
|
||||
.SS "TIME ZONE"
|
||||
Tries to set the date and time of the local server to that on the remote server using \fB/bin/date\fR\&.
|
||||
|
||||
.PP
|
||||
Displays the timezone in hours from GMT on the remote computer.
|
||||
.SS "[RPC|ADS] JOIN [TYPE] [-U USERNAME[%PASSWORD]] [OPTIONS]"
|
||||
Displays the timezone in hours from GMT on the remote computer\&.
|
||||
|
||||
.SS "[RPC|ADS] JOIN [TYPE] [-U username[%password]] [options]"
|
||||
|
||||
.PP
|
||||
Join a domain. If the account already exists on the server, and
|
||||
[TYPE] is MEMBER, the machine will attempt to join automatically.
|
||||
(Assuming that the machine has been created in server manager)
|
||||
Otherwise, a password will be prompted for, and a new account may
|
||||
be created.
|
||||
Join a domain\&. If the account already exists on the server, and [TYPE] is MEMBER, the machine will attempt to join automatically\&. (Assuming that the machine has been created in server manager) Otherwise, a password will be prompted for, and a new account may be created\&.
|
||||
|
||||
.PP
|
||||
[TYPE] may be PDC, BDC or MEMBER to specify the type of server
|
||||
joining the domain.
|
||||
.SS "[RPC] OLDJOIN [OPTIONS]"
|
||||
[TYPE] may be PDC, BDC or MEMBER to specify the type of server joining the domain\&.
|
||||
|
||||
.SS "[RPC] OLDJOIN [options]"
|
||||
|
||||
.PP
|
||||
Join a domain. Use the OLDJOIN option to join the domain
|
||||
using the old style of domain joining - you need to create a trust
|
||||
account in server manager first.
|
||||
Join a domain\&. Use the OLDJOIN option to join the domain using the old style of domain joining - you need to create a trust account in server manager first\&.
|
||||
|
||||
.SS "[RPC|ADS] USER"
|
||||
.SS "[RPC|ADS] USER DELETE TARGET"
|
||||
|
||||
.PP
|
||||
Delete specified user
|
||||
.SS "[RPC|ADS] USER LIST"
|
||||
|
||||
.PP
|
||||
List all users
|
||||
.SS "[RPC|ADS] USER INFO TARGET"
|
||||
|
||||
.PP
|
||||
List the domain groups of a the specified user.
|
||||
.SS "[RPC|ADS] USER ADD NAME [PASSWORD] [-F USER FLAGS] [-C COMMENT]"
|
||||
List the domain groups of a the specified user\&.
|
||||
|
||||
.PP
|
||||
Add specified user.
|
||||
Add specified user\&.
|
||||
|
||||
.SS "[RPC|ADS] GROUP"
|
||||
.SS "[RPC|ADS] GROUP [MISC OPTIONS] [TARGETS]"
|
||||
|
||||
.PP
|
||||
List user groups.
|
||||
.SS "[RPC|ADS] GROUP DELETE NAME [MISC. OPTIONS]"
|
||||
List user groups\&.
|
||||
|
||||
.PP
|
||||
Delete specified group.
|
||||
.SS "[RPC|ADS] GROUP ADD NAME [-C COMMENT]"
|
||||
Delete specified group\&.
|
||||
|
||||
.PP
|
||||
Create specified group.
|
||||
Create specified group\&.
|
||||
|
||||
.SS "[RAP|RPC] SHARE"
|
||||
.SS "[RAP|RPC] SHARE [MISC. OPTIONS] [TARGETS]"
|
||||
|
||||
.PP
|
||||
Enumerates all exported resources (network shares) on target server.
|
||||
.SS "[RAP|RPC] SHARE ADD NAME=SERVERPATH [-C COMMENT] [-M MAXUSERS] [TARGETS]"
|
||||
Enumerates all exported resources (network shares) on target server\&.
|
||||
|
||||
.PP
|
||||
Adds a share from a server (makes the export active). Maxusers
|
||||
specifies the number of users that can be connected to the
|
||||
share simultaneously.
|
||||
.SS "SHARE DELETE SHARENAM"
|
||||
Adds a share from a server (makes the export active)\&. Maxusers specifies the number of users that can be connected to the share simultaneously\&.
|
||||
|
||||
.PP
|
||||
Delete specified share.
|
||||
.SS "[RPC|RAP] FILE"
|
||||
Delete specified share\&.
|
||||
|
||||
.SS "[RPC|RAP] FILE"
|
||||
|
||||
.PP
|
||||
List all open files on remote server.
|
||||
.SS "[RPC|RAP] FILE CLOSE FILEID"
|
||||
List all open files on remote server\&.
|
||||
|
||||
.PP
|
||||
Close file with specified \fIfileid\fR on
|
||||
remote server.
|
||||
.SS "[RPC|RAP] FILE INFO FILEID"
|
||||
Close file with specified \fIfileid\fR on remote server\&.
|
||||
|
||||
.PP
|
||||
Print information on specified \fIfileid\fR.
|
||||
Currently listed are: file-id, username, locks, path, permissions.
|
||||
.SS "[RAP|RPC] FILE USER"
|
||||
.sp
|
||||
Print information on specified \fIfileid\fR\&. Currently listed are: file-id, username, locks, path, permissions\&.
|
||||
|
||||
.RS
|
||||
.B "Note:"
|
||||
Currently NOT implemented.
|
||||
.Sh "Note"
|
||||
|
||||
.PP
|
||||
Currently NOT implemented\&.
|
||||
|
||||
.RE
|
||||
|
||||
.SS "SESSION"
|
||||
.SS "RAP SESSION"
|
||||
|
||||
.PP
|
||||
Without any other options, SESSION enumerates all active SMB/CIFS
|
||||
sessions on the target server.
|
||||
.SS "RAP SESSION DELETE|CLOSE CLIENT_NAME"
|
||||
Without any other options, SESSION enumerates all active SMB/CIFS sessions on the target server\&.
|
||||
|
||||
.PP
|
||||
Close the specified sessions.
|
||||
.SS "RAP SESSION INFO CLIENT_NAME"
|
||||
Close the specified sessions\&.
|
||||
|
||||
.PP
|
||||
Give a list with all the open files in specified session.
|
||||
Give a list with all the open files in specified session\&.
|
||||
|
||||
.SS "RAP SERVER DOMAIN"
|
||||
|
||||
.PP
|
||||
List all servers in specified domain or workgroup. Defaults
|
||||
to local domain.
|
||||
List all servers in specified domain or workgroup\&. Defaults to local domain\&.
|
||||
|
||||
.SS "RAP DOMAIN"
|
||||
|
||||
.PP
|
||||
Lists all domains and workgroups visible on the
|
||||
current network.
|
||||
Lists all domains and workgroups visible on the current network\&.
|
||||
|
||||
.SS "RAP PRINTQ"
|
||||
.SS "RAP PRINTQ LIST QUEUE_NAME"
|
||||
|
||||
.PP
|
||||
Lists the specified print queue and print jobs on the server.
|
||||
If the \fIQUEUE_NAME\fR is omitted, all
|
||||
queues are listed.
|
||||
.SS "RAP PRINTQ DELETE JOBID"
|
||||
Lists the specified print queue and print jobs on the server\&. If the \fIQUEUE_NAME\fR is omitted, all queues are listed\&.
|
||||
|
||||
.PP
|
||||
Delete job with specified id.
|
||||
.SS "RAP VALIDATE USER [PASSWORD]"
|
||||
Delete job with specified id\&.
|
||||
|
||||
.SS "RAP VALIDATE user [password]"
|
||||
|
||||
.PP
|
||||
Validate whether the specified user can log in to the
|
||||
remote server. If the password is not specified on the commandline, it
|
||||
will be prompted.
|
||||
.sp
|
||||
Validate whether the specified user can log in to the remote server\&. If the password is not specified on the commandline, it will be prompted\&.
|
||||
|
||||
.RS
|
||||
.B "Note:"
|
||||
Currently NOT implemented.
|
||||
.Sh "Note"
|
||||
|
||||
.PP
|
||||
Currently NOT implemented\&.
|
||||
|
||||
.RE
|
||||
|
||||
.SS "RAP GROUPMEMBER"
|
||||
.SS "RAP GROUPMEMBER LIST GROUP"
|
||||
|
||||
.PP
|
||||
List all members of the specified group.
|
||||
.SS "RAP GROUPMEMBER DELETE GROUP USER"
|
||||
List all members of the specified group\&.
|
||||
|
||||
.PP
|
||||
Delete member from group.
|
||||
.SS "RAP GROUPMEMBER ADD GROUP USER"
|
||||
Delete member from group\&.
|
||||
|
||||
.PP
|
||||
Add member to group.
|
||||
.SS "RAP ADMIN COMMAND"
|
||||
Add member to group\&.
|
||||
|
||||
.SS "RAP ADMIN command"
|
||||
|
||||
.PP
|
||||
Execute the specified \fIcommand\fR on
|
||||
the remote server. Only works with OS/2 servers.
|
||||
.sp
|
||||
Execute the specified \fIcommand\fR on the remote server\&. Only works with OS/2 servers\&.
|
||||
|
||||
.RS
|
||||
.B "Note:"
|
||||
Currently NOT implemented.
|
||||
.Sh "Note"
|
||||
|
||||
.PP
|
||||
Currently NOT implemented\&.
|
||||
|
||||
.RE
|
||||
|
||||
.SS "RAP SERVICE"
|
||||
.SS "RAP SERVICE START NAME [ARGUMENTS...]"
|
||||
|
||||
.PP
|
||||
Start the specified service on the remote server. Not implemented yet.
|
||||
.sp
|
||||
Start the specified service on the remote server\&. Not implemented yet\&.
|
||||
|
||||
.RS
|
||||
.B "Note:"
|
||||
Currently NOT implemented.
|
||||
.RE
|
||||
.SS "RAP SERVICE STOP"
|
||||
.Sh "Note"
|
||||
|
||||
.PP
|
||||
Stop the specified service on the remote server.
|
||||
.sp
|
||||
.RS
|
||||
.B "Note:"
|
||||
Currently NOT implemented.
|
||||
Currently NOT implemented\&.
|
||||
|
||||
.RE
|
||||
|
||||
.PP
|
||||
Stop the specified service on the remote server\&.
|
||||
|
||||
.RS
|
||||
.Sh "Note"
|
||||
|
||||
.PP
|
||||
Currently NOT implemented\&.
|
||||
|
||||
.RE
|
||||
|
||||
.SS "RAP PASSWORD USER OLDPASS NEWPASS"
|
||||
|
||||
.PP
|
||||
Change password of \fIUSER\fR from \fIOLDPASS\fR to \fINEWPASS\fR.
|
||||
Change password of \fIUSER\fR from \fIOLDPASS\fR to \fINEWPASS\fR\&.
|
||||
|
||||
.SS "LOOKUP"
|
||||
.SS "LOOKUP HOST HOSTNAME [TYPE]"
|
||||
|
||||
.PP
|
||||
Lookup the IP address of the given host with the specified type (netbios suffix).
|
||||
The type defaults to 0x20 (workstation).
|
||||
.SS "LOOKUP LDAP [DOMAIN"
|
||||
Lookup the IP address of the given host with the specified type (netbios suffix)\&. The type defaults to 0x20 (workstation)\&.
|
||||
|
||||
.PP
|
||||
Give IP address of LDAP server of specified \fIDOMAIN\fR. Defaults to local domain.
|
||||
.SS "LOOKUP KDC [REALM]"
|
||||
Give IP address of LDAP server of specified \fIDOMAIN\fR\&. Defaults to local domain\&.
|
||||
|
||||
.PP
|
||||
Give IP address of KDC for the specified \fIREALM\fR.
|
||||
Defaults to local realm.
|
||||
.SS "LOOKUP DC [DOMAIN]"
|
||||
Give IP address of KDC for the specified \fIREALM\fR\&. Defaults to local realm\&.
|
||||
|
||||
.PP
|
||||
Give IP's of Domain Controllers for specified \fIDOMAIN\fR. Defaults to local domain.
|
||||
.SS "LOOKUP MASTER DOMAIN"
|
||||
Give IP's of Domain Controllers for specified \fI DOMAIN\fR\&. Defaults to local domain\&.
|
||||
|
||||
.PP
|
||||
Give IP of master browser for specified \fIDOMAIN\fR
|
||||
or workgroup. Defaults to local domain.
|
||||
Give IP of master browser for specified \fIDOMAIN\fR or workgroup\&. Defaults to local domain\&.
|
||||
|
||||
.SS "CACHE"
|
||||
.PP
|
||||
Samba uses a general caching interface called 'gencache'. It
|
||||
can be controlled using 'NET CACHE'.
|
||||
.PP
|
||||
All the timeout parameters support the suffixes:
|
||||
|
||||
s - Seconds
|
||||
.PP
|
||||
Samba uses a general caching interface called 'gencache'\&. It can be controlled using 'NET CACHE'\&.
|
||||
|
||||
m - Minutes
|
||||
.PP
|
||||
All the timeout parameters support the suffixes: s - Secondsm - Minutesh - Hoursd - Daysw - Weeks
|
||||
|
||||
h - Hours
|
||||
.PP
|
||||
Add specified key+data to the cache with the given timeout\&.
|
||||
|
||||
d - Days
|
||||
.PP
|
||||
Delete key from the cache\&.
|
||||
|
||||
w - Weeks
|
||||
.SS "CACHE ADD KEY DATA TIME-OUT"
|
||||
.PP
|
||||
Add specified key+data to the cache with the given timeout.
|
||||
.SS "CACHE DEL KEY"
|
||||
Update data of existing cache entry\&.
|
||||
|
||||
.PP
|
||||
Delete key from the cache.
|
||||
.SS "CACHE SET KEY DATA TIME-OUT"
|
||||
Search for the specified pattern in the cache data\&.
|
||||
|
||||
.PP
|
||||
Update data of existing cache entry.
|
||||
.SS "CACHE SEARCH PATTERN"
|
||||
List all current items in the cache\&.
|
||||
|
||||
.PP
|
||||
Search for the specified pattern in the cache data.
|
||||
.SS "CACHE LIST"
|
||||
.PP
|
||||
List all current items in the cache.
|
||||
.SS "CACHE FLUSH"
|
||||
.PP
|
||||
Remove all the current items from the cache.
|
||||
Remove all the current items from the cache\&.
|
||||
|
||||
.SS "GETLOCALSID [DOMAIN]"
|
||||
|
||||
.PP
|
||||
Print the SID of the specified domain, or if the parameter is
|
||||
omitted, the SID of the domain the local server is in.
|
||||
.SS "SETLOCALSID S-1-5-21-X-Y-Z"
|
||||
Print the SID of the specified domain, or if the parameter is omitted, the SID of the domain the local server is in\&.
|
||||
|
||||
.SS "SETLOCALSID S-1-5-21-x-y-z"
|
||||
|
||||
.PP
|
||||
Sets domain sid for the local server to the specified SID.
|
||||
Sets domain sid for the local server to the specified SID\&.
|
||||
|
||||
.SS "GROUPMAP"
|
||||
|
||||
.PP
|
||||
Manage the mappings between Windows group SIDs and UNIX groups\&. Parameters take the for "parameter=value"\&. Common options include:
|
||||
|
||||
.TP 3
|
||||
\(bu
|
||||
unixgroup - Name of the UNIX group
|
||||
|
||||
.TP
|
||||
\(bu
|
||||
ntgroup - Name of the Windows NT group (must be resolvable to a SID
|
||||
|
||||
.TP
|
||||
\(bu
|
||||
rid - Unsigned 32-bit integer
|
||||
|
||||
.TP
|
||||
\(bu
|
||||
sid - Full SID in the form of "S-1-\&.\&.\&."
|
||||
|
||||
.TP
|
||||
\(bu
|
||||
type - Type of the group; either 'domain', 'local', or 'builtin'
|
||||
|
||||
.TP
|
||||
\(bu
|
||||
comment - Freeform text description of the group
|
||||
|
||||
.LP
|
||||
|
||||
.PP
|
||||
Add a new group mapping entry
|
||||
|
||||
.PP
|
||||
net groupmap add {rid=int|sid=string} unixgroup=string [type={domain|local|builtin}] [ntgroup=string] [comment=string]
|
||||
|
||||
.PP
|
||||
Delete a group mapping entry
|
||||
|
||||
.PP
|
||||
net groupmap delete {ntgroup=string|sid=SID}
|
||||
|
||||
.PP
|
||||
Update en existing group entry
|
||||
|
||||
.PP
|
||||
net groupmap modify {ntgroup=string|sid=SID} [unixgroup=string] [comment=string] [type={domain|local}
|
||||
|
||||
.PP
|
||||
List existing group mapping entries
|
||||
|
||||
.PP
|
||||
net groupmap list [verbose] [ntgroup=string] [sid=SID]
|
||||
|
||||
.SS "MAXRID"
|
||||
|
||||
.PP
|
||||
Prints out the highest RID currently in use on the local
|
||||
server (by the active 'passdb backend').
|
||||
Prints out the highest RID currently in use on the local server (by the active 'passdb backend')\&.
|
||||
|
||||
.SS "RPC INFO"
|
||||
|
||||
.PP
|
||||
Print information about the domain of the remote server,
|
||||
such as domain name, domain sid and number of users and groups.
|
||||
Print information about the domain of the remote server, such as domain name, domain sid and number of users and groups\&.
|
||||
|
||||
.SS "[RPC|ADS] TESTJOIN"
|
||||
|
||||
.PP
|
||||
Check whether participation in a domain is still valid.
|
||||
Check whether participation in a domain is still valid\&.
|
||||
|
||||
.SS "[RPC|ADS] CHANGETRUSTPW"
|
||||
|
||||
.PP
|
||||
Force change of domain trust password.
|
||||
Force change of domain trust password\&.
|
||||
|
||||
.SS "RPC TRUSTDOM"
|
||||
.SS "RPC TRUSTDOM ADD DOMAIN"
|
||||
|
||||
.PP
|
||||
Add a interdomain trust account for
|
||||
\fIDOMAIN\fR to the remote server.
|
||||
.SS "RPC TRUSTDOM DEL DOMAIM"
|
||||
Add a interdomain trust account for \fIDOMAIN\fR to the remote server\&.
|
||||
|
||||
.PP
|
||||
Remove interdomain trust account for
|
||||
\fIDOMAIN\fR from the remote server.
|
||||
.sp
|
||||
Remove interdomain trust account for \fIDOMAIN\fR from the remote server\&.
|
||||
|
||||
.RS
|
||||
.B "Note:"
|
||||
Currently NOT implemented.
|
||||
.RE
|
||||
.SS "RPC TRUSTDOM ESTABLISH DOMAIN"
|
||||
.Sh "Note"
|
||||
|
||||
.PP
|
||||
Establish a trust relationship to a trusting domain.
|
||||
Interdomain account must already be created on the remote PDC.
|
||||
.SS "RPC TRUSTDOM REVOKE DOMAIN"
|
||||
Currently NOT implemented\&.
|
||||
|
||||
.RE
|
||||
|
||||
.PP
|
||||
Establish a trust relationship to a trusting domain\&. Interdomain account must already be created on the remote PDC\&.
|
||||
|
||||
.PP
|
||||
Abandon relationship to trusted domain
|
||||
.SS "RPC TRUSTDOM LIST"
|
||||
|
||||
.PP
|
||||
List all current interdomain trust relationships.
|
||||
List all current interdomain trust relationships\&.
|
||||
|
||||
.SS "RPC ABORTSHUTDOWN"
|
||||
|
||||
.PP
|
||||
Abort the shutdown of a remote server.
|
||||
.SS "SHUTDOWN [-T TIMEOUT] [-R] [-F] [-C MESSAGE]"
|
||||
Abort the shutdown of a remote server\&.
|
||||
|
||||
.SS "SHUTDOWN [-t timeout] [-r] [-f] [-C message]"
|
||||
|
||||
.PP
|
||||
Shut down the remote server.
|
||||
Shut down the remote server\&.
|
||||
|
||||
.TP
|
||||
\fB-r\fR
|
||||
Reboot after shutdown.
|
||||
-r
|
||||
Reboot after shutdown\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-f\fR
|
||||
Force shutting down all applications.
|
||||
-f
|
||||
Force shutting down all applications\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-t timeout\fR
|
||||
Timeout before system will be shut down. An interactive
|
||||
user of the system can use this time to cancel the shutdown.
|
||||
-t timeout
|
||||
Timeout before system will be shut down\&. An interactive user of the system can use this time to cancel the shutdown\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-C message\fR
|
||||
Display the specified message on the screen to
|
||||
announce the shutdown.
|
||||
-C message
|
||||
Display the specified message on the screen to announce the shutdown\&.
|
||||
|
||||
|
||||
.SS "SAMDUMP"
|
||||
|
||||
.PP
|
||||
Print out sam database of remote server. You need
|
||||
to run this on either a BDC.
|
||||
Print out sam database of remote server\&. You need to run this on either a BDC\&.
|
||||
|
||||
.SS "VAMPIRE"
|
||||
|
||||
.PP
|
||||
Export users, aliases and groups from remote server to
|
||||
local server. Can only be run an a BDC.
|
||||
Export users, aliases and groups from remote server to local server\&. Can only be run an a BDC\&.
|
||||
|
||||
.SS "GETSID"
|
||||
|
||||
.PP
|
||||
Fetch domain SID and store it in the local \fIsecrets.tdb\fR.
|
||||
Fetch domain SID and store it in the local \fIsecrets\&.tdb\fR\&.
|
||||
|
||||
.SS "ADS LEAVE"
|
||||
|
||||
.PP
|
||||
Make the remote host leave the domain it is part of.
|
||||
Make the remote host leave the domain it is part of\&.
|
||||
|
||||
.SS "ADS STATUS"
|
||||
|
||||
.PP
|
||||
Print out status of machine account of the local machine in ADS.
|
||||
Prints out quite some debug info. Aimed at developers, regular
|
||||
users should use \fBNET ADS TESTJOIN\fR.
|
||||
Print out status of machine account of the local machine in ADS\&. Prints out quite some debug info\&. Aimed at developers, regular users should use \fBNET ADS TESTJOIN\fR\&.
|
||||
|
||||
.SS "ADS PRINTER"
|
||||
.SS "ADS PRINTER INFO [PRINTER] [SERVER]"
|
||||
|
||||
.PP
|
||||
Lookup info for \fIPRINTER\fR on \fISERVER\fR. The printer name defaults to "*", the
|
||||
server name defaults to the local host.
|
||||
.SS "ADS PRINTER PUBLISH PRINTER"
|
||||
Lookup info for \fIPRINTER\fR on \fISERVER\fR\&. The printer name defaults to "*", the server name defaults to the local host\&.
|
||||
|
||||
.PP
|
||||
Publish specified printer using ADS.
|
||||
.SS "ADS PRINTER REMOVE PRINTER"
|
||||
Publish specified printer using ADS\&.
|
||||
|
||||
.PP
|
||||
Remove specified printer from ADS directory.
|
||||
Remove specified printer from ADS directory\&.
|
||||
|
||||
.SS "ADS SEARCH EXPRESSION ATTRIBUTES..."
|
||||
|
||||
.PP
|
||||
Perform a raw LDAP search on a ADS server and dump the results. The
|
||||
expression is a standard LDAP search expression, and the
|
||||
attributes are a list of LDAP fields to show in the results.
|
||||
Perform a raw LDAP search on a ADS server and dump the results\&. The expression is a standard LDAP search expression, and the attributes are a list of LDAP fields to show in the results\&.
|
||||
|
||||
.PP
|
||||
Example: \fBnet ads search '(objectCategory=group)' sAMAccountName\fR
|
||||
.SS "ADS DN DN (ATTRIBUTES)"
|
||||
Example: \fBnet ads search '(objectCategory=group)' sAMAccountName\fR
|
||||
|
||||
.SS "ADS DN DN (attributes)"
|
||||
|
||||
.PP
|
||||
Perform a raw LDAP search on a ADS server and dump the results. The
|
||||
DN standard LDAP DN, and the attributes are a list of LDAP fields
|
||||
to show in the result.
|
||||
Perform a raw LDAP search on a ADS server and dump the results\&. The DN standard LDAP DN, and the attributes are a list of LDAP fields to show in the result\&.
|
||||
|
||||
.PP
|
||||
Example: \fBnet ads dn 'CN=administrator,CN=Users,DC=my,DC=domain' SAMAccountName\fR
|
||||
|
||||
.SS "WORKGROUP"
|
||||
|
||||
.PP
|
||||
Print out workgroup name for specified kerberos realm.
|
||||
Print out workgroup name for specified kerberos realm\&.
|
||||
|
||||
.SS "HELP [COMMAND]"
|
||||
|
||||
.PP
|
||||
Gives usage information for the specified command.
|
||||
Gives usage information for the specified command\&.
|
||||
|
||||
.SH "VERSION"
|
||||
|
||||
.PP
|
||||
This man page is incomplete for version 3.0 of the Samba
|
||||
suite.
|
||||
This man page is complete for version 3\&.0 of the Samba suite\&.
|
||||
|
||||
.SH "AUTHOR"
|
||||
|
||||
.PP
|
||||
The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.
|
||||
The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
|
||||
|
||||
.PP
|
||||
The net manpage was written by Jelmer Vernooij.
|
||||
The net manpage was written by Jelmer Vernooij\&.
|
||||
|
||||
|
||||
@ -1,245 +1,178 @@
|
||||
.\" This manpage has been automatically generated by docbook2man
|
||||
.\" from a DocBook document. This tool can be found at:
|
||||
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
||||
.\" Please send any bug reports, improvements, comments, patches,
|
||||
.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
||||
.TH "NMBD" "8" "19 april 2003" "" ""
|
||||
|
||||
.\"Generated by db2man.xsl. Don't modify this, modify the source.
|
||||
.de Sh \" Subsection
|
||||
.br
|
||||
.if t .Sp
|
||||
.ne 5
|
||||
.PP
|
||||
\fB\\$1\fR
|
||||
.PP
|
||||
..
|
||||
.de Sp \" Vertical space (when we can't use .PP)
|
||||
.if t .sp .5v
|
||||
.if n .sp
|
||||
..
|
||||
.de Ip \" List item
|
||||
.br
|
||||
.ie \\n(.$>=3 .ne \\$3
|
||||
.el .ne 3
|
||||
.IP "\\$1" \\$2
|
||||
..
|
||||
.TH "NMBD" 8 "" "" ""
|
||||
.SH NAME
|
||||
nmbd \- NetBIOS name server to provide NetBIOS over IP naming services to clients
|
||||
.SH SYNOPSIS
|
||||
nmbd \- NetBIOS name server to provide NetBIOS over IP naming services to clients
|
||||
.SH "SYNOPSIS"
|
||||
|
||||
\fBnmbd\fR [ \fB-D\fR ] [ \fB-F\fR ] [ \fB-S\fR ] [ \fB-a\fR ] [ \fB-i\fR ] [ \fB-o\fR ] [ \fB-h\fR ] [ \fB-V\fR ] [ \fB-d <debug level>\fR ] [ \fB-H <lmhosts file>\fR ] [ \fB-l <log directory>\fR ] [ \fB-n <primary netbios name>\fR ] [ \fB-p <port number>\fR ] [ \fB-s <configuration file>\fR ]
|
||||
.nf
|
||||
\fBnmbd\fR [-D] [-F] [-S] [-a] [-i] [-o] [-h] [-V] [-d <debug level>] [-H <lmhosts file>] [-l <log directory>] [-n <primary netbios name>] [-p <port number>] [-s <configuration file>]
|
||||
|
||||
.fi
|
||||
|
||||
.SH "DESCRIPTION"
|
||||
|
||||
.PP
|
||||
This program is part of the \fBSamba\fR(7) suite.
|
||||
This program is part of the \fBSamba\fR(7) suite\&.
|
||||
|
||||
.PP
|
||||
\fBnmbd\fR is a server that understands
|
||||
and can reply to NetBIOS over IP name service requests, like
|
||||
those produced by SMB/CIFS clients such as Windows 95/98/ME,
|
||||
Windows NT, Windows 2000, Windows XP and LanManager clients. It also
|
||||
participates in the browsing protocols which make up the
|
||||
Windows "Network Neighborhood" view.
|
||||
\fBnmbd\fR is a server that understands and can reply to NetBIOS over IP name service requests, like those produced by SMB/CIFS clients such as Windows 95/98/ME, Windows NT, Windows 2000, Windows XP and LanManager clients\&. It also participates in the browsing protocols which make up the Windows "Network Neighborhood" view\&.
|
||||
|
||||
.PP
|
||||
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.
|
||||
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\&.
|
||||
|
||||
.PP
|
||||
Amongst other services, \fBnmbd\fR 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 can be overridden with the \fB-n\fR
|
||||
option (see OPTIONS below). Thus \fBnmbd\fR will
|
||||
reply to broadcast queries for its own name(s). Additional
|
||||
names for \fBnmbd\fR to respond on can be set
|
||||
via parameters in the \fBsmb.conf\fR(5) configuration file.
|
||||
Amongst other services, \fBnmbd\fR 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 can be overridden with the \fB-n\fR option (see OPTIONS below)\&. Thus \fBnmbd\fR will reply to broadcast queries for its own name(s)\&. Additional names for \fBnmbd\fR to respond on can be set via parameters in the \fBsmb.conf\fR(5) configuration file\&.
|
||||
|
||||
.PP
|
||||
\fBnmbd\fR 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.
|
||||
\fBnmbd\fR 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\&.
|
||||
|
||||
.PP
|
||||
In addition, \fBnmbd\fR can act as a WINS
|
||||
proxy, relaying broadcast queries from clients that do
|
||||
not understand how to talk the WINS protocol to a WINS
|
||||
server.
|
||||
In addition, \fBnmbd\fR can act as a WINS proxy, relaying broadcast queries from clients that do not understand how to talk the WINS protocol to a WINS server\&.
|
||||
|
||||
.SH "OPTIONS"
|
||||
.TP
|
||||
\fB-D\fR
|
||||
If specified, this parameter causes
|
||||
\fBnmbd\fR to operate as a daemon. That is,
|
||||
it detaches itself and runs in the background, fielding
|
||||
requests on the appropriate port. By default, \fBnmbd\fR
|
||||
will operate as a daemon if launched from a command shell.
|
||||
nmbd can also be operated from the \fBinetd\fR
|
||||
meta-daemon, although this is not recommended.
|
||||
.TP
|
||||
\fB-F\fR
|
||||
If specified, this parameter causes
|
||||
the main \fBnmbd\fR process to not daemonize,
|
||||
i.e. double-fork and disassociate with the terminal.
|
||||
Child processes are still created as normal to service
|
||||
each connection request, but the main process does not
|
||||
exit. This operation mode is suitable for running
|
||||
\fBnmbd\fR under process supervisors such
|
||||
as \fBsupervise\fR and \fBsvscan\fR
|
||||
from Daniel J. Bernstein's \fBdaemontools\fR
|
||||
package, or the AIX process monitor.
|
||||
.TP
|
||||
\fB-S\fR
|
||||
If specified, this parameter causes
|
||||
\fBnmbd\fR to log to standard output rather
|
||||
than a file.
|
||||
.TP
|
||||
\fB-i\fR
|
||||
If this parameter is specified it causes the
|
||||
server to run "interactively", not as a daemon, even if the
|
||||
server is executed on the command line of a shell. Setting this
|
||||
parameter negates the implicit daemon mode when run from the
|
||||
command line. \fBnmbd\fR also logs to standard
|
||||
output, as if the -S parameter had been
|
||||
given.
|
||||
.TP
|
||||
\fB-h|--help\fR
|
||||
Print a summary of command line options.
|
||||
.TP
|
||||
\fB-H <filename>\fR
|
||||
NetBIOS lmhosts file. 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 \fIname resolve
|
||||
order\fR described in \fBsmb.conf\fR(5) to resolve any
|
||||
NetBIOS name queries needed by the server. Note
|
||||
that the contents of this file are \fBNOT\fR
|
||||
used by \fBnmbd\fR to answer any name queries.
|
||||
Adding a line to this file affects name NetBIOS resolution
|
||||
from this host \fBONLY\fR.
|
||||
|
||||
The default path to this file is compiled into
|
||||
Samba as part of the build process. Common defaults
|
||||
are \fI/usr/local/samba/lib/lmhosts\fR,
|
||||
\fI/usr/samba/lib/lmhosts\fR or
|
||||
\fI/etc/samba/lmhosts\fR. See the \fBlmhosts\fR(5) man page for details on the contents of this file.
|
||||
.TP
|
||||
\fB-V\fR
|
||||
Prints the version number for
|
||||
\fBsmbd\fR.
|
||||
.TP
|
||||
\fB-s <configuration file>\fR
|
||||
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 \fIsmb.conf(5)\fR for more information.
|
||||
The default configuration file name is determined at
|
||||
compile time.
|
||||
.TP
|
||||
\fB-d|--debug=debuglevel\fR
|
||||
\fIdebuglevel\fR is an integer
|
||||
from 0 to 10. The default value if this parameter is
|
||||
not specified is zero.
|
||||
-D
|
||||
If specified, this parameter causes \fBnmbd\fR to operate as a daemon\&. That is, it detaches itself and runs in the background, fielding requests on the appropriate port\&. By default, \fBnmbd\fR will operate as a daemon if launched from a command shell\&. nmbd can also be operated from the \fBinetd\fR meta-daemon, although this is not recommended\&.
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
.TP
|
||||
-F
|
||||
If specified, this parameter causes the main \fBnmbd\fR process to not daemonize, i\&.e\&. double-fork and disassociate with the terminal\&. Child processes are still created as normal to service each connection request, but the main process does not exit\&. This operation mode is suitable for running \fBnmbd\fR under process supervisors such as \fBsupervise\fR and \fBsvscan\fR from Daniel J\&. Bernstein's \fBdaemontools\fR package, or the AIX process monitor\&.
|
||||
|
||||
|
||||
Note that specifying this parameter here will
|
||||
override the log
|
||||
level file.
|
||||
.TP
|
||||
\fB-l|--logfile=logbasename\fR
|
||||
File name for log/debug files. The extension
|
||||
".client" will be appended. The log file is
|
||||
never removed by the client.
|
||||
-S
|
||||
If specified, this parameter causes \fBnmbd\fR to log to standard output rather than a file\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-p <UDP port number>\fR
|
||||
UDP port number is a positive integer value.
|
||||
This option changes the default UDP port number (normally 137)
|
||||
that \fBnmbd\fR responds to name queries on. Don't
|
||||
use this option unless you are an expert, in which case you
|
||||
won't need help!
|
||||
-i
|
||||
If this parameter is specified it causes the server to run "interactively", not as a daemon, even if the server is executed on the command line of a shell\&. Setting this parameter negates the implicit daemon mode when run from the command line\&. \fBnmbd\fR also logs to standard output, as if the \fB-S\fR parameter had been given\&.
|
||||
|
||||
|
||||
.TP
|
||||
-h|--help
|
||||
Print a summary of command line options\&.
|
||||
|
||||
|
||||
.TP
|
||||
-H <filename>
|
||||
NetBIOS lmhosts file\&. 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 \fIname resolve order\fR described in \fBsmb.conf\fR(5) to resolve any NetBIOS name queries needed by the server\&. Note that the contents of this file are \fBNOT\fR used by \fBnmbd\fR to answer any name queries\&. Adding a line to this file affects name NetBIOS resolution from this host \fBONLY\fR\&.
|
||||
|
||||
|
||||
The default path to this file is compiled into Samba as part of the build process\&. Common defaults are \fI/usr/local/samba/lib/lmhosts\fR, \fI/usr/samba/lib/lmhosts\fR or \fI/etc/samba/lmhosts\fR\&. See the \fBlmhosts\fR(5) man page for details on the contents of this file\&.
|
||||
|
||||
|
||||
.TP
|
||||
-V
|
||||
Prints the version number for \fBsmbd\fR\&.
|
||||
|
||||
|
||||
.TP
|
||||
-s <configuration file>
|
||||
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 \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
|
||||
|
||||
|
||||
.TP
|
||||
-d|--debug=debuglevel
|
||||
\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
|
||||
|
||||
|
||||
The higher this value, the more detail will be logged to the log files about the activities of the 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\&.
|
||||
|
||||
|
||||
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\&.
|
||||
|
||||
|
||||
Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&.
|
||||
|
||||
|
||||
.TP
|
||||
-l|--logfile=logbasename
|
||||
File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&.
|
||||
|
||||
|
||||
.TP
|
||||
-p <UDP port number>
|
||||
UDP port number is a positive integer value\&. This option changes the default UDP port number (normally 137) that \fBnmbd\fR responds to name queries on\&. Don't use this option unless you are an expert, in which case you won't need help!
|
||||
|
||||
|
||||
.SH "FILES"
|
||||
.TP
|
||||
\fB\fI/etc/inetd.conf\fB\fR
|
||||
If the server is to be run by the
|
||||
\fBinetd\fR meta-daemon, this file
|
||||
must contain suitable startup information for the
|
||||
meta-daemon. See the install document
|
||||
for details.
|
||||
.TP
|
||||
\fB\fI/etc/rc\fB\fR
|
||||
or whatever initialization script your
|
||||
system uses).
|
||||
|
||||
If running the server as a daemon at startup,
|
||||
this file will need to contain an appropriate startup
|
||||
sequence for the server. See the "How to Install and Test SAMBA" document
|
||||
for details.
|
||||
.TP
|
||||
\fB\fI/etc/services\fB\fR
|
||||
If running the server via the
|
||||
meta-daemon \fBinetd\fR, 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 "How to Install and Test SAMBA"
|
||||
document for details.
|
||||
\fI/etc/inetd\&.conf\fR
|
||||
If the server is to be run by the \fBinetd\fR meta-daemon, this file must contain suitable startup information for the meta-daemon\&. See the install document for details\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB\fI/usr/local/samba/lib/smb.conf\fB\fR
|
||||
This is the default location of
|
||||
the \fBsmb.conf\fR(5) server
|
||||
configuration file. Other common places that systems
|
||||
install this file are \fI/usr/samba/lib/smb.conf\fR
|
||||
and \fI/etc/samba/smb.conf\fR.
|
||||
\fI/etc/rc\fR
|
||||
or whatever initialization script your system uses)\&.
|
||||
|
||||
|
||||
If running the server as a daemon at startup, this file will need to contain an appropriate startup sequence for the server\&. See the "How to Install and Test SAMBA" document for details\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fI/etc/services\fR
|
||||
If running the server via the meta-daemon \fBinetd\fR, 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 "How to Install and Test SAMBA" document for details\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fI/usr/local/samba/lib/smb\&.conf\fR
|
||||
This is the default location of the \fBsmb.conf\fR(5) server configuration file\&. Other common places that systems install this file are \fI/usr/samba/lib/smb\&.conf\fR and \fI/etc/samba/smb\&.conf\fR\&.
|
||||
|
||||
|
||||
When run as a WINS server (see the \fBwins support\fR parameter in the \fBsmb.conf\fR(5) man page), \fBnmbd\fR will store the WINS database in the file \fIwins\&.dat\fR in the \fIvar/locks\fR directory configured under wherever Samba was configured to install itself\&.
|
||||
|
||||
|
||||
If \fBnmbd\fR is acting as a \fB browse master\fR (see the \fBlocal master\fR parameter in the \fBsmb.conf\fR(5) man page, \fBnmbd\fR will store the browsing database in the file \fIbrowse\&.dat \fR in the \fIvar/locks\fR directory configured under wherever Samba was configured to install itself\&.
|
||||
|
||||
When run as a WINS server (see the
|
||||
wins support
|
||||
parameter in the \fBsmb.conf\fR(5) man page),
|
||||
\fBnmbd\fR
|
||||
will store the WINS database in the file \fIwins.dat\fR
|
||||
in the \fIvar/locks\fR directory configured under
|
||||
wherever Samba was configured to install itself.
|
||||
|
||||
If \fBnmbd\fR is acting as a \fB browse master\fR (see the local master
|
||||
parameter in the \fBsmb.conf\fR(5) man page, \fBnmbd\fR
|
||||
will store the browsing database in the file \fIbrowse.dat
|
||||
\fR in the \fIvar/locks\fR directory
|
||||
configured under wherever Samba was configured to install itself.
|
||||
.SH "SIGNALS"
|
||||
|
||||
.PP
|
||||
To shut down an \fBnmbd\fR process it is recommended
|
||||
that SIGKILL (-9) \fBNOT\fR be used, except as a last
|
||||
resort, as this may leave the name database in an inconsistent state.
|
||||
The correct way to terminate \fBnmbd\fR is to send it
|
||||
a SIGTERM (-15) signal and wait for it to die on its own.
|
||||
To shut down an \fBnmbd\fR process it is recommended that SIGKILL (-9) \fBNOT\fR be used, except as a last resort, as this may leave the name database in an inconsistent state\&. The correct way to terminate \fBnmbd\fR is to send it a SIGTERM (-15) signal and wait for it to die on its own\&.
|
||||
|
||||
.PP
|
||||
\fBnmbd\fR will accept SIGHUP, which will cause
|
||||
it to dump out its namelists into the file \fInamelist.debug
|
||||
\fR in the \fI/usr/local/samba/var/locks\fR
|
||||
directory (or the \fIvar/locks\fR directory configured
|
||||
under wherever Samba was configured to install itself). This will also
|
||||
cause \fBnmbd\fR to dump out its server database in
|
||||
the \fIlog.nmb\fR file.
|
||||
\fBnmbd\fR will accept SIGHUP, which will cause it to dump out its namelists into the file \fInamelist\&.debug \fR in the \fI/usr/local/samba/var/locks\fR directory (or the \fIvar/locks\fR directory configured under wherever Samba was configured to install itself)\&. This will also cause \fBnmbd\fR to dump out its server database in the \fIlog\&.nmb\fR file\&.
|
||||
|
||||
.PP
|
||||
The debug log level of nmbd may be raised or lowered
|
||||
using \fBsmbcontrol\fR(1) (SIGUSR[1|2] signals
|
||||
are no longer used since Samba 2.2). This is to allow
|
||||
transient problems to be diagnosed, whilst still running
|
||||
at a normally low log level.
|
||||
The debug log level of nmbd may be raised or lowered using \fBsmbcontrol\fR(1) (SIGUSR[1|2] signals are no longer used since Samba 2\&.2)\&. This is to allow transient problems to be diagnosed, whilst still running at a normally low log level\&.
|
||||
|
||||
.SH "VERSION"
|
||||
|
||||
.PP
|
||||
This man page is correct for version 3.0 of
|
||||
the Samba suite.
|
||||
This man page is correct for version 3\&.0 of the Samba suite\&.
|
||||
|
||||
.SH "SEE ALSO"
|
||||
|
||||
.PP
|
||||
\fBinetd\fR(8), \fBsmbd\fR(8), \fBsmb.conf\fR(5), \fBsmbclient\fR(1), \fBtestparm\fR(1), \fBtestprns\fR(1), and the Internet
|
||||
RFC's \fIrfc1001.txt\fR, \fIrfc1002.txt\fR.
|
||||
In addition the CIFS (formerly SMB) specification is available
|
||||
as a link from the Web page
|
||||
http://samba.org/cifs/ <URL:http://samba.org/cifs/>.
|
||||
\fBinetd\fR(8), \fBsmbd\fR(8), \fBsmb.conf\fR(5), \fBsmbclient\fR(1), \fBtestparm\fR(1), \fBtestprns\fR(1), and the Internet RFC's \fIrfc1001\&.txt\fR, \fIrfc1002\&.txt\fR\&. In addition the CIFS (formerly SMB) specification is available as a link from the Web page http://samba\&.org/cifs/\&.
|
||||
|
||||
.SH "AUTHOR"
|
||||
|
||||
.PP
|
||||
The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.
|
||||
The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
|
||||
|
||||
.PP
|
||||
The original Samba man pages were written by Karl Auer.
|
||||
The man page sources were converted to YODL format (another
|
||||
excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook
|
||||
XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.
|
||||
The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
|
||||
|
||||
|
||||
@ -1,198 +1,185 @@
|
||||
.\" This manpage has been automatically generated by docbook2man
|
||||
.\" from a DocBook document. This tool can be found at:
|
||||
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
||||
.\" Please send any bug reports, improvements, comments, patches,
|
||||
.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
||||
.TH "NMBLOOKUP" "1" "19 april 2003" "" ""
|
||||
|
||||
.\"Generated by db2man.xsl. Don't modify this, modify the source.
|
||||
.de Sh \" Subsection
|
||||
.br
|
||||
.if t .Sp
|
||||
.ne 5
|
||||
.PP
|
||||
\fB\\$1\fR
|
||||
.PP
|
||||
..
|
||||
.de Sp \" Vertical space (when we can't use .PP)
|
||||
.if t .sp .5v
|
||||
.if n .sp
|
||||
..
|
||||
.de Ip \" List item
|
||||
.br
|
||||
.ie \\n(.$>=3 .ne \\$3
|
||||
.el .ne 3
|
||||
.IP "\\$1" \\$2
|
||||
..
|
||||
.TH "NMBLOOKUP" 1 "" "" ""
|
||||
.SH NAME
|
||||
nmblookup \- NetBIOS over TCP/IP client used to lookup NetBIOS names
|
||||
.SH SYNOPSIS
|
||||
nmblookup \- NetBIOS over TCP/IP client used to lookup NetBIOS names
|
||||
.SH "SYNOPSIS"
|
||||
|
||||
\fBnmblookup\fR [ \fB-M\fR ] [ \fB-R\fR ] [ \fB-S\fR ] [ \fB-r\fR ] [ \fB-A\fR ] [ \fB-h\fR ] [ \fB-B <broadcast address>\fR ] [ \fB-U <unicast address>\fR ] [ \fB-d <debug level>\fR ] [ \fB-s <smb config file>\fR ] [ \fB-i <NetBIOS scope>\fR ] [ \fB-T\fR ] [ \fB-f\fR ] \fBname\fR
|
||||
.nf
|
||||
\fBnmblookup\fR [-M] [-R] [-S] [-r] [-A] [-h] [-B <broadcast address>] [-U <unicast
|
||||
address>] [-d <debug level>] [-s <smb config file>] [-i <NetBIOS scope>]
|
||||
[-T] [-f] {name}
|
||||
.fi
|
||||
|
||||
.SH "DESCRIPTION"
|
||||
|
||||
.PP
|
||||
This tool is part of the \fBSamba\fR(7) suite.
|
||||
This tool is part of the \fBSamba\fR(7) suite\&.
|
||||
|
||||
.PP
|
||||
\fBnmblookup\fR 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.
|
||||
\fBnmblookup\fR 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\&.
|
||||
|
||||
.SH "OPTIONS"
|
||||
.TP
|
||||
\fB-M\fR
|
||||
Searches for a master browser by looking
|
||||
up the NetBIOS name \fIname\fR with a
|
||||
type of 0x1d. If \fI name\fR is "-" then it does a lookup on the special name
|
||||
__MSBROWSE__.
|
||||
.TP
|
||||
\fB-R\fR
|
||||
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.
|
||||
.TP
|
||||
\fB-S\fR
|
||||
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.
|
||||
.TP
|
||||
\fB-r\fR
|
||||
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 privilege is needed to bind to this port, and
|
||||
in addition, if the \fBnmbd\fR(8) daemon is running on this machine it also binds to this port.
|
||||
.TP
|
||||
\fB-A\fR
|
||||
Interpret \fIname\fR as
|
||||
an IP Address and do a node status query on this address.
|
||||
.TP
|
||||
\fB-n <primary NetBIOS name>\fR
|
||||
This option allows you to override
|
||||
the NetBIOS name that Samba uses for itself. This is identical
|
||||
to setting the \fINetBIOS
|
||||
name\fR parameter in the \fBsmb.conf\fR(5) file. However, a command
|
||||
line setting will take precedence over settings in
|
||||
\fBsmb.conf\fR(5).
|
||||
.TP
|
||||
\fB-i <scope>\fR
|
||||
This specifies a NetBIOS scope that
|
||||
\fBnmblookup\fR 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
|
||||
\fBvery\fR rarely used, only set this parameter
|
||||
if you are the system administrator in charge of all the
|
||||
NetBIOS systems you communicate with.
|
||||
.TP
|
||||
\fB-W|--workgroup=domain\fR
|
||||
Set the SMB domain of the username. This
|
||||
overrides the default domain which is the domain defined in
|
||||
smb.conf. If the domain specified is the same as the servers
|
||||
NetBIOS name, it causes the client to log on using the servers local
|
||||
SAM (as opposed to the Domain SAM).
|
||||
.TP
|
||||
\fB-O socket options\fR
|
||||
TCP socket options to set on the client
|
||||
socket. See the socket options parameter in
|
||||
the \fBsmb.conf\fR(5) manual page for the list of valid
|
||||
options.
|
||||
.TP
|
||||
\fB-h|--help\fR
|
||||
Print a summary of command line options.
|
||||
.TP
|
||||
\fB-B <broadcast address>\fR
|
||||
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 \fIinterfaces\fR
|
||||
parameter of the \fBsmb.conf\fR(5) file.
|
||||
.TP
|
||||
\fB-U <unicast address>\fR
|
||||
Do a unicast query to the specified address or
|
||||
host \fIunicast address\fR. This option
|
||||
(along with the \fI-R\fR option) is needed to
|
||||
query a WINS server.
|
||||
.TP
|
||||
\fB-V\fR
|
||||
Prints the version number for
|
||||
\fBsmbd\fR.
|
||||
.TP
|
||||
\fB-s <configuration file>\fR
|
||||
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 \fIsmb.conf(5)\fR for more information.
|
||||
The default configuration file name is determined at
|
||||
compile time.
|
||||
.TP
|
||||
\fB-d|--debug=debuglevel\fR
|
||||
\fIdebuglevel\fR is an integer
|
||||
from 0 to 10. The default value if this parameter is
|
||||
not specified is zero.
|
||||
|
||||
The higher this value, the more detail will be
|
||||
logged to the log files about the activities of the
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
Note that specifying this parameter here will
|
||||
override the log
|
||||
level file.
|
||||
.TP
|
||||
\fB-l|--logfile=logbasename\fR
|
||||
File name for log/debug files. The extension
|
||||
".client" will be appended. The log file is
|
||||
never removed by the client.
|
||||
.TP
|
||||
\fB-T\fR
|
||||
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
|
||||
-M
|
||||
Searches for a master browser by looking up the NetBIOS name \fIname\fR with a type of \fB0x1d\fR\&. If \fI name\fR is "-" then it does a lookup on the special name \fB__MSBROWSE__\fR\&. Please note that in order to use the name "-", you need to make sure "-" isn't parsed as an argument, e\&.g\&. use : \fBnmblookup -M -- -\fR\&.
|
||||
|
||||
\fBIP address .... NetBIOS name\fR
|
||||
|
||||
pair that is the normal output.
|
||||
.TP
|
||||
\fB-f\fR
|
||||
Show which flags apply to the name that has been looked up. Possible
|
||||
answers are zero or more of: Response, Authoritative,
|
||||
Truncated, Recursion_Desired, Recursion_Available, Broadcast.
|
||||
-R
|
||||
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\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBname\fR
|
||||
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 '#<type>' to the name. This name may also be
|
||||
\&'*', which will return all registered names within a broadcast
|
||||
area.
|
||||
-S
|
||||
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\&.
|
||||
|
||||
|
||||
.TP
|
||||
-r
|
||||
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 privilege is needed to bind to this port, and in addition, if the \fBnmbd\fR(8) daemon is running on this machine it also binds to this port\&.
|
||||
|
||||
|
||||
.TP
|
||||
-A
|
||||
Interpret \fIname\fR as an IP Address and do a node status query on this address\&.
|
||||
|
||||
|
||||
.TP
|
||||
-n <primary NetBIOS name>
|
||||
This option allows you to override the NetBIOS name that Samba uses for itself\&. This is identical to setting the \fINetBIOS name\fR parameter in the \fBsmb.conf\fR(5) file\&. However, a command line setting will take precedence over settings in \fBsmb.conf\fR(5)\&.
|
||||
|
||||
|
||||
.TP
|
||||
-i <scope>
|
||||
This specifies a NetBIOS scope that \fBnmblookup\fR 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 \fBvery\fR rarely used, only set this parameter if you are the system administrator in charge of all the NetBIOS systems you communicate with\&.
|
||||
|
||||
|
||||
.TP
|
||||
-W|--workgroup=domain
|
||||
Set the SMB domain of the username\&. This overrides the default domain which is the domain defined in smb\&.conf\&. If the domain specified is the same as the servers NetBIOS name, it causes the client to log on using the servers local SAM (as opposed to the Domain SAM)\&.
|
||||
|
||||
|
||||
.TP
|
||||
-O socket options
|
||||
TCP socket options to set on the client socket\&. See the socket options parameter in the \fBsmb.conf\fR(5) manual page for the list of valid options\&.
|
||||
|
||||
|
||||
.TP
|
||||
-h|--help
|
||||
Print a summary of command line options\&.
|
||||
|
||||
|
||||
.TP
|
||||
-B <broadcast address>
|
||||
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 \fIinterfaces\fR parameter of the \fBsmb.conf\fR(5) file\&.
|
||||
|
||||
|
||||
.TP
|
||||
-U <unicast address>
|
||||
Do a unicast query to the specified address or host \fIunicast address\fR\&. This option (along with the \fI-R\fR option) is needed to query a WINS server\&.
|
||||
|
||||
|
||||
.TP
|
||||
-V
|
||||
Prints the version number for \fBsmbd\fR\&.
|
||||
|
||||
|
||||
.TP
|
||||
-s <configuration file>
|
||||
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 \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
|
||||
|
||||
|
||||
.TP
|
||||
-d|--debug=debuglevel
|
||||
\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
|
||||
|
||||
|
||||
The higher this value, the more detail will be logged to the log files about the activities of the 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\&.
|
||||
|
||||
|
||||
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\&.
|
||||
|
||||
|
||||
Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&.
|
||||
|
||||
|
||||
.TP
|
||||
-l|--logfile=logbasename
|
||||
File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&.
|
||||
|
||||
|
||||
.TP
|
||||
-T
|
||||
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
|
||||
|
||||
|
||||
\fBIP address \&.\&.\&.\&. NetBIOS name\fR
|
||||
|
||||
|
||||
pair that is the normal output\&.
|
||||
|
||||
|
||||
.TP
|
||||
-f
|
||||
Show which flags apply to the name that has been looked up\&. Possible answers are zero or more of: Response, Authoritative, Truncated, Recursion_Desired, Recursion_Available, Broadcast\&.
|
||||
|
||||
|
||||
.TP
|
||||
name
|
||||
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 '#<type>' to the name\&. This name may also be '*', which will return all registered names within a broadcast area\&.
|
||||
|
||||
|
||||
.SH "EXAMPLES"
|
||||
|
||||
.PP
|
||||
\fBnmblookup\fR can be used to query
|
||||
a WINS server (in the same way \fBnslookup\fR is
|
||||
used to query DNS servers). To query a WINS server, \fBnmblookup\fR
|
||||
must be called like this:
|
||||
\fBnmblookup\fR can be used to query a WINS server (in the same way \fBnslookup\fR is used to query DNS servers)\&. To query a WINS server, \fBnmblookup\fR must be called like this:
|
||||
|
||||
.PP
|
||||
\fBnmblookup -U server -R 'name'\fR
|
||||
|
||||
.PP
|
||||
For example, running :
|
||||
|
||||
.PP
|
||||
\fBnmblookup -U samba.org -R 'IRIX#1B'\fR
|
||||
|
||||
.PP
|
||||
would query the WINS server samba.org for the domain
|
||||
master browser (1B name type) for the IRIX workgroup.
|
||||
would query the WINS server samba\&.org for the domain master browser (1B name type) for the IRIX workgroup\&.
|
||||
|
||||
.SH "VERSION"
|
||||
|
||||
.PP
|
||||
This man page is correct for version 3.0 of
|
||||
the Samba suite.
|
||||
This man page is correct for version 3\&.0 of the Samba suite\&.
|
||||
|
||||
.SH "SEE ALSO"
|
||||
|
||||
.PP
|
||||
\fBnmbd\fR(8), \fBsamba\fR(7), and \fBsmb.conf\fR(5).
|
||||
\fBnmbd\fR(8), \fBsamba\fR(7), and \fBsmb.conf\fR(5)\&.
|
||||
|
||||
.SH "AUTHOR"
|
||||
|
||||
.PP
|
||||
The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.
|
||||
The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
|
||||
|
||||
.PP
|
||||
The original Samba man pages were written by Karl Auer.
|
||||
The man page sources were converted to YODL format (another
|
||||
excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook
|
||||
XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.
|
||||
The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
|
||||
|
||||
|
||||
@ -1,109 +1,135 @@
|
||||
.\" This manpage has been automatically generated by docbook2man
|
||||
.\" from a DocBook document. This tool can be found at:
|
||||
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
||||
.\" Please send any bug reports, improvements, comments, patches,
|
||||
.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
||||
.TH "NTLM_AUTH" "1" "19 april 2003" "" ""
|
||||
|
||||
.\"Generated by db2man.xsl. Don't modify this, modify the source.
|
||||
.de Sh \" Subsection
|
||||
.br
|
||||
.if t .Sp
|
||||
.ne 5
|
||||
.PP
|
||||
\fB\\$1\fR
|
||||
.PP
|
||||
..
|
||||
.de Sp \" Vertical space (when we can't use .PP)
|
||||
.if t .sp .5v
|
||||
.if n .sp
|
||||
..
|
||||
.de Ip \" List item
|
||||
.br
|
||||
.ie \\n(.$>=3 .ne \\$3
|
||||
.el .ne 3
|
||||
.IP "\\$1" \\$2
|
||||
..
|
||||
.TH "NTLM_AUTH" 1 "" "" ""
|
||||
.SH NAME
|
||||
ntlm_auth \- tool to allow external access to Winbind's NTLM authentication function
|
||||
.SH SYNOPSIS
|
||||
.SH "SYNOPSIS"
|
||||
|
||||
\fBntlm_auth\fR [ \fB-d debuglevel\fR ] [ \fB-l logfile\fR ] [ \fB-s <smb config file>\fR ]
|
||||
.nf
|
||||
\fBntlm_auth\fR [-d debuglevel] [-l logfile] [-s <smb config file>]
|
||||
.fi
|
||||
|
||||
.SH "DESCRIPTION"
|
||||
|
||||
.PP
|
||||
This tool is part of the \fBSamba\fR(7) suite.
|
||||
This tool is part of the \fBSamba\fR(7) suite\&.
|
||||
|
||||
.PP
|
||||
\fBntlm_auth\fR is a helper utility that authenticates
|
||||
users using NT/LM authentication. It returns 0 if the users is authenticated
|
||||
successfully and 1 if access was denied. ntlm_auth uses winbind to access
|
||||
the user and authentication data for a domain. This utility
|
||||
is only to be used by other programs (currently squid).
|
||||
\fBntlm_auth\fR is a helper utility that authenticates users using NT/LM authentication\&. It returns 0 if the users is authenticated successfully and 1 if access was denied\&. ntlm_auth uses winbind to access the user and authentication data for a domain\&. This utility is only to be used by other programs (currently squid)\&.
|
||||
|
||||
.SH "OPTIONS"
|
||||
|
||||
.TP
|
||||
\fB--helper-protocol=PROTO\fR
|
||||
--helper-protocol=PROTO
|
||||
Operate as a stdio-based helper
|
||||
|
||||
|
||||
.TP
|
||||
\fB--username=USERNAME\fR
|
||||
--username=USERNAME
|
||||
Specify username of user to authenticate
|
||||
|
||||
|
||||
.TP
|
||||
\fB--domain=DOMAIN\fR
|
||||
--domain=DOMAIN
|
||||
Specify domain of user to authenticate
|
||||
|
||||
|
||||
.TP
|
||||
\fB--workstation=WORKSTATION\fR
|
||||
--workstation=WORKSTATION
|
||||
Specify the workstation the user authenticated from
|
||||
|
||||
|
||||
.TP
|
||||
\fB--challenge=STRING\fR
|
||||
--challenge=STRING
|
||||
challenge (HEX encoded)
|
||||
|
||||
|
||||
.TP
|
||||
\fB--lm-response=RESPONSE\fR
|
||||
--lm-response=RESPONSE
|
||||
LM Response to the challenge (HEX encoded)
|
||||
|
||||
|
||||
.TP
|
||||
\fB--nt-response=RESPONSE\fR
|
||||
--nt-response=RESPONSE
|
||||
NT or NTLMv2 Response to the challenge (HEX encoded)
|
||||
|
||||
|
||||
.TP
|
||||
\fB--password=PASSWORD\fR
|
||||
--password=PASSWORD
|
||||
User's plaintext password
|
||||
|
||||
|
||||
.TP
|
||||
\fB--request-lm-key\fR
|
||||
--request-lm-key
|
||||
Retreive LM session key
|
||||
|
||||
|
||||
.TP
|
||||
\fB--request-nt-key\fR
|
||||
--request-nt-key
|
||||
Request NT key
|
||||
.TP
|
||||
\fB-V\fR
|
||||
Prints the version number for
|
||||
\fBsmbd\fR.
|
||||
.TP
|
||||
\fB-s <configuration file>\fR
|
||||
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 \fIsmb.conf(5)\fR for more information.
|
||||
The default configuration file name is determined at
|
||||
compile time.
|
||||
.TP
|
||||
\fB-d|--debug=debuglevel\fR
|
||||
\fIdebuglevel\fR is an integer
|
||||
from 0 to 10. The default value if this parameter is
|
||||
not specified is zero.
|
||||
|
||||
The higher this value, the more detail will be
|
||||
logged to the log files about the activities of the
|
||||
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.
|
||||
|
||||
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.
|
||||
.TP
|
||||
-V
|
||||
Prints the version number for \fBsmbd\fR\&.
|
||||
|
||||
|
||||
Note that specifying this parameter here will
|
||||
override the log
|
||||
level file.
|
||||
.TP
|
||||
\fB-l|--logfile=logbasename\fR
|
||||
File name for log/debug files. The extension
|
||||
".client" will be appended. The log file is
|
||||
never removed by the client.
|
||||
-s <configuration file>
|
||||
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 \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-h|--help\fR
|
||||
Print a summary of command line options.
|
||||
-d|--debug=debuglevel
|
||||
\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
|
||||
|
||||
|
||||
The higher this value, the more detail will be logged to the log files about the activities of the 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\&.
|
||||
|
||||
|
||||
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\&.
|
||||
|
||||
|
||||
Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&.
|
||||
|
||||
|
||||
.TP
|
||||
-l|--logfile=logbasename
|
||||
File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&.
|
||||
|
||||
|
||||
.TP
|
||||
-h|--help
|
||||
Print a summary of command line options\&.
|
||||
|
||||
|
||||
.SH "VERSION"
|
||||
|
||||
.PP
|
||||
This man page is correct for version 3.0 of the Samba
|
||||
suite.
|
||||
This man page is correct for version 3\&.0 of the Samba suite\&.
|
||||
|
||||
.SH "AUTHOR"
|
||||
|
||||
.PP
|
||||
The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.
|
||||
The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
|
||||
|
||||
.PP
|
||||
The ntlm_auth manpage was written by Jelmer Vernooij.
|
||||
The ntlm_auth manpage was written by Jelmer Vernooij\&.
|
||||
|
||||
|
||||
@ -1,56 +1,75 @@
|
||||
.\" This manpage has been automatically generated by docbook2man
|
||||
.\" from a DocBook document. This tool can be found at:
|
||||
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
||||
.\" Please send any bug reports, improvements, comments, patches,
|
||||
.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
||||
.TH "PDBEDIT" "8" "19 april 2003" "" ""
|
||||
|
||||
.\"Generated by db2man.xsl. Don't modify this, modify the source.
|
||||
.de Sh \" Subsection
|
||||
.br
|
||||
.if t .Sp
|
||||
.ne 5
|
||||
.PP
|
||||
\fB\\$1\fR
|
||||
.PP
|
||||
..
|
||||
.de Sp \" Vertical space (when we can't use .PP)
|
||||
.if t .sp .5v
|
||||
.if n .sp
|
||||
..
|
||||
.de Ip \" List item
|
||||
.br
|
||||
.ie \\n(.$>=3 .ne \\$3
|
||||
.el .ne 3
|
||||
.IP "\\$1" \\$2
|
||||
..
|
||||
.TH "PDBEDIT" 8 "" "" ""
|
||||
.SH NAME
|
||||
pdbedit \- manage the SAM database
|
||||
.SH SYNOPSIS
|
||||
.SH "SYNOPSIS"
|
||||
|
||||
\fBpdbedit\fR [ \fB-l\fR ] [ \fB-v\fR ] [ \fB-w\fR ] [ \fB-u username\fR ] [ \fB-f fullname\fR ] [ \fB-h homedir\fR ] [ \fB-D drive\fR ] [ \fB-S script\fR ] [ \fB-p profile\fR ] [ \fB-a\fR ] [ \fB-m\fR ] [ \fB-x\fR ] [ \fB-i passdb-backend\fR ] [ \fB-e passdb-backend\fR ] [ \fB-g\fR ] [ \fB-b passdb-backend\fR ] [ \fB-g\fR ] [ \fB-d debuglevel\fR ] [ \fB-s configfile\fR ] [ \fB-P account-policy\fR ] [ \fB-C value\fR ]
|
||||
.nf
|
||||
\fBpdbedit\fR [-l] [-v] [-w] [-u username] [-f fullname] [-h homedir] [-D drive] [-S
|
||||
script] [-p profile] [-a] [-m] [-x] [-i passdb-backend] [-e passdb-backend]
|
||||
[-g] [-b passdb-backend] [-g] [-d debuglevel] [-s configfile] [-P account-policy]
|
||||
[-C value]
|
||||
.fi
|
||||
|
||||
.SH "DESCRIPTION"
|
||||
|
||||
.PP
|
||||
This tool is part of the \fBSamba\fR(7) suite.
|
||||
This tool is part of the \fBSamba\fR(7) suite\&.
|
||||
|
||||
.PP
|
||||
The pdbedit program is used to manage the users accounts
|
||||
stored in the sam database and can only be run by root.
|
||||
The pdbedit program is used to manage the users accounts stored in the sam database and can only be run by root\&.
|
||||
|
||||
.PP
|
||||
The pdbedit tool uses the passdb modular interface and is
|
||||
independent from the kind of users database used (currently there
|
||||
are smbpasswd, ldap, nis+ and tdb based and more can be added
|
||||
without changing the tool).
|
||||
The pdbedit tool uses the passdb modular interface and is independent from the kind of users database used (currently there are smbpasswd, ldap, nis+ and tdb based and more can be added without changing the tool)\&.
|
||||
|
||||
.PP
|
||||
There are five main ways to use pdbedit: adding a user account,
|
||||
removing a user account, modifing a user account, listing user
|
||||
accounts, importing users accounts.
|
||||
There are five main ways to use pdbedit: adding a user account, removing a user account, modifing a user account, listing user accounts, importing users accounts\&.
|
||||
|
||||
.SH "OPTIONS"
|
||||
|
||||
.TP
|
||||
\fB-l\fR
|
||||
This option lists all the user accounts
|
||||
present in the users database.
|
||||
This option prints a list of user/uid pairs separated by
|
||||
the ':' character.
|
||||
-l
|
||||
This option lists all the user accounts present in the users database\&. This option prints a list of user/uid pairs separated by the ':' character\&.
|
||||
|
||||
|
||||
Example: \fBpdbedit -l\fR
|
||||
|
||||
|
||||
.nf
|
||||
|
||||
sorce:500:Simo Sorce
|
||||
samba:45:Test User
|
||||
.fi
|
||||
|
||||
|
||||
.TP
|
||||
\fB-v\fR
|
||||
This option enables the verbose listing format.
|
||||
It causes pdbedit to list the users in the database, printing
|
||||
out the account fields in a descriptive format.
|
||||
-v
|
||||
This option enables the verbose listing format\&. It causes pdbedit to list the users in the database, printing out the account fields in a descriptive format\&.
|
||||
|
||||
|
||||
Example: \fBpdbedit -l -v\fR
|
||||
|
||||
|
||||
.nf
|
||||
|
||||
---------------
|
||||
username: sorce
|
||||
user ID/Group: 500/500
|
||||
@ -58,7 +77,7 @@ user RID/GRID: 2000/2001
|
||||
Full Name: Simo Sorce
|
||||
Home Directory: \\\\BERSERKER\\sorce
|
||||
HomeDir Drive: H:
|
||||
Logon Script: \\\\BERSERKER\\netlogon\\sorce.bat
|
||||
Logon Script: \\\\BERSERKER\\netlogon\\sorce\&.bat
|
||||
Profile Path: \\\\BERSERKER\\profile
|
||||
---------------
|
||||
username: samba
|
||||
@ -70,222 +89,225 @@ HomeDir Drive:
|
||||
Logon Script:
|
||||
Profile Path: \\\\BERSERKER\\profile
|
||||
.fi
|
||||
|
||||
|
||||
.TP
|
||||
\fB-w\fR
|
||||
This option sets the "smbpasswd" listing format.
|
||||
It will make pdbedit list the users in the database, printing
|
||||
out the account fields in a format compatible with the
|
||||
\fIsmbpasswd\fR file format. (see the
|
||||
\fBsmbpasswd\fR(5) for details)
|
||||
-w
|
||||
This option sets the "smbpasswd" listing format\&. It will make pdbedit list the users in the database, printing out the account fields in a format compatible with the \fIsmbpasswd\fR file format\&. (see the \fBsmbpasswd\fR(5) for details)
|
||||
|
||||
|
||||
Example: \fBpdbedit -l -w\fR
|
||||
|
||||
.nf
|
||||
|
||||
sorce:500:508818B733CE64BEAAD3B435B51404EE:D2A2418EFC466A8A0F6B1DBB5C3DB80C:[UX ]:LCT-00000000:
|
||||
samba:45:0F2B255F7B67A7A9AAD3B435B51404EE:BC281CE3F53B6A5146629CD4751D3490:[UX ]:LCT-3BFA1E8D:
|
||||
.fi
|
||||
|
||||
.TP
|
||||
\fB-u username\fR
|
||||
This option specifies the username to be
|
||||
used for the operation requested (listing, adding, removing).
|
||||
It is \fBrequired\fR in add, remove and modify
|
||||
operations and \fBoptional\fR in list
|
||||
operations.
|
||||
-u username
|
||||
This option specifies the username to be used for the operation requested (listing, adding, removing)\&. It is \fBrequired\fR in add, remove and modify operations and \fBoptional\fR in list operations\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-f fullname\fR
|
||||
This option can be used while adding or
|
||||
modifing a user account. It will specify the user's full
|
||||
name.
|
||||
-f fullname
|
||||
This option can be used while adding or modifing a user account\&. It will specify the user's full name\&.
|
||||
|
||||
|
||||
Example: \fB-f "Simo Sorce"\fR
|
||||
.TP
|
||||
\fB-h homedir\fR
|
||||
This option can be used while adding or
|
||||
modifing a user account. It will specify the user's home
|
||||
directory network path.
|
||||
|
||||
Example: \fB-h "\\\\\\\\BERSERKER\\\\sorce"\fR
|
||||
|
||||
.TP
|
||||
\fB-D drive\fR
|
||||
This option can be used while adding or
|
||||
modifing a user account. It will specify the windows drive
|
||||
letter to be used to map the home directory.
|
||||
-h homedir
|
||||
This option can be used while adding or modifing a user account\&. It will specify the user's home directory network path\&.
|
||||
|
||||
|
||||
Example: \fB-h "\\\\BERSERKER\\sorce"\fR
|
||||
|
||||
|
||||
.TP
|
||||
-D drive
|
||||
This option can be used while adding or modifing a user account\&. It will specify the windows drive letter to be used to map the home directory\&.
|
||||
|
||||
|
||||
Example: \fB-d "H:"\fR
|
||||
.TP
|
||||
\fB-S script\fR
|
||||
This option can be used while adding or
|
||||
modifing a user account. It will specify the user's logon
|
||||
script path.
|
||||
|
||||
Example: \fB-s "\\\\\\\\BERSERKER\\\\netlogon\\\\sorce.bat"\fR
|
||||
.TP
|
||||
\fB-p profile\fR
|
||||
This option can be used while adding or
|
||||
modifing a user account. It will specify the user's profile
|
||||
directory.
|
||||
|
||||
Example: \fB-p "\\\\\\\\BERSERKER\\\\netlogon"\fR
|
||||
.TP
|
||||
\fB-a\fR
|
||||
This option is used to add a user into the
|
||||
database. This command needs a user name specified with
|
||||
the -u switch. When adding a new user, pdbedit will also
|
||||
ask for the password to be used.
|
||||
-S script
|
||||
This option can be used while adding or modifing a user account\&. It will specify the user's logon script path\&.
|
||||
|
||||
|
||||
Example: \fB-s "\\\\BERSERKER\\netlogon\\sorce.bat"\fR
|
||||
|
||||
|
||||
.TP
|
||||
-p profile
|
||||
This option can be used while adding or modifing a user account\&. It will specify the user's profile directory\&.
|
||||
|
||||
|
||||
Example: \fB-p "\\\\BERSERKER\\netlogon"\fR
|
||||
|
||||
|
||||
.TP
|
||||
-a
|
||||
This option is used to add a user into the database\&. This command needs a user name specified with the -u switch\&. When adding a new user, pdbedit will also ask for the password to be used\&.
|
||||
|
||||
|
||||
Example: \fBpdbedit -a -u sorce\fR
|
||||
|
||||
.nf
|
||||
new password:
|
||||
retype new password
|
||||
.fi
|
||||
|
||||
|
||||
|
||||
.TP
|
||||
\fB-m\fR
|
||||
This option may only be used in conjunction
|
||||
with the \fI-a\fR option. It will make
|
||||
pdbedit to add a machine trust account instead of a user
|
||||
account (-u username will provide the machine name).
|
||||
-m
|
||||
This option may only be used in conjunction with the \fI-a\fR option\&. It will make pdbedit to add a machine trust account instead of a user account (-u username will provide the machine name)\&.
|
||||
|
||||
|
||||
Example: \fBpdbedit -a -m -u w2k-wks\fR
|
||||
|
||||
|
||||
.TP
|
||||
\fB-x\fR
|
||||
This option causes pdbedit to delete an account
|
||||
from the database. It needs a username specified with the
|
||||
-u switch.
|
||||
-x
|
||||
This option causes pdbedit to delete an account from the database\&. It needs a username specified with the -u switch\&.
|
||||
|
||||
|
||||
Example: \fBpdbedit -x -u bob\fR
|
||||
|
||||
|
||||
.TP
|
||||
\fB-i passdb-backend\fR
|
||||
Use a different passdb backend to retrieve users
|
||||
than the one specified in smb.conf. Can be used to import data into
|
||||
your local user database.
|
||||
-i passdb-backend
|
||||
Use a different passdb backend to retrieve users than the one specified in smb\&.conf\&. Can be used to import data into your local user database\&.
|
||||
|
||||
|
||||
This option will ease migration from one passdb backend to another\&.
|
||||
|
||||
|
||||
Example: \fBpdbedit -i smbpasswd:/etc/smbpasswd.old \fR
|
||||
|
||||
This option will ease migration from one passdb backend to
|
||||
another.
|
||||
|
||||
Example: \fBpdbedit -i smbpasswd:/etc/smbpasswd.old
|
||||
\fR
|
||||
.TP
|
||||
\fB-e passdb-backend\fR
|
||||
Exports all currently available users to the
|
||||
specified password database backend.
|
||||
-e passdb-backend
|
||||
Exports all currently available users to the specified password database backend\&.
|
||||
|
||||
|
||||
This option will ease migration from one passdb backend to another and will ease backing up\&.
|
||||
|
||||
This option will ease migration from one passdb backend to
|
||||
another and will ease backing up.
|
||||
|
||||
Example: \fBpdbedit -e smbpasswd:/root/samba-users.backup\fR
|
||||
.TP
|
||||
\fB-g\fR
|
||||
If you specify \fI-g\fR,
|
||||
then \fI-i in-backend -e out-backend\fR
|
||||
applies to the group mapping instead of the user database.
|
||||
|
||||
This option will ease migration from one passdb backend to
|
||||
another and will ease backing up.
|
||||
.TP
|
||||
\fB-g\fR
|
||||
If you specify \fI-g\fR,
|
||||
then \fI-i in-backend -e out-backend\fR
|
||||
applies to the group mapping instead of the user database.
|
||||
|
||||
This option will ease migration from one passdb backend to
|
||||
another and will ease backing up.
|
||||
.TP
|
||||
\fB-b passdb-backend\fR
|
||||
Use a different default passdb backend.
|
||||
-g
|
||||
If you specify \fI-g\fR, then \fI-i in-backend -e out-backend\fR applies to the group mapping instead of the user database\&.
|
||||
|
||||
|
||||
This option will ease migration from one passdb backend to another and will ease backing up\&.
|
||||
|
||||
|
||||
.TP
|
||||
-g
|
||||
If you specify \fI-g\fR, then \fI-i in-backend -e out-backend\fR applies to the group mapping instead of the user database\&.
|
||||
|
||||
|
||||
This option will ease migration from one passdb backend to another and will ease backing up\&.
|
||||
|
||||
|
||||
.TP
|
||||
-b passdb-backend
|
||||
Use a different default passdb backend\&.
|
||||
|
||||
|
||||
Example: \fBpdbedit -b xml:/root/pdb-backup.xml -l\fR
|
||||
|
||||
|
||||
.TP
|
||||
\fB-P account-policy\fR
|
||||
-P account-policy
|
||||
Display an account policy
|
||||
|
||||
Valid policies are: minimum password age, reset count minutes, disconnect time,
|
||||
user must logon to change password, password history, lockout duration, min password length,
|
||||
maximum password age and bad lockout attempt.
|
||||
|
||||
Valid policies are: minimum password age, reset count minutes, disconnect time, user must logon to change password, password history, lockout duration, min password length, maximum password age and bad lockout attempt\&.
|
||||
|
||||
|
||||
Example: \fBpdbedit -P "bad lockout attempt"\fR
|
||||
|
||||
|
||||
.nf
|
||||
|
||||
account policy value for bad lockout attempt is 0
|
||||
.fi
|
||||
|
||||
|
||||
.TP
|
||||
\fB-C account-policy-value\fR
|
||||
Sets an account policy to a specified value.
|
||||
This option may only be used in conjunction
|
||||
with the \fI-P\fR option.
|
||||
-C account-policy-value
|
||||
Sets an account policy to a specified value\&. This option may only be used in conjunction with the \fI-P\fR option\&.
|
||||
|
||||
|
||||
Example: \fBpdbedit -P "bad lockout attempt" -C 3\fR
|
||||
|
||||
|
||||
.nf
|
||||
|
||||
account policy value for bad lockout attempt was 0
|
||||
account policy value for bad lockout attempt is now 3
|
||||
.fi
|
||||
.TP
|
||||
\fB-h|--help\fR
|
||||
Print a summary of command line options.
|
||||
.TP
|
||||
\fB-V\fR
|
||||
Prints the version number for
|
||||
\fBsmbd\fR.
|
||||
.TP
|
||||
\fB-s <configuration file>\fR
|
||||
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 \fIsmb.conf(5)\fR for more information.
|
||||
The default configuration file name is determined at
|
||||
compile time.
|
||||
.TP
|
||||
\fB-d|--debug=debuglevel\fR
|
||||
\fIdebuglevel\fR is an integer
|
||||
from 0 to 10. The default value if this parameter is
|
||||
not specified is zero.
|
||||
|
||||
The higher this value, the more detail will be
|
||||
logged to the log files about the activities of the
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
Note that specifying this parameter here will
|
||||
override the log
|
||||
level file.
|
||||
.TP
|
||||
\fB-l|--logfile=logbasename\fR
|
||||
File name for log/debug files. The extension
|
||||
".client" will be appended. The log file is
|
||||
never removed by the client.
|
||||
-h|--help
|
||||
Print a summary of command line options\&.
|
||||
|
||||
|
||||
.TP
|
||||
-V
|
||||
Prints the version number for \fBsmbd\fR\&.
|
||||
|
||||
|
||||
.TP
|
||||
-s <configuration file>
|
||||
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 \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
|
||||
|
||||
|
||||
.TP
|
||||
-d|--debug=debuglevel
|
||||
\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
|
||||
|
||||
|
||||
The higher this value, the more detail will be logged to the log files about the activities of the 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\&.
|
||||
|
||||
|
||||
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\&.
|
||||
|
||||
|
||||
Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&.
|
||||
|
||||
|
||||
.TP
|
||||
-l|--logfile=logbasename
|
||||
File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&.
|
||||
|
||||
|
||||
.SH "NOTES"
|
||||
|
||||
.PP
|
||||
This command may be used only by root.
|
||||
This command may be used only by root\&.
|
||||
|
||||
.SH "VERSION"
|
||||
|
||||
.PP
|
||||
This man page is correct for version 2.2 of
|
||||
the Samba suite.
|
||||
This man page is correct for version 2\&.2 of the Samba suite\&.
|
||||
|
||||
.SH "SEE ALSO"
|
||||
|
||||
.PP
|
||||
\fBsmbpasswd\fR(5), \fBsamba\fR(7)
|
||||
|
||||
.SH "AUTHOR"
|
||||
|
||||
.PP
|
||||
The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.
|
||||
The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
|
||||
|
||||
.PP
|
||||
The original Samba man pages were written by Karl Auer.
|
||||
The man page sources were converted to YODL format (another
|
||||
excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook
|
||||
XML 4.2 for Samba 3.0 was done by Alexander Bokovoy.
|
||||
The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
|
||||
|
||||
|
||||
@ -1,45 +1,71 @@
|
||||
.\" This manpage has been automatically generated by docbook2man
|
||||
.\" from a DocBook document. This tool can be found at:
|
||||
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
||||
.\" Please send any bug reports, improvements, comments, patches,
|
||||
.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
||||
.TH "PROFILES" "1" "19 april 2003" "" ""
|
||||
|
||||
.\"Generated by db2man.xsl. Don't modify this, modify the source.
|
||||
.de Sh \" Subsection
|
||||
.br
|
||||
.if t .Sp
|
||||
.ne 5
|
||||
.PP
|
||||
\fB\\$1\fR
|
||||
.PP
|
||||
..
|
||||
.de Sp \" Vertical space (when we can't use .PP)
|
||||
.if t .sp .5v
|
||||
.if n .sp
|
||||
..
|
||||
.de Ip \" List item
|
||||
.br
|
||||
.ie \\n(.$>=3 .ne \\$3
|
||||
.el .ne 3
|
||||
.IP "\\$1" \\$2
|
||||
..
|
||||
.TH "PROFILES" 1 "" "" ""
|
||||
.SH NAME
|
||||
profiles \- A utility to report and change SIDs in registry files
|
||||
.SH SYNOPSIS
|
||||
.SH "SYNOPSIS"
|
||||
|
||||
\fBprofiles\fR [ \fB-v\fR ] [ \fB-c SID\fR ] [ \fB-n SID\fR ] \fBfile\fR
|
||||
.nf
|
||||
\fBprofiles\fR [-v] [-c SID] [-n SID] {file}
|
||||
.fi
|
||||
|
||||
.SH "DESCRIPTION"
|
||||
|
||||
.PP
|
||||
This tool is part of the \fBSamba\fR(7) suite.
|
||||
This tool is part of the \fBSamba\fR(7) suite\&.
|
||||
|
||||
.PP
|
||||
\fBprofiles\fR is a utility that
|
||||
reports and changes SIDs in windows registry files. It currently only
|
||||
supports NT.
|
||||
\fBprofiles\fR is a utility that reports and changes SIDs in windows registry files\&. It currently only supports NT\&.
|
||||
|
||||
.SH "OPTIONS"
|
||||
|
||||
.TP
|
||||
\fBfile\fR
|
||||
Registry file to view or edit.
|
||||
file
|
||||
Registry file to view or edit\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-v,--verbose\fR
|
||||
Increases verbosity of messages.
|
||||
-v,--verbose
|
||||
Increases verbosity of messages\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-c SID1 -n SID2\fR
|
||||
Change all occurences of SID1 in \fIfile\fR by SID2.
|
||||
-c SID1 -n SID2
|
||||
Change all occurences of SID1 in \fIfile\fR by SID2\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-h|--help\fR
|
||||
Print a summary of command line options.
|
||||
-h|--help
|
||||
Print a summary of command line options\&.
|
||||
|
||||
|
||||
.SH "VERSION"
|
||||
|
||||
.PP
|
||||
This man page is correct for version 3.0 of the Samba
|
||||
suite.
|
||||
This man page is correct for version 3\&.0 of the Samba suite\&.
|
||||
|
||||
.SH "AUTHOR"
|
||||
|
||||
.PP
|
||||
The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.
|
||||
The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
|
||||
|
||||
.PP
|
||||
The profiles man page was written by Jelmer Vernooij.
|
||||
The profiles man page was written by Jelmer Vernooij\&.
|
||||
|
||||
|
||||
@ -1,330 +1,403 @@
|
||||
.\" This manpage has been automatically generated by docbook2man
|
||||
.\" from a DocBook document. This tool can be found at:
|
||||
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
||||
.\" Please send any bug reports, improvements, comments, patches,
|
||||
.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
||||
.TH "RPCCLIENT" "1" "19 april 2003" "" ""
|
||||
|
||||
.\"Generated by db2man.xsl. Don't modify this, modify the source.
|
||||
.de Sh \" Subsection
|
||||
.br
|
||||
.if t .Sp
|
||||
.ne 5
|
||||
.PP
|
||||
\fB\\$1\fR
|
||||
.PP
|
||||
..
|
||||
.de Sp \" Vertical space (when we can't use .PP)
|
||||
.if t .sp .5v
|
||||
.if n .sp
|
||||
..
|
||||
.de Ip \" List item
|
||||
.br
|
||||
.ie \\n(.$>=3 .ne \\$3
|
||||
.el .ne 3
|
||||
.IP "\\$1" \\$2
|
||||
..
|
||||
.TH "RPCCLIENT" 1 "" "" ""
|
||||
.SH NAME
|
||||
rpcclient \- tool for executing client side MS-RPC functions
|
||||
.SH SYNOPSIS
|
||||
rpcclient \- tool for executing client side MS-RPC functions
|
||||
.SH "SYNOPSIS"
|
||||
|
||||
\fBrpcclient\fR [ \fB-A authfile\fR ] [ \fB-c <command string>\fR ] [ \fB-d debuglevel\fR ] [ \fB-h\fR ] [ \fB-l logfile\fR ] [ \fB-N\fR ] [ \fB-s <smb config file>\fR ] [ \fB-U username[%password]\fR ] [ \fB-W workgroup\fR ] [ \fB-N\fR ] [ \fB-I destinationIP\fR ] \fBserver\fR
|
||||
.nf
|
||||
\fBrpcclient\fR [-A authfile] [-c <command string>] [-d debuglevel] [-h] [-l logfile]
|
||||
[-N] [-s <smb config file>] [-U username[%password]] [-W workgroup]
|
||||
[-N] [-I destinationIP] {server}
|
||||
.fi
|
||||
|
||||
.SH "DESCRIPTION"
|
||||
|
||||
.PP
|
||||
This tool is part of the \fBSamba\fR(7) suite.
|
||||
This tool is part of the \fBSamba\fR(7) suite\&.
|
||||
|
||||
.PP
|
||||
\fBrpcclient\fR is a utility initially developed
|
||||
to test MS-RPC functionality in Samba itself. It has undergone
|
||||
several stages of development and stability. Many system administrators
|
||||
have now written scripts around it to manage Windows NT clients from
|
||||
their UNIX workstation.
|
||||
\fBrpcclient\fR is a utility initially developed to test MS-RPC functionality in Samba itself\&. It has undergone several stages of development and stability\&. Many system administrators have now written scripts around it to manage Windows NT clients from their UNIX workstation\&.
|
||||
|
||||
.SH "OPTIONS"
|
||||
.TP
|
||||
\fBserver\fR
|
||||
NetBIOS name of Server to which to connect.
|
||||
The server can be any SMB/CIFS server. The name is
|
||||
resolved using the \fIname resolve order\fR line from \fBsmb.conf\fR(5).
|
||||
.TP
|
||||
\fB-c|--command='command string'\fR
|
||||
execute semicolon separated commands (listed
|
||||
below))
|
||||
.TP
|
||||
\fB-I IP-address\fR
|
||||
\fIIP address\fR is the address of the server to connect to.
|
||||
It should be specified in standard "a.b.c.d" notation.
|
||||
|
||||
Normally the client would attempt to locate a named
|
||||
SMB/CIFS server by looking it up via the NetBIOS name resolution
|
||||
mechanism described above in the \fIname resolve order\fR
|
||||
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.
|
||||
.TP
|
||||
server
|
||||
NetBIOS name of Server to which to connect\&. The server can be any SMB/CIFS server\&. The name is resolved using the \fIname resolve order\fR line from \fBsmb.conf\fR(5)\&.
|
||||
|
||||
There is no default for this parameter. If not supplied,
|
||||
it will be determined automatically by the client as described
|
||||
above.
|
||||
.TP
|
||||
\fB-V\fR
|
||||
Prints the version number for
|
||||
\fBsmbd\fR.
|
||||
.TP
|
||||
\fB-s <configuration file>\fR
|
||||
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 \fIsmb.conf(5)\fR for more information.
|
||||
The default configuration file name is determined at
|
||||
compile time.
|
||||
.TP
|
||||
\fB-d|--debug=debuglevel\fR
|
||||
\fIdebuglevel\fR is an integer
|
||||
from 0 to 10. The default value if this parameter is
|
||||
not specified is zero.
|
||||
|
||||
The higher this value, the more detail will be
|
||||
logged to the log files about the activities of the
|
||||
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.
|
||||
.TP
|
||||
-c|--command='command string'
|
||||
execute semicolon separated commands (listed below))
|
||||
|
||||
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.
|
||||
|
||||
Note that specifying this parameter here will
|
||||
override the log
|
||||
level file.
|
||||
.TP
|
||||
\fB-l|--logfile=logbasename\fR
|
||||
File name for log/debug files. The extension
|
||||
".client" will be appended. The log file is
|
||||
never removed by the client.
|
||||
.TP
|
||||
\fB-N\fR
|
||||
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.
|
||||
-I IP-address
|
||||
\fIIP address\fR is the address of the server to connect to\&. It should be specified in standard "a\&.b\&.c\&.d" notation\&.
|
||||
|
||||
|
||||
Normally the client would attempt to locate a named SMB/CIFS server by looking it up via the NetBIOS name resolution mechanism described above in the \fIname resolve order\fR parameter above\&. Using this parameter will force the client to assume that the server is on the machine with the specified IP address and the NetBIOS name component of the resource being connected to will be ignored\&.
|
||||
|
||||
|
||||
There is no default for this parameter\&. If not supplied, it will be determined automatically by the client as described above\&.
|
||||
|
||||
|
||||
Unless a password is specified on the command line or
|
||||
this parameter is specified, the client will request a
|
||||
password.
|
||||
.TP
|
||||
\fB-k\fR
|
||||
Try to authenticate with kerberos. Only useful in
|
||||
an Active Directory environment.
|
||||
-V
|
||||
Prints the version number for \fBsmbd\fR\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-A|--authfile=filename\fR
|
||||
This option allows
|
||||
you to specify a file from which to read the username and
|
||||
password used in the connection. The format of the file is
|
||||
-s <configuration file>
|
||||
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 \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
|
||||
|
||||
|
||||
.TP
|
||||
-d|--debug=debuglevel
|
||||
\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
|
||||
|
||||
|
||||
The higher this value, the more detail will be logged to the log files about the activities of the 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\&.
|
||||
|
||||
|
||||
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\&.
|
||||
|
||||
|
||||
Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&.
|
||||
|
||||
|
||||
.TP
|
||||
-l|--logfile=logbasename
|
||||
File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&.
|
||||
|
||||
|
||||
.TP
|
||||
-N
|
||||
If specified, this parameter suppresses the normal password prompt from the client to the user\&. This is useful when accessing a service that does not require a password\&.
|
||||
|
||||
|
||||
Unless a password is specified on the command line or this parameter is specified, the client will request a password\&.
|
||||
|
||||
|
||||
.TP
|
||||
-k
|
||||
Try to authenticate with kerberos\&. Only useful in an Active Directory environment\&.
|
||||
|
||||
|
||||
.TP
|
||||
-A|--authfile=filename
|
||||
This option allows you to specify a file from which to read the username and password used in the connection\&. The format of the file is
|
||||
|
||||
|
||||
.nf
|
||||
|
||||
username = <value>
|
||||
password = <value>
|
||||
domain = <value>
|
||||
.fi
|
||||
|
||||
Make certain that the permissions on the file restrict
|
||||
access from unwanted users.
|
||||
.TP
|
||||
\fB-U|--user=username[%password]\fR
|
||||
Sets the SMB username or username and password.
|
||||
|
||||
If %password is not specified, the user will be prompted. The
|
||||
client will first check the \fBUSER\fR environment variable, then the
|
||||
\fBLOGNAME\fR variable and if either exists, the
|
||||
string is uppercased. If these environmental variables are not
|
||||
found, the username GUEST is used.
|
||||
Make certain that the permissions on the file restrict access from unwanted users\&.
|
||||
|
||||
A third option is to use a credentials file which
|
||||
contains the plaintext of the username and password. This
|
||||
option is mainly provided for scripts where the admin does not
|
||||
wish to pass the credentials on the command line or via environment
|
||||
variables. If this method is used, make certain that the permissions
|
||||
on the file restrict access from unwanted users. See the
|
||||
\fI-A\fR for more details.
|
||||
|
||||
Be cautious about including passwords in scripts. Also, on
|
||||
many systems the command line of a running process may be seen
|
||||
via the \fBps\fR command. To be safe always allow
|
||||
\fBrpcclient\fR to prompt for a password and type
|
||||
it in directly.
|
||||
.TP
|
||||
\fB-n <primary NetBIOS name>\fR
|
||||
This option allows you to override
|
||||
the NetBIOS name that Samba uses for itself. This is identical
|
||||
to setting the \fINetBIOS
|
||||
name\fR parameter in the \fBsmb.conf\fR(5) file. However, a command
|
||||
line setting will take precedence over settings in
|
||||
\fBsmb.conf\fR(5).
|
||||
-U|--user=username[%password]
|
||||
Sets the SMB username or username and password\&.
|
||||
|
||||
|
||||
If %password is not specified, the user will be prompted\&. The client will first check the \fBUSER\fR environment variable, then the \fBLOGNAME\fR variable and if either exists, the string is uppercased\&. If these environmental variables are not found, the username \fBGUEST\fR is used\&.
|
||||
|
||||
|
||||
A third option is to use a credentials file which contains the plaintext of the username and password\&. This option is mainly provided for scripts where the admin does not wish to pass the credentials on the command line or via environment variables\&. If this method is used, make certain that the permissions on the file restrict access from unwanted users\&. See the \fI-A\fR for more details\&.
|
||||
|
||||
|
||||
Be cautious about including passwords in scripts\&. Also, on many systems the command line of a running process may be seen via the \fBps\fR command\&. To be safe always allow \fBrpcclient\fR to prompt for a password and type it in directly\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-i <scope>\fR
|
||||
This specifies a NetBIOS scope that
|
||||
\fBnmblookup\fR 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
|
||||
\fBvery\fR rarely used, only set this parameter
|
||||
if you are the system administrator in charge of all the
|
||||
NetBIOS systems you communicate with.
|
||||
-n <primary NetBIOS name>
|
||||
This option allows you to override the NetBIOS name that Samba uses for itself\&. This is identical to setting the \fINetBIOS name\fR parameter in the \fBsmb.conf\fR(5) file\&. However, a command line setting will take precedence over settings in \fBsmb.conf\fR(5)\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-W|--workgroup=domain\fR
|
||||
Set the SMB domain of the username. This
|
||||
overrides the default domain which is the domain defined in
|
||||
smb.conf. If the domain specified is the same as the servers
|
||||
NetBIOS name, it causes the client to log on using the servers local
|
||||
SAM (as opposed to the Domain SAM).
|
||||
-i <scope>
|
||||
This specifies a NetBIOS scope that \fBnmblookup\fR 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 \fBvery\fR rarely used, only set this parameter if you are the system administrator in charge of all the NetBIOS systems you communicate with\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-O socket options\fR
|
||||
TCP socket options to set on the client
|
||||
socket. See the socket options parameter in
|
||||
the \fBsmb.conf\fR(5) manual page for the list of valid
|
||||
options.
|
||||
-W|--workgroup=domain
|
||||
Set the SMB domain of the username\&. This overrides the default domain which is the domain defined in smb\&.conf\&. If the domain specified is the same as the servers NetBIOS name, it causes the client to log on using the servers local SAM (as opposed to the Domain SAM)\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-h|--help\fR
|
||||
Print a summary of command line options.
|
||||
-O socket options
|
||||
TCP socket options to set on the client socket\&. See the socket options parameter in the \fBsmb.conf\fR(5) manual page for the list of valid options\&.
|
||||
|
||||
|
||||
.TP
|
||||
-h|--help
|
||||
Print a summary of command line options\&.
|
||||
|
||||
|
||||
.SH "COMMANDS"
|
||||
|
||||
.SS "LSARPC"
|
||||
|
||||
.TP
|
||||
\fBlsaquery\fR
|
||||
lsaquery
|
||||
Query info policy
|
||||
|
||||
|
||||
.TP
|
||||
\fBlookupsids\fR
|
||||
Resolve a list
|
||||
of SIDs to usernames.
|
||||
lookupsids
|
||||
Resolve a list of SIDs to usernames\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBlookupnames\fR
|
||||
Resolve a list
|
||||
of usernames to SIDs.
|
||||
lookupnames
|
||||
Resolve a list of usernames to SIDs\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBenumtrusts\fR
|
||||
enumtrusts
|
||||
Enumerate trusted domains
|
||||
|
||||
|
||||
.TP
|
||||
\fBenumprivs\fR
|
||||
enumprivs
|
||||
Enumerate privileges
|
||||
|
||||
|
||||
.TP
|
||||
\fBgetdispname\fR
|
||||
getdispname
|
||||
Get the privilege name
|
||||
|
||||
|
||||
.TP
|
||||
\fBlsaenumsid\fR
|
||||
lsaenumsid
|
||||
Enumerate the LSA SIDS
|
||||
|
||||
|
||||
.TP
|
||||
\fBlsaenumprivsaccount\fR
|
||||
lsaenumprivsaccount
|
||||
Enumerate the privileges of an SID
|
||||
|
||||
|
||||
.TP
|
||||
\fBlsaenumacctrights\fR
|
||||
lsaenumacctrights
|
||||
Enumerate the rights of an SID
|
||||
|
||||
|
||||
.TP
|
||||
\fBlsaenumacctwithright\fR
|
||||
lsaenumacctwithright
|
||||
Enumerate accounts with a right
|
||||
|
||||
|
||||
.TP
|
||||
\fBlsaaddacctrights\fR
|
||||
lsaaddacctrights
|
||||
Add rights to an account
|
||||
|
||||
|
||||
.TP
|
||||
\fBlsaremoveacctrights\fR
|
||||
lsaremoveacctrights
|
||||
Remove rights from an account
|
||||
|
||||
|
||||
.TP
|
||||
\fBlsalookupprivvalue\fR
|
||||
lsalookupprivvalue
|
||||
Get a privilege value given its name
|
||||
|
||||
|
||||
.TP
|
||||
\fBlsaquerysecobj\fR
|
||||
lsaquerysecobj
|
||||
Query LSA security object
|
||||
|
||||
|
||||
.SS "LSARPC-DS"
|
||||
|
||||
.TP
|
||||
\fBdsroledominfo\fR
|
||||
dsroledominfo
|
||||
Get Primary Domain Information
|
||||
|
||||
|
||||
.PP
|
||||
|
||||
|
||||
.PP
|
||||
\fBDFS\fR
|
||||
|
||||
.TP
|
||||
\fBdfsexist\fR
|
||||
dfsexist
|
||||
Query DFS support
|
||||
|
||||
|
||||
.TP
|
||||
\fBdfsadd\fR
|
||||
dfsadd
|
||||
Add a DFS share
|
||||
|
||||
|
||||
.TP
|
||||
\fBdfsremove\fR
|
||||
dfsremove
|
||||
Remove a DFS share
|
||||
|
||||
|
||||
.TP
|
||||
\fBdfsgetinfo\fR
|
||||
dfsgetinfo
|
||||
Query DFS share info
|
||||
|
||||
|
||||
.TP
|
||||
\fBdfsenum\fR
|
||||
dfsenum
|
||||
Enumerate dfs shares
|
||||
|
||||
|
||||
.SS "REG"
|
||||
|
||||
.TP
|
||||
\fBshutdown\fR
|
||||
shutdown
|
||||
Remote Shutdown
|
||||
|
||||
|
||||
.TP
|
||||
\fBabortshutdown\fR
|
||||
abortshutdown
|
||||
Abort Shutdown
|
||||
|
||||
|
||||
.SS "SRVSVC"
|
||||
|
||||
.TP
|
||||
\fBsrvinfo\fR
|
||||
srvinfo
|
||||
Server query info
|
||||
|
||||
|
||||
.TP
|
||||
\fBnetshareenum\fR
|
||||
netshareenum
|
||||
Enumerate shares
|
||||
|
||||
|
||||
.TP
|
||||
\fBnetfileenum\fR
|
||||
netfileenum
|
||||
Enumerate open files
|
||||
|
||||
|
||||
.TP
|
||||
\fBnetremotetod\fR
|
||||
netremotetod
|
||||
Fetch remote time of day
|
||||
|
||||
|
||||
.SS "SAMR"
|
||||
|
||||
.TP
|
||||
\fBqueryuser\fR
|
||||
queryuser
|
||||
Query user info
|
||||
|
||||
|
||||
.TP
|
||||
\fBquerygroup\fR
|
||||
querygroup
|
||||
Query group info
|
||||
|
||||
|
||||
.TP
|
||||
\fBqueryusergroups\fR
|
||||
queryusergroups
|
||||
Query user groups
|
||||
|
||||
|
||||
.TP
|
||||
\fBquerygroupmem\fR
|
||||
querygroupmem
|
||||
Query group membership
|
||||
|
||||
|
||||
.TP
|
||||
\fBqueryaliasmem\fR
|
||||
queryaliasmem
|
||||
Query alias membership
|
||||
|
||||
|
||||
.TP
|
||||
\fBquerydispinfo\fR
|
||||
querydispinfo
|
||||
Query display info
|
||||
|
||||
|
||||
.TP
|
||||
\fBquerydominfo\fR
|
||||
querydominfo
|
||||
Query domain info
|
||||
|
||||
|
||||
.TP
|
||||
\fBenumdomusers\fR
|
||||
enumdomusers
|
||||
Enumerate domain users
|
||||
|
||||
|
||||
.TP
|
||||
\fBenumdomgroups\fR
|
||||
enumdomgroups
|
||||
Enumerate domain groups
|
||||
|
||||
|
||||
.TP
|
||||
\fBenumalsgroups\fR
|
||||
enumalsgroups
|
||||
Enumerate alias groups
|
||||
|
||||
|
||||
.TP
|
||||
\fBcreatedomuser\fR
|
||||
createdomuser
|
||||
Create domain user
|
||||
|
||||
|
||||
.TP
|
||||
\fBsamlookupnames\fR
|
||||
samlookupnames
|
||||
Look up names
|
||||
|
||||
|
||||
.TP
|
||||
\fBsamlookuprids\fR
|
||||
samlookuprids
|
||||
Look up names
|
||||
|
||||
|
||||
.TP
|
||||
\fBdeletedomuser\fR
|
||||
deletedomuser
|
||||
Delete domain user
|
||||
|
||||
|
||||
.TP
|
||||
\fBsamquerysecobj\fR
|
||||
samquerysecobj
|
||||
Query SAMR security object
|
||||
|
||||
|
||||
.TP
|
||||
\fBgetdompwinfo\fR
|
||||
getdompwinfo
|
||||
Retrieve domain password info
|
||||
|
||||
|
||||
.TP
|
||||
\fBlookupdomain\fR
|
||||
lookupdomain
|
||||
Look up domain
|
||||
|
||||
|
||||
.SS "SPOOLSS"
|
||||
|
||||
.TP
|
||||
\fBadddriver <arch> <config>\fR
|
||||
Execute an AddPrinterDriver() RPC to install the printer driver
|
||||
information on the server. Note that the driver files should
|
||||
already exist in the directory returned by
|
||||
\fBgetdriverdir\fR. Possible values for
|
||||
\fIarch\fR are the same as those for
|
||||
the \fBgetdriverdir\fR command.
|
||||
The \fIconfig\fR parameter is defined as
|
||||
follows:
|
||||
adddriver <arch> <config>
|
||||
Execute an AddPrinterDriver() RPC to install the printer driver information on the server\&. Note that the driver files should already exist in the directory returned by \fBgetdriverdir\fR\&. Possible values for \fIarch\fR are the same as those for the \fBgetdriverdir\fR command\&. The \fIconfig\fR parameter is defined as follows:
|
||||
|
||||
|
||||
.nf
|
||||
|
||||
Long Printer Name:\\
|
||||
Driver File Name:\\
|
||||
Data File Name:\\
|
||||
@ -335,193 +408,209 @@ Default Data Type:\\
|
||||
Comma Separated list of Files
|
||||
.fi
|
||||
|
||||
Any empty fields should be enter as the string "NULL".
|
||||
|
||||
Samba does not need to support the concept of Print Monitors
|
||||
since these only apply to local printers whose driver can make
|
||||
use of a bi-directional link for communication. This field should
|
||||
be "NULL". On a remote NT print server, the Print Monitor for a
|
||||
driver must already be installed prior to adding the driver or
|
||||
else the RPC will fail.
|
||||
Any empty fields should be enter as the string "NULL"\&.
|
||||
|
||||
|
||||
Samba does not need to support the concept of Print Monitors since these only apply to local printers whose driver can make use of a bi-directional link for communication\&. This field should be "NULL"\&. On a remote NT print server, the Print Monitor for a driver must already be installed prior to adding the driver or else the RPC will fail\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBaddprinter <printername> <sharename> <drivername> <port>\fR
|
||||
Add a printer on the remote server. This printer
|
||||
will be automatically shared. Be aware that the printer driver
|
||||
must already be installed on the server (see \fBadddriver\fR)
|
||||
and the \fIport\fRmust be a valid port name (see
|
||||
\fBenumports\fR.
|
||||
addprinter <printername> <sharename> <drivername> <port>
|
||||
Add a printer on the remote server\&. This printer will be automatically shared\&. Be aware that the printer driver must already be installed on the server (see \fBadddriver\fR) and the \fIport\fRmust be a valid port name (see \fBenumports\fR\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBdeldriver\fR
|
||||
Delete the
|
||||
specified printer driver for all architectures. This
|
||||
does not delete the actual driver files from the server,
|
||||
only the entry from the server's list of drivers.
|
||||
deldriver
|
||||
Delete the specified printer driver for all architectures\&. This does not delete the actual driver files from the server, only the entry from the server's list of drivers\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBenumdata\fR
|
||||
Enumerate all
|
||||
printer setting data stored on the server. On Windows NT clients,
|
||||
these values are stored in the registry, while Samba servers
|
||||
store them in the printers TDB. This command corresponds
|
||||
to the MS Platform SDK GetPrinterData() function (* This
|
||||
command is currently unimplemented).
|
||||
enumdata
|
||||
Enumerate all printer setting data stored on the server\&. On Windows NT clients, these values are stored in the registry, while Samba servers store them in the printers TDB\&. This command corresponds to the MS Platform SDK GetPrinterData() function (* This command is currently unimplemented)\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBenumdataex\fR
|
||||
enumdataex
|
||||
Enumerate printer data for a key
|
||||
.TP
|
||||
\fBenumjobs <printer>\fR
|
||||
List the jobs and status of a given printer.
|
||||
This command corresponds to the MS Platform SDK EnumJobs()
|
||||
function
|
||||
.TP
|
||||
\fBenumkey\fR
|
||||
Enumerate printer keys
|
||||
.TP
|
||||
\fBenumports [level]\fR
|
||||
Executes an EnumPorts() call using the specified
|
||||
info level. Currently only info levels 1 and 2 are supported.
|
||||
.TP
|
||||
\fBenumdrivers [level]\fR
|
||||
Execute an EnumPrinterDrivers() call. This lists the various installed
|
||||
printer drivers for all architectures. Refer to the MS Platform SDK
|
||||
documentation for more details of the various flags and calling
|
||||
options. Currently supported info levels are 1, 2, and 3.
|
||||
.TP
|
||||
\fBenumprinters [level]\fR
|
||||
Execute an EnumPrinters() call. This lists the various installed
|
||||
and share printers. Refer to the MS Platform SDK documentation for
|
||||
more details of the various flags and calling options. Currently
|
||||
supported info levels are 0, 1, and 2.
|
||||
.TP
|
||||
\fBgetdata <printername> <valuename;>\fR
|
||||
Retrieve the data for a given printer setting. See
|
||||
the \fBenumdata\fR command for more information.
|
||||
This command corresponds to the GetPrinterData() MS Platform
|
||||
SDK function.
|
||||
.TP
|
||||
\fBgetdataex\fR
|
||||
Get printer driver data with keyname
|
||||
.TP
|
||||
\fBgetdriver <printername>\fR
|
||||
Retrieve the printer driver information (such as driver file,
|
||||
config file, dependent files, etc...) for
|
||||
the given printer. This command corresponds to the GetPrinterDriver()
|
||||
MS Platform SDK function. Currently info level 1, 2, and 3 are supported.
|
||||
.TP
|
||||
\fBgetdriverdir <arch>\fR
|
||||
Execute a GetPrinterDriverDirectory()
|
||||
RPC to retrieve the SMB share name and subdirectory for
|
||||
storing printer driver files for a given architecture. Possible
|
||||
values for \fIarch\fR are "Windows 4.0"
|
||||
(for Windows 95/98), "Windows NT x86", "Windows NT PowerPC", "Windows
|
||||
Alpha_AXP", and "Windows NT R4000".
|
||||
.TP
|
||||
\fBgetprinter <printername>\fR
|
||||
Retrieve the current printer information. This command
|
||||
corresponds to the GetPrinter() MS Platform SDK function.
|
||||
.TP
|
||||
\fBgetprintprocdir\fR
|
||||
Get print processor directory
|
||||
.TP
|
||||
\fBopenprinter <printername>\fR
|
||||
Execute an OpenPrinterEx() and ClosePrinter() RPC
|
||||
against a given printer.
|
||||
.TP
|
||||
\fBsetdriver <printername> <drivername>\fR
|
||||
Execute a SetPrinter() command to update the printer driver
|
||||
associated with an installed printer. The printer driver must
|
||||
already be correctly installed on the print server.
|
||||
|
||||
See also the \fBenumprinters\fR and
|
||||
\fBenumdrivers\fR commands for obtaining a list of
|
||||
of installed printers and drivers.
|
||||
|
||||
.TP
|
||||
\fBaddform\fR
|
||||
enumjobs <printer>
|
||||
List the jobs and status of a given printer\&. This command corresponds to the MS Platform SDK EnumJobs() function
|
||||
|
||||
|
||||
.TP
|
||||
enumkey
|
||||
Enumerate printer keys
|
||||
|
||||
|
||||
.TP
|
||||
enumports [level]
|
||||
Executes an EnumPorts() call using the specified info level\&. Currently only info levels 1 and 2 are supported\&.
|
||||
|
||||
|
||||
.TP
|
||||
enumdrivers [level]
|
||||
Execute an EnumPrinterDrivers() call\&. This lists the various installed printer drivers for all architectures\&. Refer to the MS Platform SDK documentation for more details of the various flags and calling options\&. Currently supported info levels are 1, 2, and 3\&.
|
||||
|
||||
|
||||
.TP
|
||||
enumprinters [level]
|
||||
Execute an EnumPrinters() call\&. This lists the various installed and share printers\&. Refer to the MS Platform SDK documentation for more details of the various flags and calling options\&. Currently supported info levels are 0, 1, and 2\&.
|
||||
|
||||
|
||||
.TP
|
||||
getdata <printername> <valuename;>
|
||||
Retrieve the data for a given printer setting\&. See the \fBenumdata\fR command for more information\&. This command corresponds to the GetPrinterData() MS Platform SDK function\&.
|
||||
|
||||
|
||||
.TP
|
||||
getdataex
|
||||
Get printer driver data with keyname
|
||||
|
||||
|
||||
.TP
|
||||
getdriver <printername>
|
||||
Retrieve the printer driver information (such as driver file, config file, dependent files, etc\&.\&.\&.) for the given printer\&. This command corresponds to the GetPrinterDriver() MS Platform SDK function\&. Currently info level 1, 2, and 3 are supported\&.
|
||||
|
||||
|
||||
.TP
|
||||
getdriverdir <arch>
|
||||
Execute a GetPrinterDriverDirectory() RPC to retrieve the SMB share name and subdirectory for storing printer driver files for a given architecture\&. Possible values for \fIarch\fR are "Windows 4\&.0" (for Windows 95/98), "Windows NT x86", "Windows NT PowerPC", "Windows Alpha_AXP", and "Windows NT R4000"\&.
|
||||
|
||||
|
||||
.TP
|
||||
getprinter <printername>
|
||||
Retrieve the current printer information\&. This command corresponds to the GetPrinter() MS Platform SDK function\&.
|
||||
|
||||
|
||||
.TP
|
||||
getprintprocdir
|
||||
Get print processor directory
|
||||
|
||||
|
||||
.TP
|
||||
openprinter <printername>
|
||||
Execute an OpenPrinterEx() and ClosePrinter() RPC against a given printer\&.
|
||||
|
||||
|
||||
.TP
|
||||
setdriver <printername> <drivername>
|
||||
Execute a SetPrinter() command to update the printer driver associated with an installed printer\&. The printer driver must already be correctly installed on the print server\&.
|
||||
|
||||
|
||||
See also the \fBenumprinters\fR and \fBenumdrivers\fR commands for obtaining a list of of installed printers and drivers\&.
|
||||
|
||||
|
||||
.TP
|
||||
addform
|
||||
Add form
|
||||
|
||||
|
||||
.TP
|
||||
\fBsetform\fR
|
||||
setform
|
||||
Set form
|
||||
|
||||
|
||||
.TP
|
||||
\fBgetform\fR
|
||||
getform
|
||||
Get form
|
||||
|
||||
|
||||
.TP
|
||||
\fBdeleteform\fR
|
||||
deleteform
|
||||
Delete form
|
||||
|
||||
|
||||
.TP
|
||||
\fBenumforms\fR
|
||||
enumforms
|
||||
Enumerate form
|
||||
|
||||
|
||||
.TP
|
||||
\fBsetprinter\fR
|
||||
setprinter
|
||||
Set printer comment
|
||||
|
||||
|
||||
.TP
|
||||
\fBsetprinterdata\fR
|
||||
setprinterdata
|
||||
Set REG_SZ printer data
|
||||
|
||||
|
||||
.TP
|
||||
\fBrffpcnex\fR
|
||||
rffpcnex
|
||||
Rffpcnex test
|
||||
|
||||
|
||||
.SS "NETLOGON"
|
||||
|
||||
.TP
|
||||
\fBlogonctrl2\fR
|
||||
logonctrl2
|
||||
Logon Control 2
|
||||
|
||||
|
||||
.TP
|
||||
\fBlogonctrl\fR
|
||||
logonctrl
|
||||
Logon Control
|
||||
|
||||
|
||||
.TP
|
||||
\fBsamsync\fR
|
||||
samsync
|
||||
Sam Synchronisation
|
||||
|
||||
|
||||
.TP
|
||||
\fBsamdeltas\fR
|
||||
samdeltas
|
||||
Query Sam Deltas
|
||||
|
||||
|
||||
.TP
|
||||
\fBsamlogon\fR
|
||||
samlogon
|
||||
Sam Logon
|
||||
|
||||
|
||||
.SS "GENERAL COMMANDS"
|
||||
|
||||
.TP
|
||||
\fBdebuglevel\fR
|
||||
Set the current
|
||||
debug level used to log information.
|
||||
debuglevel
|
||||
Set the current debug level used to log information\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBhelp (?)\fR
|
||||
Print a listing of all
|
||||
known commands or extended help on a particular command.
|
||||
help (?)
|
||||
Print a listing of all known commands or extended help on a particular command\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBquit (exit)\fR
|
||||
Exit \fBrpcclient
|
||||
\fR.
|
||||
quit (exit)
|
||||
Exit \fBrpcclient \fR\&.
|
||||
|
||||
|
||||
.SH "BUGS"
|
||||
|
||||
.PP
|
||||
\fBrpcclient\fR is designed as a developer testing tool
|
||||
and may not be robust in certain areas (such as command line parsing).
|
||||
It has been known to generate a core dump upon failures when invalid
|
||||
parameters where passed to the interpreter.
|
||||
\fBrpcclient\fR is designed as a developer testing tool and may not be robust in certain areas (such as command line parsing)\&. It has been known to generate a core dump upon failures when invalid parameters where passed to the interpreter\&.
|
||||
|
||||
.PP
|
||||
From Luke Leighton's original rpcclient man page:
|
||||
|
||||
.PP
|
||||
\fBWARNING!\fR The MSRPC over SMB code has
|
||||
been developed from examining Network traces. No documentation is
|
||||
available from the original creators (Microsoft) on how MSRPC over
|
||||
SMB works, or how the individual MSRPC services work. Microsoft's
|
||||
implementation of these services has been demonstrated (and reported)
|
||||
to be... a bit flaky in places.
|
||||
\fBWARNING!\fR The MSRPC over SMB code has been developed from examining Network traces\&. No documentation is available from the original creators (Microsoft) on how MSRPC over SMB works, or how the individual MSRPC services work\&. Microsoft's implementation of these services has been demonstrated (and reported) to be\&.\&.\&. a bit flaky in places\&.
|
||||
|
||||
.PP
|
||||
The development of Samba's implementation is also a bit rough,
|
||||
and as more of the services are understood, it can even result in
|
||||
versions of \fBsmbd\fR(8) and \fBrpcclient\fR(1) that are incompatible for some commands or services. Additionally,
|
||||
the developers are sending reports to Microsoft, and problems found
|
||||
or reported to Microsoft are fixed in Service Packs, which may
|
||||
result in incompatibilities.
|
||||
The development of Samba's implementation is also a bit rough, and as more of the services are understood, it can even result in versions of \fBsmbd\fR(8) and \fBrpcclient\fR(1) that are incompatible for some commands or services\&. Additionally, the developers are sending reports to Microsoft, and problems found or reported to Microsoft are fixed in Service Packs, which may result in incompatibilities\&.
|
||||
|
||||
.SH "VERSION"
|
||||
|
||||
.PP
|
||||
This man page is correct for version 3.0 of the Samba
|
||||
suite.
|
||||
This man page is correct for version 3\&.0 of the Samba suite\&.
|
||||
|
||||
.SH "AUTHOR"
|
||||
|
||||
.PP
|
||||
The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.
|
||||
The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
|
||||
|
||||
.PP
|
||||
The original rpcclient man page was written by Matthew
|
||||
Geddes, Luke Kenneth Casson Leighton, and rewritten by Gerald Carter.
|
||||
The conversion to DocBook for Samba 2.2 was done by Gerald
|
||||
Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was
|
||||
done by Alexander Bokovoy.
|
||||
The original rpcclient man page was written by Matthew Geddes, Luke Kenneth Casson Leighton, and rewritten by Gerald Carter\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
|
||||
|
||||
|
||||
11277
docs/manpages/smb.conf.5
11277
docs/manpages/smb.conf.5
File diff suppressed because it is too large
Load Diff
@ -1,127 +1,135 @@
|
||||
.\" This manpage has been automatically generated by docbook2man
|
||||
.\" from a DocBook document. This tool can be found at:
|
||||
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
||||
.\" Please send any bug reports, improvements, comments, patches,
|
||||
.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
||||
.TH "SMBCACLS" "1" "19 april 2003" "" ""
|
||||
|
||||
.\"Generated by db2man.xsl. Don't modify this, modify the source.
|
||||
.de Sh \" Subsection
|
||||
.br
|
||||
.if t .Sp
|
||||
.ne 5
|
||||
.PP
|
||||
\fB\\$1\fR
|
||||
.PP
|
||||
..
|
||||
.de Sp \" Vertical space (when we can't use .PP)
|
||||
.if t .sp .5v
|
||||
.if n .sp
|
||||
..
|
||||
.de Ip \" List item
|
||||
.br
|
||||
.ie \\n(.$>=3 .ne \\$3
|
||||
.el .ne 3
|
||||
.IP "\\$1" \\$2
|
||||
..
|
||||
.TH "SMBCACLS" 1 "" "" ""
|
||||
.SH NAME
|
||||
smbcacls \- Set or get ACLs on an NT file or directory names
|
||||
.SH SYNOPSIS
|
||||
.SH "SYNOPSIS"
|
||||
|
||||
\fBsmbcacls\fR \fB//server/share\fR \fBfilename\fR [ \fB-D acls\fR ] [ \fB-M acls\fR ] [ \fB-A acls\fR ] [ \fB-S acls\fR ] [ \fB-C name\fR ] [ \fB-G name\fR ] [ \fB-n\fR ] [ \fB-t\fR ] [ \fB-U username\fR ] [ \fB-h\fR ] [ \fB-d\fR ]
|
||||
.nf
|
||||
\fBsmbcacls\fR {//server/share} {filename} [-D acls] [-M acls] [-A acls] [-S acls] [-C name] [-G name] [-n] [-t] [-U username] [-h] [-d]
|
||||
|
||||
.fi
|
||||
|
||||
.SH "DESCRIPTION"
|
||||
|
||||
.PP
|
||||
This tool is part of the \fBSamba\fR(7) suite.
|
||||
This tool is part of the \fBSamba\fR(7) suite\&.
|
||||
|
||||
.PP
|
||||
The \fBsmbcacls\fR program manipulates NT Access Control
|
||||
Lists (ACLs) on SMB file shares.
|
||||
The \fBsmbcacls\fR program manipulates NT Access Control Lists (ACLs) on SMB file shares\&.
|
||||
|
||||
.SH "OPTIONS"
|
||||
|
||||
.PP
|
||||
The following options are available to the \fBsmbcacls\fR program.
|
||||
The format of ACLs is described in the section ACL FORMAT
|
||||
.TP
|
||||
\fB-A acls\fR
|
||||
Add the ACLs specified to the ACL list. Existing
|
||||
access control entries are unchanged.
|
||||
.TP
|
||||
\fB-M acls\fR
|
||||
Modify the mask value (permissions) for the ACLs
|
||||
specified on the command line. An error will be printed for each
|
||||
ACL specified that was not already present in the ACL list
|
||||
.TP
|
||||
\fB-D acls\fR
|
||||
Delete any ACLs specified on the command line.
|
||||
An error will be printed for each ACL specified that was not
|
||||
already present in the ACL list.
|
||||
.TP
|
||||
\fB-S acls\fR
|
||||
This command sets the ACLs on the file with
|
||||
only the ones specified on the command line. All other ACLs are
|
||||
erased. Note that the ACL specified must contain at least a revision,
|
||||
type, owner and group for the call to succeed.
|
||||
.TP
|
||||
\fB-U username\fR
|
||||
Specifies a username used to connect to the
|
||||
specified service. The username may be of the form "username" in
|
||||
which case the user is prompted to enter in a password and the
|
||||
workgroup specified in the \fBsmb.conf\fR(5) file is
|
||||
used, or "username%password" or "DOMAIN\\username%password" and the
|
||||
password and workgroup names are used as provided.
|
||||
.TP
|
||||
\fB-C name\fR
|
||||
The owner of a file or directory can be changed
|
||||
to the name given using the \fI-C\fR option.
|
||||
The name can be a sid in the form S-1-x-y-z or a name resolved
|
||||
against the server specified in the first argument.
|
||||
The following options are available to the \fBsmbcacls\fR program\&. The format of ACLs is described in the section ACL FORMAT
|
||||
|
||||
This command is a shortcut for -M OWNER:name.
|
||||
.TP
|
||||
\fB-G name\fR
|
||||
The group owner of a file or directory can
|
||||
be changed to the name given using the \fI-G\fR
|
||||
option. The name can be a sid in the form S-1-x-y-z or a name
|
||||
resolved against the server specified n the first argument.
|
||||
-A acls
|
||||
Add the ACLs specified to the ACL list\&. Existing access control entries are unchanged\&.
|
||||
|
||||
This command is a shortcut for -M GROUP:name.
|
||||
.TP
|
||||
\fB-n\fR
|
||||
This option displays all ACL information in numeric
|
||||
format. The default is to convert SIDs to names and ACE types
|
||||
and masks to a readable string format.
|
||||
.TP
|
||||
\fB-t\fR
|
||||
Don't actually do anything, only validate the correctness of
|
||||
the arguments.
|
||||
.TP
|
||||
\fB-h|--help\fR
|
||||
Print a summary of command line options.
|
||||
.TP
|
||||
\fB-V\fR
|
||||
Prints the version number for
|
||||
\fBsmbd\fR.
|
||||
.TP
|
||||
\fB-s <configuration file>\fR
|
||||
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 \fIsmb.conf(5)\fR for more information.
|
||||
The default configuration file name is determined at
|
||||
compile time.
|
||||
.TP
|
||||
\fB-d|--debug=debuglevel\fR
|
||||
\fIdebuglevel\fR is an integer
|
||||
from 0 to 10. The default value if this parameter is
|
||||
not specified is zero.
|
||||
|
||||
The higher this value, the more detail will be
|
||||
logged to the log files about the activities of the
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
Note that specifying this parameter here will
|
||||
override the log
|
||||
level file.
|
||||
.TP
|
||||
\fB-l|--logfile=logbasename\fR
|
||||
File name for log/debug files. The extension
|
||||
".client" will be appended. The log file is
|
||||
never removed by the client.
|
||||
-M acls
|
||||
Modify the mask value (permissions) for the ACLs specified on the command line\&. An error will be printed for each ACL specified that was not already present in the ACL list
|
||||
|
||||
|
||||
.TP
|
||||
-D acls
|
||||
Delete any ACLs specified on the command line\&. An error will be printed for each ACL specified that was not already present in the ACL list\&.
|
||||
|
||||
|
||||
.TP
|
||||
-S acls
|
||||
This command sets the ACLs on the file with only the ones specified on the command line\&. All other ACLs are erased\&. Note that the ACL specified must contain at least a revision, type, owner and group for the call to succeed\&.
|
||||
|
||||
|
||||
.TP
|
||||
-U username
|
||||
Specifies a username used to connect to the specified service\&. The username may be of the form "username" in which case the user is prompted to enter in a password and the workgroup specified in the \fBsmb.conf\fR(5) file is used, or "username%password" or "DOMAIN\\username%password" and the password and workgroup names are used as provided\&.
|
||||
|
||||
|
||||
.TP
|
||||
-C name
|
||||
The owner of a file or directory can be changed to the name given using the \fI-C\fR option\&. The name can be a sid in the form S-1-x-y-z or a name resolved against the server specified in the first argument\&.
|
||||
|
||||
|
||||
This command is a shortcut for -M OWNER:name\&.
|
||||
|
||||
|
||||
.TP
|
||||
-G name
|
||||
The group owner of a file or directory can be changed to the name given using the \fI-G\fR option\&. The name can be a sid in the form S-1-x-y-z or a name resolved against the server specified n the first argument\&.
|
||||
|
||||
|
||||
This command is a shortcut for -M GROUP:name\&.
|
||||
|
||||
|
||||
.TP
|
||||
-n
|
||||
This option displays all ACL information in numeric format\&. The default is to convert SIDs to names and ACE types and masks to a readable string format\&.
|
||||
|
||||
|
||||
.TP
|
||||
-t
|
||||
Don't actually do anything, only validate the correctness of the arguments\&.
|
||||
|
||||
|
||||
.TP
|
||||
-h|--help
|
||||
Print a summary of command line options\&.
|
||||
|
||||
|
||||
.TP
|
||||
-V
|
||||
Prints the version number for \fBsmbd\fR\&.
|
||||
|
||||
|
||||
.TP
|
||||
-s <configuration file>
|
||||
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 \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
|
||||
|
||||
|
||||
.TP
|
||||
-d|--debug=debuglevel
|
||||
\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
|
||||
|
||||
|
||||
The higher this value, the more detail will be logged to the log files about the activities of the 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\&.
|
||||
|
||||
|
||||
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\&.
|
||||
|
||||
|
||||
Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&.
|
||||
|
||||
|
||||
.TP
|
||||
-l|--logfile=logbasename
|
||||
File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&.
|
||||
|
||||
|
||||
.SH "ACL FORMAT"
|
||||
|
||||
.PP
|
||||
The format of an ACL is one or more ACL entries separated by
|
||||
either commas or newlines. An ACL entry is one of the following:
|
||||
The format of an ACL is one or more ACL entries separated by either commas or newlines\&. An ACL entry is one of the following:
|
||||
|
||||
.PP
|
||||
|
||||
.nf
|
||||
@ -131,102 +139,108 @@ OWNER:<sid or name>
|
||||
GROUP:<sid or name>
|
||||
ACL:<sid or name>:<type>/<flags>/<mask>
|
||||
.fi
|
||||
|
||||
|
||||
.PP
|
||||
The revision of the ACL specifies the internal Windows
|
||||
NT ACL revision for the security descriptor.
|
||||
If not specified it defaults to 1. Using values other than 1 may
|
||||
cause strange behaviour.
|
||||
The revision of the ACL specifies the internal Windows NT ACL revision for the security descriptor\&. If not specified it defaults to 1\&. Using values other than 1 may cause strange behaviour\&.
|
||||
|
||||
.PP
|
||||
The owner and group specify the owner and group sids for the
|
||||
object. If a SID in the format CWS-1-x-y-z is specified this is used,
|
||||
otherwise the name specified is resolved using the server on which
|
||||
the file or directory resides.
|
||||
The owner and group specify the owner and group sids for the object\&. If a SID in the format CWS-1-x-y-z is specified this is used, otherwise the name specified is resolved using the server on which the file or directory resides\&.
|
||||
|
||||
.PP
|
||||
ACLs specify permissions granted to the SID. This SID again
|
||||
can be specified in CWS-1-x-y-z format or as a name in which case
|
||||
it is resolved against the server on which the file or directory
|
||||
resides. The type, flags and mask values determine the type of
|
||||
access granted to the SID.
|
||||
ACLs specify permissions granted to the SID\&. This SID again can be specified in CWS-1-x-y-z format or as a name in which case it is resolved against the server on which the file or directory resides\&. The type, flags and mask values determine the type of access granted to the SID\&.
|
||||
|
||||
.PP
|
||||
The type can be either 0 or 1 corresponding to ALLOWED or
|
||||
DENIED access to the SID. The flags values are generally
|
||||
zero for file ACLs and either 9 or 2 for directory ACLs. Some
|
||||
common flags are:
|
||||
.TP 0.2i
|
||||
The type can be either 0 or 1 corresponding to ALLOWED or DENIED access to the SID\&. The flags values are generally zero for file ACLs and either 9 or 2 for directory ACLs\&. Some common flags are:
|
||||
|
||||
.TP 3
|
||||
\(bu
|
||||
#define SEC_ACE_FLAG_OBJECT_INHERIT 0x1
|
||||
.TP 0.2i
|
||||
\fB#define SEC_ACE_FLAG_OBJECT_INHERIT 0x1\fR
|
||||
|
||||
.TP
|
||||
\(bu
|
||||
#define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2
|
||||
.TP 0.2i
|
||||
\fB#define SEC_ACE_FLAG_CONTAINER_INHERIT 0x2\fR
|
||||
|
||||
.TP
|
||||
\(bu
|
||||
#define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4
|
||||
.TP 0.2i
|
||||
\fB#define SEC_ACE_FLAG_NO_PROPAGATE_INHERIT 0x4\fR
|
||||
|
||||
.TP
|
||||
\(bu
|
||||
#define SEC_ACE_FLAG_INHERIT_ONLY 0x8
|
||||
\fB#define SEC_ACE_FLAG_INHERIT_ONLY 0x8\fR
|
||||
|
||||
.LP
|
||||
|
||||
.PP
|
||||
At present flags can only be specified as decimal or
|
||||
hexadecimal values.
|
||||
At present flags can only be specified as decimal or hexadecimal values\&.
|
||||
|
||||
.PP
|
||||
The mask is a value which expresses the access right
|
||||
granted to the SID. It can be given as a decimal or hexadecimal value,
|
||||
or by using one of the following text strings which map to the NT
|
||||
file permissions of the same name.
|
||||
.TP 0.2i
|
||||
The mask is a value which expresses the access right granted to the SID\&. It can be given as a decimal or hexadecimal value, or by using one of the following text strings which map to the NT file permissions of the same name\&.
|
||||
|
||||
.TP 3
|
||||
\(bu
|
||||
\fBR\fR - Allow read access
|
||||
.TP 0.2i
|
||||
\fBR\fR - Allow read access
|
||||
|
||||
.TP
|
||||
\(bu
|
||||
\fBW\fR - Allow write access
|
||||
.TP 0.2i
|
||||
|
||||
.TP
|
||||
\(bu
|
||||
\fBX\fR - Execute permission on the object
|
||||
.TP 0.2i
|
||||
|
||||
.TP
|
||||
\(bu
|
||||
\fBD\fR - Delete the object
|
||||
.TP 0.2i
|
||||
|
||||
.TP
|
||||
\(bu
|
||||
\fBP\fR - Change permissions
|
||||
.TP 0.2i
|
||||
|
||||
.TP
|
||||
\(bu
|
||||
\fBO\fR - Take ownership
|
||||
|
||||
.LP
|
||||
|
||||
.PP
|
||||
The following combined permissions can be specified:
|
||||
.TP 0.2i
|
||||
|
||||
.TP 3
|
||||
\(bu
|
||||
\fBREAD\fR - Equivalent to 'RX'
|
||||
permissions
|
||||
.TP 0.2i
|
||||
\fBREAD\fR - Equivalent to 'RX' permissions
|
||||
|
||||
.TP
|
||||
\(bu
|
||||
\fBCHANGE\fR - Equivalent to 'RXWD' permissions
|
||||
.TP 0.2i
|
||||
|
||||
.TP
|
||||
\(bu
|
||||
\fBFULL\fR - Equivalent to 'RWXDPO'
|
||||
permissions
|
||||
\fBFULL\fR - Equivalent to 'RWXDPO' permissions
|
||||
|
||||
.LP
|
||||
|
||||
.SH "EXIT STATUS"
|
||||
|
||||
.PP
|
||||
The \fBsmbcacls\fR program sets the exit status
|
||||
depending on the success or otherwise of the operations performed.
|
||||
The exit status may be one of the following values.
|
||||
The \fBsmbcacls\fR program sets the exit status depending on the success or otherwise of the operations performed\&. The exit status may be one of the following values\&.
|
||||
|
||||
.PP
|
||||
If the operation succeeded, smbcacls returns and exit
|
||||
status of 0. If \fBsmbcacls\fR couldn't connect to the specified server,
|
||||
or there was an error getting or setting the ACLs, an exit status
|
||||
of 1 is returned. If there was an error parsing any command line
|
||||
arguments, an exit status of 2 is returned.
|
||||
If the operation succeeded, smbcacls returns and exit status of 0\&. If \fBsmbcacls\fR couldn't connect to the specified server, or there was an error getting or setting the ACLs, an exit status of 1 is returned\&. If there was an error parsing any command line arguments, an exit status of 2 is returned\&.
|
||||
|
||||
.SH "VERSION"
|
||||
|
||||
.PP
|
||||
This man page is correct for version 3.0 of the Samba suite.
|
||||
This man page is correct for version 3\&.0 of the Samba suite\&.
|
||||
|
||||
.SH "AUTHOR"
|
||||
|
||||
.PP
|
||||
The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.
|
||||
The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
|
||||
|
||||
.PP
|
||||
\fBsmbcacls\fR was written by Andrew Tridgell
|
||||
and Tim Potter.
|
||||
\fBsmbcacls\fR was written by Andrew Tridgell and Tim Potter\&.
|
||||
|
||||
.PP
|
||||
The conversion to DocBook for Samba 2.2 was done
|
||||
by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0 was done
|
||||
by Alexander Bokovoy.
|
||||
The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
|
||||
|
||||
|
||||
File diff suppressed because it is too large
Load Diff
@ -1,189 +1,216 @@
|
||||
.\" This manpage has been automatically generated by docbook2man
|
||||
.\" from a DocBook document. This tool can be found at:
|
||||
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
||||
.\" Please send any bug reports, improvements, comments, patches,
|
||||
.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
||||
.TH "SMBCONTROL" "1" "19 april 2003" "" ""
|
||||
|
||||
.\"Generated by db2man.xsl. Don't modify this, modify the source.
|
||||
.de Sh \" Subsection
|
||||
.br
|
||||
.if t .Sp
|
||||
.ne 5
|
||||
.PP
|
||||
\fB\\$1\fR
|
||||
.PP
|
||||
..
|
||||
.de Sp \" Vertical space (when we can't use .PP)
|
||||
.if t .sp .5v
|
||||
.if n .sp
|
||||
..
|
||||
.de Ip \" List item
|
||||
.br
|
||||
.ie \\n(.$>=3 .ne \\$3
|
||||
.el .ne 3
|
||||
.IP "\\$1" \\$2
|
||||
..
|
||||
.TH "SMBCONTROL" 1 "" "" ""
|
||||
.SH NAME
|
||||
smbcontrol \- send messages to smbd, nmbd or winbindd processes
|
||||
.SH SYNOPSIS
|
||||
.SH "SYNOPSIS"
|
||||
|
||||
\fBsmbcontrol\fR [ \fB-i\fR ] [ \fB-s\fR ]
|
||||
.nf
|
||||
\fBsmbcontrol\fR [-i] [-s]
|
||||
.fi
|
||||
|
||||
|
||||
\fBsmbcontrol\fR [ \fBdestination\fR ] [ \fBmessage-type\fR ] [ \fBparameter\fR ]
|
||||
.nf
|
||||
\fBsmbcontrol\fR [destination] [message-type] [parameter]
|
||||
.fi
|
||||
|
||||
.SH "DESCRIPTION"
|
||||
|
||||
.PP
|
||||
This tool is part of the \fBSamba\fR(7) suite.
|
||||
This tool is part of the \fBSamba\fR(7) suite\&.
|
||||
|
||||
.PP
|
||||
\fBsmbcontrol\fR is a very small program, which
|
||||
sends messages to a \fBsmbd\fR(8), a \fBnmbd\fR(8), or a \fBwinbindd\fR(8) daemon running on the system.
|
||||
\fBsmbcontrol\fR is a very small program, which sends messages to a \fBsmbd\fR(8), a \fBnmbd\fR(8), or a \fBwinbindd\fR(8) daemon running on the system\&.
|
||||
|
||||
.SH "OPTIONS"
|
||||
.TP
|
||||
\fB-h|--help\fR
|
||||
Print a summary of command line options.
|
||||
.TP
|
||||
\fB-s <configuration file>\fR
|
||||
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 \fIsmb.conf(5)\fR for more information.
|
||||
The default configuration file name is determined at
|
||||
compile time.
|
||||
.TP
|
||||
\fB-i\fR
|
||||
Run interactively. Individual commands
|
||||
of the form destination message-type parameters can be entered
|
||||
on STDIN. An empty command line or a "q" will quit the
|
||||
program.
|
||||
.TP
|
||||
\fBdestination\fR
|
||||
One of \fInmbd\fR, \fIsmbd\fR or a process ID.
|
||||
|
||||
The \fIsmbd\fR destination causes the
|
||||
message to "broadcast" to all smbd daemons.
|
||||
|
||||
The \fInmbd\fR destination causes the
|
||||
message to be sent to the nmbd daemon specified in the
|
||||
\fInmbd.pid\fR file.
|
||||
|
||||
If a single process ID is given, the message is sent
|
||||
to only that process.
|
||||
.TP
|
||||
\fBmessage-type\fR
|
||||
Type of message to send. See
|
||||
the section MESSAGE-TYPES for details.
|
||||
-h|--help
|
||||
Print a summary of command line options\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBparameters\fR
|
||||
-s <configuration file>
|
||||
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 \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
|
||||
|
||||
|
||||
.TP
|
||||
-i
|
||||
Run interactively\&. Individual commands of the form destination message-type parameters can be entered on STDIN\&. An empty command line or a "q" will quit the program\&.
|
||||
|
||||
|
||||
.TP
|
||||
destination
|
||||
One of \fInmbd\fR, \fIsmbd\fR or a process ID\&.
|
||||
|
||||
|
||||
The \fIsmbd\fR destination causes the message to "broadcast" to all smbd daemons\&.
|
||||
|
||||
|
||||
The \fInmbd\fR destination causes the message to be sent to the nmbd daemon specified in the \fInmbd\&.pid\fR file\&.
|
||||
|
||||
|
||||
If a single process ID is given, the message is sent to only that process\&.
|
||||
|
||||
|
||||
.TP
|
||||
message-type
|
||||
Type of message to send\&. See the section \fBMESSAGE-TYPES\fR for details\&.
|
||||
|
||||
|
||||
.TP
|
||||
parameters
|
||||
any parameters required for the message-type
|
||||
|
||||
|
||||
.SH "MESSAGE-TYPES"
|
||||
|
||||
.PP
|
||||
Available message types are:
|
||||
|
||||
.TP
|
||||
\fBclose-share\fR
|
||||
Order smbd to close the client
|
||||
connections to the named share. Note that this doesn't affect client
|
||||
connections to any other shares. This message-type takes an argument of the
|
||||
share name for which client connections will be closed, or the
|
||||
"*" character which will close all currently open shares.
|
||||
This may be useful if you made changes to the access controls on the share.
|
||||
This message can only be sent to smbd.
|
||||
close-share
|
||||
Order smbd to close the client connections to the named share\&. Note that this doesn't affect client connections to any other shares\&. This message-type takes an argument of the share name for which client connections will be closed, or the "*" character which will close all currently open shares\&. This may be useful if you made changes to the access controls on the share\&. This message can only be sent to \fBsmbd\fR\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBdebug\fR
|
||||
Set debug level to the value specified by the
|
||||
parameter. This can be sent to any of the destinations.
|
||||
debug
|
||||
Set debug level to the value specified by the parameter\&. This can be sent to any of the destinations\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBforce-election\fR
|
||||
This message causes the \fBnmbd\fR daemon to
|
||||
force a new browse master election.
|
||||
force-election
|
||||
This message causes the \fBnmbd\fR daemon to force a new browse master election\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBping\fR
|
||||
Send specified number of "ping" messages and
|
||||
wait for the same number of reply "pong" messages. This can be sent to
|
||||
any of the destinations.
|
||||
ping
|
||||
Send specified number of "ping" messages and wait for the same number of reply "pong" messages\&. This can be sent to any of the destinations\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBprofile\fR
|
||||
Change profile settings of a daemon, based on the
|
||||
parameter. The parameter can be "on" to turn on profile stats
|
||||
collection, "off" to turn off profile stats collection, "count"
|
||||
to enable only collection of count stats (time stats are
|
||||
disabled), and "flush" to zero the current profile stats. This can
|
||||
be sent to any smbd or nmbd destinations.
|
||||
profile
|
||||
Change profile settings of a daemon, based on the parameter\&. The parameter can be "on" to turn on profile stats collection, "off" to turn off profile stats collection, "count" to enable only collection of count stats (time stats are disabled), and "flush" to zero the current profile stats\&. This can be sent to any smbd or nmbd destinations\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBdebuglevel\fR
|
||||
Request debuglevel of a certain daemon and write it to stdout. This
|
||||
can be sent to any of the destinations.
|
||||
debuglevel
|
||||
Request debuglevel of a certain daemon and write it to stdout\&. This can be sent to any of the destinations\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBprofilelevel\fR
|
||||
Request profilelevel of a certain daemon and write it to stdout.
|
||||
This can be sent to any smbd or nmbd destinations.
|
||||
profilelevel
|
||||
Request profilelevel of a certain daemon and write it to stdout\&. This can be sent to any smbd or nmbd destinations\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBprintnotify\fR
|
||||
Order smbd to send a printer notify message to any Windows NT clients
|
||||
connected to a printer. This message-type takes the following arguments:
|
||||
printnotify
|
||||
Order smbd to send a printer notify message to any Windows NT clients connected to a printer\&. This message-type takes the following arguments:
|
||||
|
||||
|
||||
|
||||
.RS
|
||||
|
||||
.TP
|
||||
\fBqueuepause printername\fR
|
||||
Send a queue pause change notify
|
||||
message to the printer specified.
|
||||
queuepause printername
|
||||
Send a queue pause change notify message to the printer specified\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBqueueresume printername\fR
|
||||
Send a queue resume change notify
|
||||
message for the printer specified.
|
||||
queueresume printername
|
||||
Send a queue resume change notify message for the printer specified\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBjobpause printername unixjobid\fR
|
||||
Send a job pause change notify
|
||||
message for the printer and unix jobid
|
||||
specified.
|
||||
jobpause printername unixjobid
|
||||
Send a job pause change notify message for the printer and unix jobid specified\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBjobresume printername unixjobid\fR
|
||||
Send a job resume change notify
|
||||
message for the printer and unix jobid
|
||||
specified.
|
||||
jobresume printername unixjobid
|
||||
Send a job resume change notify message for the printer and unix jobid specified\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBjobdelete printername unixjobid\fR
|
||||
Send a job delete change notify
|
||||
message for the printer and unix jobid
|
||||
specified.
|
||||
jobdelete printername unixjobid
|
||||
Send a job delete change notify message for the printer and unix jobid specified\&.
|
||||
|
||||
|
||||
.RE
|
||||
Note that this message only sends notification that an event has occured\&. It doesn't actually cause the event to happen\&.
|
||||
|
||||
|
||||
This message can only be sent to \fBsmbd\fR\&.
|
||||
|
||||
Note that this message only sends notification that an
|
||||
event has occured. It doesn't actually cause the
|
||||
event to happen.
|
||||
|
||||
This message can only be sent to smbd.
|
||||
.TP
|
||||
\fBsamsync\fR
|
||||
Order smbd to synchronise sam database from PDC (being BDC). Can only be sent to smbd.
|
||||
.sp
|
||||
.RS
|
||||
.B "Note:"
|
||||
samsync
|
||||
Order smbd to synchronise sam database from PDC (being BDC)\&. Can only be sent to \fBsmbd\fR\&.
|
||||
|
||||
Not working at the moment
|
||||
.RE
|
||||
|
||||
|
||||
.TP
|
||||
\fBsamrepl\fR
|
||||
Send sam replication message, with specified serial. Can only be sent to smbd. Should not be used manually.
|
||||
samrepl
|
||||
Send sam replication message, with specified serial\&. Can only be sent to \fBsmbd\fR\&. Should not be used manually\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBdmalloc-mark\fR
|
||||
Set a mark for dmalloc. Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support.
|
||||
dmalloc-mark
|
||||
Set a mark for dmalloc\&. Can be sent to both smbd and nmbd\&. Only available if samba is built with dmalloc support\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBdmalloc-log-changed\fR
|
||||
Dump the pointers that have changed since the mark set by dmalloc-mark.
|
||||
Can be sent to both smbd and nmbd. Only available if samba is built with dmalloc support.
|
||||
dmalloc-log-changed
|
||||
Dump the pointers that have changed since the mark set by dmalloc-mark\&. Can be sent to both smbd and nmbd\&. Only available if samba is built with dmalloc support\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBshutdown\fR
|
||||
Shut down specified daemon. Can be sent to both smbd and nmbd.
|
||||
shutdown
|
||||
Shut down specified daemon\&. Can be sent to both smbd and nmbd\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBpool-usage\fR
|
||||
Print a human-readable description of all
|
||||
talloc(pool) memory usage by the specified daemon/process. Available
|
||||
for both smbd and nmbd.
|
||||
pool-usage
|
||||
Print a human-readable description of all talloc(pool) memory usage by the specified daemon/process\&. Available for both smbd and nmbd\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBdrvupgrade\fR
|
||||
Force clients of printers using specified driver
|
||||
to update their local version of the driver. Can only be
|
||||
sent to smbd.
|
||||
drvupgrade
|
||||
Force clients of printers using specified driver to update their local version of the driver\&. Can only be sent to smbd\&.
|
||||
|
||||
|
||||
.SH "VERSION"
|
||||
|
||||
.PP
|
||||
This man page is correct for version 3.0 of
|
||||
the Samba suite.
|
||||
This man page is correct for version 3\&.0 of the Samba suite\&.
|
||||
|
||||
.SH "SEE ALSO"
|
||||
|
||||
.PP
|
||||
\fBnmbd\fR(8) and \fBsmbd\fR(8).
|
||||
\fBnmbd\fR(8) and \fBsmbd\fR(8)\&.
|
||||
|
||||
.SH "AUTHOR"
|
||||
|
||||
.PP
|
||||
The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.
|
||||
The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
|
||||
|
||||
.PP
|
||||
The original Samba man pages were written by Karl Auer.
|
||||
The man page sources were converted to YODL format (another
|
||||
excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for
|
||||
Samba 3.0 was done by Alexander Bokovoy.
|
||||
The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
|
||||
|
||||
|
||||
@ -1,183 +1,199 @@
|
||||
.\" This manpage has been automatically generated by docbook2man
|
||||
.\" from a DocBook document. This tool can be found at:
|
||||
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
||||
.\" Please send any bug reports, improvements, comments, patches,
|
||||
.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
||||
.TH "SMBCQUOTAS" "1" "19 april 2003" "" ""
|
||||
|
||||
.\"Generated by db2man.xsl. Don't modify this, modify the source.
|
||||
.de Sh \" Subsection
|
||||
.br
|
||||
.if t .Sp
|
||||
.ne 5
|
||||
.PP
|
||||
\fB\\$1\fR
|
||||
.PP
|
||||
..
|
||||
.de Sp \" Vertical space (when we can't use .PP)
|
||||
.if t .sp .5v
|
||||
.if n .sp
|
||||
..
|
||||
.de Ip \" List item
|
||||
.br
|
||||
.ie \\n(.$>=3 .ne \\$3
|
||||
.el .ne 3
|
||||
.IP "\\$1" \\$2
|
||||
..
|
||||
.TH "SMBCQUOTAS" 1 "" "" ""
|
||||
.SH NAME
|
||||
smbcquotas \- Set or get QUOTAs of NTFS 5 shares
|
||||
.SH SYNOPSIS
|
||||
.SH "SYNOPSIS"
|
||||
|
||||
\fBsmbcquotas\fR \fB//server/share\fR [ \fB-u user\fR ] [ \fB-L\fR ] [ \fB-F\fR ] [ \fB-S QUOTA_SET_COMMAND\fR ] [ \fB-n\fR ] [ \fB-t\fR ] [ \fB-v\fR ] [ \fB-d debuglevel\fR ] [ \fB-s configfile\fR ] [ \fB-l logfilebase\fR ] [ \fB-V\fR ] [ \fB-U username\fR ] [ \fB-N\fR ] [ \fB-k\fR ] [ \fB-A\fR ]
|
||||
.nf
|
||||
\fBsmbcquotas\fR {//server/share} [-u user] [-L] [-F] [-S QUOTA_SET_COMMAND] [-n] [-t]
|
||||
[-v] [-d debuglevel] [-s configfile] [-l logfilebase] [-V] [-U username]
|
||||
[-N] [-k] [-A]
|
||||
.fi
|
||||
|
||||
.SH "DESCRIPTION"
|
||||
|
||||
.PP
|
||||
This tool is part of the \fBSamba\fR(7) suite.
|
||||
This tool is part of the \fBSamba\fR(7) suite\&.
|
||||
|
||||
.PP
|
||||
The \fBsmbcquotas\fR program manipulates NT Quotas on SMB file shares.
|
||||
The \fBsmbcquotas\fR program manipulates NT Quotas on SMB file shares\&.
|
||||
|
||||
.SH "OPTIONS"
|
||||
|
||||
.PP
|
||||
The following options are available to the \fBsmbcquotas\fR program.
|
||||
.TP
|
||||
\fB-u user\fR
|
||||
Specifies the user of whom the quotas are get or set.
|
||||
By default the current user's username will be used.
|
||||
.TP
|
||||
\fB-L\fR
|
||||
Lists all quota records of the share.
|
||||
.TP
|
||||
\fB-F\fR
|
||||
Show the share quota status and default limits.
|
||||
.TP
|
||||
\fB-S QUOTA_SET_COMMAND\fR
|
||||
This command set/modify quotas for a user or on the share,
|
||||
depending on the QUOTA_SET_COMMAND parameter witch is described later
|
||||
.TP
|
||||
\fB-n\fR
|
||||
This option displays all QUOTA information in numeric
|
||||
format. The default is to convert SIDs to names and QUOTA limits
|
||||
to a readable string format.
|
||||
.TP
|
||||
\fB-t\fR
|
||||
Don't actually do anything, only validate the correctness of
|
||||
the arguments.
|
||||
.TP
|
||||
\fB-v\fR
|
||||
Be verbose.
|
||||
.TP
|
||||
\fB-h|--help\fR
|
||||
Print a summary of command line options.
|
||||
.TP
|
||||
\fB-V\fR
|
||||
Prints the version number for
|
||||
\fBsmbd\fR.
|
||||
.TP
|
||||
\fB-s <configuration file>\fR
|
||||
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 \fIsmb.conf(5)\fR for more information.
|
||||
The default configuration file name is determined at
|
||||
compile time.
|
||||
.TP
|
||||
\fB-d|--debug=debuglevel\fR
|
||||
\fIdebuglevel\fR is an integer
|
||||
from 0 to 10. The default value if this parameter is
|
||||
not specified is zero.
|
||||
The following options are available to the \fBsmbcquotas\fR program\&.
|
||||
|
||||
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.
|
||||
.TP
|
||||
-u user
|
||||
Specifies the user of whom the quotas are get or set\&. By default the current user's username will be used\&.
|
||||
|
||||
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.
|
||||
|
||||
Note that specifying this parameter here will
|
||||
override the log
|
||||
level file.
|
||||
.TP
|
||||
\fB-l|--logfile=logbasename\fR
|
||||
File name for log/debug files. The extension
|
||||
".client" will be appended. The log file is
|
||||
never removed by the client.
|
||||
.TP
|
||||
\fB-N\fR
|
||||
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.
|
||||
-L
|
||||
Lists all quota records of the share\&.
|
||||
|
||||
|
||||
Unless a password is specified on the command line or
|
||||
this parameter is specified, the client will request a
|
||||
password.
|
||||
.TP
|
||||
\fB-k\fR
|
||||
Try to authenticate with kerberos. Only useful in
|
||||
an Active Directory environment.
|
||||
-F
|
||||
Show the share quota status and default limits\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-A|--authfile=filename\fR
|
||||
This option allows
|
||||
you to specify a file from which to read the username and
|
||||
password used in the connection. The format of the file is
|
||||
-S QUOTA_SET_COMMAND
|
||||
This command set/modify quotas for a user or on the share, depending on the QUOTA_SET_COMMAND parameter witch is described later
|
||||
|
||||
|
||||
.TP
|
||||
-n
|
||||
This option displays all QUOTA information in numeric format\&. The default is to convert SIDs to names and QUOTA limits to a readable string format\&.
|
||||
|
||||
|
||||
.TP
|
||||
-t
|
||||
Don't actually do anything, only validate the correctness of the arguments\&.
|
||||
|
||||
|
||||
.TP
|
||||
-v
|
||||
Be verbose\&.
|
||||
|
||||
|
||||
.TP
|
||||
-h|--help
|
||||
Print a summary of command line options\&.
|
||||
|
||||
|
||||
.TP
|
||||
-V
|
||||
Prints the version number for \fBsmbd\fR\&.
|
||||
|
||||
|
||||
.TP
|
||||
-s <configuration file>
|
||||
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 \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
|
||||
|
||||
|
||||
.TP
|
||||
-d|--debug=debuglevel
|
||||
\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
|
||||
|
||||
|
||||
The higher this value, the more detail will be logged to the log files about the activities of the 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\&.
|
||||
|
||||
|
||||
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\&.
|
||||
|
||||
|
||||
Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&.
|
||||
|
||||
|
||||
.TP
|
||||
-l|--logfile=logbasename
|
||||
File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&.
|
||||
|
||||
|
||||
.TP
|
||||
-N
|
||||
If specified, this parameter suppresses the normal password prompt from the client to the user\&. This is useful when accessing a service that does not require a password\&.
|
||||
|
||||
|
||||
Unless a password is specified on the command line or this parameter is specified, the client will request a password\&.
|
||||
|
||||
|
||||
.TP
|
||||
-k
|
||||
Try to authenticate with kerberos\&. Only useful in an Active Directory environment\&.
|
||||
|
||||
|
||||
.TP
|
||||
-A|--authfile=filename
|
||||
This option allows you to specify a file from which to read the username and password used in the connection\&. The format of the file is
|
||||
|
||||
|
||||
.nf
|
||||
|
||||
username = <value>
|
||||
password = <value>
|
||||
domain = <value>
|
||||
.fi
|
||||
|
||||
Make certain that the permissions on the file restrict
|
||||
access from unwanted users.
|
||||
|
||||
Make certain that the permissions on the file restrict access from unwanted users\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-U|--user=username[%password]\fR
|
||||
Sets the SMB username or username and password.
|
||||
-U|--user=username[%password]
|
||||
Sets the SMB username or username and password\&.
|
||||
|
||||
If %password is not specified, the user will be prompted. The
|
||||
client will first check the \fBUSER\fR environment variable, then the
|
||||
\fBLOGNAME\fR variable and if either exists, the
|
||||
string is uppercased. If these environmental variables are not
|
||||
found, the username GUEST is used.
|
||||
|
||||
A third option is to use a credentials file which
|
||||
contains the plaintext of the username and password. This
|
||||
option is mainly provided for scripts where the admin does not
|
||||
wish to pass the credentials on the command line or via environment
|
||||
variables. If this method is used, make certain that the permissions
|
||||
on the file restrict access from unwanted users. See the
|
||||
\fI-A\fR for more details.
|
||||
If %password is not specified, the user will be prompted\&. The client will first check the \fBUSER\fR environment variable, then the \fBLOGNAME\fR variable and if either exists, the string is uppercased\&. If these environmental variables are not found, the username \fBGUEST\fR is used\&.
|
||||
|
||||
|
||||
A third option is to use a credentials file which contains the plaintext of the username and password\&. This option is mainly provided for scripts where the admin does not wish to pass the credentials on the command line or via environment variables\&. If this method is used, make certain that the permissions on the file restrict access from unwanted users\&. See the \fI-A\fR for more details\&.
|
||||
|
||||
|
||||
Be cautious about including passwords in scripts\&. Also, on many systems the command line of a running process may be seen via the \fBps\fR command\&. To be safe always allow \fBrpcclient\fR to prompt for a password and type it in directly\&.
|
||||
|
||||
|
||||
Be cautious about including passwords in scripts. Also, on
|
||||
many systems the command line of a running process may be seen
|
||||
via the \fBps\fR command. To be safe always allow
|
||||
\fBrpcclient\fR to prompt for a password and type
|
||||
it in directly.
|
||||
.SH "QUOTA_SET_COMAND"
|
||||
|
||||
.PP
|
||||
The format of an ACL is one or more ACL entries separated by
|
||||
either commas or newlines. An ACL entry is one of the following:
|
||||
The format of an ACL is one or more ACL entries separated by either commas or newlines\&. An ACL entry is one of the following:
|
||||
|
||||
.PP
|
||||
for user setting quotas for the specified by -u or the current username:
|
||||
|
||||
.PP
|
||||
\fB UQLIM:<username><softlimit><hardlimit>
|
||||
\fR
|
||||
\fB UQLIM:<username><softlimit><hardlimit> \fR
|
||||
|
||||
.PP
|
||||
for setting the share quota defaults limits:
|
||||
|
||||
.PP
|
||||
\fB FSQLIM:<softlimit><hardlimit>
|
||||
\fR
|
||||
\fB FSQLIM:<softlimit><hardlimit> \fR
|
||||
|
||||
.PP
|
||||
for changing the share quota settings:
|
||||
|
||||
.PP
|
||||
\fB FSQFLAGS:QUOTA_ENABLED/DENY_DISK/LOG_SOFTLIMIT/LOG_HARD_LIMIT
|
||||
\fR
|
||||
\fB FSQFLAGS:QUOTA_ENABLED/DENY_DISK/LOG_SOFTLIMIT/LOG_HARD_LIMIT \fR
|
||||
|
||||
.SH "EXIT STATUS"
|
||||
|
||||
.PP
|
||||
The \fBsmbcquotas\fR program sets the exit status
|
||||
depending on the success or otherwise of the operations performed.
|
||||
The exit status may be one of the following values.
|
||||
The \fBsmbcquotas\fR program sets the exit status depending on the success or otherwise of the operations performed\&. The exit status may be one of the following values\&.
|
||||
|
||||
.PP
|
||||
If the operation succeeded, smbcquotas returns an exit
|
||||
status of 0. If \fBsmbcquotas\fR couldn't connect to the specified server,
|
||||
or when there was an error getting or setting the quota(s), an exit status
|
||||
of 1 is returned. If there was an error parsing any command line
|
||||
arguments, an exit status of 2 is returned.
|
||||
If the operation succeeded, smbcquotas returns an exit status of 0\&. If \fBsmbcquotas\fR couldn't connect to the specified server, or when there was an error getting or setting the quota(s), an exit status of 1 is returned\&. If there was an error parsing any command line arguments, an exit status of 2 is returned\&.
|
||||
|
||||
.SH "VERSION"
|
||||
|
||||
.PP
|
||||
This man page is correct for version 3.0 of the Samba suite.
|
||||
This man page is correct for version 3\&.0 of the Samba suite\&.
|
||||
|
||||
.SH "AUTHOR"
|
||||
|
||||
.PP
|
||||
The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.
|
||||
The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
|
||||
|
||||
.PP
|
||||
\fBsmbcacls\fR was written by Stefan Metzmacher.
|
||||
\fBsmbcacls\fR was written by Stefan Metzmacher\&.
|
||||
|
||||
|
||||
@ -1,306 +1,230 @@
|
||||
.\" This manpage has been automatically generated by docbook2man
|
||||
.\" from a DocBook document. This tool can be found at:
|
||||
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
||||
.\" Please send any bug reports, improvements, comments, patches,
|
||||
.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
||||
.TH "SMBD" "8" "19 april 2003" "" ""
|
||||
|
||||
.\"Generated by db2man.xsl. Don't modify this, modify the source.
|
||||
.de Sh \" Subsection
|
||||
.br
|
||||
.if t .Sp
|
||||
.ne 5
|
||||
.PP
|
||||
\fB\\$1\fR
|
||||
.PP
|
||||
..
|
||||
.de Sp \" Vertical space (when we can't use .PP)
|
||||
.if t .sp .5v
|
||||
.if n .sp
|
||||
..
|
||||
.de Ip \" List item
|
||||
.br
|
||||
.ie \\n(.$>=3 .ne \\$3
|
||||
.el .ne 3
|
||||
.IP "\\$1" \\$2
|
||||
..
|
||||
.TH "SMBD" 8 "" "" ""
|
||||
.SH NAME
|
||||
smbd \- server to provide SMB/CIFS services to clients
|
||||
.SH SYNOPSIS
|
||||
.SH "SYNOPSIS"
|
||||
|
||||
\fBsmbd\fR [ \fB-D\fR ] [ \fB-F\fR ] [ \fB-S\fR ] [ \fB-i\fR ] [ \fB-h\fR ] [ \fB-V\fR ] [ \fB-b\fR ] [ \fB-d <debug level>\fR ] [ \fB-l <log directory>\fR ] [ \fB-p <port number>\fR ] [ \fB-O <socket option>\fR ] [ \fB-s <configuration file>\fR ]
|
||||
.nf
|
||||
\fBsmbd\fR [-D] [-F] [-S] [-i] [-h] [-V] [-b] [-d <debug level>] [-l <log directory>]
|
||||
[-p <port number>] [-O <socket option>] [-s <configuration file>]
|
||||
.fi
|
||||
|
||||
.SH "DESCRIPTION"
|
||||
|
||||
.PP
|
||||
This program is part of the \fBSamba\fR(7) suite.
|
||||
This program is part of the \fBSamba\fR(7) suite\&.
|
||||
|
||||
.PP
|
||||
\fBsmbd\fR 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/98/ME, Windows NT, Windows 2000,
|
||||
OS/2, DAVE for Macintosh, and smbfs for Linux.
|
||||
\fBsmbd\fR 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/98/ME, Windows NT, Windows 2000, OS/2, DAVE for Macintosh, and smbfs for Linux\&.
|
||||
|
||||
.PP
|
||||
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 \fBsmb.conf\fR(5). This man page will not describe the
|
||||
services, but will concentrate on the administrative aspects
|
||||
of running the server.
|
||||
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 \fBsmb.conf\fR(5)\&. This man page will not describe the services, but will concentrate on the administrative aspects of running the server\&.
|
||||
|
||||
.PP
|
||||
Please note that there are significant security
|
||||
implications to running this server, and the \fBsmb.conf\fR(5) manual page should be regarded as mandatory reading before
|
||||
proceeding with installation.
|
||||
Please note that there are significant security implications to running this server, and the \fBsmb.conf\fR(5) manual page should be regarded as mandatory reading before proceeding with installation\&.
|
||||
|
||||
.PP
|
||||
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.
|
||||
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\&.
|
||||
|
||||
.PP
|
||||
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 \fBsmbd\fR killed and restarted.
|
||||
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 \fBsmbd\fR killed and restarted\&.
|
||||
|
||||
.SH "OPTIONS"
|
||||
.TP
|
||||
\fB-D\fR
|
||||
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 \fBsmbd\fR for
|
||||
servers that provide more than casual use file and
|
||||
print services. This switch is assumed if \fBsmbd
|
||||
\fR is executed on the command line of a shell.
|
||||
.TP
|
||||
\fB-F\fR
|
||||
If specified, this parameter causes
|
||||
the main \fBsmbd\fR process to not daemonize,
|
||||
i.e. double-fork and disassociate with the terminal.
|
||||
Child processes are still created as normal to service
|
||||
each connection request, but the main process does not
|
||||
exit. This operation mode is suitable for running
|
||||
\fBsmbd\fR under process supervisors such
|
||||
as \fBsupervise\fR and \fBsvscan\fR
|
||||
from Daniel J. Bernstein's \fBdaemontools\fR
|
||||
package, or the AIX process monitor.
|
||||
.TP
|
||||
\fB-S\fR
|
||||
If specified, this parameter causes
|
||||
\fBsmbd\fR to log to standard output rather
|
||||
than a file.
|
||||
.TP
|
||||
\fB-i\fR
|
||||
If this parameter is specified it causes the
|
||||
server to run "interactively", not as a daemon, even if the
|
||||
server is executed on the command line of a shell. Setting this
|
||||
parameter negates the implicit deamon mode when run from the
|
||||
command line. \fBsmbd\fR also logs to standard
|
||||
output, as if the \fB-S\fR parameter had been
|
||||
given.
|
||||
.TP
|
||||
\fB-V\fR
|
||||
Prints the version number for
|
||||
\fBsmbd\fR.
|
||||
.TP
|
||||
\fB-s <configuration file>\fR
|
||||
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 \fIsmb.conf(5)\fR for more information.
|
||||
The default configuration file name is determined at
|
||||
compile time.
|
||||
.TP
|
||||
\fB-d|--debug=debuglevel\fR
|
||||
\fIdebuglevel\fR is an integer
|
||||
from 0 to 10. The default value if this parameter is
|
||||
not specified is zero.
|
||||
|
||||
The higher this value, the more detail will be
|
||||
logged to the log files about the activities of the
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
Note that specifying this parameter here will
|
||||
override the log
|
||||
level file.
|
||||
.TP
|
||||
\fB-l|--logfile=logbasename\fR
|
||||
File name for log/debug files. The extension
|
||||
".client" will be appended. The log file is
|
||||
never removed by the client.
|
||||
.TP
|
||||
\fB-h|--help\fR
|
||||
Print a summary of command line options.
|
||||
.TP
|
||||
\fB-b\fR
|
||||
Prints information about how
|
||||
Samba was built.
|
||||
.TP
|
||||
\fB-l <log directory>\fR
|
||||
If specified,
|
||||
\fIlog directory\fR
|
||||
specifies a log directory into which the "log.smbd" log
|
||||
file will be created for informational and debug
|
||||
messages from the running server. The log
|
||||
file generated is never removed by the server although
|
||||
its size may be controlled by the \fImax log size\fR
|
||||
option in the \fBsmb.conf\fR(5) file. \fBBeware:\fR
|
||||
If the directory specified does not exist, \fBsmbd\fR
|
||||
will log to the default debug log location defined at compile time.
|
||||
-D
|
||||
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 \fBsmbd\fR for servers that provide more than casual use file and print services\&. This switch is assumed if \fBsmbd \fR is executed on the command line of a shell\&.
|
||||
|
||||
|
||||
The default log directory is specified at
|
||||
compile time.
|
||||
.TP
|
||||
\fB-p <port number>\fR
|
||||
\fIport number\fR is a positive integer
|
||||
value. The default value if this parameter is not
|
||||
specified is 139.
|
||||
-F
|
||||
If specified, this parameter causes the main \fBsmbd\fR process to not daemonize, i\&.e\&. double-fork and disassociate with the terminal\&. Child processes are still created as normal to service each connection request, but the main process does not exit\&. This operation mode is suitable for running \fBsmbd\fR under process supervisors such as \fBsupervise\fR and \fBsvscan\fR from Daniel J\&. Bernstein's \fBdaemontools\fR package, or the AIX process monitor\&.
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
.TP
|
||||
-S
|
||||
If specified, this parameter causes \fBsmbd\fR to log to standard output rather than a file\&.
|
||||
|
||||
|
||||
.TP
|
||||
-i
|
||||
If this parameter is specified it causes the server to run "interactively", not as a daemon, even if the server is executed on the command line of a shell\&. Setting this parameter negates the implicit deamon mode when run from the command line\&. \fBsmbd\fR also logs to standard output, as if the \fB-S\fR parameter had been given\&.
|
||||
|
||||
|
||||
.TP
|
||||
-V
|
||||
Prints the version number for \fBsmbd\fR\&.
|
||||
|
||||
|
||||
.TP
|
||||
-s <configuration file>
|
||||
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 \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
|
||||
|
||||
|
||||
.TP
|
||||
-d|--debug=debuglevel
|
||||
\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
|
||||
|
||||
|
||||
The higher this value, the more detail will be logged to the log files about the activities of the 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\&.
|
||||
|
||||
|
||||
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\&.
|
||||
|
||||
|
||||
Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&.
|
||||
|
||||
|
||||
.TP
|
||||
-l|--logfile=logbasename
|
||||
File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&.
|
||||
|
||||
|
||||
.TP
|
||||
-h|--help
|
||||
Print a summary of command line options\&.
|
||||
|
||||
|
||||
.TP
|
||||
-b
|
||||
Prints information about how Samba was built\&.
|
||||
|
||||
|
||||
.TP
|
||||
-l <log directory>
|
||||
If specified, \fIlog directory\fR specifies a log directory into which the "log\&.smbd" log file will be created for informational and debug messages from the running server\&. The log file generated is never removed by the server although its size may be controlled by the \fImax log size\fR option in the \fBsmb.conf\fR(5) file\&. \fBBeware:\fR If the directory specified does not exist, \fBsmbd\fR will log to the default debug log location defined at compile time\&.
|
||||
|
||||
|
||||
The default log directory is specified at compile time\&.
|
||||
|
||||
|
||||
.TP
|
||||
-p <port number>
|
||||
\fIport number\fR is a positive integer value\&. The default value if this parameter is not specified is 139\&.
|
||||
|
||||
|
||||
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\&.
|
||||
|
||||
|
||||
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\&.
|
||||
|
||||
|
||||
This parameter is not normally specified except in the above situation\&.
|
||||
|
||||
|
||||
This parameter is not normally specified except
|
||||
in the above situation.
|
||||
.SH "FILES"
|
||||
.TP
|
||||
\fB\fI/etc/inetd.conf\fB\fR
|
||||
If the server is to be run by the
|
||||
\fBinetd\fR meta-daemon, this file
|
||||
must contain suitable startup information for the
|
||||
meta-daemon. See the "How to Install and Test SAMBA"
|
||||
document for details.
|
||||
.TP
|
||||
\fB\fI/etc/rc\fB\fR
|
||||
or whatever initialization script your
|
||||
system uses).
|
||||
|
||||
If running the server as a daemon at startup,
|
||||
this file will need to contain an appropriate startup
|
||||
sequence for the server. See the "How to Install and Test SAMBA"
|
||||
document for details.
|
||||
.TP
|
||||
\fB\fI/etc/services\fB\fR
|
||||
If running the server via the
|
||||
meta-daemon \fBinetd\fR, 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 "How to Install and Test SAMBA"
|
||||
document for details.
|
||||
.TP
|
||||
\fB\fI/usr/local/samba/lib/smb.conf\fB\fR
|
||||
This is the default location of the \fBsmb.conf\fR(5) server configuration file. Other common places that systems
|
||||
install this file are \fI/usr/samba/lib/smb.conf\fR
|
||||
and \fI/etc/samba/smb.conf\fR.
|
||||
\fI/etc/inetd\&.conf\fR
|
||||
If the server is to be run by the \fBinetd\fR meta-daemon, this file must contain suitable startup information for the meta-daemon\&. See the "How to Install and Test SAMBA" document for details\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fI/etc/rc\fR
|
||||
or whatever initialization script your system uses)\&.
|
||||
|
||||
|
||||
If running the server as a daemon at startup, this file will need to contain an appropriate startup sequence for the server\&. See the "How to Install and Test SAMBA" document for details\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fI/etc/services\fR
|
||||
If running the server via the meta-daemon \fBinetd\fR, 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 "How to Install and Test SAMBA" document for details\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fI/usr/local/samba/lib/smb\&.conf\fR
|
||||
This is the default location of the \fBsmb.conf\fR(5) server configuration file\&. Other common places that systems install this file are \fI/usr/samba/lib/smb\&.conf\fR and \fI/etc/samba/smb\&.conf\fR\&.
|
||||
|
||||
|
||||
This file describes all the services the server is to make available to clients\&. See \fBsmb.conf\fR(5) for more information\&.
|
||||
|
||||
|
||||
This file describes all the services the server
|
||||
is to make available to clients. See \fBsmb.conf\fR(5) for more information.
|
||||
.SH "LIMITATIONS"
|
||||
|
||||
.PP
|
||||
On some systems \fBsmbd\fR 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.
|
||||
On some systems \fBsmbd\fR 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\&.
|
||||
|
||||
.SH "ENVIRONMENT VARIABLES"
|
||||
|
||||
.TP
|
||||
\fBPRINTER\fR
|
||||
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.
|
||||
If no printer name is specified to printable services, most systems will use the value of this variable (or \fBlp\fR if this variable is not defined) as the name of the printer to use\&. This is not specific to the server, however\&.
|
||||
|
||||
|
||||
.SH "PAM INTERACTION"
|
||||
|
||||
.PP
|
||||
Samba uses PAM for authentication (when presented with a plaintext
|
||||
password), for account checking (is this account disabled?) and for
|
||||
session management. The degree too which samba supports PAM is restricted
|
||||
by the limitations of the SMB protocol and the \fIobey
|
||||
pam restricions\fR \fBsmb.conf\fR(5) paramater. When this is set, the following restrictions apply:
|
||||
.TP 0.2i
|
||||
Samba uses PAM for authentication (when presented with a plaintext password), for account checking (is this account disabled?) and for session management\&. The degree too which samba supports PAM is restricted by the limitations of the SMB protocol and the \fIobey pam restricions\fR \fBsmb.conf\fR(5) paramater\&. When this is set, the following restrictions apply:
|
||||
|
||||
.TP 3
|
||||
\(bu
|
||||
\fBAccount Validation\fR: All accesses to a
|
||||
samba server are checked
|
||||
against PAM to see if the account is vaild, not disabled and is permitted to
|
||||
login at this time. This also applies to encrypted logins.
|
||||
.TP 0.2i
|
||||
\fBAccount Validation\fR: All accesses to a samba server are checked against PAM to see if the account is vaild, not disabled and is permitted to login at this time\&. This also applies to encrypted logins\&.
|
||||
|
||||
.TP
|
||||
\(bu
|
||||
\fBSession Management\fR: When not using share
|
||||
level secuirty, users must pass PAM's session checks before access
|
||||
is granted. Note however, that this is bypassed in share level secuirty.
|
||||
Note also that some older pam configuration files may need a line
|
||||
added for session support.
|
||||
\fBSession Management\fR: When not using share level secuirty, users must pass PAM's session checks before access is granted\&. Note however, that this is bypassed in share level secuirty\&. Note also that some older pam configuration files may need a line added for session support\&.
|
||||
|
||||
.LP
|
||||
|
||||
.SH "VERSION"
|
||||
|
||||
.PP
|
||||
This man page is correct for version 3.0 of
|
||||
the Samba suite.
|
||||
This man page is correct for version 3\&.0 of the Samba suite\&.
|
||||
|
||||
.SH "DIAGNOSTICS"
|
||||
|
||||
.PP
|
||||
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.
|
||||
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\&.
|
||||
|
||||
.PP
|
||||
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.
|
||||
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\&.
|
||||
|
||||
.PP
|
||||
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.
|
||||
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\&.
|
||||
|
||||
.SH "SIGNALS"
|
||||
|
||||
.PP
|
||||
Sending the \fBsmbd\fR a SIGHUP will cause it to
|
||||
reload its \fIsmb.conf\fR configuration
|
||||
file within a short period of time.
|
||||
Sending the \fBsmbd\fR a SIGHUP will cause it to reload its \fIsmb\&.conf\fR configuration file within a short period of time\&.
|
||||
|
||||
.PP
|
||||
To shut down a user's \fBsmbd\fR process it is recommended
|
||||
that \fBSIGKILL (-9)\fR \fBNOT\fR
|
||||
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 \fBsmbd\fR is to send it a SIGTERM (-15) signal and wait for
|
||||
it to die on its own.
|
||||
To shut down a user's \fBsmbd\fR process it is recommended that \fBSIGKILL (-9)\fR \fBNOT\fR 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 \fBsmbd\fR is to send it a SIGTERM (-15) signal and wait for it to die on its own\&.
|
||||
|
||||
.PP
|
||||
The debug log level of \fBsmbd\fR may be raised
|
||||
or lowered using \fBsmbcontrol\fR(1) program (SIGUSR[1|2] signals are no longer
|
||||
used since Samba 2.2). This is to allow transient problems to be diagnosed,
|
||||
whilst still running at a normally low log level.
|
||||
The debug log level of \fBsmbd\fR may be raised or lowered using \fBsmbcontrol\fR(1) program (SIGUSR[1|2] signals are no longer used since Samba 2\&.2)\&. This is to allow transient problems to be diagnosed, whilst still running at a normally low log level\&.
|
||||
|
||||
.PP
|
||||
Note that as the signal handlers send a debug write,
|
||||
they are not re-entrant in \fBsmbd\fR. This you should wait until
|
||||
\fBsmbd\fR 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.
|
||||
Note that as the signal handlers send a debug write, they are not re-entrant in \fBsmbd\fR\&. This you should wait until\fBsmbd\fR 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\&.
|
||||
|
||||
.SH "SEE ALSO"
|
||||
|
||||
.PP
|
||||
\fBhosts_access\fR(5), \fBinetd\fR(8), \fBnmbd\fR(8), \fBsmb.conf\fR(5), \fBsmbclient\fR(1), \fBtestparm\fR(1), \fBtestprns\fR(1), and the
|
||||
Internet RFC's \fIrfc1001.txt\fR, \fIrfc1002.txt\fR.
|
||||
In addition the CIFS (formerly SMB) specification is available
|
||||
as a link from the Web page
|
||||
http://samba.org/cifs/ <URL:http://samba.org/cifs/>.
|
||||
\fBhosts_access\fR(5), \fBinetd\fR(8), \fBnmbd\fR(8), \fBsmb.conf\fR(5), \fBsmbclient\fR(1), \fBtestparm\fR(1), \fBtestprns\fR(1), and the Internet RFC's\fIrfc1001\&.txt\fR, \fIrfc1002\&.txt\fR\&. In addition the CIFS (formerly SMB) specification is available as a link from the Web page http://samba\&.org/cifs/\&.
|
||||
|
||||
.SH "AUTHOR"
|
||||
|
||||
.PP
|
||||
The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.
|
||||
The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
|
||||
|
||||
.PP
|
||||
The original Samba man pages were written by Karl Auer.
|
||||
The man page sources were converted to YODL format (another
|
||||
excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for
|
||||
Samba 3.0 was done by Alexander Bokovoy.
|
||||
The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
|
||||
|
||||
|
||||
@ -1,68 +1,91 @@
|
||||
.\" This manpage has been automatically generated by docbook2man
|
||||
.\" from a DocBook document. This tool can be found at:
|
||||
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
||||
.\" Please send any bug reports, improvements, comments, patches,
|
||||
.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
||||
.TH "SMBMNT" "8" "19 april 2003" "" ""
|
||||
|
||||
.\"Generated by db2man.xsl. Don't modify this, modify the source.
|
||||
.de Sh \" Subsection
|
||||
.br
|
||||
.if t .Sp
|
||||
.ne 5
|
||||
.PP
|
||||
\fB\\$1\fR
|
||||
.PP
|
||||
..
|
||||
.de Sp \" Vertical space (when we can't use .PP)
|
||||
.if t .sp .5v
|
||||
.if n .sp
|
||||
..
|
||||
.de Ip \" List item
|
||||
.br
|
||||
.ie \\n(.$>=3 .ne \\$3
|
||||
.el .ne 3
|
||||
.IP "\\$1" \\$2
|
||||
..
|
||||
.TH "SMBMNT" 8 "" "" ""
|
||||
.SH NAME
|
||||
smbmnt \- helper utility for mounting SMB filesystems
|
||||
.SH SYNOPSIS
|
||||
.SH "SYNOPSIS"
|
||||
|
||||
\fBsmbmnt\fR \fBmount-point\fR [ \fB-s <share>\fR ] [ \fB-r\fR ] [ \fB-u <uid>\fR ] [ \fB-g <gid>\fR ] [ \fB-f <mask>\fR ] [ \fB-d <mask>\fR ] [ \fB-o <options>\fR ] [ \fB-h\fR ]
|
||||
.nf
|
||||
\fBsmbmnt\fR {mount-point} [-s <share>] [-r] [-u <uid>] [-g <gid>] [-f <mask>] [-d <mask>] [-o <options>] [-h]
|
||||
|
||||
.fi
|
||||
|
||||
.SH "DESCRIPTION"
|
||||
|
||||
.PP
|
||||
\fBsmbmnt\fR is a helper application used
|
||||
by the smbmount program to do the actual mounting of SMB shares.
|
||||
\fBsmbmnt\fR can be installed setuid root if you want
|
||||
normal users to be able to mount their SMB shares.
|
||||
\fBsmbmnt\fR is a helper application used by the smbmount program to do the actual mounting of SMB shares\&.\fBsmbmnt\fR can be installed setuid root if you want normal users to be able to mount their SMB shares\&.
|
||||
|
||||
.PP
|
||||
A setuid smbmnt will only allow mounts on directories owned
|
||||
by the user, and that the user has write permission on.
|
||||
A setuid smbmnt will only allow mounts on directories owned by the user, and that the user has write permission on\&.
|
||||
|
||||
.PP
|
||||
The \fBsmbmnt\fR program is normally invoked
|
||||
by \fBsmbmount\fR(8). It should not be invoked directly by users.
|
||||
The \fBsmbmnt\fR program is normally invoked by \fBsmbmount\fR(8)\&. It should not be invoked directly by users\&.
|
||||
|
||||
.PP
|
||||
smbmount searches the normal PATH for smbmnt. You must ensure
|
||||
that the smbmnt version in your path matches the smbmount used.
|
||||
smbmount searches the normal PATH for smbmnt\&. You must ensure that the smbmnt version in your path matches the smbmount used\&.
|
||||
|
||||
.SH "OPTIONS"
|
||||
|
||||
.TP
|
||||
\fB-r\fR
|
||||
mount the filesystem read-only
|
||||
-r
|
||||
mount the filesystem read-only
|
||||
|
||||
|
||||
.TP
|
||||
\fB-u uid\fR
|
||||
specify the uid that the files will
|
||||
be owned by
|
||||
-u uid
|
||||
specify the uid that the files will be owned by
|
||||
|
||||
|
||||
.TP
|
||||
\fB-g gid\fR
|
||||
specify the gid that the files will be
|
||||
owned by
|
||||
-g gid
|
||||
specify the gid that the files will be owned by
|
||||
|
||||
|
||||
.TP
|
||||
\fB-f mask\fR
|
||||
-f mask
|
||||
specify the octal file mask applied
|
||||
|
||||
|
||||
.TP
|
||||
\fB-d mask\fR
|
||||
specify the octal directory mask
|
||||
applied
|
||||
-d mask
|
||||
specify the octal directory mask applied
|
||||
|
||||
|
||||
.TP
|
||||
\fB-o options\fR
|
||||
list of options that are passed as-is to smbfs, if this
|
||||
command is run on a 2.4 or higher Linux kernel.
|
||||
-o options
|
||||
list of options that are passed as-is to smbfs, if this command is run on a 2\&.4 or higher Linux kernel\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-h|--help\fR
|
||||
Print a summary of command line options.
|
||||
-h|--help
|
||||
Print a summary of command line options\&.
|
||||
|
||||
|
||||
.SH "AUTHOR"
|
||||
|
||||
.PP
|
||||
Volker Lendecke, Andrew Tridgell, Michael H. Warfield
|
||||
and others.
|
||||
Volker Lendecke, Andrew Tridgell, Michael H\&. Warfield and others\&.
|
||||
|
||||
.PP
|
||||
The current maintainer of smbfs and the userspace
|
||||
tools \fBsmbmount\fR, \fBsmbumount\fR,
|
||||
and \fBsmbmnt\fR is Urban Widmark <URL:mailto:urban@teststation.com>.
|
||||
The SAMBA Mailing list <URL:mailto:samba@samba.org>
|
||||
is the preferred place to ask questions regarding these programs.
|
||||
The current maintainer of smbfs and the userspace tools \fBsmbmount\fR, \fBsmbumount\fR, and \fBsmbmnt\fR is Urban Widmark\&. The SAMBA Mailing list is the preferred place to ask questions regarding these programs\&.
|
||||
|
||||
.PP
|
||||
The conversion of this manpage for Samba 2.2 was performed
|
||||
by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0
|
||||
was done by Alexander Bokovoy.
|
||||
The conversion of this manpage for Samba 2\&.2 was performed by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
|
||||
|
||||
|
||||
@ -1,214 +1,214 @@
|
||||
.\" This manpage has been automatically generated by docbook2man
|
||||
.\" from a DocBook document. This tool can be found at:
|
||||
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
||||
.\" Please send any bug reports, improvements, comments, patches,
|
||||
.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
||||
.TH "SMBMOUNT" "8" "19 april 2003" "" ""
|
||||
|
||||
.\"Generated by db2man.xsl. Don't modify this, modify the source.
|
||||
.de Sh \" Subsection
|
||||
.br
|
||||
.if t .Sp
|
||||
.ne 5
|
||||
.PP
|
||||
\fB\\$1\fR
|
||||
.PP
|
||||
..
|
||||
.de Sp \" Vertical space (when we can't use .PP)
|
||||
.if t .sp .5v
|
||||
.if n .sp
|
||||
..
|
||||
.de Ip \" List item
|
||||
.br
|
||||
.ie \\n(.$>=3 .ne \\$3
|
||||
.el .ne 3
|
||||
.IP "\\$1" \\$2
|
||||
..
|
||||
.TH "SMBMOUNT" 8 "" "" ""
|
||||
.SH NAME
|
||||
smbmount \- mount an smbfs filesystem
|
||||
.SH SYNOPSIS
|
||||
|
||||
\fBsmbmount\fR \fBservice\fR \fBmount-point\fR [ \fB-o options\fR ]
|
||||
|
||||
.SH "DESCRIPTION"
|
||||
.PP
|
||||
\fBsmbmount\fR mounts a Linux SMB filesystem. It
|
||||
is usually invoked as \fBmount.smbfs\fR by
|
||||
the \fBmount\fR(8) command when using the
|
||||
"-t smbfs" option. This command only works in Linux, and the kernel must
|
||||
support the smbfs filesystem.
|
||||
.PP
|
||||
Options to \fBsmbmount\fR are specified as a comma-separated
|
||||
list of key=value pairs. It is possible to send options other
|
||||
than those listed here, assuming that smbfs supports them. If
|
||||
you get mount failures, check your kernel log for errors on
|
||||
unknown options.
|
||||
.PP
|
||||
\fBsmbmount\fR is a daemon. After mounting it keeps running until
|
||||
the mounted smbfs is umounted. It will log things that happen
|
||||
when in daemon mode using the "machine name" smbmount, so
|
||||
typically this output will end up in \fIlog.smbmount\fR. The \fB smbmount\fR process may also be called mount.smbfs.
|
||||
.PP
|
||||
\fBNOTE:\fR \fBsmbmount\fR
|
||||
calls \fBsmbmnt\fR(8) to do the actual mount. You
|
||||
must make sure that \fBsmbmnt\fR is in the path so
|
||||
that it can be found.
|
||||
.SH "OPTIONS"
|
||||
.TP
|
||||
\fBusername=<arg>\fR
|
||||
specifies the username to connect as. If
|
||||
this is not given, then the environment variable \fB USER\fR is used. This option can also take the
|
||||
form "user%password" or "user/workgroup" or
|
||||
"user/workgroup%password" to allow the password and workgroup
|
||||
to be specified as part of the username.
|
||||
.TP
|
||||
\fBpassword=<arg>\fR
|
||||
specifies the SMB password. If this
|
||||
option is not given then the environment variable
|
||||
\fBPASSWD\fR is used. If it can find
|
||||
no password \fBsmbmount\fR will prompt
|
||||
for a passeword, unless the guest option is
|
||||
given.
|
||||
|
||||
Note that passwords which contain the argument delimiter
|
||||
character (i.e. a comma ',') will failed to be parsed correctly
|
||||
on the command line. However, the same password defined
|
||||
in the PASSWD environment variable or a credentials file (see
|
||||
below) will be read correctly.
|
||||
.TP
|
||||
\fBcredentials=<filename>\fR
|
||||
specifies a file that contains a username and/or password.
|
||||
The format of the file is:
|
||||
.SH "SYNOPSIS"
|
||||
|
||||
.nf
|
||||
\fBsmbmount\fR {service} {mount-point} [-o options]
|
||||
.fi
|
||||
|
||||
.SH "DESCRIPTION"
|
||||
|
||||
.PP
|
||||
\fBsmbmount\fR mounts a Linux SMB filesystem\&. It is usually invoked as \fBmount.smbfs\fR by the \fBmount\fR(8) command when using the "-t smbfs" option\&. This command only works in Linux, and the kernel must support the smbfs filesystem\&.
|
||||
|
||||
.PP
|
||||
Options to \fBsmbmount\fR are specified as a comma-separated list of key=value pairs\&. It is possible to send options other than those listed here, assuming that smbfs supports them\&. If you get mount failures, check your kernel log for errors on unknown options\&.
|
||||
|
||||
.PP
|
||||
\fBsmbmount\fR is a daemon\&. After mounting it keeps running until the mounted smbfs is umounted\&. It will log things that happen when in daemon mode using the "machine name" smbmount, so typically this output will end up in \fIlog\&.smbmount\fR\&. The \fB smbmount\fR process may also be called mount\&.smbfs\&.
|
||||
|
||||
.PP
|
||||
\fBNOTE:\fR \fBsmbmount\fR calls \fBsmbmnt\fR(8) to do the actual mount\&. You must make sure that \fBsmbmnt\fR is in the path so that it can be found\&.
|
||||
|
||||
.SH "OPTIONS"
|
||||
|
||||
.TP
|
||||
username=<arg>
|
||||
specifies the username to connect as\&. If this is not given, then the environment variable \fB USER\fR is used\&. This option can also take the form "user%password" or "user/workgroup" or "user/workgroup%password" to allow the password and workgroup to be specified as part of the username\&.
|
||||
|
||||
|
||||
.TP
|
||||
password=<arg>
|
||||
specifies the SMB password\&. If this option is not given then the environment variable \fBPASSWD\fR is used\&. If it can find no password \fBsmbmount\fR will prompt for a passeword, unless the guest option is given\&.
|
||||
|
||||
|
||||
Note that passwords which contain the argument delimiter character (i\&.e\&. a comma ',') will failed to be parsed correctly on the command line\&. However, the same password defined in the PASSWD environment variable or a credentials file (see below) will be read correctly\&.
|
||||
|
||||
|
||||
.TP
|
||||
credentials=<filename>
|
||||
specifies a file that contains a username and/or password\&.
|
||||
The format of the file is:
|
||||
.nf
|
||||
|
||||
username = <value>
|
||||
password = <value>
|
||||
.fi
|
||||
|
||||
This is preferred over having passwords in plaintext in a
|
||||
shared file, such as \fI/etc/fstab\fR. Be sure to protect any
|
||||
credentials file properly.
|
||||
|
||||
This is preferred over having passwords in plaintext in a shared file, such as \fI/etc/fstab\fR\&. Be sure to protect any credentials file properly\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBkrb\fR
|
||||
Use kerberos (Active Directory).
|
||||
krb
|
||||
Use kerberos (Active Directory)\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBnetbiosname=<arg>\fR
|
||||
sets the source NetBIOS name. It defaults
|
||||
to the local hostname.
|
||||
netbiosname=<arg>
|
||||
sets the source NetBIOS name\&. It defaults to the local hostname\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBuid=<arg>\fR
|
||||
sets the uid that will own all files on
|
||||
the mounted filesystem.
|
||||
It may be specified as either a username or a numeric uid.
|
||||
uid=<arg>
|
||||
sets the uid that will own all files on the mounted filesystem\&. It may be specified as either a username or a numeric uid\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBgid=<arg>\fR
|
||||
sets the gid that will own all files on
|
||||
the mounted filesystem.
|
||||
It may be specified as either a groupname or a numeric
|
||||
gid.
|
||||
gid=<arg>
|
||||
sets the gid that will own all files on the mounted filesystem\&. It may be specified as either a groupname or a numeric gid\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBport=<arg>\fR
|
||||
sets the remote SMB port number. The default
|
||||
is 139.
|
||||
port=<arg>
|
||||
sets the remote SMB port number\&. The default is 139\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBfmask=<arg>\fR
|
||||
sets the file mask. This determines the
|
||||
permissions that remote files have in the local filesystem.
|
||||
The default is based on the current umask.
|
||||
fmask=<arg>
|
||||
sets the file mask\&. This determines the permissions that remote files have in the local filesystem\&. The default is based on the current umask\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBdmask=<arg>\fR
|
||||
Sets the directory mask. This determines the
|
||||
permissions that remote directories have in the local filesystem.
|
||||
The default is based on the current umask.
|
||||
dmask=<arg>
|
||||
Sets the directory mask\&. This determines the permissions that remote directories have in the local filesystem\&. The default is based on the current umask\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBdebug=<arg>\fR
|
||||
Sets the debug level. This is useful for
|
||||
tracking down SMB connection problems. A suggested value to
|
||||
start with is 4. If set too high there will be a lot of
|
||||
output, possibly hiding the useful output.
|
||||
debug=<arg>
|
||||
Sets the debug level\&. This is useful for tracking down SMB connection problems\&. A suggested value to start with is 4\&. If set too high there will be a lot of output, possibly hiding the useful output\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBip=<arg>\fR
|
||||
Sets the destination host or IP address.
|
||||
ip=<arg>
|
||||
Sets the destination host or IP address\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBworkgroup=<arg>\fR
|
||||
Sets the workgroup on the destination
|
||||
workgroup=<arg>
|
||||
Sets the workgroup on the destination
|
||||
|
||||
|
||||
.TP
|
||||
\fBsockopt=<arg>\fR
|
||||
Sets the TCP socket options. See the \fBsmb.conf\fR(5) \fIsocket options\fR option.
|
||||
sockopt=<arg>
|
||||
Sets the TCP socket options\&. See the \fBsmb.conf\fR(5) \fIsocket options\fR option\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBscope=<arg>\fR
|
||||
Sets the NetBIOS scope
|
||||
scope=<arg>
|
||||
Sets the NetBIOS scope
|
||||
|
||||
|
||||
.TP
|
||||
\fBguest\fR
|
||||
Don't prompt for a password
|
||||
guest
|
||||
Don't prompt for a password
|
||||
|
||||
|
||||
.TP
|
||||
\fBro\fR
|
||||
mount read-only
|
||||
ro
|
||||
mount read-only
|
||||
|
||||
|
||||
.TP
|
||||
\fBrw\fR
|
||||
mount read-write
|
||||
rw
|
||||
mount read-write
|
||||
|
||||
|
||||
.TP
|
||||
\fBiocharset=<arg>\fR
|
||||
sets the charset used by the Linux side for codepage
|
||||
to charset translations (NLS). Argument should be the
|
||||
name of a charset, like iso8859-1. (Note: only kernel
|
||||
2.4.0 or later)
|
||||
iocharset=<arg>
|
||||
sets the charset used by the Linux side for codepage to charset translations (NLS)\&. Argument should be the name of a charset, like iso8859-1\&. (Note: only kernel 2\&.4\&.0 or later)
|
||||
|
||||
|
||||
.TP
|
||||
\fBcodepage=<arg>\fR
|
||||
sets the codepage the server uses. See the iocharset
|
||||
option. Example value cp850. (Note: only kernel 2.4.0
|
||||
or later)
|
||||
codepage=<arg>
|
||||
sets the codepage the server uses\&. See the iocharset option\&. Example value cp850\&. (Note: only kernel 2\&.4\&.0 or later)
|
||||
|
||||
|
||||
.TP
|
||||
\fBttl=<arg>\fR
|
||||
sets how long a directory listing is cached in milliseconds
|
||||
(also affects visibility of file size and date
|
||||
changes). A higher value means that changes on the
|
||||
server take longer to be noticed but it can give
|
||||
better performance on large directories, especially
|
||||
over long distances. Default is 1000ms but something
|
||||
like 10000ms (10 seconds) is probably more reasonable
|
||||
in many cases.
|
||||
(Note: only kernel 2.4.2 or later)
|
||||
ttl=<arg>
|
||||
sets how long a directory listing is cached in milliseconds (also affects visibility of file size and date changes)\&. A higher value means that changes on the server take longer to be noticed but it can give better performance on large directories, especially over long distances\&. Default is 1000ms but something like 10000ms (10 seconds) is probably more reasonable in many cases\&. (Note: only kernel 2\&.4\&.2 or later)
|
||||
|
||||
|
||||
.SH "ENVIRONMENT VARIABLES"
|
||||
|
||||
.PP
|
||||
The variable \fBUSER\fR may contain the username of the
|
||||
person using the client. This information is used only if the
|
||||
protocol level is high enough to support session-level
|
||||
passwords. The variable can be used to set both username and
|
||||
password by using the format username%password.
|
||||
The variable \fBUSER\fR may contain the username of the person using the client\&. This information is used only if the protocol level is high enough to support session-level passwords\&. The variable can be used to set both username and password by using the format username%password\&.
|
||||
|
||||
.PP
|
||||
The variable \fBPASSWD\fR may contain the password of the
|
||||
person using the client. This information is used only if the
|
||||
protocol level is high enough to support session-level
|
||||
passwords.
|
||||
The variable \fBPASSWD\fR may contain the password of the person using the client\&. This information is used only if the protocol level is high enough to support session-level passwords\&.
|
||||
|
||||
.PP
|
||||
The variable \fBPASSWD_FILE\fR may contain the pathname
|
||||
of a file to read the password from. A single line of input is
|
||||
read and used as the password.
|
||||
The variable \fBPASSWD_FILE\fR may contain the pathname of a file to read the password from\&. A single line of input is read and used as the password\&.
|
||||
|
||||
.SH "BUGS"
|
||||
|
||||
.PP
|
||||
Passwords and other options containing , can not be handled.
|
||||
For passwords an alternative way of passing them is in a credentials
|
||||
file or in the PASSWD environment.
|
||||
Passwords and other options containing , can not be handled\&. For passwords an alternative way of passing them is in a credentials file or in the PASSWD environment\&.
|
||||
|
||||
.PP
|
||||
The credentials file does not handle usernames or passwords with
|
||||
leading space.
|
||||
The credentials file does not handle usernames or passwords with leading space\&.
|
||||
|
||||
.PP
|
||||
One smbfs bug is important enough to mention here, even if it
|
||||
is a bit misplaced:
|
||||
.TP 0.2i
|
||||
One smbfs bug is important enough to mention here, even if it is a bit misplaced:
|
||||
|
||||
.TP 3
|
||||
\(bu
|
||||
Mounts sometimes stop working. This is usually
|
||||
caused by smbmount terminating. Since smbfs needs smbmount to
|
||||
reconnect when the server disconnects, the mount will eventually go
|
||||
dead. An umount/mount normally fixes this. At least 2 ways to
|
||||
trigger this bug are known.
|
||||
Mounts sometimes stop working\&. This is usually caused by smbmount terminating\&. Since smbfs needs smbmount to reconnect when the server disconnects, the mount will eventually go dead\&. An umount/mount normally fixes this\&. At least 2 ways to trigger this bug are known\&.
|
||||
|
||||
.LP
|
||||
|
||||
.PP
|
||||
Note that the typical response to a bug report is suggestion
|
||||
to try the latest version first. So please try doing that first,
|
||||
and always include which versions you use of relevant software
|
||||
when reporting bugs (minimum: samba, kernel, distribution)
|
||||
Note that the typical response to a bug report is suggestion to try the latest version first\&. So please try doing that first, and always include which versions you use of relevant software when reporting bugs (minimum: samba, kernel, distribution)
|
||||
|
||||
.SH "SEE ALSO"
|
||||
|
||||
.PP
|
||||
Documentation/filesystems/smbfs.txt in the linux kernel
|
||||
source tree may contain additional options and information.
|
||||
Documentation/filesystems/smbfs\&.txt in the linux kernel source tree may contain additional options and information\&.
|
||||
|
||||
.PP
|
||||
FreeBSD also has a smbfs, but it is not related to smbmount
|
||||
|
||||
.PP
|
||||
For Solaris, HP-UX and others you may want to look at \fBsmbsh\fR(1) or at other solutions, such as
|
||||
Sharity or perhaps replacing the SMB server with a NFS server.
|
||||
For Solaris, HP-UX and others you may want to look at \fBsmbsh\fR(1) or at other solutions, such as Sharity or perhaps replacing the SMB server with a NFS server\&.
|
||||
|
||||
.SH "AUTHOR"
|
||||
|
||||
.PP
|
||||
Volker Lendecke, Andrew Tridgell, Michael H. Warfield
|
||||
and others.
|
||||
Volker Lendecke, Andrew Tridgell, Michael H\&. Warfield and others\&.
|
||||
|
||||
.PP
|
||||
The current maintainer of smbfs and the userspace
|
||||
tools \fBsmbmount\fR, \fBsmbumount\fR,
|
||||
and \fBsmbmnt\fR is Urban Widmark <URL:mailto:urban@teststation.com>.
|
||||
The SAMBA Mailing list <URL:mailto:samba@samba.org>
|
||||
is the preferred place to ask questions regarding these programs.
|
||||
The current maintainer of smbfs and the userspace tools \fBsmbmount\fR, \fBsmbumount\fR, and \fBsmbmnt\fR is Urban Widmark\&. The SAMBA Mailing list is the preferred place to ask questions regarding these programs\&.
|
||||
|
||||
.PP
|
||||
The conversion of this manpage for Samba 2.2 was performed
|
||||
by Gerald Carter. The conversion to DocBook XML 4.2 for Samba 3.0
|
||||
was done by Alexander Bokovoy.
|
||||
The conversion of this manpage for Samba 2\&.2 was performed by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
|
||||
|
||||
|
||||
@ -1,155 +1,111 @@
|
||||
.\" This manpage has been automatically generated by docbook2man
|
||||
.\" from a DocBook document. This tool can be found at:
|
||||
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
||||
.\" Please send any bug reports, improvements, comments, patches,
|
||||
.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
||||
.TH "SMBPASSWD" "5" "19 april 2003" "" ""
|
||||
|
||||
.\"Generated by db2man.xsl. Don't modify this, modify the source.
|
||||
.de Sh \" Subsection
|
||||
.br
|
||||
.if t .Sp
|
||||
.ne 5
|
||||
.PP
|
||||
\fB\\$1\fR
|
||||
.PP
|
||||
..
|
||||
.de Sp \" Vertical space (when we can't use .PP)
|
||||
.if t .sp .5v
|
||||
.if n .sp
|
||||
..
|
||||
.de Ip \" List item
|
||||
.br
|
||||
.ie \\n(.$>=3 .ne \\$3
|
||||
.el .ne 3
|
||||
.IP "\\$1" \\$2
|
||||
..
|
||||
.TH "SMBPASSWD" 5 "" "" ""
|
||||
.SH NAME
|
||||
smbpasswd \- The Samba encrypted password file
|
||||
.SH SYNOPSIS
|
||||
.SH "SYNOPSIS"
|
||||
|
||||
.PP
|
||||
\fIsmbpasswd\fR
|
||||
|
||||
.SH "DESCRIPTION"
|
||||
|
||||
.PP
|
||||
This tool is part of the \fBSamba\fR(7) suite.
|
||||
This tool is part of the \fBSamba\fR(7) suite\&.
|
||||
|
||||
.PP
|
||||
smbpasswd is the Samba 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.
|
||||
smbpasswd is the Samba 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\&.
|
||||
|
||||
.SH "FILE FORMAT"
|
||||
|
||||
.PP
|
||||
The format of the smbpasswd file used by Samba 2.2
|
||||
is very similar to the familiar Unix \fIpasswd(5)\fR
|
||||
file. It is an ASCII file containing one line for each user. Each field
|
||||
ithin 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:
|
||||
.TP
|
||||
\fBname\fR
|
||||
This is the user name. It must be a name that
|
||||
already exists in the standard UNIX passwd file.
|
||||
.TP
|
||||
\fBuid\fR
|
||||
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 smbpasswd file entry as being valid for a user.
|
||||
.TP
|
||||
\fBLanman Password Hash\fR
|
||||
This is the LANMAN hash of the user's password,
|
||||
encoded as 32 hex digits. The LANMAN hash is created by DES
|
||||
encrypting a well known string with the user's password as the
|
||||
DES key. This is the same password used by Windows 95/98 machines.
|
||||
Note that this password hash is regarded as weak as it is
|
||||
vulnerable to dictionary attacks and if two users choose the
|
||||
same password this entry will be identical (i.e. the password
|
||||
is not "salted" as the UNIX password is). If the user has a
|
||||
null password this field will contain the characters "NO PASSWORD"
|
||||
as the start of the hex string. If the hex string is equal to
|
||||
32 'X' characters then the user's account is marked as
|
||||
disabled and the user will not be able to
|
||||
log onto the Samba server.
|
||||
The format of the smbpasswd file used by Samba 2\&.2 is very similar to the familiar Unix \fIpasswd(5)\fR file\&. It is an ASCII file containing one line for each user\&. Each field ithin 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:
|
||||
|
||||
\fBWARNING !!\fR 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 \fBplain text
|
||||
equivalents\fR and must \fBNOT\fR be made
|
||||
available to anyone but the root user. To protect these passwords
|
||||
the smbpasswd file is placed in a directory with read and
|
||||
traverse access only to the root user and the smbpasswd file
|
||||
itself must be set to be read/write only by root, with no
|
||||
other access.
|
||||
.TP
|
||||
\fBNT Password Hash\fR
|
||||
This is the Windows NT hash of the user's
|
||||
password, encoded as 32 hex digits. The Windows NT hash is
|
||||
created by taking the user's password as represented in
|
||||
16-bit, little-endian UNICODE and then applying the MD4
|
||||
(internet rfc1321) hashing algorithm to it.
|
||||
name
|
||||
This is the user name\&. It must be a name that already exists in the standard UNIX passwd file\&.
|
||||
|
||||
This password hash is considered more secure than
|
||||
the LANMAN Password Hash 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 "salted" as the UNIX password is).
|
||||
|
||||
\fBWARNING !!\fR. 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 \fBplain text
|
||||
equivalents\fR and must \fBNOT\fR be made
|
||||
available to anyone but the root user. To protect these passwords
|
||||
the smbpasswd file is placed in a directory with read and
|
||||
traverse access only to the root user and the smbpasswd file
|
||||
itself must be set to be read/write only by root, with no
|
||||
other access.
|
||||
.TP
|
||||
\fBAccount Flags\fR
|
||||
This section contains flags that describe
|
||||
the attributes of the users account. In the Samba 2.2 release
|
||||
this field is bracketed by '[' and ']' characters and is always
|
||||
13 characters in length (including the '[' and ']' characters).
|
||||
The contents of this field may be any of the following characters:
|
||||
.RS
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
\fBU\fR - This means
|
||||
this is a "User" account, i.e. an ordinary user. Only User
|
||||
and Workstation Trust accounts are currently supported
|
||||
in the smbpasswd file.
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
\fBN\fR - This means the
|
||||
account has no password (the passwords in the fields LANMAN
|
||||
Password Hash and NT Password Hash are ignored). Note that this
|
||||
will only allow users to log on with no password if the \fI null passwords\fR parameter is set in the \fBsmb.conf\fR(5) config file.
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
\fBD\fR - This means the account
|
||||
is disabled and no SMB/CIFS logins will be allowed for this user.
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
\fBW\fR - This means this account
|
||||
is a "Workstation Trust" 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.
|
||||
.RE
|
||||
uid
|
||||
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 smbpasswd file entry as being valid for a user\&.
|
||||
|
||||
|
||||
Other flags may be added as the code is extended in future.
|
||||
The rest of this field space is filled in with spaces.
|
||||
.TP
|
||||
\fBLast Change Time\fR
|
||||
This field consists of the time the account was
|
||||
last modified. It consists of the characters 'LCT-' (standing for
|
||||
"Last Change Time") followed by a numeric encoding of the UNIX time
|
||||
in seconds since the epoch (1970) that the last change was made.
|
||||
Lanman Password Hash
|
||||
This is the LANMAN hash of the user's password, encoded as 32 hex digits\&. The LANMAN hash is created by DES encrypting a well known string with the user's password as the DES key\&. This is the same password used by Windows 95/98 machines\&. Note that this password hash is regarded as weak as it is vulnerable to dictionary attacks and if two users choose the same password this entry will be identical (i\&.e\&. the password is not "salted" as the UNIX password is)\&. If the user has a null password this field will contain the characters "NO PASSWORD" as the start of the hex string\&. If the hex string is equal to 32 'X' characters then the user's account is marked as \fBdisabled\fR and the user will not be able to log onto the Samba server\&.
|
||||
|
||||
|
||||
\fBWARNING !!\fR 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 \fBplain text equivalents\fR and must \fBNOT\fR be made available to anyone but the root user\&. To protect these passwords the smbpasswd file is placed in a directory with read and traverse access only to the root user and the smbpasswd file itself must be set to be read/write only by root, with no other access\&.
|
||||
|
||||
|
||||
.TP
|
||||
NT Password Hash
|
||||
This is the Windows NT hash of the user's password, encoded as 32 hex digits\&. The Windows NT hash is created by taking the user's password as represented in 16-bit, little-endian UNICODE and then applying the MD4 (internet rfc1321) hashing algorithm to it\&.
|
||||
|
||||
|
||||
This password hash is considered more secure than the LANMAN Password Hash 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 "salted" as the UNIX password is)\&.
|
||||
|
||||
|
||||
\fBWARNING !!\fR\&. 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 \fBplain text equivalents\fR and must \fBNOT\fR be made available to anyone but the root user\&. To protect these passwords the smbpasswd file is placed in a directory with read and traverse access only to the root user and the smbpasswd file itself must be set to be read/write only by root, with no other access\&.
|
||||
|
||||
|
||||
.TP
|
||||
Account Flags
|
||||
This section contains flags that describe the attributes of the users account\&. In the Samba 2\&.2 release this field is bracketed by '[' and ']' characters and is always 13 characters in length (including the '[' and ']' characters)\&. The contents of this field may be any of the following characters:
|
||||
|
||||
|
||||
\fBU\fR - This means this is a "User" account, i\&.e\&. an ordinary user\&. Only User and Workstation Trust accounts are currently supported in the smbpasswd file\&.
|
||||
|
||||
\fBN\fR - This means the account has no password (the passwords in the fields LANMAN Password Hash and NT Password Hash are ignored)\&. Note that this will only allow users to log on with no password if the \fI null passwords\fR parameter is set in the \fBsmb.conf\fR(5) config file\&.
|
||||
|
||||
\fBD\fR - This means the account is disabled and no SMB/CIFS logins will be allowed for this user\&.
|
||||
|
||||
\fBW\fR - This means this account is a "Workstation Trust" 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\&.
|
||||
|
||||
Other flags may be added as the code is extended in future\&. The rest of this field space is filled in with spaces\&.
|
||||
|
||||
|
||||
.TP
|
||||
Last Change Time
|
||||
This field consists of the time the account was last modified\&. It consists of the characters 'LCT-' (standing for "Last Change Time") followed by a numeric encoding of the UNIX time in seconds since the epoch (1970) that the last change was made\&.
|
||||
|
||||
|
||||
.PP
|
||||
All other colon separated fields are ignored at this time.
|
||||
All other colon separated fields are ignored at this time\&.
|
||||
|
||||
.SH "VERSION"
|
||||
|
||||
.PP
|
||||
This man page is correct for version 3.0 of
|
||||
the Samba suite.
|
||||
This man page is correct for version 3\&.0 of the Samba suite\&.
|
||||
|
||||
.SH "SEE ALSO"
|
||||
|
||||
.PP
|
||||
\fBsmbpasswd\fR(8), \fBSamba\fR(7), and
|
||||
the Internet RFC1321 for details on the MD4 algorithm.
|
||||
\fBsmbpasswd\fR(8), \fBSamba\fR(7), and the Internet RFC1321 for details on the MD4 algorithm\&.
|
||||
|
||||
.SH "AUTHOR"
|
||||
|
||||
.PP
|
||||
The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.
|
||||
The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
|
||||
|
||||
.PP
|
||||
The original Samba man pages were written by Karl Auer.
|
||||
The man page sources were converted to YODL format (another
|
||||
excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2
|
||||
for Samba 3.0 was done by Alexander Bokovoy.
|
||||
The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
|
||||
|
||||
|
||||
@ -1,288 +1,219 @@
|
||||
.\" This manpage has been automatically generated by docbook2man
|
||||
.\" from a DocBook document. This tool can be found at:
|
||||
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
||||
.\" Please send any bug reports, improvements, comments, patches,
|
||||
.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
||||
.TH "SMBPASSWD" "8" "19 april 2003" "" ""
|
||||
|
||||
.\"Generated by db2man.xsl. Don't modify this, modify the source.
|
||||
.de Sh \" Subsection
|
||||
.br
|
||||
.if t .Sp
|
||||
.ne 5
|
||||
.PP
|
||||
\fB\\$1\fR
|
||||
.PP
|
||||
..
|
||||
.de Sp \" Vertical space (when we can't use .PP)
|
||||
.if t .sp .5v
|
||||
.if n .sp
|
||||
..
|
||||
.de Ip \" List item
|
||||
.br
|
||||
.ie \\n(.$>=3 .ne \\$3
|
||||
.el .ne 3
|
||||
.IP "\\$1" \\$2
|
||||
..
|
||||
.TH "SMBPASSWD" 8 "" "" ""
|
||||
.SH NAME
|
||||
smbpasswd \- change a user's SMB password
|
||||
.SH SYNOPSIS
|
||||
.SH "SYNOPSIS"
|
||||
|
||||
\fBsmbpasswd\fR [ \fB-a\fR ] [ \fB-x\fR ] [ \fB-d\fR ] [ \fB-e\fR ] [ \fB-D debuglevel\fR ] [ \fB-n\fR ] [ \fB-r <remote machine>\fR ] [ \fB-R <name resolve order>\fR ] [ \fB-m\fR ] [ \fB-U username[%password]\fR ] [ \fB-h\fR ] [ \fB-s\fR ] [ \fB-w pass\fR ] [ \fB-i\fR ] [ \fB-L\fR ] [ \fBusername\fR ]
|
||||
.nf
|
||||
\fBsmbpasswd\fR [-a] [-x] [-d] [-e] [-D debuglevel] [-n] [-r <remote machine>] [-R <name resolve order>] [-m] [-U username[%password]] [-h] [-s] [-w pass] [-i] [-L] [username]
|
||||
|
||||
.fi
|
||||
|
||||
.SH "DESCRIPTION"
|
||||
|
||||
.PP
|
||||
This tool is part of the \fBSamba\fR(7) suite.
|
||||
This tool is part of the \fBSamba\fR(7) suite\&.
|
||||
|
||||
.PP
|
||||
The smbpasswd program has several different
|
||||
functions, depending on whether it is run by the \fBroot\fR 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.
|
||||
The smbpasswd program has several different functions, depending on whether it is run by the \fBroot\fR 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\&.
|
||||
|
||||
.PP
|
||||
By default (when run with no arguments) it will attempt to
|
||||
change the current user's SMB password on the local machine. This is
|
||||
similar to the way the \fBpasswd(1)\fR program works. \fB smbpasswd\fR differs from how the passwd program works
|
||||
however in that it is not \fBsetuid root\fR but works in
|
||||
a client-server mode and communicates with a
|
||||
locally running \fBsmbd\fR(8). As a consequence in order for this to
|
||||
succeed the smbd daemon must be running on the local machine. On a
|
||||
UNIX machine the encrypted SMB passwords are usually stored in
|
||||
the \fBsmbpasswd\fR(5) file.
|
||||
By default (when run with no arguments) it will attempt to change the current user's SMB password on the local machine\&. This is similar to the way the \fBpasswd(1)\fR program works\&. \fB smbpasswd\fR differs from how the passwd program works however in that it is not \fBsetuid root\fR but works in a client-server mode and communicates with a locally running \fBsmbd\fR(8)\&. As a consequence in order for this to succeed the smbd daemon must be running on the local machine\&. On a UNIX machine the encrypted SMB passwords are usually stored in the \fBsmbpasswd\fR(5) file\&.
|
||||
|
||||
.PP
|
||||
When run by an ordinary user with no options, smbpasswd
|
||||
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 smbpasswd file) then just press
|
||||
the <Enter> key when asked for your old password.
|
||||
When run by an ordinary user with no options, smbpasswd 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 smbpasswd file) then just press the <Enter> key when asked for your old password\&.
|
||||
|
||||
.PP
|
||||
smbpasswd 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 (\fI-r\fR) and \fI-U\fR options
|
||||
below.
|
||||
smbpasswd 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 (\fI-r\fR) and \fI-U\fR options below\&.
|
||||
|
||||
.PP
|
||||
When run by root, smbpasswd allows new users to be added
|
||||
and deleted in the smbpasswd file, as well as allows changes to
|
||||
the attributes of the user in this file to be made. When run by root, \fB smbpasswd\fR accesses the local smbpasswd file
|
||||
directly, thus enabling changes to be made even if smbd is not
|
||||
running.
|
||||
When run by root, smbpasswd allows new users to be added and deleted in the smbpasswd file, as well as allows changes to the attributes of the user in this file to be made\&. When run by root, \fB smbpasswd\fR accesses the local smbpasswd file directly, thus enabling changes to be made even if smbd is not running\&.
|
||||
|
||||
.SH "OPTIONS"
|
||||
|
||||
.TP
|
||||
\fB-a\fR
|
||||
This option specifies that the username
|
||||
following should be added to the local smbpasswd file, with the
|
||||
new password typed (type <Enter> for the old password). This
|
||||
option is ignored if the username following already exists in
|
||||
the smbpasswd file and it is treated like a regular change
|
||||
password command. Note that the default passdb backends require
|
||||
the user to already exist in the system password file (usually
|
||||
\fI/etc/passwd\fR), else the request to add the
|
||||
user will fail.
|
||||
-a
|
||||
This option specifies that the username following should be added to the local smbpasswd file, with the new password typed (type <Enter> for the old password)\&. This option is ignored if the username following already exists in the smbpasswd file and it is treated like a regular change password command\&. Note that the default passdb backends require the user to already exist in the system password file (usually \fI/etc/passwd\fR), else the request to add the user will fail\&.
|
||||
|
||||
|
||||
This option is only available when running smbpasswd as root\&.
|
||||
|
||||
|
||||
This option is only available when running smbpasswd
|
||||
as root.
|
||||
.TP
|
||||
\fB-x\fR
|
||||
This option specifies that the username
|
||||
following should be deleted from the local smbpasswd file.
|
||||
-x
|
||||
This option specifies that the username following should be deleted from the local smbpasswd file\&.
|
||||
|
||||
|
||||
This option is only available when running smbpasswd as root\&.
|
||||
|
||||
|
||||
This option is only available when running smbpasswd as
|
||||
root.
|
||||
.TP
|
||||
\fB-d\fR
|
||||
This option specifies that the username following
|
||||
should be disabled in the local smbpasswd
|
||||
file. This is done by writing a 'D' flag
|
||||
into the account control space in the smbpasswd file. Once this
|
||||
is done all attempts to authenticate via SMB using this username
|
||||
will fail.
|
||||
-d
|
||||
This option specifies that the username following should be \fBdisabled\fR in the local smbpasswd file\&. This is done by writing a \fB'D'\fR flag into the account control space in the smbpasswd file\&. Once this is done all attempts to authenticate via SMB using this username will fail\&.
|
||||
|
||||
|
||||
If the smbpasswd file is in the 'old' format (pre-Samba 2\&.0 format) there is no space in the user's password entry to write this information and the command will FAIL\&. See \fBsmbpasswd\fR(5) for details on the 'old' and new password file formats\&.
|
||||
|
||||
|
||||
This option is only available when running smbpasswd as root\&.
|
||||
|
||||
If the smbpasswd file is in the 'old' format (pre-Samba 2.0
|
||||
format) there is no space in the user's password entry to write
|
||||
this information and the command will FAIL. See \fBsmbpasswd\fR(5) for details on the 'old' and new password file formats.
|
||||
|
||||
This option is only available when running smbpasswd as
|
||||
root.
|
||||
.TP
|
||||
\fB-e\fR
|
||||
This option specifies that the username following
|
||||
should be enabled in the local smbpasswd 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.
|
||||
-e
|
||||
This option specifies that the username following should be \fBenabled\fR in the local smbpasswd 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\&.
|
||||
|
||||
|
||||
If the smbpasswd file is in the 'old' format, then \fB smbpasswd\fR will FAIL to enable the account\&. See \fBsmbpasswd\fR(5) for details on the 'old' and new password file formats\&.
|
||||
|
||||
|
||||
This option is only available when running smbpasswd as root\&.
|
||||
|
||||
If the smbpasswd file is in the 'old' format, then \fB smbpasswd\fR will FAIL to enable the account.
|
||||
See \fBsmbpasswd\fR(5) for
|
||||
details on the 'old' and new password file formats.
|
||||
|
||||
This option is only available when running smbpasswd as root.
|
||||
.TP
|
||||
\fB-D debuglevel\fR
|
||||
\fIdebuglevel\fR is an integer
|
||||
from 0 to 10. The default value if this parameter is not specified
|
||||
is zero.
|
||||
-D debuglevel
|
||||
\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
|
||||
|
||||
|
||||
The higher this value, the more detail will be logged to the log files about the activities of smbpasswd\&. At level 0, only critical errors and serious warnings will be logged\&.
|
||||
|
||||
|
||||
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\&.
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
.TP
|
||||
\fB-n\fR
|
||||
This option specifies that the username following
|
||||
should have their password set to null (i.e. a blank password) in
|
||||
the local smbpasswd file. This is done by writing the string "NO
|
||||
PASSWORD" as the first part of the first password stored in the
|
||||
smbpasswd file.
|
||||
-n
|
||||
This option specifies that the username following should have their password set to null (i\&.e\&. a blank password) in the local smbpasswd file\&. This is done by writing the string "NO PASSWORD" as the first part of the first password stored in the smbpasswd file\&.
|
||||
|
||||
|
||||
Note that to allow users to logon to a Samba server once the password has been set to "NO PASSWORD" in the smbpasswd file the administrator must set the following parameter in the [global] section of the \fIsmb\&.conf\fR file :
|
||||
|
||||
Note that to allow users to logon to a Samba server once
|
||||
the password has been set to "NO PASSWORD" in the smbpasswd
|
||||
file the administrator must set the following parameter in the [global]
|
||||
section of the \fIsmb.conf\fR file :
|
||||
|
||||
\fBnull passwords = yes\fR
|
||||
|
||||
This option is only available when running smbpasswd as
|
||||
root.
|
||||
.TP
|
||||
\fB-r remote machine name\fR
|
||||
This option allows a user to specify what machine
|
||||
they wish to change their password on. Without this parameter
|
||||
smbpasswd defaults to the local host. The \fIremote
|
||||
machine name\fR is the NetBIOS name of the SMB/CIFS
|
||||
server to contact to attempt the password change. This name is
|
||||
resolved into an IP address using the standard name resolution
|
||||
mechanism in all programs of the Samba suite. See the \fI-R
|
||||
name resolve order\fR parameter for details on changing
|
||||
this resolving mechanism.
|
||||
|
||||
The username whose password is changed is that of the
|
||||
current UNIX logged on user. See the \fI-U username\fR
|
||||
parameter for details on changing the password for a different
|
||||
username.
|
||||
This option is only available when running smbpasswd as root\&.
|
||||
|
||||
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).
|
||||
|
||||
\fBNote\fR 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.
|
||||
.TP
|
||||
\fB-R name resolve order\fR
|
||||
This option allows the user of smbpasswd to determine
|
||||
what name resolution services to use when looking up the NetBIOS
|
||||
name of the host being connected to.
|
||||
-r remote machine name
|
||||
This option allows a user to specify what machine they wish to change their password on\&. Without this parameter smbpasswd defaults to the local host\&. The \fIremote machine name\fR is the NetBIOS name of the SMB/CIFS server to contact to attempt the password change\&. This name is resolved into an IP address using the standard name resolution mechanism in all programs of the Samba suite\&. See the \fI-R name resolve order\fR parameter for details on changing this resolving mechanism\&.
|
||||
|
||||
The options are :"lmhosts", "host", "wins" and "bcast". They
|
||||
cause names to be resolved as follows:
|
||||
.RS
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
lmhosts: Lookup an IP
|
||||
address in the Samba lmhosts file. If the line in lmhosts has
|
||||
no name type attached to the NetBIOS name (see the \fBlmhosts\fR(5) for details) then
|
||||
any name type matches for lookup.
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
host: Do a standard host
|
||||
name to IP address resolution, using the system \fI/etc/hosts
|
||||
\fR, NIS, or DNS lookups. This method of name resolution
|
||||
is operating system depended for instance on IRIX or Solaris this
|
||||
may be controlled by the \fI/etc/nsswitch.conf\fR
|
||||
file). Note that this method is only used if the NetBIOS name
|
||||
type being queried is the 0x20 (server) name type, otherwise
|
||||
it is ignored.
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
wins: Query a name with
|
||||
the IP address listed in the \fIwins server\fR
|
||||
parameter. If no WINS server has been specified this method
|
||||
will be ignored.
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
bcast: Do a broadcast on
|
||||
each of the known local interfaces listed in the
|
||||
\fIinterfaces\fR parameter. This is the least
|
||||
reliable of the name resolution methods as it depends on the
|
||||
target host being on a locally connected subnet.
|
||||
.RE
|
||||
|
||||
The default order is \fBlmhosts, host, wins, bcast\fR
|
||||
and without this parameter or any entry in the \fBsmb.conf\fR(5) file the name resolution methods will
|
||||
be attempted in this order.
|
||||
.TP
|
||||
\fB-m\fR
|
||||
This option tells smbpasswd that the account
|
||||
being changed is a MACHINE account. Currently this is used
|
||||
when Samba is being used as an NT Primary Domain Controller.
|
||||
The username whose password is changed is that of the current UNIX logged on user\&. See the \fI-U username\fR parameter for details on changing the password for a different username\&.
|
||||
|
||||
|
||||
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)\&.
|
||||
|
||||
|
||||
\fBNote\fR 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\&.
|
||||
|
||||
This option is only available when running smbpasswd as root.
|
||||
.TP
|
||||
\fB-U username\fR
|
||||
This option may only be used in conjunction
|
||||
with the \fI-r\fR 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.
|
||||
.TP
|
||||
\fB-h\fR
|
||||
This option prints the help string for \fB smbpasswd\fR, selecting the correct one for running as root
|
||||
or as an ordinary user.
|
||||
.TP
|
||||
\fB-s\fR
|
||||
This option causes smbpasswd to be silent (i.e.
|
||||
not issue prompts) and to read its old and new passwords from
|
||||
standard input, rather than from \fI/dev/tty\fR
|
||||
(like the \fBpasswd(1)\fR program does). This option
|
||||
is to aid people writing scripts to drive smbpasswd
|
||||
.TP
|
||||
\fB-w password\fR
|
||||
This parameter is only available if Samba
|
||||
has been configured to use the experimental
|
||||
\fB--with-ldapsam\fR option. The \fI-w\fR
|
||||
switch is used to specify the password to be used with the
|
||||
\fIldap admin
|
||||
dn\fR Note that the password is stored in
|
||||
the \fIsecrets.tdb\fR and is keyed off
|
||||
of the admin's DN. This means that if the value of \fIldap
|
||||
admin dn\fR ever changes, the password will need to be
|
||||
manually updated as well.
|
||||
.TP
|
||||
\fB-i\fR
|
||||
This option tells smbpasswd that the account
|
||||
being changed is an interdomain trust account. Currently this is used
|
||||
when Samba is being used as an NT Primary Domain Controller.
|
||||
The account contains the info about another trusted domain.
|
||||
|
||||
This option is only available when running smbpasswd as root.
|
||||
.TP
|
||||
\fB-L\fR
|
||||
Run in local mode.
|
||||
-R name resolve order
|
||||
This option allows the user of smbpasswd to determine what name resolution services to use when looking up the NetBIOS name of the host being connected to\&.
|
||||
|
||||
|
||||
The options are :"lmhosts", "host", "wins" and "bcast"\&. They cause names to be resolved as follows:
|
||||
|
||||
|
||||
\fBlmhosts\fR: Lookup an IP address in the Samba lmhosts file\&. If the line in lmhosts has no name type attached to the NetBIOS name (see the \fBlmhosts\fR(5) for details) then any name type matches for lookup\&.
|
||||
|
||||
\fBhost\fR: Do a standard host name to IP address resolution, using the system \fI/etc/hosts \fR, NIS, or DNS lookups\&. This method of name resolution is operating system depended for instance on IRIX or Solaris this may be controlled by the \fI/etc/nsswitch\&.conf\fR file)\&. Note that this method is only used if the NetBIOS name type being queried is the 0x20 (server) name type, otherwise it is ignored\&.
|
||||
|
||||
\fBwins\fR: Query a name with the IP address listed in the \fIwins server\fR parameter\&. If no WINS server has been specified this method will be ignored\&.
|
||||
|
||||
\fBbcast\fR: Do a broadcast on each of the known local interfaces listed in the \fIinterfaces\fR parameter\&. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet\&.
|
||||
|
||||
The default order is \fBlmhosts, host, wins, bcast\fR and without this parameter or any entry in the \fBsmb.conf\fR(5) file the name resolution methods will be attempted in this order\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fBusername\fR
|
||||
This specifies the username for all of the
|
||||
\fBroot only\fR options to operate on. Only root
|
||||
can specify this parameter as only root has the permission needed
|
||||
to modify attributes directly in the local smbpasswd file.
|
||||
-m
|
||||
This option tells smbpasswd that the account being changed is a MACHINE account\&. Currently this is used when Samba is being used as an NT Primary Domain Controller\&.
|
||||
|
||||
|
||||
This option is only available when running smbpasswd as root\&.
|
||||
|
||||
|
||||
.TP
|
||||
-U username
|
||||
This option may only be used in conjunction with the \fI-r\fR 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\&.
|
||||
|
||||
|
||||
.TP
|
||||
-h
|
||||
This option prints the help string for \fB smbpasswd\fR, selecting the correct one for running as root or as an ordinary user\&.
|
||||
|
||||
|
||||
.TP
|
||||
-s
|
||||
This option causes smbpasswd to be silent (i\&.e\&. not issue prompts) and to read its old and new passwords from standard input, rather than from \fI/dev/tty\fR (like the \fBpasswd(1)\fR program does)\&. This option is to aid people writing scripts to drive smbpasswd
|
||||
|
||||
|
||||
.TP
|
||||
-w password
|
||||
This parameter is only available if Samba has been configured to use the experimental \fB--with-ldapsam\fR option\&. The \fI-w\fR switch is used to specify the password to be used with the \fIldap admin dn\fR\&. Note that the password is stored in the \fIsecrets\&.tdb\fR and is keyed off of the admin's DN\&. This means that if the value of \fIldap admin dn\fR ever changes, the password will need to be manually updated as well\&.
|
||||
|
||||
|
||||
.TP
|
||||
-i
|
||||
This option tells smbpasswd that the account being changed is an interdomain trust account\&. Currently this is used when Samba is being used as an NT Primary Domain Controller\&. The account contains the info about another trusted domain\&.
|
||||
|
||||
|
||||
This option is only available when running smbpasswd as root\&.
|
||||
|
||||
|
||||
.TP
|
||||
-L
|
||||
Run in local mode\&.
|
||||
|
||||
|
||||
.TP
|
||||
username
|
||||
This specifies the username for all of the \fBroot only\fR options to operate on\&. Only root can specify this parameter as only root has the permission needed to modify attributes directly in the local smbpasswd file\&.
|
||||
|
||||
|
||||
.SH "NOTES"
|
||||
|
||||
.PP
|
||||
Since \fBsmbpasswd\fR works in client-server
|
||||
mode communicating with a local smbd for a non-root user then
|
||||
the smbd daemon must be running for this to work. A common problem
|
||||
is to add a restriction to the hosts that may access the \fB smbd\fR running on the local machine by specifying either \fIallow
|
||||
hosts\fR or \fIdeny hosts\fR entry in
|
||||
the \fBsmb.conf\fR(5) file and neglecting to
|
||||
allow "localhost" access to the smbd.
|
||||
Since \fBsmbpasswd\fR works in client-server mode communicating with a local smbd for a non-root user then the smbd daemon must be running for this to work\&. A common problem is to add a restriction to the hosts that may access the \fB smbd\fR running on the local machine by specifying either \fIallow hosts\fR or \fIdeny hosts\fR entry in the \fBsmb.conf\fR(5) file and neglecting to allow "localhost" access to the smbd\&.
|
||||
|
||||
.PP
|
||||
In addition, the smbpasswd command is only useful if Samba
|
||||
has been set up to use encrypted passwords. See the document "LanMan and NT Password Encryption in Samba" in the docs directory for details
|
||||
on how to do this.
|
||||
In addition, the smbpasswd command is only useful if Samba has been set up to use encrypted passwords\&. See the document "LanMan and NT Password Encryption in Samba" in the docs directory for details on how to do this\&.
|
||||
|
||||
.SH "VERSION"
|
||||
|
||||
.PP
|
||||
This man page is correct for version 3.0 of the Samba suite.
|
||||
This man page is correct for version 3\&.0 of the Samba suite\&.
|
||||
|
||||
.SH "SEE ALSO"
|
||||
|
||||
.PP
|
||||
\fBsmbpasswd\fR(5), \fBSamba\fR(7).
|
||||
\fBsmbpasswd\fR(5), \fBSamba\fR(7)\&.
|
||||
|
||||
.SH "AUTHOR"
|
||||
|
||||
.PP
|
||||
The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.
|
||||
The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
|
||||
|
||||
.PP
|
||||
The original Samba man pages were written by Karl Auer.
|
||||
The man page sources were converted to YODL format (another
|
||||
excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2
|
||||
for Samba 3.0 was done by Alexander Bokovoy.
|
||||
The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
|
||||
|
||||
|
||||
@ -1,180 +1,141 @@
|
||||
.\" This manpage has been automatically generated by docbook2man
|
||||
.\" from a DocBook document. This tool can be found at:
|
||||
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
||||
.\" Please send any bug reports, improvements, comments, patches,
|
||||
.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
||||
.TH "SMBSH" "1" "19 april 2003" "" ""
|
||||
|
||||
.\"Generated by db2man.xsl. Don't modify this, modify the source.
|
||||
.de Sh \" Subsection
|
||||
.br
|
||||
.if t .Sp
|
||||
.ne 5
|
||||
.PP
|
||||
\fB\\$1\fR
|
||||
.PP
|
||||
..
|
||||
.de Sp \" Vertical space (when we can't use .PP)
|
||||
.if t .sp .5v
|
||||
.if n .sp
|
||||
..
|
||||
.de Ip \" List item
|
||||
.br
|
||||
.ie \\n(.$>=3 .ne \\$3
|
||||
.el .ne 3
|
||||
.IP "\\$1" \\$2
|
||||
..
|
||||
.TH "SMBSH" 1 "" "" ""
|
||||
.SH NAME
|
||||
smbsh \- Allows access to Windows NT filesystem using UNIX commands
|
||||
.SH SYNOPSIS
|
||||
|
||||
\fBsmbsh\fR [ \fB-W workgroup\fR ] [ \fB-U username\fR ] [ \fB-P prefix\fR ] [ \fB-R <name resolve order>\fR ] [ \fB-d <debug level>\fR ] [ \fB-l logfile\fR ] [ \fB-L libdir\fR ]
|
||||
|
||||
.SH "DESCRIPTION"
|
||||
.PP
|
||||
This tool is part of the \fBSamba\fR(7) suite.
|
||||
.PP
|
||||
\fBsmbsh\fR allows you to access an NT filesystem
|
||||
using UNIX commands such as \fBls\fR, \fB egrep\fR, and \fBrcp\fR. You must use a
|
||||
shell that is dynamically linked in order for \fBsmbsh\fR
|
||||
to work correctly.
|
||||
.SH "OPTIONS"
|
||||
.TP
|
||||
\fB-W WORKGROUP\fR
|
||||
Override the default workgroup specified in the
|
||||
workgroup parameter of the \fBsmb.conf\fR(5) file
|
||||
for this session. This may be needed to connect to some
|
||||
servers.
|
||||
.TP
|
||||
\fB-U username[%pass]\fR
|
||||
Sets the SMB username or username and password.
|
||||
If this option is not specified, the user will be prompted for
|
||||
both the username and the password. If %pass is not specified,
|
||||
the user will be prompted for the password.
|
||||
.TP
|
||||
\fB-P prefix\fR
|
||||
This option allows
|
||||
the user to set the directory prefix for SMB access. The
|
||||
default value if this option is not specified is
|
||||
\fBsmb\fR.
|
||||
.TP
|
||||
\fB-s <configuration file>\fR
|
||||
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 \fIsmb.conf(5)\fR for more information.
|
||||
The default configuration file name is determined at
|
||||
compile time.
|
||||
.TP
|
||||
\fB-d|--debug=debuglevel\fR
|
||||
\fIdebuglevel\fR is an integer
|
||||
from 0 to 10. The default value if this parameter is
|
||||
not specified is zero.
|
||||
|
||||
The higher this value, the more detail will be
|
||||
logged to the log files about the activities of the
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
Note that specifying this parameter here will
|
||||
override the log
|
||||
level file.
|
||||
.TP
|
||||
\fB-R <name resolve order>\fR
|
||||
This option is used to determine what naming
|
||||
services and in what order to resolve
|
||||
host names to IP addresses. The option takes a space-separated
|
||||
string of different name resolution options.
|
||||
|
||||
The options are: "lmhosts", "host", "wins" and "bcast".
|
||||
They cause names to be resolved as follows :
|
||||
.RS
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
lmhosts:
|
||||
Lookup an IP address in the Samba lmhosts file. If the
|
||||
line in lmhosts has no name type attached to the
|
||||
NetBIOS name
|
||||
(see the \fBlmhosts\fR(5) for details)
|
||||
then any name type matches for lookup.
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
host:
|
||||
Do a standard host name to IP address resolution, using
|
||||
the system \fI/etc/hosts\fR, NIS, or DNS
|
||||
lookups. This method of name resolution is operating
|
||||
system dependent, for instance on IRIX or Solaris this
|
||||
may be controlled by the \fI/etc/nsswitch.conf\fR file). Note that this method is only used
|
||||
if the NetBIOS name type being queried is the 0x20
|
||||
(server) name type, otherwise it is ignored.
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
wins:
|
||||
Query a name with the IP address listed in the
|
||||
\fIwins server\fR parameter. If no
|
||||
WINS server has been specified this method will be
|
||||
ignored.
|
||||
.TP 0.2i
|
||||
\(bu
|
||||
bcast:
|
||||
Do a broadcast on each of the known local interfaces
|
||||
listed in the \fIinterfaces\fR
|
||||
parameter. This is the least reliable of the name
|
||||
resolution methods as it depends on the target host
|
||||
being on a locally connected subnet.
|
||||
.RE
|
||||
|
||||
If this parameter is not set then the name resolve order
|
||||
defined in the \fBsmb.conf\fR(5) file parameter
|
||||
(\fIname resolve order\fR) will be used.
|
||||
|
||||
The default order is lmhosts, host, wins, bcast. Without
|
||||
this parameter or any entry in the \fIname resolve order\fR parameter of the \fBsmb.conf\fR(5) file, the name resolution methods
|
||||
will be attempted in this order.
|
||||
.TP
|
||||
\fB-L libdir\fR
|
||||
This parameter specifies the location of the
|
||||
shared libraries used by \fBsmbsh\fR. The default
|
||||
value is specified at compile time.
|
||||
.SH "EXAMPLES"
|
||||
.PP
|
||||
To use the \fBsmbsh\fR command, execute \fB smbsh\fR from the prompt and enter the username and password
|
||||
that authenticates you to the machine running the Windows NT
|
||||
operating system.
|
||||
smbsh \- Allows access to Windows NT filesystem using UNIX commands
|
||||
.SH "SYNOPSIS"
|
||||
|
||||
.nf
|
||||
\fBsmbsh\fR [-W workgroup] [-U username] [-P prefix] [-R <name resolve order>] [-d <debug level>] [-l logfile] [-L libdir]
|
||||
|
||||
.fi
|
||||
|
||||
.SH "DESCRIPTION"
|
||||
|
||||
.PP
|
||||
This tool is part of the \fBSamba\fR(7) suite\&.
|
||||
|
||||
.PP
|
||||
\fBsmbsh\fR allows you to access an NT filesystem using UNIX commands such as \fBls\fR, \fB egrep\fR, and \fBrcp\fR\&. You must use a shell that is dynamically linked in order for \fBsmbsh\fR to work correctly\&.
|
||||
|
||||
.SH "OPTIONS"
|
||||
|
||||
.TP
|
||||
-W WORKGROUP
|
||||
Override the default workgroup specified in the workgroup parameter of the \fBsmb.conf\fR(5) file for this session\&. This may be needed to connect to some servers\&.
|
||||
|
||||
|
||||
.TP
|
||||
-U username[%pass]
|
||||
Sets the SMB username or username and password\&. If this option is not specified, the user will be prompted for both the username and the password\&. If %pass is not specified, the user will be prompted for the password\&.
|
||||
|
||||
|
||||
.TP
|
||||
-P prefix
|
||||
This option allows the user to set the directory prefix for SMB access\&. The default value if this option is not specified is \fBsmb\fR\&.
|
||||
|
||||
|
||||
.TP
|
||||
-s <configuration file>
|
||||
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 \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
|
||||
|
||||
|
||||
.TP
|
||||
-d|--debug=debuglevel
|
||||
\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
|
||||
|
||||
|
||||
The higher this value, the more detail will be logged to the log files about the activities of the 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\&.
|
||||
|
||||
|
||||
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\&.
|
||||
|
||||
|
||||
Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&.
|
||||
|
||||
|
||||
.TP
|
||||
-R <name resolve order>
|
||||
This option is used to determine what naming services and in what order to resolve host names to IP addresses\&. The option takes a space-separated string of different name resolution options\&.
|
||||
|
||||
|
||||
The options are: "lmhosts", "host", "wins" and "bcast"\&. They cause names to be resolved as follows :
|
||||
|
||||
|
||||
\fBlmhosts\fR: Lookup an IP address in the Samba lmhosts file\&. If the line in lmhosts has no name type attached to the NetBIOS name (see the \fBlmhosts\fR(5) for details) then any name type matches for lookup\&.
|
||||
|
||||
\fBhost\fR: Do a standard host name to IP address resolution, using the system \fI/etc/hosts\fR, NIS, or DNS lookups\&. This method of name resolution is operating system dependent, for instance on IRIX or Solaris this may be controlled by the \fI/etc/nsswitch\&.conf \fR file)\&. Note that this method is only used if the NetBIOS name type being queried is the 0x20 (server) name type, otherwise it is ignored\&.
|
||||
|
||||
\fBwins\fR: Query a name with the IP address listed in the \fIwins server\fR parameter\&. If no WINS server has been specified this method will be ignored\&.
|
||||
|
||||
\fBbcast\fR: Do a broadcast on each of the known local interfaces listed in the \fIinterfaces\fR parameter\&. This is the least reliable of the name resolution methods as it depends on the target host being on a locally connected subnet\&.
|
||||
|
||||
If this parameter is not set then the name resolve order defined in the \fBsmb.conf\fR(5) file parameter (\fIname resolve order\fR) will be used\&.
|
||||
|
||||
|
||||
The default order is lmhosts, host, wins, bcast\&. Without this parameter or any entry in the \fIname resolve order \fR parameter of the \fBsmb.conf\fR(5) file, the name resolution methods will be attempted in this order\&.
|
||||
|
||||
|
||||
.TP
|
||||
-L libdir
|
||||
This parameter specifies the location of the shared libraries used by \fBsmbsh\fR\&. The default value is specified at compile time\&.
|
||||
|
||||
|
||||
.SH "EXAMPLES"
|
||||
|
||||
.PP
|
||||
To use the \fBsmbsh\fR command, execute \fB smbsh\fR from the prompt and enter the username and password that authenticates you to the machine running the Windows NT operating system\&.
|
||||
.nf
|
||||
|
||||
system% \fBsmbsh\fR
|
||||
Username: \fBuser\fR
|
||||
Password: \fBXXXXXXX\fR
|
||||
.fi
|
||||
|
||||
|
||||
.PP
|
||||
Any dynamically linked command you execute from
|
||||
this shell will access the \fI/smb\fR directory
|
||||
using the smb protocol. For example, the command \fBls /smb
|
||||
\fR will show a list of workgroups. The command
|
||||
\fBls /smb/MYGROUP \fR will show all the machines in
|
||||
the workgroup MYGROUP. The command
|
||||
\fBls /smb/MYGROUP/<machine-name>\fR will show the share
|
||||
names for that machine. You could then, for example, use the \fB cd\fR command to change directories, \fBvi\fR to
|
||||
edit files, and \fBrcp\fR to copy files.
|
||||
Any dynamically linked command you execute from this shell will access the \fI/smb\fR directory using the smb protocol\&. For example, the command \fBls /smb \fR will show a list of workgroups\&. The command\fBls /smb/MYGROUP \fR will show all the machines in the workgroup MYGROUP\&. The command\fBls /smb/MYGROUP/<machine-name>\fR will show the share names for that machine\&. You could then, for example, use the \fB cd\fR command to change directories, \fBvi\fR to edit files, and \fBrcp\fR to copy files\&.
|
||||
|
||||
.SH "VERSION"
|
||||
|
||||
.PP
|
||||
This man page is correct for version 3.0 of the Samba suite.
|
||||
This man page is correct for version 3\&.0 of the Samba suite\&.
|
||||
|
||||
.SH "BUGS"
|
||||
|
||||
.PP
|
||||
\fBsmbsh\fR works by intercepting the standard
|
||||
libc calls with the dynamically loaded versions in \fI smbwrapper.o\fR. Not all calls have been "wrapped", so
|
||||
some programs may not function correctly under \fBsmbsh
|
||||
\fR.
|
||||
\fBsmbsh\fR works by intercepting the standard libc calls with the dynamically loaded versions in \fI smbwrapper\&.o\fR\&. Not all calls have been "wrapped", so some programs may not function correctly under \fBsmbsh \fR\&.
|
||||
|
||||
.PP
|
||||
Programs which are not dynamically linked cannot make
|
||||
use of \fBsmbsh\fR's functionality. Most versions
|
||||
of UNIX have a \fBfile\fR command that will
|
||||
describe how a program was linked.
|
||||
Programs which are not dynamically linked cannot make use of \fBsmbsh\fR's functionality\&. Most versions of UNIX have a \fBfile\fR command that will describe how a program was linked\&.
|
||||
|
||||
.SH "SEE ALSO"
|
||||
|
||||
.PP
|
||||
\fBsmbd\fR(8), \fBsmb.conf\fR(5)
|
||||
|
||||
.SH "AUTHOR"
|
||||
|
||||
.PP
|
||||
The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.
|
||||
The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
|
||||
|
||||
.PP
|
||||
The original Samba man pages were written by Karl Auer.
|
||||
The man page sources were converted to YODL format (another
|
||||
excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2
|
||||
for Samba 3.0 was done by Alexander Bokovoy.
|
||||
The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
|
||||
|
||||
|
||||
@ -1,100 +1,115 @@
|
||||
.\" This manpage has been automatically generated by docbook2man
|
||||
.\" from a DocBook document. This tool can be found at:
|
||||
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
||||
.\" Please send any bug reports, improvements, comments, patches,
|
||||
.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
||||
.TH "SMBSPOOL" "8" "19 april 2003" "" ""
|
||||
|
||||
.\"Generated by db2man.xsl. Don't modify this, modify the source.
|
||||
.de Sh \" Subsection
|
||||
.br
|
||||
.if t .Sp
|
||||
.ne 5
|
||||
.PP
|
||||
\fB\\$1\fR
|
||||
.PP
|
||||
..
|
||||
.de Sp \" Vertical space (when we can't use .PP)
|
||||
.if t .sp .5v
|
||||
.if n .sp
|
||||
..
|
||||
.de Ip \" List item
|
||||
.br
|
||||
.ie \\n(.$>=3 .ne \\$3
|
||||
.el .ne 3
|
||||
.IP "\\$1" \\$2
|
||||
..
|
||||
.TH "SMBSPOOL" 8 "" "" ""
|
||||
.SH NAME
|
||||
smbspool \- send a print file to an SMB printer
|
||||
.SH SYNOPSIS
|
||||
.SH "SYNOPSIS"
|
||||
|
||||
\fBsmbspool\fR \fBjob\fR \fBuser\fR \fBtitle\fR \fBcopies\fR \fBoptions\fR [ \fBfilename\fR ]
|
||||
.nf
|
||||
\fBsmbspool\fR {job} {user} {title} {copies} {options} [filename]
|
||||
.fi
|
||||
|
||||
.SH "DESCRIPTION"
|
||||
|
||||
.PP
|
||||
This tool is part of the \fBSamba\fR(7) suite.
|
||||
This tool is part of the \fBSamba\fR(7) suite\&.
|
||||
|
||||
.PP
|
||||
smbspool is a very small print spooling program that
|
||||
sends a print file to an SMB printer. The command-line arguments
|
||||
are position-dependent for compatibility with the Common UNIX
|
||||
Printing System, but you can use smbspool with any printing system
|
||||
or from a program or script.
|
||||
smbspool is a very small print spooling program that sends a print file to an SMB printer\&. The command-line arguments are position-dependent for compatibility with the Common UNIX Printing System, but you can use smbspool with any printing system or from a program or script\&.
|
||||
|
||||
.PP
|
||||
\fBDEVICE URI\fR
|
||||
|
||||
.PP
|
||||
smbspool specifies the destination using a Uniform Resource
|
||||
Identifier ("URI") with a method of "smb". This string can take
|
||||
a number of forms:
|
||||
.TP 0.2i
|
||||
smbspool specifies the destination using a Uniform Resource Identifier ("URI") with a method of "smb"\&. This string can take a number of forms:
|
||||
|
||||
.TP 3
|
||||
\(bu
|
||||
smb://server/printer
|
||||
.TP 0.2i
|
||||
|
||||
.TP
|
||||
\(bu
|
||||
smb://workgroup/server/printer
|
||||
.TP 0.2i
|
||||
|
||||
.TP
|
||||
\(bu
|
||||
smb://username:password@server/printer
|
||||
.TP 0.2i
|
||||
|
||||
.TP
|
||||
\(bu
|
||||
smb://username:password@workgroup/server/printer
|
||||
|
||||
.LP
|
||||
|
||||
.PP
|
||||
smbspool tries to get the URI from argv[0]. If argv[0]
|
||||
contains the name of the program then it looks in the \fB DEVICE_URI\fR environment variable.
|
||||
smbspool tries to get the URI from argv[0]\&. If argv[0] contains the name of the program then it looks in the \fB DEVICE_URI\fR environment variable\&.
|
||||
|
||||
.PP
|
||||
Programs using the \fBexec(2)\fR functions can
|
||||
pass the URI in argv[0], while shell scripts must set the
|
||||
\fBDEVICE_URI\fR environment variable prior to
|
||||
running smbspool.
|
||||
Programs using the \fBexec(2)\fR functions can pass the URI in argv[0], while shell scripts must set the\fBDEVICE_URI\fR environment variable prior to running smbspool\&.
|
||||
|
||||
.SH "OPTIONS"
|
||||
.TP 0.2i
|
||||
|
||||
.TP 3
|
||||
\(bu
|
||||
The job argument (argv[1]) contains the
|
||||
job ID number and is presently not used by smbspool.
|
||||
.TP 0.2i
|
||||
The job argument (argv[1]) contains the job ID number and is presently not used by smbspool\&.
|
||||
|
||||
.TP
|
||||
\(bu
|
||||
The user argument (argv[2]) contains the
|
||||
print user's name and is presently not used by smbspool.
|
||||
.TP 0.2i
|
||||
The user argument (argv[2]) contains the print user's name and is presently not used by smbspool\&.
|
||||
|
||||
.TP
|
||||
\(bu
|
||||
The title argument (argv[3]) contains the
|
||||
job title string and is passed as the remote file name
|
||||
when sending the print job.
|
||||
.TP 0.2i
|
||||
The title argument (argv[3]) contains the job title string and is passed as the remote file name when sending the print job\&.
|
||||
|
||||
.TP
|
||||
\(bu
|
||||
The copies argument (argv[4]) contains
|
||||
the number of copies to be printed of the named file. If
|
||||
no filename is provided then this argument is not used by
|
||||
smbspool.
|
||||
.TP 0.2i
|
||||
The copies argument (argv[4]) contains the number of copies to be printed of the named file\&. If no filename is provided then this argument is not used by smbspool\&.
|
||||
|
||||
.TP
|
||||
\(bu
|
||||
The options argument (argv[5]) contains
|
||||
the print options in a single string and is currently
|
||||
not used by smbspool.
|
||||
.TP 0.2i
|
||||
The options argument (argv[5]) contains the print options in a single string and is currently not used by smbspool\&.
|
||||
|
||||
.TP
|
||||
\(bu
|
||||
The filename argument (argv[6]) contains the
|
||||
name of the file to print. If this argument is not specified
|
||||
then the print file is read from the standard input.
|
||||
The filename argument (argv[6]) contains the name of the file to print\&. If this argument is not specified then the print file is read from the standard input\&.
|
||||
|
||||
.LP
|
||||
|
||||
.SH "VERSION"
|
||||
|
||||
.PP
|
||||
This man page is correct for version 3.0 of the Samba suite.
|
||||
This man page is correct for version 3\&.0 of the Samba suite\&.
|
||||
|
||||
.SH "SEE ALSO"
|
||||
|
||||
.PP
|
||||
\fBsmbd\fR(8) and \fBSamba\fR(7).
|
||||
\fBsmbd\fR(8) and \fBSamba\fR(7)\&.
|
||||
|
||||
.SH "AUTHOR"
|
||||
|
||||
.PP
|
||||
\fBsmbspool\fR was written by Michael Sweet
|
||||
at Easy Software Products.
|
||||
\fBsmbspool\fR was written by Michael Sweet at Easy Software Products\&.
|
||||
|
||||
.PP
|
||||
The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.
|
||||
The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
|
||||
|
||||
.PP
|
||||
The original Samba man pages were written by Karl Auer.
|
||||
The man page sources were converted to YODL format (another
|
||||
excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2
|
||||
for Samba 3.0 was done by Alexander Bokovoy.
|
||||
The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
|
||||
|
||||
|
||||
@ -1,112 +1,131 @@
|
||||
.\" This manpage has been automatically generated by docbook2man
|
||||
.\" from a DocBook document. This tool can be found at:
|
||||
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
||||
.\" Please send any bug reports, improvements, comments, patches,
|
||||
.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
||||
.TH "SMBSTATUS" "1" "19 april 2003" "" ""
|
||||
|
||||
.\"Generated by db2man.xsl. Don't modify this, modify the source.
|
||||
.de Sh \" Subsection
|
||||
.br
|
||||
.if t .Sp
|
||||
.ne 5
|
||||
.PP
|
||||
\fB\\$1\fR
|
||||
.PP
|
||||
..
|
||||
.de Sp \" Vertical space (when we can't use .PP)
|
||||
.if t .sp .5v
|
||||
.if n .sp
|
||||
..
|
||||
.de Ip \" List item
|
||||
.br
|
||||
.ie \\n(.$>=3 .ne \\$3
|
||||
.el .ne 3
|
||||
.IP "\\$1" \\$2
|
||||
..
|
||||
.TH "SMBSTATUS" 1 "" "" ""
|
||||
.SH NAME
|
||||
smbstatus \- report on current Samba connections
|
||||
.SH SYNOPSIS
|
||||
.SH "SYNOPSIS"
|
||||
|
||||
\fBsmbstatus\fR [ \fB-P\fR ] [ \fB-b\fR ] [ \fB-d <debug level>\fR ] [ \fB-v\fR ] [ \fB-L\fR ] [ \fB-B\fR ] [ \fB-p\fR ] [ \fB-S\fR ] [ \fB-s <configuration file>\fR ] [ \fB-u <username>\fR ]
|
||||
.nf
|
||||
\fBsmbstatus\fR [-P] [-b] [-d <debug level>] [-v] [-L] [-B] [-p] [-S] [-s <configuration
|
||||
file>] [-u <username>]
|
||||
.fi
|
||||
|
||||
.SH "DESCRIPTION"
|
||||
|
||||
.PP
|
||||
This tool is part of the \fBSamba\fR(7) suite.
|
||||
This tool is part of the \fBSamba\fR(7) suite\&.
|
||||
|
||||
.PP
|
||||
\fBsmbstatus\fR is a very simple program to
|
||||
list the current Samba connections.
|
||||
\fBsmbstatus\fR is a very simple program to list the current Samba connections\&.
|
||||
|
||||
.SH "OPTIONS"
|
||||
.TP
|
||||
\fB-P|--profile\fR
|
||||
If samba has been compiled with the
|
||||
profiling option, print only the contents of the profiling
|
||||
shared memory area.
|
||||
.TP
|
||||
\fB-b|--brief\fR
|
||||
gives brief output.
|
||||
.TP
|
||||
\fB-V\fR
|
||||
Prints the version number for
|
||||
\fBsmbd\fR.
|
||||
.TP
|
||||
\fB-s <configuration file>\fR
|
||||
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 \fIsmb.conf(5)\fR for more information.
|
||||
The default configuration file name is determined at
|
||||
compile time.
|
||||
.TP
|
||||
\fB-d|--debug=debuglevel\fR
|
||||
\fIdebuglevel\fR is an integer
|
||||
from 0 to 10. The default value if this parameter is
|
||||
not specified is zero.
|
||||
|
||||
The higher this value, the more detail will be
|
||||
logged to the log files about the activities of the
|
||||
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.
|
||||
.TP
|
||||
-P|--profile
|
||||
If samba has been compiled with the profiling option, print only the contents of the profiling shared memory area\&.
|
||||
|
||||
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.
|
||||
|
||||
Note that specifying this parameter here will
|
||||
override the log
|
||||
level file.
|
||||
.TP
|
||||
\fB-l|--logfile=logbasename\fR
|
||||
File name for log/debug files. The extension
|
||||
".client" will be appended. The log file is
|
||||
never removed by the client.
|
||||
-b|--brief
|
||||
gives brief output\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-v|--verbose\fR
|
||||
gives verbose output.
|
||||
-V
|
||||
Prints the version number for \fBsmbd\fR\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-L|--locks\fR
|
||||
causes smbstatus to only list locks.
|
||||
-s <configuration file>
|
||||
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 \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-B|--byterange\fR
|
||||
causes smbstatus to include byte range locks.
|
||||
-d|--debug=debuglevel
|
||||
\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
|
||||
|
||||
|
||||
The higher this value, the more detail will be logged to the log files about the activities of the 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\&.
|
||||
|
||||
|
||||
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\&.
|
||||
|
||||
|
||||
Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-p|--processes\fR
|
||||
print a list of \fBsmbd\fR(8) processes and exit.
|
||||
Useful for scripting.
|
||||
-l|--logfile=logbasename
|
||||
File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-S|--shares\fR
|
||||
causes smbstatus to only list shares.
|
||||
-v|--verbose
|
||||
gives verbose output\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-h|--help\fR
|
||||
Print a summary of command line options.
|
||||
-L|--locks
|
||||
causes smbstatus to only list locks\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-u|--user=<username>\fR
|
||||
selects information relevant to
|
||||
\fIusername\fR only.
|
||||
-B|--byterange
|
||||
causes smbstatus to include byte range locks\&.
|
||||
|
||||
|
||||
.TP
|
||||
-p|--processes
|
||||
print a list of \fBsmbd\fR(8) processes and exit\&. Useful for scripting\&.
|
||||
|
||||
|
||||
.TP
|
||||
-S|--shares
|
||||
causes smbstatus to only list shares\&.
|
||||
|
||||
|
||||
.TP
|
||||
-h|--help
|
||||
Print a summary of command line options\&.
|
||||
|
||||
|
||||
.TP
|
||||
-u|--user=<username>
|
||||
selects information relevant to \fIusername\fR only\&.
|
||||
|
||||
|
||||
.SH "VERSION"
|
||||
|
||||
.PP
|
||||
This man page is correct for version 3.0 of
|
||||
the Samba suite.
|
||||
This man page is correct for version 3\&.0 of the Samba suite\&.
|
||||
|
||||
.SH "SEE ALSO"
|
||||
|
||||
.PP
|
||||
\fBsmbd\fR(8) and \fBsmb.conf\fR(5).
|
||||
\fBsmbd\fR(8) and \fBsmb.conf\fR(5)\&.
|
||||
|
||||
.SH "AUTHOR"
|
||||
|
||||
.PP
|
||||
The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.
|
||||
The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
|
||||
|
||||
.PP
|
||||
The original Samba man pages were written by Karl Auer.
|
||||
The man page sources were converted to YODL format (another
|
||||
excellent piece of Open Source software, available at ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2
|
||||
for Samba 3.0 was done by Alexander Bokovoy.
|
||||
The original Samba man pages were written by Karl Auer\&. The man page sources were converted to YODL format (another excellent piece of Open Source software, available at ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
|
||||
|
||||
|
||||
@ -1,120 +1,148 @@
|
||||
.\" This manpage has been automatically generated by docbook2man
|
||||
.\" from a DocBook document. This tool can be found at:
|
||||
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
||||
.\" Please send any bug reports, improvements, comments, patches,
|
||||
.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
||||
.TH "SMBTAR" "1" "19 april 2003" "" ""
|
||||
|
||||
.\"Generated by db2man.xsl. Don't modify this, modify the source.
|
||||
.de Sh \" Subsection
|
||||
.br
|
||||
.if t .Sp
|
||||
.ne 5
|
||||
.PP
|
||||
\fB\\$1\fR
|
||||
.PP
|
||||
..
|
||||
.de Sp \" Vertical space (when we can't use .PP)
|
||||
.if t .sp .5v
|
||||
.if n .sp
|
||||
..
|
||||
.de Ip \" List item
|
||||
.br
|
||||
.ie \\n(.$>=3 .ne \\$3
|
||||
.el .ne 3
|
||||
.IP "\\$1" \\$2
|
||||
..
|
||||
.TH "SMBTAR" 1 "" "" ""
|
||||
.SH NAME
|
||||
smbtar \- shell script for backing up SMB/CIFS shares directly to UNIX tape drives
|
||||
.SH SYNOPSIS
|
||||
smbtar \- shell script for backing up SMB/CIFS shares directly to UNIX tape drives
|
||||
.SH "SYNOPSIS"
|
||||
|
||||
\fBsmbtar\fR [ \fB-r\fR ] [ \fB-i\fR ] [ \fB-a\fR ] [ \fB-v\fR ] \fB-s server\fR [ \fB-p password\fR ] [ \fB-x services\fR ] [ \fB-X\fR ] [ \fB-N filename\fR ] [ \fB-b blocksize\fR ] [ \fB-d directory\fR ] [ \fB-l loglevel\fR ] [ \fB-u user\fR ] [ \fB-t tape\fR ] \fBfilenames\fR
|
||||
.nf
|
||||
\fBsmbtar\fR [-r] [-i] [-a] [-v] {-s server} [-p password] [-x services] [-X] [-N filename]
|
||||
[-b blocksize] [-d directory] [-l loglevel] [-u user] [-t tape] {filenames}
|
||||
|
||||
.fi
|
||||
|
||||
.SH "DESCRIPTION"
|
||||
|
||||
.PP
|
||||
This tool is part of the \fBSamba\fR(7) suite.
|
||||
This tool is part of the \fBSamba\fR(7) suite\&.
|
||||
|
||||
.PP
|
||||
\fBsmbtar\fR is a very small shell script on top
|
||||
of \fBsmbclient\fR(1) which dumps SMB shares directly to tape.
|
||||
\fBsmbtar\fR is a very small shell script on top of \fBsmbclient\fR(1) which dumps SMB shares directly to tape\&.
|
||||
|
||||
.SH "OPTIONS"
|
||||
|
||||
.TP
|
||||
\fB-s server\fR
|
||||
The SMB/CIFS server that the share resides
|
||||
upon.
|
||||
-s server
|
||||
The SMB/CIFS server that the share resides upon\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-x service\fR
|
||||
The share name on the server to connect to.
|
||||
The default is "backup".
|
||||
-x service
|
||||
The share name on the server to connect to\&. The default is "backup"\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-X\fR
|
||||
Exclude mode. Exclude filenames... from tar
|
||||
create or restore.
|
||||
-X
|
||||
Exclude mode\&. Exclude filenames\&.\&.\&. from tar create or restore\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-d directory\fR
|
||||
Change to initial \fIdirectory
|
||||
\fR before restoring / backing up files.
|
||||
-d directory
|
||||
Change to initial \fIdirectory \fR before restoring / backing up files\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-v\fR
|
||||
Verbose mode.
|
||||
-v
|
||||
Verbose mode\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-p password\fR
|
||||
The password to use to access a share.
|
||||
Default: none
|
||||
-p password
|
||||
The password to use to access a share\&. Default: none
|
||||
|
||||
|
||||
.TP
|
||||
\fB-u user\fR
|
||||
The user id to connect as. Default:
|
||||
UNIX login name.
|
||||
-u user
|
||||
The user id to connect as\&. Default: UNIX login name\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-a\fR
|
||||
Reset DOS archive bit mode to
|
||||
indicate file has been archived.
|
||||
-a
|
||||
Reset DOS archive bit mode to indicate file has been archived\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-t tape\fR
|
||||
Tape device. May be regular file or tape
|
||||
device. Default: \fI$TAPE\fR environmental
|
||||
variable; if not set, a file called \fItar.out
|
||||
\fR.
|
||||
-t tape
|
||||
Tape device\&. May be regular file or tape device\&. Default: \fI$TAPE\fR environmental variable; if not set, a file called \fItar\&.out \fR\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-b blocksize\fR
|
||||
Blocking factor. Defaults to 20. See
|
||||
\fBtar(1)\fR for a fuller explanation.
|
||||
-b blocksize
|
||||
Blocking factor\&. Defaults to 20\&. See \fBtar(1)\fR for a fuller explanation\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-N filename\fR
|
||||
Backup only files newer than filename. Could
|
||||
be used (for example) on a log file to implement incremental
|
||||
backups.
|
||||
-N filename
|
||||
Backup only files newer than filename\&. Could be used (for example) on a log file to implement incremental backups\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-i\fR
|
||||
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.
|
||||
-i
|
||||
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\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-r\fR
|
||||
Restore. Files are restored to the share
|
||||
from the tar file.
|
||||
-r
|
||||
Restore\&. Files are restored to the share from the tar file\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-l log level\fR
|
||||
Log (debug) level. Corresponds to the
|
||||
\fI-d\fR flag of \fBsmbclient\fR(1).
|
||||
-l log level
|
||||
Log (debug) level\&. Corresponds to the \fI-d\fR flag of \fBsmbclient\fR(1)\&.
|
||||
|
||||
|
||||
.SH "ENVIRONMENT VARIABLES"
|
||||
|
||||
.PP
|
||||
The \fI$TAPE\fR variable specifies the
|
||||
default tape device to write to. May be overridden
|
||||
with the -t option.
|
||||
The \fI$TAPE\fR variable specifies the default tape device to write to\&. May be overridden with the -t option\&.
|
||||
|
||||
.SH "BUGS"
|
||||
|
||||
.PP
|
||||
The \fBsmbtar\fR script has different
|
||||
options from ordinary tar and from smbclient's tar command.
|
||||
The \fBsmbtar\fR script has different options from ordinary tar and from smbclient's tar command\&.
|
||||
|
||||
.SH "CAVEATS"
|
||||
|
||||
.PP
|
||||
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. smbtar works best
|
||||
with GNU tar and may not work well with other versions.
|
||||
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\&. smbtar works best with GNU tar and may not work well with other versions\&.
|
||||
|
||||
.SH "DIAGNOSTICS"
|
||||
|
||||
.PP
|
||||
See the \fBDIAGNOSTICS\fR section for the \fBsmbclient\fR(1) command.
|
||||
See the \fBDIAGNOSTICS\fR section for the \fBsmbclient\fR(1) command\&.
|
||||
|
||||
.SH "VERSION"
|
||||
|
||||
.PP
|
||||
This man page is correct for version 3.0 of
|
||||
the Samba suite.
|
||||
This man page is correct for version 3\&.0 of the Samba suite\&.
|
||||
|
||||
.SH "SEE ALSO"
|
||||
|
||||
.PP
|
||||
\fBsmbd\fR(8), \fBsmbclient\fR(1), \fBsmb.conf\fR(5).
|
||||
\fBsmbd\fR(8), \fBsmbclient\fR(1), \fBsmb.conf\fR(5)\&.
|
||||
|
||||
.SH "AUTHOR"
|
||||
|
||||
.PP
|
||||
The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.
|
||||
The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
|
||||
|
||||
.PP
|
||||
Ricky Poulten <URL:mailto:poultenr@logica.co.uk>
|
||||
wrote the tar extension and this man page. The \fBsmbtar\fR
|
||||
script was heavily rewritten and improved by Martin Kraemer <URL:mailto: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 ftp://ftp.icce.rug.nl/pub/unix/ <URL:ftp://ftp.icce.rug.nl/pub/unix/>) and updated for the Samba 2.0
|
||||
release by Jeremy Allison. The conversion to DocBook for
|
||||
Samba 2.2 was done by Gerald Carter. The conversion to DocBook XML 4.2 for
|
||||
Samba 3.0 was done by Alexander Bokovoy.
|
||||
Ricky Poulten wrote the tar extension and this man page\&. The \fBsmbtar\fR script was heavily rewritten and improved by Martin Kraemer\&. 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 ftp://ftp\&.icce\&.rug\&.nl/pub/unix/) and updated for the Samba 2\&.0 release by Jeremy Allison\&. The conversion to DocBook for Samba 2\&.2 was done by Gerald Carter\&. The conversion to DocBook XML 4\&.2 for Samba 3\&.0 was done by Alexander Bokovoy\&.
|
||||
|
||||
|
||||
@ -1,144 +1,143 @@
|
||||
.\" This manpage has been automatically generated by docbook2man
|
||||
.\" from a DocBook document. This tool can be found at:
|
||||
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
|
||||
.\" Please send any bug reports, improvements, comments, patches,
|
||||
.\" etc. to Steve Cheng <steve@ggi-project.org>.
|
||||
.TH "SMBTREE" "1" "19 april 2003" "" ""
|
||||
|
||||
.\"Generated by db2man.xsl. Don't modify this, modify the source.
|
||||
.de Sh \" Subsection
|
||||
.br
|
||||
.if t .Sp
|
||||
.ne 5
|
||||
.PP
|
||||
\fB\\$1\fR
|
||||
.PP
|
||||
..
|
||||
.de Sp \" Vertical space (when we can't use .PP)
|
||||
.if t .sp .5v
|
||||
.if n .sp
|
||||
..
|
||||
.de Ip \" List item
|
||||
.br
|
||||
.ie \\n(.$>=3 .ne \\$3
|
||||
.el .ne 3
|
||||
.IP "\\$1" \\$2
|
||||
..
|
||||
.TH "SMBTREE" 1 "" "" ""
|
||||
.SH NAME
|
||||
smbtree \- A text based smb network browser
|
||||
.SH SYNOPSIS
|
||||
.SH "SYNOPSIS"
|
||||
|
||||
\fBsmbtree\fR [ \fB-b\fR ] [ \fB-D\fR ] [ \fB-S\fR ]
|
||||
.nf
|
||||
\fBsmbtree\fR [-b] [-D] [-S]
|
||||
.fi
|
||||
|
||||
.SH "DESCRIPTION"
|
||||
|
||||
.PP
|
||||
This tool is part of the \fBSamba\fR(7) suite.
|
||||
This tool is part of the \fBSamba\fR(7) suite\&.
|
||||
|
||||
.PP
|
||||
\fBsmbtree\fR is a smb browser program
|
||||
in text mode. It is similar to the "Network Neighborhood" found
|
||||
on Windows computers. It prints a tree with all
|
||||
the known domains, the servers in those domains and
|
||||
the shares on the servers.
|
||||
\fBsmbtree\fR is a smb browser program in text mode\&. It is similar to the "Network Neighborhood" found on Windows computers\&. It prints a tree with all the known domains, the servers in those domains and the shares on the servers\&.
|
||||
|
||||
.SH "OPTIONS"
|
||||
.TP
|
||||
\fB-b\fR
|
||||
Query network nodes by sending requests
|
||||
as broadcasts instead of querying the (domain) master browser.
|
||||
.TP
|
||||
\fB-D\fR
|
||||
Only print a list of all
|
||||
the domains known on broadcast or by the
|
||||
master browser
|
||||
.TP
|
||||
\fB-S\fR
|
||||
Only print a list of
|
||||
all the domains and servers responding on broadcast or
|
||||
known by the master browser.
|
||||
.TP
|
||||
\fB-V\fR
|
||||
Prints the version number for
|
||||
\fBsmbd\fR.
|
||||
.TP
|
||||
\fB-s <configuration file>\fR
|
||||
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 \fIsmb.conf(5)\fR for more information.
|
||||
The default configuration file name is determined at
|
||||
compile time.
|
||||
.TP
|
||||
\fB-d|--debug=debuglevel\fR
|
||||
\fIdebuglevel\fR is an integer
|
||||
from 0 to 10. The default value if this parameter is
|
||||
not specified is zero.
|
||||
|
||||
The higher this value, the more detail will be
|
||||
logged to the log files about the activities of the
|
||||
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.
|
||||
.TP
|
||||
-b
|
||||
Query network nodes by sending requests as broadcasts instead of querying the (domain) master browser\&.
|
||||
|
||||
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.
|
||||
|
||||
Note that specifying this parameter here will
|
||||
override the log
|
||||
level file.
|
||||
.TP
|
||||
\fB-l|--logfile=logbasename\fR
|
||||
File name for log/debug files. The extension
|
||||
".client" will be appended. The log file is
|
||||
never removed by the client.
|
||||
.TP
|
||||
\fB-N\fR
|
||||
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.
|
||||
-D
|
||||
Only print a list of all the domains known on broadcast or by the master browser
|
||||
|
||||
|
||||
Unless a password is specified on the command line or
|
||||
this parameter is specified, the client will request a
|
||||
password.
|
||||
.TP
|
||||
\fB-k\fR
|
||||
Try to authenticate with kerberos. Only useful in
|
||||
an Active Directory environment.
|
||||
-S
|
||||
Only print a list of all the domains and servers responding on broadcast or known by the master browser\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-A|--authfile=filename\fR
|
||||
This option allows
|
||||
you to specify a file from which to read the username and
|
||||
password used in the connection. The format of the file is
|
||||
-V
|
||||
Prints the version number for \fBsmbd\fR\&.
|
||||
|
||||
|
||||
.TP
|
||||
-s <configuration file>
|
||||
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 \fI smb\&.conf(5)\fR for more information\&. The default configuration file name is determined at compile time\&.
|
||||
|
||||
|
||||
.TP
|
||||
-d|--debug=debuglevel
|
||||
\fIdebuglevel\fR is an integer from 0 to 10\&. The default value if this parameter is not specified is zero\&.
|
||||
|
||||
|
||||
The higher this value, the more detail will be logged to the log files about the activities of the 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\&.
|
||||
|
||||
|
||||
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\&.
|
||||
|
||||
|
||||
Note that specifying this parameter here will override the log level parameter in the \fIsmb\&.conf(5)\fR file\&.
|
||||
|
||||
|
||||
.TP
|
||||
-l|--logfile=logbasename
|
||||
File name for log/debug files\&. The extension \fB"\&.client"\fR will be appended\&. The log file is never removed by the client\&.
|
||||
|
||||
|
||||
.TP
|
||||
-N
|
||||
If specified, this parameter suppresses the normal password prompt from the client to the user\&. This is useful when accessing a service that does not require a password\&.
|
||||
|
||||
|
||||
Unless a password is specified on the command line or this parameter is specified, the client will request a password\&.
|
||||
|
||||
|
||||
.TP
|
||||
-k
|
||||
Try to authenticate with kerberos\&. Only useful in an Active Directory environment\&.
|
||||
|
||||
|
||||
.TP
|
||||
-A|--authfile=filename
|
||||
This option allows you to specify a file from which to read the username and password used in the connection\&. The format of the file is
|
||||
|
||||
|
||||
.nf
|
||||
|
||||
username = <value>
|
||||
password = <value>
|
||||
domain = <value>
|
||||
.fi
|
||||
|
||||
Make certain that the permissions on the file restrict
|
||||
access from unwanted users.
|
||||
|
||||
Make certain that the permissions on the file restrict access from unwanted users\&.
|
||||
|
||||
|
||||
.TP
|
||||
\fB-U|--user=username[%password]\fR
|
||||
Sets the SMB username or username and password.
|
||||
-U|--user=username[%password]
|
||||
Sets the SMB username or username and password\&.
|
||||
|
||||
If %password is not specified, the user will be prompted. The
|
||||
client will first check the \fBUSER\fR environment variable, then the
|
||||
\fBLOGNAME\fR variable and if either exists, the
|
||||
string is uppercased. If these environmental variables are not
|
||||
found, the username GUEST is used.
|
||||
|
||||
A third option is to use a credentials file which
|
||||
contains the plaintext of the username and password. This
|
||||
option is mainly provided for scripts where the admin does not
|
||||
wish to pass the credentials on the command line or via environment
|
||||
variables. If this method is used, make certain that the permissions
|
||||
on the file restrict access from unwanted users. See the
|
||||
\fI-A\fR for more details.
|
||||
If %password is not specified, the user will be prompted\&. The client will first check the \fBUSER\fR environment variable, then the \fBLOGNAME\fR variable and if either exists, the string is uppercased\&. If these environmental variables are not found, the username \fBGUEST\fR is used\&.
|
||||
|
||||
|
||||
A third option is to use a credentials file which contains the plaintext of the username and password\&. This option is mainly provided for scripts where the admin does not wish to pass the credentials on the command line or via environment variables\&. If this method is used, make certain that the permissions on the file restrict access from unwanted users\&. See the \fI-A\fR for more details\&.
|
||||
|
||||
|
||||
Be cautious about including passwords in scripts\&. Also, on many systems the command line of a running process may be seen via the \fBps\fR command\&. To be safe always allow \fBrpcclient\fR to prompt for a password and type it in directly\&.
|
||||
|
||||
|
||||
Be cautious about including passwords in scripts. Also, on
|
||||
many systems the command line of a running process may be seen
|
||||
via the \fBps\fR command. To be safe always allow
|
||||
\fBrpcclient\fR to prompt for a password and type
|
||||
it in directly.
|
||||
.TP
|
||||
\fB-h|--help\fR
|
||||
Print a summary of command line options.
|
||||
-h|--help
|
||||
Print a summary of command line options\&.
|
||||
|
||||
|
||||
.SH "VERSION"
|
||||
|
||||
.PP
|
||||
This man page is correct for version 3.0 of the Samba
|
||||
suite.
|
||||
This man page is correct for version 3\&.0 of the Samba suite\&.
|
||||
|
||||
.SH "AUTHOR"
|
||||
|
||||
.PP
|
||||
The original Samba software and related utilities
|
||||
were created by Andrew Tridgell. Samba is now developed
|
||||
by the Samba Team as an Open Source project similar
|
||||
to the way the Linux kernel is developed.
|
||||
The original Samba software and related utilities were created by Andrew Tridgell\&. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed\&.
|
||||
|
||||
.PP
|
||||
The smbtree man page was written by Jelmer Vernooij.
|
||||
The smbtree man page was written by Jelmer Vernooij\&.
|
||||
|
||||
|
||||
Some files were not shown because too many files have changed in this diff Show More
Loading…
x
Reference in New Issue
Block a user