sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-01-12 09:18:10 +03:00
Code

syncing docs with HEAD

Browse Source
This commit is contained in:
Gerald Carter 0001-01-01 00:00:00 +00:00
parent d74382ccfe
commit d8fe70c3b4
76 changed files with 3600 additions and 22518 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
docs/Samba-Developers-Guide.pdf
View File

Binary file not shown.

BIN
docs/Samba-HOWTO-Collection.pdf
View File

Binary file not shown.

55
docs/docbook/global.ent
View File

@ -31,3 +31,58 @@
<!-- Misc -->
<!ENTITY samba.pub.cvshost 'pserver.samba.org'>
<!ENTITY stdarg.debuglevel '
<varlistentry>
<term>-d|--debug=debuglevel</term>
<listitem>
<para><replaceable>debuglevel</replaceable> is an integer
from 0 to 10. The default value if this parameter is
not specified is zero.</para>
<para>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.</para>
<para>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.</para>
<para>Note that specifying this parameter here will
override the <ulink url="smb.conf.5.html#loglevel">log
level</ulink> parameter in the <ulink url="smb.conf.5.html">
<filename>smb.conf(5)</filename></ulink> file.</para>
</listitem>
</varlistentry>'>
<!ENTITY stdarg.help '
<varlistentry>
<term>-h|--help</term>
<listitem><para>Print a summary of command line options.
</para></listitem>
</varlistentry>'>
<!ENTITY stdarg.configfile '
<varlistentry>
<term>-s &lt;configuration file&gt;</term>
<listitem><para>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 <ulink url="smb.conf.5.html"><filename>
smb.conf(5)</filename></ulink> for more information.
The default configuration file name is determined at
compile time.</para></listitem>
</varlistentry>'>
<!ENTITY stdarg.version '
<varlistentry>
<term>-v</term>
<listitem><para>Prints the version number for
<command>smbd</command>.</para></listitem>
</varlistentry>'>

19
docs/docbook/manpages/findsmb.1.sgml
View File

@ -39,6 +39,15 @@
<title>OPTIONS</title>
<variablelist>
<varlistentry>
<term>-r</term>
<listitem><para>Controls whether <command>findsmb</command> 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, <ulink url="nmblookup.1.html"><command>nmblookup</command></ulink>
will be called with <constant>-B<constant> option.</para></listitem>
</varlistentry>
<varlistentry>
<term>subnet broadcast address</term>
<listitem><para>Without this option, <command>findsmb
@ -66,15 +75,17 @@
not show any information about the operating system or server
version.</para>
<para>The command must be run on a system without <ulink
<para>The command with <constant>-r</constant> option
must be run on a system without <ulink
url="nmbd.8.html"><command>nmbd</command></ulink> running.
If <command>nmbd</command> 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. </para>
the command must be run as root and with <constant>-r</constant>
option on a machine without <command>nmbd</command> running.</para>
<para>For example, running <command>findsmb</command> on a machine
without <command>nmbd</command> running would yield output similar
<para>For example, running <command>findsmb</command> without
<constant>-r</constant> option set would yield output similar
to the following</para>
<screen><computeroutput>

2
docs/docbook/projdoc/Diagnosis.sgml
View File

@ -14,7 +14,7 @@
<address><email>jelmer@samba.org</email></address>
</affiliation>
</author>
<pubdate>$Id: Diagnosis.sgml,v 1.1.2.3 2002/11/22 00:32:23 tpot Exp $</pubdate>
<pubdate>Wed Jan 15</pubdate>
</chapterinfo>
<title>Diagnosing your samba server</title>

6
docs/docbook/projdoc/Samba-LDAP-HOWTO.sgml
View File

@ -2,12 +2,12 @@
<chapterinfo>
<author>
<firstname>Gerald (Jerry)></firstname><surname>Carter</surname>
<firstname>Gerald (Jerry)</firstname><surname>Carter</surname>
<affiliation>
<orgname>Samba Team</orgname>
<address><email>jerry@samba.org</email></address>
</affiliation>
<firstname>Olivier (lem)></firstname><surname>Lemaire</surname>
<firstname>Olivier (lem)</firstname><surname>Lemaire</surname>
<affiliation>
<orgname>IDEALX</orgname>
<address><email>olem@IDEALX.org</email></address>
@ -47,7 +47,7 @@ Two additional Samba resources which may prove to be helpful are
</para>
<itemizedlist>
<listitem><para>The <ulink url="http://www.unav.es/cti/ldap-smb/ldap-smb-2_2-howto.html">Samba-PDC-LDAP-HOWTO</ulink>
<listitem><para>The <ulink url="http://www.unav.es/cti/ldap-smb/ldap-smb-3-howto.html">Samba-PDC-LDAP-HOWTO</ulink>
maintained by Ignacio Coupeau.</para></listitem>
<listitem><para>The NT migration scripts from <ulink url="http://samba.idealx.org/">IDEALX</ulink> that are

8
docs/docbook/projdoc/pdb_mysql.sgml
View File

