sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-12-20 16:23:51 +03:00
Code Activity

syncing up with SAMBA_2_2

Browse Source
This commit is contained in:
Gerald Carter
-
parent 870e9e4e89
commit 1bc58c21b1
39 changed files with 8165 additions and 3013 deletions
Download Patch File Download Diff File Expand all files Collapse all files

193
docs/htmldocs/CVS-Access.html Normal file
View File

@@ -0,0 +1,193 @@
<HTML
><HEAD
><TITLE
>HOWTO Access Samba source code via CVS</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"
>HOWTO Access Samba source code via CVS</A
></H1
><HR></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="AEN3"
>Introduction</A
></H1
><P
>Samba is developed in an open environnment. Developers use CVS
(Concurrent Versioning System) to "checkin" (also known as
"commit") new source code. Samba's various CVS branches can
be accessed via anonymouns CVS using the instructions
detailed in this chapter.</P
><P
>This document is a modified version of the instructions found at
<A
HREF="http://samba.org/samba/cvs.html"
TARGET="_top"
>http://samba.org/samba/cvs.html</A
></P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN8"
>CVS Access to samba.org</A
></H1
><P
>The machine samba.org runs a publicly accessible CVS
repository for access to the source code of several packages,
including samba, rsync and jitterbug. There are two main ways of
accessing the CVS server on this host.</P
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN11"
>Access via CVSweb</A
></H2
><P
>You can access the source code via your
favourite WWW browser. This allows you to access the contents of
individual files in the repository and also to look at the revision
history and commit logs of individual files. You can also ask for a diff
listing between any two versions on the repository.</P
><P
>Use the URL : <A
HREF="http://samba.org/cgi-bin/cvsweb"
TARGET="_top"
>http://samba.org/cgi-bin/cvsweb</A
></P
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN16"
>Access via cvs</A
></H2
><P
>You can also access the source code via a
normal cvs client. This gives you much more control over you can
do with the repository and allows you to checkout whole source trees
and keep them uptodate via normal cvs commands. This is the
preferred method of access if you are a developer and not
just a casual browser.</P
><P
>To download the latest cvs source code, point your
browser at the URL : <A
HREF="http://www.cyclic.com/"
TARGET="_top"
>http://www.cyclic.com/</A
>.
and click on the 'How to get cvs' link. CVS is free software under
the GNU GPL (as is Samba). Note that there are several graphical CVS clients
which provide a graphical interface to the sometimes mundane CVS commands.
Links to theses clients are also available from http://www.cyclic.com.</P
><P
>To gain access via anonymous cvs use the following steps.
For this example it is assumed that you want a copy of the
samba source code. For the other source code repositories
on this system just substitute the correct package name</P
><P
></P
><OL
TYPE="1"
><LI
><P
> Install a recent copy of cvs. All you really need is a
copy of the cvs client binary.
</P
></LI
><LI
><P
> Run the command
</P
><P
> <B
CLASS="COMMAND"
>cvs -d :pserver:cvs@samba.org:/cvsroot login</B
>
</P
><P
> When it asks you for a password type <TT
CLASS="USERINPUT"
><B
>cvs</B
></TT
>.
</P
></LI
><LI
><P
> Run the command
</P
><P
> <B
CLASS="COMMAND"
>cvs -d :pserver:cvs@samba.org:/cvsroot co samba</B
>
</P
><P
> This will create a directory called samba containing the
latest samba source code (i.e. the HEAD tagged cvs branch). This
currently corresponds to the 3.0 development tree.
</P
><P
> CVS branches other HEAD can be obtained by using the <TT
CLASS="PARAMETER"
><I
>-r</I
></TT
>
and defining a tag name. A list of branch tag names can be found on the
"Development" page of the samba web site. A common request is to obtain the
latest 2.2 release code. This could be done by using the following command.
</P
><P
> <B
CLASS="COMMAND"
>cvs -d :pserver:cvs@samba.org:/cvsroot co -r SAMBA_2_2 samba</B
>
</P
></LI
><LI
><P
> Whenever you want to merge in the latest code changes use
the following command from within the samba directory:
</P
><P
> <B
CLASS="COMMAND"
>cvs update -d -P</B
>
</P
></LI
></OL
></DIV
></DIV
></DIV
></BODY
></HTML
>

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

