summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorGerald Carter <jerry@samba.org>2001-03-07 13:46:45 +0000
committerGerald Carter <jerry@samba.org>2001-03-07 13:46:45 +0000
commit92ac0108cd20f73146e50d34cd91e7d7b8eb79bb (patch)
treed5919196f8e622e1d3d86cf542a83e5d9df98584 /docs
parent965ec0c89f1cde92031a03040e757261b3a385e2 (diff)
downloadsamba-92ac0108cd20f73146e50d34cd91e7d7b8eb79bb.tar.gz
samba-92ac0108cd20f73146e50d34cd91e7d7b8eb79bb.tar.xz
samba-92ac0108cd20f73146e50d34cd91e7d7b8eb79bb.zip
some autogen documentation
Diffstat (limited to 'docs')
-rw-r--r--docs/htmldocs/DOMAIN_MEMBER.html21
-rw-r--r--docs/htmldocs/NT_Security.html29
-rw-r--r--docs/htmldocs/UNIX_INSTALL.html815
-rw-r--r--docs/htmldocs/msdfs_setup.html203
-rw-r--r--docs/htmldocs/printer_driver2.html672
-rw-r--r--docs/htmldocs/smb.conf.5.html96
-rw-r--r--docs/htmldocs/smbmount.8.html2
-rw-r--r--docs/manpages/smb.conf.598
-rw-r--r--docs/manpages/smbmnt.82
-rw-r--r--docs/manpages/smbmount.84
10 files changed, 1825 insertions, 117 deletions
diff --git a/docs/htmldocs/DOMAIN_MEMBER.html b/docs/htmldocs/DOMAIN_MEMBER.html
index 6ae8e7a49d1..b16722c51b2 100644
--- a/docs/htmldocs/DOMAIN_MEMBER.html
+++ b/docs/htmldocs/DOMAIN_MEMBER.html
@@ -1,7 +1,7 @@
<HTML
><HEAD
><TITLE
-></TITLE
+>security = domain in Samba 2.x</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
@@ -15,11 +15,20 @@ ALINK="#0000FF"
><DIV
CLASS="ARTICLE"
><DIV
+CLASS="TITLEPAGE"
+><H1
+CLASS="TITLE"
+><A
+NAME="AEN1"
+>security = domain in Samba 2.x</A
+></H1
+><HR></DIV
+><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN2"
+NAME="AEN3"
>Joining an NT Domain with Samba 2.2</A
></H1
><P
@@ -104,11 +113,11 @@ CLASS="REPLACEABLE"
><I
>&lt;NT DOMAIN NAME&gt;</I
></TT
->.
- <TT
+>.<TT
CLASS="REPLACEABLE"
><I
->&lt;Samba Server Name&gt;</I
+>&lt;Samba
+ Server Name&gt;</I
></TT
>.mac</TT
></P
@@ -242,7 +251,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
-NAME="AEN65"
+NAME="AEN66"
>Why is this better than security = server?</A
></H1
><P
diff --git a/docs/htmldocs/NT_Security.html b/docs/htmldocs/NT_Security.html
index 8615a7f0dab..081f7fb838a 100644
--- a/docs/htmldocs/NT_Security.html
+++ b/docs/htmldocs/NT_Security.html
@@ -1,7 +1,7 @@
<HTML
><HEAD
><TITLE
-></TITLE
+>UNIX Permission Bits and WIndows NT Access Control Lists</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
@@ -15,11 +15,20 @@ ALINK="#0000FF"
><DIV
CLASS="ARTICLE"
><DIV
+CLASS="TITLEPAGE"
+><H1
+CLASS="TITLE"
+><A
+NAME="AEN1"
+>UNIX Permission Bits and WIndows NT Access Control Lists</A
+></H1
+><HR></DIV
+><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
-NAME="AEN2"
+NAME="AEN3"
>Viewing and changing UNIX permissions using the NT
security dialogs</A
></H1
@@ -58,7 +67,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
-NAME="AEN11"
+NAME="AEN12"
>How to view file security on a Samba share</A
></H1
><P
@@ -110,7 +119,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
-NAME="AEN22"
+NAME="AEN23"
>Viewing file ownership</A
></H1
><P
@@ -198,7 +207,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
-NAME="AEN42"
+NAME="AEN43"
>Viewing file or directory permissions</A
></H1
><P
@@ -260,7 +269,7 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
-NAME="AEN57"
+NAME="AEN58"
>File Permissions</A
></H2
><P
@@ -322,7 +331,7 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
-NAME="AEN71"
+NAME="AEN72"
>Directory Permissions</A
></H2
><P
@@ -354,7 +363,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
-NAME="AEN78"
+NAME="AEN79"
>Modifying file or directory permissions</A
></H1
><P
@@ -452,7 +461,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
-NAME="AEN100"
+NAME="AEN101"
>Interaction with the standard Samba create mask
parameters</A
></H1
@@ -726,7 +735,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
-NAME="AEN164"
+NAME="AEN165"
>Interaction with the standard Samba file attribute
mapping</A
></H1
diff --git a/docs/htmldocs/UNIX_INSTALL.html b/docs/htmldocs/UNIX_INSTALL.html
new file mode 100644
index 00000000000..34f4ed9283a
--- /dev/null
+++ b/docs/htmldocs/UNIX_INSTALL.html
@@ -0,0 +1,815 @@
+<HTML
+><HEAD
+><TITLE
+>How to Install and Test SAMBA</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="AEN1"
+>How to Install and Test SAMBA</A
+></H1
+><HR></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN3"
+>Step 0: Read the man pages</A
+></H1
+><P
+>The man pages distributed with SAMBA contain
+ lots of useful info that will help to get you started.
+ If you don't know how to read man pages then try
+ something like:</P
+><P
+><TT
+CLASS="PROMPT"
+>$ </TT
+><TT
+CLASS="USERINPUT"
+><B
+>nroff -man smbd.8 | more
+ </B
+></TT
+></P
+><P
+>Other sources of information are pointed to
+ by the Samba web site,<A
+HREF="http://www.samba.org/"
+TARGET="_top"
+> http://www.samba.org</A
+></P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H1
+CLASS="SECT1"
+><A
+NAME="AEN11"
+>Step 1: Building the Binaries</A
+></H1
+><P
+>To do this, first run the program <B
+CLASS="COMMAND"
+>./configure
+ </B
+> in the source directory. This should automatically
+ configure Samba for your operating system. If you have unusual
+ needs then you may wish to run</P
+><P
+><TT
+CLASS="PROMPT"
+>root# </TT
+><TT
+CLASS="USERINPUT"
+><B
+>./configure --help
+ </B
+></TT
+></P
+><P
+>first to see what special options you can enable.
+ Then exectuting</P
+><P
+><TT
+CLASS="PROMPT"
+>root# </TT
+><TT
+CLASS="USERINPUT"
+><B
+>make</B
+></TT
+></P
+><P
+>will create the binaries. Once it's successfully
+ compiled you can use </P
+><P
+><TT
+CLASS="PROMPT"
+>root# </TT
+><TT
+CLASS="USERINPUT"
+><B
+>make install</B
+></TT
+></P
+><P
+>to install the binaries and manual pages. You can
+ separately install the binaries and/or man pages using</P
+><P
+><TT
+CLASS="PROMPT"
+>root# </TT
+><TT
+CLASS="USERINPUT"
+><B
+>make installbin
+ </B
+></TT
+></P
+><P
+>and</P
+><P
+><TT
+CLASS="PROMPT"
+>root# </TT
+><TT
+CLASS="USERINPUT"
+><B
+>make installman
+ </B
+></TT
+></P
+><P
+>Note that if you are upgrading for a previous version
+ of Samba you might like to know that the old versions of
+ the binaries will be renamed with a ".old" extension. You
+ can go back to the previous version with</P
+><P
+><TT
+CLASS="PROMPT"
+>root# </TT
+><TT
+CLASS="USERINPUT"
+><B
+>make revert
+ </B
+></TT
+></P
+><P
+>if you find this version a disaster!</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H1
+CLASS="SECT1"
+><A
+NAME="AEN39"
+>Step 2: The all important step</A
+></H1
+><P
+>At this stage you must fetch yourself a
+ coffee or other drink you find stimulating. Getting the rest
+ of the install right can sometimes be tricky, so you will
+ probably need it.</P
+><P
+>If you have installed samba before then you can skip
+ this step.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H1
+CLASS="SECT1"
+><A
+NAME="AEN43"
+>Step 3: Create the smb configuration file.</A
+></H1
+><P
+>There are sample configuration files in the examples
+ subdirectory in the distribution. I suggest you read them
+ carefully so you can see how the options go together in
+ practice. See the man page for all the options.</P
+><P
+>The simplest useful configuration file would be
+ something like this:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> [global]
+ workgroup = MYGROUP
+
+ [homes]
+ guest ok = no
+ read only = no
+ </PRE
+></P
+><P
+>which would allow connections by anyone with an
+ account on the server, using either their login name or
+ "homes" as the service name. (Note that I also set the
+ workgroup that Samba is part of. See BROWSING.txt for defails)</P
+><P
+>Note that <B
+CLASS="COMMAND"
+>make install</B
+> will not install
+ a <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file. You need to create it
+ yourself. </P
+><P
+>Make sure you put the smb.conf file in the same place
+ you specified in the<TT
+CLASS="FILENAME"
+>Makefile</TT
+> (the default is to
+ look for it in <TT
+CLASS="FILENAME"
+>/usr/local/samba/lib/</TT
+>).</P
+><P
+>For more information about security settings for the
+ [homes] share please refer to the document UNIX_SECURITY.txt.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H1
+CLASS="SECT1"
+><A
+NAME="AEN57"
+>Step 4: Test your config file with
+ <B
+CLASS="COMMAND"
+>testparm</B
+></A
+></H1
+><P
+>It's important that you test the validity of your
+ <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file using the testparm program.
+ If testparm runs OK then it will list the loaded services. If
+ not it will give an error message.</P
+><P
+>Make sure it runs OK and that the services look
+ resonable before proceeding. </P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H1
+CLASS="SECT1"
+><A
+NAME="AEN63"
+>Step 5: Starting the smbd and nmbd</A
+></H1
+><P
+>You must choose to start smbd and nmbd either
+ as daemons or from <B
+CLASS="COMMAND"
+>inetd</B
+>. Don't try
+ to do both! Either you can put them in <TT
+CLASS="FILENAME"
+> inetd.conf</TT
+> and have them started on demand
+ by <B
+CLASS="COMMAND"
+>inetd</B
+>, or you can start them as
+ daemons either from the command line or in <TT
+CLASS="FILENAME"
+> /etc/rc.local</TT
+>. See the man pages for details
+ on the command line options. Take particular care to read
+ the bit about what user you need to be in order to start
+ Samba. In many cases you must be root.</P
+><P
+>The main advantage of starting <B
+CLASS="COMMAND"
+>smbd</B
+>
+ and <B
+CLASS="COMMAND"
+>nmbd</B
+> as a daemon is that they will
+ respond slightly more quickly to an initial connection
+ request. This is, however, unlikely to be a problem.</P
+><DIV
+CLASS="SECT2"
+><HR><H2
+CLASS="SECT2"
+><A
+NAME="AEN73"
+>Step 5a: Starting from inetd.conf</A
+></H2
+><P
+>NOTE; The following will be different if
+ you use NIS or NIS+ to distributed services maps.</P
+><P
+>Look at your <TT
+CLASS="FILENAME"
+>/etc/services</TT
+>.
+ What is defined at port 139/tcp. If nothing is defined
+ then add a line like this:</P
+><P
+><TT
+CLASS="USERINPUT"
+><B
+>netbios-ssn 139/tcp</B
+></TT
+></P
+><P
+>similarly for 137/udp you should have an entry like:</P
+><P
+><TT
+CLASS="USERINPUT"
+><B
+>netbios-ns 137/udp</B
+></TT
+></P
+><P
+>Next edit your <TT
+CLASS="FILENAME"
+>/etc/inetd.conf</TT
+>
+ and add two lines something like this:</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> netbios-ssn stream tcp nowait root /usr/local/samba/bin/smbd smbd
+ netbios-ns dgram udp wait root /usr/local/samba/bin/nmbd nmbd
+ </PRE
+></P
+><P
+>The exact syntax of <TT
+CLASS="FILENAME"
+>/etc/inetd.conf</TT
+>
+ varies between unixes. Look at the other entries in inetd.conf
+ for a guide.</P
+><P
+>NOTE: Some unixes already have entries like netbios_ns
+ (note the underscore) in <TT
+CLASS="FILENAME"
+>/etc/services</TT
+>.
+ You must either edit <TT
+CLASS="FILENAME"
+>/etc/services</TT
+> or
+ <TT
+CLASS="FILENAME"
+>/etc/inetd.conf</TT
+> to make them consistant.</P
+><P
+>NOTE: On many systems you may need to use the
+ "interfaces" option in smb.conf to specify the IP address
+ and netmask of your interfaces. Run <B
+CLASS="COMMAND"
+>ifconfig</B
+>
+ as root if you don't know what the broadcast is for your
+ net. <B
+CLASS="COMMAND"
+>nmbd</B
+> tries to determine it at run
+ time, but fails on somunixes. See the section on "testing nmbd"
+ for a method of finding if you need to do this.</P
+><P
+>!!!WARNING!!! Many unixes only accept around 5
+ parameters on the command line in <TT
+CLASS="FILENAME"
+>inetd.conf</TT
+>.
+ This means you shouldn't use spaces between the options and
+ arguments, or you should use a script, and start the script
+ from <B
+CLASS="COMMAND"
+>inetd</B
+>.</P
+><P
+>Restart <B
+CLASS="COMMAND"
+>inetd</B
+>, perhaps just send
+ it a HUP. If you have installed an earlier version of <B
+CLASS="COMMAND"
+> nmbd</B
+> then you may need to kill nmbd as well.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H2
+CLASS="SECT2"
+><A
+NAME="AEN102"
+>Step 5b. Alternative: starting it as a daemon</A
+></H2
+><P
+>To start the server as a daemon you should create
+ a script something like this one, perhaps calling
+ it <TT
+CLASS="FILENAME"
+>startsmb</TT
+>.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> #!/bin/sh
+ /usr/local/samba/bin/smbd -D
+ /usr/local/samba/bin/nmbd -D
+ </PRE
+></P
+><P
+>then make it executable with <B
+CLASS="COMMAND"
+>chmod
+ +x startsmb</B
+></P
+><P
+>You can then run <B
+CLASS="COMMAND"
+>startsmb</B
+> by
+ hand or execute it from <TT
+CLASS="FILENAME"
+>/etc/rc.local</TT
+>
+ </P
+><P
+>To kill it send a kill signal to the processes
+ <B
+CLASS="COMMAND"
+>nmbd</B
+> and <B
+CLASS="COMMAND"
+>smbd</B
+>.</P
+><P
+>NOTE: If you use the SVR4 style init system then
+ you may like to look at the <TT
+CLASS="FILENAME"
+>examples/svr4-startup</TT
+>
+ script to make Samba fit into that system.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H1
+CLASS="SECT1"
+><A
+NAME="AEN118"
+>Step 6: Try listing the shares available on your
+ server</A
+></H1
+><P
+><TT
+CLASS="PROMPT"
+>$ </TT
+><TT
+CLASS="USERINPUT"
+><B
+>smbclient -L
+ <TT
+CLASS="REPLACEABLE"
+><I
+>yourhostname</I
+></TT
+></B
+></TT
+></P
+><P
+>Your should get back a list of shares available on
+ your server. If you don't then something is incorrectly setup.
+ Note that this method can also be used to see what shares
+ are available on other LanManager clients (such as WfWg).</P
+><P
+>If you choose user level security then you may find
+ that Samba requests a password before it will list the shares.
+ See the <B
+CLASS="COMMAND"
+>smbclient</B
+> man page for details. (you
+ can force it to list the shares without a password by
+ adding the option -U% to the command line. This will not work
+ with non-Samba servers)</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H1
+CLASS="SECT1"
+><A
+NAME="AEN127"
+>Step 7: Try connecting with the unix client</A
+></H1
+><P
+><TT
+CLASS="PROMPT"
+>$ </TT
+><TT
+CLASS="USERINPUT"
+><B
+>smbclient <TT
+CLASS="REPLACEABLE"
+><I
+> //yourhostname/aservice</I
+></TT
+></B
+></TT
+></P
+><P
+>Typically the <TT
+CLASS="REPLACEABLE"
+><I
+>yourhostname</I
+></TT
+>
+ would be the name of the host where you installed <B
+CLASS="COMMAND"
+> smbd</B
+>. The <TT
+CLASS="REPLACEABLE"
+><I
+>aservice</I
+></TT
+> is
+ any service you have defined in the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>
+ file. Try your user name if you just have a [homes] section
+ in <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>.</P
+><P
+>For example if your unix host is bambi and your login
+ name is fred you would type:</P
+><P
+><TT
+CLASS="PROMPT"
+>$ </TT
+><TT
+CLASS="USERINPUT"
+><B
+>smbclient //bambi/fred
+ </B
+></TT
+></P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H1
+CLASS="SECT1"
+><A
+NAME="AEN143"
+>Step 8: Try connecting from a DOS, WfWg, Win9x, WinNT,
+ Win2k, OS/2, etc... client</A
+></H1
+><P
+>Try mounting disks. eg:</P
+><P
+><TT
+CLASS="PROMPT"
+>C:\WINDOWS\&#62; </TT
+><TT
+CLASS="USERINPUT"
+><B
+>net use d: \\servername\service
+ </B
+></TT
+></P
+><P
+>Try printing. eg:</P
+><P
+><TT
+CLASS="PROMPT"
+>C:\WINDOWS\&#62; </TT
+><TT
+CLASS="USERINPUT"
+><B
+>net use lpt1:
+ \\servername\spoolservice</B
+></TT
+></P
+><P
+><TT
+CLASS="PROMPT"
+>C:\WINDOWS\&#62; </TT
+><TT
+CLASS="USERINPUT"
+><B
+>print filename
+ </B
+></TT
+></P
+><P
+>Celebrate, or send me a bug report!</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H1
+CLASS="SECT1"
+><A
+NAME="AEN157"
+>What If Things Don't Work?</A
+></H1
+><P
+>If nothing works and you start to think "who wrote
+ this pile of trash" then I suggest you do step 2 again (and
+ again) till you calm down.</P
+><P
+>Then you might read the file DIAGNOSIS.txt and the
+ FAQ. If you are still stuck then try the mailing list or
+ newsgroup (look in the README for details). Samba has been
+ successfully installed at thousands of sites worldwide, so maybe
+ someone else has hit your problem and has overcome it. You could
+ also use the WWW site to scan back issues of the samba-digest.</P
+><P
+>When you fix the problem PLEASE send me some updates to the
+ documentation (or source code) so that the next person will find it
+ easier. </P
+><DIV
+CLASS="SECT2"
+><HR><H2
+CLASS="SECT2"
+><A
+NAME="AEN162"
+>Diagnosing Problems</A
+></H2
+><P
+>If you have instalation problems then go to
+ <TT
+CLASS="FILENAME"
+>DIAGNOSIS.txt</TT
+> to try to find the
+ problem.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H2
+CLASS="SECT2"
+><A
+NAME="AEN166"
+>Scope IDs</A
+></H2
+><P
+>By default Samba uses a blank scope ID. This means
+ all your windows boxes must also have a blank scope ID.
+ If you really want to use a non-blank scope ID then you will
+ need to use the -i &lt;scope&gt; option to nmbd, smbd, and
+ smbclient. All your PCs will need to have the same setting for
+ this to work. I do not recommend scope IDs.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H2
+CLASS="SECT2"
+><A
+NAME="AEN169"
+>Choosing the Protocol Level</A
+></H2
+><P
+>The SMB protocol has many dialects. Currently
+ Samba supports 5, called CORE, COREPLUS, LANMAN1,
+ LANMAN2 and NT1.</P
+><P
+>You can choose what maximum protocol to support
+ in the <TT
+CLASS="FILENAME"
+>smb.conf</TT
+> file. The default is
+ NT1 and that is the best for the vast majority of sites.</P
+><P
+>In older versions of Samba you may have found it
+ necessary to use COREPLUS. The limitations that led to
+ this have mostly been fixed. It is now less likely that you
+ will want to use less than LANMAN1. The only remaining advantage
+ of COREPLUS is that for some obscure reason WfWg preserves
+ the case of passwords in this protocol, whereas under LANMAN1,
+ LANMAN2 or NT1 it uppercases all passwords before sending them,
+ forcing you to use the "password level=" option in some cases.</P
+><P
+>The main advantage of LANMAN2 and NT1 is support for
+ long filenames with some clients (eg: smbclient, Windows NT
+ or Win95). </P
+><P
+>See the smb.conf(5) manual page for more details.</P
+><P
+>Note: To support print queue reporting you may find
+ that you have to use TCP/IP as the default protocol under
+ WfWg. For some reason if you leave Netbeui as the default
+ it may break the print queue reporting on some systems.
+ It is presumably a WfWg bug.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H2
+CLASS="SECT2"
+><A
+NAME="AEN178"
+>Printing from UNIX to a Client PC</A
+></H2
+><P
+>To use a printer that is available via a smb-based
+ server from a unix host you will need to compile the
+ smbclient program. You then need to install the script
+ "smbprint". Read the instruction in smbprint for more details.
+ </P
+><P
+>There is also a SYSV style script that does much
+ the same thing called smbprint.sysv. It contains instructions.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H2
+CLASS="SECT2"
+><A
+NAME="AEN182"
+>Locking</A
+></H2
+><P
+>One area which sometimes causes trouble is locking.</P
+><P
+>There are two types of locking which need to be
+ performed by a SMB server. The first is "record locking"
+ which allows a client to lock a range of bytes in a open file.
+ The second is the "deny modes" that are specified when a file
+ is open.</P
+><P
+>Samba supports "record locking" using the fcntl() unix system
+ call. This is often implemented using rpc calls to a rpc.lockd process
+ running on the system that owns the filesystem. Unfortunately many
+ rpc.lockd implementations are very buggy, particularly when made to
+ talk to versions from other vendors. It is not uncommon for the
+ rpc.lockd to crash.</P
+><P
+>There is also a problem translating the 32 bit lock
+ requests generated by PC clients to 31 bit requests supported
+ by most unixes. Unfortunately many PC applications (typically
+ OLE2 applications) use byte ranges with the top bit set
+ as semaphore sets. Samba attempts translation to support
+ these types of applications, and the translation has proved
+ to be quite successful.</P
+><P
+>Strictly a SMB server should check for locks before
+ every read and write call on a file. Unfortunately with the
+ way fcntl() works this can be slow and may overstress the
+ rpc.lockd. It is also almost always unnecessary as clients
+ are supposed to independently make locking calls before reads
+ and writes anyway if locking is important to them. By default
+ Samba only makes locking calls when explicitly asked
+ to by a client, but if you set "strict locking = yes" then it will
+ make lock checking calls on every read and write. </P
+><P
+>You can also disable by range locking completely
+ using "locking = no". This is useful for those shares that
+ don't support locking or don't need it (such as cdroms). In
+ this case Samba fakes the return codes of locking calls to
+ tell clients that everything is OK.</P
+><P
+>The second class of locking is the "deny modes". These
+ are set by an application when it opens a file to determine
+ what types of access should be allowed simultaneously with
+ its open. A client may ask for DENY_NONE, DENY_READ, DENY_WRITE
+ or DENY_ALL. There are also special compatability modes called
+ DENY_FCB and DENY_DOS.</P
+><P
+>You can disable share modes using "share modes = no".
+ This may be useful on a heavily loaded server as the share
+ modes code is very slow. See also the FAST_SHARE_MODES
+ option in the Makefile for a way to do full share modes
+ very fast using shared memory (if your OS supports it).</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H2
+CLASS="SECT2"
+><A
+NAME="AEN192"
+>Mapping Usernames</A
+></H2
+><P
+>If you have different usernames on the PCs and
+ the unix server then take a look at the "username map" option.
+ See the smb.conf man page for details.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H2
+CLASS="SECT2"
+><A
+NAME="AEN195"
+>Other Character Sets</A
+></H2
+><P
+>If you have problems using filenames with accented
+ characters in them (like the German, French or Scandinavian
+ character sets) then I recommmend you look at the "valid chars"
+ option in smb.conf and also take a look at the validchars
+ package in the examples directory.</P
+></DIV
+></DIV
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/msdfs_setup.html b/docs/htmldocs/msdfs_setup.html
new file mode 100644
index 00000000000..97c17b9e088
--- /dev/null
+++ b/docs/htmldocs/msdfs_setup.html
@@ -0,0 +1,203 @@
+<HTML
+><HEAD
+><TITLE
+>Hosting a Microsoft Distributed File System tree on Samba</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="AEN1"
+>Hosting a Microsoft Distributed File System tree on Samba</A
+></H1
+><HR></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN3"
+>Instructions</A
+></H1
+><P
+>The Distributed File System (or Dfs) provides a means of
+ separating the logical view of files and directories that users
+ see from the actual physical locations of these resources on the
+ network. It allows for higher availability, smoother storage expansion,
+ load balancing etc. For more information about Dfs, refer to <A
+HREF="http://www.microsoft.com/NTServer/nts/downloads/winfeatures/NTSDistrFile/AdminGuide.asp"
+TARGET="_top"
+> Microsoft documentation</A
+>. </P
+><P
+>This document explains how to host a Dfs tree on a Unix
+ machine (for Dfs-aware clients to browse) using Samba.</P
+><P
+>A Samba server can be made a Dfs server by setting the global
+ boolean <A
+HREF="smb.conf.5.html#HOSTMSDFS"
+TARGET="_top"
+><TT
+CLASS="PARAMETER"
+><I
+> host msdfs</I
+></TT
+></A
+> parameter in the <TT
+CLASS="FILENAME"
+>smb.conf
+ </TT
+> file. You designate a share as a Dfs root using the share
+ level boolean <A
+HREF="smb.conf.5.html#MSDFSROOT"
+TARGET="_top"
+><TT
+CLASS="PARAMETER"
+><I
+> msdfs root</I
+></TT
+></A
+> parameter. A Dfs root directory on
+ Samba hosts Dfs links in the form of symbolic links that point
+ to other servers. For example, a symbolic link
+ <TT
+CLASS="FILENAME"
+>junction-&gt;msdfs:storage1&bsol;share1</TT
+> in
+ the share directory acts as the Dfs junction. When Dfs-aware
+ clients attempt to access the junction link, they are redirected
+ to the storage location (in this case, \\storage1\share1).</P
+><P
+>Dfs trees on Samba work with all Dfs-aware clients ranging
+ from Windows 95 to 2000.</P
+><P
+>Here's an example of setting up a Dfs tree on a Samba
+ server.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+># The smb.conf file:
+[global]
+ netbios name = SAMBA
+ host msdfs = yes
+
+[dfs]
+ path = /export/dfsroot
+ msdfs root = yes
+ </PRE
+></P
+><P
+>In the /export/dfsroot directory we set up our dfs links to
+ other servers on the network.</P
+><P
+><TT
+CLASS="PROMPT"
+>root# </TT
+><TT
+CLASS="USERINPUT"
+><B
+>cd /export/dfsroot</B
+></TT
+></P
+><P
+><TT
+CLASS="PROMPT"
+>root# </TT
+><TT
+CLASS="USERINPUT"
+><B
+>chown root /export/dfsroot</B
+></TT
+></P
+><P
+><TT
+CLASS="PROMPT"
+>root# </TT
+><TT
+CLASS="USERINPUT"
+><B
+>chmod 755 /export/dfsroot</B
+></TT
+></P
+><P
+><TT
+CLASS="PROMPT"
+>root# </TT
+><TT
+CLASS="USERINPUT"
+><B
+>ln -s msdfs:storageA\\shareA linka</B
+></TT
+></P
+><P
+><TT
+CLASS="PROMPT"
+>root# </TT
+><TT
+CLASS="USERINPUT"
+><B
+>ln -s msdfs:serverB\\share,serverC\\share linkb</B
+></TT
+></P
+><P
+>You should set up the permissions and ownership of
+ the directory acting as the Dfs root such that only designated
+ users can create, delete or modify the msdfs links. Also note
+ that symlink names should be all lowercase. This limitation exists
+ to have Samba avoid trying all the case combinations to get at
+ the link name. Finally set up the symbolic links to point to the
+ network shares you want, and start Samba.</P
+><P
+>Users on Dfs-aware clients can now browse the Dfs tree
+ on the Samba server at \\samba\dfs. Accessing
+ links linka or linkb (which appear as directories to the client)
+ takes users directly to the appropriate shares on the network.</P
+><DIV
+CLASS="SECT2"
+><HR><H2
+CLASS="SECT2"
+><A
+NAME="AEN37"
+>Notes</A
+></H2
+><P
+></P
+><UL
+><LI
+><P
+>Windows clients need to be rebooted
+ if a previously mounted non-dfs share is made a dfs
+ root or vice versa. A better way is to introduce a
+ new share and make it the dfs root.</P
+></LI
+><LI
+><P
+>Currently there's a restriction that msdfs
+ symlink names should all be lowercase.</P
+></LI
+><LI
+><P
+>For security purposes, the directory
+ acting as the root of the Dfs tree should have ownership
+ and permissions set so that only designated users can
+ modify the symbolic links in the directory.</P
+></LI
+></UL
+></DIV
+></DIV
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/printer_driver2.html b/docs/htmldocs/printer_driver2.html
new file mode 100644
index 00000000000..543b765870b
--- /dev/null
+++ b/docs/htmldocs/printer_driver2.html
@@ -0,0 +1,672 @@
+<HTML
+><HEAD
+><TITLE
+>Printing Support in Samba 2.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="AEN1"
+>Printing Support in Samba 2.2.x</A
+></H1
+><HR></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN3"
+>Introduction</A
+></H1
+><P
+>Beginning with the 2.2.0 release, Samba now supports
+ the native Windows NT printing mechanisms implemented via
+ MS-RPC (i.e. the SPOOLSS named pipe). Previous versions of
+ Samba only supported the LanMan printing calls.</P
+><P
+>The additional functionality provided by the new
+ SPOOLSS support includes:</P
+><P
+></P
+><UL
+><LI
+><P
+>Support for downloading printer driver
+ files to Windows 95/98/NT/2000 clients upon demand.
+ </P
+></LI
+><LI
+><P
+>Uploading of printer drivers via the
+ Windows NT Add Printer Wizard (APW) or the <A
+HREF="http://imprints.sourceforge.net"
+TARGET="_top"
+>Imprints tool set
+ </A
+></P
+></LI
+><LI
+><P
+>Support for the native MS-RPC printing
+ calls such as StartDocPrinter, EnumJobs(), etc... (See
+ the <A
+HREF="http://msdn.microsoft.com/"
+TARGET="_top"
+>MSDN documentation
+ </A
+> for more information on the Win32 printing API)
+ </P
+></LI
+><LI
+><P
+>Support for NT Access Control Lists (ACL)
+ on printer objects</P
+></LI
+><LI
+><P
+>Improved support for printer queue manipulation
+ through the use of an internal database for spooled job
+ information</P
+></LI
+></UL
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H1
+CLASS="SECT1"
+><A
+NAME="AEN20"
+>Configuration</A
+></H1
+><P
+>In order to support the uploading of printer driver
+ files, you must first configure a file share named [print$].
+ The name of this share is hard coded in Samba's internals so
+ the name is very important (print$ is the service used by
+ Windows NT print servers to provide support for printer driver
+ download.</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
+>Previous versions of Samba recommended using
+ a share named [printer$]. This name was taken from the
+ printer$ service created by Windows 9x clients when a
+ printer was shared. Windows 9x printer servers always have
+ a printer$ service which provides read-only access via no
+ password in order to support printer driver downloads.</P
+><P
+>However, the initial implementation allowed for a
+ parameter named <TT
+CLASS="PARAMETER"
+><I
+>printer driver location</I
+></TT
+>
+ to be used on a per share basis to specify the location of
+ the driver files associated with that printer. Another
+ parameter named <TT
+CLASS="PARAMETER"
+><I
+>printer driver</I
+></TT
+> 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 depreciated and should not
+ be used in new installations. For more information on this change,
+ you should refer to the <A
+HREF="#MIGRATION"
+>Migration section
+ </A
+>of this document.</P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+>You should modify the server's smb.conf file to create the
+ following file share (of course, some of the parameter values,
+ such as 'path' are arbitrary and should be replaced with
+ appropriate values for your site):</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>[print$]
+ path = /usr/local/samba/printers
+ guest ok = yes
+ browseable = yes
+ read only = yes
+ write list = ntadmin
+ </PRE
+></P
+><P
+>The <A
+HREF="smb./conf.5.html#WRITELIST"
+TARGET="_top"
+><TT
+CLASS="PARAMETER"
+><I
+> write list</I
+></TT
+></A
+> is used to allow administrative
+ level user accounts to have write access in order to update files
+ on the share. See the <A
+HREF="smb./conf.5.html"
+TARGET="_top"
+> smb.conf(5) man page</A
+> for more information on
+ configuring file shares.</P
+><P
+>The requirement for <A
+HREF="smb.conf.5.html#GUESTOK"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+> guest ok = yes</B
+></A
+> depends upon how your
+ site is configured. If users will be guaranteed to have
+ an account on the Samba host, then this is a non-issue.</P
+><P
+><I
+CLASS="EMPHASIS"
+>author's note: </I
+>The non-issue is that
+ if all your Windows NT users are guarenteed to be authenticated
+ by the Samba server (such as a domain member server and the NT
+ user has already been validated by the Domain Controller in
+ order to logon to the Windows NT console), then guest access
+ is not necessary. Of course, in a workgroup environment where
+ you just want to be able to print without worrying about
+ silly accounts and security, then configure the share for
+ guest access. You'll probably want to add <A
+HREF="smb.conf.5.html#MAPTOGUEST"
+TARGET="_top"
+><B
+CLASS="COMMAND"
+>map to guest = Bad User
+ </B
+></A
+> in the [global] section as well. Make sure
+ you understand what this parameter does before using it
+ though. --jerry]</P
+><P
+>In order for a Windows NT print server to support
+ the downloading of driver files by multiple client architectures,
+ it must create subdirectories within the [print$] service
+ which correspond to each of the supported client architectures.
+ Samba follows this model as well.</P
+><P
+>Next create the directory tree below the [print$] share
+ for each architecture you wish to support.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+> [print$]-----
+ |-W32X86 ; "Windows NT x86"
+ |-WIN40 ; "Windows 95/98"
+ |-W32ALPHA ; "Windows NT Alpha_AXP"
+ |-W32MIPS ; "Windows NT R4000"
+ |-W32PPC ; "Windows NT PowerPC"
+ </PRE
+></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
+><I
+CLASS="EMPHASIS"
+>ATTENTION! REQUIRED PERMISSIONS</I
+></P
+><P
+>In order to currently add a new driver to you Samba host,
+ one of two conditions must hold true:</P
+><P
+></P
+><UL
+><LI
+><P
+>The account used to connect to the Samba host
+ must have a uid of 0 (i.e. a root account)</P
+></LI
+><LI
+><P
+>The account used to connect to the Samba host
+ must be a member of the <A
+HREF="smb.conf.5.html"
+TARGET="_top"
+><TT
+CLASS="PARAMETER"
+><I
+> printer admin</I
+></TT
+></A
+> list.</P
+></LI
+></UL
+><P
+>Of course, the connected account must still possess access
+ to add files to the sibdirectories beneath [print$].</P
+></TD
+></TR
+></TABLE
+></DIV
+><P
+>Once you have created the required [print$] service and
+ associated subdirectories, simply log onto the Samba server using
+ a root (or <TT
+CLASS="PARAMETER"
+><I
+>printer admin</I
+></TT
+>) account
+ from a Windows NT 4.0 client. Navigate to the "Printers" folder
+ on the Samba server. You should see an initial listing of printers
+ that matches the printer shares defined on your Samba host.</P
+><P
+>It is possible on a Windows NT print server to have printers
+ listed in the Printers folder which are not shared. Samba does
+ not make this distinction. By definition, the only printers of
+ which Samba is aware are those which are specified as shares in
+ <TT
+CLASS="FILENAME"
+>smb.conf</TT
+>.</P
+><P
+>Another interesting side note is that Windows NT clients do
+ not use the SMB printer share, but rather can print directly
+ to any printer on another Windows NT host using MS-RPC. This
+ of course assumes that the printing client has the necessary
+ privileges on the remote host serving the printer. The default
+ permissions assigned by Windows NT to a printer gives the "Print"
+ permissions to the "Everyone" well-known group.</P
+><P
+>The initial listing of printers in the Samba host's
+ Printers folder will have no printer driver assigned to them.
+ The way assign a driver to a printer is to view the Properties
+ of the printer and either</P
+><P
+></P
+><UL
+><LI
+><P
+>Use the "New Driver..." button to install
+ a new printer driver, or</P
+></LI
+><LI
+><P
+>Select a driver from the popup list of
+ installed drivers. Initially this list will be empty.</P
+></LI
+></UL
+><P
+>If you wish to install printer drivers for client
+ operating systems other than "Windows NT x86", you will need
+ to use the "Sharing" tab of the printer properties dialog.</P
+><P
+>Assuming you have connected with a root account, you
+ will also be able modify other printer properties such as
+ ACLs and device settings using this dialog box.</P
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H1
+CLASS="SECT1"
+><A
+NAME="AEN74"
+>The Imprints Toolset</A
+></H1
+><P
+>The Imprints tool set provides a UNIX equivalent of the
+ Windows NT Add Printer Wizard. For complete information, please
+ refer to the Imprints web site at <A
+HREF="http://imprints.sourceforge.net/"
+TARGET="_top"
+> http://imprints.sourceforge.net/</A
+> as well as the documentation
+ included with the imprints source distribution. This section will
+ only provide a brief introduction to the features of Imprints.</P
+><DIV
+CLASS="SECT2"
+><HR><H2
+CLASS="SECT2"
+><A
+NAME="AEN78"
+>What is Imprints?</A
+></H2
+><P
+>Imprints is a collection of tools for supporting the goals
+ of</P
+><P
+></P
+><UL
+><LI
+><P
+>Providing a central repository information
+ regarding Windows NT and 95/98 printer driver packages</P
+></LI
+><LI
+><P
+>Providing the tools necessary for creating
+ the Imprints printer driver packages.</P
+></LI
+><LI
+><P
+>Providing an installation client which
+ will obtain and install printer drivers on remote Samba
+ and Windows NT 4 print servers.</P
+></LI
+></UL
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H2
+CLASS="SECT2"
+><A
+NAME="AEN88"
+>Creating Printer Driver Packages</A
+></H2
+><P
+>The process of creating printer driver packages is beyond
+ the scope of this document (refer to Imprints.txt also included
+ with the Samba distribution for more information). In short,
+ an Imprints driver package is a gzipped tarball containing the
+ driver files, related INF files, and a control file needed by the
+ installation client.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H2
+CLASS="SECT2"
+><A
+NAME="AEN91"
+>The Imprints server</A
+></H2
+><P
+>The Imprints server is really a database server that
+ may be queried via standard HTTP mechanisms. Each printer
+ entry in the database has an associated URL for the actual
+ downloading of the package. Each package is digitally signed
+ via GnuPG which can be used to verify that package downloaded
+ is actually the one referred in the Imprints database. It is
+ <I
+CLASS="EMPHASIS"
+>not</I
+> recommended that this security check
+ be disabled.</P
+></DIV
+><DIV
+CLASS="SECT2"
+><HR><H2
+CLASS="SECT2"
+><A
+NAME="AEN95"
+>The Installation Client</A
+></H2
+><P
+>More information regarding the Imprints installation client
+ is available in the <TT
+CLASS="FILENAME"
+>Imprints-Client-HOWTO.ps</TT
+>
+ file included with the imprints source package.</P
+><P
+>The Imprints installation client comes in two forms.</P
+><P
+></P
+><UL
+><LI
+><P
+>a set of command line Perl scripts</P
+></LI
+><LI
+><P
+>a GTK+ based graphical interface to
+ the command line perl scripts</P
+></LI
+></UL
+><P
+>The installation client (in both forms) provides a means
+ of querying the Imprints database server for a matching
+ list of known printer model names as well as a means to
+ download and install the drivers on remote Samba and Windows
+ NT print servers.</P
+><P
+>The basic installation process is in four steps and
+ perl code is wrapped around <B
+CLASS="COMMAND"
+>smbclient</B
+>
+ and <B
+CLASS="COMMAND"
+>rpcclient</B
+>.</P
+><P
+><PRE
+CLASS="PROGRAMLISTING"
+>
+ foreach (supported architecture for a given driver)
+ {
+ 1. rpcclient: Get the appropriate upload directory
+ on the remote server
+ 2. smbclient: Upload the driver files
+ 3. rpcclient: Issues an AddPrinterDriver() MS-RPC
+ }
+
+ 4. rpcclient: Issue an AddPrinterEx() MS-RPC to actually
+ create the printer
+ </PRE
+></P
+><P
+>One of the problems encountered when implementing
+ the Imprints tool set was the name space issues between
+ various supported client architectures. For example, Windows
+ NT includes a driver named "Apple LaserWriter II NTX v51.8"
+ and Windows 95 callsits version of this driver "Apple
+ LaserWriter II NTX"</P
+><P
+>The problem is how to know what client drivers have
+ been uploaded for a printer. As astute reader will remember
+ that the Windows NT Printer Properties dialog only includes
+ space for one printer driver name. A quick look in the
+ Windows NT 4.0 system registry at</P
+><P
+><TT
+CLASS="FILENAME"
+>HKLM\System\CurrentControlSet\Control\Print\Environment
+ </TT
+></P
+><P
+>will reveal that Windows NT always uses the NT driver
+ name. The is ok as Windows NT always requires that at least
+ the Windows NT version of the printer driver is present.
+ However, Samba does not have the requirement internally.
+ Therefore, how can you use the NT driver name if is has not
+ already been installed?</P
+><P
+>The way of sidestepping this limitation is to require
+ that all Imprints printer driver packages include both the Intel
+ Windows NT and 95/98 printer drivers and that NT driver is
+ installed first.</P
+></DIV
+></DIV
+><DIV
+CLASS="SECT1"
+><HR><H1
+CLASS="SECT1"
+><A
+NAME="AEN117"
+><A
+NAME="MIGRATION"
+></A
+>Migration to from Samba 2.0.x to
+ 2.2.x</A
+></H1
+><P
+>Given that printer driver management has changed
+ (we hope improved :) ) in 2.2.0 over prior releases,
+ migration from an existing setup to 2.2.0 can follow
+ several paths.</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
+>The following smb.conf parameters are considered to be
+ depreciated and will be removed soon. Do not use them
+ in new installations</P
+><P
+></P
+><UL
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>printer driver file (G)</I
+></TT
+>
+ </P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>printer driver (S)</I
+></TT
+>
+ </P
+></LI
+><LI
+><P
+><TT
+CLASS="PARAMETER"
+><I
+>printer driver location (S)</I
+></TT
+>
+ </P
+></LI
+></UL
+></TD
+></TR
+></TABLE
+></DIV
+><P
+>Here are the possible scenarios for supporting migration:</P
+><P
+></P
+><UL
+><LI
+><P
+>If you does 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 does not want to migrate the
+ 9x drivers to the new setup, the leave the existing
+ printers.def 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 moved to the "this tool is the old way of doing it"
+ pile.</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. (comment: this could possibly be scripted
+ using smbclient and rpcclient, but I haven't had time --jerry)
+ </P
+></LI
+></UL
+></DIV
+></DIV
+></BODY
+></HTML
+> \ No newline at end of file
diff --git a/docs/htmldocs/smb.conf.5.html b/docs/htmldocs/smb.conf.5.html
index f3ec5d263a9..18db106119f 100644
--- a/docs/htmldocs/smb.conf.5.html
+++ b/docs/htmldocs/smb.conf.5.html
@@ -134,7 +134,7 @@ CLASS="EMPHASIS"
to the user of the service. Some housekeeping options are
also specifiable.</P
><P
->Sections are either filespace services (used by the
+>Sections are either file share services (used by the
client as an extension of their native file systems) or
printable services (used by the client to access print services
on the host running the server).</P
@@ -219,7 +219,7 @@ NAME="AEN50"
>parameters in this section apply to the server
as a whole, or are defaults for sections which do not
specifically define certain items. See the notes
- under paraMETERS for more information.</P
+ under PARAMETERS for more information.</P
></DIV
><DIV
CLASS="REFSECT2"
@@ -539,7 +539,7 @@ CLASS="VARIABLELIST"
>%h</DT
><DD
><P
->the internet hostname that Samba is running
+>the Internet hostname that Samba is running
on.</P
></DD
><DT
@@ -561,7 +561,7 @@ CLASS="VARIABLELIST"
>%M</DT
><DD
><P
->the internet name of the client machine.
+>the Internet name of the client machine.
</P
></DD
><DT
@@ -749,10 +749,10 @@ NAME="AEN234"
>NOTE ABOUT USERNAME/PASSWORD VALIDATION</H2
><P
>There are a number of ways in which a user can connect
- to a service. The server follows the following steps in determining
+ to a service. The server uses the following steps in determining
if it will allow a connection to a specified service. If all the
- steps fail then the connection request is rejected. If one of the
- steps pass then the following steps are not checked.</P
+ steps fail, then the connection request is rejected. However, if one of the
+ steps succeeds, then the following steps are not checked.</P
><P
>If the service is marked "guest only = yes" then
steps 1 to 5 are skipped.</P
@@ -2244,7 +2244,7 @@ NAME="AEN725"
><H2
>COMPLETE LIST OF SERVICE PARAMETERS</H2
><P
->Here is a list of all service parameters. See the section of
+>Here is a list of all service parameters. See the section on
each parameter for details. Note that some are synonyms.</P
><P
></P
@@ -3305,7 +3305,7 @@ HREF="smbd.8.html"
TARGET="_top"
>smbd(8)
</A
-> under special circumstances decribed below.</P
+> under special circumstances described below.</P
><P
>Normally, a Samba server requires that UNIX users are
created for all users accessing files on this server. For sites
@@ -3543,7 +3543,7 @@ CLASS="PARAMETER"
></UL
><P
>All parameters are filled in from the PRINTER_INFO_2 structure sent
- by the Windows NT/2000 client with one excpetion. The "Windows 9x
+ by the Windows NT/2000 client with one exception. The "Windows 9x
driver location" parameter is included for backwards compatibility
only. The remaining fields in the structure are generated from answers
to the APW questions.</P
@@ -3708,7 +3708,7 @@ CLASS="COMMAND"
>
will announce itself as, to a network neighborhood browse
list. By default this is set to Windows NT. The valid options
- are : "NT" (which is a synonym for "NT Server"), "NT Server",
+ are : "NT Server" (which can also be written as "NT"),
"NT Workstation", "Win95" or "WfW" meaning Windows NT Server,
Windows NT Workstation, Windows 95 and Windows for Workgroups
respectively. Do not change this parameter unless you have a
@@ -4369,7 +4369,7 @@ CLASS="COMMAND"
>. This will output
the code page. The default for USA MS-DOS, Windows 95, and
Windows NT releases is code page 437. The default for western
- european releases of the above operating systems is code page 850.</P
+ European releases of the above operating systems is code page 850.</P
><P
>This parameter tells <A
HREF="smbd.8.html"
@@ -5193,7 +5193,7 @@ CLASS="COMMAND"
>smbd(8)</B
></A
> under special circumstances
- decribed below.</P
+ described below.</P
><P
>Normally, a Samba server requires that UNIX users are
created for all users accessing files on this server. For sites
@@ -5555,7 +5555,7 @@ CLASS="PARAMETER"
CLASS="FILENAME"
>./</TT
>. The script should return two
- integers in ascii. The first should be the total disk space in blocks,
+ integers in ASCII. The first should be the total disk space in blocks,
and the second should be the number of available blocks. An optional
third return value can give the block size in bytes. The default
blocksize is 1024 bytes.</P
@@ -6112,7 +6112,7 @@ CLASS="PARAMETER"
>domain
master</I
></TT
-> ne enabled by default.</P
+> be enabled by default.</P
><P
>Default: <B
CLASS="COMMAND"
@@ -6974,7 +6974,7 @@ CLASS="PARAMETER"
></TT
></A
> (see below). Whatever privileges this
- ser has will be available to any client connecting to the guest service.
+ user has will be available to any client connecting to the guest service.
Typically this user will exist in the password file, but will not
have a valid login. The user account "ftp" is often a good choice
for this parameter. If a username is specified in a given service,
@@ -7017,7 +7017,7 @@ NAME="GUESTOK"
CLASS="CONSTANT"
>yes</TT
> for
- a service, then no password is equired to connect to the service.
+ a service, then no password is required to connect to the service.
Privileges will be those of the <A
HREF="#GUESTACCOUNT"
><TT
@@ -7737,11 +7737,11 @@ NAME="INTERFACES"
><P
>The "mask" parameters can either be a bit length (such
as 24 for a C class network) or a full netmask in dotted
- decmal form.</P
+ decimal form.</P
><P
>The "IP" parameters above can either be a full dotted
decimal IP address or a hostname which will be looked up via
- the OSes normal hostname resolution mechanisms.</P
+ the OS's normal hostname resolution mechanisms.</P
><P
>For example, the following line:</P
><P
@@ -7889,7 +7889,7 @@ NAME="KERNELOPLOCKS"
>kernel oplocks (G)</DT
><DD
><P
->For UNIXs that support kernel based <A
+>For UNIXes that support kernel based <A
HREF="#OPLOCKS"
><TT
CLASS="PARAMETER"
@@ -7975,7 +7975,7 @@ NAME="LEVEL2OPLOCKS"
exclusive oplocks). This allows all openers of the file that
support level2 oplocks to cache the file for read-ahead only (ie.
they may not cache writes or lock requests) and increases performance
- for many acesses of files that are not commonly written (such as
+ for many accesses of files that are not commonly written (such as
application .EXE files).</P
><P
>Once one of the clients which have a read-only oplock
@@ -8339,7 +8339,7 @@ NAME="LOGFILE"
>log file (G)</DT
><DD
><P
->This options allows you to override the name
+>This option allows you to override the name
of the Samba log file (also known as the debug file).</P
><P
>This option takes the standard substitutions, allowing
@@ -9238,7 +9238,7 @@ CLASS="FILENAME"
>;1
</TT
> off the ends of filenames on some CDROMS (only visible
- under some UNIXs). To do this use a map of (*;1 *;).</P
+ under some UNIXes). To do this use a map of (*;1 *;).</P
><P
>Default: <I
CLASS="EMPHASIS"
@@ -10732,7 +10732,7 @@ NAME="OPLOCKS"
issue oplocks (opportunistic locks) to file open requests on this
share. The oplock code can dramatically (approx. 30% or more) improve
the speed of access to files on Samba servers. It allows the clients
- to aggressively cache files ocally and you may want to disable this
+ to aggressively cache files locally and you may want to disable this
option for unreliable network environments (it is turned on by
default in Windows NT Servers). For more information see the file
<TT
@@ -11249,9 +11249,9 @@ CLASS="COMMAND"
> you can get Samba
to do all its username/password validation via a remote server.</P
><P
->This options sets the name of the password server to use.
+>This option sets the name of the password server to use.
It must be a NetBIOS name, so if the machine's NetBIOS name is
- different from its internet name then you may have to add its NetBIOS
+ different from its Internet name then you may have to add its NetBIOS
name to the lmhosts file which is stored in the same directory
as the <TT
CLASS="FILENAME"
@@ -11298,8 +11298,8 @@ CLASS="PARAMETER"
</I
></TT
>, which means the Samba server will use the incoming
- client as the passwordserver. If you use this then you better
- trust your clients, and you better restrict them with hosts allow!</P
+ client as the password server. If you use this then you better
+ trust your clients, and you had better restrict them with hosts allow!</P
><P
>If the <TT
CLASS="PARAMETER"
@@ -11312,8 +11312,8 @@ CLASS="CONSTANT"
>domain</TT
>, then the list of machines in this
option must be a list of Primary or Backup Domain controllers for the
- Domain or the character '*', as the Samba server is cryptographicly
- in that domain, and will use cryptographicly authenticated RPC calls
+ Domain or the character '*', as the Samba server is effectively
+ in that domain, and will use cryptographically authenticated RPC calls
to authenticate the user logging on. The advantage of using <B
CLASS="COMMAND"
> security = domain</B
@@ -11844,7 +11844,7 @@ CLASS="PARAMETER"
printable service nor a global print command, spool files will
be created but not processed and (most importantly) not removed.</P
><P
->Note that printing may fail on some UNIXs from the
+>Note that printing may fail on some UNIXes from the
<TT
CLASS="CONSTANT"
>nobody</TT
@@ -12115,13 +12115,13 @@ CLASS="FILENAME"
CLASS="FILENAME"
>docs
</TT
-> ofthe Samba distribution for more information
+> of the Samba distribution for more information
on the new method of loading printer drivers onto a Samba server.
</P
><P
>This option allows you to control the string
that clients receive when they ask the server for the printer driver
- associated with a printer. If you are using Windows95 or WindowsNT
+ associated with a printer. If you are using Windows95 or Windows NT
then you can use this to automate the setup of printers on your
system.</P
><P
@@ -12138,7 +12138,7 @@ CLASS="PARAMETER"
></A
> option set and the client will
give you a list of printer drivers. The appropriate strings are
- shown in a scrollbox after you have chosen the printer manufacturer.</P
+ shown in a scroll box after you have chosen the printer manufacturer.</P
><P
>See also <A
HREF="#PRINTERDRIVERFILE"
@@ -12176,7 +12176,7 @@ CLASS="FILENAME"
CLASS="FILENAME"
>docs
</TT
-> ofthe Samba distribution for more information
+> of the Samba distribution for more information
on the new method of loading printer drivers onto a Samba server.
</P
><P
@@ -12251,7 +12251,7 @@ CLASS="FILENAME"
CLASS="FILENAME"
>docs
</TT
-> ofthe Samba distribution for more information
+> of the Samba distribution for more information
on the new method of loading printer drivers onto a Samba server.
</P
><P
@@ -12927,10 +12927,10 @@ NAME="RESTRICTANONYMOUS"
but it doesn't. Setting it to true will force these anonymous
connections to be denied, and the client will be required to always
supply a username and password when connecting. Use of this parameter
- is only recommened for homogenous NT client environments.</P
+ is only recommended for homogeneous NT client environments.</P
><P
>This parameter makes the use of macro expansions that rely
- on the username (%U, %G, etc) consistant. NT 4.0
+ on the username (%U, %G, etc) consistent. NT 4.0
likes to use anonymous connections when refreshing the share list,
and this is a way to work around that.</P
><P
@@ -14006,12 +14006,12 @@ NAME="SHOWADDPRINTERWIZARD"
for Windows NT/2000 client in Samba 2.2, a "Printers..." folder will
appear on Samba hosts in the share listing. Normally this folder will
contain an icon for the MS Add Printer Wizard (APW). However, it is
- possible to disable this feature regardless of the level of priviledge
- of the connacted user.</P
+ possible to disable this feature regardless of the level of privilege
+ of the connected user.</P
><P
>Under normal circumstances, the Windows NT/2000 client will
open a handle on the printer server with OpenPrinterEx() asking for
- Administrator priviledges. If the user does not have adminstrative
+ Administrator privileges. If the user does not have administrative
access on the print server (i.e is not root or a member of the
<TT
CLASS="PARAMETER"
@@ -14020,7 +14020,7 @@ CLASS="PARAMETER"
></TT
> group), the OpenPrinterEx()
call fails and the clients another open call with a request for
- a lower priviledge level. This should succeed, however the APW
+ a lower privilege level. This should succeed, however the APW
icon will not be displayed.</P
><P
>Disabling the <TT
@@ -14034,7 +14034,7 @@ CLASS="PARAMETER"
CLASS="EMPHASIS"
> Note :</I
>This does not prevent the same user from having
- administrative priviledge on an individual printer.</P
+ administrative privilege on an individual printer.</P
><P
>See also <A
HREF="#ADDPRINTERCOMMAND"
@@ -15188,7 +15188,7 @@ CLASS="CONSTANT"
> LOG_DEBUG</TT
>.</P
><P
->This paramter sets the threshold for sending messages
+>This parameter sets the threshold for sending messages
to syslog. Only messages with debug level less than this value
will be sent to syslog.</P
><P
@@ -15395,7 +15395,7 @@ NAME="UNIXREALNAME"
><P
>This boolean parameter when set causes samba
to supply the real name field from the unix password file to
- the client. This isuseful for setting up mail clients and WWW
+ the client. This is useful for setting up mail clients and WWW
browsers on systems used by more than one person.</P
><P
>Default: <B
@@ -15607,7 +15607,7 @@ CLASS="PARAMETER"
of all users in the netgroup group of that name.</P
><P
>Note that searching though a groups database can take
- quite some time, snd some clients may time out during the
+ quite some time, and some clients may time out during the
search.</P
><P
>See the section <A
@@ -15644,7 +15644,7 @@ NAME="USERNAMELEVEL"
><P
>If this parameter is set to non-zero the behavior changes.
This parameter is a number that specifies the number of uppercase
- combinations to try whilst trying to determine the UNIX user name. The
+ combinations to try while trying to determine the UNIX user name. The
higher the number the more combinations will be tried, but the slower
the discovery of usernames will be. Use this parameter when you have
strange usernames on your UNIX machine, such as <TT
@@ -16311,7 +16311,7 @@ CLASS="REPLACEABLE"
>user</I
></TT
>. This parameter
- is only applizaable when using the <TT
+ is only applicable when using the <TT
CLASS="FILENAME"
>pam_winbind.so</TT
>
diff --git a/docs/htmldocs/smbmount.8.html b/docs/htmldocs/smbmount.8.html
index 62ceffe1b4c..0b1e84b3301 100644
--- a/docs/htmldocs/smbmount.8.html
+++ b/docs/htmldocs/smbmount.8.html
@@ -24,7 +24,7 @@ NAME="AEN5"
></A
><H2
>Name</H2
->smbmount&nbsp;--&nbsp;mount and smbfs filesystem</DIV
+>smbmount&nbsp;--&nbsp;mount an smbfs filesystem</DIV
><DIV
CLASS="REFSYNOPSISDIV"
><A
diff --git a/docs/manpages/smb.conf.5 b/docs/manpages/smb.conf.5
index b740605fb6b..4de4faa1aa4 100644
--- a/docs/manpages/smb.conf.5
+++ b/docs/manpages/smb.conf.5
@@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
-.TH "SMB.CONF" "5" "02 March 2001" "" ""
+.TH "SMB.CONF" "5" "06 March 2001" "" ""
.SH NAME
smb.conf \- The configuration file for the Samba suite
.SH "SYNOPSIS"
@@ -65,7 +65,7 @@ given plus a description of the access rights which are granted
to the user of the service. Some housekeeping options are
also specifiable.
.PP
-Sections are either filespace services (used by the
+Sections are either file share services (used by the
client as an extension of their native file systems) or
printable services (used by the client to access print services
on the host running the server).
@@ -123,7 +123,7 @@ elsewhere):
parameters in this section apply to the server
as a whole, or are defaults for sections which do not
specifically define certain items. See the notes
-under paraMETERS for more information.
+under PARAMETERS for more information.
.SS "THE HOMES SECTION"
.PP
If a section called homes is included in the
@@ -349,7 +349,7 @@ by %u.
the Samba version.
.TP
\fB%h\fR
-the internet hostname that Samba is running
+the Internet hostname that Samba is running
on.
.TP
\fB%m\fR
@@ -362,7 +362,7 @@ to change your config based on what the client calls you. Your
server can have a "dual personality".
.TP
\fB%M\fR
-the internet name of the client machine.
+the Internet name of the client machine.
.TP
\fB%N\fR
the name of your NIS home directory server.
@@ -455,10 +455,10 @@ NT server, in that it is case insensitive but case preserving.
.SH "NOTE ABOUT USERNAME/PASSWORD VALIDATION"
.PP
There are a number of ways in which a user can connect
-to a service. The server follows the following steps in determining
+to a service. The server uses the following steps in determining
if it will allow a connection to a specified service. If all the
-steps fail then the connection request is rejected. If one of the
-steps pass then the following steps are not checked.
+steps fail, then the connection request is rejected. However, if one of the
+steps succeeds, then the following steps are not checked.
.PP
If the service is marked "guest only = yes" then
steps 1 to 5 are skipped.
@@ -971,7 +971,7 @@ each parameter for details. Note that some are synonyms.
\fIwrite raw\fR
.SH "COMPLETE LIST OF SERVICE PARAMETERS"
.PP
-Here is a list of all service parameters. See the section of
+Here is a list of all service parameters. See the section on
each parameter for details. Note that some are synonyms.
.TP 0.2i
\(bu
@@ -1320,7 +1320,7 @@ each parameter for details. Note that some are synonyms.
\fBadd user script (G)\fR
This is the full pathname to a script that will
be run \fBAS ROOT\fR by smbd(8)
- <URL:smbd.8.html> under special circumstances decribed below.
+ <URL:smbd.8.html> under special circumstances described below.
Normally, a Samba server requires that UNIX users are
created for all users accessing files on this server. For sites
@@ -1400,7 +1400,7 @@ order:
.RE
.PP
All parameters are filled in from the PRINTER_INFO_2 structure sent
-by the Windows NT/2000 client with one excpetion. The "Windows 9x
+by the Windows NT/2000 client with one exception. The "Windows 9x
driver location" parameter is included for backwards compatibility
only. The remaining fields in the structure are generated from answers
to the APW questions.
@@ -1463,7 +1463,7 @@ This specifies what type of server
\fBnmbd\fR <URL:nmbd.8.html>
will announce itself as, to a network neighborhood browse
list. By default this is set to Windows NT. The valid options
-are : "NT" (which is a synonym for "NT Server"), "NT Server",
+are : "NT Server" (which can also be written as "NT"),
"NT Workstation", "Win95" or "WfW" meaning Windows NT Server,
Windows NT Workstation, Windows 95 and Windows for Workgroups
respectively. Do not change this parameter unless you have a
@@ -1680,7 +1680,7 @@ page a Windows or DOS client is using, open a DOS command prompt
and type the command \fBchcp\fR. This will output
the code page. The default for USA MS-DOS, Windows 95, and
Windows NT releases is code page 437. The default for western
-european releases of the above operating systems is code page 850.
+European releases of the above operating systems is code page 850.
This parameter tells smbd(8) <URL:smbd.8.html>
which of the \fIcodepage.XXX
@@ -2025,7 +2025,7 @@ Default: \fBdelete readonly = no\fR
\fBdelete user script (G)\fR
This is the full pathname to a script that will
be run \fBAS ROOT\fR by \fBsmbd(8)\fR <URL:smbd.8.html> under special circumstances
-decribed below.
+described below.
Normally, a Samba server requires that UNIX users are
created for all users accessing files on this server. For sites
@@ -2146,7 +2146,7 @@ this function.
The external program will be passed a single parameter indicating
a directory in the filesystem being queried. This will typically consist
of the string \fI./\fR. The script should return two
-integers in ascii. The first should be the total disk space in blocks,
+integers in ASCII. The first should be the total disk space in blocks,
and the second should be the number of available blocks. An optional
third return value can give the block size in bytes. The default
blocksize is 1024 bytes.
@@ -2357,7 +2357,7 @@ If \fBdomain logons = yes\fR
, then the default behavior is to enable the \fIdomain
master\fR parameter. If \fIdomain logons\fR is
not enabled (the default setting), then neither will \fIdomain
-master\fR ne enabled by default.
+master\fR be enabled by default.
Default: \fBdomain master = auto\fR
.TP
@@ -2717,7 +2717,7 @@ group\fR.
\fBguest account (S)\fR
This is a username which will be used for access
to services which are specified as \fI guest ok\fR (see below). Whatever privileges this
-ser has will be available to any client connecting to the guest service.
+user has will be available to any client connecting to the guest service.
Typically this user will exist in the password file, but will not
have a valid login. The user account "ftp" is often a good choice
for this parameter. If a username is specified in a given service,
@@ -2736,7 +2736,7 @@ Example: \fBguest account = ftp\fR
.TP
\fBguest ok (S)\fR
If this parameter is yes for
-a service, then no password is equired to connect to the service.
+a service, then no password is required to connect to the service.
Privileges will be those of the \fI guest account\fR.
See the section below on \fI security\fR for more information about this option.
@@ -2996,12 +2996,12 @@ a broadcast/mask pair.
.PP
The "mask" parameters can either be a bit length (such
as 24 for a C class network) or a full netmask in dotted
-decmal form.
+decimal form.
.PP
.PP
The "IP" parameters above can either be a full dotted
decimal IP address or a hostname which will be looked up via
-the OSes normal hostname resolution mechanisms.
+the OS's normal hostname resolution mechanisms.
.PP
.PP
For example, the following line:
@@ -3070,7 +3070,7 @@ Default: \fBkeepalive = 300\fR
Example: \fBkeepalive = 600\fR
.TP
\fBkernel oplocks (G)\fR
-For UNIXs that support kernel based \fIoplocks\fR
+For UNIXes that support kernel based \fIoplocks\fR
(currently only IRIX and the Linux 2.4 kernel), this parameter
allows the use of them to be turned on or off.
@@ -3102,7 +3102,7 @@ of releasing all oplocks on a second open, as in traditional,
exclusive oplocks). This allows all openers of the file that
support level2 oplocks to cache the file for read-ahead only (ie.
they may not cache writes or lock requests) and increases performance
-for many acesses of files that are not commonly written (such as
+for many accesses of files that are not commonly written (such as
application .EXE files).
Once one of the clients which have a read-only oplock
@@ -3223,7 +3223,7 @@ You should never need to set this parameter.
Default: \fBlocking = yes\fR
.TP
\fBlog file (G)\fR
-This options allows you to override the name
+This option allows you to override the name
of the Samba log file (also known as the debug file).
This option takes the standard substitutions, allowing
@@ -3593,7 +3593,7 @@ you would use:
One very useful case is to remove the annoying \fI;1
\fRoff the ends of filenames on some CDROMS (only visible
-under some UNIXs). To do this use a map of (*;1 *;).
+under some UNIXes). To do this use a map of (*;1 *;).
Default: \fBno mangled map\fR
@@ -4248,7 +4248,7 @@ This boolean option tells smbd whether to
issue oplocks (opportunistic locks) to file open requests on this
share. The oplock code can dramatically (approx. 30% or more) improve
the speed of access to files on Samba servers. It allows the clients
-to aggressively cache files ocally and you may want to disable this
+to aggressively cache files locally and you may want to disable this
option for unreliable network environments (it is turned on by
default in Windows NT Servers). For more information see the file
\fISpeed.txt\fR in the Samba \fIdocs/\fR
@@ -4433,9 +4433,9 @@ as a WinNT box) with this option, and using \fBsecurity = domain
\fRor \fBsecurity = server\fR you can get Samba
to do all its username/password validation via a remote server.
-This options sets the name of the password server to use.
+This option sets the name of the password server to use.
It must be a NetBIOS name, so if the machine's NetBIOS name is
-different from its internet name then you may have to add its NetBIOS
+different from its Internet name then you may have to add its NetBIOS
name to the lmhosts file which is stored in the same directory
as the \fIsmb.conf\fR file.
@@ -4460,14 +4460,14 @@ server!
The name of the password server takes the standard
substitutions, but probably the only useful one is \fI%m
\fR, which means the Samba server will use the incoming
-client as the passwordserver. If you use this then you better
-trust your clients, and you better restrict them with hosts allow!
+client as the password server. If you use this then you better
+trust your clients, and you had better restrict them with hosts allow!
If the \fIsecurity\fR parameter is set to
domain, then the list of machines in this
option must be a list of Primary or Backup Domain controllers for the
-Domain or the character '*', as the Samba server is cryptographicly
-in that domain, and will use cryptographicly authenticated RPC calls
+Domain or the character '*', as the Samba server is effectively
+in that domain, and will use cryptographically authenticated RPC calls
to authenticate the user logging on. The advantage of using \fB security = domain\fR is that if you list several hosts in the
\fIpassword server\fR option then \fBsmbd
\fRwill try each in turn till it finds one that responds. This
@@ -4679,7 +4679,7 @@ If there is neither a specified print command for a
printable service nor a global print command, spool files will
be created but not processed and (most importantly) not removed.
-Note that printing may fail on some UNIXs from the
+Note that printing may fail on some UNIXes from the
nobody account. If this happens then create
an alternative guest account that can print and set the \fIguest account\fR
in the [global] section.
@@ -4785,12 +4785,12 @@ Example: \fBprinter admin = admin, @staff\fR
parameter and will be removed in the next major release
following version 2.2. Please see the instructions in
\fIPRINTER_DRIVER2.txt\fR in the \fIdocs
-\fRofthe Samba distribution for more information
+\fRof the Samba distribution for more information
on the new method of loading printer drivers onto a Samba server.
This option allows you to control the string
that clients receive when they ask the server for the printer driver
-associated with a printer. If you are using Windows95 or WindowsNT
+associated with a printer. If you are using Windows95 or Windows NT
then you can use this to automate the setup of printers on your
system.
@@ -4799,7 +4799,7 @@ sensitive) that describes the appropriate printer driver for your
system. If you don't know the exact string to use then you should
first try with no \fI printer driver\fR option set and the client will
give you a list of printer drivers. The appropriate strings are
-shown in a scrollbox after you have chosen the printer manufacturer.
+shown in a scroll box after you have chosen the printer manufacturer.
See also \fIprinter
driver file\fR.
@@ -4811,7 +4811,7 @@ Example: \fBprinter driver = HP LaserJet 4L\fR
parameter and will be removed in the next major release
following version 2.2. Please see the instructions in
\fIPRINTER_DRIVER2.txt\fR in the \fIdocs
-\fRofthe Samba distribution for more information
+\fRof the Samba distribution for more information
on the new method of loading printer drivers onto a Samba server.
This parameter tells Samba where the printer driver
@@ -4839,7 +4839,7 @@ Example: \fBprinter driver file =
parameter and will be removed in the next major release
following version 2.2. Please see the instructions in
\fIPRINTER_DRIVER2.txt\fR in the \fIdocs
-\fRofthe Samba distribution for more information
+\fRof the Samba distribution for more information
on the new method of loading printer drivers onto a Samba server.
This parameter tells clients of a particular printer
@@ -5121,10 +5121,10 @@ case where the server is expecting the client to send a username,
but it doesn't. Setting it to true will force these anonymous
connections to be denied, and the client will be required to always
supply a username and password when connecting. Use of this parameter
-is only recommened for homogenous NT client environments.
+is only recommended for homogeneous NT client environments.
This parameter makes the use of macro expansions that rely
-on the username (%U, %G, etc) consistant. NT 4.0
+on the username (%U, %G, etc) consistent. NT 4.0
likes to use anonymous connections when refreshing the share list,
and this is a way to work around that.
@@ -5538,22 +5538,22 @@ With the introduction of MS-RPC based printing support
for Windows NT/2000 client in Samba 2.2, a "Printers..." folder will
appear on Samba hosts in the share listing. Normally this folder will
contain an icon for the MS Add Printer Wizard (APW). However, it is
-possible to disable this feature regardless of the level of priviledge
-of the connacted user.
+possible to disable this feature regardless of the level of privilege
+of the connected user.
Under normal circumstances, the Windows NT/2000 client will
open a handle on the printer server with OpenPrinterEx() asking for
-Administrator priviledges. If the user does not have adminstrative
+Administrator privileges. If the user does not have administrative
access on the print server (i.e is not root or a member of the
\fIprinter admin\fR group), the OpenPrinterEx()
call fails and the clients another open call with a request for
-a lower priviledge level. This should succeed, however the APW
+a lower privilege level. This should succeed, however the APW
icon will not be displayed.
Disabling the \fIshow add printer wizard\fR
parameter will always cause the OpenPrinterEx() on the server
to fail. Thus the APW icon will never be displayed. \fB Note :\fRThis does not prevent the same user from having
-administrative priviledge on an individual printer.
+administrative privilege on an individual printer.
See also \fIaddprinter
command\fR, \fIdeleteprinter command\fR, \fIprinter admin\fR
@@ -6058,7 +6058,7 @@ level one maps onto LOG_WARNING, debug level
two maps onto LOG_NOTICE, debug level three
maps onto LOG_INFO. All higher levels are mapped to LOG_DEBUG.
-This paramter sets the threshold for sending messages
+This parameter sets the threshold for sending messages
to syslog. Only messages with debug level less than this value
will be sent to syslog.
@@ -6133,7 +6133,7 @@ Default: \fBunix password sync = no\fR
\fBunix realname (G)\fR
This boolean parameter when set causes samba
to supply the real name field from the unix password file to
-the client. This isuseful for setting up mail clients and WWW
+the client. This is useful for setting up mail clients and WWW
browsers on systems used by more than one person.
Default: \fBunix realname = yes\fR
@@ -6231,7 +6231,7 @@ is compiled with netgroup support) and will expand to a list
of all users in the netgroup group of that name.
Note that searching though a groups database can take
-quite some time, snd some clients may time out during the
+quite some time, and some clients may time out during the
search.
See the section NOTE ABOUT
@@ -6253,7 +6253,7 @@ username is not found on the UNIX machine.
If this parameter is set to non-zero the behavior changes.
This parameter is a number that specifies the number of uppercase
-combinations to try whilst trying to determine the UNIX user name. The
+combinations to try while trying to determine the UNIX user name. The
higher the number the more combinations will be tried, but the slower
the discovery of usernames will be. Use this parameter when you have
strange usernames on your UNIX machine, such as AstrangeUser
@@ -6566,7 +6566,7 @@ available in Samba 3.0.
This parameter allows an admin to define the character
used when listing a username of the form of \fIDOMAIN
\fR\\\fIuser\fR. This parameter
-is only applizaable when using the \fIpam_winbind.so\fR
+is only applicable when using the \fIpam_winbind.so\fR
and \fInss_winbind.so\fR modules for UNIX services.
Example: \fBwinbind separator = \\\fR
diff --git a/docs/manpages/smbmnt.8 b/docs/manpages/smbmnt.8
index c675b5ba66c..a9fe5a463ba 100644
--- a/docs/manpages/smbmnt.8
+++ b/docs/manpages/smbmnt.8
@@ -3,7 +3,7 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
-.TH "SMBMNT" "8" "02 March 2001" "" ""
+.TH "SMBMNT" "8" "06 March 2001" "" ""
.SH NAME
smbmnt \- helper utility for mounting SMB filesystems
.SH SYNOPSIS
diff --git a/docs/manpages/smbmount.8 b/docs/manpages/smbmount.8
index 4b9db402ea2..caa507b8a74 100644
--- a/docs/manpages/smbmount.8
+++ b/docs/manpages/smbmount.8
@@ -3,9 +3,9 @@
.\" <http://shell.ipoline.com/~elmert/hacks/docbook2X/>
.\" Please send any bug reports, improvements, comments, patches,
.\" etc. to Steve Cheng <steve@ggi-project.org>.
-.TH "SMBMOUNT" "8" "02 March 2001" "" ""
+.TH "SMBMOUNT" "8" "06 March 2001" "" ""
.SH NAME
-smbmount \- mount and smbfs filesystem
+smbmount \- mount an smbfs filesystem
.SH SYNOPSIS
.sp
\fBsmbumount\fR \fBservice\fR \fBmount-point\fR [ \fB-o options\fR ]
generated by cgit (git 2.34.1) at 2024-11-19 03:32:29 +0000