@ -54,6 +54,14 @@ identifier:mysql port - defaults to 3306
identifier:table - Name of the table containing users
</programlisting></para>
<para>
<emphasis>
WARNING: since the password for the mysql user is stored in the
smb.conf file, you should make the the smb.conf file
readable only to the user that runs samba. This is considered a security
bug and will be fixed soon.</emphasis>
</para>
<para>Names of the columns in this table(I've added column types those columns should have first):</para>
<para><programlisting>

4
docs/docbook/projdoc/samba-doc.sgml
View File

@ -22,7 +22,6 @@
<!ENTITY Portability SYSTEM "Portability.sgml">
<!ENTITY Other-Clients SYSTEM "Other-Clients.sgml">
<!ENTITY ADS-HOWTO SYSTEM "ADS-HOWTO.sgml">
<!ENTITY oplocks SYSTEM "oplocks.sgml">
<!ENTITY pdb-mysql SYSTEM "pdb_mysql.sgml">
<!ENTITY pdb-xml SYSTEM "pdb_xml.sgml">
<!ENTITY VFS SYSTEM "VFS.sgml">
@ -43,7 +42,7 @@
<title>Abstract</title>
<para>
<emphasis>Last Update</emphasis> : $Date: 2002/11/22 00:32:23 $
<emphasis>Last Update</emphasis> : $Date: 2003/01/15 22:29:21 $
</para>
<para>
@ -80,7 +79,6 @@ PLEASE read this.</para>
</partintro>
&UNIX-INSTALL;
&BROWSING;
&oplocks;
&BROWSING-Quick;
&ENCRYPTION;
</part>

24
docs/faq/clientapp.html
View File

@ -10,8 +10,8 @@ REL="HOME"
TITLE="Samba FAQ"
HREF="samba-faq.html"><LINK
REL="PREVIOUS"
TITLE="Compiling and installing Samba on a Unix host"
HREF="install.html"><LINK
TITLE="Configuration problems"
HREF="config.html"><LINK
REL="NEXT"
TITLE="Common errors"
HREF="errors.html"></HEAD
@ -42,7 +42,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="install.html"
HREF="config.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -71,15 +71,15 @@ CLASS="CHAPTER"
><A
NAME="CLIENTAPP"
></A
>Chapter 3. Specific client application problems</H1
>Chapter 4. Specific client application problems</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN170"
NAME="AEN175"
></A
>3.1. MS Office Setup reports "Cannot change properties of '\MSOFFICE\SETUP.INI'"</H1
>4.1. MS Office Setup reports "Cannot change properties of '\MSOFFICE\SETUP.INI'"</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
@ -98,9 +98,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN175"
NAME="AEN180"
></A
>3.2. How to use a Samba share as an administrative share for MS Office, etc.</H1
>4.2. How to use a Samba share as an administrative share for MS Office, etc.</H1
><P
>Microsoft Office products can be installed as an administrative installation
from which the application can either be run off the administratively installed
@ -160,9 +160,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN190"
NAME="AEN195"
></A
>3.3. Microsoft Access database opening errors</H1
>4.3. Microsoft Access database opening errors</H1
><P
>Here are some notes on running MS-Access on a Samba drive from <A
HREF="stefank@esi.com.au"
@ -210,7 +210,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="install.html"
HREF="config.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -238,7 +238,7 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Compiling and installing Samba on a Unix host</TD
>Configuration problems</TD
><TD
WIDTH="34%"
ALIGN="center"

33
docs/faq/errors.html
View File

@ -71,15 +71,15 @@ CLASS="CHAPTER"
><A
NAME="ERRORS"
></A
>Chapter 4. Common errors</H1
>Chapter 5. Common errors</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN201"
NAME="AEN206"
></A
>4.1. Not listening for calling name</H1
>5.1. Not listening for calling name</H1
><P
><PRE
CLASS="PROGRAMLISTING"
@ -103,9 +103,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN208"
NAME="AEN213"
></A
>4.2. System Error 1240</H1
>5.2. System Error 1240</H1
><P
>System error 1240 means that the client is refusing to talk
to a non-encrypting server. Microsoft changed WinNT in service
@ -139,9 +139,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN215"
NAME="AEN220"
></A
>4.3. smbclient ignores -N !</H1
>5.3. smbclient ignores -N !</H1
><P
><SPAN
CLASS="QUOTE"
@ -174,9 +174,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN224"
NAME="AEN229"
></A
>4.4. The data on the CD-Drive I've shared seems to be corrupted!</H1
>5.4. The data on the CD-Drive I've shared seems to be corrupted!</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
@ -190,9 +190,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN228"
NAME="AEN233"
></A
>4.5. Why can users access home directories of other users?</H1
>5.5. Why can users access home directories of other users?</H1
><P
><SPAN
CLASS="QUOTE"
@ -243,6 +243,17 @@ CLASS="PROGRAMLISTING"
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="AEN246"
></A
>5.6. Until a few minutes after samba has started, clients get the error "Domain Controller Unavailable"</H1
><P
>A domain controller has to announce on the network who it is. This usually takes a while.</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"

10
docs/faq/install.html
View File

@ -13,8 +13,8 @@ REL="PREVIOUS"
TITLE="General Information"
HREF="general.html"><LINK
REL="NEXT"
TITLE="Specific client application problems"
HREF="clientapp.html"></HEAD
TITLE="Configuration problems"
HREF="config.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -56,7 +56,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="clientapp.html"
HREF="config.html"
ACCESSKEY="N"
>Next</A
></TD
@ -496,7 +496,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="clientapp.html"
HREF="config.html"
ACCESSKEY="N"
>Next</A
></TD
@ -516,7 +516,7 @@ VALIGN="top"
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Specific client application problems</TD
>Configuration problems</TD
></TR
></TABLE
></DIV

96
docs/faq/samba-faq.html
View File

@ -156,118 +156,142 @@ HREF="install.html#AEN155"
></DD
><DT
>3. <A
HREF="config.html"
>Configuration problems</A
></DT
><DD
><DL
><DT
>3.1. <A
HREF="config.html#AEN170"
>I have set 'force user' and samba still makes 'root' the owner of all the files I touch!</A
></DT
></DL
></DD
><DT
>4. <A
HREF="clientapp.html"
>Specific client application problems</A
></DT
><DD
><DL
><DT
>3.1. <A
HREF="clientapp.html#AEN170"
>4.1. <A
HREF="clientapp.html#AEN175"
>MS Office Setup reports "Cannot change properties of '\MSOFFICE\SETUP.INI'"</A
></DT
><DT
>3.2. <A
HREF="clientapp.html#AEN175"
>4.2. <A
HREF="clientapp.html#AEN180"
>How to use a Samba share as an administrative share for MS Office, etc.</A
></DT
><DT
>3.3. <A
HREF="clientapp.html#AEN190"
>4.3. <A
HREF="clientapp.html#AEN195"
>Microsoft Access database opening errors</A
></DT
></DL
></DD
><DT
>4. <A
>5. <A
HREF="errors.html"
>Common errors</A
></DT
><DD
><DL
><DT
>4.1. <A
HREF="errors.html#AEN201"
>5.1. <A
HREF="errors.html#AEN206"
>Not listening for calling name</A
></DT
><DT
>4.2. <A
HREF="errors.html#AEN208"
>5.2. <A
HREF="errors.html#AEN213"
>System Error 1240</A
></DT
><DT
>4.3. <A
HREF="errors.html#AEN215"
>5.3. <A
HREF="errors.html#AEN220"
>smbclient ignores -N !</A
></DT
><DT
>4.4. <A
HREF="errors.html#AEN224"
>5.4. <A
HREF="errors.html#AEN229"
>The data on the CD-Drive I've shared seems to be corrupted!</A
></DT
><DT
>4.5. <A
HREF="errors.html#AEN228"
>5.5. <A
HREF="errors.html#AEN233"
>Why can users access home directories of other users?</A
></DT
><DT
>5.6. <A
HREF="errors.html#AEN246"
>Until a few minutes after samba has started, clients get the error "Domain Controller Unavailable"</A
></DT
></DL
></DD
><DT
>5. <A
>6. <A
HREF="features.html"
>Features</A
></DT
><DD
><DL
><DT
>5.1. <A
HREF="features.html#AEN243"
>6.1. <A
HREF="features.html#AEN251"
>How can I prevent my samba server from being used to distribute the Nimda worm?</A
></DT
><DT
>5.2. <A
HREF="features.html#AEN257"
>6.2. <A
HREF="features.html#AEN265"
>How can I use samba as a fax server?</A
></DT
><DD
><DL
><DT
>5.2.1. <A
HREF="features.html#AEN268"
>6.2.1. <A
HREF="features.html#AEN276"
>Tools for printing faxes</A
></DT
><DT
>5.2.2. <A
HREF="features.html#AEN278"
>6.2.2. <A
HREF="features.html#AEN286"
>Making the fax-server</A
></DT
><DT
>5.2.3. <A
HREF="features.html#AEN294"
>6.2.3. <A
HREF="features.html#AEN302"
>Installing the client drivers</A
></DT
><DT
>5.2.4. <A
HREF="features.html#AEN308"
>6.2.4. <A
HREF="features.html#AEN316"
>Example smb.conf</A
></DT
></DL
></DD
><DT
>5.3. <A
HREF="features.html#AEN312"
>6.3. <A
HREF="features.html#AEN320"
>Samba doesn't work well together with DHCP!</A
></DT
><DT
>5.4. <A
HREF="features.html#AEN325"
>6.4. <A
HREF="features.html#AEN333"
>How can I assign NetBIOS names to clients with DHCP?</A
></DT
><DT
>5.5. <A
HREF="features.html#AEN332"
>6.5. <A
HREF="features.html#AEN340"
>How do I convert between unix and dos text formats?</A
></DT
><DT
>6.6. <A
HREF="features.html#AEN345"
>Does samba have wins replication support?</A
></DT
></DL
></DD
></DL

656
docs/htmldocs/ENCRYPTION.html
View File

@ -1,656 +0,0 @@
<HTML
><HEAD
><TITLE
>LanMan and NT Password Encryption in Samba 2.x</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
><BODY
CLASS="ARTICLE"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="ARTICLE"
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="TITLE"
><A
NAME="PWENCRYPT"
>LanMan and NT Password Encryption in Samba 2.x</A
></H1
><HR></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3"
>Introduction</A
></H1
><P
>With the development of LanManager and Windows NT
compatible password encryption for Samba, it is now able
to validate user connections in exactly the same way as
a LanManager or Windows NT server.</P
><P
>This document describes how the SMB password encryption
algorithm works and what issues there are in choosing whether
you want to use it. You should read it carefully, especially
the part about security and the "PROS and CONS" section.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN7"
>How does it work?</A
></H1
><P
>LanManager encryption is somewhat similar to UNIX
password encryption. The server uses a file containing a
hashed value of a user's password. This is created by taking
the user's plaintext password, capitalising it, and either
truncating to 14 bytes or padding to 14 bytes with null bytes.
This 14 byte value is used as two 56 bit DES keys to encrypt
a 'magic' eight byte value, forming a 16 byte value which is
stored by the server and client. Let this value be known as
the "hashed password".</P
><P
>Windows NT encryption is a higher quality mechanism,
consisting of doing an MD4 hash on a Unicode version of the user's
password. This also produces a 16 byte hash value that is
non-reversible.</P
><P
>When a client (LanManager, Windows for WorkGroups, Windows
95 or Windows NT) wishes to mount a Samba drive (or use a Samba
resource), it first requests a connection and negotiates the
protocol that the client and server will use. In the reply to this
request the Samba server generates and appends an 8 byte, random
value - this is stored in the Samba server after the reply is sent
and is known as the "challenge". The challenge is different for
every client connection.</P
><P
>The client then uses the hashed password (16 byte values
described above), appended with 5 null bytes, as three 56 bit
DES keys, each of which is used to encrypt the challenge 8 byte
value, forming a 24 byte value known as the "response".</P
><P
>In the SMB call SMBsessionsetupX (when user level security
is selected) or the call SMBtconX (when share level security is
selected), the 24 byte response is returned by the client to the
Samba server. For Windows NT protocol levels the above calculation
is done on both hashes of the user's password and both responses are
returned in the SMB call, giving two 24 byte values.</P
><P
>The Samba server then reproduces the above calculation, using
its own stored value of the 16 byte hashed password (read from the
<TT
CLASS="FILENAME"
>smbpasswd</TT
> file - described later) and the challenge
value that it kept from the negotiate protocol reply. It then checks
to see if the 24 byte value it calculates matches the 24 byte value
returned to it from the client.</P
><P
>If these values match exactly, then the client knew the
correct password (or the 16 byte hashed value - see security note
below) and is thus allowed access. If not, then the client did not
know the correct password and is denied access.</P
><P
>Note that the Samba server never knows or stores the cleartext
of the user's password - just the 16 byte hashed values derived from
it. Also note that the cleartext password or 16 byte hashed values
are never transmitted over the network - thus increasing security.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN18"
>Important Notes About Security</A
></H1
><P
>The unix and SMB password encryption techniques seem similar
on the surface. This similarity is, however, only skin deep. The unix
scheme typically sends clear text passwords over the network when
logging in. This is bad. The SMB encryption scheme never sends the
cleartext password over the network but it does store the 16 byte
hashed values on disk. This is also bad. Why? Because the 16 byte hashed
values are a "password equivalent". You cannot derive the user's
password from them, but they could potentially be used in a modified
client to gain access to a server. This would require considerable
technical knowledge on behalf of the attacker but is perfectly possible.
You should thus treat the smbpasswd file as though it contained the
cleartext passwords of all your users. Its contents must be kept
secret, and the file should be protected accordingly.</P
><P
>Ideally we would like a password scheme which neither requires
plain text passwords on the net or on disk. Unfortunately this
is not available as Samba is stuck with being compatible with
other SMB systems (WinNT, WfWg, Win95 etc). </P
><DIV
CLASS="WARNING"
><P
></P
><TABLE
CLASS="WARNING"
BORDER="1"
WIDTH="100%"
><TR
><TD
ALIGN="CENTER"
><B
>Warning</B
></TD
></TR
><TR
><TD
ALIGN="LEFT"
><P
>Note that Windows NT 4.0 Service pack 3 changed the
default for permissible authentication so that plaintext
passwords are <I
CLASS="EMPHASIS"
>never</I
> sent over the wire.
The solution to this is either to switch to encrypted passwords
with Samba or edit the Windows NT registry to re-enable plaintext
passwords. See the document WinNT.txt for details on how to do
this.</P
><P
>Other Microsoft operating systems which also exhibit
this behavior includes</P
><P
></P
><UL
><LI
><P
>MS DOS Network client 3.0 with
the basic network redirector installed</P
></LI
><LI
><P
>Windows 95 with the network redirector
update installed</P
></LI
><LI
><P
>Windows 98 [se]</P
></LI
><LI
><P
>Windows 2000</P
></LI
></UL
><P
><I
CLASS="EMPHASIS"
>Note :</I
>All current release of
Microsoft SMB/CIFS clients support authentication via the
SMB Challenge/Response mechanism described here. Enabling
clear text authentication does not disable the ability
of the client to participate in encrypted authentication.</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN37"
>Advantages of SMB Encryption</A
></H2
><P
></P
><UL
><LI
><P
>plain text passwords are not passed across
the network. Someone using a network sniffer cannot just
record passwords going to the SMB server.</P
></LI
><LI
><P
>WinNT doesn't like talking to a server
that isn't using SMB encrypted passwords. It will refuse
to browse the server if the server is also in user level
security mode. It will insist on prompting the user for the
password on each connection, which is very annoying. The
only things you can do to stop this is to use SMB encryption.
</P
></LI
></UL
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN44"
>Advantages of non-encrypted passwords</A
></H2
><P
></P
><UL
><LI
><P
>plain text passwords are not kept
on disk. </P
></LI
><LI
><P
>uses same password file as other unix
services such as login and ftp</P
></LI
><LI
><P
>you are probably already using other
services (such as telnet and ftp) which send plain text
passwords over the net, so sending them for SMB isn't
such a big deal.</P
></LI
></UL
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN53"
><A
NAME="SMBPASSWDFILEFORMAT"
></A
>The smbpasswd file</A
></H1
><P
>In order for Samba to participate in the above protocol
it must be able to look up the 16 byte hashed values given a user name.
Unfortunately, as the UNIX password value is also a one way hash
function (ie. it is impossible to retrieve the cleartext of the user's
password given the UNIX hash of it), a separate password file
containing this 16 byte value must be kept. To minimise problems with
these two password files, getting out of sync, the UNIX <TT
CLASS="FILENAME"
> /etc/passwd</TT
> and the <TT
CLASS="FILENAME"
>smbpasswd</TT
> file,
a utility, <B
CLASS="COMMAND"
>mksmbpasswd.sh</B
>, is provided to generate
a smbpasswd file from a UNIX <TT
CLASS="FILENAME"
>/etc/passwd</TT
> file.
</P
><P
>To generate the smbpasswd file from your <TT
CLASS="FILENAME"
>/etc/passwd
</TT
> file use the following command :</P
><P
><TT
CLASS="PROMPT"
>$ </TT
><TT
CLASS="USERINPUT"
><B
>cat /etc/passwd | mksmbpasswd.sh
&gt; /usr/local/samba/private/smbpasswd</B
></TT
></P
><P
>If you are running on a system that uses NIS, use</P
><P
><TT
CLASS="PROMPT"
>$ </TT
><TT
CLASS="USERINPUT"
><B
>ypcat passwd | mksmbpasswd.sh
&gt; /usr/local/samba/private/smbpasswd</B
></TT
></P
><P
>The <B
CLASS="COMMAND"
>mksmbpasswd.sh</B
> program is found in
the Samba source directory. By default, the smbpasswd file is
stored in :</P
><P
><TT
CLASS="FILENAME"
>/usr/local/samba/private/smbpasswd</TT
></P
><P
>The owner of the <TT
CLASS="FILENAME"
>/usr/local/samba/private/</TT
>
directory should be set to root, and the permissions on it should
be set to 0500 (<B
CLASS="COMMAND"
>chmod 500 /usr/local/samba/private</B
>).
</P
><P
>Likewise, the smbpasswd file inside the private directory should
be owned by root and the permissions on is should be set to 0600
(<B
CLASS="COMMAND"
>chmod 600 smbpasswd</B
>).</P
><P
>The format of the smbpasswd file is (The line has been
wrapped here. It should appear as one entry per line in
your smbpasswd file.)</P
><P
><PRE
CLASS="PROGRAMLISTING"
>username:uid:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:
[Account type]:LCT-&lt;last-change-time&gt;:Long name
</PRE
></P
><P
>Although only the <TT
CLASS="REPLACEABLE"
><I
>username</I
></TT
>,
<TT
CLASS="REPLACEABLE"
><I
>uid</I
></TT
>, <TT
CLASS="REPLACEABLE"
><I
> XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX</I
></TT
>,
[<TT
CLASS="REPLACEABLE"
><I
>Account type</I
></TT
>] and <TT
CLASS="REPLACEABLE"
><I
> last-change-time</I
></TT
> sections are significant
and are looked at in the Samba code.</P
><P
>It is <I
CLASS="EMPHASIS"
>VITALLY</I
> important that there by 32
'X' characters between the two ':' characters in the XXX sections -
the smbpasswd and Samba code will fail to validate any entries that
do not have 32 characters between ':' characters. The first XXX
section is for the Lanman password hash, the second is for the
Windows NT version.</P
><P
>When the password file is created all users have password entries
consisting of 32 'X' characters. By default this disallows any access
as this user. When a user has a password set, the 'X' characters change
to 32 ascii hexadecimal digits (0-9, A-F). These are an ascii
representation of the 16 byte hashed value of a user's password.</P
><P
>To set a user to have no password (not recommended), edit the file
using vi, and replace the first 11 characters with the ascii text
<TT
CLASS="CONSTANT"
>"NO PASSWORD"</TT
> (minus the quotes).</P
><P
>For example, to clear the password for user bob, his smbpasswd file
entry would look like :</P
><P
><PRE
CLASS="PROGRAMLISTING"
> bob:100:NO PASSWORDXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:[U ]:LCT-00000000:Bob's full name:/bobhome:/bobshell
</PRE
></P
><P
>If you are allowing users to use the smbpasswd command to set
their own passwords, you may want to give users NO PASSWORD initially
so they do not have to enter a previous password when changing to their
new password (not recommended). In order for you to allow this the
<B
CLASS="COMMAND"
>smbpasswd</B
> program must be able to connect to the
<B
CLASS="COMMAND"
>smbd</B
> daemon as that user with no password. Enable this
by adding the line :</P
><P
><B
CLASS="COMMAND"
>null passwords = yes</B
></P
><P
>to the [global] section of the smb.conf file (this is why
the above scenario is not recommended). Preferably, allocate your
users a default password to begin with, so you do not have
to enable this on your server.</P
><P
><I
CLASS="EMPHASIS"
>Note : </I
>This file should be protected very
carefully. Anyone with access to this file can (with enough knowledge of
the protocols) gain access to your SMB server. The file is thus more
sensitive than a normal unix <TT
CLASS="FILENAME"
>/etc/passwd</TT
> file.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN105"
>The smbpasswd Command</A
></H1
><P
>The smbpasswd command maintains the two 32 byte password fields
in the smbpasswd file. If you wish to make it similar to the unix
<B
CLASS="COMMAND"
>passwd</B
> or <B
CLASS="COMMAND"
>yppasswd</B
> programs,
install it in <TT
CLASS="FILENAME"
>/usr/local/samba/bin/</TT
> (or your
main Samba binary directory).</P
><P
>Note that as of Samba 1.9.18p4 this program <I
CLASS="EMPHASIS"
>MUST NOT
BE INSTALLED</I
> setuid root (the new <B
CLASS="COMMAND"
>smbpasswd</B
>
code enforces this restriction so it cannot be run this way by
accident).</P
><P
><B
CLASS="COMMAND"
>smbpasswd</B
> now works in a client-server mode
where it contacts the local smbd to change the user's password on its
behalf. This has enormous benefits - as follows.</P
><P
></P
><UL
><LI
><P
>smbpasswd no longer has to be setuid root -
an enormous range of potential security problems is
eliminated.</P
></LI
><LI
><P
><B
CLASS="COMMAND"
>smbpasswd</B
> now has the capability
to change passwords on Windows NT servers (this only works when
the request is sent to the NT Primary Domain Controller if you
are changing an NT Domain user's password).</P
></LI
></UL
><P
>To run smbpasswd as a normal user just type :</P
><P
><TT
CLASS="PROMPT"
>$ </TT
><TT
CLASS="USERINPUT"
><B
>smbpasswd</B
></TT
></P
><P
><TT
CLASS="PROMPT"
>Old SMB password: </TT
><TT
CLASS="USERINPUT"
><B
>&lt;type old value here -
or hit return if there was no old password&gt;</B
></TT
></P
><P
><TT
CLASS="PROMPT"
>New SMB Password: </TT
><TT
CLASS="USERINPUT"
><B
>&lt;type new value&gt;
</B
></TT
></P
><P
><TT
CLASS="PROMPT"
>Repeat New SMB Password: </TT
><TT
CLASS="USERINPUT"
><B
>&lt;re-type new value
</B
></TT
></P
><P
>If the old value does not match the current value stored for
that user, or the two new values do not match each other, then the
password will not be changed.</P
><P
>If invoked by an ordinary user it will only allow the user
to change his or her own Samba password.</P
><P
>If run by the root user smbpasswd may take an optional
argument, specifying the user name whose SMB password you wish to
change. Note that when run as root smbpasswd does not prompt for
or check the old password value, thus allowing root to set passwords
for users who have forgotten their passwords.</P
><P
><B
CLASS="COMMAND"
>smbpasswd</B
> is designed to work in the same way
and be familiar to UNIX users who use the <B
CLASS="COMMAND"
>passwd</B
> or
<B
CLASS="COMMAND"
>yppasswd</B
> commands.</P
><P
>For more details on using <B
CLASS="COMMAND"
>smbpasswd</B
> refer
to the man page which will always be the definitive reference.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN144"
>Setting up Samba to support LanManager Encryption</A
></H1
><P
>This is a very brief description on how to setup samba to
support password encryption. </P
><P
></P
><OL
TYPE="1"
><LI
><P
>compile and install samba as usual</P
></LI
><LI
><P
>enable encrypted passwords in <TT
CLASS="FILENAME"
> smb.conf</TT
> by adding the line <B
CLASS="COMMAND"
>encrypt
passwords = yes</B
> in the [global] section</P
></LI
><LI
><P
>create the initial <TT
CLASS="FILENAME"
>smbpasswd</TT
>
password file in the place you specified in the Makefile
(--prefix=&lt;dir&gt;). See the notes under the <A
HREF="#SMBPASSWDFILEFORMAT"
>The smbpasswd File</A
>
section earlier in the document for details.</P
></LI
></OL
><P
>Note that you can test things using smbclient.</P
></DIV
></DIV
></BODY
></HTML
>

783
docs/htmldocs/NT_Security.html
View File

@ -1,783 +0,0 @@
<HTML
><HEAD
><TITLE
>UNIX Permission Bits and Windows NT Access Control Lists</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
><BODY
CLASS="ARTICLE"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="ARTICLE"
><DIV
CLASS="TITLEPAGE"
><H1
CLASS="TITLE"
><A
NAME="UNIX-PERMISSIONS"
>UNIX Permission Bits and Windows NT Access Control Lists</A
></H1
><HR></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3"
>Viewing and changing UNIX permissions using the NT
security dialogs</A
></H1
><P
>New in the Samba 2.0.4 release is the ability for Windows
NT clients to use their native security settings dialog box to
view and modify the underlying UNIX permissions.</P
><P
>Note that this ability is careful not to compromise
the security of the UNIX host Samba is running on, and
still obeys all the file permission rules that a Samba
administrator can set.</P
><P
>In Samba 2.0.4 and above the default value of the
parameter <A
HREF="smb.conf.5.html#NTACLSUPPORT"
TARGET="_top"
><TT
CLASS="PARAMETER"
><I
> nt acl support</I
></TT
></A
> has been changed from
<TT
CLASS="CONSTANT"
>false</TT
> to <TT
CLASS="CONSTANT"
>true</TT
>, so
manipulation of permissions is turned on by default.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN12"
>How to view file security on a Samba share</A
></H1
><P
>From an NT 4.0 client, single-click with the right
mouse button on any file or directory in a Samba mounted
drive letter or UNC path. When the menu pops-up, click
on the <I
CLASS="EMPHASIS"
>Properties</I
> entry at the bottom of
the menu. This brings up the normal file properties dialog
box, but with Samba 2.0.4 this will have a new tab along the top
marked <I
CLASS="EMPHASIS"
>Security</I
>. Click on this tab and you
will see three buttons, <I
CLASS="EMPHASIS"
>Permissions</I
>,
<I
CLASS="EMPHASIS"
>Auditing</I
>, and <I
CLASS="EMPHASIS"
>Ownership</I
>.
The <I
CLASS="EMPHASIS"
>Auditing</I
> button will cause either
an error message <SPAN
CLASS="ERRORNAME"
>A requested privilege is not held
by the client</SPAN
> to appear if the user is not the
NT Administrator, or a dialog which is intended to allow an
Administrator to add auditing requirements to a file if the
user is logged on as the NT Administrator. This dialog is
non-functional with a Samba share at this time, as the only
useful button, the <B
CLASS="COMMAND"
>Add</B
> button will not currently
allow a list of users to be seen.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN23"
>Viewing file ownership</A
></H1
><P
>Clicking on the <B
CLASS="COMMAND"
>"Ownership"</B
> button
brings up a dialog box telling you who owns the given file. The
owner name will be of the form :</P
><P
><B
CLASS="COMMAND"
>"SERVER\user (Long name)"</B
></P
><P
>Where <TT
CLASS="REPLACEABLE"
><I
>SERVER</I
></TT
> is the NetBIOS name of
the Samba server, <TT
CLASS="REPLACEABLE"
><I
>user</I
></TT
> is the user name of
the UNIX user who owns the file, and <TT
CLASS="REPLACEABLE"
><I
>(Long name)</I
></TT
>
is the descriptive string identifying the user (normally found in the
GECOS field of the UNIX password database). Click on the <B
CLASS="COMMAND"
>Close
</B
> button to remove this dialog.</P
><P
>If the parameter <TT
CLASS="PARAMETER"
><I
>nt acl support</I
></TT
>
is set to <TT
CLASS="CONSTANT"
>false</TT
> then the file owner will
be shown as the NT user <B
CLASS="COMMAND"
>"Everyone"</B
>.</P
><P
>The <B
CLASS="COMMAND"
>Take Ownership</B
> button will not allow
you to change the ownership of this file to yourself (clicking on
it will display a dialog box complaining that the user you are
currently logged onto the NT client cannot be found). The reason
for this is that changing the ownership of a file is a privileged
operation in UNIX, available only to the <I
CLASS="EMPHASIS"
>root</I
>
user. As clicking on this button causes NT to attempt to change
the ownership of a file to the current user logged into the NT
client this will not work with Samba at this time.</P
><P
>There is an NT chown command that will work with Samba
and allow a user with Administrator privilege connected
to a Samba 2.0.4 server as root to change the ownership of
files on both a local NTFS filesystem or remote mounted NTFS
or Samba drive. This is available as part of the <I
CLASS="EMPHASIS"
>Seclib
</I
> NT security library written by Jeremy Allison of
the Samba Team, available from the main Samba ftp site.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN43"
>Viewing file or directory permissions</A
></H1
><P
>The third button is the <B
CLASS="COMMAND"
>"Permissions"</B
>
button. Clicking on this brings up a dialog box that shows both
the permissions and the UNIX owner of the file or directory.
The owner is displayed in the form :</P
><P
><B
CLASS="COMMAND"
>"SERVER\user (Long name)"</B
></P
><P
>Where <TT
CLASS="REPLACEABLE"
><I
>SERVER</I
></TT
> is the NetBIOS name of
the Samba server, <TT
CLASS="REPLACEABLE"
><I
>user</I
></TT
> is the user name of
the UNIX user who owns the file, and <TT
CLASS="REPLACEABLE"
><I
>(Long name)</I
></TT
>
is the descriptive string identifying the user (normally found in the
GECOS field of the UNIX password database).</P
><P
>If the parameter <TT
CLASS="PARAMETER"
><I
>nt acl support</I
></TT
>
is set to <TT
CLASS="CONSTANT"
>false</TT
> then the file owner will
be shown as the NT user <B
CLASS="COMMAND"
>"Everyone"</B
> and the
permissions will be shown as NT "Full Control".</P
><P
>The permissions field is displayed differently for files
and directories, so I'll describe the way file permissions
are displayed first.</P
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN58"
>File Permissions</A
></H2
><P
>The standard UNIX user/group/world triple and
the corresponding "read", "write", "execute" permissions
triples are mapped by Samba into a three element NT ACL
with the 'r', 'w', and 'x' bits mapped into the corresponding
NT permissions. The UNIX world permissions are mapped into
the global NT group <B
CLASS="COMMAND"
>Everyone</B
>, followed
by the list of permissions allowed for UNIX world. The UNIX
owner and group permissions are displayed as an NT
<B
CLASS="COMMAND"
>user</B
> icon and an NT <B
CLASS="COMMAND"
>local
group</B
> icon respectively followed by the list
of permissions allowed for the UNIX user and group.</P
><P
>As many UNIX permission sets don't map into common
NT names such as <B
CLASS="COMMAND"
>"read"</B
>, <B
CLASS="COMMAND"
> "change"</B
> or <B
CLASS="COMMAND"
>"full control"</B
> then
usually the permissions will be prefixed by the words <B
CLASS="COMMAND"
> "Special Access"</B
> in the NT display list.</P
><P
>But what happens if the file has no permissions allowed
for a particular UNIX user group or world component ? In order
to allow "no permissions" to be seen and modified then Samba
overloads the NT <B
CLASS="COMMAND"
>"Take Ownership"</B
> ACL attribute
(which has no meaning in UNIX) and reports a component with
no permissions as having the NT <B
CLASS="COMMAND"
>"O"</B
> bit set.
This was chosen of course to make it look like a zero, meaning
zero permissions. More details on the decision behind this will
be given below.</P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN72"
>Directory Permissions</A
></H2
><P
>Directories on an NT NTFS file system have two
different sets of permissions. The first set of permissions
is the ACL set on the directory itself, this is usually displayed
in the first set of parentheses in the normal <B
CLASS="COMMAND"
>"RW"</B
>
NT style. This first set of permissions is created by Samba in
exactly the same way as normal file permissions are, described
above, and is displayed in the same way.</P
><P
>The second set of directory permissions has no real meaning
in the UNIX permissions world and represents the <B
CLASS="COMMAND"
> "inherited"</B
> permissions that any file created within
this directory would inherit.</P
><P
>Samba synthesises these inherited permissions for NT by
returning as an NT ACL the UNIX permission mode that a new file
created by Samba on this share would receive.</P
></DIV
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN79"
>Modifying file or directory permissions</A
></H1
><P
>Modifying file and directory permissions is as simple
as changing the displayed permissions in the dialog box, and
clicking the <B
CLASS="COMMAND"
>OK</B
> button. However, there are
limitations that a user needs to be aware of, and also interactions
with the standard Samba permission masks and mapping of DOS
attributes that need to also be taken into account.</P
><P
>If the parameter <TT
CLASS="PARAMETER"
><I
>nt acl support</I
></TT
>
is set to <TT
CLASS="CONSTANT"
>false</TT
> then any attempt to set
security permissions will fail with an <B
CLASS="COMMAND"
>"Access Denied"
</B
> message.</P
><P
>The first thing to note is that the <B
CLASS="COMMAND"
>"Add"</B
>
button will not return a list of users in Samba 2.0.4 (it will give
an error message of <B
CLASS="COMMAND"
>"The remote procedure call failed
and did not execute"</B
>). This means that you can only
manipulate the current user/group/world permissions listed in
the dialog box. This actually works quite well as these are the
only permissions that UNIX actually has.</P
><P
>If a permission triple (either user, group, or world)
is removed from the list of permissions in the NT dialog box,
then when the <B
CLASS="COMMAND"
>"OK"</B
> button is pressed it will
be applied as "no permissions" on the UNIX side. If you then
view the permissions again the "no permissions" entry will appear
as the NT <B
CLASS="COMMAND"
>"O"</B
> flag, as described above. This
allows you to add permissions back to a file or directory once
you have removed them from a triple component.</P
><P
>As UNIX supports only the "r", "w" and "x" bits of
an NT ACL then if other NT security attributes such as "Delete
access" are selected then they will be ignored when applied on
the Samba server.</P
><P
>When setting permissions on a directory the second
set of permissions (in the second set of parentheses) is
by default applied to all files within that directory. If this
is not what you want you must uncheck the <B
CLASS="COMMAND"
>"Replace
permissions on existing files"</B
> checkbox in the NT
dialog before clicking <B
CLASS="COMMAND"
>"OK"</B
>.</P
><P
>If you wish to remove all permissions from a
user/group/world component then you may either highlight the
component and click the <B
CLASS="COMMAND"
>"Remove"</B
> button,
or set the component to only have the special <B
CLASS="COMMAND"
>"Take
Ownership"</B
> permission (displayed as <B
CLASS="COMMAND"
>"O"
</B
>) highlighted.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN101"
>Interaction with the standard Samba create mask
parameters</A
></H1
><P
>Note that with Samba 2.0.5 there are four new parameters
to control this interaction. These are :</P
><P
><TT
CLASS="PARAMETER"
><I
>security mask</I
></TT
></P
><P
><TT
CLASS="PARAMETER"
><I
>force security mode</I
></TT
></P
><P
><TT
CLASS="PARAMETER"
><I
>directory security mask</I
></TT
></P
><P
><TT
CLASS="PARAMETER"
><I
>force directory security mode</I
></TT
></P
><P
>Once a user clicks <B
CLASS="COMMAND"
>"OK"</B
> to apply the
permissions Samba maps the given permissions into a user/group/world
r/w/x triple set, and then will check the changed permissions for a
file against the bits set in the <A
HREF="smb.conf.5.html#SECURITYMASK"
TARGET="_top"
>
<TT
CLASS="PARAMETER"
><I
>security mask</I
></TT
></A
> parameter. Any bits that
were changed that are not set to '1' in this parameter are left alone
in the file permissions.</P
><P
>Essentially, zero bits in the <TT
CLASS="PARAMETER"
><I
>security mask</I
></TT
>
mask may be treated as a set of bits the user is <I
CLASS="EMPHASIS"
>not</I
>
allowed to change, and one bits are those the user is allowed to change.
</P
><P
>If not set explicitly this parameter is set to the same value as
the <A
HREF="smb.conf.5.html#CREATEMASK"
TARGET="_top"
><TT
CLASS="PARAMETER"
><I
>create mask
</I
></TT
></A
> parameter to provide compatibility with Samba 2.0.4
where this permission change facility was introduced. To allow a user to
modify all the user/group/world permissions on a file, set this parameter
to 0777.</P
><P
>Next Samba checks the changed permissions for a file against
the bits set in the <A
HREF="smb.conf.5.html#FORCESECURITYMODE"
TARGET="_top"
> <TT
CLASS="PARAMETER"
><I
>force security mode</I
></TT
></A
> parameter. Any bits
that were changed that correspond to bits set to '1' in this parameter
are forced to be set.</P
><P
>Essentially, bits set in the <TT
CLASS="PARAMETER"
><I
>force security mode
</I
></TT
> parameter may be treated as a set of bits that, when
modifying security on a file, the user has always set to be 'on'.</P
><P
>If not set explicitly this parameter is set to the same value
as the <A
HREF="smb.conf.5.html#FORCECREATEMODE"
TARGET="_top"
><TT
CLASS="PARAMETER"
><I
>force
create mode</I
></TT
></A
> parameter to provide compatibility
with Samba 2.0.4 where the permission change facility was introduced.
To allow a user to modify all the user/group/world permissions on a file
with no restrictions set this parameter to 000.</P
><P
>The <TT
CLASS="PARAMETER"
><I
>security mask</I
></TT
> and <TT
CLASS="PARAMETER"
><I
>force
security mode</I
></TT
> parameters are applied to the change
request in that order.</P
><P
>For a directory Samba will perform the same operations as
described above for a file except using the parameter <TT
CLASS="PARAMETER"
><I
> directory security mask</I
></TT
> instead of <TT
CLASS="PARAMETER"
><I
>security
mask</I
></TT
>, and <TT
CLASS="PARAMETER"
><I
>force directory security mode
</I
></TT
> parameter instead of <TT
CLASS="PARAMETER"
><I
>force security mode
</I
></TT
>.</P
><P
>The <TT
CLASS="PARAMETER"
><I
>directory security mask</I
></TT
> parameter
by default is set to the same value as the <TT
CLASS="PARAMETER"
><I
>directory mask
</I
></TT
> parameter and the <TT
CLASS="PARAMETER"
><I
>force directory security
mode</I
></TT
> parameter by default is set to the same value as
the <TT
CLASS="PARAMETER"
><I
>force directory mode</I
></TT
> parameter to provide
compatibility with Samba 2.0.4 where the permission change facility
was introduced.</P
><P
>In this way Samba enforces the permission restrictions that
an administrator can set on a Samba share, whilst still allowing users
to modify the permission bits within that restriction.</P
><P
>If you want to set up a share that allows users full control
in modifying the permission bits on their files and directories and
doesn't force any particular bits to be set 'on', then set the following
parameters in the <A
HREF="smb.conf.5.html"
TARGET="_top"
><TT
CLASS="FILENAME"
>smb.conf(5)
</TT
></A
> file in that share specific section :</P
><P
><TT
CLASS="PARAMETER"
><I
>security mask = 0777</I
></TT
></P
><P
><TT
CLASS="PARAMETER"
><I
>force security mode = 0</I
></TT
></P
><P
><TT
CLASS="PARAMETER"
><I
>directory security mask = 0777</I
></TT
></P
><P
><TT
CLASS="PARAMETER"
><I
>force directory security mode = 0</I
></TT
></P
><P
>As described, in Samba 2.0.4 the parameters :</P
><P
><TT
CLASS="PARAMETER"
><I
>create mask</I
></TT
></P
><P
><TT
CLASS="PARAMETER"
><I
>force create mode</I
></TT
></P
><P
><TT
CLASS="PARAMETER"
><I
>directory mask</I
></TT
></P
><P
><TT
CLASS="PARAMETER"
><I
>force directory mode</I
></TT
></P
><P
>were used instead of the parameters discussed here.</P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN165"
>Interaction with the standard Samba file attribute
mapping</A
></H1
><P
>Samba maps some of the DOS attribute bits (such as "read
only") into the UNIX permissions of a file. This means there can
be a conflict between the permission bits set via the security
dialog and the permission bits set by the file attribute mapping.
</P
><P
>One way this can show up is if a file has no UNIX read access
for the owner it will show up as "read only" in the standard
file attributes tabbed dialog. Unfortunately this dialog is
the same one that contains the security info in another tab.</P
><P
>What this can mean is that if the owner changes the permissions
to allow themselves read access using the security dialog, clicks
<B
CLASS="COMMAND"
>"OK"</B
> to get back to the standard attributes tab
dialog, and then clicks <B
CLASS="COMMAND"
>"OK"</B
> on that dialog, then
NT will set the file permissions back to read-only (as that is what
the attributes still say in the dialog). This means that after setting
permissions and clicking <B
CLASS="COMMAND"
>"OK"</B
> to get back to the
attributes dialog you should always hit <B
CLASS="COMMAND"
>"Cancel"</B
>
rather than <B
CLASS="COMMAND"
>"OK"</B
> to ensure that your changes
are not overridden.</P
></DIV
></DIV
></BODY
></HTML
>

2313
docs/htmldocs/Samba-Developers-Guide.html
View File

File diff suppressed because it is too large Load Diff

14862
docs/htmldocs/Samba-HOWTO-Collection.html
View File

File diff suppressed because it is too large Load Diff

1440
docs/htmldocs/Samba-HOWTO.html
View File

File diff suppressed because it is too large Load Diff

2284
docs/htmldocs/Samba-PDC-HOWTO.html
View File

File diff suppressed because it is too large Load Diff

55
docs/htmldocs/browsing-quick.html
View File

@ -9,12 +9,15 @@ CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><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="Improved browsing in samba"
HREF="improved-browsing.html"><LINK
TITLE="Oplocks"
HREF="oplocks.html"><LINK
REL="NEXT"
TITLE="Samba performance issues"
HREF="speed.html"></HEAD
TITLE="LanMan and NT Password Encryption in Samba"
HREF="pwencrypt.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="improved-browsing.html"
HREF="oplocks.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="speed.html"
HREF="pwencrypt.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,7 +74,7 @@ CLASS="CHAPTER"
><A
NAME="BROWSING-QUICK"
></A
>Chapter 16. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</H1
>Chapter 4. Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</H1
><P
>This document should be read in conjunction with Browsing and may
be taken as the fast track guide to implementing browsing across subnets
@ -83,9 +86,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2665"
NAME="AEN393"
></A
>16.1. Discussion</H1
>4.1. Discussion</H1
><P
>Firstly, all MS Windows networking is based on SMB (Server Message
Block) based messaging. SMB messaging is implemented using NetBIOS. Samba
@ -129,9 +132,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2673"
NAME="AEN401"
></A
>16.2. Use of the "Remote Announce" parameter</H1
>4.2. Use of the "Remote Announce" parameter</H1
><P
>The "remote announce" parameter of smb.conf can be used to forcibly ensure
that all the NetBIOS names on a network get announced to a remote network.
@ -187,9 +190,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2687"
NAME="AEN415"
></A
>16.3. Use of the "Remote Browse Sync" parameter</H1
>4.3. Use of the "Remote Browse Sync" parameter</H1
><P
>The "remote browse sync" parameter of smb.conf is used to announce to
another LMB that it must synchronise it's NetBIOS name list with our
@ -209,9 +212,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2692"
NAME="AEN420"
></A
>16.4. Use of WINS</H1
>4.4. Use of WINS</H1
><P
>Use of WINS (either Samba WINS _or_ MS Windows NT Server WINS) is highly
recommended. Every NetBIOS machine registers it's name together with a
@ -271,9 +274,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2703"
NAME="AEN431"
></A
>16.5. Do NOT use more than one (1) protocol on MS Windows machines</H1
>4.5. Do NOT use more than one (1) protocol on MS Windows machines</H1
><P
>A very common cause of browsing problems results from installing more than
one protocol on an MS Windows machine.</P
@ -301,9 +304,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2709"
NAME="AEN437"
></A
>16.6. Name Resolution Order</H1
>4.6. Name Resolution Order</H1
><P
>Resolution of NetBIOS names to IP addresses can take place using a number
of methods. The only ones that can provide NetBIOS name_type information
@ -398,7 +401,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="improved-browsing.html"
HREF="oplocks.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -416,7 +419,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="speed.html"
HREF="pwencrypt.html"
ACCESSKEY="N"
>Next</A
></TD
@ -426,17 +429,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Improved browsing in samba</TD
>Oplocks</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="introduction.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Samba performance issues</TD
>LanMan and NT Password Encryption in Samba</TD
></TR
></TABLE
></DIV

72
docs/htmldocs/bugreport.html
View File

@ -9,12 +9,15 @@ CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
REL="UP"
TITLE="Appendixes"
HREF="appendixes.html"><LINK
REL="PREVIOUS"
TITLE="HOWTO Access Samba source code via CVS"
HREF="cvs-access.html"><LINK
TITLE="Samba and other CIFS clients"
HREF="other-clients.html"><LINK
REL="NEXT"
TITLE="Group mapping HOWTO"
HREF="groupmapping.html"></HEAD
TITLE="Diagnosing your samba server"
HREF="diagnosis.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="cvs-access.html"
HREF="other-clients.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="groupmapping.html"
HREF="diagnosis.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,17 +74,26 @@ CLASS="CHAPTER"
><A
NAME="BUGREPORT"
></A
>Chapter 19. Reporting Bugs</H1
>Chapter 26. Reporting Bugs</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2921"
NAME="AEN3368"
></A
>19.1. Introduction</H1
>26.1. Introduction</H1
><P
>The email address for bug reports is samba@samba.org</P
>The email address for bug reports for stable releases is <A
HREF="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
report. Also, please see if it has changed between releases, as we
@ -102,16 +114,20 @@ 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 http://samba.org/samba/ </P
at <A
HREF="http://samba.org/samba/"
TARGET="_top"
>http://samba.org/samba/</A
>.</P
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2928"
NAME="AEN3378"
></A
>19.2. General info</H1
>26.2. General info</H1
><P
>Before submitting a bug report check your config for silly
errors. Look in your log files for obvious messages that tell you that
@ -134,9 +150,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2934"
NAME="AEN3384"
></A
>19.3. Debug levels</H1
>26.3. Debug levels</H1
><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
@ -204,9 +220,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2951"
NAME="AEN3401"
></A
>19.4. Internal errors</H1
>26.4. Internal errors</H1
><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
@ -248,9 +264,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2961"
NAME="AEN3411"
></A
>19.5. Attaching to a running process</H1
>26.5. Attaching to a running process</H1
><P
>Unfortunately some unixes (in particular some recent linux kernels)
refuse to dump a core file if the task has changed uid (which smbd
@ -265,9 +281,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2964"
NAME="AEN3414"
></A
>19.6. Patches</H1
>26.6. Patches</H1
><P
>The best sort of bug report is one that includes a fix! If you send us
patches please use <B
@ -298,7 +314,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="cvs-access.html"
HREF="other-clients.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -316,7 +332,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="groupmapping.html"
HREF="diagnosis.html"
ACCESSKEY="N"
>Next</A
></TD
@ -326,17 +342,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>HOWTO Access Samba source code via CVS</TD
>Samba and other CIFS clients</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="appendixes.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Group mapping HOWTO</TD
>Diagnosing your samba server</TD
></TR
></TABLE
></DIV

47
docs/htmldocs/cvs-access.html
View File

@ -9,12 +9,15 @@ CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
REL="UP"
TITLE="Optional configuration"
HREF="optional.html"><LINK
REL="PREVIOUS"
TITLE="Samba performance issues"
HREF="speed.html"><LINK
TITLE="Storing Samba's User/Machine Account information in an LDAP Directory"
HREF="samba-ldap-howto.html"><LINK
REL="NEXT"
TITLE="Reporting Bugs"
HREF="bugreport.html"></HEAD
TITLE="Group mapping HOWTO"
HREF="groupmapping.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="speed.html"
HREF="samba-ldap-howto.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="bugreport.html"
HREF="groupmapping.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,15 +74,15 @@ CLASS="CHAPTER"
><A
NAME="CVS-ACCESS"
></A
>Chapter 18. HOWTO Access Samba source code via CVS</H1
>Chapter 21. HOWTO Access Samba source code via CVS</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2873"
NAME="AEN2974"
></A
>18.1. Introduction</H1
>21.1. Introduction</H1
><P
>Samba is developed in an open environment. Developers use CVS
(Concurrent Versioning System) to "checkin" (also known as
@ -99,9 +102,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2878"
NAME="AEN2979"
></A
>18.2. CVS Access to samba.org</H1
>21.2. CVS Access to samba.org</H1
><P
>The machine samba.org runs a publicly accessible CVS
repository for access to the source code of several packages,
@ -112,9 +115,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2881"
NAME="AEN2982"
></A
>18.2.1. Access via CVSweb</H2
>21.2.1. Access via CVSweb</H2
><P
>You can access the source code via your
favourite WWW browser. This allows you to access the contents of
@ -133,9 +136,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2886"
NAME="AEN2987"
></A
>18.2.2. Access via cvs</H2
>21.2.2. Access via cvs</H2
><P
>You can also access the source code via a
normal cvs client. This gives you much more control over you can
@ -253,7 +256,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="speed.html"
HREF="samba-ldap-howto.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -271,7 +274,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="bugreport.html"
HREF="groupmapping.html"
ACCESSKEY="N"
>Next</A
></TD
@ -281,17 +284,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Samba performance issues</TD
>Storing Samba's User/Machine Account information in an LDAP Directory</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="optional.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Reporting Bugs</TD
>Group mapping HOWTO</TD
></TR
></TABLE
></DIV

102
docs/htmldocs/diagnosis.html
View File

@ -9,9 +9,12 @@ CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
REL="UP"
TITLE="Appendixes"
HREF="appendixes.html"><LINK
REL="PREVIOUS"
TITLE="Samba and other CIFS clients"
HREF="other-clients.html"></HEAD
TITLE="Reporting Bugs"
HREF="bugreport.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -39,7 +42,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="other-clients.html"
HREF="bugreport.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -64,47 +67,44 @@ CLASS="CHAPTER"
><A
NAME="DIAGNOSIS"
></A
>Chapter 23. Diagnosing your samba server</H1
>Chapter 27. Diagnosing your samba server</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3184"
NAME="AEN3437"
></A
>23.1. Introduction</H1
>27.1. Introduction</H1
><P
>This file contains a list of tests you can perform to validate your
Samba server. It also tells you what the likely cause of the problem
is if it fails any one of these steps. If it passes all these tests
then it is probably working fine.</P
><P
>You should do ALL the tests, in the order shown. I have tried to
>You should do ALL the tests, in the order shown. We have tried to
carefully choose them so later tests only use capabilities verified in
the earlier tests.</P
><P
>If you send me an email saying "it doesn't work" and you have not
followed this test procedure then you should not be surprised if I
ignore your email.</P
>If you send one of the samba mailing lists an email saying "it doesn't work"
and you have not followed this test procedure then you should not be surprised
your email is ignored.</P
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3189"
NAME="AEN3442"
></A
>23.2. Assumptions</H1
>27.2. Assumptions</H1
><P
>In all of the tests I assume you have a Samba server called BIGSERVER
and a PC called ACLIENT both in workgroup TESTGROUP. I also assume the
PC is running windows for workgroups with a recent copy of the
microsoft tcp/ip stack. Alternatively, your PC may be running Windows
95 or Windows NT (Workstation or Server).</P
>In all of the tests it is assumed you have a Samba server called
BIGSERVER and a PC called ACLIENT both in workgroup TESTGROUP.</P
><P
>The procedure is similar for other types of clients.</P
><P
>I also assume you know the name of an available share in your
>It is also assumed you know the name of an available share in your
smb.conf. I will assume this share is called "tmp". You can add a
"tmp" share like by adding the following to smb.conf:</P
><P
@ -116,7 +116,7 @@ CLASS="PROGRAMLISTING"
read only = yes&#13;</PRE
></P
><P
>THESE TESTS ASSUME VERSION 2.0.6 OR LATER OF THE SAMBA SUITE. SOME
>THESE TESTS ASSUME VERSION 3.0.0 OR LATER OF THE SAMBA SUITE. SOME
COMMANDS SHOWN DID NOT EXIST IN EARLIER VERSIONS</P
><P
>Please pay attention to the error messages you receive. If any error message
@ -133,17 +133,17 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3199"
NAME="AEN3452"
></A
>23.3. Tests</H1
>27.3. Tests</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3201"
NAME="AEN3454"
></A
>23.3.1. Test 1</H2
>27.3.1. Test 1</H2
><P
>In the directory in which you store your smb.conf file, run the command
"testparm smb.conf". If it reports any errors then your smb.conf
@ -151,7 +151,7 @@ configuration file is faulty.</P
><P
>Note: Your smb.conf file may be located in: <TT
CLASS="FILENAME"
>/etc</TT
>/etc/samba</TT
>
Or in: <TT
CLASS="FILENAME"
@ -163,9 +163,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3207"
NAME="AEN3460"
></A
>23.3.2. Test 2</H2
>27.3.2. Test 2</H2
><P
>Run the command "ping BIGSERVER" from the PC and "ping ACLIENT" from
the unix box. If you don't get a valid response then your TCP/IP
@ -189,9 +189,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3213"
NAME="AEN3466"
></A
>23.3.3. Test 3</H2
>27.3.3. Test 3</H2
><P
>Run the command "smbclient -L BIGSERVER" on the unix box. You
should get a list of available shares back. </P
@ -260,9 +260,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3228"
NAME="AEN3481"
></A
>23.3.4. Test 4</H2
>27.3.4. Test 4</H2
><P
>Run the command "nmblookup -B BIGSERVER __SAMBA__". You should get the
IP address of your Samba server back.</P
@ -281,9 +281,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3233"
NAME="AEN3486"
></A
>23.3.5. Test 5</H2
>27.3.5. Test 5</H2
><P
>run the command <B
CLASS="COMMAND"
@ -302,9 +302,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3239"
NAME="AEN3492"
></A
>23.3.6. Test 6</H2
>27.3.6. Test 6</H2
><P
>Run the command <B
CLASS="COMMAND"
@ -336,9 +336,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3247"
NAME="AEN3500"
></A
>23.3.7. Test 7</H2
>27.3.7. Test 7</H2
><P
>Run the command <B
CLASS="COMMAND"
@ -425,9 +425,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3273"
NAME="AEN3526"
></A
>23.3.8. Test 8</H2
>27.3.8. Test 8</H2
><P
>On the PC type the command <B
CLASS="COMMAND"
@ -485,9 +485,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3290"
NAME="AEN3543"
></A
>23.3.9. Test 9</H2
>27.3.9. Test 9</H2
><P
>Run the command <B
CLASS="COMMAND"
@ -519,9 +519,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3298"
NAME="AEN3551"
></A
>23.3.10. Test 10</H2
>27.3.10. Test 10</H2
><P
>Run the command <B
CLASS="COMMAND"
@ -545,9 +545,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3304"
NAME="AEN3557"
></A
>23.3.11. Test 11</H2
>27.3.11. Test 11</H2
><P
>From file manager try to browse the server. Your samba server should
appear in the browse list of your local workgroup (or the one you
@ -573,9 +573,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3309"
NAME="AEN3562"
></A
>23.4. Still having troubles?</H1
>27.4. Still having troubles?</H1
><P
>Try the mailing list or newsgroup, or use the ethereal utility to
sniff the problem. The official samba mailing list can be reached at
@ -611,7 +611,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="other-clients.html"
HREF="bugreport.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -635,12 +635,16 @@ VALIGN="top"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Samba and other CIFS clients</TD
>Reporting Bugs</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="appendixes.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"

47
docs/htmldocs/domain-security.html
View File

@ -2,19 +2,22 @@
<HTML
><HEAD
><TITLE
>security = domain in Samba 2.x</TITLE
>Samba as a NT4 domain member</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><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="Security levels"
HREF="securitylevels.html"><LINK
TITLE="Samba as a ADS domain member"
HREF="ads.html"><LINK
REL="NEXT"
TITLE="Unified Logons between Windows NT and UNIX using Winbind"
HREF="winbind.html"></HEAD
TITLE="Optional configuration"
HREF="optional.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="securitylevels.html"
HREF="ads.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="winbind.html"
HREF="optional.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,15 +74,15 @@ CLASS="CHAPTER"
><A
NAME="DOMAIN-SECURITY"
></A
>Chapter 9. security = domain in Samba 2.x</H1
>Chapter 10. Samba as a NT4 domain member</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1133"
NAME="AEN1286"
></A
>9.1. Joining an NT Domain with Samba 2.2</H1
>10.1. Joining an NT Domain with Samba 2.2</H1
><P
>Assume you have a Samba 2.x server with a NetBIOS name of
<TT
@ -308,12 +311,12 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1197"
NAME="AEN1350"
></A
>9.2. Samba and Windows 2000 Domains</H1
>10.2. Samba and Windows 2000 Domains</H1
><P
>Many people have asked regarding the state of Samba's ability to participate in
a Windows 2000 Domain. Samba 2.2 is able to act as a member server of a Windows
a Windows 2000 Domain. Samba 3.0 is able to act as a member server of a Windows
2000 domain operating in mixed or native mode.</P
><P
>There is much confusion between the circumstances that require a "mixed" mode
@ -333,9 +336,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1202"
NAME="AEN1355"
></A
>9.3. Why is this better than security = server?</H1
>10.3. Why is this better than security = server?</H1
><P
>Currently, domain security in Samba doesn't free you from
having to create local Unix users to represent the users attaching
@ -435,7 +438,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="securitylevels.html"
HREF="ads.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -453,7 +456,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="winbind.html"
HREF="optional.html"
ACCESSKEY="N"
>Next</A
></TD
@ -463,17 +466,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Security levels</TD
>Samba as a ADS domain member</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="type.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Unified Logons between Windows NT and UNIX using Winbind</TD
>Optional configuration</TD
></TR
></TABLE
></DIV

2
docs/htmldocs/findsmb.1.html
View File

@ -193,7 +193,7 @@ NAME="AEN48"
><H2
>VERSION</H2
><P
>This man page is correct for version 2.2 of
>This man page is correct for version 3.0 of
the Samba suite.</P
></DIV
><DIV

31
docs/htmldocs/groupmapping.html
View File

@ -9,12 +9,15 @@ CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
REL="UP"
TITLE="Optional configuration"
HREF="optional.html"><LINK
REL="PREVIOUS"
TITLE="Reporting Bugs"
HREF="bugreport.html"><LINK
TITLE="HOWTO Access Samba source code via CVS"
HREF="cvs-access.html"><LINK
REL="NEXT"
TITLE="Portability"
HREF="portability.html"></HEAD
TITLE="Samba performance issues"
HREF="speed.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="bugreport.html"
HREF="cvs-access.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="portability.html"
HREF="speed.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,7 +74,7 @@ CLASS="CHAPTER"
><A
NAME="GROUPMAPPING"
></A
>Chapter 20. Group mapping HOWTO</H1
>Chapter 22. Group mapping HOWTO</H1
><P
>
Starting with Samba 3.0 alpha 2, a new group mapping function is available. The
@ -182,7 +185,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="bugreport.html"
HREF="cvs-access.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -200,7 +203,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="portability.html"
HREF="speed.html"
ACCESSKEY="N"
>Next</A
></TD
@ -210,17 +213,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Reporting Bugs</TD
>HOWTO Access Samba source code via CVS</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="optional.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Portability</TD
>Samba performance issues</TD
></TR
></TABLE
></DIV

83
docs/htmldocs/improved-browsing.html
View File

@ -9,12 +9,15 @@ CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><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="Using samba 3.0 with ActiveDirectory support"
HREF="ads.html"><LINK
TITLE="How to Install and Test SAMBA"
HREF="install.html"><LINK
REL="NEXT"
TITLE="Quick Cross Subnet Browsing / Cross Workgroup Browsing guide"
HREF="browsing-quick.html"></HEAD
TITLE="Oplocks"
HREF="oplocks.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="ads.html"
HREF="install.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="browsing-quick.html"
HREF="oplocks.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,15 +74,15 @@ CLASS="CHAPTER"
><A
NAME="IMPROVED-BROWSING"
></A
>Chapter 15. Improved browsing in samba</H1
>Chapter 2. Improved browsing in samba</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2517"
NAME="AEN229"
></A
>15.1. Overview of browsing</H1
>2.1. Overview of browsing</H1
><P
>SMB networking provides a mechanism by which clients can access a list
of machines in a network, a so-called "browse list". This list
@ -101,9 +104,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2521"
NAME="AEN233"
></A
>15.2. Browsing support in samba</H1
>2.2. Browsing support in samba</H1
><P
>Samba now fully supports browsing. The browsing is supported by nmbd
and is also controlled by options in the smb.conf file (see smb.conf(5)).</P
@ -146,9 +149,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2530"
NAME="AEN242"
></A
>15.3. Problem resolution</H1
>2.3. Problem resolution</H1
><P
>If something doesn't work then hopefully the log.nmb file will help
you track down the problem. Try a debug level of 2 or 3 for finding
@ -180,9 +183,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2537"
NAME="AEN249"
></A
>15.4. Browsing across subnets</H1
>2.4. Browsing across subnets</H1
><P
>With the release of Samba 1.9.17(alpha1 and above) Samba has been
updated to enable it to support the replication of browse lists
@ -211,9 +214,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2542"
NAME="AEN254"
></A
>15.4.1. How does cross subnet browsing work ?</H2
>2.4.1. How does cross subnet browsing work ?</H2
><P
>Cross subnet browsing is a complicated dance, containing multiple
moving parts. It has taken Microsoft several years to get the code
@ -423,9 +426,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2577"
NAME="AEN289"
></A
>15.5. Setting up a WINS server</H1
>2.5. Setting up a WINS server</H1
><P
>Either a Samba machine or a Windows NT Server machine may be set up
as a WINS server. To set a Samba machine to be a WINS server you must
@ -477,7 +480,7 @@ all smb.conf files :</P
><P
><B
CLASS="COMMAND"
> wins server = &gt;name or IP address&lt;</B
>wins server = &gt;name or IP address&lt;</B
></P
><P
>where &gt;name or IP address&lt; is either the DNS name of the WINS server
@ -506,9 +509,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2596"
NAME="AEN308"
></A
>15.6. Setting up Browsing in a WORKGROUP</H1
>2.6. Setting up Browsing in a WORKGROUP</H1
><P
>To set up cross subnet browsing on a network containing machines
in up to be in a WORKGROUP, not an NT Domain you need to set up one
@ -529,7 +532,7 @@ set the following option in the [global] section of the smb.conf file :</P
><P
><B
CLASS="COMMAND"
> domain master = yes</B
>domain master = yes</B
></P
><P
>The domain master browser should also preferrably be the local master
@ -590,9 +593,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2614"
NAME="AEN326"
></A
>15.7. Setting up Browsing in a DOMAIN</H1
>2.7. Setting up Browsing in a DOMAIN</H1
><P
>If you are adding Samba servers to a Windows NT Domain then
you must not set up a Samba server as a domain master browser.
@ -641,9 +644,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2624"
NAME="AEN336"
></A
>15.8. Forcing samba to be the master</H1
>2.8. Forcing samba to be the master</H1
><P
>Who becomes the "master browser" is determined by an election process
using broadcasts. Each election packet contains a number of parameters
@ -689,9 +692,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2633"
NAME="AEN345"
></A
>15.9. Making samba the domain master</H1
>2.9. Making samba the domain master</H1
><P
>The domain master is responsible for collating the browse lists of
multiple subnets so that browsing can occur between subnets. You can
@ -762,9 +765,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2651"
NAME="AEN363"
></A
>15.10. Note about broadcast addresses</H1
>2.10. Note about broadcast addresses</H1
><P
>If your network uses a "0" based broadcast address (for example if it
ends in a 0) then you will strike problems. Windows for Workgroups
@ -776,9 +779,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2654"
NAME="AEN366"
></A
>15.11. Multiple interfaces</H1
>2.11. Multiple interfaces</H1
><P
>Samba now supports machines with multiple network interfaces. If you
have multiple interfaces then you will need to use the "interfaces"
@ -801,7 +804,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="ads.html"
HREF="install.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -819,7 +822,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="browsing-quick.html"
HREF="oplocks.html"
ACCESSKEY="N"
>Next</A
></TD
@ -829,17 +832,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Using samba 3.0 with ActiveDirectory support</TD
>How to Install and Test SAMBA</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><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
>Oplocks</TD
></TR
></TABLE
></DIV

116
docs/htmldocs/install.html
View File

@ -9,12 +9,15 @@ CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><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="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
TITLE="General installation"
HREF="introduction.html"><LINK
REL="NEXT"
TITLE="Integrating MS Windows networks with Samba"
HREF="integrate-ms-networks.html"></HEAD
TITLE="Improved browsing in samba"
HREF="improved-browsing.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="samba-howto-collection.html"
HREF="introduction.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="integrate-ms-networks.html"
HREF="improved-browsing.html"
ACCESSKEY="N"
>Next</A
></TD
@ -77,9 +80,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN20"
NAME="AEN26"
></A
>1.1. Step 0: Read the man pages</H1
>1.1. Read the man pages</H1
><P
>The man pages distributed with SAMBA contain
lots of useful info that will help to get you started.
@ -92,10 +95,20 @@ CLASS="PROMPT"
><TT
CLASS="USERINPUT"
><B
>man smbd.8</B
></TT
>
or
<TT
CLASS="PROMPT"
>$ </TT
><TT
CLASS="USERINPUT"
><B
>nroff -man smbd.8 | more
</B
></TT
></P
> on older unixes.</P
><P
>Other sources of information are pointed to
by the Samba web site,<A
@ -109,9 +122,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN28"
NAME="AEN36"
></A
>1.2. Step 1: Building the Binaries</H1
>1.2. Building the Binaries</H1
><P
>To do this, first run the program <B
CLASS="COMMAND"
@ -208,9 +221,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN56"
NAME="AEN64"
></A
>1.3. Step 2: The all important step</H1
>1.3. The all important step</H1
><P
>At this stage you must fetch yourself a
coffee or other drink you find stimulating. Getting the rest
@ -225,9 +238,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN60"
NAME="AEN68"
></A
>1.4. Step 3: Create the smb configuration file.</H1
>1.4. Create the smb configuration file.</H1
><P
>There are sample configuration files in the examples
subdirectory in the distribution. I suggest you read them
@ -281,9 +294,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN74"
NAME="AEN82"
></A
>1.5. Step 4: Test your config file with
>1.5. Test your config file with
<B
CLASS="COMMAND"
>testparm</B
@ -299,15 +312,21 @@ CLASS="FILENAME"
><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
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN80"
NAME="AEN90"
></A
>1.6. Step 5: Starting the smbd and nmbd</H1
>1.6. Starting the smbd and nmbd</H1
><P
>You must choose to start smbd and nmbd either
as daemons or from <B
@ -345,9 +364,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN90"
NAME="AEN100"
></A
>1.6.1. Step 5a: Starting from inetd.conf</H2
>1.6.1. Starting from inetd.conf</H2
><P
>NOTE; The following will be different if
you use NIS or NIS+ to distributed services maps.</P
@ -449,9 +468,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN119"
NAME="AEN129"
></A
>1.6.2. Step 5b. Alternative: starting it as a daemon</H2
>1.6.2. Alternative: starting it as a daemon</H2
><P
>To start the server as a daemon you should create
a script something like this one, perhaps calling
@ -506,9 +525,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN135"
NAME="AEN145"
></A
>1.7. Step 6: Try listing the shares available on your
>1.7. Try listing the shares available on your
server</H1
><P
><TT
@ -547,9 +566,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN144"
NAME="AEN154"
></A
>1.8. Step 7: Try connecting with the unix client</H1
>1.8. Try connecting with the unix client</H1
><P
><TT
CLASS="PROMPT"
@ -610,9 +629,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN160"
NAME="AEN170"
></A
>1.9. Step 8: Try connecting from a DOS, WfWg, Win9x, WinNT,
>1.9. Try connecting from a DOS, WfWg, Win9x, WinNT,
Win2k, OS/2, etc... client</H1
><P
>Try mounting disks. eg:</P
@ -659,7 +678,7 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN174"
NAME="AEN184"
></A
>1.10. What If Things Don't Work?</H1
><P
@ -682,15 +701,16 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN179"
NAME="AEN189"
></A
>1.10.1. Diagnosing Problems</H2
><P
>If you have installation problems then go to
<TT
CLASS="FILENAME"
>DIAGNOSIS.txt</TT
> to try to find the
>If you have installation problems then go to the
<A
HREF="Diagnosis.html"
TARGET="_top"
>Diagnosis</A
> chapter to try to find the
problem.</P
></DIV
><DIV
@ -698,7 +718,7 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN183"
NAME="AEN193"
></A
>1.10.2. Scope IDs</H2
><P
@ -714,7 +734,7 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN186"
NAME="AEN196"
></A
>1.10.3. Choosing the Protocol Level</H2
><P
@ -755,7 +775,7 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN195"
NAME="AEN205"
></A
>1.10.4. Printing from UNIX to a Client PC</H2
><P
@ -776,7 +796,7 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN200"
NAME="AEN210"
></A
>1.10.5. Locking</H2
><P
@ -836,7 +856,7 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN209"
NAME="AEN219"
></A
>1.10.6. Mapping Usernames</H2
><P
@ -862,7 +882,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="samba-howto-collection.html"
HREF="introduction.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -880,7 +900,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="integrate-ms-networks.html"
HREF="improved-browsing.html"
ACCESSKEY="N"
>Next</A
></TD
@ -890,17 +910,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>SAMBA Project Documentation</TD
>General installation</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="introduction.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Integrating MS Windows networks with Samba</TD
>Improved browsing in samba</TD
></TR
></TABLE
></DIV

115
docs/htmldocs/integrate-ms-networks.html
View File

@ -9,13 +9,15 @@ CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
REL="UP"
TITLE="Optional configuration"
HREF="optional.html"><LINK
REL="PREVIOUS"
TITLE="How to Install and Test SAMBA"
HREF="install.html"><LINK
TITLE="Optional configuration"
HREF="optional.html"><LINK
REL="NEXT"
TITLE="Configuring PAM for distributed but centrally
managed authentication"
HREF="pam.html"></HEAD
TITLE="UNIX Permission Bits and Windows NT Access Control Lists"
HREF="unix-permissions.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -43,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="install.html"
HREF="optional.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -57,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="pam.html"
HREF="unix-permissions.html"
ACCESSKEY="N"
>Next</A
></TD
@ -72,15 +74,15 @@ CLASS="CHAPTER"
><A
NAME="INTEGRATE-MS-NETWORKS"
></A
>Chapter 2. Integrating MS Windows networks with Samba</H1
>Chapter 11. Integrating MS Windows networks with Samba</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN223"
NAME="AEN1387"
></A
>2.1. Agenda</H1
>11.1. Agenda</H1
><P
>To identify the key functional mechanisms of MS Windows networking
to enable the deployment of Samba as a means of extending and/or
@ -145,9 +147,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN245"
NAME="AEN1409"
></A
>2.2. Name Resolution in a pure Unix/Linux world</H1
>11.2. Name Resolution in a pure Unix/Linux world</H1
><P
>The key configuration files covered in this section are:</P
><P
@ -187,9 +189,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN261"
NAME="AEN1425"
></A
>2.2.1. <TT
>11.2.1. <TT
CLASS="FILENAME"
>/etc/hosts</TT
></H2
@ -268,9 +270,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN277"
NAME="AEN1441"
></A
>2.2.2. <TT
>11.2.2. <TT
CLASS="FILENAME"
>/etc/resolv.conf</TT
></H2
@ -306,9 +308,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN288"
NAME="AEN1452"
></A
>2.2.3. <TT
>11.2.3. <TT
CLASS="FILENAME"
>/etc/host.conf</TT
></H2
@ -335,9 +337,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN296"
NAME="AEN1460"
></A
>2.2.4. <TT
>11.2.4. <TT
CLASS="FILENAME"
>/etc/nsswitch.conf</TT
></H2
@ -376,7 +378,7 @@ facilities and/or services are correctly configured.</P
sent, TCP/IP networks are silent. All TCP/IP communications assumes a
principal of speaking only when necessary.</P
><P
>Samba version 2.2.0 will add Linux support for extensions to
>Starting with version 2.2.0 samba has Linux support for extensions to
the name service switch infrastructure so that linux clients will
be able to obtain resolution of MS Windows NetBIOS names to IP
Addresses. To gain this functionality Samba needs to be compiled
@ -404,9 +406,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN308"
NAME="AEN1472"
></A
>2.3. Name resolution as used within MS Windows networking</H1
>11.3. Name resolution as used within MS Windows networking</H1
><P
>MS Windows networking is predicated about the name each machine
is given. This name is known variously (and inconsistently) as
@ -489,9 +491,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN320"
NAME="AEN1484"
></A
>2.3.1. The NetBIOS Name Cache</H2
>11.3.1. The NetBIOS Name Cache</H2
><P
>All MS Windows machines employ an in memory buffer in which is
stored the NetBIOS names and IP addresses for all external
@ -516,9 +518,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN325"
NAME="AEN1489"
></A
>2.3.2. The LMHOSTS file</H2
>11.3.2. The LMHOSTS file</H2
><P
>This file is usually located in MS Windows NT 4.0 or
2000 in <TT
@ -619,9 +621,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN333"
NAME="AEN1497"
></A
>2.3.3. HOSTS file</H2
>11.3.3. HOSTS file</H2
><P
>This file is usually located in MS Windows NT 4.0 or 2000 in
<TT
@ -641,9 +643,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN338"
NAME="AEN1502"
></A
>2.3.4. DNS Lookup</H2
>11.3.4. DNS Lookup</H2
><P
>This capability is configured in the TCP/IP setup area in the network
configuration facility. If enabled an elaborate name resolution sequence
@ -661,9 +663,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN341"
NAME="AEN1505"
></A
>2.3.5. WINS Lookup</H2
>11.3.5. WINS Lookup</H2
><P
>A WINS (Windows Internet Name Server) service is the equivaent of the
rfc1001/1002 specified NBNS (NetBIOS Name Server). A WINS server stores
@ -704,9 +706,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN353"
NAME="AEN1517"
></A
>2.4. How browsing functions and how to deploy stable and
>11.4. How browsing functions and how to deploy stable and
dependable browsing using Samba</H1
><P
>As stated above, MS Windows machines register their NetBIOS names
@ -771,9 +773,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN363"
NAME="AEN1527"
></A
>2.5. MS Windows security options and how to configure
>11.5. MS Windows security options and how to configure
Samba for seemless integration</H1
><P
>MS Windows clients may use encrypted passwords as part of a
@ -908,9 +910,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN391"
NAME="AEN1555"
></A
>2.5.1. Use MS Windows NT as an authentication server</H2
>11.5.1. Use MS Windows NT as an authentication server</H2
><P
>This method involves the additions of the following parameters
in the smb.conf file:</P
@ -944,9 +946,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN399"
NAME="AEN1563"
></A
>2.5.2. Make Samba a member of an MS Windows NT security domain</H2
>11.5.2. Make Samba a member of an MS Windows NT security domain</H2
><P
>This method involves additon of the following paramters in the smb.conf file:</P
><P
@ -1007,9 +1009,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN416"
NAME="AEN1580"
></A
>2.5.3. Configure Samba as an authentication server</H2
>11.5.3. Configure Samba as an authentication server</H2
><P
>This mode of authentication demands that there be on the
Unix/Linux system both a Unix style account as well as an
@ -1044,9 +1046,9 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN423"
NAME="AEN1587"
></A
>2.5.3.1. Users</H3
>11.5.3.1. Users</H3
><P
>A user account that may provide a home directory should be
created. The following Linux system commands are typical of
@ -1067,9 +1069,9 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN428"
NAME="AEN1592"
></A
>2.5.3.2. MS Windows NT Machine Accounts</H3
>11.5.3.2. MS Windows NT Machine Accounts</H3
><P
>These are required only when Samba is used as a domain
controller. Refer to the Samba-PDC-HOWTO for more details.</P
@ -1088,9 +1090,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN433"
NAME="AEN1597"
></A
>2.6. Conclusions</H1
>11.6. Conclusions</H1
><P
>Samba provides a flexible means to operate as...</P
><P
@ -1136,7 +1138,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="install.html"
HREF="optional.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -1154,7 +1156,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="pam.html"
HREF="unix-permissions.html"
ACCESSKEY="N"
>Next</A
></TD
@ -1164,18 +1166,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>How to Install and Test SAMBA</TD
>Optional configuration</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="optional.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Configuring PAM for distributed but centrally
managed authentication</TD
>UNIX Permission Bits and Windows NT Access Control Lists</TD
></TR
></TABLE
></DIV

29
docs/htmldocs/msdfs.html
View File

@ -9,13 +9,16 @@ CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
REL="UP"
TITLE="Optional configuration"
HREF="optional.html"><LINK
REL="PREVIOUS"
TITLE="Configuring PAM for distributed but centrally
managed authentication"
HREF="pam.html"><LINK
REL="NEXT"
TITLE="UNIX Permission Bits and Windows NT Access Control Lists"
HREF="unix-permissions.html"></HEAD
TITLE="Printing Support"
HREF="printing.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -57,7 +60,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="unix-permissions.html"
HREF="printing.html"
ACCESSKEY="N"
>Next</A
></TD
@ -72,15 +75,15 @@ CLASS="CHAPTER"
><A
NAME="MSDFS"
></A
>Chapter 4. Hosting a Microsoft Distributed File System tree on Samba</H1
>Chapter 14. Hosting a Microsoft Distributed File System tree on Samba</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN525"
NAME="AEN1872"
></A
>4.1. Instructions</H1
>14.1. Instructions</H1
><P
>The Distributed File System (or Dfs) provides a means of
separating the logical view of files and directories that users
@ -226,9 +229,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN560"
NAME="AEN1907"
></A
>4.1.1. Notes</H2
>14.1.1. Notes</H2
><P
></P
><UL
@ -289,7 +292,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="unix-permissions.html"
HREF="printing.html"
ACCESSKEY="N"
>Next</A
></TD
@ -305,12 +308,16 @@ managed authentication</TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="optional.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>UNIX Permission Bits and Windows NT Access Control Lists</TD
>Printing Support</TD
></TR
></TABLE
></DIV

25
docs/htmldocs/nmblookup.1.html
View File

@ -38,12 +38,12 @@ NAME="AEN8"
><B
CLASS="COMMAND"
>nmblookup</B
> [-M] [-R] [-S] [-r] [-A] [-h] [-B &lt;broadcast address&gt;] [-U &lt;unicast address&gt;] [-d &lt;debug level&gt;] [-s &lt;smb config file&gt;] [-i &lt;NetBIOS scope&gt;] [-T] {name}</P
> [-M] [-R] [-S] [-r] [-A] [-h] [-B &lt;broadcast address&gt;] [-U &lt;unicast address&gt;] [-d &lt;debug level&gt;] [-s &lt;smb config file&gt;] [-i &lt;NetBIOS scope&gt;] [-T] [-f] {name}</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN24"
NAME="AEN25"
></A
><H2
>DESCRIPTION</H2
@ -66,7 +66,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN30"
NAME="AEN31"
></A
><H2
>OPTIONS</H2
@ -286,6 +286,15 @@ CLASS="EMPHASIS"
> 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
answers are zero or more of: Response, Authoritative,
Truncated, Recursion_Desired, Recursion_Available, Broadcast.
</P
></DD
><DT
>name</DT
><DD
><P
@ -302,7 +311,7 @@ CLASS="EMPHASIS"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN110"
NAME="AEN115"
></A
><H2
>EXAMPLES</H2
@ -339,18 +348,18 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN122"
NAME="AEN127"
></A
><H2
>VERSION</H2
><P
>This man page is correct for version 2.2 of
>This man page is correct for version 3.0 of
the Samba suite.</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN125"
NAME="AEN130"
></A
><H2
>SEE ALSO</H2
@ -377,7 +386,7 @@ TARGET="_top"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN132"
NAME="AEN137"
></A
><H2
>AUTHOR</H2

73
docs/htmldocs/other-clients.html
View File

@ -9,12 +9,15 @@ CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
REL="UP"
TITLE="Appendixes"
HREF="appendixes.html"><LINK
REL="PREVIOUS"
TITLE="Portability"
HREF="portability.html"><LINK
REL="NEXT"
TITLE="Diagnosing your samba server"
HREF="diagnosis.html"></HEAD
TITLE="Reporting Bugs"
HREF="bugreport.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="diagnosis.html"
HREF="bugreport.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,7 +74,7 @@ CLASS="CHAPTER"
><A
NAME="OTHER-CLIENTS"
></A
>Chapter 22. Samba and other CIFS clients</H1
>Chapter 25. Samba and other CIFS clients</H1
><P
>This chapter contains client-specific information.</P
><DIV
@ -79,9 +82,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3070"
NAME="AEN3258"
></A
>22.1. Macintosh clients?</H1
>25.1. Macintosh clients?</H1
><P
>Yes. <A
HREF="http://www.thursby.com/"
@ -125,17 +128,17 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3079"
NAME="AEN3267"
></A
>22.2. OS2 Client</H1
>25.2. OS2 Client</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3081"
NAME="AEN3269"
></A
>22.2.1. How can I configure OS/2 Warp Connect or
>25.2.1. How can I configure OS/2 Warp Connect or
OS/2 Warp 4 as a client for Samba?</H2
><P
>A more complete answer to this question can be
@ -192,9 +195,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3096"
NAME="AEN3284"
></A
>22.2.2. How can I configure OS/2 Warp 3 (not Connect),
>25.2.2. How can I configure OS/2 Warp 3 (not Connect),
OS/2 1.2, 1.3 or 2.x for Samba?</H2
><P
>You can use the free Microsoft LAN Manager 2.2c Client
@ -236,9 +239,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3105"
NAME="AEN3293"
></A
>22.2.3. Are there any other issues when OS/2 (any version)
>25.2.3. Are there any other issues when OS/2 (any version)
is used as a client?</H2
><P
>When you do a NET VIEW or use the "File and Print
@ -258,9 +261,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3109"
NAME="AEN3297"
></A
>22.2.4. How do I get printer driver download working
>25.2.4. How do I get printer driver download working
for OS/2 clients?</H2
><P
>First, create a share called [PRINTDRV] that is
@ -309,17 +312,17 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3119"
NAME="AEN3307"
></A
>22.3. Windows for Workgroups</H1
>25.3. Windows for Workgroups</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3121"
NAME="AEN3309"
></A
>22.3.1. Use latest TCP/IP stack from Microsoft</H2
>25.3.1. Use latest TCP/IP stack from Microsoft</H2
><P
>Use the latest TCP/IP stack from microsoft if you use Windows
for workgroups.</P
@ -339,9 +342,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3126"
NAME="AEN3314"
></A
>22.3.2. Delete .pwl files after password change</H2
>25.3.2. Delete .pwl files after password change</H2
><P
>WfWg does a lousy job with passwords. I find that if I change my
password on either the unix box or the PC the safest thing to do is to
@ -359,9 +362,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3131"
NAME="AEN3319"
></A
>22.3.3. Configure WfW password handling</H2
>25.3.3. Configure WfW password handling</H2
><P
>There is a program call admincfg.exe
on the last disk (disk 8) of the WFW 3.11 disk set. To install it
@ -378,9 +381,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN3135"
NAME="AEN3323"
></A
>22.3.4. Case handling of passwords</H2
>25.3.4. Case handling of passwords</H2
><P
>Windows for Workgroups uppercases the password before sending it to the server. Unix passwords can be case-sensitive though. Check the <A
HREF="smb.conf.5.html"
@ -397,9 +400,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3140"
NAME="AEN3328"
></A
>22.4. Windows '95/'98</H1
>25.4. Windows '95/'98</H1
><P
>When using Windows 95 OEM SR2 the following updates are recommended where Samba
is being used. Please NOTE that the above change will affect you once these
@ -445,9 +448,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3156"
NAME="AEN3344"
></A
>22.5. Windows 2000 Service Pack 2</H1
>25.5. Windows 2000 Service Pack 2</H1
><P
>
There are several annoyances with Windows 2000 SP2. One of which
@ -557,7 +560,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="diagnosis.html"
HREF="bugreport.html"
ACCESSKEY="N"
>Next</A
></TD
@ -572,12 +575,16 @@ VALIGN="top"
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="appendixes.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Diagnosing your samba server</TD
>Reporting Bugs</TD
></TR
></TABLE
></DIV

33
docs/htmldocs/pam.html
View File

@ -10,9 +10,12 @@ CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
REL="UP"
TITLE="Optional configuration"
HREF="optional.html"><LINK
REL="PREVIOUS"
TITLE="Integrating MS Windows networks with Samba"
HREF="integrate-ms-networks.html"><LINK
TITLE="UNIX Permission Bits and Windows NT Access Control Lists"
HREF="unix-permissions.html"><LINK
REL="NEXT"
TITLE="Hosting a Microsoft Distributed File System tree on Samba"
HREF="msdfs.html"></HEAD
@ -43,7 +46,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="integrate-ms-networks.html"
HREF="unix-permissions.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -72,16 +75,16 @@ CLASS="CHAPTER"
><A
NAME="PAM"
></A
>Chapter 3. Configuring PAM for distributed but centrally
>Chapter 13. Configuring PAM for distributed but centrally
managed authentication</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN454"
NAME="AEN1801"
></A
>3.1. Samba and PAM</H1
>13.1. Samba and PAM</H1
><P
>A number of Unix systems (eg: Sun Solaris), as well as the
xxxxBSD family and Linux, now utilize the Pluggable Authentication
@ -293,9 +296,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN498"
NAME="AEN1845"
></A
>3.2. Distributed Authentication</H1
>13.2. Distributed Authentication</H1
><P
>The astute administrator will realize from this that the
combination of <TT
@ -326,9 +329,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN505"
NAME="AEN1852"
></A
>3.3. PAM Configuration in smb.conf</H1
>13.3. PAM Configuration in smb.conf</H1
><P
>There is an option in smb.conf called <A
HREF="smb.conf.5.html#OBEYPAMRESTRICTIONS"
@ -378,7 +381,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="integrate-ms-networks.html"
HREF="unix-permissions.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -406,12 +409,16 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Integrating MS Windows networks with Samba</TD
>UNIX Permission Bits and Windows NT Access Control Lists</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="optional.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"

75
docs/htmldocs/pdbedit.8.html
View File

@ -444,13 +444,80 @@ CLASS="PROGRAMLISTING"
></TABLE
></P
></DD
><DT
>-d|--debug=debuglevel</DT
><DD
><P
><TT
CLASS="REPLACEABLE"
><I
>debuglevel</I
></TT
> 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 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
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
>-h|--help</DT
><DD
><P
>Print a summary of command line options.</P
></DD
><DT
>-s &#60;configuration file&#62;</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.
The default configuration file name is determined at
compile time.</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN161"
NAME="AEN182"
></A
><H2
>NOTES</H2
@ -460,7 +527,7 @@ NAME="AEN161"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN164"
NAME="AEN185"
></A
><H2
>VERSION</H2
@ -471,7 +538,7 @@ NAME="AEN164"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN167"
NAME="AEN188"
></A
><H2
>SEE ALSO</H2
@ -491,7 +558,7 @@ TARGET="_top"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN172"
NAME="AEN193"
></A
><H2
>AUTHOR</H2

41
docs/htmldocs/portability.html
View File

@ -9,9 +9,12 @@ CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
REL="UP"
TITLE="Appendixes"
HREF="appendixes.html"><LINK
REL="PREVIOUS"
TITLE="Group mapping HOWTO"
HREF="groupmapping.html"><LINK
TITLE="Appendixes"
HREF="appendixes.html"><LINK
REL="NEXT"
TITLE="Samba and other CIFS clients"
HREF="other-clients.html"></HEAD
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="groupmapping.html"
HREF="appendixes.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -71,7 +74,7 @@ CLASS="CHAPTER"
><A
NAME="PORTABILITY"
></A
>Chapter 21. Portability</H1
>Chapter 24. Portability</H1
><P
>Samba works on a wide range of platforms but the interface all the
platforms provide is not always compatible. This chapter contains
@ -81,9 +84,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3011"
NAME="AEN3198"
></A
>21.1. HPUX</H1
>24.1. HPUX</H1
><P
>HP's implementation of supplementary groups is, er, non-standard (for
hysterical reasons). There are two group files, /etc/group and
@ -101,15 +104,19 @@ to initgroups() be run as users not in any groups with GIDs outside the
allowed range.</P
><P
>This is documented in the HP manual pages under setgroups(2) and passwd(4).</P
><P
>On HPUX you must use gcc or the HP Ansi compiler. The free compiler
that comes with HP-UX is not Ansi compliant and cannot compile
Samba.</P
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3016"
NAME="AEN3204"
></A
>21.2. SCO Unix</H1
>24.2. SCO Unix</H1
><P
>
If you run an old version of SCO Unix then you may need to get important
@ -124,9 +131,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3020"
NAME="AEN3208"
></A
>21.3. DNIX</H1
>24.3. DNIX</H1
><P
>DNIX has a problem with seteuid() and setegid(). These routines are
needed for Samba to work correctly, but they were left out of the DNIX
@ -231,9 +238,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3049"
NAME="AEN3237"
></A
>21.4. RedHat Linux Rembrandt-II</H1
>24.4. RedHat Linux Rembrandt-II</H1
><P
>By default RedHat Rembrandt-II during installation adds an
entry to /etc/hosts as follows:
@ -267,7 +274,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="groupmapping.html"
HREF="appendixes.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -295,12 +302,16 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Group mapping HOWTO</TD
>Appendixes</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="appendixes.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"

634
docs/htmldocs/printing.html
View File

@ -2,19 +2,22 @@
<HTML
><HEAD
><TITLE
>Printing Support in Samba 2.2.x</TITLE
>Printing Support</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
REL="UP"
TITLE="Optional configuration"
HREF="optional.html"><LINK
REL="PREVIOUS"
TITLE="UNIX Permission Bits and Windows NT Access Control Lists"
HREF="unix-permissions.html"><LINK
TITLE="Hosting a Microsoft Distributed File System tree on Samba"
HREF="msdfs.html"><LINK
REL="NEXT"
TITLE="Debugging Printing Problems"
HREF="printingdebug.html"></HEAD
TITLE="Unified Logons between Windows NT and UNIX using Winbind"
HREF="winbind.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="unix-permissions.html"
HREF="msdfs.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="printingdebug.html"
HREF="winbind.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,15 +74,15 @@ CLASS="CHAPTER"
><A
NAME="PRINTING"
></A
>Chapter 6. Printing Support in Samba 2.2.x</H1
>Chapter 15. Printing Support</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN763"
NAME="AEN1933"
></A
>6.1. Introduction</H1
>15.1. Introduction</H1
><P
>Beginning with the 2.2.0 release, Samba supports
the native Windows NT printing mechanisms implemented via
@ -136,12 +139,7 @@ TARGET="_top"
>There has been some initial confusion about what all this means
and whether or not it is a requirement for printer drivers to be
installed on a Samba host in order to support printing from Windows
clients. A bug existed in Samba 2.2.0 which made Windows NT/2000 clients
require that the Samba server possess a valid driver for the printer.
This is fixed in Samba 2.2.1 and once again, Windows NT/2000 clients
can use the local APW for installing drivers to be used with a Samba
served printer. This is the same behavior exhibited by Windows 9x clients.
As a side note, Samba does not use these drivers in any way to process
clients. As a side note, Samba does not use these drivers in any way to process
spooled files. They are utilized entirely by the clients.</P
><P
>The following MS KB article, may be of some help if you are dealing with
@ -165,9 +163,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN785"
NAME="AEN1955"
></A
>6.2. Configuration</H1
>15.2. Configuration</H1
><DIV
CLASS="WARNING"
><P
@ -222,20 +220,6 @@ CLASS="PARAMETER"
> provided
a means of defining the printer driver name to be sent to
the client.</P
><P
>These parameters, including <TT
CLASS="PARAMETER"
><I
>printer driver
file</I
></TT
> parameter, are being deprecated and should not
be used in new installations. For more information on this change,
you should refer to the <A
HREF="printing.html#MIGRATION"
>Migration section</A
>
of this document.</P
></TD
></TR
></TABLE
@ -245,9 +229,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN796"
NAME="AEN1963"
></A
>6.2.1. Creating [print$]</H2
>15.2.1. Creating [print$]</H2
><P
>In order to support the uploading of printer driver
files, you must first configure a file share named [print$].
@ -468,22 +452,14 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN831"
NAME="AEN1998"
></A
>6.2.2. Setting Drivers for Existing Printers</H2
>15.2.2. Setting Drivers for Existing Printers</H2
><P
>The initial listing of printers in the Samba host's
Printers folder will have no real printer driver assigned
to them. By default, in Samba 2.2.0 this driver name was set to
<SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>NO PRINTER DRIVER AVAILABLE FOR THIS PRINTER</I
></SPAN
>.
Later versions changed this to a NULL string to allow the use
tof the local Add Printer Wizard on NT/2000 clients.
to them. This defaults to a NULL string to allow the use
of the local Add Printer Wizard on NT/2000 clients.
Attempting to view the printer properties for a printer
which has this default driver assigned will result in
the error message:</P
@ -548,9 +524,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN848"
NAME="AEN2014"
></A
>6.2.3. Support a large number of printers</H2
>15.2.3. Support a large number of printers</H2
><P
>One issue that has arisen during the development
phase of Samba 2.2 is the need to support driver downloads for
@ -614,9 +590,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN859"
NAME="AEN2025"
></A
>6.2.4. Adding New Printers via the Windows NT APW</H2
>15.2.4. Adding New Printers via the Windows NT APW</H2
><P
>By default, Samba offers all printer shares defined in <TT
CLASS="FILENAME"
@ -783,9 +759,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN889"
NAME="AEN2055"
></A
>6.2.5. Samba and Printer Ports</H2
>15.2.5. Samba and Printer Ports</H2
><P
>Windows NT/2000 print servers associate a port with each printer. These normally
take the form of LPT1:, COM1:, FILE:, etc... Samba must also support the
@ -820,9 +796,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN897"
NAME="AEN2063"
></A
>6.3. The Imprints Toolset</H1
>15.3. The Imprints Toolset</H1
><P
>The Imprints tool set provides a UNIX equivalent of the
Windows NT Add Printer Wizard. For complete information, please
@ -838,9 +814,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN901"
NAME="AEN2067"
></A
>6.3.1. What is Imprints?</H2
>15.3.1. What is Imprints?</H2
><P
>Imprints is a collection of tools for supporting the goals
of</P
@ -870,9 +846,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN911"
NAME="AEN2077"
></A
>6.3.2. Creating Printer Driver Packages</H2
>15.3.2. Creating Printer Driver Packages</H2
><P
>The process of creating printer driver packages is beyond
the scope of this document (refer to Imprints.txt also included
@ -886,9 +862,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN914"
NAME="AEN2080"
></A
>6.3.3. The Imprints server</H2
>15.3.3. The Imprints server</H2
><P
>The Imprints server is really a database server that
may be queried via standard HTTP mechanisms. Each printer
@ -910,9 +886,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN918"
NAME="AEN2084"
></A
>6.3.4. The Installation Client</H2
>15.3.4. The Installation Client</H2
><P
>More information regarding the Imprints installation client
is available in the <TT
@ -1004,168 +980,388 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN940"
NAME="AEN2106"
></A
>6.4. <A
NAME="MIGRATION"
></A
>Migration to from Samba 2.0.x to 2.2.x</H1
><P
>Given that printer driver management has changed (we hope improved) in
2.2 over prior releases, migration from an existing setup to 2.2 can
follow several paths. Here are the possible scenarios for
migration:</P
><P
></P
><UL
><LI
><P
>If you do not desire the new Windows NT
print driver support, nothing needs to be done.
All existing parameters work the same.</P
></LI
><LI
><P
>If you want to take advantage of NT printer
driver support but do not want to migrate the
9x drivers to the new setup, the leave the existing
<TT
CLASS="FILENAME"
>printers.def</TT
> file. When smbd attempts
to locate a
9x driver for the printer in the TDB and fails it
will drop down to using the printers.def (and all
associated parameters). The <B
CLASS="COMMAND"
>make_printerdef</B
>
tool will also remain for backwards compatibility but will
be removed in the next major release.</P
></LI
><LI
><P
>If you install a Windows 9x driver for a printer
on your Samba host (in the printing TDB), this information will
take precedence and the three old printing parameters
will be ignored (including print driver location).</P
></LI
><LI
><P
>If you want to migrate an existing <TT
CLASS="FILENAME"
>printers.def</TT
>
file into the new setup, the current only solution is to use the Windows
NT APW to install the NT drivers and the 9x drivers. This can be scripted
using <B
CLASS="COMMAND"
>smbclient</B
> and <B
CLASS="COMMAND"
>rpcclient</B
>. See the
Imprints installation client at <A
HREF="http://imprints.sourceforge.net/"
TARGET="_top"
>http://imprints.sourceforge.net/</A
>
for an example.
</P
></LI
></UL
>15.4. Diagnosis</H1
><DIV
CLASS="WARNING"
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2108"
></A
>15.4.1. Introduction</H2
><P
>This is a short description of how to debug printing problems with
Samba. This describes how to debug problems with printing from a SMB
client to a Samba server, not the other way around. For the reverse
see the examples/printing directory.</P
><P
>Ok, so you want to print to a Samba server from your PC. The first
thing you need to understand is that Samba does not actually do any
printing itself, it just acts as a middleman between your PC client
and your Unix printing subsystem. Samba receives the file from the PC
then passes the file to a external "print command". What print command
you use is up to you.</P
><P
>The whole things is controlled using options in smb.conf. The most
relevant options (which you should look up in the smb.conf man page)
are:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> [global]
print command - send a file to a spooler
lpq command - get spool queue status
lprm command - remove a job
[printers]
path = /var/spool/lpd/samba</PRE
></P
><TABLE
CLASS="WARNING"
WIDTH="100%"
BORDER="0"
><TR
><TD
WIDTH="25"
ALIGN="CENTER"
VALIGN="TOP"
><IMG
SRC="/docbook-dsssl/warning.gif"
HSPACE="5"
ALT="Warning"></TD
><TH
ALIGN="LEFT"
VALIGN="CENTER"
><B
>Achtung!</B
></TH
></TR
><TR
><TD
>&nbsp;</TD
><TD
ALIGN="LEFT"
VALIGN="TOP"
><P
>The following <TT
CLASS="FILENAME"
>smb.conf</TT
> parameters are considered to
be deprecated and will be removed soon. Do not use them in new
installations</P
>The following are nice to know about:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> queuepause command - stop a printer or print queue
queueresume command - start a printer or print queue</PRE
></P
><UL
><LI
><P
><TT
CLASS="PARAMETER"
><I
>printer driver file (G)</I
></TT
>
</P
></LI
><LI
>Example:</P
><P
><TT
CLASS="PARAMETER"
><I
>printer driver (S)</I
></TT
>
</P
></LI
><LI
><PRE
CLASS="PROGRAMLISTING"
> print command = /usr/bin/lpr -r -P%p %s
lpq command = /usr/bin/lpq -P%p %s
lprm command = /usr/bin/lprm -P%p %j
queuepause command = /usr/sbin/lpc -P%p stop
queuepause command = /usr/sbin/lpc -P%p start</PRE
></P
><P
><TT
CLASS="PARAMETER"
><I
>printer driver location (S)</I
></TT
>
</P
></LI
></UL
></TD
></TR
></TABLE
>Samba should set reasonable defaults for these depending on your
system type, but it isn't clairvoyant. It is not uncommon that you
have to tweak these for local conditions. The commands should
always have fully specified pathnames, as the smdb may not have
the correct PATH values.</P
><P
>When you send a job to Samba to be printed, it will make a temporary
copy of it in the directory specified in the [printers] section.
and it should be periodically cleaned out. The lpr -r option
requests that the temporary copy be removed after printing; If
printing fails then you might find leftover files in this directory,
and it should be periodically cleaned out. Samba used the lpq
command to determine the "job number" assigned to your print job
by the spooler.</P
><P
>The %&gt;letter&lt; are "macros" that get dynamically replaced with appropriate
values when they are used. The %s gets replaced with the name of the spool
file that Samba creates and the %p gets replaced with the name of the
printer. The %j gets replaced with the "job number" which comes from
the lpq output.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2124"
></A
>15.4.2. Debugging printer problems</H2
><P
>The have been two new parameters add in Samba 2.2.2 to for
better support of Samba 2.0.x backwards capability (<TT
CLASS="PARAMETER"
><I
>disable
spoolss</I
></TT
>) and for using local printers drivers on Windows
NT/2000 clients (<TT
CLASS="PARAMETER"
><I
>use client driver</I
></TT
>). Both of
these options are described in the smb.coinf(5) man page and are
disabled by default.</P
>One way to debug printing problems is to start by replacing these
command with shell scripts that record the arguments and the contents
of the print file. A simple example of this kind of things might
be:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> print command = /tmp/saveprint %p %s
#!/bin/saveprint
# we make sure that we are the right user
/usr/bin/id -p &#62;/tmp/tmp.print
# we run the command and save the error messages
# replace the command with the one appropriate for your system
/usr/bin/lpr -r -P$1 $2 2&#62;&#62;&#38;/tmp/tmp.print</PRE
></P
><P
>Then you print a file and try removing it. You may find that the
print queue needs to be stopped in order to see the queue status
and remove the job:</P
><P
><PRE
CLASS="PROGRAMLISTING"
>&#13;h4: {42} % echo hi &#62;/tmp/hi
h4: {43} % smbclient //localhost/lw4
added interface ip=10.0.0.4 bcast=10.0.0.255 nmask=255.255.255.0
Password:
Domain=[ASTART] OS=[Unix] Server=[Samba 2.0.7]
smb: \&#62; print /tmp/hi
putting file /tmp/hi as hi-17534 (0.0 kb/s) (average 0.0 kb/s)
smb: \&#62; queue
1049 3 hi-17534
smb: \&#62; cancel 1049
Error cancelling job 1049 : code 0
smb: \&#62; cancel 1049
Job 1049 cancelled
smb: \&#62; queue
smb: \&#62; exit</PRE
></P
><P
>The 'code 0' indicates that the job was removed. The comment
by the smbclient is a bit misleading on this.
You can observe the command output and then and look at the
/tmp/tmp.print file to see what the results are. You can quickly
find out if the problem is with your printing system. Often people
have problems with their /etc/printcap file or permissions on
various print queues.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2133"
></A
>15.4.3. What printers do I have?</H2
><P
>You can use the 'testprns' program to check to see if the printer
name you are using is recognized by Samba. For example, you can
use:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> testprns printer /etc/printcap</PRE
></P
><P
>Samba can get its printcap information from a file or from a program.
You can try the following to see the format of the extracted
information:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> testprns -a printer /etc/printcap
testprns -a printer '|/bin/cat printcap'</PRE
></P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2141"
></A
>15.4.4. Setting up printcap and print servers</H2
><P
>You may need to set up some printcaps for your Samba system to use.
It is strongly recommended that you use the facilities provided by
the print spooler to set up queues and printcap information.</P
><P
>Samba requires either a printcap or program to deliver printcap
information. This printcap information has the format:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> name|alias1|alias2...:option=value:...</PRE
></P
><P
>For almost all printing systems, the printer 'name' must be composed
only of alphanumeric or underscore '_' characters. Some systems also
allow hyphens ('-') as well. An alias is an alternative name for the
printer, and an alias with a space in it is used as a 'comment'
about the printer. The printcap format optionally uses a \ at the end of lines
to extend the printcap to multiple lines.</P
><P
>Here are some examples of printcap files:</P
><P
><P
></P
><OL
TYPE="1"
><LI
><P
>pr just printer name</P
></LI
><LI
><P
>pr|alias printer name and alias</P
></LI
><LI
><P
>pr|My Printer printer name, alias used as comment</P
></LI
><LI
><P
>pr:sh:\ Same as pr:sh:cm= testing
:cm= \
testing</P
></LI
><LI
><P
>pr:sh Same as pr:sh:cm= testing
:cm= testing</P
></LI
></OL
></P
><P
>Samba reads the printcap information when first started. If you make
changes in the printcap information, then you must do the following:</P
><P
></P
><OL
TYPE="1"
><LI
><P
>make sure that the print spooler is aware of these changes.
The LPRng system uses the 'lpc reread' command to do this.</P
></LI
><LI
><P
>make sure that the spool queues, etc., exist and have the
correct permissions. The LPRng system uses the 'checkpc -f'
command to do this.</P
></LI
><LI
><P
>You now should send a SIGHUP signal to the smbd server to have
it reread the printcap information.</P
></LI
></OL
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2169"
></A
>15.4.5. Job sent, no output</H2
><P
>This is the most frustrating part of printing. You may have sent the
job, verified that the job was forwarded, set up a wrapper around
the command to send the file, but there was no output from the printer.</P
><P
>First, check to make sure that the job REALLY is getting to the
right print queue. If you are using a BSD or LPRng print spooler,
you can temporarily stop the printing of jobs. Jobs can still be
submitted, but they will not be printed. Use:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> lpc -Pprinter stop</PRE
></P
><P
>Now submit a print job and then use 'lpq -Pprinter' to see if the
job is in the print queue. If it is not in the print queue then
you will have to find out why it is not being accepted for printing.</P
><P
>Next, you may want to check to see what the format of the job really
was. With the assistance of the system administrator you can view
the submitted jobs files. You may be surprised to find that these
are not in what you would expect to call a printable format.
You can use the UNIX 'file' utitily to determine what the job
format actually is:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> cd /var/spool/lpd/printer # spool directory of print jobs
ls # find job files
file dfA001myhost</PRE
></P
><P
>You should make sure that your printer supports this format OR that
your system administrator has installed a 'print filter' that will
convert the file to a format appropriate for your printer.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2180"
></A
>15.4.6. Job sent, strange output</H2
><P
>Once you have the job printing, you can then start worrying about
making it print nicely.</P
><P
>The most common problem is extra pages of output: banner pages
OR blank pages at the end.</P
><P
>If you are getting banner pages, check and make sure that the
printcap option or printer option is configured for no banners.
If you have a printcap, this is the :sh (suppress header or banner
page) option. You should have the following in your printer.</P
><P
><PRE
CLASS="PROGRAMLISTING"
> printer: ... :sh</PRE
></P
><P
>If you have this option and are still getting banner pages, there
is a strong chance that your printer is generating them for you
automatically. You should make sure that banner printing is disabled
for the printer. This usually requires using the printer setup software
or procedures supplied by the printer manufacturer.</P
><P
>If you get an extra page of output, this could be due to problems
with your job format, or if you are generating PostScript jobs,
incorrect setting on your printer driver on the MicroSoft client.
For example, under Win95 there is a option:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> Printers|Printer Name|(Right Click)Properties|Postscript|Advanced|</PRE
></P
><P
>that allows you to choose if a Ctrl-D is appended to all jobs.
This is a very bad thing to do, as most spooling systems will
automatically add a ^D to the end of the job if it is detected as
PostScript. The multiple ^D may cause an additional page of output.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2192"
></A
>15.4.7. Raw PostScript printed</H2
><P
>This is a problem that is usually caused by either the print spooling
system putting information at the start of the print job that makes
the printer think the job is a text file, or your printer simply
does not support PostScript. You may need to enable 'Automatic
Format Detection' on your printer.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2195"
></A
>15.4.8. Advanced Printing</H2
><P
>Note that you can do some pretty magic things by using your
imagination with the "print command" option and some shell scripts.
Doing print accounting is easy by passing the %U option to a print
command shell script. You could even make the print command detect
the type of output and its size and send it to an appropriate
printer.</P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2198"
></A
>15.4.9. Real debugging</H2
><P
>If the above debug tips don't help, then maybe you need to bring in
the bug guns, system tracing. See Tracing.txt in this directory.</P
></DIV
></DIV
></DIV
><DIV
@ -1184,7 +1380,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="unix-permissions.html"
HREF="msdfs.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -1202,7 +1398,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="printingdebug.html"
HREF="winbind.html"
ACCESSKEY="N"
>Next</A
></TD
@ -1212,17 +1408,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>UNIX Permission Bits and Windows NT Access Control Lists</TD
>Hosting a Microsoft Distributed File System tree on Samba</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="optional.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Debugging Printing Problems</TD
>Unified Logons between Windows NT and UNIX using Winbind</TD
></TR
></TABLE
></DIV

515
docs/htmldocs/printingdebug.html
View File

@ -1,515 +0,0 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>Debugging Printing Problems</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
REL="PREVIOUS"
TITLE="Printing Support in Samba 2.2.x"
HREF="printing.html"><LINK
REL="NEXT"
TITLE="Security levels"
HREF="securitylevels.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="printing.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="securitylevels.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="CHAPTER"
><H1
><A
NAME="PRINTINGDEBUG"
></A
>Chapter 7. Debugging Printing Problems</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN986"
></A
>7.1. Introduction</H1
><P
>This is a short description of how to debug printing problems with
Samba. This describes how to debug problems with printing from a SMB
client to a Samba server, not the other way around. For the reverse
see the examples/printing directory.</P
><P
>Ok, so you want to print to a Samba server from your PC. The first
thing you need to understand is that Samba does not actually do any
printing itself, it just acts as a middleman between your PC client
and your Unix printing subsystem. Samba receives the file from the PC
then passes the file to a external "print command". What print command
you use is up to you.</P
><P
>The whole things is controlled using options in smb.conf. The most
relevant options (which you should look up in the smb.conf man page)
are:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> [global]
print command - send a file to a spooler
lpq command - get spool queue status
lprm command - remove a job
[printers]
path = /var/spool/lpd/samba</PRE
></P
><P
>The following are nice to know about:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> queuepause command - stop a printer or print queue
queueresume command - start a printer or print queue</PRE
></P
><P
>Example:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> print command = /usr/bin/lpr -r -P%p %s
lpq command = /usr/bin/lpq -P%p %s
lprm command = /usr/bin/lprm -P%p %j
queuepause command = /usr/sbin/lpc -P%p stop
queuepause command = /usr/sbin/lpc -P%p start</PRE
></P
><P
>Samba should set reasonable defaults for these depending on your
system type, but it isn't clairvoyant. It is not uncommon that you
have to tweak these for local conditions. The commands should
always have fully specified pathnames, as the smdb may not have
the correct PATH values.</P
><P
>When you send a job to Samba to be printed, it will make a temporary
copy of it in the directory specified in the [printers] section.
and it should be periodically cleaned out. The lpr -r option
requests that the temporary copy be removed after printing; If
printing fails then you might find leftover files in this directory,
and it should be periodically cleaned out. Samba used the lpq
command to determine the "job number" assigned to your print job
by the spooler.</P
><P
>The %&gt;letter&lt; are "macros" that get dynamically replaced with appropriate
values when they are used. The %s gets replaced with the name of the spool
file that Samba creates and the %p gets replaced with the name of the
printer. The %j gets replaced with the "job number" which comes from
the lpq output.</P
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1002"
></A
>7.2. Debugging printer problems</H1
><P
>One way to debug printing problems is to start by replacing these
command with shell scripts that record the arguments and the contents
of the print file. A simple example of this kind of things might
be:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> print command = /tmp/saveprint %p %s
#!/bin/saveprint
# we make sure that we are the right user
/usr/bin/id -p &#62;/tmp/tmp.print
# we run the command and save the error messages
# replace the command with the one appropriate for your system
/usr/bin/lpr -r -P$1 $2 2&#62;&#62;&#38;/tmp/tmp.print</PRE
></P
><P
>Then you print a file and try removing it. You may find that the
print queue needs to be stopped in order to see the queue status
and remove the job:</P
><P
><PRE
CLASS="PROGRAMLISTING"
>&#13;h4: {42} % echo hi &#62;/tmp/hi
h4: {43} % smbclient //localhost/lw4
added interface ip=10.0.0.4 bcast=10.0.0.255 nmask=255.255.255.0
Password:
Domain=[ASTART] OS=[Unix] Server=[Samba 2.0.7]
smb: \&#62; print /tmp/hi
putting file /tmp/hi as hi-17534 (0.0 kb/s) (average 0.0 kb/s)
smb: \&#62; queue
1049 3 hi-17534
smb: \&#62; cancel 1049
Error cancelling job 1049 : code 0
smb: \&#62; cancel 1049
Job 1049 cancelled
smb: \&#62; queue
smb: \&#62; exit</PRE
></P
><P
>The 'code 0' indicates that the job was removed. The comment
by the smbclient is a bit misleading on this.
You can observe the command output and then and look at the
/tmp/tmp.print file to see what the results are. You can quickly
find out if the problem is with your printing system. Often people
have problems with their /etc/printcap file or permissions on
various print queues.</P
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1011"
></A
>7.3. What printers do I have?</H1
><P
>You can use the 'testprns' program to check to see if the printer
name you are using is recognized by Samba. For example, you can
use:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> testprns printer /etc/printcap</PRE
></P
><P
>Samba can get its printcap information from a file or from a program.
You can try the following to see the format of the extracted
information:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> testprns -a printer /etc/printcap
testprns -a printer '|/bin/cat printcap'</PRE
></P
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1019"
></A
>7.4. Setting up printcap and print servers</H1
><P
>You may need to set up some printcaps for your Samba system to use.
It is strongly recommended that you use the facilities provided by
the print spooler to set up queues and printcap information.</P
><P
>Samba requires either a printcap or program to deliver printcap
information. This printcap information has the format:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> name|alias1|alias2...:option=value:...</PRE
></P
><P
>For almost all printing systems, the printer 'name' must be composed
only of alphanumeric or underscore '_' characters. Some systems also
allow hyphens ('-') as well. An alias is an alternative name for the
printer, and an alias with a space in it is used as a 'comment'
about the printer. The printcap format optionally uses a \ at the end of lines
to extend the printcap to multiple lines.</P
><P
>Here are some examples of printcap files:</P
><P
><P
></P
><OL
TYPE="1"
><LI
><P
>pr just printer name</P
></LI
><LI
><P
>pr|alias printer name and alias</P
></LI
><LI
><P
>pr|My Printer printer name, alias used as comment</P
></LI
><LI
><P
>pr:sh:\ Same as pr:sh:cm= testing
:cm= \
testing</P
></LI
><LI
><P
>pr:sh Same as pr:sh:cm= testing
:cm= testing</P
></LI
></OL
></P
><P
>Samba reads the printcap information when first started. If you make
changes in the printcap information, then you must do the following:</P
><P
></P
><OL
TYPE="1"
><LI
><P
>make sure that the print spooler is aware of these changes.
The LPRng system uses the 'lpc reread' command to do this.</P
></LI
><LI
><P
>make sure that the spool queues, etc., exist and have the
correct permissions. The LPRng system uses the 'checkpc -f'
command to do this.</P
></LI
><LI
><P
>You now should send a SIGHUP signal to the smbd server to have
it reread the printcap information.</P
></LI
></OL
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1047"
></A
>7.5. Job sent, no output</H1
><P
>This is the most frustrating part of printing. You may have sent the
job, verified that the job was forwarded, set up a wrapper around
the command to send the file, but there was no output from the printer.</P
><P
>First, check to make sure that the job REALLY is getting to the
right print queue. If you are using a BSD or LPRng print spooler,
you can temporarily stop the printing of jobs. Jobs can still be
submitted, but they will not be printed. Use:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> lpc -Pprinter stop</PRE
></P
><P
>Now submit a print job and then use 'lpq -Pprinter' to see if the
job is in the print queue. If it is not in the print queue then
you will have to find out why it is not being accepted for printing.</P
><P
>Next, you may want to check to see what the format of the job really
was. With the assistance of the system administrator you can view
the submitted jobs files. You may be surprised to find that these
are not in what you would expect to call a printable format.
You can use the UNIX 'file' utitily to determine what the job
format actually is:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> cd /var/spool/lpd/printer # spool directory of print jobs
ls # find job files
file dfA001myhost</PRE
></P
><P
>You should make sure that your printer supports this format OR that
your system administrator has installed a 'print filter' that will
convert the file to a format appropriate for your printer.</P
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1058"
></A
>7.6. Job sent, strange output</H1
><P
>Once you have the job printing, you can then start worrying about
making it print nicely.</P
><P
>The most common problem is extra pages of output: banner pages
OR blank pages at the end.</P
><P
>If you are getting banner pages, check and make sure that the
printcap option or printer option is configured for no banners.
If you have a printcap, this is the :sh (suppress header or banner
page) option. You should have the following in your printer.</P
><P
><PRE
CLASS="PROGRAMLISTING"
> printer: ... :sh</PRE
></P
><P
>If you have this option and are still getting banner pages, there
is a strong chance that your printer is generating them for you
automatically. You should make sure that banner printing is disabled
for the printer. This usually requires using the printer setup software
or procedures supplied by the printer manufacturer.</P
><P
>If you get an extra page of output, this could be due to problems
with your job format, or if you are generating PostScript jobs,
incorrect setting on your printer driver on the MicroSoft client.
For example, under Win95 there is a option:</P
><P
><PRE
CLASS="PROGRAMLISTING"
> Printers|Printer Name|(Right Click)Properties|Postscript|Advanced|</PRE
></P
><P
>that allows you to choose if a Ctrl-D is appended to all jobs.
This is a very bad thing to do, as most spooling systems will
automatically add a ^D to the end of the job if it is detected as
PostScript. The multiple ^D may cause an additional page of output.</P
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1070"
></A
>7.7. Raw PostScript printed</H1
><P
>This is a problem that is usually caused by either the print spooling
system putting information at the start of the print job that makes
the printer think the job is a text file, or your printer simply
does not support PostScript. You may need to enable 'Automatic
Format Detection' on your printer.</P
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1073"
></A
>7.8. Advanced Printing</H1
><P
>Note that you can do some pretty magic things by using your
imagination with the "print command" option and some shell scripts.
Doing print accounting is easy by passing the %U option to a print
command shell script. You could even make the print command detect
the type of output and its size and send it to an appropriate
printer.</P
></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1076"
></A
>7.9. Real debugging</H1
><P
>If the above debug tips don't help, then maybe you need to bring in
the bug guns, system tracing. See Tracing.txt in this directory.</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="printing.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="securitylevels.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Printing Support in Samba 2.2.x</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Security levels</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>

131
docs/htmldocs/rpcclient.1.html
View File

@ -1,12 +1,11 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>rpcclient</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -16,7 +15,9 @@ VLINK="#840084"
ALINK="#0000FF"
><H1
><A
NAME="RPCCLIENT">rpcclient</H1
NAME="RPCCLIENT"
></A
>rpcclient</H1
><DIV
CLASS="REFNAMEDIV"
><A
@ -29,13 +30,15 @@ NAME="AEN5"
><DIV
CLASS="REFSYNOPSISDIV"
><A
NAME="AEN8"><H2
NAME="AEN8"
></A
><H2
>Synopsis</H2
><P
><B
CLASS="COMMAND"
>rpcclient</B
> [-A authfile] [-c &#60;command string&#62;] [-d debuglevel] [-h] [-l logfile] [-N] [-s &#60;smb config file&#62;] [-U username[%password]] [-W workgroup] [-N] [-I destinationIP] {server}</P
> [-A authfile] [-c &lt;command string&gt;] [-d debuglevel] [-h] [-l logfile] [-N] [-s &lt;smb config file&gt;] [-U username[%password]] [-W workgroup] [-N] [-I destinationIP] {server}</P
></DIV
><DIV
CLASS="REFSECT1"
@ -102,21 +105,12 @@ CLASS="FILENAME"
password used in the connection. The format of the file is
</P
><P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="90%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
> username = &#60;value&#62;
password = &#60;value&#62;
domain = &#60;value&#62;
> username = &lt;value&gt;
password = &lt;value&gt;
domain = &lt;value&gt;
</PRE
></TD
></TR
></TABLE
></P
><P
>Make certain that the permissions on the file restrict
@ -130,6 +124,53 @@ CLASS="PROGRAMLISTING"
below)) </P
></DD
><DT
>-d|--debug=debuglevel</DT
><DD
><P
><TT
CLASS="REPLACEABLE"
><I
>debuglevel</I
></TT
> 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 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
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
>-h|--help</DT
><DD
><P
>Print a summary of command line options.</P
></DD
><DT
>-I IP-address</DT
><DD
><P
@ -262,14 +303,17 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN92"
NAME="AEN107"
></A
><H2
>COMMANDS</H2
><P
><SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>LSARPC</I
></SPAN
></P
><P
></P
@ -310,9 +354,12 @@ CLASS="COMMAND"
><P
> </P
><P
><SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>SAMR</I
></SPAN
></P
><P
></P
@ -377,9 +424,12 @@ CLASS="COMMAND"
><P
> </P
><P
><SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>SPOOLSS</I
></SPAN
></P
><P
></P
@ -388,7 +438,7 @@ CLASS="EMPHASIS"
><P
><B
CLASS="COMMAND"
>adddriver &#60;arch&#62; &#60;config&#62;</B
>adddriver &lt;arch&gt; &lt;config&gt;</B
>
- Execute an AddPrinterDriver() RPC to install the printer driver
information on the server. Note that the driver files should
@ -415,12 +465,6 @@ CLASS="PARAMETER"
> parameter is defined as
follows: </P
><P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="90%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
> Long Printer Name:\
@ -432,9 +476,6 @@ CLASS="PROGRAMLISTING"
Default Data Type:\
Comma Separated list of Files
</PRE
></TD
></TR
></TABLE
></P
><P
>Any empty fields should be enter as the string "NULL". </P
@ -450,8 +491,8 @@ CLASS="PROGRAMLISTING"
><P
><B
CLASS="COMMAND"
>addprinter &#60;printername&#62;
&#60;sharename&#62; &#60;drivername&#62; &#60;port&#62;</B
>addprinter &lt;printername&gt;
&lt;sharename&gt; &lt;drivername&gt; &lt;port&gt;</B
>
- Add a printer on the remote server. This printer
will be automatically shared. Be aware that the printer driver
@ -497,7 +538,7 @@ CLASS="COMMAND"
><P
><B
CLASS="COMMAND"
>enumjobs &#60;printer&#62;</B
>enumjobs &lt;printer&gt;</B
>
- List the jobs and status of a given printer.
This command corresponds to the MS Platform SDK EnumJobs()
@ -539,7 +580,7 @@ CLASS="COMMAND"
><P
><B
CLASS="COMMAND"
>getdata &#60;printername&#62;</B
>getdata &lt;printername&gt;</B
>
- Retrieve the data for a given printer setting. See
the <B
@ -553,7 +594,7 @@ CLASS="COMMAND"
><P
><B
CLASS="COMMAND"
>getdriver &#60;printername&#62;</B
>getdriver &lt;printername&gt;</B
>
- Retrieve the printer driver information (such as driver file,
config file, dependent files, etc...) for
@ -565,7 +606,7 @@ CLASS="COMMAND"
><P
><B
CLASS="COMMAND"
>getdriverdir &#60;arch&#62;</B
>getdriverdir &lt;arch&gt;</B
>
- Execute a GetPrinterDriverDirectory()
RPC to retrieve the SMB share name and subdirectory for
@ -583,7 +624,7 @@ CLASS="PARAMETER"
><P
><B
CLASS="COMMAND"
>getprinter &#60;printername&#62;</B
>getprinter &lt;printername&gt;</B
>
- Retrieve the current printer information. This command
corresponds to the GetPrinter() MS Platform SDK function.
@ -593,7 +634,7 @@ CLASS="COMMAND"
><P
><B
CLASS="COMMAND"
>openprinter &#60;printername&#62;</B
>openprinter &lt;printername&gt;</B
>
- Execute an OpenPrinterEx() and ClosePrinter() RPC
against a given printer. </P
@ -602,8 +643,8 @@ CLASS="COMMAND"
><P
><B
CLASS="COMMAND"
>setdriver &#60;printername&#62;
&#60;drivername&#62;</B
>setdriver &lt;printername&gt;
&lt;drivername&gt;</B
>
- Execute a SetPrinter() command to update the printer driver
associated with an installed printer. The printer driver must
@ -621,9 +662,12 @@ CLASS="COMMAND"
></LI
></UL
><P
><SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>GENERAL OPTIONS</I
></SPAN
></P
><P
></P
@ -661,7 +705,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN212"
NAME="AEN227"
></A
><H2
>BUGS</H2
@ -676,9 +720,12 @@ CLASS="COMMAND"
><P
>From Luke Leighton's original rpcclient man page:</P
><P
><SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>"WARNING!</I
></SPAN
> 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
@ -703,7 +750,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN222"
NAME="AEN237"
></A
><H2
>VERSION</H2
@ -714,7 +761,7 @@ NAME="AEN222"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN225"
NAME="AEN240"
></A
><H2
>AUTHOR</H2

57
docs/htmldocs/samba-bdc.html
View File

@ -9,12 +9,15 @@ CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><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="How to Configure Samba 2.2 as a Primary Domain Controller"
TITLE="How to Configure Samba as a NT4 Primary Domain Controller"
HREF="samba-pdc.html"><LINK
REL="NEXT"
TITLE="Storing Samba's User/Machine Account information in an LDAP Directory"
HREF="samba-ldap-howto.html"></HEAD
TITLE="Samba as a ADS domain member"
HREF="ads.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="samba-ldap-howto.html"
HREF="ads.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,15 +74,15 @@ CLASS="CHAPTER"
><A
NAME="SAMBA-BDC"
></A
>Chapter 12. How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</H1
>Chapter 8. How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2148"
NAME="AEN1143"
></A
>12.1. Prerequisite Reading</H1
>8.1. Prerequisite Reading</H1
><P
>Before you continue reading in this chapter, please make sure
that you are comfortable with configuring a Samba PDC
@ -94,9 +97,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2152"
NAME="AEN1147"
></A
>12.2. Background</H1
>8.2. Background</H1
><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
@ -139,9 +142,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2160"
NAME="AEN1155"
></A
>12.3. What qualifies a Domain Controller on the network?</H1
>8.3. What qualifies a Domain Controller on the network?</H1
><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
@ -156,9 +159,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2163"
NAME="AEN1158"
></A
>12.3.1. How does a Workstation find its domain controller?</H2
>8.3.1. How does a Workstation find its domain controller?</H2
><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
@ -175,9 +178,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2166"
NAME="AEN1161"
></A
>12.3.2. When is the PDC needed?</H2
>8.3.2. When is the PDC needed?</H2
><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
@ -191,9 +194,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2169"
NAME="AEN1164"
></A
>12.4. Can Samba be a Backup Domain Controller?</H1
>8.4. Can Samba be a Backup Domain Controller?</H1
><P
>With version 2.2, no. The native NT SAM replication protocols have
not yet been fully implemented. The Samba Team is working on
@ -210,9 +213,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2173"
NAME="AEN1168"
></A
>12.5. How do I set up a Samba BDC?</H1
>8.5. How do I set up a Samba BDC?</H1
><P
>Several things have to be done:</P
><P
@ -277,9 +280,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2190"
NAME="AEN1185"
></A
>12.5.1. How do I replicate the smbpasswd file?</H2
>8.5.1. How do I replicate the smbpasswd file?</H2
><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
@ -329,7 +332,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="samba-ldap-howto.html"
HREF="ads.html"
ACCESSKEY="N"
>Next</A
></TD
@ -339,17 +342,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>How to Configure Samba 2.2 as a Primary Domain Controller</TD
>How to Configure Samba as a NT4 Primary Domain Controller</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="type.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Storing Samba's User/Machine Account information in an LDAP Directory</TD
>Samba as a ADS domain member</TD
></TR
></TABLE
></DIV

2
docs/htmldocs/samba-howto-collection.html
View File

@ -48,7 +48,7 @@ CLASS="emphasis"
CLASS="EMPHASIS"
>Last Update</I
></SPAN
> : $Date: 2002/11/13 15:34:49 $</P
> : $Date: 2003/01/15 22:29:23 $</P
><P
>This book is a collection of HOWTOs added to Samba documentation over the years.
I try to ensure that all are current, but sometimes the is a larger job

79
docs/htmldocs/samba-ldap-howto.html
View File

@ -9,12 +9,15 @@ CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
REL="UP"
TITLE="Optional configuration"
HREF="optional.html"><LINK
REL="PREVIOUS"
TITLE="How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain"
HREF="samba-bdc.html"><LINK
TITLE="Stackable VFS modules"
HREF="vfs.html"><LINK
REL="NEXT"
TITLE="Using samba 3.0 with ActiveDirectory support"
HREF="ads.html"></HEAD
TITLE="HOWTO Access Samba source code via CVS"
HREF="cvs-access.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="samba-bdc.html"
HREF="vfs.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="ads.html"
HREF="cvs-access.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,15 +74,15 @@ CLASS="CHAPTER"
><A
NAME="SAMBA-LDAP-HOWTO"
></A
>Chapter 13. Storing Samba's User/Machine Account information in an LDAP Directory</H1
>Chapter 20. Storing Samba's User/Machine Account information in an LDAP Directory</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2211"
NAME="AEN2747"
></A
>13.1. Purpose</H1
>20.1. Purpose</H1
><P
>This document describes how to use an LDAP directory for storing Samba user
account information traditionally stored in the smbpasswd(5) file. It is
@ -145,9 +148,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2231"
NAME="AEN2767"
></A
>13.2. Introduction</H1
>20.2. Introduction</H1
><P
>Traditionally, when configuring <A
HREF="smb.conf.5.html#ENCRYPTPASSWORDS"
@ -262,9 +265,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2260"
NAME="AEN2796"
></A
>13.3. Supported LDAP Servers</H1
>20.3. Supported LDAP Servers</H1
><P
>The LDAP samdb code in 2.2.3 has been developed and tested using the OpenLDAP
2.0 server and client libraries. The same code should be able to work with
@ -287,9 +290,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2265"
NAME="AEN2801"
></A
>13.4. Schema and Relationship to the RFC 2307 posixAccount</H1
>20.4. Schema and Relationship to the RFC 2307 posixAccount</H1
><P
>Samba 2.2.3 includes the necessary schema file for OpenLDAP 2.0 in
<TT
@ -346,17 +349,17 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2277"
NAME="AEN2813"
></A
>13.5. Configuring Samba with LDAP</H1
>20.5. Configuring Samba with LDAP</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2279"
NAME="AEN2815"
></A
>13.5.1. OpenLDAP configuration</H2
>20.5.1. OpenLDAP configuration</H2
><P
>To include support for the sambaAccount object in an OpenLDAP directory
server, first copy the samba.schema file to slapd's configuration directory.</P
@ -436,9 +439,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2296"
NAME="AEN2832"
></A
>13.5.2. Configuring Samba</H2
>20.5.2. Configuring Samba</H2
><P
>The following parameters are available in smb.conf only with <TT
CLASS="PARAMETER"
@ -556,9 +559,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2324"
NAME="AEN2860"
></A
>13.6. Accounts and Groups management</H1
>20.6. Accounts and Groups management</H1
><P
>As users accounts are managed thru the sambaAccount objectclass, you should
modify you existing administration tools to deal with sambaAccount attributes.</P
@ -581,9 +584,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2329"
NAME="AEN2865"
></A
>13.7. Security and sambaAccount</H1
>20.7. Security and sambaAccount</H1
><P
>There are two important points to remember when discussing the security
of sambaAccount entries in the directory.</P
@ -660,9 +663,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2349"
NAME="AEN2885"
></A
>13.8. LDAP specials attributes for sambaAccounts</H1
>20.8. LDAP specials attributes for sambaAccounts</H1
><P
>The sambaAccount objectclass is composed of the following attributes:</P
><P
@ -871,9 +874,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2419"
NAME="AEN2955"
></A
>13.9. Example LDIF Entries for a sambaAccount</H1
>20.9. Example LDIF Entries for a sambaAccount</H1
><P
>The following is a working LDIF with the inclusion of the posixAccount objectclass:</P
><P
@ -929,9 +932,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2427"
NAME="AEN2963"
></A
>13.10. Comments</H1
>20.10. Comments</H1
><P
>Please mail all comments regarding this HOWTO to <A
HREF="mailto:jerry@samba.org"
@ -957,7 +960,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="samba-bdc.html"
HREF="vfs.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -975,7 +978,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="ads.html"
HREF="cvs-access.html"
ACCESSKEY="N"
>Next</A
></TD
@ -985,17 +988,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>How to Act as a Backup Domain Controller in a Purely Samba Controlled Domain</TD
>Stackable VFS modules</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="optional.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Using samba 3.0 with ActiveDirectory support</TD
>HOWTO Access Samba source code via CVS</TD
></TR
></TABLE
></DIV

95
docs/htmldocs/securitylevels.html
View File

@ -2,19 +2,22 @@
<HTML
><HEAD
><TITLE
>Security levels</TITLE
>User and Share security level (for servers not in a domain)</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><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="Debugging Printing Problems"
HREF="printingdebug.html"><LINK
TITLE="Type of installation"
HREF="type.html"><LINK
REL="NEXT"
TITLE="security = domain in Samba 2.x"
HREF="domain-security.html"></HEAD
TITLE="How to Configure Samba as a NT4 Primary Domain Controller"
HREF="samba-pdc.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="printingdebug.html"
HREF="type.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="domain-security.html"
HREF="samba-pdc.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,61 +74,7 @@ CLASS="CHAPTER"
><A
NAME="SECURITYLEVELS"
></A
>Chapter 8. Security levels</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1089"
></A
>8.1. Introduction</H1
><P
>Samba supports the following options to the global smb.conf parameter</P
><P
><PRE
CLASS="PROGRAMLISTING"
>[global]
<A
HREF="smb.conf.5.html#SECURITY"
TARGET="_top"
><TT
CLASS="PARAMETER"
><I
>security</I
></TT
></A
> = [share|user(default)|domain|ads]</PRE
></P
><P
>Please refer to the smb.conf man page for usage information and to the document
<A
HREF="DOMAIN_MEMBER.html"
TARGET="_top"
>DOMAIN_MEMBER.html</A
> for further background details
on domain mode security. The Windows 2000 Kerberos domain security model
(security = ads) is described in the <A
HREF="ADS-HOWTO.html"
TARGET="_top"
>ADS-HOWTO.html</A
>.</P
><P
>Of the above, "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
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1100"
></A
>8.2. More complete description of security levels</H1
>Chapter 6. User and Share security level (for servers not in a domain)</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
@ -211,7 +160,13 @@ 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
></DIV
><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
><DIV
CLASS="NAVFOOTER"
@ -229,7 +184,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="printingdebug.html"
HREF="type.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -247,7 +202,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="domain-security.html"
HREF="samba-pdc.html"
ACCESSKEY="N"
>Next</A
></TD
@ -257,17 +212,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Debugging Printing Problems</TD
>Type of installation</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="type.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>security = domain in Samba 2.x</TD
>How to Configure Samba as a NT4 Primary Domain Controller</TD
></TR
></TABLE
></DIV

4
docs/htmldocs/smb.conf.5.html
View File

@ -13057,7 +13057,7 @@ CLASS="PARAMETER"
>
list will be allowed. By default this option is disabled so that a
client can supply a username to be used by the server. Enabling
this parameter will force the server to only use the login
this parameter will force the server to only user the login
names from the <TT
CLASS="PARAMETER"
><I
@ -13066,7 +13066,7 @@ CLASS="PARAMETER"
> list and is only really
useful in <A
HREF="#SECURITYEQUALSSHARE"
>share level</A
>shave level</A
>
security.</P
><P

116
docs/htmldocs/smbclient.1.html
View File

@ -1,12 +1,11 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>smbclient</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -16,7 +15,9 @@ VLINK="#840084"
ALINK="#0000FF"
><H1
><A
NAME="SMBCLIENT">smbclient</H1
NAME="SMBCLIENT"
></A
>smbclient</H1
><DIV
CLASS="REFNAMEDIV"
><A
@ -29,13 +30,15 @@ NAME="AEN5"
><DIV
CLASS="REFSYNOPSISDIV"
><A
NAME="AEN8"><H2
NAME="AEN8"
></A
><H2
>Synopsis</H2
><P
><B
CLASS="COMMAND"
>smbclient</B
> {servicename} [password] [-b &#60;buffer size&#62;] [-d debuglevel] [-D Directory] [-U username] [-W workgroup] [-M &#60;netbios name&#62;] [-m maxprotocol] [-A authfile] [-N] [-l logfile] [-L &#60;netbios name&#62;] [-I destinationIP] [-E] [-c &#60;command string&#62;] [-i scope] [-O &#60;socket options&#62;] [-p port] [-R &#60;name resolve order&#62;] [-s &#60;smb config file&#62;] [-T&#60;c|x&#62;IXFqgbNan]</P
> {servicename} [password] [-b &lt;buffer size&gt;] [-d debuglevel] [-D Directory] [-U username] [-W workgroup] [-M &lt;netbios name&gt;] [-m maxprotocol] [-A authfile] [-N] [-l logfile] [-L &lt;netbios name&gt;] [-I destinationIP] [-E] [-c &lt;command string&gt;] [-i scope] [-O &lt;socket options&gt;] [-p port] [-R &lt;name resolve order&gt;] [-s &lt;smb config file&gt;] [-T&lt;c|x&gt;IXFqgbNan]</P
></DIV
><DIV
CLASS="REFSECT1"
@ -193,7 +196,7 @@ CLASS="FILENAME"
options. </P
></DD
><DT
>-R &#60;name resolve order&#62;</DT
>-R &lt;name resolve order&gt;</DT
><DD
><P
>This option is used by the programs in the Samba
@ -346,9 +349,12 @@ CLASS="FILENAME"
> for a description of how to handle incoming
WinPopup messages in Samba. </P
><P
><SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>Note</I
></SPAN
>: Copy WinPopup into the startup group
on your WfWg PCs if you want them to always be able to receive
messages. </P
@ -367,9 +373,12 @@ CLASS="FILENAME"
CLASS="FILENAME"
>rfc1002.txt</TT
>.
NetBIOS scopes are <I
NetBIOS scopes are <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>very</I
></SPAN
> rarely used, only set
this parameter if you are the system administrator in charge of all
the NetBIOS systems you communicate with. </P
@ -426,14 +435,20 @@ CLASS="REPLACEABLE"
><I
>debuglevel</I
></TT
> is set to the letter 'A', then <I
> is set to the letter 'A', then <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>all
</I
></SPAN
> debug messages will be printed. This setting
is for developers only (and people who <I
is for developers only (and people who <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>really</I
></SPAN
> want
to know how the code works internally). </P
><P
@ -595,21 +610,12 @@ CLASS="COMMAND"
password used in the connection. The format of the file is
</P
><P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="90%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>username = &#60;value&#62;
password = &#60;value&#62;
domain = &#60;value&#62;
>username = &lt;value&gt;
password = &lt;value&gt;
domain = &lt;value&gt;
</PRE
></TD
></TR
></TABLE
></P
><P
>If the domain parameter is missing the current workgroup name
@ -645,12 +651,18 @@ CLASS="COMMAND"
> how to interpret
filenames coming from the remote server. Usually Asian language
multibyte UNIX implementations use different character sets than
SMB/CIFS servers (<I
SMB/CIFS servers (<SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>EUC</I
> instead of <I
></SPAN
> instead of <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
> SJIS</I
></SPAN
> for example). Setting this parameter will let
<B
CLASS="COMMAND"
@ -864,9 +876,12 @@ CLASS="PARAMETER"
></LI
></UL
><P
><SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>Tar Long File Names</I
></SPAN
></P
><P
><B
@ -882,18 +897,24 @@ CLASS="COMMAND"
files in the archive with relative names, not absolute names.
</P
><P
><SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>Tar Filenames</I
></SPAN
></P
><P
>All file names can be given as DOS path names (with '\'
as the component separator) or as UNIX path names (with '/' as
the component separator). </P
><P
><SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>Examples</I
></SPAN
></P
><P
>Restore from tar file <TT
@ -995,7 +1016,7 @@ NAME="AEN310"
><P
><TT
CLASS="PROMPT"
>smb:\&#62; </TT
>smb:\&gt; </TT
></P
><P
>The backslash ("\") indicates the current working directory
@ -1015,7 +1036,7 @@ CLASS="PROMPT"
><P
>Parameters shown in square brackets (e.g., "[parameter]") are
optional. If not given, the command will use suitable defaults. Parameters
shown in angle brackets (e.g., "&#60;parameter&#62;") are required.
shown in angle brackets (e.g., "&lt;parameter&gt;") are required.
</P
><P
>Note that all commands operating on the server are actually
@ -1106,7 +1127,7 @@ CLASS="REPLACEABLE"
directory on the server will be reported. </P
></DD
><DT
>del &#60;mask&#62;</DT
>del &lt;mask&gt;</DT
><DD
><P
>The client will request that the server attempt
@ -1119,7 +1140,7 @@ CLASS="REPLACEABLE"
directory on the server. </P
></DD
><DT
>dir &#60;mask&#62;</DT
>dir &lt;mask&gt;</DT
><DD
><P
>A list of the files matching <TT
@ -1139,7 +1160,7 @@ CLASS="REPLACEABLE"
from the program. </P
></DD
><DT
>get &#60;remote file name&#62; [local file name]</DT
>get &lt;remote file name&gt; [local file name]</DT
><DD
><P
>Copy the file called <TT
@ -1204,13 +1225,13 @@ CLASS="REPLACEABLE"
lowercase filenames are the norm on UNIX systems. </P
></DD
><DT
>ls &#60;mask&#62;</DT
>ls &lt;mask&gt;</DT
><DD
><P
>See the dir command above. </P
></DD
><DT
>mask &#60;mask&#62;</DT
>mask &lt;mask&gt;</DT
><DD
><P
>This command allows the user to set up a mask
@ -1236,13 +1257,13 @@ CLASS="REPLACEABLE"
mask back to "*" after using the mget or mput commands. </P
></DD
><DT
>md &#60;directory name&#62;</DT
>md &lt;directory name&gt;</DT
><DD
><P
>See the mkdir command. </P
></DD
><DT
>mget &#60;mask&#62;</DT
>mget &lt;mask&gt;</DT
><DD
><P
>Copy all files matching <TT
@ -1267,14 +1288,14 @@ CLASS="COMMAND"
> are binary. See also the lowercase command. </P
></DD
><DT
>mkdir &#60;directory name&#62;</DT
>mkdir &lt;directory name&gt;</DT
><DD
><P
>Create a new directory on the server (user access
privileges permitting) with the specified name. </P
></DD
><DT
>mput &#60;mask&#62;</DT
>mput &lt;mask&gt;</DT
><DD
><P
>Copy all files matching <TT
@ -1300,7 +1321,7 @@ CLASS="COMMAND"
are binary. </P
></DD
><DT
>print &#60;file name&#62;</DT
>print &lt;file name&gt;</DT
><DD
><P
>Print the specified file from the local machine
@ -1309,7 +1330,7 @@ CLASS="COMMAND"
>See also the printmode command.</P
></DD
><DT
>printmode &#60;graphics or text&#62;</DT
>printmode &lt;graphics or text&gt;</DT
><DD
><P
>Set the print mode to suit either binary data
@ -1329,7 +1350,7 @@ CLASS="COMMAND"
</P
></DD
><DT
>put &#60;local file name&#62; [remote file name]</DT
>put &lt;local file name&gt; [remote file name]</DT
><DD
><P
>Copy the file called <TT
@ -1361,7 +1382,7 @@ CLASS="COMMAND"
>See the exit command. </P
></DD
><DT
>rd &#60;directory name&#62;</DT
>rd &lt;directory name&gt;</DT
><DD
><P
>See the rmdir command. </P
@ -1386,7 +1407,7 @@ CLASS="COMMAND"
using the mask command will be ignored. </P
></DD
><DT
>rm &#60;mask&#62;</DT
>rm &lt;mask&gt;</DT
><DD
><P
>Remove all files matching <TT
@ -1398,14 +1419,14 @@ CLASS="REPLACEABLE"
working directory on the server. </P
></DD
><DT
>rmdir &#60;directory name&#62;</DT
>rmdir &lt;directory name&gt;</DT
><DD
><P
>Remove the specified directory (user access
privileges permitting) from the server. </P
></DD
><DT
>setmode &#60;filename&#62; &#60;perm=[+|\-]rsha&#62;</DT
>setmode &lt;filename&gt; &lt;perm=[+|\-]rsha&gt;</DT
><DD
><P
>A version of the DOS attrib command to set
@ -1430,7 +1451,7 @@ CLASS="COMMAND"
</P
></DD
><DT
>tar &#60;c|x&#62;[IXbgNa]</DT
>tar &lt;c|x&gt;[IXbgNa]</DT
><DD
><P
>Performs a tar operation - see the <TT
@ -1446,7 +1467,7 @@ CLASS="PARAMETER"
</P
></DD
><DT
>blocksize &#60;blocksize&#62;</DT
>blocksize &lt;blocksize&gt;</DT
><DD
><P
>Blocksize. Must be followed by a valid (greater
@ -1459,7 +1480,7 @@ CLASS="REPLACEABLE"
>*TBLOCK (usually 512 byte) blocks. </P
></DD
><DT
>tarmode &#60;full|inc|reset|noreset&#62;</DT
>tarmode &lt;full|inc|reset|noreset&gt;</DT
><DD
><P
>Changes tar's behavior with regard to archive
@ -1547,9 +1568,12 @@ CLASS="FILENAME"
> /usr/samba/bin/</TT
> directory, this directory readable
by all, writeable only by root. The client program itself should
be executable by all. The client should <I
be executable by all. The client should <SPAN
CLASS="emphasis"
><I
CLASS="EMPHASIS"
>NOT</I
></SPAN
> be
setuid or setgid! </P
><P

2
docs/htmldocs/smbd.8.html
View File

@ -191,7 +191,7 @@ CLASS="COMMAND"
CLASS="COMMAND"
>-S</B
> parameter had been
given.
given.
</P
></DD
><DT

94
docs/htmldocs/smbgroupedit.8.html
View File

@ -1,11 +1,12 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
<HTML
><HEAD
><TITLE
>smbgroupedit</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -15,9 +16,7 @@ VLINK="#840084"
ALINK="#0000FF"
><H1
><A
NAME="SMBGROUPEDIT"
></A
>smbgroupedit</H1
NAME="SMBGROUPEDIT">smbgroupedit</H1
><DIV
CLASS="REFNAMEDIV"
><A
@ -29,15 +28,13 @@ NAME="AEN5"
><DIV
CLASS="REFSYNOPSISDIV"
><A
NAME="AEN8"
></A
><H2
NAME="AEN8"><H2
>Synopsis</H2
><P
><B
CLASS="COMMAND"
>smbroupedit</B
> [-v [l|s]] [-a UNIX-groupname [-d NT-groupname|-p privilege|]]</P
> [-v [l|s]] [-a UNIX-groupname [-d NT-groupname|-p privilege|]]</P
></DIV
><DIV
CLASS="REFSECT1"
@ -89,6 +86,12 @@ CLASS="VARIABLELIST"
><P
>give a long listing, of the format:</P
><P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="90%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>"NT Group Name"
@ -97,10 +100,19 @@ CLASS="PROGRAMLISTING"
Group type :
Comment :
Privilege :</PRE
></TD
></TR
></TABLE
></P
><P
>For examples,</P
><P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="90%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>Users
@ -109,6 +121,9 @@ CLASS="PROGRAMLISTING"
Group type: Local group
Comment :
Privilege : No privilege</PRE
></TD
></TR
></TABLE
></P
></DD
><DT
@ -117,16 +132,34 @@ CLASS="PROGRAMLISTING"
><P
>display a short listing of the format:</P
><P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="90%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>NTGroupName(SID) -&#62; UnixGroupName</PRE
></TD
></TR
></TABLE
></P
><P
>For example,</P
><P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="90%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>Users (S-1-5-32-545) -&#62; -1</PRE
></TD
></TR
></TABLE
></P
></DD
></DL
@ -211,6 +244,12 @@ TYPE="a"
>Get the SID for the Windows NT "Domain Admins"
group:</P
><P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="90%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
><TT
@ -221,6 +260,9 @@ CLASS="COMMAND"
>smbgroupedit -vs | grep "Domain Admins"</B
>
Domain Admins (S-1-5-21-1108995562-3116817432-1375597819-512) -&#62; -1</PRE
></TD
></TR
></TABLE
></P
></LI
><LI
@ -229,6 +271,12 @@ Domain Admins (S-1-5-21-1108995562-3116817432-1375597819-512) -&#62; -1</PRE
"Domain Admins" group, by running the command:
</P
><P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="90%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
><TT
@ -238,16 +286,16 @@ CLASS="PROMPT"
CLASS="COMMAND"
>smbgroupedit \
-c S-1-5-21-1108995562-3116817432-1375597819-512 \
-u domadm</B
-u domadm -td</B
></PRE
></TD
></TR
></TABLE
></P
><P
> <SPAN
CLASS="emphasis"
><I
> <I
CLASS="EMPHASIS"
>warning:</I
></SPAN
> don't copy and paste this sample, the
Domain Admins SID (the S-1-5-21-...-512) is different for every PDC.
</P
@ -258,6 +306,12 @@ CLASS="EMPHASIS"
><P
>To verify that your mapping has taken effect:</P
><P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
><TT
@ -268,12 +322,21 @@ CLASS="COMMAND"
>smbgroupedit -vs|grep "Domain Admins"</B
>
Domain Admins (S-1-5-21-1108995562-3116817432-1375597819-512) -&#62; domadm</PRE
></TD
></TR
></TABLE
></P
><P
>To give access to a certain directory on a domain member machine (an
NT/W2K or a samba server running winbind) to some users who are member
of a group on your samba PDC, flag that group as a domain group:</P
><P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
><TT
@ -283,6 +346,9 @@ CLASS="PROMPT"
CLASS="COMMAND"
>smbgroupedit -a unixgroup -td</B
></PRE
></TD
></TR
></TABLE
></P
></DIV
><DIV

2
docs/htmldocs/smbpasswd.5.html
View File

@ -301,7 +301,7 @@ NAME="AEN73"
><H2
>VERSION</H2
><P
>This man page is correct for version 2.2 of
>This man page is correct for version 3.0 of
the Samba suite.</P
></DIV
><DIV

37
docs/htmldocs/smbsh.1.html
View File

@ -1,11 +1,12 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
<HTML
><HEAD
><TITLE
>smbsh</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -15,9 +16,7 @@ VLINK="#840084"
ALINK="#0000FF"
><H1
><A
NAME="SMBSH"
></A
>smbsh</H1
NAME="SMBSH">smbsh</H1
><DIV
CLASS="REFNAMEDIV"
><A
@ -30,15 +29,13 @@ NAME="AEN5"
><DIV
CLASS="REFSYNOPSISDIV"
><A
NAME="AEN8"
></A
><H2
NAME="AEN8"><H2
>Synopsis</H2
><P
><B
CLASS="COMMAND"
>smbsh</B
> [-W workgroup] [-U username] [-P prefix] [-R &lt;name resolve order&gt;] [-d &lt;debug level&gt;] [-l logfile] [-L libdir]</P
> [-W workgroup] [-U username] [-P prefix] [-R &#60;name resolve order&#62;] [-d &#60;debug level&#62;] [-l logfile] [-L libdir]</P
></DIV
><DIV
CLASS="REFSECT1"
@ -115,17 +112,14 @@ CLASS="FILENAME"
>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
<I
CLASS="EMPHASIS"
>smb</I
></SPAN
>.
</P
></DD
><DT
>-R &lt;name resolve order&gt;</DT
>-R &#60;name resolve order&#62;</DT
><DD
><P
>This option is used to determine what naming
@ -236,7 +230,7 @@ CLASS="FILENAME"
order. </P
></DD
><DT
>-d &lt;debug level&gt;</DT
>-d &#60;debug level&#62;</DT
><DD
><P
>debug level is an integer from 0 to 10.</P
@ -305,6 +299,12 @@ CLASS="COMMAND"
that authenticates you to the machine running the Windows NT
operating system.</P
><P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
> <TT
@ -335,6 +335,9 @@ CLASS="USERINPUT"
></TT
>
</PRE
></TD
></TR
></TABLE
></P
><P
>Any dynamically linked command you execute from
@ -354,7 +357,7 @@ CLASS="COMMAND"
the workgroup MYGROUP. The command
<B
CLASS="COMMAND"
>ls /smb/MYGROUP/&lt;machine-name&gt;</B
>ls /smb/MYGROUP/&#60;machine-name&#62;</B
> will show the share
names for that machine. You could then, for example, use the <B
CLASS="COMMAND"
@ -376,7 +379,7 @@ NAME="AEN112"
><H2
>VERSION</H2
><P
>This man page is correct for version 2.2 of
>This man page is correct for version 3.0 of
the Samba suite.</P
></DIV
><DIV

111
docs/htmldocs/speed.html
View File

@ -9,12 +9,15 @@ CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
REL="UP"
TITLE="Optional configuration"
HREF="optional.html"><LINK
REL="PREVIOUS"
TITLE="Quick Cross Subnet Browsing / Cross Workgroup Browsing guide"
HREF="browsing-quick.html"><LINK
TITLE="Group mapping HOWTO"
HREF="groupmapping.html"><LINK
REL="NEXT"
TITLE="HOWTO Access Samba source code via CVS"
HREF="cvs-access.html"></HEAD
TITLE="Appendixes"
HREF="appendixes.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="browsing-quick.html"
HREF="groupmapping.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="cvs-access.html"
HREF="appendixes.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,15 +74,15 @@ CLASS="CHAPTER"
><A
NAME="SPEED"
></A
>Chapter 17. Samba performance issues</H1
>Chapter 23. Samba performance issues</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2742"
NAME="AEN3065"
></A
>17.1. Comparisons</H1
>23.1. Comparisons</H1
><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
@ -108,17 +111,17 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2748"
NAME="AEN3071"
></A
>17.2. Oplocks</H1
>23.2. Oplocks</H1
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2750"
NAME="AEN3073"
></A
>17.2.1. Overview</H2
>23.2.1. Overview</H2
><P
>Oplocks are the way that SMB clients get permission from a server to
locally cache file operations. If a server grants an oplock
@ -152,9 +155,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2758"
NAME="AEN3081"
></A
>17.2.2. Level2 Oplocks</H2
>23.2.2. Level2 Oplocks</H2
><P
>With Samba 2.0.5 a new capability - level2 (read only) oplocks is
supported (although the option is off by default - see the smb.conf
@ -176,9 +179,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN2764"
NAME="AEN3087"
></A
>17.2.3. Old 'fake oplocks' option - deprecated</H2
>23.2.3. Old 'fake oplocks' option - deprecated</H2
><P
>Samba can also fake oplocks, by granting a oplock whenever a client
asks for one. This is controlled using the smb.conf option "fake
@ -197,9 +200,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2768"
NAME="AEN3091"
></A
>17.3. Socket options</H1
>23.3. Socket options</H1
><P
>There are a number of socket options that can greatly affect the
performance of a TCP based server like Samba.</P
@ -225,9 +228,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2775"
NAME="AEN3098"
></A
>17.4. Read size</H1
>23.4. Read size</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
@ -251,9 +254,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2780"
NAME="AEN3103"
></A
>17.5. Max xmit</H1
>23.5. Max xmit</H1
><P
>At startup the client and server negotiate a "maximum transmit" size,
which limits the size of nearly all SMB commands. You can set the
@ -274,9 +277,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2785"
NAME="AEN3108"
></A
>17.6. Locking</H1
>23.6. Locking</H1
><P
>By default Samba does not implement strict locking on each read/write
call (although it did in previous versions). If you enable strict
@ -291,9 +294,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2789"
NAME="AEN3112"
></A
>17.7. Share modes</H1
>23.7. Share modes</H1
><P
>Some people find that opening files is very slow. This is often
because of the "share modes" code needed to fully implement the dos
@ -321,9 +324,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2794"
NAME="AEN3117"
></A
>17.8. Log level</H1
>23.8. Log level</H1
><P
>If you set the log level (also known as "debug level") higher than 2
then you may suffer a large drop in performance. This is because the
@ -335,9 +338,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2797"
NAME="AEN3120"
></A
>17.9. Wide lines</H1
>23.9. Wide lines</H1
><P
>The "wide links" option is now enabled by default, but if you disable
it (for better security) then you may suffer a performance hit in
@ -349,9 +352,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2800"
NAME="AEN3123"
></A
>17.10. Read raw</H1
>23.10. Read raw</H1
><P
>The "read raw" operation is designed to be an optimised, low-latency
file read operation. A server may choose to not support it,
@ -371,9 +374,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2805"
NAME="AEN3128"
></A
>17.11. Write raw</H1
>23.11. Write raw</H1
><P
>The "write raw" operation is designed to be an optimised, low-latency
file write operation. A server may choose to not support it,
@ -388,9 +391,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2809"
NAME="AEN3132"
></A
>17.12. Read prediction</H1
>23.12. Read prediction</H1
><P
>Samba can do read prediction on some of the SMB commands. Read
prediction means that Samba reads some extra data on the last file it
@ -414,9 +417,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2816"
NAME="AEN3139"
></A
>17.13. Memory mapping</H1
>23.13. Memory mapping</H1
><P
>Samba supports reading files via memory mapping them. One some
machines this can give a large boost to performance, on others it
@ -435,9 +438,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2821"
NAME="AEN3144"
></A
>17.14. Slow Clients</H1
>23.14. Slow Clients</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
@ -452,9 +455,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2825"
NAME="AEN3148"
></A
>17.15. Slow Logins</H1
>23.15. Slow Logins</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
@ -465,9 +468,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2828"
NAME="AEN3151"
></A
>17.16. Client tuning</H1
>23.16. Client tuning</H1
><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
@ -569,9 +572,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN2860"
NAME="AEN3183"
></A
>17.17. My Results</H1
>23.17. My Results</H1
><P
>Some people want to see real numbers in a document like this, so here
they are. I have a 486sx33 client running WfWg 3.11 with the 3.11b
@ -610,7 +613,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="browsing-quick.html"
HREF="groupmapping.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -628,7 +631,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="cvs-access.html"
HREF="appendixes.html"
ACCESSKEY="N"
>Next</A
></TD
@ -638,17 +641,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Quick Cross Subnet Browsing / Cross Workgroup Browsing guide</TD
>Group mapping HOWTO</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="optional.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>HOWTO Access Samba source code via CVS</TD
>Appendixes</TD
></TR
></TABLE
></DIV

69
docs/htmldocs/unix-permissions.html
View File

@ -9,12 +9,16 @@ CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
REL="UP"
TITLE="Optional configuration"
HREF="optional.html"><LINK
REL="PREVIOUS"
TITLE="Hosting a Microsoft Distributed File System tree on Samba"
HREF="msdfs.html"><LINK
TITLE="Integrating MS Windows networks with Samba"
HREF="integrate-ms-networks.html"><LINK
REL="NEXT"
TITLE="Printing Support in Samba 2.2.x"
HREF="printing.html"></HEAD
TITLE="Configuring PAM for distributed but centrally
managed authentication"
HREF="pam.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -42,7 +46,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="msdfs.html"
HREF="integrate-ms-networks.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +60,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="printing.html"
HREF="pam.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,15 +75,15 @@ CLASS="CHAPTER"
><A
NAME="UNIX-PERMISSIONS"
></A
>Chapter 5. UNIX Permission Bits and Windows NT Access Control Lists</H1
>Chapter 12. UNIX Permission Bits and Windows NT Access Control Lists</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN580"
NAME="AEN1618"
></A
>5.1. Viewing and changing UNIX permissions using the NT
>12.1. Viewing and changing UNIX permissions using the NT
security dialogs</H1
><P
>New in the Samba 2.0.4 release is the ability for Windows
@ -116,9 +120,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN589"
NAME="AEN1627"
></A
>5.2. How to view file security on a Samba share</H1
>12.2. How to view file security on a Samba share</H1
><P
>From an NT 4.0 client, single-click with the right
mouse button on any file or directory in a Samba mounted
@ -186,9 +190,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN600"
NAME="AEN1638"
></A
>5.3. Viewing file ownership</H1
>12.3. Viewing file ownership</H1
><P
>Clicking on the <B
CLASS="COMMAND"
@ -280,9 +284,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN620"
NAME="AEN1658"
></A
>5.4. Viewing file or directory permissions</H1
>12.4. Viewing file or directory permissions</H1
><P
>The third button is the <B
CLASS="COMMAND"
@ -342,9 +346,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN635"
NAME="AEN1673"
></A
>5.4.1. File Permissions</H2
>12.4.1. File Permissions</H2
><P
>The standard UNIX user/group/world triple and
the corresponding "read", "write", "execute" permissions
@ -404,9 +408,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN649"
NAME="AEN1687"
></A
>5.4.2. Directory Permissions</H2
>12.4.2. Directory Permissions</H2
><P
>Directories on an NT NTFS file system have two
different sets of permissions. The first set of permissions
@ -436,9 +440,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN656"
NAME="AEN1694"
></A
>5.5. Modifying file or directory permissions</H1
>12.5. Modifying file or directory permissions</H1
><P
>Modifying file and directory permissions is as simple
as changing the displayed permissions in the dialog box, and
@ -534,9 +538,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN678"
NAME="AEN1716"
></A
>5.6. Interaction with the standard Samba create mask
>12.6. Interaction with the standard Samba create mask
parameters</H1
><P
>Note that with Samba 2.0.5 there are four new parameters
@ -811,9 +815,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN742"
NAME="AEN1780"
></A
>5.7. Interaction with the standard Samba file attribute
>12.7. Interaction with the standard Samba file attribute
mapping</H1
><P
>Samba maps some of the DOS attribute bits (such as "read
@ -870,7 +874,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="msdfs.html"
HREF="integrate-ms-networks.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -888,7 +892,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="printing.html"
HREF="pam.html"
ACCESSKEY="N"
>Next</A
></TD
@ -898,17 +902,22 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Hosting a Microsoft Distributed File System tree on Samba</TD
>Integrating MS Windows networks with Samba</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="optional.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Printing Support in Samba 2.2.x</TD
>Configuring PAM for distributed but centrally
managed authentication</TD
></TR
></TABLE
></DIV

15
docs/htmldocs/wbinfo.1.html
View File

@ -1,12 +1,11 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
<!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.76b+
"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -16,7 +15,9 @@ VLINK="#840084"
ALINK="#0000FF"
><H1
><A
NAME="WBINFO">wbinfo</H1
NAME="WBINFO"
></A
>wbinfo</H1
><DIV
CLASS="REFNAMEDIV"
><A
@ -28,13 +29,15 @@ NAME="AEN5"
><DIV
CLASS="REFSYNOPSISDIV"
><A
NAME="AEN8"><H2
NAME="AEN8"
></A
><H2
>Synopsis</H2
><P
><B
CLASS="COMMAND"
>wbinfo</B
> [-u] [-g] [-i ip] [-N netbios-name] [-n name] [-s sid] [-U uid] [-G gid] [-S sid] [-Y sid] [-t] [-m] [-r user] [-a user%password] [-A user%password] [-p]</P
> [-u] [-g] [-i ip] [-N netbios-name] [-n name] [-s sid] [-U uid] [-G gid] [-S sid] [-Y sid] [-t] [-m] [-r user] [-a user%password] [-A user%password] [-p]</P
></DIV
><DIV
CLASS="REFSECT1"

175
docs/htmldocs/wfw_slip.htm
View File

@ -1,175 +0,0 @@
<HTML>
<HEAD>
<TITLE>Peter Karrer Announces SLIP for WFW</TITLE>
</HEAD>
<BODY>
<H1><I>Winserve</I></H1>
<HR>
<H2><I>Peter Karrer Announces SLIP for WFW</I></H2>
[NEW 03-22-95)
<HR>
<B>Hello,</B>
<P>
I've discovered a way to run WfW's TCP/IP-32 over a SLIP packet driver. This
allows WfW users to do Windows networking over dialup lines just like it is
possible with NT and the Windows 95 beta!
<P>
For instance, you can mount Microsoft's FTP server as a network drive in File
Manager or connect to an MS Mail post office over the Internet. Of course,
the usual Internet stuff works as well. Another interesting site is
WINSERVE.001; check out www.winserve.com.
<HR>
This method should work with any class 1 (Ethernet II) packet driver. However,
I'm not in a position to try anything else than SLIPPER/CSLIPPER.
<HR>
<H3>Files you need:</H3>
<B>WFWT32.EXE:</B> ftp://ftp.microsoft.com/bussys/msclient/wfw/wfwt32.exe
<P>
Microsoft's free TCP/IP for WfW. It's a self-extracting archive which
should be executed in an empty directory.
<P>
<B>SLIPPER.EXE:</B> ftp://biocserver.bioc.cwru.edu/pub/dos/slipper/slippr15.zip
<P>
Peter Tattam's SLIP packet driver. CSLIPPER.EXE is a variant which supports
VJ header compression.
<P>
<B>PDETHER.EXE:</B> ftp://sjf-lwp.idz.sjf.novell.com/odi/pdether/pde105.zip
<P>
Don Provan's ODI-over-Packet Driver shim. This *must* be version 1.05 (or
above).
<P>
<B>LSL.COM:</B>
<P>
Novell's LAN Support Layer. If you're an owner of Windows 3.10, you'll
have it on one of your install disks. Use "expand a:lsl.co_ lsl.com" to
expand it. Microsoft has stopped bundling LSL.COM with WfW 3.11, though.
The newest version of LSL.COM can be downloaded as part of
ftp://ftp.novell.com/pub/netware/nwos/dosclnt12/vlms/vlmup2.exe.
However, it's not clear if this one may be legally used outside Netware
environments.
<P>
<B>NET.CFG:</B>
<P>
A configuration file for LSL and PDETHER. It should contain the following
text:
<P>
<PRE>
Link Support
Buffers 8 1600
Link Driver PDETHER
Int 60
Frame Ethernet_II
Protocol IP 800 Ethernet_II
Protocol ARP 806 Ethernet_II
Protocol RARP 8035 Ethernet_II
</PRE>
<P>
<B>DISCOMX.COM:</B>
<P>
A little hack of mine to disable the COM port used by the SLIP packet driver.
Usage is e.g. "discomx 2" to disable COM2. This should be run before
starting WfW, otherwise you'll get "device conflict" messages. Here it is:
<P><PRE>
begin 644 discomx.com
F,=N)V8H.@`"P(+^!`/.N3XH="=MT!DN`XP/1XS')!R:)CP`$S2``
`
end
</PRE>
(Save this text to disk as <I>filename</I>, then run "uudecode <I>filename</I>".
uudecode can be found, for instance, at
ftp://ftp.switch.ch/mirror/simtel/msdos/starter/uudecode.com )
<P>
<B>LMHOSTS:</B>
<P>
An optional file which should be stored in your Windows subdirectory. It is
used to map NetBIOS computer names to IP addresses. Example:
<P>
<PRE>
198.105.232.1 ftp #PRE # ftp.microsoft.com
204.118.34.11 winserve.001 #PRE # Winserve
</PRE>
<HR>
<H3>How to install it:</H3>
<P>
<UL>
<LI>Put the files mentioned above into a directory, e.g. C:\SLIP.
<P>
<LI>Put the following lines into AUTOEXEC.BAT:
<P><PRE>
cd \slip
slipper com1 vec=60 baud=57600 ether (may vary with your modem setup)
lsl
pdether
discomx 1 (must correspond to SLIPPER's COM port)
</PRE>
(If you use another vec= setting, you must update that in NET.CFG as well.)
Use CSLIPPER instead of SLIPPER if your SLIP provider supports VJC.
<P>
<LI>Start WfW.
<UL>
<LI>Under Windows Setup, choose "Change Network Settings".
<LI>Select "Install Microsoft Windows Network".
<LI>In "Drivers...", choose "Add Adapter"
and install the "IPXODI Support driver (Ethernet) [ODI/NDIS3]".
<LI>In "Add Protocols...", select "Unlisted or Updated Protocol". When asked for a
driver disk, enter the directory where you expanded WFWT32.EXE.
<LI>Configure TCP/IP (IP address, enable LMHOSTS lookup, try 204.118.34.11 as primary
WINS server). Remove all other protocols (NetBEUI, IPX/SPX).
</UL>
<P>
<LI>Windows will probably update the first lines of AUTOEXEC.BAT with
<P>
<PRE>
c:\windows\net start
c:\windows\odihlp.exe.
</PRE>
The "odihlp" line must be moved behind the "pdether" line.
<P>
<LI>Windows will also update NET.CFG with some "Frame" lines. These must
be removed (except "Frame Ethernet_II").
<P>
<LI>Somehow, you will have to dial in to your SLIP provider. I do it manually
before slipper (or cslipper) gets loaded, using a DOS-based terminal program.
But there are some automatic dialers around. I've seen recommendations for
ftp://mvmpc9.ciw.uni-karlsruhe.de/x-slip/slip_it.exe.
<P>
<LI>To connect to Microsoft's FTP server (or Winserve) go into File Manager,
choose "Connect Network drive" and enter "\\ftp" or "\\winserve.001" into
the "Path:" field.
</UL>
<HR>
<H3>How it works:</H3>
<P>
Microsoft's TCP/IP-32 requires an NDIS3 interface. NDIS is Microsoft's way
to interface with a network.
<P>
WfW also contains an NDIS3-over-ODI "shim", whose real mode component is
ODIHLP.EXE. ODI is Novell's way to interface with a network.
<P>
SLIPPER is a Packet Driver (PD) for use over serial lines. PDs are everybody
else's way to interface with a network. SLIPPER's "ether" option makes it
look like an Ethernet PD to applications using it.
<P>
A "shim" is a program which simulates a network application programming
interface on top of another.
<P>
There is no NDIS SLIP driver which would work with WfW.
<P>
There is no NDIS-over-PD shim.
<P>
However, there's an ODI-over-PD shim (PDETHER) and an NDIS-over-ODI shim
(ODIHLP etc.)
<P>
OK, so let's do NDIS-over-ODI-over-PD!
<P>
This should have worked all the time; however, a non-feature in PDETHER
versions < 1.05 has prevented the method from functioning until now.
<HR>
<B>Questions, suggestions etc. please to
<P>
<PRE>
Peter Karrer pkarrer@ife.ee.ethz.ch
</PRE>
</B>
</BODY>
</HTML>

147
docs/htmldocs/winbind.html
View File

@ -9,12 +9,15 @@ CONTENT="Modular DocBook HTML Stylesheet Version 1.77"><LINK
REL="HOME"
TITLE="SAMBA Project Documentation"
HREF="samba-howto-collection.html"><LINK
REL="UP"
TITLE="Optional configuration"
HREF="optional.html"><LINK
REL="PREVIOUS"
TITLE="security = domain in Samba 2.x"
HREF="domain-security.html"><LINK
TITLE="Printing Support"
HREF="printing.html"><LINK
REL="NEXT"
TITLE="How to Configure Samba 2.2 as a Primary Domain Controller"
HREF="samba-pdc.html"></HEAD
TITLE="Passdb MySQL plugin"
HREF="pdb-mysql.html"></HEAD
><BODY
CLASS="CHAPTER"
BGCOLOR="#FFFFFF"
@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="domain-security.html"
HREF="printing.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -56,7 +59,7 @@ WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="samba-pdc.html"
HREF="pdb-mysql.html"
ACCESSKEY="N"
>Next</A
></TD
@ -71,15 +74,15 @@ CLASS="CHAPTER"
><A
NAME="WINBIND"
></A
>Chapter 10. Unified Logons between Windows NT and UNIX using Winbind</H1
>Chapter 16. Unified Logons between Windows NT and UNIX using Winbind</H1
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1255"
NAME="AEN2238"
></A
>10.1. Abstract</H1
>16.1. Abstract</H1
><P
>Integration of UNIX and Microsoft Windows NT through
a unified logon has been considered a "holy grail" in heterogeneous
@ -104,9 +107,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1259"
NAME="AEN2242"
></A
>10.2. Introduction</H1
>16.2. Introduction</H1
><P
>It is well known that UNIX and Microsoft Windows NT have
different models for representing user and group information and
@ -158,9 +161,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1272"
NAME="AEN2255"
></A
>10.3. What Winbind Provides</H1
>16.3. What Winbind Provides</H1
><P
>Winbind unifies UNIX and Windows NT account management by
allowing a UNIX box to become a full member of a NT domain. Once
@ -200,9 +203,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1279"
NAME="AEN2262"
></A
>10.3.1. Target Uses</H2
>16.3.1. Target Uses</H2
><P
>Winbind is targeted at organizations that have an
existing NT based domain infrastructure into which they wish
@ -224,9 +227,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1283"
NAME="AEN2266"
></A
>10.4. How Winbind Works</H1
>16.4. How Winbind Works</H1
><P
>The winbind system is designed around a client/server
architecture. A long running <B
@ -244,9 +247,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1288"
NAME="AEN2271"
></A
>10.4.1. Microsoft Remote Procedure Calls</H2
>16.4.1. Microsoft Remote Procedure Calls</H2
><P
>Over the last two years, efforts have been underway
by various Samba Team members to decode various aspects of
@ -270,9 +273,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1292"
NAME="AEN2275"
></A
>10.4.2. Name Service Switch</H2
>16.4.2. Name Service Switch</H2
><P
>The Name Service Switch, or NSS, is a feature that is
present in many UNIX operating systems. It allows system
@ -350,9 +353,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1308"
NAME="AEN2291"
></A
>10.4.3. Pluggable Authentication Modules</H2
>16.4.3. Pluggable Authentication Modules</H2
><P
>Pluggable Authentication Modules, also known as PAM,
is a system for abstracting authentication and authorization
@ -399,9 +402,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1316"
NAME="AEN2299"
></A
>10.4.4. User and Group ID Allocation</H2
>16.4.4. User and Group ID Allocation</H2
><P
>When a user or group is created under Windows NT
is it allocated a numerical relative identifier (RID). This is
@ -425,9 +428,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1320"
NAME="AEN2303"
></A
>10.4.5. Result Caching</H2
>16.4.5. Result Caching</H2
><P
>An active system can generate a lot of user and group
name lookups. To reduce the network cost of these lookups winbind
@ -448,9 +451,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1323"
NAME="AEN2306"
></A
>10.5. Installation and Configuration</H1
>16.5. Installation and Configuration</H1
><P
>Many thanks to John Trostel <A
HREF="mailto:jtrostel@snapserver.com"
@ -475,9 +478,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1330"
NAME="AEN2313"
></A
>10.5.1. Introduction</H2
>16.5.1. Introduction</H2
><P
>This HOWTO describes the procedures used to get winbind up and
running on my RedHat 7.1 system. Winbind is capable of providing access
@ -534,9 +537,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1343"
NAME="AEN2326"
></A
>10.5.2. Requirements</H2
>16.5.2. Requirements</H2
><P
>If you have a samba configuration file that you are currently
using... <SPAN
@ -574,7 +577,7 @@ CLASS="FILENAME"
> back to the original state they were in if
you get frustrated with the way things are going. ;-)</P
><P
>The latest version of SAMBA (version 2.2.2 as of this writing), now
>The latest version of SAMBA (version 3.0 as of this writing), now
includes a functioning winbindd daemon. Please refer to the
<A
HREF="http://samba.org/"
@ -604,9 +607,9 @@ CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN1357"
NAME="AEN2340"
></A
>10.5.3. Testing Things Out</H2
>16.5.3. Testing Things Out</H2
><P
>Before starting, it is probably best to kill off all the SAMBA
related daemons running on your server. Kill off all <B
@ -649,9 +652,9 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN1368"
NAME="AEN2351"
></A
>10.5.3.1. Configure and compile SAMBA</H3
>16.5.3.1. Configure and compile SAMBA</H3
><P
>The configuration and compilation of SAMBA is pretty straightforward.
The first three steps may not be necessary depending upon
@ -715,9 +718,9 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN1387"
NAME="AEN2370"
></A
>10.5.3.2. Configure <TT
>16.5.3.2. Configure <TT
CLASS="FILENAME"
>nsswitch.conf</TT
> and the
@ -820,9 +823,9 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN1420"
NAME="AEN2403"
></A
>10.5.3.3. Configure smb.conf</H3
>16.5.3.3. Configure smb.conf</H3
><P
>Several parameters are needed in the smb.conf file to control
the behavior of <B
@ -895,9 +898,9 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN1436"
NAME="AEN2419"
></A
>10.5.3.4. Join the SAMBA server to the PDC domain</H3
>16.5.3.4. Join the SAMBA server to the PDC domain</H3
><P
>Enter the following command to make the SAMBA server join the
PDC domain, where <TT
@ -919,7 +922,7 @@ CLASS="PROMPT"
>root#</TT
> <B
CLASS="COMMAND"
>/usr/local/samba/bin/net rpc join -s PDC -U Administrator</B
>/usr/local/samba/bin/net rpc join -S PDC -U Administrator</B
></P
><P
>The proper response to the command should be: "Joined the domain
@ -941,9 +944,9 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN1447"
NAME="AEN2430"
></A
>10.5.3.5. Start up the winbindd daemon and test it!</H3
>16.5.3.5. Start up the winbindd daemon and test it!</H3
><P
>Eventually, you will want to modify your smb startup script to
automatically invoke the winbindd daemon when the other parts of
@ -1064,17 +1067,17 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN1483"
NAME="AEN2466"
></A
>10.5.3.6. Fix the init.d startup scripts</H3
>16.5.3.6. Fix the init.d startup scripts</H3
><DIV
CLASS="SECT4"
><H4
CLASS="SECT4"
><A
NAME="AEN1485"
NAME="AEN2468"
></A
>10.5.3.6.1. Linux</H4
>16.5.3.6.1. Linux</H4
><P
>The <B
CLASS="COMMAND"
@ -1168,9 +1171,9 @@ CLASS="SECT4"
><H4
CLASS="SECT4"
><A
NAME="AEN1502"
NAME="AEN2485"
></A
>10.5.3.6.2. Solaris</H4
>16.5.3.6.2. Solaris</H4
><P
>On solaris, you need to modify the
<TT
@ -1239,9 +1242,9 @@ CLASS="SECT4"
><H4
CLASS="SECT4"
><A
NAME="AEN1509"
NAME="AEN2492"
></A
>10.5.3.6.3. Restarting</H4
>16.5.3.6.3. Restarting</H4
><P
>If you restart the <B
CLASS="COMMAND"
@ -1263,9 +1266,9 @@ CLASS="SECT3"
><H3
CLASS="SECT3"
><A
NAME="AEN1515"
NAME="AEN2498"
></A
>10.5.3.7. Configure Winbind and PAM</H3
>16.5.3.7. Configure Winbind and PAM</H3
><P
>If you have made it this far, you know that winbindd and samba are working
together. If you want to use winbind to provide authentication for other
@ -1321,9 +1324,9 @@ CLASS="SECT4"
><H4
CLASS="SECT4"
><A
NAME="AEN1532"
NAME="AEN2515"
></A
>10.5.3.7.1. Linux/FreeBSD-specific PAM configuration</H4
>16.5.3.7.1. Linux/FreeBSD-specific PAM configuration</H4
><P
>The <TT
CLASS="FILENAME"
@ -1450,9 +1453,9 @@ CLASS="SECT4"
><H4
CLASS="SECT4"
><A
NAME="AEN1565"
NAME="AEN2548"
></A
>10.5.3.7.2. Solaris-specific configuration</H4
>16.5.3.7.2. Solaris-specific configuration</H4
><P
>The /etc/pam.conf needs to be changed. I changed this file so that my Domain
users can logon both locally as well as telnet.The following are the changes
@ -1537,9 +1540,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1572"
NAME="AEN2555"
></A
>10.6. Limitations</H1
>16.6. Limitations</H1
><P
>Winbind has a number of limitations in its current
released version that we hope to overcome in future
@ -1578,9 +1581,9 @@ CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN1582"
NAME="AEN2565"
></A
>10.7. Conclusion</H1
>16.7. Conclusion</H1
><P
>The winbind system, through the use of the Name Service
Switch, Pluggable Authentication Modules, and appropriate
@ -1606,7 +1609,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="domain-security.html"
HREF="printing.html"
ACCESSKEY="P"
>Prev</A
></TD
@ -1624,7 +1627,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="samba-pdc.html"
HREF="pdb-mysql.html"
ACCESSKEY="N"
>Next</A
></TD
@ -1634,17 +1637,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>security = domain in Samba 2.x</TD
>Printing Support</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><A
HREF="optional.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>How to Configure Samba 2.2 as a Primary Domain Controller</TD
>Passdb MySQL plugin</TD
></TR
></TABLE
></DIV

161
docs/htmldocs/winbindd.8.html
View File

@ -1,11 +1,12 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN">
<HTML
><HEAD
><TITLE
>winbindd</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.77"></HEAD
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
@ -15,9 +16,7 @@ VLINK="#840084"
ALINK="#0000FF"
><H1
><A
NAME="WINBINDD"
></A
>winbindd</H1
NAME="WINBINDD">winbindd</H1
><DIV
CLASS="REFNAMEDIV"
><A
@ -30,20 +29,18 @@ NAME="AEN5"
><DIV
CLASS="REFSYNOPSISDIV"
><A
NAME="AEN8"
></A
><H2
NAME="AEN8"><H2
>Synopsis</H2
><P
><B
CLASS="COMMAND"
>winbindd</B
> [-i] [-d &lt;debug level&gt;] [-s &lt;smb config file&gt;]</P
> [-F] [-S] [-i] [-B] [-d &#60;debug level&#62;] [-s &#60;smb config file&#62;] [-n]</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN14"
NAME="AEN18"
></A
><H2
>DESCRIPTION</H2
@ -171,11 +168,20 @@ CLASS="FILENAME"
> and then from the
Windows NT server. </P
><P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>passwd: files winbind
group: files winbind
</PRE
></TD
></TR
></TABLE
></P
><P
>The following simple configuration in the
@ -192,7 +198,7 @@ CLASS="FILENAME"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN57"
NAME="AEN61"
></A
><H2
>OPTIONS</H2
@ -202,6 +208,48 @@ NAME="AEN57"
CLASS="VARIABLELIST"
><DL
><DT
>-F</DT
><DD
><P
>If specified, this parameter causes
the main <B
CLASS="COMMAND"
>winbindd</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"
>winbindd</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
>
package, or the AIX process monitor.
</P
></DD
><DT
>-S</DT
><DD
><P
>If specified, this parameter causes
<B
CLASS="COMMAND"
>winbindd</B
> to log to standard output rather
than a file.</P
></DD
><DT
>-d debuglevel</DT
><DD
><P
@ -223,7 +271,49 @@ CLASS="COMMAND"
of <B
CLASS="COMMAND"
>winbindd</B
> is required. </P
> is required.
<B
CLASS="COMMAND"
>winbindd</B
> also logs to standard output,
as if the <B
CLASS="COMMAND"
>-S</B
> parameter had been given.
</P
></DD
><DT
>-n</DT
><DD
><P
>Disable caching. This means winbindd will
always have to wait for a response from the domain controller
before it can respond to a client and this thus makes things
slower. The results will however be more accurate, since
results from the cache might not be up-to-date. This
might also temporarily hang winbindd if the DC doesn't respond.
</P
></DD
><DT
>-B</DT
><DD
><P
>Dual daemon mode. This means winbindd will run
as 2 threads. The first will answer all requests from the cache,
thus making responses to clients faster. The other will
update the cache for the query that the first has just responded.
Advantage of this is that responses are accurate and fast.
</P
></DD
><DT
>-s|--conf=smb.conf</DT
><DD
><P
>Specifies the location of the all-important
<TT
CLASS="FILENAME"
>smb.conf</TT
> file. </P
></DD
></DL
></DIV
@ -231,7 +321,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN70"
NAME="AEN103"
></A
><H2
>NAME AND ID RESOLUTION</H2
@ -262,7 +352,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN76"
NAME="AEN109"
></A
><H2
>CONFIGURATION</H2
@ -402,7 +492,7 @@ CLASS="PARAMETER"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN118"
NAME="AEN151"
></A
><H2
>EXAMPLE SETUP</H2
@ -417,11 +507,20 @@ CLASS="FILENAME"
> put the
following:</P
><P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>passwd: files winbind
group: files winbind
</PRE
></TD
></TR
></TABLE
></P
><P
>In <TT
@ -435,6 +534,12 @@ CLASS="PARAMETER"
></TT
> lines with something like this: </P
><P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>auth required /lib/security/pam_securetty.so
@ -442,6 +547,9 @@ auth required /lib/security/pam_nologin.so
auth sufficient /lib/security/pam_winbind.so
auth required /lib/security/pam_pwdb.so use_first_pass shadow nullok
</PRE
></TD
></TR
></TABLE
></P
><P
>Note in particular the use of the <TT
@ -522,6 +630,12 @@ CLASS="FILENAME"
> containing directives like the
following: </P
><P
><TABLE
BORDER="0"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><PRE
CLASS="PROGRAMLISTING"
>[global]
@ -535,6 +649,9 @@ CLASS="PROGRAMLISTING"
security = domain
password server = *
</PRE
></TD
></TR
></TABLE
></P
><P
>Now start winbindd and you should find that your user and
@ -553,7 +670,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN157"
NAME="AEN190"
></A
><H2
>NOTES</H2
@ -611,7 +728,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN173"
NAME="AEN206"
></A
><H2
>SIGNALS</H2
@ -662,7 +779,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN190"
NAME="AEN223"
></A
><H2
>FILES</H2
@ -738,18 +855,18 @@ CLASS="FILENAME"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN219"
NAME="AEN252"
></A
><H2
>VERSION</H2
><P
>This man page is correct for version 2.2 of
>This man page is correct for version 3.0 of
the Samba suite.</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN222"
NAME="AEN255"
></A
><H2
>SEE ALSO</H2
@ -777,7 +894,7 @@ TARGET="_top"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN229"
NAME="AEN262"
></A
><H2
>AUTHOR</H2

2
docs/manpages/findsmb.1
View File

@ -3,7 +3,7 @@
.\" <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" "26 November 2002" "" ""
.TH "FINDSMB" "1" "05 November 2002" "" ""
.SH NAME
findsmb \- list info about machines that respond to SMB name queries on a subnet
.SH SYNOPSIS

2
docs/manpages/lmhosts.5
View File

@ -3,7 +3,7 @@
.\" <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" "01 October 2002" "" ""
.TH "LMHOSTS" "5" "05 November 2002" "" ""
.SH NAME
lmhosts \- The Samba NetBIOS hosts file
.SH SYNOPSIS

2
docs/manpages/net.8
View File

@ -3,7 +3,7 @@
.\" <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" "03 October 2002" "" ""
.TH "NET" "8" "05 November 2002" "" ""
.SH NAME
net \- Tool for administration of Samba and remote CIFS servers.
.SH SYNOPSIS

2
docs/manpages/nmblookup.1
View File

@ -3,7 +3,7 @@
.\" <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" "26 November 2002" "" ""
.TH "NMBLOOKUP" "1" "05 November 2002" "" ""
.SH NAME
nmblookup \- NetBIOS over TCP/IP client used to lookup NetBIOS names
.SH SYNOPSIS

35
docs/manpages/pdbedit.8
View File

@ -210,6 +210,41 @@ Example: \fBpdbedit -P "bad lockout attempt" -V 3\fR
account policy value for bad lockout attempt is now 3
.fi
.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-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.
.SH "NOTES"
.PP
This command may be used only by root.

27
docs/manpages/rpcclient.1
View File

@ -3,7 +3,7 @@
.\" <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" "26 November 2002" "" ""
.TH "RPCCLIENT" "1" "05 November 2002" "" ""
.SH NAME
rpcclient \- tool for executing client side MS-RPC functions
.SH SYNOPSIS
@ -47,6 +47,31 @@ access from unwanted users.
execute semicolon separated commands (listed
below))
.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-h|--help\fR
Print a summary of command line options.
.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.

2
docs/manpages/samba.7
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SAMBA" "7" "01 October 2002" "" ""
.TH "SAMBA" "7" "05 November 2002" "" ""
.SH NAME
SAMBA \- A Windows SMB/CIFS fileserver for UNIX
.SH SYNOPSIS

6
docs/manpages/smb.conf.5
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SMB.CONF" "5" "27 December 2002" "" ""
.TH "SMB.CONF" "5" "29 December 2002" "" ""
.SH NAME
smb.conf \- The configuration file for the Samba suite
.SH "SYNOPSIS"
@ -4725,9 +4725,9 @@ This is a boolean option that controls whether
connections with usernames not in the \fIuser\fR
list will be allowed. By default this option is disabled so that a
client can supply a username to be used by the server. Enabling
this parameter will force the server to only use the login
this parameter will force the server to only user the login
names from the \fIuser\fR list and is only really
useful in share level
useful in shave level
security.
Note that this also means Samba won't try to deduce

2
docs/manpages/smbcacls.1
View File

@ -3,7 +3,7 @@
.\" <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" "01 October 2002" "" ""
.TH "SMBCACLS" "1" "05 November 2002" "" ""
.SH NAME
smbcacls \- Set or get ACLs on an NT file or directory names
.SH SYNOPSIS

2
docs/manpages/smbclient.1
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SMBCLIENT" "1" "26 November 2002" "" ""
.TH "SMBCLIENT" "1" "05 November 2002" "" ""
.SH NAME
smbclient \- ftp-like client to access SMB/CIFS resources on servers
.SH SYNOPSIS

2
docs/manpages/smbcontrol.1
View File

@ -3,7 +3,7 @@
.\" <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" "01 October 2002" "" ""
.TH "SMBCONTROL" "1" "05 November 2002" "" ""
.SH NAME
smbcontrol \- send messages to smbd, nmbd or winbindd processes
.SH SYNOPSIS

2
docs/manpages/smbd.8
View File

@ -84,7 +84,7 @@ 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.
given.
.TP
\fB-h\fR
Prints the help information (usage)

2
docs/manpages/smbmnt.8
View File

@ -3,7 +3,7 @@
.\" <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" "01 October 2002" "" ""
.TH "SMBMNT" "8" "05 November 2002" "" ""
.SH NAME
smbmnt \- helper utility for mounting SMB filesystems
.SH SYNOPSIS

2
docs/manpages/smbmount.8
View File

@ -3,7 +3,7 @@
.\" <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" "01 October 2002" "" ""
.TH "SMBMOUNT" "8" "05 November 2002" "" ""
.SH NAME
smbmount \- mount an smbfs filesystem
.SH SYNOPSIS

2
docs/manpages/smbpasswd.5
View File

@ -3,7 +3,7 @@
.\" <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" "26 November 2002" "" ""
.TH "SMBPASSWD" "5" "05 November 2002" "" ""
.SH NAME
smbpasswd \- The Samba encrypted password file
.SH SYNOPSIS

2
docs/manpages/smbspool.8
View File

@ -3,7 +3,7 @@
.\" <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" "01 October 2002" "" ""
.TH "SMBSPOOL" "8" "05 November 2002" "" ""
.SH NAME
smbspool \- send a print file to an SMB printer
.SH SYNOPSIS

2
docs/manpages/smbstatus.1
View File

@ -3,7 +3,7 @@
.\" <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" "01 October 2002" "" ""
.TH "SMBSTATUS" "1" "05 November 2002" "" ""
.SH NAME
smbstatus \- report on current Samba connections
.SH SYNOPSIS

2
docs/manpages/smbtar.1
View File

@ -3,7 +3,7 @@
.\" <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" "01 October 2002" "" ""
.TH "SMBTAR" "1" "05 November 2002" "" ""
.SH NAME
smbtar \- shell script for backing up SMB/CIFS shares directly to UNIX tape drives
.SH SYNOPSIS

2
docs/manpages/smbumount.8
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SMBUMOUNT" "8" "01 October 2002" "" ""
.TH "SMBUMOUNT" "8" "05 November 2002" "" ""
.SH NAME
smbumount \- smbfs umount for normal users
.SH SYNOPSIS

2
docs/manpages/swat.8
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "SWAT" "8" "01 October 2002" "" ""
.TH "SWAT" "8" "05 November 2002" "" ""
.SH NAME
swat \- Samba Web Administration Tool
.SH SYNOPSIS

2
docs/manpages/testprns.1
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "TESTPRNS" "1" "01 October 2002" "" ""
.TH "TESTPRNS" "1" "05 November 2002" "" ""
.SH NAME
testprns \- check printer name for validity with smbd
.SH SYNOPSIS

25
docs/manpages/vfstest.1
View File

@ -24,6 +24,31 @@ supports cascaded VFS modules.
Execute the specified (colon-separated) commands.
See below for the commands that are available.
.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-h|--help\fR
Print a summary of command line options.
.TP
\fB-l|--logfile=logbasename\fR
File name for log/debug files. The extension
\&'.client' will be appended. The log file is never removed

2
docs/manpages/wbinfo.1
View File

@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "WBINFO" "1" "26 November 2002" "" ""
.TH "WBINFO" "1" "05 November 2002" "" ""
.SH NAME
wbinfo \- Query information from winbind daemon
.SH SYNOPSIS