File diff suppressed because it is too large Load Diff

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

File diff suppressed because it is too large Load Diff

12
docs/htmldocs/make_smbcodepage.1.html
View File

@@ -14,7 +14,7 @@ VLINK="#840084"
ALINK="#0000FF"
><H1
><A
NAME="FINDSMB"
NAME="MAKE-SMBCODEPAGE"
>make_smbcodepage</A
></H1
><DIV
@@ -104,24 +104,24 @@ CLASS="PARAMETER"
>inputfile</DT
><DD
><P
>This is the input file to process. In t
he '<TT
>This is the input file to process. In
the <TT
CLASS="PARAMETER"
><I
>c</I
></TT
>' case this will be a text
> case this will be a text
codepage definition file such as the ones found in the Samba
<TT
CLASS="FILENAME"
>source/codepages</TT
> directory. In
the '<TT
the <TT
CLASS="PARAMETER"
><I
>d</I
></TT
>' case this will be the
> case this will be the
binary format codepage definition file normally found in
the <TT
CLASS="FILENAME"

276
docs/htmldocs/make_unicodemap.1.html Normal file
View File

@@ -0,0 +1,276 @@
<HTML
><HEAD
><TITLE
>make_unicodemap</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.57"></HEAD
><BODY
CLASS="REFENTRY"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><H1
><A
NAME="MAKE-UNICODEMAP"
>make_unicodemap</A
></H1
><DIV
CLASS="REFNAMEDIV"
><A
NAME="AEN5"
></A
><H2
>Name</H2
>make_unicodemap&nbsp;--&nbsp;construct a unicode map file for Samba</DIV
><DIV
CLASS="REFSYNOPSISDIV"
><A
NAME="AEN8"
></A
><H2
>Synopsis</H2
><P
><B
CLASS="COMMAND"
>make_unicodemap</B
> {codepage} {inputfile} {outputfile}</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN14"
></A
><H2
>DESCRIPTION</H2
><P
> This tool is part of the <A
HREF="samba.7.html"
TARGET="_top"
>Samba</A
>
suite.
</P
><P
> <B
CLASS="COMMAND"
>make_unicodemap</B
> compiles text unicode map
files into binary unicodef map files for use with the
internationalization features of Samba 2.2.
</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN20"
></A
><H2
>OPTIONS</H2
><P
></P
><DIV
CLASS="VARIABLELIST"
><DL
><DT
>codepage</DT
><DD
><P
>This is the codepage or UNIX character
set we are processing (a number, e.g. 850).
</P
></DD
><DT
>inputfile</DT
><DD
><P
>This is the input file to process. This is a
text unicode map file such as the ones found in the Samba
<TT
CLASS="FILENAME"
>source/codepages</TT
> directory.
</P
></DD
><DT
>outputfile</DT
><DD
><P
>This is the binary output file to produce.
</P
></DD
></DL
></DIV
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN36"
></A
><H2
>Samba Unicode Map Files</H2
><P
> A text Samba unicode map file is a description that tells Samba
how to map characters from a specified DOS code page or UNIX character
set to 16 bit unicode.
</P
><P
>A binary Samba unicode map file is a binary representation
of the same information, including a value that specifies what
codepage or UNIX character set this file is describing.
</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN40"
></A
><H2
>Files</H2
><P
><TT
CLASS="FILENAME"
>CP&#60;codepage&#62;.TXT</TT
></P
><P
> These are the input (text) unicode map files provided
in the Samba <TT
CLASS="FILENAME"
>source/codepages</TT
>
directory.
</P
><P
> A text unicode map file consists of multiple lines
containing two fields. These fields are :
</P
><P
></P
><UL
><LI
><P
><TT
CLASS="PARAMETER"
><I
>character</I
></TT
> - which is
the (hex) character mapped on this line.
</P
></LI
><LI
><P
><TT
CLASS="PARAMETER"
><I
>unicode</I
></TT
> - which
is the (hex) 16 bit unicode character that the character
will map to.
</P
></LI
></UL
><P
> <TT
CLASS="FILENAME"
>unicode_map.&#60;codepage&#62;</TT
> - These are
the output (binary) unicode map files produced and placed in
the Samba destination <TT
CLASS="FILENAME"
>lib/codepage</TT
>
directory.
</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN57"
></A
><H2
>Installation</H2
><P
> The location of the server and its support files is a matter
for individual system administrators. The following are thus
suggestions only.
</P
><P
> It is recommended that the <B
CLASS="COMMAND"
>make_unicodemap</B
>
program be installed under the
<TT
CLASS="FILENAME"
>$prefix/samba</TT
> hierarchy,
in a directory readable by all, writeable only by root. The
program itself should be executable by all. The program
should NOT be setuid or setgid!
</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN63"
></A
><H2
>VERSION</H2
><P
>This man page is correct for version 2.2 of
the Samba suite.</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN66"
></A
><H2
>SEE ALSO</H2
><P
><A
HREF="smbd.8.html"
TARGET="_top"
><B
CLASS="COMMAND"
>smbd(8)</B
></A
>,
<A
HREF="smb.conf.5.html"
TARGET="_top"
>smb.conf(5)</A
>
</P
></DIV
><DIV
CLASS="REFSECT1"
><A
NAME="AEN72"
></A
><H2
>AUTHOR</H2
><P
>The original Samba software and related utilities
were created by Andrew Tridgell. Samba is now developed
by the Samba Team as an Open Source project similar
to the way the Linux kernel is developed.</P
><P
>The original Samba man pages were written by Karl Auer.
The man page sources were converted to YODL format (another
excellent piece of Open Source software, available at
<A
HREF="ftp://ftp.icce.rug.nl/pub/unix/"
TARGET="_top"
> ftp://ftp.icce.rug.nl/pub/unix/</A
>) and updated for the Samba 2.0
release by Jeremy Allison. The conversion to DocBook for
Samba 2.2 was done by Gerald Carter</P
></DIV
></BODY
></HTML
>

265
docs/htmldocs/printer_driver2.html
View File

@@ -83,23 +83,61 @@ TARGET="_top"
information</P
></LI
></UL
><P
>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
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
Windows 2000 clients: <I
CLASS="EMPHASIS"
>How to Add Printers with No User
Interaction in Windows 2000</I
></P
><P
><A
HREF="http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP"
TARGET="_top"
>http://support.microsoft.com/support/kb/articles/Q189/1/05.ASP</A
></P
></DIV
><DIV
CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN20"
NAME="AEN25"
>Configuration</A
></H1
><DIV
CLASS="WARNING"
><P
><I
CLASS="EMPHASIS"
>WARNING!!!</I
> 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
></P
><TABLE
CLASS="WARNING"
BORDER="1"
WIDTH="100%"
><TR
><TD
ALIGN="CENTER"
><B
>[print$] vs. [printer$]</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
@@ -124,21 +162,26 @@ the client.</P
>These parameters, including <TT
CLASS="PARAMETER"
><I
>printer driver
>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
>Migration section</A
>
of this document.</P
></TD
></TR
></TABLE
></DIV
><DIV
CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN30"
NAME="AEN36"
>Creating [print$]</A
></H2
><P
@@ -161,6 +204,11 @@ CLASS="PROGRAMLISTING"
guest ok = yes
browseable = yes
read only = yes
; since this share is configured as read only, then we need
; a 'write list'. Check the file system permissions to make
; sure this account can copy files to the share. If this
; is setup to a non-root account, then it should also exist
; as a 'printer admin'
write list = ntadmin</PRE
></P
><P
@@ -178,16 +226,17 @@ 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
>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
>guest
ok = yes</B
></A
> depends upon how your
site is configured. If users will be guaranteed to have
@@ -257,26 +306,26 @@ ALIGN="CENTER"
ALIGN="LEFT"
><P
>In order to currently add a new driver to you Samba host,
one of two conditions must hold true:</P
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
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
must be a member of the <A
HREF="smb.conf.5.html#PRINTERADMIN"
TARGET="_top"
><TT
CLASS="PARAMETER"
><I
>printer
admin</I
admin</I
></TT
></A
> list.</P
@@ -284,7 +333,8 @@ CLASS="PARAMETER"
></UL
><P
>Of course, the connected account must still possess access
to add files to the subdirectories beneath [print$].</P
to add files to the subdirectories beneath [print$]. Remember
that all file shares are set to 'read only' by default.</P
></TD
></TR
></TABLE
@@ -307,14 +357,34 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN65"
NAME="AEN71"
>Setting Drivers for Existing Printers</A
></H2
><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
Printers folder will have no real printer driver assigned
to them. By default, in Samba 2.2.0 this driver name was set to
<I
CLASS="EMPHASIS"
>NO PRINTER DRIVER AVAILABLE FOR THIS PRINTER</I
>.
Later versions changed this to a NULL string to allow the use
tof 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
><P
><I
CLASS="EMPHASIS"
>Device settings cannot be displayed. The driver
for the specified printer is not installed, only spooler
properties will be displayed. Do you want to install the
driver now?</I
></P
><P
>Click "No" in the error dialog and you will be presented with
the printer properties window. The way assign a driver to a
printer is to either</P
><P
></P
><UL
@@ -361,7 +431,7 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN78"
NAME="AEN88"
>Support a large number of printers</A
></H2
><P
@@ -413,7 +483,7 @@ Domain=[NARNIA] OS=[Unix] Server=[Samba 2.2.0-alpha3]
<TT
CLASS="PROMPT"
>$ </TT
>rpcclient pogo -U root%bleaK.er \
>rpcclient pogo -U root%secret \
<TT
CLASS="PROMPT"
>&gt; </TT
@@ -427,7 +497,7 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN89"
NAME="AEN99"
>Adding New Printers via the Windows NT APW</A
></H2
><P
@@ -449,7 +519,7 @@ CLASS="PARAMETER"
><I
>printer admin</I
></TT
>.
>).
</P
></LI
><LI
@@ -476,8 +546,8 @@ TARGET="_top"
><TT
CLASS="PARAMETER"
><I
>addprinter
command</I
>add
printer command</I
></TT
></A
> must have a defined value. The program
@@ -499,7 +569,7 @@ CLASS="COMMAND"
CLASS="PARAMETER"
><I
>add printer
program</I
command</I
></TT
> and reparse to the <TT
CLASS="FILENAME"
@@ -512,7 +582,7 @@ CLASS="PARAMETER"
><I
>add printer program</I
></TT
> is executed undet the context
> is executed under the context
of the connected user, not necessarily a root account.</P
><P
>There is a complementing <A
@@ -521,8 +591,8 @@ TARGET="_top"
><TT
CLASS="PARAMETER"
><I
>deleteprinter
command</I
>delete
printer command</I
></TT
></A
> for removing entries from the "Printers..."
@@ -533,7 +603,7 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN114"
NAME="AEN124"
>Samba and Printer Ports</A
></H2
><P
@@ -570,7 +640,7 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN122"
NAME="AEN132"
>The Imprints Toolset</A
></H1
><P
@@ -588,7 +658,7 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN126"
NAME="AEN136"
>What is Imprints?</A
></H2
><P
@@ -620,7 +690,7 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN136"
NAME="AEN146"
>Creating Printer Driver Packages</A
></H2
><P
@@ -636,7 +706,7 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN139"
NAME="AEN149"
>The Imprints server</A
></H2
><P
@@ -657,7 +727,7 @@ CLASS="SECT2"
><HR><H2
CLASS="SECT2"
><A
NAME="AEN143"
NAME="AEN153"
>The Installation Client</A
></H2
><P
@@ -734,7 +804,7 @@ CLASS="FILENAME"
></P
><P
>will reveal that Windows NT always uses the NT driver
name. The is ok as Windows NT always requires that at least
name. This 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
@@ -751,18 +821,61 @@ CLASS="SECT1"
><HR><H1
CLASS="SECT1"
><A
NAME="AEN165"
NAME="AEN175"
><A
NAME="MIGRATION"
></A
>Migration to from Samba 2.0.x to
2.2.x</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
>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.</P
><P
>Windows clients have a tendency to remember things for quite a while.
For example, if a Windows NT client has attached to a Samba 2.0 server,
it will remember the server as a LanMan printer server. Upgrading
the Samba host to 2.2 makes support for MSRPC printing possible, but
the NT client will still remember the previous setting.</P
><P
>In order to give an NT client printing "amesia" (only necessary if you
want to use the newer MSRPC printing functionality in Samba), delete
the registry keys associated with the print server contained in
<TT
CLASS="CONSTANT"
>[HKLM\SYSTEM\CurrentControlSet\Control\Print]</TT
>. The
spooler service on the client should be stopped prior to doing this:</P
><P
><TT
CLASS="PROMPT"
>C:\WINNT\ &#62;</TT
> <TT
CLASS="USERINPUT"
><B
>net stop spooler</B
></TT
></P
><P
><I
CLASS="EMPHASIS"
>All the normal disclaimers about editing the registry go
here.</I
> Be careful, and know what you are doing.</P
><P
>The spooler service should be restarted after you have finished
removing the appropriate registry entries by replacing the
<B
CLASS="COMMAND"
>stop</B
> command above with <B
CLASS="COMMAND"
>start</B
>.</P
><P
>Windows 9x clients will continue to use LanMan printing calls
with a 2.2 Samba server so there is no need to perform any of these
modifications on non-NT clients.</P
><DIV
CLASS="WARNING"
><P
@@ -782,9 +895,8 @@ ALIGN="CENTER"
><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
>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
@@ -796,7 +908,7 @@ CLASS="PARAMETER"
>printer driver file (G)</I
></TT
>
</P
</P
></LI
><LI
><P
@@ -806,7 +918,7 @@ CLASS="PARAMETER"
>printer driver (S)</I
></TT
>
</P
</P
></LI
><LI
><P
@@ -816,7 +928,7 @@ CLASS="PARAMETER"
>printer driver location (S)</I
></TT
>
</P
</P
></LI
></UL
></TD
@@ -831,31 +943,31 @@ CLASS="PARAMETER"
><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
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
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
driver support but do 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
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
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
@@ -863,23 +975,22 @@ CLASS="COMMAND"
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
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
> and <B
CLASS="COMMAND"
>rpcclient</B
>. See the
Imprints installation client at <A
Imprints installation client at <A
HREF="http://imprints.sourceforge.net/"
TARGET="_top"
>http://imprints.sourceforge.net/</A
>
for an example.
</P
for an example.
</P
></LI
></UL
></DIV

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

@@ -151,8 +151,9 @@ CLASS="PROGRAMLISTING"
>-l logbasename</DT
><DD
><P
>File name for log/debug files. .client will be
appended. The log file is never removed by the client.
>File name for log/debug files. The extension
'.client' will be appended. The log file is never removed
by the client.
</P
></DD
><DT
@@ -235,14 +236,8 @@ CLASS="COMMAND"
><DD
><P
>Set the SMB domain of the username. This
overrides the default domain which is the domain of the
server specified with the <TT
CLASS="PARAMETER"
><I
>-S</I
></TT
> option.
If the domain specified is the same as the server's NetBIOS name,
overrides the default domain which is the domain defined in
smb.conf. If the domain specified is the same as the server's NetBIOS name,
it causes the client to log on using the server's local SAM (as
opposed to the Domain SAM). </P
></DD
@@ -252,7 +247,7 @@ CLASS="PARAMETER"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN91"
NAME="AEN90"
></A
><H2
>COMMANDS</H2
@@ -275,14 +270,18 @@ CLASS="COMMAND"
><B
CLASS="COMMAND"
>lookupsids</B
></P
> - Resolve a list
of SIDs to usernames.
</P
></LI
><LI
><P
><B
CLASS="COMMAND"
>lookupnames</B
></P
> - Resolve s list
of usernames to SIDs.
</P
></LI
><LI
><P
@@ -329,6 +328,34 @@ CLASS="COMMAND"
>querygroupmem</B
></P
></LI
><LI
><P
><B
CLASS="COMMAND"
>queryaliasmem</B
></P
></LI
><LI
><P
><B
CLASS="COMMAND"
>querydispinfo</B
></P
></LI
><LI
><P
><B
CLASS="COMMAND"
>querydominfo</B
></P
></LI
><LI
><P
><B
CLASS="COMMAND"
>enumdomgroups</B
></P
></LI
></UL
><P
> </P
@@ -429,6 +456,17 @@ CLASS="COMMAND"
><P
><B
CLASS="COMMAND"
>deldriver</B
> - Delete the
specified printer driver for all architectures. This
does not delete the actual driver files from the server,
only the entry from the server's list of drivers.
</P
></LI
><LI
><P
><B
CLASS="COMMAND"
>enumdata</B
> - Enumerate all
printer setting data stored on the server. On Windows NT clients,
@@ -603,7 +641,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN196"
NAME="AEN210"
></A
><H2
>BUGS</H2
@@ -644,7 +682,7 @@ CLASS="COMMAND"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN206"
NAME="AEN220"
></A
><H2
>VERSION</H2
@@ -655,7 +693,7 @@ NAME="AEN206"
><DIV
CLASS="REFSECT1"
><A
NAME="AEN209"
NAME="AEN223"
></A
><H2
>AUTHOR</H2

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

File diff suppressed because it is too large Load Diff

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

@@ -14,7 +14,7 @@ VLINK="#840084"
ALINK="#0000FF"
><H1
><A
NAME="FINDSMB"
NAME="SMBCONTROL"
>smbcontrol</A
></H1
><DIV

4
docs/htmldocs/smbspool.8.html
View File

@@ -14,7 +14,7 @@ VLINK="#840084"
ALINK="#0000FF"
><H1
><A
NAME="FINDSMB"
NAME="SMBSPOOL"
>smbspool</A
></H1
><DIV
@@ -24,7 +24,7 @@ NAME="AEN5"
></A
><H2
>Name</H2
>nmblookup&nbsp;--&nbsp;send print file to an SMB printer</DIV
>smbspool&nbsp;--&nbsp;send print file to an SMB printer</DIV
><DIV
CLASS="REFSYNOPSISDIV"
><A

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

@@ -14,7 +14,7 @@ VLINK="#840084"
ALINK="#0000FF"
><H1
><A
NAME="FINDSMB"
NAME="SMBSTATUS"
>smbstatus</A
></H1
><DIV

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

@@ -35,7 +35,7 @@ NAME="AEN8"
><P
><B
CLASS="COMMAND"
>nmblookup</B
>swat</B
> [-s &#60;smb config file&#62;] [-a]</P
></DIV
><DIV